SOAP with XI 3.0 message protocol

Hello Everybody,

In this document I would like to explain how to configure and test SOAP adapter with XI 3.0 message protocol to process proxy messages.

Many have already discussed this on SDN. I would like make this simpler for newbies in the form of a simple POC (Proxy – Proxy).

ESR setup:

Source Data Type:

Target Data Type:

Source Message Type:

Target Message Type:

Outbound Service Interface:

Inbound Service Interface:

Message Mapping:

Operation Mapping:

Integration Builder Setup:

Sender SOAP communication Channel:

Module Name: sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

Parameter Name: generateSysAck                 Parameter Value: true

Parameter Name: ignoreDuplicate                 Parameter Value: true

Receiver SOAP communication Channel:

Target URL: “http://<TargetHost>:<port>/sap/xi/engine?type=entry”

Integrated Configuration:

Configurations in ECC system:

Execute SLDCHECK T-code and check if it takes you to PI SLD webpage. If not request basis team to configure this.

Execute SPROXY T-Code in ECC system. You should be able to see ESR content there. Else, request basis team to maintain connections.

Navigate to the outbound service interface in SPROXY T-Code.

Share this service interface details with an Abaper and request him/her to generate and activate the proxy.

Navigate to the inbound service interface.

Share this service interface details with an Abaper and request him/her to generate and activate the proxy.

Execute SM59 in ECC system and create Type G RFC destination to PI system.

     Target Host: PI host

     Service No: PI port number

     Path Prefix: /XISOAPAdapter/MessageServlet?ximessage=true

Execute T-Code SM59 in ECC system and create Type H destination to PI system.

     Target Host: PI host

     Service No: PI port number

     Path Prefix: /sap/xi/engine?type=entry

Execute T-Code SXMSIF in ABAP system

Create a new entry for outbound service interface.

Execute T-Code SXMB_ADM in ECC system.

Execute Integration Engine Configuration –> Edit –> Change Selected Config Data –> Role of Business System –> Select “Application System” –> Corresponding Integ. Server –> dest://<Type H RFC destination created previously>

Execute Integration Engine Configuration –> Change Configuration (F9) –> Ctrl+F1 –> New Entry (F5) –> Category: RUNTIME –> Parameters: CENTRAL_SYSTEM –> Subparameter: SLD –> Current Value: is.<PI sys no>.<PI host> –> Save

Execute Integration Engine Configuration –> Change Configuration (F9) –> Ctrl+F1 –> New Entry (F5) –> Category: RUNTIME –> Parameters: ENGINE_TYPE –> Current Value: LOC –> Save

Execute Integration Engine Configuration –> Change Configuration (F9) –> Ctrl+F1 –> New Entry (F5) –> Category: RUNTIME –> Parameters: IS_URL –> Current Value: dest://<Type H RFC Destination crated in SM59> –> Save

Execute Integration Engine Configuration –> Change Configuration (F9) –> Ctrl+F1 –> New Entry (F5) –> Category: RUNTIME –> Parameters: IS_URL –> Subparameter : Sender ID created in SXMSIF –> Current Value: dest://<Type G RFC Destination crated in SM59> –> Save

Execute T-Code SMICM –> Shift+1 or click on Services –> Configure permanent HTTP Service Port (this port number has to be used to configure target url in receiver soap channel)

Reference: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/5bdafa97817511e10000000a42189b/content.htm

Execute SICF T-Code in ECC system and execute.

Expand default_host –> sap –> xi and right click on engine_test (XI Test Handler) and select Test Service.

This will open “http://<ECC Host>:<ECC Port>/sap/xi/engine_test?sap-client=<ECC Client>” in the browser. It should ask for user credentials. Provide ECC credentials. You should get below response. If not, request basis team to fix this.

Testing:

Execute SPROXY T-Code in ECC system and navigate to outbound service interface –> Right Click –> Display Proxy –> Test (F8) –> Execute (F8) –> XML Editor (Ctrl+F2) –> Input Values

Execute (F8) –> Trigger Commit (if required).

Execute SXI_MONITOR T-Code in ECC system and verify if proxy is successfully sent to PI system.

Verify in PI Java Stack monitoring if message is received and is delivered to target ECC system.

Execute SXI_MONITORING T-Code in ECC system and verify if message is successfully received into it.