Using Sequential and Parallel Processing

Subscribing systems can process service operations sequentially or in parallel.

In sequential processing, the subscribing system processes messages defined in inbound service operations in the order received.

In parallel processing, the subscribing system processes messages defined in service operations in parallel, in no specific sequence.

You can use sequential or parallel processing when using either full table publishing or batch publishing.

You configure sequential or parallel processing at the queue level on the subscribing system.

Note the following prerequisites for using pre-processing and post-processing tasks in conjunction with the parallel processing feature of the utility:

• The pre-processing and post-processing task functionality of the parallel processing feature of the Publish Utility is currently available in the HCM application only.

• To use pre-processing and post-processing tasks in conjunction with parallel processing you must apply the following resolutions to both the publishing and subscribing systems:

  • HCM 9.0 systems: Resolution 827074.

  • HCM 9.1 systems: Resolution 827350.

To implement sequential processing, on the subscribing system associate the message on the inbound service operation with an ordered queue.

See PeopleTools: PeopleSoft Integration Broker, “Managing Service Operations,” Defining Service Operation Version Information, “Specifying Messages for Service Operations”

To implement parallel processing, on the subscribing system associate the message on the inbound service operation with an unordered queue. If the message is currently assigned to an ordered queue, assign it to a unordered queue.

In order to realize any performance gain from parallel processing, multiple subscription handlers must be set up for the subscription node to process messages on the unordered queue.

Only Messages that utilize functions inside the PeopleCode function library FUNCLIB_EOEIP for their pre-processing, post-processing and subscription handler logic will have the order of processing logic enforced when using the parallel processing mode.

See PeopleTools: PeopleSoft Integration Broker, “Managing Service Operations,” Defining Service Operation Version Information, “Specifying Messages for Service Operations”

See PeopleTools: PeopleSoft Integration Broker, “Managing Service Operation Queues,” Adding Queue Definitions

If your business requirements change, you can change the processing mode from sequential processing to parallel processing or vice versa, by moving the message associated with the service operation to the appropriate queue type.

If you have coded pre-processing or post-processing tasks, you must move the code for those tasks in the service operation message. More information is provided elsewhere in this documentation.

See Performing Pre-Processing and Post-Processing Tasks.