Modification of the SOAP Adapter

Hi all,
my problem is still the same as posted in the last thread. I have a webservice request submitted to the XI, which has no header element. So i have the problem that the message does not reach the XI due to an authorization error.
Now i had the idea to implement an own adapter. But instead of developing it from zero, i could modify the original SOAP Adapter. Is there a possibility to get the SOAP Adapters source code or has anyone an idea how i could resolve this problem without an own adapter.
I am not allowed to turn authorization off for the whole SOAP Adapter.
Thanks in Advance
Dieter

Hi Dieter,
1. add the credential (user and password) in the sender application, how to do this depends on what platform you use in the sender application.
2. following the link below, you find the document on how to develop a module.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
I don't think you need to develop a ADAPTER for this problem.
Regards,
Hui

Similar Messages

Messages failing in the SOAP adapter with the errror

HI
I am getting the below error in the SOAP adapter monitoring . can any body tell what does "No route to host: Connect" mean .
could some one help us on resolving this .
Error Exception caught by adapter framework: No route to host: connect
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: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect. Setting message to status failed.
Error The message status set to FAIL.
Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect.
thanks and regards
sandeep

Hi!
First please confirm whether you are working on XI or PI 7.1 ?
because in XI you need to generate WSDL manaually via Tools>Define Web service-Giving Input..and in XI you need to test the SOAP scenario from external tool like Altova xml spy tool kit or else SOAP client tool.
In PI 7.1::
You can publish directly the web service in the SERVICE REGISTRY from sender agreement onwards.
once it is published you can check the status on your interface in service registry as CONFIGURED..Okay
Here you can test directly in service registry...
According to your error check ocne agan even though you gone through all the steps..
1. Check whether the SOAP service is active or not in SICF>SAP>bc>XI>Service-->SOAP.
2. sicne after generating wSDL u can get one url right that URL itself acts as a gateway to enter the source data into XI..
lets give to the source team to try with XI super uID adn PWD as authentification.
3. Also please STOP ur communication Channel and start once again.
4. Please check whether the WEB Service is configured correctly or not.
Regards::
Amar Srinivas Eli

PI 7.3 AEX - XI 3.0 message protocol in the SOAP adapter.

Hello,
My client's landscape is on SAP PI 7.3 AEX(Java only installation) and SAP ECC 6.0 EhP4.
I have configured a HTTP-Proxy scenario. For the proxy messages to go into the SAP ECC system, I have configured a SOAP Receiver adapter in PI 7.3 AEX.
I have created a service interface in ESR in PI 7.3 and generated the proxy in the SAP ECC system.
I have configured the SOAP receiver to use the XI 3.0 protocol and by using the Addressing Type as 'URL Address'. The URL that I am using is " http://<SAP_ECC_server>:PORT/sap/xi/engine?type=entry ".
When I try to test the scenario, the messages are not reaching the target ECC destination and in the SOAP Receiver communication channel, I am getting the following error:
Information:                Delivering to channel: SOAP_RECEIVER
Information:                MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Information:                SOAP: request message entering the adapter with user Guest
Error:                          SOAP: call failed: java.io.IOException: unable to create a socket Information                 SOAP: sending a delivery error ack ...
Now, in my client estate there is also a SAP PI 7.11 system, I have replicated the service interface in the ESR on 7.11 and regenerated the proxy in SAP ECC. When I now run the scenario, it works.
Just stressing here on the point that, the abap proxy generated from SAP PI 7.3 ESR did not work(but worked when I generated the abap proxy from SAP PI 7.11 ESR) when configured using the XI protocol on the SOAP adapter.
ALso, I have gone through the 'Note 1247043 - Release Restrictions for EHP 1 for SAP NetWeaver PI 7.1'.
Is the behaviour I am facing a release restriction on SAP PI 7.3
Need suggestions from anyone who has tried configuring this scenario, is there anything that I have missed?
I am happy to share more info if required...
Thanks in advance,
Best Regards,
Karthik

HI Karthik,
Did you able to resolve this in PI 7.3??
Even i am also facing the same issue in receiver soap adapter for abap server proxy:
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Please let me know how did u resolve this?
Thanks,
Prasanthi

Any one knows how to use Axis Framework in the SOAP Adapter Modules

How to use Axis Framework in the SOAP Adapter?
How to add custom handler modules?
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm
I went through the above link on help.sap.com. But still could not create a working example.
I have created a wc on some 3ed party app server using apaches axis. I am trying to call that web service from XI using SOAP receiver? I need to add some security related headers to the soap message, SO I am trying to use a handler. I want to know how to configure this handler in SOAP axis adapter module.
Thank you
Moni

Ravi ,
I am trying exactly the same. Hers is the scenario.
ABAP Proxy --> PI (7.0) SP 12 ---> WebService.
Since This is service is secured, means it is using OASIS web servie securyty user name token,
I am trying to use AXIS adapter. and I want to configure HandlerBean in which I want to use apache wss4j api to add the userNameToken. I am looking for some documentation on this.
I need to add SOAP action element too as I can not configure this one on the communication channel.
Thanks for any inputs in this regard.
Moni

Using the Axis Framework in the SOAP Adapter

Hello experts,
I am currenty checking how I can easily manipulate sender and receiver details and how I could get attachments into XI.
I saw in the sap help that it is possible to use the AXIS framework from the SOAP adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/45/a39e244b030063e10000000a11466f/frameset.htm
As usual, the documentation is of the same quality SAP usually provides.
So my first question would be: This is a moduke to be used from the SOAP adapter right? I am asking because they also wirte about the AXIS adapter and its metadata.
In oder to get it working, I created in the NWDStudio a library project, added my libraries (to the root directory) and deployed it via SDM. Deployment is succesful but its not working.
SAPHelp says I should check for a MessageServlet - I ask myself how that could appear suddenly just by packaging some axis libraries...?
I am using for that the ESA box (NW04s SP6) - I was not able to see whether there are some dependencies to the SP - are they?
Thanks for your support!
Helge

Helge,
Axis is outdated and has some issues ..use Apache Soap instead its much better and easy to use.
http://ws.apache.org/soap/
Regards
Ravi

Configuring the SOAP Adapter

Hi Folks,
I have a sceanrio where an AXIS client needs to talk to the XI SOAP Adapter.
How do I configure the SOAP adapter?
I tried to access the help docs for configuring the SOAP adapter. I understand that the adapter depends upon the plain J2SE Adapter Engine which should be available on port 8000.
But when I try to access
http://<hostname>:8000 I get an access denied error
Please help!
Thanks in advance,
Shailesh

Hi Shailesh,
Maybe your 8000 Port is in Use. So you can chance the port to 8200 or something else.
You Change port in "GUIBrowserEngine.properties" file.
And try to patch the Plain J2SE Adapter Engine with "SP 10 for XI Connectivity SE 3.0"
Regards,
Robin

Problem with the SOAP adapter !

Hi!
We are trying to use a WebServices from XI.
In the WSDL file that we have imported and use'd in
our mapping the information about the soap header look's
like this :
<wsdlsoap:header message="impl:serviceRequest" part="toCountry" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="fromCountry" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="language" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="customerCodeOwner" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="customerCode" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="userId" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="userPassword" use="literal" />
But then the message leave the SOAP adapter
it looks like this:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header/>
<SOAP:Body>
<ns1:serviceRequest xmlns:ns1='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/wsdl'>
<nRGDecisionSupportDSCRequest>
<ns2:criteria xmlns:ns2='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/request'>
<ns2:socialSecurityNumberApplicant>XXXXXXXXXX</ns2:socialSecurityNumberApplicant>
<ns2:conversationCode>X</ns2:conversationCode>
</ns2:criteria>
</nRGDecisionSupportDSCRequest>
<toCountry>XX</toCountry>
<fromCountry>XX</fromCountry>
<language>XX</language>
<customerCodeOwner>SYD9001</customerCodeOwner>
<customerCode>XXXXXXX</customerCode>
<userId>XXXX</userId>
<userPassword>XXXXXX</userPassword>
</ns1:serviceRequest>
</SOAP:Body>
</SOAP:Envelope>
The SOAP header info. is in the body !
Ofcourse the message fails !!
Any ideas ??
//Stig

Hi Stig,
Although specified in the WSDL 1.1 spec, the use of soap:header is quite rare.
And having a soap header consisting of multiple parts and not referring to single XSDL element is a bit in conflict with the document/literal approach.
Bottom line: please try and convince your business partner to not use the soap:header trick and stick to standard document/literal web services.
Kind regards, Guy Cretgs

Problems when calling the SOAP adapter from a Webdynpro

Hi,
An error occurs in the SOAP adapter when sending a message from a Webdynpro client. I have downloaded the SAP Soap Client and made the same test and that works fine.
I had to do some debugging to finally find the stack trace found below.
Does anybody have an idea of why the call doesn't work from Webdynpro?
<text>com.sap.aii.af.service.cpa.CPAException: invalid channel (party:service:channel) = <null>
     at com.sap.aii.af.mp.soap.web.MessageServlet.getChannelID(MessageServlet.java:415)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:377)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)</text>
</s:SystemError>
Thanks for help,
Hans

Hi Suraj
First I should mention that I have imported a generated WSDL from XI to create the Model and thus the port configuration. The URL looks like this:
http://<host>:<port>/XISOAPAdapter/MessageServlet?Version=3.0&Channel=:Telia_Kundservice_portal:Sender_SOAP&version=3.0&Sender.Service=Telia_Kundservice_portal&Interface=urn%3Aacandofrontec.se%2FTelia%2Ffaktura%5ETelia_faktura_4
Service = Telia_Kundservice_portal
Channel = Sender_SOAP
I've also tried with a modified shorter version which is also the one I'm using from the SAP SOAP client.
http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:Telia_Kundservice_portal:Sender_SOAP
The actual call is a typical one:
wdContext.currentRequest_Faktura().modelObject().execute();
Before this call the Basic authentication (user/passw) is set.
Regards,
Hans

Configurating the SOAP-Adapter

Hallo,
i'm trying to run the SOAP-Adapter. The Adapter Engine offers an Test-Environment. With this Test-Client you can send SOAP-Messages and receive some kind of response. First try faild. So i read every posting in this forum, but i still can't get it. I think the Adapterconfiguration is well done. (If i refer to the most postings) What else is to do in the Repository or the Directory?
My current errormessage from the Test-Environment:
content-type: text/xml
content-length: 405
content-id: <[email protected]>
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: com.sap.aii.messaging.mo.MalformedMessageException: Fatal Error: com.inqmy.lib.xml.parser.ParserException: XMLParser: No data allowed here:Bit (:main:, row:1, col:3); </faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope>

Moritz--
Assuming that the error message is coming from the request side, and not the response side...
The adapter thinks that the XML you're sending in is bad. That error is coming from the SOAP adapter itself; the adapter is telling you that you have an XML syntax error.
Check your XML for missing tags, a forgotten "/" in an end tag, misplaced "<" or ">", or characters outside of your start-tag/end-tag pairs. "-" or "+" sometimes pops up as an extra character between tags if you copy and paste XML from a Web browser (or other GUI application) or the XI monitor.
--Dan King
Capgemini

How to create SDA file for using AXIS Framework in the SOAP Adapter

Hi experts,
I have the following question:
How I can create the SDA file aii_af_axisprovider.sda for using the AXIS Framework in the SOAP Adpater described in http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm ?
I have downloaded the files axis.jar, commons-discovery-0.2.jar, commons-logging-1.0.4.jar, commons-net-1.0.0-dev.jar and wsdl4j-1.5.1.jar. But how to create the SDA file aii_af_axisprovider.sda? Which tool I have to use for this? It is enough to compress these 5 jar-files in the sda file or need I further files with further information (meta information etc.)?
Thanks and best regards
Christopher

Hi Christopher,
Check this discussion if you have not checked already.
Re: NTLM Authentication dosent work with XI ?
Regards,
Ravi

What is the transport protocol File (Axis) in the SOAP Adapter

Hi,
for a SOAP Receiver Adapter it's possible to choose 'File (Axis)' as transport protocol.
How does it work and is there some documentation about it?
Thanks and regards
Patrick

Hi,
thanks for your answers.
@Prateek
Yes I tried -> Doesn't say so much
@Vinod
The first thread didn't helped me and I have seen already the second one.
@kummari
The question is how can I use it?
@Gabriel
>The adapter uses transport protocol(File (Axis)) to send SOAP messages as text file
Could you please explain it a little more detailed (maybe with an example)?
My question is about in which scenarios it makes sense to use this transport protocol and how is it used?
Thanks and regards
Patrick

Problem in the SOAP ADAPTER

Iam getting following error when iam trying to view the wsdl for bapi_user_get_details.Any help?
Error when processing your request
What has happened?
The URL http://pdcntwr.wipro.com:8000/sap/bc/srt/rfc/sap/bapi_user_get_detail was not called due to an error.
Note
The following error text was processed in the system NAJ : An exception that could not be caught occurred.
The error occurred on the application server PDCNTWR_NAJ_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Form: HANDLE_REQUEST of program CL_SOAP_TRANSPORT_EXTENSN_ROOTCP
Form: HANDLE_REQUEST of program CL_SOAP_HTTP_EXTENSION========CP
Form: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_SOAP_HTTP_EXTENSION========CP
Form: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP

Hi Ravikumar,
Could you please provide more details about what exactly are you trying to achieve and a short description of your scenario?
Do you want to see the details in the WSDL file ? Or Are you trying to access a web service defined in this WSDL file?
Thanks,
Rob.

SOAP: "XI.Timeout" module in the sender adapter

Hi,
Could you please explain in detail, how to enter the XI.timeout module in the soap sender adapter.
Regards,
Vishnu.

Hi Vishnu,
The default timeout value for synchronous calls is 5 minutes. You can increase this value by setting parameter XI.Timeout in the module parameter table of the SOAP adapter. The value must be given in milliseconds. For example, value 600000 represents the timeout value of 10 minutes. This parameter is not recognized in systems prior to SP13.
In the Module tab of the Communication channel you can find Module Parameters can be specified under Module Configuration section.
Add the XI.Timeout Parameter with some Parameter Value.
regards
Ganga

Error when setting dynamically the target URL in receiver SOAP Adapter

Hi,
I'm setting dynamically (from the mapping) the target URL in the receiver SOAP adapter:
String url = "http://mosxd30:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=DUM&receiverParty=&receiverService=&interface=SI_OA_CustomInvoiceData&interfaceNamespace=urn:repsol.com:laboratory:firma";
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(key, url);
The receiver adapter fails with:
"invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized"
Reading weblogs, etc, the most probable cause for this is a wrong target URL, but then what I did was to set it as a fixed URL in the C.Channel, and it worked, so the URL is fine.
In the communication channel, I'm using "Configure user authentication", with a user and password, and what I think it's happening is that if I use another different URL dynamically, the channel is ignoring the user authentication settings.
Any ideas?
Thanks

I forgot to say that I've checked the SAP note "FAQ Soap adapter", and it says:
Q: I get an authorization error "401 Unauthorized" from the adapter's servlet. What went wrong?
           A: The adapter's servlet is protected by default. You must use one of the user names assigned in security role xi_adapter_soap_message for component XISOAPAdapter. Please consult the documentation for Visual Administrator to view and change the security setting.
           The user authentication of the SOAP adapter is not part of the SOAP adapter but of the web container of the J2EE engine. The default authentication setting is defined in the web.xml descriptor file of the SOAP dapter web application. This setting may be modified from Visual Administrator with some restriction. Please refer to the security documentation for the J2EE engine.
           Please note that 710 onwards there is no Visual Administrator instead the Netweaver Administrator is to be used to assign the roles to the user to access the SOAP adater servlet.The user must be assigned one of the following roles SAP_XI_IS_SERV_USER, SAP_XI_APPL_SERV_USER, SAP_XI_DEVELOPER_J2EE, SAP_XI_ADMINISTRATOR_J2EE.
The target URL is a sender soap adapter (the result of one interface is sent to another one via soap adapter), and it's this one which is complaining because of the authentication I think. But I don't know why it's ignoring the user authentication flag I'm using.

Error in the SOAP Receiver communication channel

Hi ,
My scenario is RFC - to -SOAP (synchronous ) i have specified the TARGET URL inthe SOAP receiver comminication chanel.. but while testing the interface by providing the test data from R/3 .. I'm not getting any Respose.. ..
If I check in the SXMB_MONI in i'm getting the following message .. but the URL whicjh i provided that is fine.. but my doubt is through XI may be it's not able to connect the Target System... .. so, please suggest me...
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: www.webservicex.net</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
regards
Jain

By default, the SOAP adapter sends the SOAP message with the content type text/xml.
When you check "Do not use SOAP envelope", the default contnet type is application/xml.
You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.
Check out this
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
One way of testing ur scenario
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
Also have a look here
SAP Note 856597
reward points if solution found helpfull
regards
chandrakanth

Modification of the SOAP Adapter

Similar Messages

Maybe you are looking for