B Configuring the PeopleSoft Message Router

This appendix describes how to configure and test a TCP/IP or HTTP target connector and a TCP/IP handler for PeopleSoft. It contains the following topics:

• Configuring the TCP/IP or HTTP Target Connector for PeopleSoft 8.4

• Configuring the TCP/IP Target Connector

• Configuring the Node for the TCP/IP 8.4 Connector

• Configuring the TCP/IP Handler for PeopleSoft 8.1

• Testing Your PeopleSoft Configuration

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.

Configuring the TCP/IP or HTTP Target Connector for PeopleSoft 8.4

The procedures in this topic assume that your Integration Broker environment is configured and tested. For more information, see Appendix D, "Using PeopleSoft Integration Broker".

1. Configure the gateway for the TCP/IP Target Connector or HTTP Target Connector. For more information, see "Configuring the TCP/IP Target Connector".

   
   

   Note: 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.

   
   

2. Configure the node. For more information, see "Configuring the Node for the TCP/IP 8.4 Connector".

   
   

   Note: Starting with release 8.4, the Integration Broker is delivered with an HTTP Outbound Connector. For more information, see "Configuring the HTTP Connector".

   
   

Configuring the TCP/IP Target Connector

To configure the gateway for the TCP/IP Target Connector:

1. In a Web browser, open your PeopleSoft release 8.4 application.

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

3. Open the LOCAL Gateway ID.

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

   Figure B-1 Gateway ID Pane

   
   Description of "Figure B-1 Gateway ID Pane"
   
   

4. 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:

   1. 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.

      Figure B-2 Properties Pane

      
      Description of "Figure B-2 Properties Pane"
      
      

   2. Enter the values for the host and the port for the system on which your PeopleSoft XML listener is listening for incoming messages.

5. Click OK.

   The Gateway window is displayed.

6. Scroll to the bottom of the window and click Save.

You have finished configuring the gateway for the TCP/IP Target Connector.

Configuring the Node for the TCP/IP 8.4 Connector

To configure the node for the TCP/IP 8.4 Connector:

1. In the Menu pane, select PeopleTools, Integration Broker, and then click Node Definitions.

2. Select the node that you want to configure.

   
   

   Note: This procedure uses a node called EXTERNAL. For more information about creating and using nodes, see Appendix D, "Using PeopleSoft Integration Broker" or your PeopleSoft documentation.

   
   

   Perform the following steps:

   1. Select External from the Node Type list.

   2. Select Implicit from the Routing Type list.

3. Select the Connectors tab, as shown in Figure B-3.

   Figure B-3 Connectors Tab

   
   Description of "Figure B-3 Connectors Tab"
   
   

   Perform the following steps:

   1. Select TCPIPTARGET84 as the Connector ID.

      Default values appear for the host and the port.

   2. Enter the values for the host and the port for the system and port that route XML to Oracle WebLogic Server. You can accept or override the default values for individual nodes.

   3. Click Save.

4. If you are warned that you are changing the connector, click OK.

5. Select the Transactions tab, as shown in Figure B-4.

   Figure B-4 Transactions Tab

   
   Description of "Figure B-4 Transactions Tab"
   
   

   Perform the following steps:

   1. If there are no transactions, click Add Transaction to add the message with which you are working. In this procedure, the node is already configured with the LOCATION_SYNC message.

   2. To view transaction details for the LOCATION_SYNC message, click Edit.

      The Transaction Detail tab appears, as shown in Figure B-5.

      Figure B-5 Transaction Detail Tab

      
      Description of "Figure B-5 Transaction Detail Tab"
      
      

   3. Add the message with which you are working.

   4. Verify that the Routing Type is Implicit.

6. Click Save.

7. Return to the Transactions tab.

   Perform the following steps:

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

   2. 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.

8. 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:

1. In a Web browser, open your PeopleSoft 8.4 application.

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

3. Open the LOCAL Gateway ID.

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

   Figure B-6 HTTP Target Connector Gateway ID Pane

   
   Description of "Figure B-6 HTTP Target Connector Gateway ID Pane"
   
   

4. If you do not see the HTTPTARGET Connector ID, click Load.

   If it does not appear, your Gateway was not installed properly. Check with your PeopleSoft system administrator.

5. Click the Properties URL for HTTPTARGET.

   The Properties pane for HTTPTARGET displays default values, as shown in Figure B-7.

   Figure B-7 HTTPTARGET Properties Pane

   
   Description of "Figure B-7 HTTPTARGET Properties Pane"
   
   

6. Scroll to the bottom and enter a value for the PRIMARYURL.

   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.

   
   

7. Click OK.

   The Gateway window is displayed.

8. 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.

To configure the node to use the HTTP Connector:

Figure B-8 Connector Configuration Pane

Description of "Figure B-8 Connector Configuration Pane"

1. In the Menu pane, expand PeopleTools, Integration Broker, and then click Node Definitions, as shown in Figure B-8.

2. Select the node that you want to configure.

   
   

   Note: This procedure uses a node called EXTERNAL. For more information about creating and using nodes, see Appendix D, "Using PeopleSoft Integration Broker" or your PeopleSoft documentation.

   
   

   Perform the following steps:

   1. From the Node Type list, select External.

   2. From the Routing Type list, select Implicit.

      Figure B-9 PeopleSoft Integration Broker Connectors Tab

      
      Description of "Figure B-9 PeopleSoft Integration Broker Connectors Tab"
      
      

3. Select the Connectors tab, as shown in Figure B-9.

   Perform the following steps:

   1. Change the Connector ID to HTTPTARGET.

   2. Enter a value for each property based on the following:

      Property ID	Property Name	Value
      HEADER	sendUncompressed	Y
      HTTPPROPERTY	Method	POST
      PRIMARYURL	URL	URL and the port of the HTTP listener

      
      
   
   

   Note: For complex business situations you can configure multiple nodes and multiple listeners.

   
   

4. Click Save.

5. If you are warned that you are changing the Connector, click OK.

6. Select the Transactions tab, as shown in Figure B-10.

   Figure B-10 PeopleSoft Integration Broker Transactions Tab

   
   Description of "Figure B-10 PeopleSoft Integration Broker Transactions Tab"
   
   

7. If there are no transactions, click Add Transaction.

   In this procedure, the node is already configured with the LOCATION_SYNC message.

   The Transaction Detail tab appears, as shown in Figure B-11.

   Figure B-11 Transaction Detail Tab

   
   Description of "Figure B-11 Transaction Detail Tab"
   
   

   You can add the message with which you are working.

   1. Verify that the Routing Type is Implicit.

   2. Click Save.

8. Return to the Transaction List. Perform the following steps:

   1. If there are other transactions, edit them.

   2. Set the status to Inactive.

      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.

9. Click Save on the Transaction List.

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

Configuring the TCP/IP Handler for PeopleSoft 8.1

The following procedure assumes that your Application Messaging environment is properly configured and tested. For more information, see Appendix D, "Using PeopleSoft Integration Broker".

To configure the TCP/IP Handler for PeopleSoft 8.1 to send messages to Oracle WebLogic Server:

1. In a Web browser, launch the PeopleSoft 8.1 Gateway Configuration servlet interface.

2. If the Simple File Handler is currently loaded, unload and delete it before proceeding.

   You must see an empty Handler directory, as shown in Figure B-12.

   Figure B-12 Empty Handler Directory

   
   Description of "Figure B-12 Empty Handler Directory"
   
   

3. Click Add handler, as shown in Figure B-13.

   Figure B-13 Loaded Add Handler Directory

   
   Description of "Figure B-13 Loaded Add Handler Directory"
   
   

   Perform the following steps:

   1. Enter the full path of TCPIPHandler81 (case-sensitive):

      psft.pt8.tcphandler.TCPIPHandler81
      

   2. Click Save.

4. Click Load.

   The PeopleSoft Handler Directory window is displayed.

5. Click Configure.

   The TCPIP81 Handler Directory window is displayed.

6. Click Add a TCPIP81 node.

   
   

   Note: The screens illustrating this procedure show a node named EXTERNAL. For more information about creating and using nodes, see Appendix D, "Using PeopleSoft Integration Broker" or your PeopleSoft documentation.

   
   

   The Add TCPIP81 Handler window is displayed, as shown in Figure B-14.

   Figure B-14 Add TCPIP81 Handler Window

   
   Description of "Figure B-14 Add TCPIP81 Handler Window"
   
   

7. Enter the requested values based on the information in the following table.

   Field	Value Example	Description
   Node Name	EXTERNAL	The name of the TCP/IP node.
   Host Name	172.19.25.152	The system on which your PeopleSoft XML listener is listening for incoming messages.
   Port	3694	The port on which your PeopleSoft XML listener is listening for incoming messages.
   Trace Directory	/tmp	The directory where a trace file is created when errors occur in message delivery.

   
   

   The system does not validate your entries.

8. Click Save.

   The TCPIP81 Handler Directory window is displayed, as shown in Figure B-15.

   Figure B-15 TCPIP81 Handler Directory Window

   
   Description of "Figure B-15 TCPIP81 Handler Directory Window"
   
   

9. For your changes to take effect, click Back to Handler Directory to return to the PeopleSoft 8.1 Handler Directory window.

10. Click Unload and re-Load TCPIPHandler81.

You can now send messages from PeopleSoft to Oracle Application Adapter for PeopleSoft.

Testing Your PeopleSoft Configuration

PeopleSoft 8.1 and 8.4 provide a ping node mechanism for testing your configuration. The mechanism functions identically in both versions.

Test your configuration to ensure that:

• Oracle WebLogic Server is up and running.

• The server name and port number for PeopleSoft and Oracle WebLogic Server match.

• The default page for HTTP exists.

To test a PeopleSoft configuration:

1. In a Web browser, open your PeopleSoft application.

2. Navigate to the message monitoring menu.

   For PeopleSoft 8.4:

   1. In the menu pane, expand PeopleTools, Integration Broker, and Monitor.

   2. Select Monitor Message.

   For PeopleSoft 8.1:

   1. In the menu pane, expand Home, PeopleTools, Application Message Monitor, and Use.

   2. Select Application Message Monitor.

3. Click the Node Status tab, as shown in Figure B-16.

   Figure B-16 Node Status Tab

   
   Description of "Figure B-16 Node Status Tab"
   
   

   Perform the following steps:

   1. From the Message Node Name list, select your node.

   2. Click Ping Node.

   If you properly configured both PeopleSoft and Oracle WebLogic Server, you receive a Success message.

   An error indicates a configuration problem. For more information, see the Integration Broker error log.