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. Details of differences between Releases 8.1 and 8.4 are discussed in other topics.
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 can use any supplied message.
In Release 8.1, the Message Channel also provides preliminary routing instructions; you can specify the Message Nodes that handle the message. Each Message Channel can route messages to multiple Message Nodes.
In Release 8.1, the primary function of the Message Node is to specify the Gateway that receives the messages.
Much of the "intelligence" built into the Message Channel in Release 8.1 moved to the Message Node in Release 8.4 which provides additional flexibility. 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.
iWay Software |