Example 3: Handling Client Messages

In this example, a JMS application sends messages to ActiveMatrix BusinessWorks for processing. Each JMS client authenticates to the JMS server with a different user ID. Messages from different clients are permitted to be processed concurrently, but all messages received from the same client must be processed in the order they are received.

Example of handling incoming messages

In this example, you can use the expression pfx:ActivityOutput/JMSProperties/pfx:JMSXUserID in the Sequencing Key field of the Misc tab of the JMS Topic Subscriber process starter. This ensures that all messages from a specific client are processed in the order they are received.