Sender SOAP adapter - WSDL not working

[former_member183906]

Hi,

I am doing Sender SOAP and receiver RFC adapter for SOAP-BAPI scenario.The WSDL is generated after IR and ID config.

URL

http://host:port/XISOAPAdapter/MessageServlet?Sender.Service=BS_VCT_Sender&Interface=urn:abb-com:vct...

But by testing by XML spy, m getting error -

com.sap.aii.af.service.cpa.CPAException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=null;AN=null;ANS=null;

Can you please let me know wats error in it. I have testing mappings and all is OK. How to test also pls tell me.

When opening URL in IE, its giving -Message Servlet is in Status OK.

Pls answer.

Thanks

[Former Member · Accepted solution]

Hi,

The below values are not able to identify.

the P/S/A i.e. Party, Service, Action values are as below,

FP = From Party

TP = To Party

FS = From Service

TS = To Service

AN= Action Name & ANS= Action namespace;

please can you verify if in case the interface provided in url is able to find correct Recievers Services and message interfaces etc. May be Test configuration option will help you.

Thanks

Swarup

[former_member183906 · Accepted solution]

Hi all

thanks for replies.

i am testing by xml spy 2009 sp1.

finally i am using this URLin SAP PI 7.0 :

*http://host:port/XISOAPAdapter/MessageServlet?senderService=BS_VCT_Sender&interface=USER_MI&... &receiverService=Sys_RD2_520&interfaceNamespace=urn:abb-com:vct:sap:ven*

But problem is i am not allowed to save WSDL file with "&" only , when i am saving file like -> senderService=&interface then its giving WSDL file not well formed. I must use "&amp" in stead of "&" to make it well formed.

Thus its not identifying -

Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=BS_VCT_Sender;TS=null;AN=null;ANS=null;

Any way that & can be avoided in WSDL.

[former_member187339 · Accepted solution]

Hi Vijayant,

Use this url in wwsdl

http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_VCT_Sender:channel

just replace channel with your sender communication channel (and leave the : as such)

no need to specify interface and namespace etc.

Regards

Suraj

Edited by: S.R.Suraj on Sep 10, 2009 3:15 AM

[former_member183906 · Accepted solution]

Its giving error

com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:

at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)

at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:910)

at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:215)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

when i tried Suraj solution -

http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_VCT_Sender:CC_VCT_Sender

please provide solution as i mentioned in just above.

How to eliminate &amp and use & only for WSDL

[former_member187339 · Accepted solution]

Hi,

>>Its giving error

Is this error in XMLSPY? Have you check SXMB_MONI to see whether the message has reached XI

Have you checked the Communication channel monitoring for channel CC_VCT_Sender? IS it having QoS as Best Effort?

I think this message has reached XI and is failing in message mapping.

Regards

Suraj

[Former Member · Accepted solution]

Hi,

Have you regenerated the wsdl with the new url http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_VCT_Sender:CC_VCT_Sender.

If not please try to create a new wsdl file with this url and try to send the SOAP request again.

Thanks,

Tiny

[Former Member · Accepted solution]

Hey,

if you change the URL then need to regenerate the WSDL where soapAdress will have the target URL ..

based on which a call will be made to destination from webservice client(XML SPY in your case)

You dont need to use the URL explicitly anywhere

just import the WSDL in your XMLSPY and generate request and provide credentials ..then it will make a call automatically..

if everytinhg is fine...

Gud luck

Rajesh

[former_member187339]

Hi,

First do a complete cache refresh and then try again.

Also check whether the URL you have mentioned in wsdl is of format

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

Regards

Suraj

[former_member183906]

1. I have given XI dev uid and pwd while testing with xml spy.

2.in xml spy wsdl is valid.

3.done cache refresh also -full.

4.wsdl is in this format only

http://host:port/XISOAPAdapter/MessageServlet?version=3.0&channel=:BS_VCT_Sender:CC_VCT_Sender&a...

pls suggest other options..

[Former Member]

With the above URL it will try to send the request directly to Integraiton engine,instead of that try first sending using adapter

URL fomrat should be

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

generate the WSLD using above format and try if there is no error you can try for sending to integration engine

Rajesh

[Former Member]

Hi Jha,

Your wsdl seems to be wrong. You have given two wsdls in two replies. If you are using xi 3.0 then try to use the wsdl as suggested by me in this thread (my first reply).

If that doesnot work then see my second reply. Even though you dont use few parameters use them in the wsdl without any values. Make sure you have correct, because I see in your first thread you have Sender.Service, instead it should be senderService (S caps in Service and s small in Sender and there is no period so please check that).

Regards,

---Satish

[former_member187339]

Hi,

Both the URLs are different

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

Send request through the Communication channel (Sender). This is the J2ee port

http://host:port/XISOAPAdapter/MessageServlet?version=3.0&channel=:BS_VCT_Sender:CC_VCT_Sender&Inter...

sends to IE. this is the abap port.

Regards

Suraj

[Former Member]

Did you provided the required credentails during testing with XML spy...

Rajesh