cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Sender Problem

Former Member
0 Kudos

Hi Experts,

My scenario is synchronous Webservice to RFC .

The URL Fromal which I given while defining the Webservice is

*http://host:port /XISOAPAdapter/MessageServlet?channel=:s:c*

While I am trying this url in Internet expoler I am getting the

Message Servlet is in Status OK

Status information:

Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/xi/NW04S_21_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $) bound to /MessageServlet

Classname ModuleProcessor: null

Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean

Lookupname for remoteModuleProcessorLookupName: null

ModuleProcessorClass not instantiated

ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0

ModuleProcessorRemote not instantiated

If I give the system proposal URL while defining WS in ID , that wsdl is getting correct response when I tested from SOAPUI.

But the user is not able to send request with that wsdl and getting the error as

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Receiver Identification

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="RCVR_DETERMINATION">MESSAGE_INCOMPLETE</SAP:Code>

<SAP:P1>Sender</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Message is incomplete. No Sender found</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Pls let me know what went wrong. Thanks

Vankadoath

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi Vankadoath,

Even i am facing the same issue!

Did u find any solution??

Regards

Niraj

Former Member
0 Kudos


Hi Niraj,

For which version of PI are you getting this error?

Just confirm your WSDL. It may contain two

***************************

<wsdl:service name="XYZ">

      <wsdl:port name="HTTP_Port" binding="p1XYZs">

         <soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="End\point" />

      </wsdl:port>

***************************

There could be another port of HTTPs type. By default, soap UI will take HTTP port. try to change the url to HTTPS and check. do remember to update the HTTP port number also in URL

Regards,

Gavaksh

srikanth_srinivasan3
Active Participant
0 Kudos

Following could be revisited:

Check you SOAP envelope parameters in SOAP sender channel;

Check your logon data;

Request the input message sent by the user or try to extract the message from 'Channel Monitoring';

Check for the correct target namespace in the WSDL provided by you to the user;

-

Srikanth Srinivasan

Former Member
0 Kudos

Hi Vankadoath,

Maybe the Sender Agreement and Receiver determination in your scenario configuration do not match, check again.

Thanks,

Thien

Former Member
0 Kudos

Thanks for your reply Pratik,

If I use the system proposal url its working fine from SAOPUI. I changed the URL In this format

http://host:port /XISOAPAdapter/MessageServlet?channel=:s:c and testing in the SOAPUI

I am getting the error as

401 Unauthorized in SOAPUI

and i didn't see any messages in MONI.

I am sure I done every thing right in IR and ID level.

and pls let me know is it mandatory To publish WSDL generated from XI to UDDI in Visual administrator? we have not defined any thing in Visual administrator. is it the problem? pls let me where i did wrong?

Thanks!

Vankadoath

baskar_gopalakrishnan2
Active Contributor
0 Kudos

> 401 Unauthorized in SOAPUI

You need to enter user/password something like PIUSER login information

> Publish WSDL in UDDI is not mandatory... YOU create WSDL and give it to the third party client to consume your webservice.

Former Member
0 Kudos

you are right bhaskar, i given user credentials so its working and getting response.

i given the wsdl file and the url to the user.

they are trying to open the WS by using this url in Internet Explorer.

url :http://host:port /XISOAPAdapter/MessageServlet?channel=:s:c

after giving the user name and password, the wsdl is not opening. its giving the status as

Message Servlet is in Status OK

Status information:

Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/xi/NW04S_21_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $) bound to /MessageServlet

Classname ModuleProcessor: null

Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean

Lookupname for remoteModuleProcessorLookupName: null

ModuleProcessorClass not instantiated

ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0

ModuleProcessorRemote not instantiated

Do i need to place the wsdl file some where in the visual admin?

Pls let me know what is wrong? Thankls!

baskar_gopalakrishnan2
Active Contributor
0 Kudos

> Do i need to place the wsdl file some where in the visual admin?

NO.

To test web service, Your client should use soap client tool like soapUI or soapsonar or XMLSPY.

Advice them to load the wsdl in the soap client tool to test it. Not via Browser.

Former Member
0 Kudos

Hi Baskar,

Hope you are fine. I am also facing a problem in my Soap TO Rfc Scenario. WHen i test my WSDL file in XML spy, it works perfect. I can see both request and response message. But when i try URL of WSDL file in internet Explorer, after putting PI username and password, it gives following message.

Message Servlet is in Status OK

Status information:

Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/xi/NW04S_14_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $) bound to /MessageServlet

Classname ModuleProcessor: null

Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean

Lookupname for remoteModuleProcessorLookupName: null

ModuleProcessorClass not instantiated

ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0

ModuleProcessorRemote not instantiated

What could be the problem? Why the URL is not working in IE,  even WSDL file working perfect in XML spy.

Thanks

Regards

Imran

Former Member
0 Kudos

Hi,

As mentioned in the previous replies, you need to use the same URL which you mentioned in your inital query and not the proposed one. I am not sure what you meant by triggering this URL through IE. If this URL was just called through browser, obvious output is what you got because there is no SOAP Request being sent through it but if you have posted it through some SOAP UI client then please check SOAP Sender channel monitoring whether the message is processed with green status or not. If not please check the error. If it is then check SXMB_MONI for any errors and post it here.

Best Regards,

Pratik

Former Member
0 Kudos

Hi,

While creating WSDL in ID please use URL format "http://host:port /XISOAPAdapter/MessageServlet?channel=:s:c" only. Donot use propsed one. Test using the above URL format only from SOAPUI. I don't think you will have any problem on this.

Regards,

Nayan

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

The URL http://host:port/XISOAPAdapter/MessageServlet?channel=:s:c is the correct URL for the WSDL using SOAP. Although I have not tried using the suggested URL from the display WSDL option, this could also work. Could you tell us what error you are getting when trying to execute from SOAP UI using XISOAPAdapter URL?

Regards,

Mark

Edited by: Mark Dihiansan on Jan 20, 2011 8:16 AM