SOAP 1.2 Axis adapter

Hi guys,
we are trying to send WS to a vendor using Axis(SOAP 1.2) adapter.
we are getting below error in response.
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: The message with To '' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndpointAddresses agree.</SAP:AdditionalText>
Any idea, what might be the cause.....
-santosh.

This error is mainly due to mismatch in endpoint URL. Are you sending the message via dispatcher or load balancing clustering mode? Talk to your target system or vendor.. Looks like there side Address Filter does not configured endpoint of your target URL. Google this error message for more details. This is not certainly PI error.

Similar Messages

Remove XI-part of SOAP Header in Axis Adapter

Hi folks!
We are running a PI 7.11 and use the SOAP Axis Sender Adapter in a synchronous SOAP Web Service scenario. Our challenge is that in our response we definitely need a SOAP Header tag, but it should be empty like this <soapenv:Header/> or this <soapenv:Header></soapenv:Header>
We tried to achieve this with the Axis Handler com.sap.aii.axis.soap.HeaderRemovalHandler. But regardless of the parameters we provide to this handler it always removes the complete SOAP Header. On sample is to remove the PI-specific Main header tag from SOAP Header:
name.1=Main
namespace.1=http://sap.com/xi/XI/Message/30
We also tried it only with namespace. But always the same sh... happens: The SOAP Header is removed completely.
Any ideas?
Thanx very much in advance!
Regards,
Volker

Hi Stefan!
Thanx for your reply. We found that Axis handler mentionedby me in SAP Note 1039369 "FAQ XI Axis Adapter" .
But please tell me how to parameterize the java:com.sap.aii.axis.xi.XI30InboundHandler to ensure that the XI part of SOAP header is removed, but not the complete SOAP header.
Thanx in advance!
Regards,
Volker

What exactly can AXIS Adapter do?

Can someone give me a scenario when only SOAP Adapter is not enough and I will have to deploy AXIS adapter to complement SOAP adapter? Is AXIS adapter useful even if i am not implementing any 'message-level' security?
Can message be posted to AXIS adapter without clinet having to authenticate to AxisAdapter?
I have an XI web service that my clinet is unable to consume as they don't know how to authnticate to SOAP adapter before sending a SOAP message. We don't have any 'message-level' security, but SOAP adapter requires Basic authentication. Client is able to pass Authentication details in SOAP Header but I guess they first need to authenticate to SOAP adapter before sending SOAP messages. can AXIS adapter accept incoming SOAp messages without user authenticating and then extract Logon details from SOAP header and authenticate client.
Thanks,
Saurabh

The Axis framework provides the following:
●      Message protocols SOAP 1.1 and SOAP 1.2
●      Transport protocols HTTP/S, SMTP, file
●      Various user authentication procedures (Basic, Digest, NTLM, SAP Assertion Tickets)
●      Various encapsulation formats (MIME, DIME, MTOM)
●      You can add your own Axis handlers to the module chain by using the HandlerBean module
Soap 1.2 message protocol is available for AXIS Soap Adapter.
please visit the article
/people/andre.stuij/blog/2008/04/23/principal-propagation-in-ccbpm-finally-made-possible
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f
http://help.sap.com/saphelp_nw70/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm

PI 7.11 Receiver SOAP (Axis) Adapter with MTOM (Attachments)

Hello,
Iu2019m trying to configure the Receiver SOAP (Axis) adapter for sending SOAP attachments via MTOM to a third-party webservice, but I'm not getting that PI transform the binary encode64 data in an payload element into a MTOM attachment (xop:include).
The configuration looks like this:
Transport Protocol: HTTP (Axis)
SOAP Version: 1.2
Encapsulation Format: MTOM
Keep Attchments: enabled
Payload Extraction: SOAP Body Child
First of all, could you confirm if this is supported?
Or Axis only supports MTOM for the transport protocol 'File (Axis)' like it seems refered in [Configuring the Receiver Axis SOAP Adapter|http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a3c48c87cd0039e10000000a11466f/frameset.htm]
Can you please provide me some guidance here?
Thanks in advance!
Kind Regards,
Alexandre

Hello,
I am facing the exact same issue.
I can't seem to set the cookie in the http header after following the guide.
Cookie: WSL-credential=MyOwnCookie
I managed to set the SOAPAction though.
Anyone has any ideas?

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.

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?

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

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

How to install SOAP Axis adapter and where is it available ??

Hi,
I heard that SOAP Axis adapter was not initially available for PI 7.0 and was introduced in some later support pack.When I checked the below url I found that some of the components are missing.
http://xi-dev.intranet.com:50000/XIAxisAdapter/MessageServlet
Can anyone please suggest how I can get that pack and where it will be available?
How to install it?
Thanks
Deepthi.

Hi Sunil,
Dont mind...one final question, they mentioned in the README file as below..
// Open the SDA archive using some unzip tool and replace the following empty
jar files with the those inclued in Axis 1.4 src package
axis.jar
commons-discovery-0.2.jar
commons-logging-1.0.4.jar
commons-net-1.0.0-dev.jar
wsdl4j-1.5.1.jar
When i checked in the Axis folder, I found so many files.
Do I need to just add this Axis zip file into aii_af_axisprovider.sda Archive file.?
If possible, It would be very helpful if you send the aii_af_axisprovider.sda file which you have deployed into your system?
Thanks
Deepthi

SOAP (Axis) Adapter

Hello XI SDNers,
I want to use SOAP (Axis) Adapter for my Webservice Scenario.
According to the SAP Note 1028961, I deployed the "aii_af_axisprovider.sda" file with corresponding ".jar" files from Apache AXIS 1.4 and the deployement was successful.
But now, If I want to use this SOAP (Axis) Adapter, I am unable to see this adapter in my list, for ex., If I create a new "Communication channel" in Configuration and want to select the new SOAP (Axis) Adapter, I couldn't see this in my list.
Am I still missing something?
-Satish.

dear ..
My system is PI7.0 sp15.
With "http://host:port/XIAxisAdapter/MessageServlet" checking , everything corrected.
All jars from axis-bin-1_4.zip and axis-src-1_4.zip .
under " aii_af_axisprovider.sda\META-INF " has a " primary-library-sda-dd.xml " , content :
<?xml version="1.0" encoding="UTF-8"?>
<SDA>
<SoftwareType>primary-library</SoftwareType>
<engine-deployment-descriptor version="2.0" />
</SDA>
I don't know, why didn't list...

SOAP Axis adapter - problem with XML formatting

Hello All,
We are using SOAP Axis adapter on our scenario (because of NTLM authenticatiom) and faced a problem that some module in a module chain is pretty-formatting XML message (inserting newlines and spaces).
Receiving WebService is REALLY strict on format and doesn't allow spaces and newlines between XML elements.
Formatting is for sure done already in adapter as in sxmb_moni message is still one-liner.
After different tests this formatting is most likely done by XI30OutboundHandler.
Are there any parameters to prevent this formatting?
If there are no parameters, than maybe there is a standard module to remove this XML indentation?
Where I can found source code for XI30OutboundHandler to check how it is extracting payload from XI message?
Thanks in advance for your answers!
Best Regards,
Artsiom Anichenka

Hi, have you find a solution for this problem?
I've tried set the parameter “disablePrettyXML”, as mentioned in SAP note 1039369 (search for “disabling pretty XML”), but apparently it didn’t work too. Have you tried that?
I still get linefeeds and carriage return in the post requisition to the WebService.
Regards,
Ronaldo Schork.

SAP PI 7.3 Receiver SOAP Axis adapter header Cookie

Hello
We are currently working a synchronous scenario like SAPERP --> PI --> WebService.
The WebService requires cookie authentication.
I have successfully tested SOAPUI <-->WebService Scenario.
The Issue is when I try to put the Cookie in the SOAP header using Axis Frame work.
1. I have followed the blog How to Set http-Header Parameters Using the Axis Framework (NW7.0)
Guess the only one available on net.
2. I have checked my http://<host>:<port>//XIAxisAdapter/MessageServle
2.1 and the status of the mandatory components are in green.
3. We are on SAP PI 7.3
When I try to execute the scenario and capture the SOAP request in TCPGateway the following is the result.
POST /ABC/ABCService_v1 HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: MYIPaddress:54000
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "urn:ABC/DEF/interface/v1.0/TEST/GetCalculation"
Content-Length: 2228
The below is the SOAP header from the soapUI application and I am expecting to achieve something similar/workable one with SAP PI.
POST /ABC/ABCService_v1 HTTP/1.0
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "urn:ABC/DEF/interface/v1.0/TEST/GetCalculation"
Cookie: WSL-credential=MyOwnCookie
Content-Length: 2512
Host: www.DEVTESTHOST.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Can anyone pls let me know why I am not able to put the cookie in the SOAP header.
Anyone who have already tried and was successful in this scenario pls do let me know what I am missing.
Thanks in advance.
Regards
Prasanna

Hello,
I am facing the exact same issue.
I can't seem to set the cookie in the http header after following the guide.
Cookie: WSL-credential=MyOwnCookie
I managed to set the SOAPAction though.
Anyone has any ideas?

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

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?

SOAP 1.2 Axis adapter

Similar Messages

Maybe you are looking for