High Level Overview of Integration Broker Publishing Steps

The Integration Broker is a complicated PeopleSoft module and can be very confusing if you don’t know what to look for.

An integration message goes through several stages in both the “publishing” system and the “subscribing” system before the integration message has completed processing. It also gets handed off between many different application server processes and at any point one of those processes can crash or be down and it can cause the message to not complete.

For some perspective the message goes through these high level steps with each one being a failure point. This information will help when looking at the Message Monitor.

Publishing System Steps

A user interacting with the application triggers some “publication” PeopleCode that creates the message.
The integration broker receives the publication event and creates the message in the publishing broker. The message will now only be visible in the “Message Queue” on the message monitor.
If the Message Channel is paused, the publication will stop here until the channel is un-paused.
A second app server process wakes up and looks at the new message and determines where it needs to publish to and creates the “publication contracts.” The message contracts will now be visible in the “Publication Queue” in the message monitor. For example, for each password change there could be 3 contracts created, one for each destination database.
A third process wakes up and sees the new publication contracts and processes each publication to each database separately.

At this point, the data is still not changed in the target systems. If the publishing database says that the messages published, you need to verify that the subscribing database had completed processing the message.

Subscribing System Steps

The subscribing database broker receives the published message and creates the new message instance in the integration broker. The message will now be visible only in the “Message Queue” on the subscribing message monitor.
If the Message Channel is paused the process will stop here until the channel becomes un-paused.
A second subscribing process wakes up and sees the new message instance and determines what subscription contracts need to be created. The message contracts will now be visible on the “Subscription Queue” on the Message Monitor.
Once the subscription contracts are created, another process wakes up and processes the subscription contract PeopleCode.
If all of the above contracts have been processed then the message is considered completed and both databases have been updated.

Author Info

Chris Malek

Chris Malek is a PeopleTools® Technical Consultant with over two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.

Work with Chris

Contents

High Level Overview of Integration Broker Publishing Steps

Publishing System Steps

Subscribing System Steps

Chris Malek

PeopleSoft Simple Web Services (SWS)

PeopleSoft Simple Web Services (SWS)

PeopleSoft Simple Web Services (SWS)

PeopleSoft Simple Web Services (SWS)