Beyond Standard Messaging
Real-time Interfaces to Non-PeopleSoft Systems
Posted on 1/8/2007 (originally published in print on 3/1/2005)
by Shannon Whitley
Over the past year I've implemented several new interfaces using Integration Broker. Working mostly on real-time transfers of data to third-party systems, I can say that I've been pleased with the overall results of the integrations. All of these interfaces involve non-PeopleSoft systems, so an important part of each interface is transforming the PeopleSoft XML into something that the other system can understand. In this article, I'll describe how some of these transformations work and provide some transformation tips along the way.
The examples that I'll discuss come from a PeopleTools 8.44 system. I'm going to assume that you have a basic understanding of Integration Broker messaging and the PeopleSoft Internal Message Format. Additionally, I'm only planning to specifically cover outbound transactions in my examples, but the concepts can be applied to inbound integrations as well.
PeopleSoft Internal Message Format
Integration Broker relies on XML messages that are defined specifically for PeopleSoft systems. The format of the XML inside the message is based on PeopleSoft's scroll and record structure. See Listing 1 for an example of XML from a PeopleSoft message created by the addition of a new Action Reason code in the HCM application.
To continue reading this article you must have a current VP1 Subscription.
