The purpose of this document to highlight new changes and steps required to configure proxy communication between SAP PI 7.3 (Java only installation) and backend SAP systems like ECC, CRM etc.
PI7.3 is coming with 2 installation options- Java only installation (AEX) and Dual stack (ABAP + Java) installation. In Java only installation i.e AEX we do not have ABAP stack on PI system hence the configuration changes are required in PI as well as Backend systems to enable proxy communication between systems.
In case of PI7.3 dual stack implementation the proxy configuration will remain same as of PI earlier versions.
Steps to be followed in PI system
1. Go to PI NWA using Http://<Hostname>:port/nwa
2. Go to Configuration->JCo RFC Provider
3. Create 2 RFC JCO providers
- SAPSLDAPI_<PI SID>
- LCRSAPRFC_<PI SID>
Create SAPSLDAPI_PEX:
Note the Application Server host and Gateway Service.
Here Application system is used to register the program id SAPSLDAPI_PEX.
Reason: In Dual stack we generally give PI ABAP stack details, however for Java only installation we need any ABAP stack details(in landscape) to register the Program ID. I have used for ECC application system that PI is exchanging data.
Perform the similar steps for LCRSAPRFC_PEX
Steps to be followed in Application system
a) Create 3 RFC destinations (SM59)
- SAPSLDAPI (Application system to SLD connection)
- LCRSAPRFC (Application system to Exchange profile connection)
- SAP_PROXY_ESR (Application system to ESR connection)
b) Configure SLDAPICUST and test connections through TA: SLD Check
c) Test SPROXY transaction
d) Configure SXMB_ADM transaction for runtime proxy message exchange
Create RFC destinations
- Create RFC destination SAPSLDAPI through SM59 of type T (Start External Program Using TCP/IP)
The gateway Host and service are blank as in PI NWA (JCo RFC) we have registered the program ID in same application system gateway.
Note: In dual stack generally we give SAP PI ABAP stack details, same details we used while creating JCo RFC Provider.
- Create RFC destination LCRSAPRFC through SM59 of type T (Start External Program Using TCP/IP) similar to RFC destination SAPSLDAPI and use program ID as LCRSAPRFC_<PI SID>
Note : In case we have more application system connected to PI using SPROXY than we need to create above RFC destinations in another application system and will pass Gateway host and Gateway service as provided in JCo RFC provider.
- Test both RFC destinations.
- Create RFC destination SAP_PROXY_ESR through SM59 of type G (HTTP Connection to External Serv)
Target Host: PI host name
Port: Http port (50XX00) where X X- System number
Long Details: with PIAPPL<SID> user authorizations
b) Configure SLDAPICUST and test connections through TA: SLDCheck
The user should have SAP_SLD_CONFIGURATOR role.
Generally we use SLD_CL_<SID> user
c) Test proxy connection with ESR for transaction: SPROXY
Note: Here all the config were working but somehow I am not getting exchange profile values using RFC destination LCRSAPRFC. Hence I had to create RFC destination SAP_PROXY_ESR to make transaction SPROXY work.
d) Configure SXMB_ADM transaction for runtime proxy message exchange
Create RFC destination <any name> of type G (HTTP Connections to External Server)
Target Host: PI host name
Port: Http port (50XX00) where XX- System number
Path Prefix: /XISOAPAdapter/MessageServlet?ximessage=true
Log on Details:
Go to Transaction: SXMB_ADM->Integration Engine configuration
Note: For dual stack we generally give ABAP stack RFC destination, since we want to use ICO object we need to connection using SOAP adapter hence the path prefix used for RFC destination is ( /XISOAPAdapter/MessageServlet?ximessage=true)
