Skip to Content
avatar image
Former Member

How to send fixed number of Sync requests in SAP PI 7.3(Java stack)?

Hi All,

We are working on SAP PI 7.3 (java stack).We have a Sync Scenario say WebService-PI-Proxy.

There can be large number of sync requests(say 600) with PI, but due to infrastructure constraints, SAP ECC can handle maximum of 15 requests at a time. In this scenario, Is there any way to hold all the sync requests in PI and send only 15 requests to SAP ECC at a time? As soon as any thread is free, another request from PI will be taken for processing.

I understand that we might have to increase the timeout parameter for request from Webservice which is acceptable in our case.

Can this be achieved (sending only fixed number of Sync requests to SAP ECC while rest are waiting in PI) ?

What is the maximum value for time out can be set for request from webservice?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 27, 2012 at 07:04 AM


    Ideally this approach should be controlled in source sender system.

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 27, 2012 at 07:38 AM


    i think you should do a performance test. Java Only provides actually a good performance, it is good possible that a message only needs a second to be processed, at least at PI if the message is not too big and the mapping not too complex. I guess most time will be consumed by the ECC receiver system, you should quantify that.

    Depending from the result you can change the timeout parametes (one would not be enough). In 7.3 you can set timeout individual for each adapter.

    Of course Praveen is 100% right, if the sender system is able to send them one by one, the hole solution would be much more stabil.



    Add comment
    10|10000 characters needed characters exceeded

    • >>SAP ECC can handle maximum of 15 requests at a time

      I am not sure, if max 15 request can be limitation on ECC end. As far as I know there is nothing you need to do in PI since limitation is from ECC end. Even if some thing can be done in PI, chances are high for time-out's.

      I think, you do not require even PI in this case, as proxies can be called directly either using inbound plain HTTP service in ECC (or) by exposing proxy as a webservice in ECC.