Contents
Delay Processing in Inbound Asynchronous Subscription Handlers
When setting up routings for subscription handlers, you can define a “delay” of when the subscription handler will process. There are various reasons why you would want to do this. Here we will show the result of the delay and what to expect in the integration broker. This is not well documented in PeopleBooks.
In the following example, we are pushing PERSON_BASIC_SYNC from a Campus Solutions PeopleSoft database to an HCM instance. We desire the HCM system to wait for a few minutes before processing the inbound message.
In the HCM PERSON_BASIC_SYNC service Operation Routing page, we set up a delay. This only seems to be available for inbound messages.
First, we set up the inbound routing and set the “Delay Processing” to 3 which represents 3 minutes based on testing (again no PeopleBooks documentation).
So what happens to the message when you set up a delay? It turns out that the “Operation Instance” gets put into a status of “hold” during the duration of the delay period as seen in this screenshot.
If we drill into the detail of the service operation, we will see that the subscription contracts are not created during the delay period.
Once the delay period has elapsed, the subscription contracts are then created for processing by the appropriate application server processes.
Chris Malek
Chris Malek s 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