Skip to Content
Former Member
Jul 04, 2011 at 09:36 AM

Proxy to JMS Scenario: switch from sync to async proxy,does it makes sense?


Hi @all,

i've implemented a sync proxy to JMS scenario that works well. Backend is ECC 6.0 and Middleware is PI 7.1.

Business Case: Run a request with a number and get a response back with a corresponding entry for the number. That means, there is always a response expected.

Now the following thing appears: the receiver system could not handle many calls at one time (200 calls are planned at each run), the calls reduces the performance. Now gys at receiver system likes to develope a buffer of 10 seconds between the requests to handle some kind of load balancing with that. That means for the request that it the response takes +10 seconds back to backend. It is also possible to handle that in SAP backend with a waiting-statement in coding, so there is no need to go from sync to async - but the customer requested us to implement this scenario in async.

JMS is always async, I know. But the Service Interfaces for Inbound and Outbound are of mode sync - so I can call my outbound Interface class in backend with Importing Output and Exporting Input.

My question is: makes it sense to go from sync to an async scenario?

And how looks the coding in backend for the response? I guess that it only makes sense to switch to async when no response entry is needed (example: for write operations).

Thanks in Advance,