Proxy to file scenario using AAE - with full configuration

By Sabyasachi Masanta, Tata Consultancy Services

Introduction  

When we are migrating PI interfaces from older version (up to 7.10) to new PI version (i.e. PI 7.11 and above) then we need to configure SAP backend system in such a way so that we can process existing proxy interfaces using AE and new interfaces suing AAE. In this type of situation we can configure the backend system for default interfaces and for specific interfaces. For default interfaces we were using AE and for the new Proxy to File (or File to Proxy) scenarios we will use AAE. This document is describing how to configure proxy scenarios using AAE with AE.  

Business Requirements  

We had a requirement to implement proxy to file scenario using AAE in PI 7.30. In this case we had a problem. Our old box was PI 7.10. In that old box we configured all the proxy to file scenario using AE. Now when all the old scenarios moved to PI 7.30, we had to configure the backend system for both the AE and AAE. For all old proxy to file scenarios and vice versa we could not change the any configuration (business requirement) so we configured new interfaces using AAE for all the new proxy scenarios.  

Methodology  

In this document we are using a proxy to file scenario. We will configure the entire proxy configuration in the backend system (ECC). Then we will configure the ICO in the PI system.  

Configuration in the ECC system  

1.     Go to transaction SM59 and create three RFC Destinations. SAPSLDAPI (for SLD Connection) of type “T”, SAP_PROXY_ESR (to get ESR object details in SPROXY) of type “G” with Path Prefix “/rep” and AAE_DXB (here DXB is the SID) of type “G” with Path Prefix “/XISOAPAdapter/MessageServlet?ximessage=true”. RFC AAE_DXB will be used for AAE connection. This RFC (AAE_DXB) will be updated in SXMB_ADM. Use PIAPPLUSER in this RFC (AAE_DXB). This is very important. PIAPPLUSER must have role SAP_XI_APPL_SERV_USER in both PI and ECC system. You can check the Program ID name from NWA.  

JCO RFC Provider (from NWA)

2.     Then configure the SLDAPICUST.  

3.     Run the SLDCHECK transaction. Summary should be “Connection to SLD works correctly”.  

 

4.     Go to transaction SXMSIF (or from transaction SXMB_ADM to “Configure Sender/Receiver ID”). Go to change mode and click on “New Entries”.  

Click here to continue...

 

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image