The PeopleSoft Integration Broker provides a mechanism for communicating with the Integration Appliance using XML files. To subscribe to data, the Integration Appliance accepts and processes XML messages posted by PeopleSoft using the available PeopleSoft connectors.
For more information about configuring the PeopleSoft Integration Broker to publish outbound asynchronous messages to the Integration Appliance, see Configuring the PeopleSoft Integration Broker.
For more information about PeopleSoft Messaging and Integration Broker, see the PeopleSoft Online Library for your PeopleSoft system.
Term | Definition |
---|---|
Message | 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 | 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. Each Message Channel can route messages to multiple Message Nodes. |
Message Node | Each Message Node can route messages to only one Connector. You can specify which messages the Message Node can handle. In addition, the Gateway Connector is bound to the Message Node. |
Integration Gateway | A program that runs on the PeopleSoft Web Server. It is the physical hub between PeopleSoft and the third-party system. |
Target Connector/Handler | The 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. |
PeopleCode | 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. |