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

Similar Messages

  • 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

  • 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

  • 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) = &lt;null&gt;
         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&amp;Channel=:Telia_Kundservice_portal:Sender_SOAP&amp;version=3.0&amp;Sender.Service=Telia_Kundservice_portal&amp;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

  • 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

  • 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

  • Login Module configuration for soap adapter ?

    Hi Guys,
    I have configured XISOAPAdapter for client certificate Authentication and i have created 1443 as the HTTPS port on the ABAP stack and defined this port in the instance profile.
    Under SSL provider i have selected 50101 as the HTTPS port and the user mapping to the certificate works fine and i was able to login directly.
    https://host:50101/XISOAPAdapter/MessageServlet - I was able to login with the user mapping to certifcate.
    but when i try https://host:1443/XISOAPAdapter/MessageServlet - it is asking for the basic password authentication and the automatic login with the certifcate is not working. Our customer will be using this url to send messages to soap adapter.
    under policy configurations for XISOAPAdapter, i have defined only clientcertificateloginmodule and define the rule as Rule1.getUserFrom=wholecert.
    any help or suggestions would be appreciated.
    Thanks,
    Srini

    Hi,
    We also experienced that limitation when a vendor is connecting to our XI SOAP Sender Adapter. It is asking for basic username/password. What we did was to create a Generic XI user with a password on it and use SSL authentication at the same time. Our Scenario was PI --> XI --> SAP R3, with the PI system using an HTTP RFC destination with a Basic Logon and Active SSL option to connect to the same system as yours https://host:portnumber/XISOAPAdapter/MessageServlet
    Let me know if this helped...
    Regards,

  • HTTPS configuration for SOAP adapter

    Hi,
    We have a requirement where we need to send the request to the target URL with https protocol.
    We have raised a request to configure the XI server for HTTPS.
    HTTPS has been configured on both ABAP stack and J2EE stack.
    But we could not find the HTTPS option in the drop down list of transport protocol in receiver Soap adapter.
    For this do we need to do any setting changes on the XI server after the configuration?
    Thanks,
    Jyothsna .

    Hi,
    You need to setup SSL layer for HTTPS endpoint.
    Possible HTTP security levels are (in ascending order):
    HTTP without SSL
    HTTP with SSL (= HTTPS), but without client authentication
    HTTP with SSL (= HTTPS) and with client authentication
    Please go through below link for referance (above information is from below link)
    Step by step guide for SSL security
    step by step guide to implement SSL
    http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ff/7932e4e9c51c4fa596c69e21151c7d/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/13/4a3ad42ae78e4ca256861e078b4160/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/3a/7cddde33ff05cae10000000a128c20/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/0a/0a2e0fef6211d3a6510000e835363f/content.htm
    General guide
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a09f3d8e-d478-2910-9eb8-caa6516dd7d9
    Message level security
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d024ca8e-e76e-2910-c183-8ea4ba681c51
    Regarding message level you can encrypt the message using certificates.
    For both of this basis team has to deploy the releavant certificates in XI ABAP Stack or Java stack.
    Generally if the scenarios are intra company we dont use any transport level or message level security since the network is already secured.
    Check the following links.. you will get the information all about the securities...
    http://help.sap.com/saphelp_nw04/helpdata/en/f7/c2953fc405330ee10000000a114084/content.htm
    Also read thru this link for message level security - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d024ca8e-e76e-2910-c183-8ea4ba681c51
    Also find soeminformation in these links
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/882a40ce93185de10000000a1550b0/frameset.htm
    /people/aparna.chaganti2/blog/2007/01/23/how-xml-encryption-can-be-done-using-web-services-security-in-sap-netweaver-xi
    Thanks
    Swarup

  • Problem regarding Configuring the File Adapter

    Hi,
    I am making a Flat File to XML File Scenario. I have made all the Necessary developments and the Routings in the Integration Repository and the Integration Directory. The Sender Communication Channel Uses the Message Protocol "File Content Conversion". All the required steps have been done. We have installed the System and also the Basis Team has done the Post Installation Activities.
    <b> The Problem is that the "File is not getting picked up". When checking the RWB and henceforth the Adapter Monitoring we see that the File Adapter is disabled and the XI and the BC adapters are green. Previously we were on SP9 and now we are on SP14. The SAP Basis is at 640 and SP9 and the SAP ABAB is on 640 and SP9.</b>
      We are also unavailable to see the File Communication Channels that we have created. When the Tcode "sxi_cache is run it is giving an error that Cache not refreshed andon refreshing various times too the Cache is not Refreshed.
    Please Suggest us what we should do. Eagerly waiting for a reply and Thanking in Anticipation. Do we need to make some for configurations for that.
    Warm Regards
    Chakra and Somnath

    Hi Somnath,
    If the sender file adapter is up and running and even after that if you find some problem, the first thing you need to do is check if your file has been picked. The easiest way to check the same is to set the mode to DELETE, that is the file gets deleted as soon as it is picked. If your file has not been picked then the reasons for the same could be the following.
    - The path that you specified while configuring the sender communication channel would have been wrong.
    - While specifying the file name take care as it is case sensitive.
    - If you require content conversion then make sure that the parameters entered at the time of configuration are all correct.
    Please go thru the following links to get a very clear picture of your requirement.
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/44/6c9442c22d1131e10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/8c/607fe4756b654ab9f420097c29f6e9/frameset.htm
    Also make sure that your content conversion is in sequence wrt Datat Type Sturcture.
    Go through these blogs below for more detail on the same:
    /people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    I hope this would help you solve your problem.
    Regards,
    abhy
    Message was edited by: Abhy Thomas

  • How to configure the jms adapter

    hi all,
           i got some trouble trying to configure de JMS adapter, i 'd be glad if some colud give me a hand with this. i'am wordering if there is a complete document about this topic to help me out with de configuration.
    thk u all very much.
    Regards, Pablo

    Hi,
    The below URL will help you to understand what is JMS, how to configure and do a testing.
    http://learn-oraclesoa.blogspot.co.uk/2013/04/oracle-jms-adapter-tutorial.html
    Below will help you to configure the JNDI for JMS
    http://manojm-nair.blogspot.co.uk/2013/02/configuring-connection-jndis-for-jms_13.html
    Thanks,
    Vijay

  • 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

  • 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

Maybe you are looking for