Skip to Content
avatar image
Former Member

Sync Interface Proxy - Soap Webservice - determine bottleneck

Dear guys,

a customer is running a synchronous scenario ABAP proxy to SOAP webservice using SAP PI 7.11.

At the moment the scenario is setup as classical scenario (dual stack).

The processing of single message tooks around 30+ seconds.

Looking at the performance monitoring as well as the HTTP_SEND step takes most of the time 30 seconds.

The webservice is called via HTTPS (SSL certificate is used).

Looking at the audit log the step taking the most time is "SOAP: request message entering the adapter with user J2EE_GUEST"

At the moment I am not sure which component of this interface is the reason for this long processing time, either PI or the receiver webservice which is called using SOAP adapter.

I suppose it should be the webservice, but would appreciate if someone could share his/her thoughts on that, before getting in touch with supplier of the webservice.

Redesign the interface using ICO (java-only) is for sure an option, but I would focus on the understanding of the issue first.

I appreciate your help.

Thanks in advance.

Best regards


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jun 19, 2014 at 11:57 AM

    Hello Jochen,

    Check note 1593920 Synchronous SOAP sender calls: fine tune PI under high load, which describes some of the tuning possibilities on the PI side.

    Below is some further info on how to tune in various locations described in the above note:
    1) Messaging System queue properties after XI 3.0 SP19 / XI 7.0SP11

    2) Note 1945745 How to increase the number of HTTP Worker (FCA) threads in PI

    3) Note 1621719 Timeout parameters in SOAP Sender/Receiver Adapter

    Also check the performance guide available via note 894509 PI Performance Check.


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Mark Smyth

      Hi Mark

      indeed it is not easy to determine the bottleneck.

      In the meantime I changed config to java-only processing (integrated configuration), so that sender is now SOAP (XI 3.0).

      Regarding thread count still 5 max threads is defined as per default.

      While running a test the SOAP resources seem not be exhausted, only 1 thread is busy


      I would conclude that this indicates that the bottleneck is not within PI.

      Please correct me, if I am wrong

      Best regards


  • Jun 20, 2014 at 04:11 AM

    Hi Jochen,

    From your screenshot of adapter monitoring, it looks like the SOAP end point is responsible for this delay. You can check the Start time and end time in IE.

    So the answer is the web service is taking too long to respond. Please check with the responsible team. 30 seconds is too long for a synchronous interface.


    Add comment
    10|10000 characters needed characters exceeded