RCVR_DETERMINATION.NO_RECEIVER_CASE_BE - encoded URL in WSDL

[naas_duplessis2]

Hi

I have a SOAP to RFC scenario and generated the wsdl using PI 7.11 Integration Builder. The generated URL in the wsdl contains HTML encoded characters because the URL contains a URL e.g..

https://myhost/sap/xi/engine?type=entry&version=3.0&Sender.Service=BC_MY_SENDER&Interface=http%3A%2F....

I have tried to use this URL in soapUI but it does not work and returns a message like the one in this thread's subject.

If you urldecode the url it works in soapUI. One of our clients who will use this web service to call us has to have the url encoded (with %) in it because of the url in a url. Problem is as soon as it hits PI, PI does not perform a urldecode and it fails.

Has anybody else encounter this problem?

Regards

Naas

[markangelo_dihiansan · Accepted solution]

Hello,

You have used the propose URL option in generating the wsdl. Can you instead use the format

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

The proposed URL above will avoid the escaping issues that you have encountered.

Hope this helps,

Mark

[naas_duplessis2 · Accepted solution]

Hi Mark

Will this be the SENDER channel, service interface and party?

Do I need to separate them with a : ? and what if I do not have a party?

https://myhost/XISOAPAdapter/MessageServlet?channel=*:SI_MY_PROCESS_OUTBOUND:BC_MY_SENDER

Naas

Edited by: Naas du Plessis on Apr 7, 2011 11:40 PM

[markangelo_dihiansan · Accepted solution]

Hello,

Will this be the SENDER channel, service interface and party?

They are the party:service(business component/business service):communicationchannel

Do I need to separate them with a : ? and what if I do not have a party?

Yes, you need to separate them with a colon. If you do not have a party it will be like this:

?channel=:service:communicationchannel

There is no need to declare the service interface, the sender agreement will take care of that once you post to that URL

Hope this helps,

Mark

[maciej_jarecki · Accepted solution]

Hi

Thi is old fashonable way of pointing to Soap Adapter but it works.

?channel=:service:communicationchannel

PI propose new one, that why you have to delete the suffix of it.

For detail please go to SAP Note 856597

Kind Regards

MAciej

[naas_duplessis2 · Accepted solution]

Hi

If I use the suggested method I get this message:

Servlet com.sap.aii.adapter.soap.web.MessageServlet (Version $Id: //tc/xpi.adapters/NW711_05_REL/src/_soap_application_web_module/webm/api/com/sap/aii/adapter/soap/web/MessageServlet.java#6 $) bound to /MessageServlet

Classname ModuleProcessor: null

Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean

Lookupname for remoteModuleProcessorLookupName: null

ModuleProcessorClass not instantiated

ModuleProcessorLocal is Instance of $Proxy95

ModuleProcessorRemote not instantiated

I tried the following: (No party) where SI = Service Interface, BC = Buss. Comp and CC = Comm. Channel - all for the Sender.

http://myhost/XISOAPAdapter/MessageServlet?channel=:SI:BC

http://myhost/XISOAPAdapter/MessageServlet?channel=:BC:CC

http://myhost/XISOAPAdapter/MessageServlet?channel=:SI:CC

http://myhost/XISOAPAdapter/MessageServlet?channel=:CC:BC

Then I tried the suggestion in point 1 of the note.

https://dpi.buw.bu.edu/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_TEST_SENDER&interf...

What am I missing?

Naas

[baskar_gopalakrishnan2 · Accepted solution]

There are two ways we can generate WSDL.

First option: what you do now.. Go to Tools and display wsdl

second option is the easiest to do: Go to sender agreement and click display wsdl. Save the wsdl and use it in SOAPUI and test it. YOu dont need to input all the fields for generating wsdl. Hope that helps.