nosoap=true, SOAP sender channel problem

[Former Member]

Hi,

We are working on a SOAP sender channel scenario were third party client is sending messages in form of plain XML through SOAP sender channel.

I know the options in SOAP channel check Do Not Use SOAP Envelope option and enter nosoap=true in the URL.

Our problem is we cannot put "&" sign in the SOAP sender channel URL as per client policy.

Can you help me how we can achieve this functionality. 

Thanks

Ahsan

[Former Member]

Good Day,

Any clue how I can resolve this issue.

Thanks.

[markangelo_dihiansan]

Hello,

Can you try escaping your URLs?

http://www.december.com/html/spec/esccodes.html

e.g

http(s)://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c&nosoap=true becomes

http(s)://host:port/XISOAPAdapter/MessageServlet%3Fchannel=p:s:c%26nosoap%3Dtrue

edit: my bad, I thought % is allowed.. I'll get back to you on this.

Hope this helps,

Mark

Message was edited by: Mark Dihiansan

[Former Member]

Hello.

Basically - there is this switch for special characters...
http://support.microsoft.com/kb/308060

however - as you can probably see - they all contain the ampersand char as well.

Can you elaborate more on the reason the client cannot use the ampersand sign?

Regards,

Imanuel Rahamim.

[Former Member]

Hi Imanuel,

Our client is government institution as per their policy the URL must be from & and % signs. It's a policy that we must follow.

Thanks for the post.

[Former Member]

Sorry the URL must be free from & and % signs.

[Former Member]

OK.

How do they send the plain XML?

And why do they have to send it without the SOAP envelope?

Do you know what programming language do they use?

[Former Member]

Actually - you have a bigger problem.

When looking into the genereic WSDL URL that you give them it should look like this:

http://<host name>:<port name>/XISOAPAdapter/MessageServlet?senderParty=<name of the sender party>&senderService=<name of the sender service>&interface=<name of the interface>&receiverParty=<name of the receiver party>&receiverService=<name of the receiver service>&interfaceNamespace=<name of the interface namespace>

As seen in SAP help here:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/3555240bea31c3e10000000a42189d/frameset.htm

So even if you manage to somehow avoid using the &nosoap=true - you still have the rest of the ampersands....

Maybe they have a way of "coding" the replacement for ampersand... but again it depends on how they make the call to the web service.

Sorry, but it seems that I can't help any more than that.

Regards,

Imanuel Rahamim.

[Former Member]

Thanks Imanuel,

For WSDL URLs you can also have a option for : sign like

https://<host name>:<port name>/XISOAPAdapter/MessageServlet?channel:Party:Service:channel

I would like to know if anyone face a similar problem before.

Regards

Ahsan

[Former Member]

They are sending plain XML messages to our SOAP sender adapter URL.

Your next questions are irrelevant. Anyhow thanks for your support.

Regards

Ahsan