How to improve the performance of SAP standard implementations using SAP PI AAE

[Former Member]

  *How to improve the performance of SAP standard implementations using SAP PI AAE.* With this weblog I want to showcase, how to improve the performance of SAP standard implementations using SAP PI AAE stands for Advance Adapter Engine. As we know for standard implementation of ESOA interfaces for any Application/Module, we should go with configuration scenario by importing the process integration scenarios that will be available in Standard ESR Content. This can be done by any functional consultants like SRM, SCM if they know basic wizard based configurations in PI server for application related implementation. I don't think, all functional developers are aware of AAE in SAP PI, with which we can increase performance of interfaces. Technically we know how to use AAE to improve the performance for any custom built applications like client specific implementation Ex: File to JMS. Because such implementation projects require PI consultants, and they know how to utilize the latest features available in PI custom implementations. So let me explain with ERP and SRM as example, to improve the performance of SAP standard implementations using SAP PI AAE targeting functional consultants, and also PI consultants who didn't try implementing AAE in standard implementations. We have some articles/blogs available in SDN to explain about the functionality of AAE, and how to use AAE. Please find some below: *{code:html}SAP NetWeaver Process Integration 7.1: Advanced Adapter Engine{code}*0.1. *{code:html}How to Set Up the Communication between ABAP Backend and SOAP Adapter using XI Protocol{code}*0.1. *Local Processing in the Advanced Adapter Engine using PI 7.1 (Local Processing in the Advanced Adapter Engine using PI 7.1)* Before continuing to the topic discussion let us see traditional configuration. In the example standard interface exeuctes from SAP ERP 6.0 EHP 4 to SAP SRM 7.0 communicating through SAP PI EHP1. To implement standard ESOA based interface we need to import *ESR-Content* in to ESR from Service Market Place, and identify the Process Integration Scenarios. Once we identify the relevant Process Integration Scenario in ESR, we will move to Integration Directory and create a Configuration Scenario by using identified Process Integration Scenario. By utilizing *Model Configurator* feature in Integration Directory, we create configuration objects by clicking next, next. But if we understand the runtime flow, then we see performance is hindered with these objects. Normally most of the standard implementation scenarios go without any mappings, not many routing techniques, and ccBPM. All the scenarios executed using this traditional way will goes through Integration engine of PI for processing. Someone can say *+Proxy is adapter less+* so this should work much faster than other features. Yes Proxy is adapter less, but still you need to configure XI adapter at receiver communication channel. And also message processing will happen through tedious pipeline steps in Integration Engine  which is time taking process. When there is mapping/no mapping, no routing and no ccBPM used (+take variable combination+) why not we use AAE which will skip pipeline processing in Integration Engine. Now we will see, how we can utilize AAE feature of PI 7.1 for standard implementation. To utilize the feature of AAE we need to configure new ICO object as explained in the Article, and little configuration in backend application servers ( ERP and SRM).  Let us see how to configure the objects.   *Configuration steps for standard implementation ERP - PI - SRM* Identify the Process Integration Scenario in relevant SWCV. Let me take SE_SOURCING_ENHANCEMENT process integration scenario as example in imported ESR-Content *SRM SERVER IC 7.0* To implement this Process Integration Scenario we need to import relevant ESR-Content *SAP APPL 6.04* for ERP end, and *SAP SRM SERVER 7.0* end For this interface there are no changes to be done for Message Mapping or Operation Mapping in ESR. So we move to Configuration in Integration Directory: Here we can skip *Model Configurator,* as this wizard generates objects required in traditional implementation. We can manually configure objects as the Model Configurator will not create objects relevant for AAE implementation. First we import/assign the business systems relevant for SAP ERP and SAP SRM to our configuration scenario. Then we create communication channels both Sender and Receiver side holding adapter type as SOAP, and Message Protocol as XI 3.0. Here comes the first difference, we create sender communication channel of adapter type SOAP but XI 3.0 as Message Protocol. So any message related to this interface should come through this sender communication channel. But to send Proxy message from ERP to SAP PI SOAP adapter we need to configure three steps in Sender Backend System, in our case it is ERP. Let us discuss that part once we finish creation of ID objects. Second difference is to create a receiver communication channel of type SOAP adapter and select XI 3.0 as message protocol. We need to provide Target URL as Integration Engine URL of SRM server which will be http://hostname:portnumber/sap/xi/engine?type=entry (http://hostname:portnumber/sap/xi/engine?type=entry) here hostname and port number are of SRM server. Then comes the Third object which is ICO - Integrated Configuration Object, this replaces all our traditional Receiver Determination, Interface Determination, and Receiver Agreement. Here we see how to create ICO object. In the first tab *Inbound Processing* select the Sender Communication Channel which we have created in earlier step. In the next tab *Receiver*, select the Receiver SRM Business System. In the next tab *Receiver Interfaces* provide the receiver interface details, and operation mapping if anything is required. In the next tab *Outbound Processing* provide the receiver SOAP communication channel that you have created in the earlier step. Save and activate all the objects in Integration Directory. Now will move to ABAP stack of ERP to create few configurations: *Step 1:* Create *RFC destination* of type *G*. This RFC destination is to point to SOAP adapter of SAP PI, earlier we used to create a type H connection that was pointing to Integration Engine of PI. *Step 2*. Next execute TCODE *SXMSIF* and provide *Sender/ReceiverID*: Any unique name corresponding to the Interface, then provide *Sender Service, Interface name *and Name Space.

*Step 3*. Execute TCODE: *SXMB_ADMIN* and click *Integration Engine Configuration* and create a new entry as follows: Select the category as *RUNTIME*, Parameters as *IS-URL*, SubParameter as *Sender/ReceiverID* created in previous step and current value as dest:// which will be *dest://PI_ADVANCE_ADAPTER_ENGINE*. Configuration should look like this.