Scribd
Upload
60 views

Peoplesoft Integration Broker: "Using Outbound Synchronous Messages"

This document discusses how to configure PeopleSoft Integration Broker release 8.4 to send outbound asynchronous messages to a third-party application using the File Output connector. The key steps are: 1) Ensure the message is active and routed to the proper Message Channel. 2) Configure the Message Channel, IntegrationGateway.properties file, Integration Gateway, and File Output connector. 3) Create and configure a new Gateway node.

Uploaded by

chakrips
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
60 views

Peoplesoft Integration Broker: "Using Outbound Synchronous Messages"

This document discusses how to configure PeopleSoft Integration Broker release 8.4 to send outbound asynchronous messages to a third-party application using the File Output connector. The key steps are: 1) Ensure the message is active and routed to the proper Message Channel. 2) Configure the Message Channel, IntegrationGateway.properties file, Integration Gateway, and File Output connector. 3) Create and configure a new Gateway node.

Uploaded by

chakrips
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

This appendix describes how to configure and test PeopleSoft Integration Broker (release 8.

4) and PeopleSoft Application Messaging (release 8.1) using a PeopleSoft-supplied File Output interface. 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-generic issues, this section uses release 8.4 terminology. When discussing release-specific issues, it uses releasespecific terminology.

Note: This section is not a substitute for PeopleSoft documentation. For more complete and up-to-date information on PeopleSoft Messaging and Integration Broker, see the PeopleSoft Online Library for your PeopleSoft system.

PeopleSoft Integration Broker


PeopleSoft Integration Broker provides a mechanism for communicating with the outside world using XML files. Communication can take place between different PeopleSoft applications or between PeopleSoft and third-party systems. To subscribe to data, third-party applications can accept and process XML messages posted by PeopleSoft using the available PeopleSoft connectors or by adding a custom built connector to the Integration Gateway. This topic primarily covers publishing outbound asynchronous messages from a PeopleSoft system to a third-party application using the delivered File Output connector. For information on outbound synchronous messages, see "Using Outbound Synchronous Messages".To send a message, you must properly configure various internal structures and processes. The following descriptions are generally release-generic. Detailed differences between releases 8.1 and 8.4 are discussed in other topics.

Message A Message is a container for the data that goes into the XML. It contains basic structural information, such as records and fields. The Message must be in an Active status to send the XML file

Message Channel The Message Channel is a mechanism for structuring records into logical groupings. Each Message can belong to only one Message Channel. The Message Channel must be in an Active (Run) status for the Message to be delivered.In release 8.1, the Message Channel also provides preliminary routing instructions; you can specify which Message Nodes handle the message. Each Message Channel can route messages to multiple Message Nodes

Message Node Message node functionality changed from 8.1 to 8.4:In release 8.1, the primary function of the Message Node is to specify which Gateway receives the messages.In release 8.4, much of the "intelligence" that was built into the Message Channel moved to the Message Node. This provides additional flexibility over release 8.1. You can specify which messages the Message Node can handle. In addition, the Gateway Connector is bound to the Message Node. Each Message Node can route messages to only one Connector.

Integration Gateway The Integration Gateway is a program that runs on the PeopleSoft Web Server. It is the physical hub between PeopleSoft and the third-party system.

Target Connector/Handler Connectors are Java programs that run under the control of the Integration Gateway and control the final output destination of the XML file. PeopleSoft release 8.4 comes with several connectors including HTTP, FTP, SMTP, JMS, POP3, and a Simple File connector that places the file in a directory on the Web Server. This section discusses the Simple File connector.

PeopleCode PeopleCode is the programming tool provided with PeopleTools that enables you to create complex application functionality. A message can only be initiated using specific PeopleCode instructions. This code is typically triggered by an application event, such as creating a new database entry through an online panel or through a batch job.

Most of the examples in this section use the LOCATION_SYNC message, which is a PeopleSoft Enterprise Integration Point (EIP) and is supplied with most PeopleSoft applications. If LOCATION_SYNC is not part of your package, you may use any supplied message.

Configuring Integration Broker in PeopleSoft 8.4


You can configure PeopleSoft 8.4 to send an asynchronous outbound message to the File Output connector. To configure application messaging in PeopleSoft 8.4: 1. Ensure that the message is active and is routed to the proper Message Channel. 2. Configure the Message Channel. 3. Configure the IntegrationGateway.properties file to communicate with your PeopleSoft 8.4 application. 4. Configure the Integration Gateway and File Output connector. 5. Create and configure a new Gateway node.

These tasks are described in detail in the following procedures. Ensuring the Message Is Active and Is Routed Correctly To ensure that the message is active and is routed to the proper Message Channel: 1. Open Application Designer. 2. On the File menu, point to Open, click Message, and then open the LOCATION_SYNC message. 3. To view the fields that are included in the Message, highlight LOCATION_TBL. 4. Right-click LOCATION_TBL and select Properties. 5. The Message Properties dialog box is displayed. 5. Select the Use tab. 6. Ensure the Active check box is selected. The message is routed to the Message Channel, ENTERPRISE_SETUP, and the default message version is VERSION_1 (messages can have multiple versions). 7. Click OK and then save the message. You have finished ensuring that the message is active and is routed correctly. Configuring the IntegrationGateway.properties File To configure the IntegrationGateway.properties file: 1. Open the IntegrationGateway.properties file using the editor of your choice. 2. Find the section of the file that specifies the JOLT connect string setting for the default application server. This is usually near line 75, and looks similar to the following:
3. ## JOLT connect string setting for optional Default Application Server. Do NOT specify a NODENAME. 4. # 5. # Example: 6. #ig.isc.serverURL=//MYSERVER:9000 7. #ig.isc.userid=MYUSERID 8. #ig.isc.password=MYPASSWORD 9. #ig.isc.toolsRel=8.40 10.

11. Uncomment (or copy and uncomment) the four lines that specify the connection. 12. Enter the appropriate information. In the following example, the tools release is 8.40.09:
ig.isc.serverURL=//isdsrv14:9000 ig.isc.userid=VP1 ig.isc.password=VP1 ig.isc.toolsRel=8.40.09

The PeopleSoft tools release must be precise to the last decimal.

Note: With release 8.42, the password must be stored in an encrypted format. PeopleSoft provides a script called PSCipher.bat (PSCipher.sh on UNIX) to accomplish encryption. Typically, this script is located in the path of the IntegrationGateway.properties file. Follow the instructions supplied by PeopleSoft to run this script.

You have finished configuring the IntegrationGateway.properties file. Configuring the Integration Gateway and the File Output Connector To configure the Integration Gateway and the File Output Connector: 1. In a Web browser, open your PeopleSoft 8.4 application in 4-tier mode. 2. In the Menu pane, expand PeopleTools, Integration Broker, and then click Gateways. 3. Open the LOCAL Gateway ID and enter the following Gateway URL:
4. hostname/PSIGW/PeopleSoftListeningConnector 5.

Where hostname is the name of your PeopleSoft Web Server. 4. Click Refresh. A message appears stating the outcome of the refresh process.

You might also like