Some Prerequisite for SOAP Communication with XI Protocal in SAP system
After the inception of PI 7.3 we are more and less in a transition phase from Dual Stack to Single stack. Architects now days prefer designs where adapters of Java Stack are only used.
In scenario involving ABAP proxies we have option of using SOAP Adapter with XI3.0 Message Protocol to interact with SAP System. As a PI consultant this seems pretty obvious but there are few prerequisites to attain this communication:
Receiver SOAP Adapter Configuration
Check the Channel Status in RWB:
Check whether the proxy receiver channel is connecting to the SAP system or not?
If we didn’t maintain the HTTP Client in the SAP system we will get the Broken pipe exception in the proxy receiver channel while testing the interface.
Configurations to maintain the HTTP Port in SAP system:
- Check if the XI Service are active in SAP system or not: Tcode: SICF
If the XI services are not active make it as active
- Check the HTTP port is present in SAP system: Tcode: SMICM
If the HTTP port is not maintained here, we should assign a port to the HTTP as shown below.
- Also confirm that MS_LOGON_HTTP protocol is available with the http port: Tcode: SMMS
SAP ECC system should be connected with SLD
and also in sm59 transaction SAPSLDAPI should be configured in the TCP/IP connections with type T.
By checking the above configurations we can easily troubleshoot the proxy issues.