Axis Adapter Framwork Error

Hi
I am not able to access the axis adapter framework like i.e. (http://host:port/XIAxisAdapter/MessageServlet)
When am trying to access i am the following getting error.
Error:
404 Not Found
The requested resource does not exist.
Please provide me solution for this?
Regards
Osman Abdul Aziz Jabri

Hi Osman,
Kindly check this note:
#1039369 - FAQ XI Axis Adapter
It may helps with most common issues and doubts.
Regards,
Caio Cagnani

Similar Messages

Error while passing URL Dynamically in SOAP AXIS adapter..!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the RCVPRN of Idoc.
If
RCVPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
RCVPRN = 200 , message has to go to http://10.190.25.16:8210/file/receiver2
RCVPRN = 300 , message has to go to http://10.190.25.16:8210/file/receiver3
I used the below UDF and it is working correctly and generating the URL dynamically .
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(keyHeader1, a);
return "";
The value is coming in SOAP document as expected like below.
<sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/SOAP" name="TServerLocation">http://10.190.25.16:8210/file/receiver3</sap:Record>
</sap:DynamicConfiguration>
I used the below Configuration modules in receiver SOAP-AXIS adapter as suggested in Note 1028961.
AF_Adapters/axis/AFAdapterBean ---> afreq
AF_Adapters/axis/HandlerBean ---> xireq
AF_Adapters/axis/HandlerBean ---> dc
AF_Adapters/axis/HandlerBean ---> remover
AF_Adapters/axis/HandlerBean ---> trp
AF_Adapters/axis/HandlerBean ---> xires
AF_Adapters/axis/AFAdapterBean ---> afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
dc ---> location.1 ---> context
dc ---> value.1 ---> transport.url
remover ---> handler.type ---> java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover ---> namespace ---> http://sap.com/xi/XI/Message/30
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
and I am getting the below error in SOAP-AXIS channel at the point java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender.
2009-03-02 15:23:44 Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
2009-03-02 15:23:45 Error Axis: error in invocation: (500)internal server error
2009-03-02 15:23:45 Error MP: Exception caught with cause (500)internal server error
2009-03-02 15:23:45 Error Exception caught by adapter framework: (500)internal server error
2009-03-02 15:23:46 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (500)internal server error: (500)internal server error.
2009-03-02 15:23:46 Error The message status set to NDLV.
Kindly let me know if anyone has any idea what might be wrong?
Note : The given URL is correct one because I cross checked by passing them normally by giving directly in adapter and they are all working and the message is going to receiver.
Thanks
Deepthi

Hi Stefan,
>> dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
>> dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
>> dc ---> location.1 ---> context
>> dc ---> value.1 ---> transport.url
>> Try read instead of write
When I tried with this, I am getting the below error "Connection refused ".
Success Axis: entering HandlerBean
Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: java.net.ConnectException: Connection refused
Error MP: Exception caught with cause java.net.ConnectException: Connection refused
Error Exception caught by adapter framework: ; nested exception is: java.net.ConnectException: Connection refused
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: ; nested exception is: java.net.ConnectException: Connection refused: java.net.ConnectException: Connection refused.
Success The message status set to WAIT.
It is going successfully when I tried sending directly. Looks like Dynamic Configuration is not working for SOAP-AXIS.
Any Suggestion?
Thanks
Deepthi.

Error in Sender AXIS adapter with UsernameToken

Hello,
I'm trying to implement a web service with UsernameToken authentication (legacy >PO>ECC), after research in this forum, some blogs and notes, I've found this approach: Axis Adapter Sender Comm Channel with usernameToken .
I did all steps, but everytime I try to consume the web service, it doesn't work and I get the following error in default trace:
No application classloader can load login module class: com.sap.engine.services.security.server.jaas.DigestLoginModule. Probably application that deployed the login module is stopped and cannot be started.
My system is PO 7.4 SP5.
Do you have any idea?

Hi,
May be below links will help you
1. /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
2. Have you used method of ConnectionFactory also??
3. 804102
xi 3.0 mail adapter with pop3 user authentication problem
4. 810238
XI 3.0 Mail Adapter for POP3 may not report some errors
Thanks
Swarup

Reciver Axis adapter error

Hi,
My interface is RFC to Webservier synchronous here i am iusnig SOAP Axis adapter for NTLM authentication.
I am getting the below error in my receiver SOAP Axis adapter
Information MP: processing local module localejbs/AF_Adapters/axis/HandlerBean
12.01.2012 08:12:39.287
Error MP: exception caught with cause org.xml.sax.SAXException: Bad envelope tag: html
Thank you
Srinivas

Hi Srinivas,
Try having a look at this [OSS Note 1039369 - FAQ XI Axis Adapter|https://websmp130.sap-ag.de/sap(bD1wbCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1039369]. You will find an FAQ for Axis Adapter there. Also, see a similar thread here: Error in SOAP Sender Communication Channel.
Hope this helps,
Grzegorz

faultstring SOAPAction /faultstring --- Error in Axis Adapter

Hi All,
I am doing an sender https scenario. My end customer uses ariba to send messages to XI. They dont want to use username and pwd to send the document. So we have eliminated the soap adapter (because it asks for username and pwd to send the request). Now we are using axis adapter (where we have removed the user and pwd paramters in axis adapter itself). So it dont ask for username and pwd anymore for any of the axis comm. channel.
Now the issue is when we send a https request to my url(I have created wsdl using xI and took the url from it) using SOAP UI I am able to get it into xi. But when they use ariba or Fiddler (we can download free for testing) they are getting an error message like:
<soapenv:Body>
<soapenv:Fault>
   <faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:Client.NoSOAPAction</faultcode>
   <faultstring>SOAPAction</faultstring>
   <detail>
    <ns2:stackTrace xmlns:ns2="http://xml.apache.org/axis/">SOAPAction
     at com.sap.aii.adapter.axis.web.ServletReceiverCore.getSoapAction(ServletReceiverCore.java:665)
     at com.sap.aii.adapter.axis.web.ServletReceiverCore.doPost(ServletReceiverCore.java:273)
     at com.sap.aii.adapter.axis.web.MessageServlet.doPost(MessageServlet.java:392)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
When I researched this it seems xi is expecting a soap action. But they dont have an option to add the soap action on their side. Now I am struck what to do.
When I googled for this error, it seems it is not error with xi, it is with the apache axis itself. It seems like by default apache axis expects a soapaction and if we dont want to send then we need to give soapaction as "" (which is null). I dont know where to give this. I assume that we need to change the jar file somewhere on axis adapter. No idea where it is and what to do with this approach.
Also I have seen stefans weblog:
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
With this first I need to create an https abap port. Then I can use soap adapter directly by sending username and pwd directly to the url. But the catch here is also to send soapaction which in our case is not possible.
Can anyone of you please help me out.
Regards,
---Satish

Satish,
I think the easiest solution is to
1. configure https on the ABAP stack: in trx STRUST you can use the same SSL certificate used to setup SSL in the KeyStorage service of V.A. so that calling the ABAP http or the J2EE http will be copletely transaprent to your SSL client (i.e. ARIBA)
2. use HTTP plain adapter ( <host>:<abap_https_port>/sap/xi/adapter_plain )
- you get rid of the SOAP envelope and SOAP action issue, as the XML payload posted by Ariba will be immediately treated as a PI message payload
- here also you can use the same two parameters as per Stefan's blog (&sap-user=<username>&sap-password=<password>) and thus get rid of the authentication issue.
Stuff sent to the plain_adapter is handled by the CL_HTTP_PLAIN_INBOUND class (use trx SE24 to take a look) and method IF_HTTP_EXTENSION~HANDLE_REQUEST: there are a number of parameters that can be supplied by the client calling it (i.e. Ariba). See below an excerpt.
* call-syntax: XI 3
* http://hostname:port/path
*                      ?namespace=???
*                      &interface=???
*                      &service=???
*                      &party=???
*                      &agency=???
*                      &scheme=???
*                      [&qos= EO|BE|EOIO]
*                      [&msgguid=???]
*                      [&queueid=???]
*                      [&trace=[1|2|3]]
I am strongly convinced that this is the far easiest solution. Programming Axis handlers can be tricky though fascinating (I've written a nice one I'll probably blog about as soon as I get a chance.) But I will nevertheless try to simulate your Axis issue when I get access to a machine like your own.
Cheers,
Alex

Axis adapter : Bad Request error

Hi,
I have a File to SOAP scenario (PI 7.0) where I am using AXIS adapter in the receiver SOAP adapter for NTLM authorisation. In the xml that I am trying to post, i have characters like & because of which I am getting a Bad Request error. Is there a way to resolve this? thanks!
Regards
Pushpinder

In file sender channel, i am using binary mode, so no encoding specified.
I see the error in the receiver SOAP adapter -
Error Axis: error in invocation: (400)Bad Request
Error Exception caught by adapter framework: (400)Bad Request
Error MP: Exception caught with cause (400)Bad Request
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (400)Bad Request: (400)Bad Request.
Error The message status set to NDLV.

Exchange rate SAOP-AXIS adapter - SAP PO 7.4

Hi Expert,
My requirement is to fetch exchange xml file from web link : http://www.nationalbanken.dk/DNUK/rates.nsf/rates.xml . I have gone through Michael blog: http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/01/05/michals-pi-tips-exchange-rates-from-an-xml-file-on-a-web-page--rest-axis
And I have done everything same but nothing happening to sender adapter.
It is showing running but no log updated.
I am working SAP PO (Process Orchestration) 7.4 SP3.
I have gone through ......../XIAxisAdapter/MessageServlet and it show below details:
Axis Adapter Message Servlet
Component Versions
Adapter Common Library Version: 1.7.4003.20130911141725.0000, NW731EXT_08_REL (2013-09-11T18:40:12+0000)
Adapter Application Version: 1.7.4003.20130911141725.0000, NW731EXT_08_REL (2013-09-11T18:40:22+0000)
Axis Version: ???
Required Components
Apache-Axis
Error: required component missing --- looking for org.apache.axis.AxisEngine in com.sap.aii.af.axisproviderlib/axis.jar; see http://ws.apache.org/axis/
Jakarta-Commons Discovery
Error: required component missing --- looking for org.apache.commons.discovery.Resource in com.sap.aii.af.axisproviderlib/commons-discovery.jar; see http://jakarta.apache.org/commons/discovery/
Jakarta-Commons Logging
Error: required component missing --- looking for org.apache.commons.logging.Log in com.sap.aii.af.axisproviderlib/commons-logging.jar; see http://jakarta.apache.org/commons/logging/
Optional Components
Thanks in advance!
Kumar

HI Amit,
I see status as error:
Required Components
Apache-Axis
Error: required component missing --- looking for org.apache.axis.AxisEngine in com.sap.aii.af.axisproviderlib/axis.jar; see http://ws.apache.org/axis/
Jakarta-Commons Discovery
Error: required component missing --- looking for org.apache.commons.discovery.Resource in com.sap.aii.af.axisproviderlib/commons-discovery.jar; see http://jakarta.apache.org/commons/discovery/
Jakarta-Commons Logging
Error: required component missing --- looking for org.apache.commons.logging.Log in com.sap.aii.af.axisproviderlib/commons-logging.jar; see http://jakarta.apache.org/commons/logging/
Number of Missing Components: 3
Status: Error
Thanks,
Kumar

Issue with Sender AXIS Adapter while XML Signing

Hi all,
We are working on a scenario, an external application pushes message to Sender AXIS Adapter in PI. However while testing XML signing we are getting below error:
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>WSDoAllReceiver: security processing failed; nested exception is:
org.apache.ws.security.WSSecurityException: The signature or decryption was invalid</faultstring>
<detail>
Could you please provide your valuable inputs on this?
Thanks,
Jaya

Hi Jaya,
Have you checked if your message is valid? Have you tested it against another server?
Which version of wss4j are you using and which PI version?
How does your module/handler configuration looks?
If the message is valid and the handler is configured correctly, you can set the trace level of org.apache to debug and see what it says.
Best regards, Yza

Problem with Dynamic Configuration in SOAP-AXIS adapter..!!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the SNDPRN of Idoc.
If SNDPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
   SNDPRN = 200 , message has to go to http://20.180.26.16:8210/file/receiver
It is working correctly when I tried for single receiver. When I' tried to use DynamicConfiguration, it is coming in SOAP document but it is not working and not passing to correct channel. According to this note 1039369, I mentioned the following modules.
AF_Adapters/axis/AFAdapterBean --->                 afreq
AF_Adapters/axis/HandlerBean      --->                  xireq
AF_Adapters/axis/HandlerBean      --->                  dc
AF_Adapters/axis/HandlerBean       --->                 remover
AF_Adapters/axis/HandlerBean       --->                 trp
AF_Adapters/axis/HandlerBean        --->                xires
AF_Adapters/axis/AFAdapterBean    --->               afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc    -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc   --->   key.1 --->      write http://sap.com/xi/XI/System/SOAP TServerLocation
dc    --->          location.1 --->         context
dc     --->         value.1      --->        transport.url
remover    ---> handler.type    --->   java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover     ---> namespace    --->      http://sap.com/xi/XI/Message/30
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
and I am getting the below error in SOAP-AXIS channel
Error Axis:    error in invocation: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error MP:     Exception caught with cause java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error           Exception caught by adapter framework: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Kindly let me know if anyone has any idea what might be wrong?
Thanks
Deepthi

I have a similar problem. I also like to add some header fields to my message und that's way I'm trying to use the AXIS adapter. (Axis adapter FAQ question 30) Unfortunately I'm getting exactly the same error message:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Deepthi, you wrote that you have missed one jar file. Can you remember which file it was?

Receiver Axis Adapter to 3rd party webservice

Hi,
My scenario is ABAP Proxy --> PI --> 3rd party webservice using Soap Adapter with Axis protocal.
I'm getting the following error when attempting to post to the 3rd party web service:
nested exception is: java.net.SocketException: Connection timed out:could be due to invalid address
We do have to go through a proxy server to go outside the firewall. I'm not sure if this may be the issue, but I don't even see where you can set this in the AXIS adapter.
Can anyone shed some light on the topic?
Thanks and regards,
Duke

Configured as stated below, and the issue was resolved.
How can I call some service over an HTTP proxy server?
The Axis's standard and adapter's HTTPSender and CommonsHTTPSender handlers recognize the java's standard network properties (http.proxyHost, http.proxyPort, http.nonProxyHosts) for HTTP proxy setting. Please check that these System properties are correctly set at the J2EE server's System properties page. For more information on how to set Java System properties, please refer to the J2EE server's documentation (SAP Note 710146 How to change J2EE Engine JVM Settings).
Thanks and regards,
Duke
Edited by: Duke on Aug 5, 2010 5:37 PM

Issue with SOAP receiver AXIS adapter

Hi All,
We have a scenario SOAP -- > PI -- > SOAP (axis) using SOAP 1.2 version synchnrous scenario. Using Webservice navigator am trying to trigger a message to PI .
Message has reached to PI box and failing in the receiver SOAP(axis) channel as :
Delivering to channel: Receive_SOAP_BulkFeedback 18.08.2014 10:33:24 Information MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error MP: exception caught with cause javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.axis.app, BC-XI-CON-SOP) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.aii.adapter.axis.modules.AFAdapterBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@6bbad627 for bean sap.com/com.sap.aii.axis.app*xml|com.sap.aii.adapter.axis.ejb.jar*xml|AFAdapterBean in application sap.com/com.sap.aii.axis.app.; nested exception is: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.af.lib.mp.module.SModule.process(com.sap.aii.af.lib.mp.module.ModuleContext, com.sap.aii.af.lib.mp.module.ModuleData) of an object loaded from field com.sap.aii.adapter.axis.modules.AFAdapterBean.core of an object
Please help and suggest.

Hi Raja,
The end system is closing the communication. Try to reset your PI ICM instance. Also check if your PI system is affected by this note 1675953 - SSL Client Authentication failed with PI SOAP Axis Adapter
Regards.

SOAP Action missing in Axis adapter

Hi,
I am not able to send data to a Web Service using Axis Adapter (SOAP 1.2) and getting an error of "SOAP Action is missing". Can see that SOAP action is missing in the SOAP message sent to Web Service. Communication channel is configured with SOAP Action.
Am on PI 7.10 SP6.
Any help is appreciated!!
Thanks
Kiran

Hello,
I tink you are using receiver SOAP Communication channel... Ask your client to provide the same... because.... your message will be processed at receiver side by using SOAP Action at receiver side...
SOAP action is mandatory for SOAP Receiver communication channels...
Thnx
Subbu

Dynamic filepath in the Axis adapter

Hi,
I have a scenario where I attatch a PDF file in a ABAP proxy as a SOAP attachment, and I need to place this file on a harddrive with the path decided from the data in the message payload. In the "normal" fileadapter I can write to the adapter specific message attributes. Is there a similar possibility with the file transport protocol with the AXIS adapter?
Kind regards
Mikkel

I have a similar problem. I also like to add some header fields to my message und that's way I'm trying to use the AXIS adapter. (Axis adapter FAQ question 30) Unfortunately I'm getting exactly the same error message:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Deepthi, you wrote that you have missed one jar file. Can you remember which file it was?

Sender SOAP Axis adapter

Hello Experts,
my scenario is to pick the data from web service and pass it to ECC side.
as i need to pick XML file from web service i used SOAP Axis adapter. configured as given in michal's blog.
the channel in running no errors in RWB, still its not picking the data.
Michal's PI tips: Exchange Rates from an XML file on a web page - REST, AXIS
your inputs on this...
regards,
chinna

Hi ,
I have confifured the same folw, it's working for me. please provide if you are getting any error.
Regards
srinivas

Axis adapter receiver handle fault message

Hi
We have a Sync interface which makes a Proxy call from ECC to PI 7.3 and then PI makes Soap(Axis) Sync call to Web sevice. We are having issues when handling SOAP 1.2 fault message.
Below is the actual fault response from Webserver:
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Header/>
   <env:Body>
      <env:Fault>
         <env:Code>
            <env:Value>env:Receiver</env:Value>
         </env:Code>
         <env:Reason>
            <env:Text xml:lang="en">FaultMsg</env:Text>
         </env:Reason>
         <env:Detail>
            <ns2:servicefault xmlns:ns2="https://hostname.de/webservice/0400-0005">
            </ns2:servicefault>
         </env:Detail>
      </env:Fault>
   </env:Body>
</env:Envelope>
But PI receives this response like system error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: FaultMsg</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked this way http://scn.sap.com/thread/1675917 but it doesn't fit for Axis adapter.
Please let me for any clues how to handle this fault response.
Regards, Dzmitry

Hi,
I'm working with Dzmitry on the issue since last week. After analyzing the implementation and checking some SAP notes I came to the following conclusion:
According to note 856597 the fault behavior of axis adapter is as follows:
" A: The receiver adapter expects a SOAP message as response. For
synchrnous calls, a successful response should be returned with
HTTP 200. In this case, the content of the SOAP body will be
returned to the caller as the response payload. When some error
occurs, the SOAP message may contain the SOAP fault element. In
this case, when the fault detail element is not empty, its
content will be returned as the fault payload in an application
error message. For others, a system error message will be
returned to the caller."
The example shows a SOAP 1.1 fault message with a "detail" node being mapped to an application fault.
As we are using SOAP 1.2 the namespace as well as structure of the fault defers. I assume that the module responsible for the transformation from AXIS message to XI message within the module chain does not recognize the detail node on out soap 1.2 fault.
Therefore the solution would be to insert a custom AXIS handler before com.sap.aii.axis.xi.XI30OutboundHandle mapping the soap 1.2 fault to a soap 1.1 fault.
Is there something like a short how to on how to implement Axis handler and how to deploy it. Sap help only says to package it into sda file....
Thanks a lot in advance!!!
BR,
Eugen

Axis Adapter Framwork Error

Similar Messages

Maybe you are looking for