x

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, Integration Broker, and then click Gateways.
3. Open the LOCAL Gateway ID.

   The following image shows the PeopleSoft Gateway ID pane on the right. The right pane includes the following: the Local Gateway check box, the Gateway URL field, fields with information for Connector ID, Description, and Connector Class Name, Properties hyperlinks, and the Refresh and Load buttons.

   

   1. 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. For information about installing the TCPIPTAGER84 connector, see the iWay Installation and Configuration manual.

   2. Click the Properties hyperlink for TCPIPTARGET84.

      The following image shows the Properties pane for TCPIPTARGET84. Gateways is selected in the Menu pane. The right pane contains the following components: the Gateway ID, Connector ID, and OK and Cancel buttons.

      

      Default values appear for the host and the port. For complex business situations, you can override this setting on the individual node.

   3. Type values for the host and the port for the machine on which your PeopleSoft XML listener is listening for incoming messages.
4. Click OK.

   The Gateway window opens.

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

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

x

To configure the node for the TCP/IP84 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 Using PeopleSoft 8 Integration Broker or your PeopleSoft documentation.

   The following image shows the Node Info tab for External node on the right. It includes the following: Description, Company ID, Hub Node, Master Node, Image Name, and Code Set Group Name fields; Node Type, Routing Type, and Authentication Options lists; Active Node, Local Node, Default Local Node, and Non-Repudiation check boxes; and Copy, Rename, and Delete buttons.

   

   1. From the Node Type drop-down list, select External.
   2. From the Routing Type drop-down list, select Implicit.
3. Select the Connectors tab.
   1. Select TCPIPTARGET84 as the Connector ID.

      Default values appear for the host and the port.

   2. Type values for the host and the port for the machine and port that route XML to your application 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.
4. Select the Transactions tab.

   The following image shows the TCP/IP84 Connector Transaction tab for the External node type. It contains transaction details and the Add Transaction, Save, and Return to Search buttons.

   

   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 make the Transaction Detail tab available and view transaction details for the LOCATION_SYNC message, click Edit.

      The following image shows the TCP/IP84 Connector Transaction Detail tab, which contains information for the following: Node Name, Effective Date, Transaction Type, Request Message, Request Message Version, and Routing Type. The Comment field is currently empty.

      

      You can add the message with which you are working.

   3. Verify that the Routing Type is Implicit.
5. Click Save and return to the Transactions tab.
   1. To edit additional transactions, click the Edit hyperlink to navigate to the Transaction Detail tab.
   2. In the Transaction Detail tab, from the Status drop-down list, select Inactive.

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

6. Click Save.

You are ready to send XML messages to your PeopleSoft XML Listener.

x

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, Integration Broker, and then click Gateways.
3. Open the LOCAL Gateway ID.

   The following image shows the HTTP Target Connector Gateway ID pane on the right and includes the following: the Local Gateway check box, the Gateway URL field, fields with information for Connector ID, Description, and Connector Class Name, Properties hyperlinks, and the Refresh and Load buttons.

   

   1. If you do not see the HTTPTARGET Connector ID, click Load.
   2. If it still does not appear, consult with your PeopleSoft system administrator as your Gateway was not installed properly.
4. Click the Properties hyperlink for HTTPTARGET.

   The Properties pane for HTTPTARGET opens, as shown in the following image. Gateways is selected in the Menu pane on the left. On the right, information about Headers appears.

   

5. Scroll to the bottom and type a value for the PRIMARYURL.

   This is the default HTTP address (machine 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.

6. Click OK.

   The Gateway window opens.

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

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

x

To configure the node to use the HTTP Connector:

1. In the Menu pane, expand PeopleTools, Integration Broker, and then click Node Definitions.
2. Select the node that you want to configure.

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

   The following image shows the Node Info tab for External node on the right. It includes the following: Description, Company ID, Hub Node, Master Node, Image Name, and Code Set Group Name fields; Node Type, Routing Type, and Authentication Options lists; Active Node, Local Node, Default Local Node, and Non-Repudiation check boxes; and Copy, Rename, and Delete buttons.

   

   1. From the Node Type drop-down list, select External.
   2. From the Routing Type drop-down list, select Implicit.
3. Select the Connectors tab.

   The following image shows the PeopleSoft Integration Broker Connectors tab for the External node. It includes the following: Gateway ID, Connector ID, Property ID, Property Name, and Value fields and Save and Return to Search buttons.

   

   1. Change the Connector ID to HTTPTARGET.
   2. Type a value for each property based on the information in the following table.

      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.

   3. Click Save.
   4. If you are warned that you are changing the Connector, click OK.
4. Select the Transactions tab.

   The following image shows the Transactions tab selected. It contains the node name, Transaction information, and the Add Transaction, Save, and Return to Search buttons.

   

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

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

   The following image shows the PeopleSoft Integration Broker Transaction Detail tab for the External node. It contains information for the following: Effective Date, Status, Transaction Type, Request Message, Request Message Version, and Routing Type. Currently, the Comment field is empty.

   

   You can add the message with which you are working.

   1. Verify that the Routing Type is Implicit.
   2. Click Save.
6. Click Return to Transaction List.
   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 can change the status to Active and have as many nodes and transactions as required to satisfy your business requirements.

7. Click Save.

You are ready to send XML messages to your PeopleSoft XML Listener.