Skip to Content
author's profile photo Former Member
Former Member

SOAP Adapter Error

Hi folks,

I am working on a scenario where an AXIS client sends SOAP messages to XI. I have configured the SOAP Adapter with the following config settings:

classname=com.sap.aii.messaging.adapter.ModuleBubble

Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl

  1. Part 1 (FromWS) : WS clients to XMB server ######

  1. The target URL of XMB broker, to which the adapter sends XMB messages.

XMB.TargetURL=http://msssapxinw:8000/sap/xi/engine?type=entry

  1. The port and path where the adapter waits for web service messages from clients.

XMBWS.WSPort=4444

XMBWS.WSPath=/soap/start

XMB.User=sapuser

XMB.Password=******

XMB.Client=020

  1. The following XMB attributes are used to fill default XMB messages.

XMB.SenderBusinessSystem=XMBWebServiceAdapterSender

XMB.SenderInterfaceNamespace=http://sap.com/xi/xidemo

XMB.SenderInterfaceName=XMBWebServiceAdapterSenderIF

XMB.ReceiverBusinessSystem=XMBWebServiceAdapterReceiver

XMB.QualityOfService=BE

-


The SOAP adapter is up and running.

This is the url that the integration engine shows:

http://msssapxinw:8000/sap/xi/engine?type=entry

I am using this exact same url to create an endpoint in my AXIS client.

When I send a SOAP message I get the following exception :

-


Error during parsing of SOAP header

org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)

org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:169)

org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:1015)

org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)

org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)

org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

javax.xml.parsers.SAXParser.parse(Unknown Source)

org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:242)

org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)

org.apache.axis.Message.getSOAPEnvelope(Message.java:376)

org.apache.axis.client.Call.invokeEngine(Call.java:2583)

org.apache.axis.client.Call.invoke(Call.java:2553)

org.apache.axis.client.Call.invoke(Call.java:2248)

org.apache.axis.client.Call.invoke(Call.java:2171)

org.apache.axis.client.Call.invoke(Call.java:1691)

Please help. Thanks in advance,

Shailesh

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Feb 03, 2005 at 11:36 AM

    Hi,

    The url you should give your client, is of the adapter engine:

    http://<host>:4444/soap/start

    where <host> is the host of your adapter engine (same as integration server if you hadn't installed a stand-alone one), 4444 is the port (as defined in XMBWS.WSPort=4444, and the path from XMBWS.WSPath=/soap/start)

    The TargetURL is used for communication of the integration server and the adapter engine.

    Hope this helps.

    Avihai

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      I'm not familiar with the AXIS client, so I can't help you much about its settings.

      However, I suggest you test the WS in the Test Environment, to make sure that it works ok, then try to figure out the settings of your specific client.

      Best of Luck,

      Avihai

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.