Designing: Creating the PeopleSoft Node to Receive Enterprise Service Bus HTTP Posts

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

Creating the PeopleSoft Node to Receive Enterprise Service Bus HTTP Posts

The procedure describes how to create and configure PeopleSoft nodes for Enterprise Service Bus HTTP posting.

To Create PeopleSoft Nodes to Receive Enterprise Service Bus HTTP Posts

In the PeopleTools Application Designer, click New on the File menu. The New dialog box appears.
Click Message Node and click OK to display the Message Node dialog box for Node 1.
Right-click the Locations pane and click Insert Location. The Location dialog box appears.
Enter the URL for the PeopleSoft Gateway Servlet and click OK.
For Apache:
```
http://PSFTHOST/servlets/psft.pt8.gateway.GatewayServlet
```
For WebLogic:
```
http://PSFTHOST/servlets/gateway
```
where PSFTHOST is the name of the host computer where PeopleSoft runs.

The URL name displays in the Message Node dialog box similar to Figure 7.
Figure 7 PeopleSoft Node for Receiving Enterprise Service Bus HTTP Posts
Click Save As on the File menu.
Enter the name of the message node.
From the File menu, click Open. The Open Object window appears.
To verify that the message node is ready for use, select Message Node from the Object Type list and click Open.
A list of all message nodes displays.. The name of the new message node appears in the Objects matching selection criteria pane.

Message nodes with PSFT prefixes are created by the PeopleSoft installation. PSFT_EP is the PeopleSoft local node for the Financials application. It is specified as a subscriber to messages sent from the PeopleSoft Adapter, and a publisher of messages to the HTTP server.
Figure 8 Viewing Message Nodes