Motivation:

The PI performance check is one of the central SAP documents for the tuning of the PI system. The last version of this document was released more than two years ago. In the meantime with the PI releases 7.31 and 7.4 many new features were introduced that also have an impact on the performance of message processing. Therefore it was time to update the guide. Apart from adapting the layout to the general SCN template format, many chapters were reworked and many new topics were added. This topics span the whole PI scope – from the Advanced Adapter Engine, the ABAP Integration Engine and also the impact and eventual changes on the IDoc and Proxy SAP backend systems.

New topics added in the new version:

  • Long processing time for Lean Message Search

  • IDoc posting configuration on receiver side

  • Tuning of SOAP sender adapter

  • More information about IDOC_AAE adapter tuning

  • Packaging for Java IDoc and Java Proxy adapter (PI 7.31 and higher)

  • New Adapter Framework Scheduler for polling adapters

  • New performance monitor for Adapter Engine (PI 7.31 and higher)

  • Enhancements of the maxReceiver parameter for individual interfaces (PI 7.31 SP11 and higher)

  • Include latest information for staging and logging
    (restructured to be part of Java only chapter) (PI 7.3 and higher)

  • FCA Thread tuning for incoming HTTP requests (PI 7.1 and higher)

  • Enhancements in the Proxy framework on sender/receiver ERPs

  • Large message queues on PI Adapter Engine (PI 7.31 and higher)

  • Generic J2EE database monitoring in NWA

  • Appendix section: XPI_Inspector

Where can I find the new guide?

The guide can be downloaded from SCN using the following link: http://scn.sap.com/docs/DOC-11909.


Is this guide only relevant for dual-stack PI?

The Performance guide discusses all the components of a PI installation – meaning the ABAP Integration Server as well as the Advanced Adapter Engine (AAE). The tuning options described for the AAE are also relevant for the Java Only PI (Advanced Adapter Engine Extended (AEX)) and the PI part of a Process Orchestration (PO) system. The aspects of NetWeaver BPM in a PO system are not covered in the guide yet . This is planned for the next version (see below).

Is this document only relevant for PI 7.31/PI 7.4?

In general the document aims at all releases higher 7.1. Of course many of the key capabilities of the AAE are only contained in later releases and these topics are then not relevant for older releases. But in general the document always mentions the corresponding release that is necessary to use the described feature. The guide can also be used generally for 7.0x systems. Older versions of the guide are still available in the Service Marketplace as described in SAP Note 894509.

Future plans for this document:

It is planned to update this guide more regularly in the future. Also we plan to add tuning sections for NetWeaver BPM to the guide to also reflect the increased usage of Process Orchestration capabilities. The relevant changes will be announced in this blog.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Nagarajan Saravanan

    Hi Mike,

    Thanks a lot for this great document. In Page-54, it is said – To avoid blockage SAP Note 1903431 allows the usage of different URLs for specific interfaces. This way you could isolate interfaces with a very high volume on a dedicated entry point using its own set of FCA Threads.

    But the sap note 1903431 talks about just two end points MessageServletInternal and MessageServletExternal. So if I have 10 interfaces all with Sender SOAP scenario, I need to use same http://<host&gt;:port/XISOAPAdapter/MessageServletExternal end point for all of them. Isn’t it?

    Then how can we configure different URLs for specific interfaces [and how to configure max FCA threads for each interface], as mentioned in Page 54?

    We are on SAP PO 7.4 SP9.

    – Saravanan N

    (0) 
    1. Mike Sibler Post author

      Hi Saravanan,

      sorry for the late reply. As you could see in the Note you can only define three different URLs. Therefore it is not possible to have one URL per interface. This is also not the purpose. You should think about this like a separation/prioritization of interfaces. While most interfaces will use the standard URL /XISOAPAdapter/MessageServlet high priority or low priority interfaces can be separated using the alternative URLs.

      A second use case is if you have a synchronou interface that is calling PI again via SOAP adapter (I know the design already sounds questionable). In such cases it was easy to construct a deadlock if the first interface takes all FCA threads so that the second interface can not be started. Also here it is sufficient to have two different URLs to avoid a complete blockage.


      I hope this explains the possible use cases of this special parameter.


      Best regards,

      Mike

      (0) 
      1. Nagarajan Saravanan

        Thanks Mike.

        So, all these three URLs work for all the SOAP interfaces. But it is upto the developer/interface-designer to choose which one of these URLs to be used for an interface.

        Is my understanding correct?

        http://<host>:port/XISOAPAdapter/MessageServlet

        http://<host>:port/XISOAPAdapter/MessageServletInternal

        http://<host>:port/XISOAPAdapter/MessageServletExternal

        I believe Sender Java HTTP Adapter too uses FCA server threads. Would this URL behaviour applicable for Java HTTP adapter as well?

        – Saravanan N

        (0) 

Leave a Reply