on 03-10-2016 12:17 PM
Hi Experts ,
We are connecting a single stack PI system (Customer) to another PI System(Bank).We are using SOAP adapter with XI3.0 to send IDOC messages successfully from Customer to Bank. But when Bank sent Text messages using SOAP adpater with XI3.0 we are getting the below Bubble Exception.
Transmitting the message to endpoint <local> using connection HTTP_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null
For this reason as per the link PI 7.31 Single Stack SOAP: call failed: com.sap... | SCN we have tried using SOAP1.1 instead of XI3.0 to connect from BANK to Customer .But since the scenario is a pass through / bypass scenario sending text files , It is failing as the SOAP1.1 is expecting XML files if am not wrong.
Please let us know the reason for the bubble exception.Is it any authentication issue ??.Kindly note that we are using PISUPER as logon user to send the Text files from BANK PI to Customer PI.
Please help.Thanks in Advance .
Regards,
Tibin Joseph
Hi Tibin,
SOAP with XI 3.0 is usually used when you are trying to connect to backed ABAP system with proxy , why dont you go with SOAP 1.1 as protocol ?
Br,
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manoj.
As per the blog . We can use the url http(s)://host:port/XISOAPAdapter/MessageServlet?ximessage=true to send messages using SOAP XI.30 to Java only stack and we have successfully send XML files also .
But while using the same url in Customer side to send some text files to us , they are getting bubble exception.
I have tried using SOAP 1.1 using both below links , but unable to send the messages because the scenario is a pass through scenario transferring TEXT files , but it supports for XML files.
1. http://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c
Error Details
Please help.
Tibin
Hi Tiben,
I just want to give you the reason why we need to create virtual receiver in ICO.
When you use SOAP with XI 3.0 in the URL we are not going to send any information about sender business system, interface and namespace, it will read from soap header like below.
ICO must be look like below.
So in your target PI system ICO must match above values then only system identifying the correct ICO for this message, initially you did not enter the receiver business system in ICO (using virtual receiver) that is why you got 500 error, If you want to see what is actual error you can see it in Further Links->Log Viewer. it probably complaining about CPA object not found.
Regards,
Praveen.
Hi Tibin,
Agreeing with Manoj first of all choose SOAP channel with HTTP protocol to connect to next PI system.
We choose XI3.0 to connect to abap backend system, and we can connect PI to PI with soap (http).
Regards,
Vikas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tibin,
The sap/xi/engine URL is used for dual stack PI system.
The XISOAPAdapter/MessageServlet is used for single stack PI system.
You want to connect from dual stack to PI single stack then in dual stack receiver channel input the 2nd url with XI3.0 protocol.
500 error is as exactly manoj suggested. Infact all the responses by Manoj are worthy here. Please check header mapping as also suggested in the blog which you have referred.
Regards,
Vikas
Hello Tibin,
IDOC with Soap adapter??
Requirement is bit confusing.
as Manoj suggested if its webservice call change the protocol to SOAP 1.1
Anyways if you can provide us the more details on the scenario can you help out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.