Designing: Additional HTTP Configurations

Classic Java CAPS

Developing Java CAPS Projects

Using SOAP Message Handlers

Creating a Runtime Environment

Designing Business Processes in the Sun Business Process Manager

Working with TCP/IP HL7 Collaborations

Developing Sun Master Indexes (Repository)

Developing Sun Master Patient Indexes

Developing OTDs for Application Adapters

Developing OTDs for Communication Adapters

Developing OTDs for Database Adapters

Developing OTDs for Web Server Adapters

Designing with Application Adapters

Building an Oracle Applications Custom Pre-Validation Package

Pre-Validation Scripts

Pre-Validation Procedures

To Build a Custom Pre-Validation Package for a Non-Supported Open Interface

Concurrent Manager Request Function

Naming Conventions for the Oracle Interface

Oracle Applications Manufacturing Module

Inventory Module

Purchase Order Import Module

Order Entry Module

Oracle Applications Financial Module

Accounts Payable Module

Accounts Receivable Module

Cash Management Module

Fixed Assets Module

General Ledger Module

Oracle Applications Validation Error Codes

Financial Budget-GL

Configuring the PeopleSoft Server for the PeopleSoft Adapter Projects

Configuring PeopleTools 8.42

Configuring PeopleSoft for Enterprise Service Bus Posting

Additional HTTP Configurations

Additional JMS Configurations

Verifying PeopleSoft Server Logs

Notes on PeopleSoft Server Disconnections for JMS

Configuring PeopleTools 8.13

Creating the PeopleSoft Node to Receive Enterprise Service Bus HTTP Posts

Activating the Message Definition to Receive Enterprise Service Bus Posts

Defining Message Channel Routing Rules

Adding the PeopleSoft Subscription Handler

Configuring for Subscription

Creating an HTTP Adapter Message Node

Activating the Message Definition for Subscription

Defining the Message Channel Routing Rules

Adding the HTTP Publication Handler

Accessing Non-Local Queue Managers and Non-Local Queues

To Connect to a Remote WebSphere MQ Queue.

Creating the WebSphere MQ Queue

To Create the WebSphere MQ Queue

IBM WebSphere MQ Server and Queue Manager Limits and Settings

Designing with Communication Adapters

Designing with Web Server Adapters

SWIFT Integration Projects

Java EE Based Components

Designing with Sun JCA Adapters

About the TCP/IP JCA Adapter

Defining Constants and Variables

Using Database Operations

Developing Sun Master Indexes

Using the JMS JCA Wizard

Using the JAXB Wizard and Code-Seeder Pallete

Additional HTTP Configurations

Verifying the HTTP Listening Connector

Two types of HTTP connectors are used with PeopleSoft adapter Projects that use HTTP to communicate to PeopleSoft: the HTTP listening connector and the HTTP target connector.

The PeopleSoft server uses the HTTP listening connector to receive messages from. The PeopleSoft adapter HTTP client external application is used to post to the HTTP listening connector. You do not have to configure the HTTP listening connector; the connector is started automatically by the PeopleSoft Integration Application.

However, you must set the location for the HTTP listening connector in the Environment properties of the PeopleSoft Adapter. The routing of messages in the PeopleSoft server is decided by the content of the message in the header section.

The HTTP target connector is used to send HTTP messages to Enterprise Service Bus. The Enterprise Service Bus component receiving the HTTP message is a servlet. The servlet name is specified in the Connectivity Map.

To Verify HTTP Listening Connector

In a text editor, open the web.xml file in the following directory:
```
bea\wlserv6.1\config\peoplesoft\applications\PSIGN\WEB-INF
```
where, bea is the WebLogic installation directory.
Verify that the following section is included, and add it if it is absent.
Figure 6 Verifying the HTTP Listening Connector