The information in this appendix assumes that you are familiar with PeopleSoft Integration Broker (in release 8.4) or Application Messaging (in release 8.1). For more information, see Appendix D, "Using PeopleSoft Integration Broker". For a complete description before you work with Oracle Application Adapter for PeopleSoft, see your PeopleSoft documentation.

Note:

In PeopleSoft release 8.1, the messaging architecture is called Application Messaging and includes Application Messaging Gateway. In release 8.4, the messaging architecture is called Integration Broker, which includes Integration Gateway. When discussing release- independent issues, this section uses release 8.4 terminology. When discussing release-specific issues, it uses release-specific terminology.

This step is optional when configuring the HTTP Connector. The HTTP Target Connector is supplied with your PeopleSoft application, and no special configuration steps are required. If you choose, you may configure default connection values on the Gateway. You can override these values when you configure the node.

If you do not see the TCPIPTARGET84 Connector ID, click Load and scroll to locate TCPIPTARGET84 in the list.

If TCPIPTARGET84 still does not appear, the connector class file was not installed in the Integration Gateway.

Perform the following steps:

Click the Properties URL for TCPIPTARGET84.

The Properties pane for TCPIPTARGET84 is displayed, as shown in Figure B-2. Default values appear for the host and the port. For complex business situations, you can override this setting on the individual node.

Edit additional transactions by clicking Edit and navigating to the Transaction Detail tab.

In the Transaction Detail tab, select Inactive from the Status list.

Inactive status is for initial testing only. After you test your configuration, you may change the status to Active and have as many nodes and transactions as required to satisfy your business requirements.

Click Save.

You can now send XML messages to your PeopleSoft XML listener.

Configuring the HTTP Target Connector

The HTTP Target Connector is supplied with your PeopleSoft application, and no special configuration steps are required. If you choose, you may configure default connection values on the Gateway. You can override these values when you configure the node. To configure the gateway for the HTTP Target Connector:

In a Web browser, open your PeopleSoft 8.4 application.

In the Menu pane, expand PeopleTools, then expand Integration Broker, and click Gateways.

Open the LOCAL Gateway ID.

A pane similar to the following Gateway ID pane is displayed, as shown in Figure B-6.

This is the default HTTP address (system and port) on which your PeopleSoft XML listener is listening for incoming messages.

Note:

For complex business situations, you can override this setting on the individual node.

Click OK.

The Gateway window is displayed.

Scroll to the bottom of the window and click Save.

You have finished configuring the gateway for the HTTP Target Connector.

Configuring the HTTP Connector

Starting with release 8.4, the Integration Broker is delivered with an HTTP Outbound Connector. This connector can be used in place of the TCP/IP 8.4 connector for sending messages to Oracle WebLogic Server.

Inactive status is for initial testing only. After you test your configuration, you may change the status to Active and have as many nodes and transactions as required to satisfy your business requirements.