Resolution:
Description:
============
This is an introduction as to why inbound services support load balancing while outbound services do not support load balancing.

Environment:
===========
TIBCO ActiveMatrix® Adapter for PeopleSoft 5.x, 6.x

Resolution:
==========
For inbound services - Subscription service and Request Response service support load balancing because they are unaffected by threads and are safe across instances.

For outbound services -

(1). CI publication service does not support load balancing.

There can be multiple publication services in the same instance but they cannot be for the same CI. PSJOA (the API through which the adapter invokes PeopleSoft application) is thread-safe for different CIs.

Publication services cannot be used across instances because multiple instances for publication mode can yield duplicates. This is because if one adapter instances reads the publication object TIB_MQUEUE_CI and retrieves 20 records, it will try to immediately update the records to "I" to signify "in-process of publication". However, if another instance reads these same records before the update of the status of the record is complete, then it will also try to publish.

If you configure a CI publication service as load balanced you may get duplicate messages. One way to minimize publication duplicates is to increase polling intervals in the instances and decrease the batch size.

(2). Message Publication services can be used as load balanced.
There is another solution for publication service that can be load balanced. If you choose Message Publication services and use a JMS queue, publication can be load balanced across different adapter instances listening to the same queue.

Does TIBCO ActiveMatrix® Adapter for PeopleSoft support load balance?