SAP Global Delivery
SAP Problems and resolutions Solutions for Cross-Industry Name/ Industry Solution Name (optional)/
DocumentDetails
Name Objective Audience Version Description
Proxy
Configuration for PI 7.3 Java only
Used for reference All Users 1.0 Proxy configuration for PI and Backend SAP system for PI7.3 Java only installation Change Log
Version Date Author Description Approved By
1.0 Aug 16, 2011 Satish Chauhan
For any info on this document please contact:
Name Email ID Contact No
Satish Chauhan [email protected] Extn: 2056
©2008 by SAP AG.
All rights reserved. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
CONTENT
PURPOSE ... 4
PROBLEM ... 5
SITUATIONS APPLICABLE ... 5
RESOLUTION ... 5
STEPSTOBEFOLLOWEDIN PI SYSTEM ... 5
STEPSTOBEFOLLOWEDIN PI SYSTEM ... 10
Purpose
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. In case of PI7.3 dual stack implementation the proxy configuration will remain same as of PI earlier versions.
Problem
PI7.3 is coming with 2 installation options- Java only installation 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.
Situations Applicable
The steps described in this document is only applicable when you have PI7.3 java only installation.
Resolution
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>
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 to register the Program ID.
Steps to be followed in PI 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 a) Create RFC destinations
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 LCRSAPRFCI through SM59 of type T (Start External Program Using TCP/IP)
Note: In dual stack generally we give SAP PI ABAP stack details, same details we used while creating JCo RFC Provider.
- Create RFC destination SAP_PROXY_ESR through SM59 of type G (HTTP Connection to External Serv)
Target Host: PI host name
Long Details: with PIAPPL<SID> user authorizations
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.
b) Configure SLDAPICUST and test connections through TA: SLD Check The user should have SAP_SLD_CONFIGURATOR role.
Generally we use SLD_CL_<SID> user.
a) Test proxy connection with ESR for transaction: SPROXY
b) 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
Path Prefix: /XISOAPAdapter/MessageServlet?ximessage=true Long Details:
Go to Transaction: SXMB_ADM->Integration Engine configuration
Edit->Change Global Configuration Data and enter the RFC destination in Corresponding Integration server for the application system.
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 prefic used for RFC destination is (
/XISOAPAdapter/MessageServlet?ximessage=true)
