Error in AXIS SOAP Adapter

[Former Member]

Hi Experts,

Cuurently i am working on Synchronous scenario.

My scenario is ABAP Client Proxy> PI>AXIS SOAP ADAPTER(Webservice).

My client requirement is to use UsernameToken security with PasswordDigest.

I have deployed all the relevant .jar files and add the modules related to usernameToken security as per *SAP Note 1039369 FAQ XI Axis Adapter* in Receiver SOAP adapter.

Now when i am pushing the data from R/3 to PI, data is successfully coming to PI however when the data is going outside PI through Receiver AXIS SOAP Adapter in RWB is showing

*The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System*

*The message status set to DLVD*.

Moreover when i am checking the message through SXMB_MONI i cant see the chequred flag for Request message and for response message its giving the following

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

- <!-- Request Message Mapping

-->

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

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="SOAP">FAULT</SAP:Code>

<SAP:P1>http://schemas.xmlsoap.org/soap/envelope/</SAP:P1>

<SAP:P2>Server.generalException</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>WSDoAllReceiver: security processing failed (actions number mismatch)</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

and when i am cheking the trace of Respose message (request for message mapping ) its giving the

<Trace level="1" type="T">Message has no payload</Trace>

<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_UrlResponse_To_CourseAccessUrlResponse_</Trace>

<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected! at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151).....

Currently SSL is not installed in my PI server.For temperory i am using HTTP instead of HTTPS.

Please provide your valuable inputs on this.

Regards

Anku chopra

Edited by: AnkuChopra on Aug 28, 2009 1:59 PM

[Former Member]

Answered

[former_member184944]

Hello I am getting a similar error in my asynchronous axis receiver adapter.

Axis: error in invocation: WSDoAllSender: cannot get SOAP envlope from messageorg.xml.sax.SAXException: Fatal Error: URI=null Line=21904: Character reference "&#xD849" is an invalid XML character.

Would you have any idea how to resolve this issue?

Thanks & Regards,

Anumeha

[Former Member]

What about on the inbound Message tab?

Rod

[Former Member]

No Payload option in Inbound Message tab as well for response message.

Regards

Anku Chopra

[Former Member]

Hi Experts,

In my Receiver SOAP adapter module Tab.

As my scenario is synchronous and i required UsernameToken with PasswordDigest security i have added following parameter value in module.(as per SAP Note 1039369 FAQ XI Axis Adapter ).

Processing Sequence.

Module Key

afreq

xireq

wssec

trp

xires

afres

Module configuration

ModuleKey ParameterName parametervalue

xireq handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler

wssec action UsernameToken

wssec handler.type java:com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender

wssec passwordType PasswordDigest

wssec pwd.password ********************

wssec user XYZ

trp handler.type java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender

trp module.pivot true

xires handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler.

Do we need to do any other configuartion apart from above in parameter value.

While getting response from third party i getting error as WSDoAllReceiver: security processing failed (actions number mismatch)

Do i need to add parameter value for WSDoAllReceiver as well as my scenario is synchronous.

Please help me out on this as i am not able to proceeed further because of the above errro.

Please advice.

regards

Anku Chopra

[Former Member]

Hi Experts,

Any inputs on this?

Please advice

Regards

Anku Chopra

[Former Member]

Hi.

The reason you are not seeing a chequred flag for the request message is because successful sync messages are not logged by default. Turn Synchronous logging on in transaction sxmb_adm -> integration engine configuration.

Looks like you are getting a soap application fault back and it looks like you are not mapping the application fault in you message mapping.

The payload of the response message should give you an indication of whats wrong...what does it say?

Cheers.

[Former Member]

Hi Rodney,

I am not getting any payload option for response message in Request Message Mapping tab.

Please advice.

Regards

Anku Chopra