Concurrency for JMS Sender Adapter - Async/Sync Bridge

[Former Member]

Hi,

We have implemented a number of Async/Sync bridges using JMS Adapters, and are encountering problems scaling the solution.

Async-Sync Bridge Scenario:

JMS Sender Adapter -> Integration Server -> Sync ABAP Proxy (CRM) -> JMS Receiver Adapter

The bridge is using the Adapter Framework modules: RequestResponseBean & ResponseOnewayBean within the Sender Adapter.

The problem is that concurrency of processing seems to be driven from the number of Java Server Cluster Nodes on the Adapter Engine. The JMS sender adapters do not appear to read from the external messaging system (MQ) in a concurrent fashion. They appear to process in a sequential manner per Adapter:

1. Read from request Message Queue (MQ)

2. Send request for processing (IS)

3. Wait response message

4. Receive response message

5. Write response message to Message Queue (MQ)

.

6. Read from request Message Queue (MQ)

7. Send request for processing (IS)

8. Wait response message

9....

We need to be able to introduce some means of scaling the solution so that mesages can be read from the MQ request message queue in a concurrent manner. Hopefully we can do this without adding more javer server nodes to the Adapter Engine.

We were looking intot he possibility of tuning AS Java properties that control the number of connections to the Messaging System of the Adapter Engine but this has not provided a solution.

Any information on this topic would be much appreciated.

regards

Murray

[kkram]

As far as I know, the only wasy for JMS adapter to do concurrent reads from a queue is by having multiple server nodes. This is document in note 856346, point 6.2

Thanks

KK