Skip to Content
avatar image
Former Member

SOAP URL issue after migration from PI 7.0 to PO 7.5

Hello Experts,

We are facing an issue in PI migration project from version 7.0 to 7.5. SOAP to XI synchronous scenario from a 3rd party vendor is working fine in PI version 7.0 and not working in PO 7.5 because of URL getting tempered with special characters.

URL maintained at the vendor end- https://xxx.xxx.xxxx.com/XISOAPAdapter/MessageServlet?channel=:TEST_BS:TEST_SOAP_Sender_Validation&version=3.0&Sender.Service=TEST_BS∬erface=urn:com.xxx.xxx.Validation^MI_ValidationRequest_Synch_OB

But when the vendor is triggering the messages, they are getting a HTTP 404 not found at their end and we don’t get any message in SAP PO and no logs in the communication channel, whereas the same works successfully when the vendor is triggering the messages pointing to PI 7.0.

After running the trace using xpi inspector, we could see the incoming URL as below when the vendor is testing https://xxx.xxx.xxxx.com/XISOAPAdapter/MessageServlet%3Fchannel%3D:TEST_BS:TEST_SOAP_Sender_Validation%26version%3D3.0%26Sender.Service%3DTEST_BS%26Interface%3Durn%3Acom.xxx.xxx.Validation%5EMI_ValidationRequest_Synch_OB

The vendor is getting a HTTP 404 not found error because of the ? getting converted to %3F which is happening in SAP PO and not in SAP PI.

Some remarks and observations:

1) If in the modified URL, the %3F is changed to ? and ran in the browser and credentials are provided, it opens the message servlet ok page otherwise shows as 404 Not Found.

2) We have similar interfaces with 2 other vendors which works fine after migration and after looking at the logs in xpi inspector, the ? after message servlet doesnt get tempered or we dont see any special characters in the URL

3)This interface works fine, when we trigger using soap UI. But when the messages are coming from the vendor, it is not able to find the resource path and we dont get any logs at PO level.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Apr 06 at 03:32 AM

    Hi Lipsita,

    A alternate option could be to change the URL to :party:business component:channel name as

    http:// <host name> : <port name>/XISOAPAdapter/MessageServlet?channel=<party name> : <service name> : <channel name>


    This needs the sending system to change the URL but this won't have any of the issues you face and more importantly this URL continues to work even though it was a older style of URL.

    Regards

    Bhavesh

    Add comment
    10|10000 characters needed characters exceeded