& character in soap URL

[former_member190284]

Hi Experts,

I have a scenerio in which the flow is

WS..>SAP PI...>RFC.

The interface is running successfully in SOAPUI

But the problem is when the 3rd party is trying to consume the same WS it's giving  an error:

forbidden access- 403

The 3rd party is saying that the special character as in  "&" is getting converted to "&lt"..and thereby they are unable to hit the WS.

Can i convert the URL ..so that it becomes without special character.

http://xyz:abc/XISOAPAdapter/MessageServlet?senderParty=&senderService=bc_ginger_sender&receiverPart...

[Former Member]

Hello Nunu,

If the 3rd party is getting "&lt" while using "&" then request them to use "&" instead.

You can also use the below url as well as has been previously suggested by .

If these does not work then you should check for User ID or password authentication issue. Or you might also check for firewall issues if there is one being maintained at yours or 3rd party's end.

Thank,

Satanik

[pvishnuvardan_reddy]

Hi Nunu,

The error code 403 specifies Authentication issue. Can you check the PI System user access/roles/Password that you have given to the WS for posting the data is having any issue or not.

Regards

Vishnu

[markangelo_dihiansan]

Hi,

The 3rd party is saying that the special character as in  "&" is getting converted to "&lt"

Well I think this is a problem on their end, &lt is an escape for the less than sign < . Ask them why are they escaping an ampersand to a less than, try using %26 instead of & or use the old way of sending it to PI as suggested by above.

Here is the new URL using %26:

http://host:port/XISOAPAdapter/MessageServlet?senderParty=%26senderService=TestService....

Take note that maybe you need to escape = to %3D as well, so it comes down to:

http://host:port/XISOAPAdapter/MessageServlet?senderParty%3D%26senderService%3DTestService....

Regards,

Mark

[iaki_vila]

Hi nunu,

Why don't try with the other URL?

http://xyz:abc/XISOAPAdapter/MessageServlet?channel=:bc_ginger_sender:<channel name>

You will need to provide sender communication channel as well.

Regards.

[former_member183816]

The 3rd party is saying that the special character as in  "&" is getting converted to "&lt"..and thereby they are unable to hit the WS.

First of all, that is not the reason, they are getting 403 forbidden.

HTTP 403 - Wikipedia, the free encyclopedia

A 403 response generally indicates one of two conditions:

• Authentication was provided, but the authenticated user is not permitted to perform the requested operation.
• The operation is forbidden to all users. For example, requests for a directory listing return code 403 when directory listing has been disabled.

Can i convert the URL ..so that it becomes without special character.

You need to install some third party tool to acheive it.

[former_member190284]

Hi Ambuj

can you pls tell me which is this 3rd party tool?

[azharshaikh]

Hi Nunu,

1.Have to tried testing the WSDL file locally in your SOAP UI tool (the wsdl file that u shared with Client)

2. Test and check if this working locally

3. What authentication mechanism is being used? Is the client having valid PI User to post data into PI?

Regards,

Azhar