SOAP Adapter details

hi all,
i am doing R/3>PI1>PI2-->File scenario.(i am working at PI2)
here i am importing the XSD's into PI2 through External definitions,for this what SOAP Adapter details i need to provide to PI1.
another interface
File>PI2>PI1-->R/3
for this scenario what SOAP Adapter Details i need to provide to PI1.
Thanks in advance
AVR

Hi AVR,
>>R/3>PI1>PI2-->File scenario
Here It will be a SOAP receiver, so the path will be as per help.sap  http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
>>File>PI2>PI1-->R/3
Here in SOAP sender you need to mention the Sender interface and namespace details and set other parameters as help.sap
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Regards
Suraj

Similar Messages

  • Error while Testing SOAP Adapter In XI

    <b>Hi Frndz
    I am trying to test my SOAP adapter which i have exposed as a webservice. I testing this from the WSNavigator which throws the following error:</b>
    HTTP/1.1 500 Internal Server Error
    Connection: close
    Set-Cookie: <value is hidden>
    Set-Cookie: <value is hidden>
    Server: SAP J2EE Engine/6.40
    Content-Type: text/xml; charset=utf-8
    Date: Thu, 15 Dec 2005 12:24:19 GMT
    <?xml version='1.0'?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
      <SOAP:Body>
        <SOAP:Fault>
          <faultcode>SOAP:Server</faultcode>
          <faultstring>Server Error</faultstring>
          <detail>
            <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
              <context>XIAdapter</context>
              <code>DeliveryException</code>
              <text><![CDATA[
    com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
         at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
              ]]></text>
            </s:SystemError>
          </detail>
        </SOAP:Fault>
      </SOAP:Body>
    </SOAP:Envelope>
    <b>I have used this url for the Webservice:</b>
    <u>http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER</u>
    <b>I am unable to figure out where the problem is.
    Any ideas to solve this?
    Thanks in Advance
    DhanyaR Nair</b>

    <b>Hi Andrews and Ravi
    Thanks for the quick response.
    <u>Andrews</u> the Message Servlet is in OK status, as it reponded from checking the url given by you.
    What should i try next?
    <u>Ravi</u> i checked the url for checking the Comm Channel. There are two IDs associated with the Channel
    1>Object ID
    2> ObjectVersion ID
    with the ObjectVersionID , we are getting the following error and with ObjectID we got the proper response  </b>
    <b>with ObjectVersion ID</b>
    <u>http://<host>:<port>//XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object version ID></u>
    <b>response:</b>
    <?xml version="1.0" ?>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
    - <detail>
    - <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
      <context>XIAdapter</context>
      <code>ADAPTER.SOAP_EXCEPTION</code>
    - <text>
    - <![CDATA[
    com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Channel object with Id Channel:a9f7f390671e11daa2300012799e22c2 not available in CPA Cache.
         at com.sap.aii.af.service.cpa.LookupManager.getCPAObject(LookupManager.java:202)
         at com.sap.aii.af.mp.soap.web.HelperServlet.processGetChannelInfo(HelperServlet.java:455)
         at com.sap.aii.af.mp.soap.web.HelperServlet.doGet(HelperServlet.java:131)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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>
      </detail>
      </SOAP:Fault>
    <b>with the object id</b>
    <u>http://<host>:<port>/XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object  ID></u>
    <b>Response</b>
    <?xml version="1.0" ?>
    - <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
      <name>CVXSACC_TEST_SENDER</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>CVXSABSR_TEST_SENDER</service>
      </s:ChannelInfo>
    <b>with the url</b>
    <u>http://<host>:<port>/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER</u>
    <b>Response</b>
    <?xml version="1.0" ?>
    - <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
      <name>CVXSACC_TEST_SENDER</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>CVXSABSR_TEST_SENDER</service>
      </s:ChannelInfo>
    <b>How should i proceed ? Any idea frndz
    Thanks in Advance
    DhanyaR Nair</b>

  • Sender SOAP Adapter

    Hi,
    Scenario is Sender SOAP and Receiver (Server Proxy) .
    Integrated the ESS applications on .net portal using soap adapter..example salary slip, ctcview....
    If we give input as empno to soap adapter it will give you salary details back to .net portal.
    All this functional;ity are working fine..
    Now i need to check the authorization to acess this soap request. As this webservice works for all the employess in the organazation. but i need to restrict for few employees. Is there any authorization check in XI as it is there in ESS.
    If so how to use that . Now in .net portal they are useing the same user name and pwd for all the soap requests.
    Regards
    Vijay
    Edited by: vijay Kumar on May 25, 2010 11:18 AM

    Michal
    Hopefully I can help you for once!
    You can set the SOAP action to debug in the Java Admin Console.
    Set com.sap.aii.af.mp.soap and com.sap.aii.messaging set to DEBUG
    Set location
    &#61680;     Services
    &#61680;     Log Configurator
    &#61680;     Locations
    &#61680;     Choose com.sap.aii.messaging
    &#61680;     Assign Severity Debug
    See https://service.sap.com/sap/support/notes/856597 for more info...
    This note has a an attachment: tcpgw.zip for tracing the whole message...

  • HTTP Header fields in SOAP adapter

    Hi All,
      I have a scenario IDoc to SOAP adapter. In which my receiver given the details as
    URL : https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
    Header Name:             Header Value
    Ent-sender                xxxx
    Ent-receiver              yyyyy
    Ent-APRF                 zzzzz
    Ent-filename             (not sure what data need to give)
    1. I request you to let me know where I need to give these headername and hader values in soap adapter. 
    2. my client require file as an attachment.  Please let me know how I need to send the payload as an file and where the name need to be given in the header name (Ent-filename).
    Currently I used  MessageTransformBean to conver my XML to text structure(flatfile structure).
    Please let me know if any more details required
    Regards,
    Dhill

    Was out for lunch break..
    Juz Rechecking
    Transport Protocol : HTTP
    Message Protocol: Soap 1.1
    Adapter Engine -> Adapter Engine on the Integration Server
    Connection Parameters
    Target URL - > https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
    Sure about no sever authentication required  and they are not using any HTTP proxy for webservice >????
    Conversion Parameters
    Do Not Use SOAP Envelope -> Unchecked
    Keep Headers -> Checked.
    Keep Attachments -> Unchecked
    Use Encoded Headers -> Unchecked
    Use Query String -> not so sure might be Unchecked
    <b>Authentication Keys</b>
    If authentication is required for the receiver system, you can enter a password and a confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.
    If you want to specify or display authentication keys, select View Authorization Keys.
    You can enter and confirm passwords for each authentication key value (TAuthKey or TproyxAuthKey).
    Try once sending the message with Adapter-Specific Message Attributes
    Unchecked. See if there is a hit.I knw itz not req but juz testing.
    Yeah adapter stat must be active.
    Last thing need to go through the whole scenario.
    <b>Cheers,
    *RAJ*
    *REWARD POINTS IF FOUND USEFULL*</b>

  • SOAP adapter in PI 7.1

    Hello, expert,
    I have made SOAP adpeter work in PI 7.0, however after upgrading to PI 7.1, I have issue with a test scenario as following.
    I've defined DT, MT and SI (Service Interface) in ESR (no mapping needed)
    In ID, I configured a scenario SOAP --> PI  --> File.
    I tested the scenario in RWB using the test tool for adapter engine using URL:
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_comp:CC_Notification_SOAP_Sender
    the message is attached in the end of this post.
    The message was successfully send to PI and saved to file, however the message going into IE pipeline and finally saved to the file is not the one I sent.
    Message sent to SOAP adapter:
    <?xml version="1.0" encoding="UTF-8"?>   
    <ns0:MT_Notification xmlns:ns0="http://mynamespace/xi">
       <Notification>
          <Number>12345</Number>
          <Type>abc</Type>
          <Status/>
          <OrderNo/>
          <FunctionalLocation>qaz</FunctionalLocation>
          <StartDate/>
          <EndDate/>
       </Notification>
    </ns0:MT_Notification>
    Message going into IE pipeline and further saved to file:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Inbound Message   -->
    <sap:Manifest xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink">
    <sap:Payload xlink:type="simple" xlink:href="cid:payload-29092409f6d11ddc4d982a0c41f100csap.com">
      <sap:Name>PayloadName</sap:Name>
      <sap:Description>PayloadDescription</sap:Description>
      <sap:Type>Application</sap:Type>
      </sap:Payload>
      </sap:Manifest>
    Also in sxmb_moni, there is a acknowledgement which do not expect.
    Does anybody have an idea how this happens?
    Thank you
    Jayson

    Hi!
    I want to answer this thread as 2 parts:
    1. First check all of your configuration whether you have done...correctly or not later please activate all of your objects...
    then try your Scenario once..if not do one thing..
    2:
    I my sugestion is Why don't you try yourr scenario by using either SOAP CLient Tool or else ALTOVA XML SPY TOOL...
    Here I am provding the Steps to be followed to use ALTOVA XML SPY Tool
    please make sure even though you have done correctly..
    Steps for Testing via ALTOVA>>
    1. Go to ID-> TOOLS-> Define Web Service
    2. Give following URL in following window
    For without Party:
    note: http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>
    3. Give Message Interface Name of Scenario
    4. Give following details in following screens  Service Name, Message Interface Name,   Namespace
    5. Finish & Save the WSDL in local folder to give to web-services
    (Generated WSDLu2019s attached in Technical Design Document)
    NOTE: AFter generating you can observe the above SOAP URL with your objects name...
    6.Once the WSDL file is created. Use a SOAP client tool or else aither ALTOVA XML SPY Tool  to create the SOAP request.
    You can create SOAP Request from WSDL using the following tool
    Once you have created the SOAP request, use the same as the payload and test the scenario.
    7. Select the option in the SEND SOAP REQuest in the MENU present in the top list of ALTOVA XML SPy Tool and give inputs i.e., SOAP URL and also give server details and it will ask authentification details
    8. Now by giving Authentification details you can send successfully....
    9. Now Got SXMB_MONI and now check your scenario is success or not..
    10. IF not go to MEssage monitoring in RWB and check at both the INtegration Server Level and ADAter engine level and then Check the AUDIT LOG
    11. ALso you can check Audit log in COmmunication channel monitoring
    12. If your SOAP Channel is in Red check Errors and then stop that channel manually and start once again and try the scenario once again...
    http://help.sap.com/saphelp_erp2004/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
    I hope it will be useful to you in final case...Suppose if it is useful to you please close this and award points to the repective contributors if it is useful to you..
    Regards:
    Amar Srinivas ELi

  • Error in Sender SOAP Adapter on XI 3.0 SP13

    Hi All.
    I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
    http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
    When I try to reach this URL, I get the successful response:
    <i>Message Servlet is in Status OK</i>
    I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
    However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
    <i>HTTP/1.1 500 Internal Server Error
    Connection: close
    Server: SAP J2EE Engine/6.40
    Content-Type: text/xml; charset=utf-8
    Date: Sat, 17 Sep 2005 02:59:12 GMT
    <?xml version='1.0'?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
      <SOAP:Body>
        <SOAP:Fault>
          <faultcode>SOAP:Server</faultcode>
          <faultstring>Server Error</faultstring>
          <detail>
            <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
              <context>XIAdapter</context>
              <code>BaseEJBException</code>
              <text><![CDATA[
    com.sap.aii.af.mp.processor.ModuleProcessorException
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
         at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
         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:159)
    Caused by: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
         ... 19 more
    Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
         ... 20 more
              ]]></text>
            </s:SystemError>
          </detail>
        </SOAP:Fault>
      </SOAP:Body>
    </SOAP:Envelope></i>
    I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
    Thanks in advance.
    Deise Lima.

    Hi Naveen,
    I have configured a SOAP sender adapter in XI 3.0 and is using the URL
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
    Message Servlet is in Status ERROR
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal not instantiated
    ModuleProcessorRemote not instantiated
    But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
    <?xml version="1.0" ?>
    http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
    <channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
    <name>CC_WEBSERVICE_SOAP</name>
    <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
    <direction>INBOUND</direction>
    <party />
    <service>BS_WEBSERVICE</service>
    </s:ChannelInfo
    I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy or Altova XML Spy we are getting a 500 internal server error.
    Am not sure what causes the error

  • SOAP Adapter in XI 3.0 (Central Engine, not J2SE Adapter)

    Hello,
    I am trying to get the demo (flight availablity check) work via SOAP, so that it can be called from .NET.   I created a communication channel with sender SOAP adapter (and adapter engine as Integration server, http://sap.com/xi/XI/Demo/Agency as interface namespace and FlightSeatAvailabilityQuery_Out as interface name)
    When I post it to XI
    http://xxxxxx:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=XX1_205&Interface=com.sap^FlightSeatAvailabilityQuery_Out&QualityOfService=BestEffort&ProcessingMode=p&MessageClass=RQ
    with soapaction http://sap.com/xi/WebService/soap1.1
    and
    <?xml version="1.0" encoding="utf-8" ?>
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
    <FlightSeatAvailabilityQuery xmlns="http://sap.com/sapexamples">
    <FlightID xmlns="">
      <AirlineID>LH</AirlineID>
      <FlightDate>2004-12-01</FlightDate>
      </FlightID>
      </FlightSeatAvailabilityQuery>
      </soap:Body>
      </soap:Envelope>
    I get just
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Body>
    </SOAP:Body>
    </SOAP:Envelope>
    Any idea why this does not work.  The plain HTTP adapter (to /sap/xi/adapter_plain) works ok.
    Thanks
    siva

    Post your message to following URL:
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    port is the J2EE port 50000 in your example.
    Check the newest manual for further details.
    Regards
    Stefan

  • 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

  • Security Issues: SSL on SOAP Adapter and Digital Signature in BPM

    Hi there,
    we're developing a R/3-XI-3rd Party Application scenario, where the XI/3rd Party communication is based on a webservice (SOAP adapter with SSL). Also, the messages in the XI/3rd Party communication must be digitally signed. I've got some questions on both subjects.
    1. About the SSL. I've started to investigate what will be necessary to enable the HTTPS option under SOAP Adapter (it's not enabled now). If I'm not correct, all I need to do is:
    - check whether the SAP Java Crypto Lib is installed in the Web AS;
    - generate the certificate request in the Visual Administrator and, after acquiring the certificate, store it with the KeyStorage option.
    Is that right?
    I'm considering that I won't need to use SSL in the ABAP Web AS, only the J2EE Java Engine (since the SOAP Adapter is based on J2EE).
    2. About the digital signature. As a first solution, we had decided on accessing a webservice based on another machine running a signature application. We'd send the unsigned XML and receive a signed XML. But since that needed to be done into the BPM, I thought that using a piece of Java code in a mapping would suit it better.
    But to be able to use the hashing/encrypting/encoding algorithms, which library needs to be installed? Is it the same SAP Java Crypto Lib that was installed for the SSL enabling?
    Thanks in advance!

    Hello Henrique,
    1. You're right. For detailed instructions please have a look at the online help: http://help.sap.com/nw04 - Security - Network and Transport Layer Security - Transport Layer Security on the SAP J2EE Engine
    2. The SOAP adapter supports security profiles. Please have a look at the online docu http://help.sap.com/nw04 -Process Integration - SAP Exchange Infrastructure - Runtime - Connectivty - Adapters - SOPA Adapter - Configuring the Sender SOAP adapter and from the link under Security Parameters to the Sender Agreement. You'll find some additional information in the following document: http://service.sap.com/~sapdownload/011000358700002767992005E/HowToMLSXI30_02_final.pdf
    Rgds.,
    Andreas

  • SOAP ACTION IN SOAP ADAPTER and PROGRAM  IF IN RFC COMMUNICATION CHANNEL

    Hi Gurus,
    Please Explain me what is SOAP action in soap adapter what is the use of it.
    What is the Program ID in the RFC communication channel and what is the use of it.
    Please tell me in  Detail.
    Thanks and Regards,
    RAM.

    Hi,
    Please Explain me what is SOAP action in soap adapter what is the use of it.
    As of W3C definition:
    The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request.
    The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.
    Putting things simple, this is an identifier of an operation that you want to execute in the web service (as one web service can offer multiple actions).
    What is the Program ID in the RFC communication channel and what is the use of it.
    Again, this is an identifier for both: RFC sender and receiver systems. It tells the receiver where to listen for connections, and the sender - where to send the data. It works a little bit like a port number in HTTP communication, but with less restrictions.
    Hope this helps,
    Greg

  • SOAP Adapter - Using Fault Message

    Hi all,
    I have developed a Synchronous Integration Scenario which receives a SOAP request to the SOAP adapter, calls an ABAP proxy in SAP ECC to post some information and return a response or a fault to the sender.
    This all works fine, I am using a fault message in the ABAP proxy to record errors and return them to the SOAP adapter using the fault mapping. Again this all works fine. However when an application error is identified and a fault message returned to thre SOAP adapter, I had expected that the error details in the fault message to be packaged up in a standard SOAP fault and returned to the sender. Instead the fault message details are sent as the payload in the SOAP body of the response.
    Can anyone provide information on if it is possible to return the fault message as a standard SOAP fault instead of in the SOAP body of the response.
    Thanks
    Gary

    Dont think this is possible in standard.
    As an alternate, maybe you can select option Do not use SOAP Enevlope int he sender SOAP Adapter and thereby the entire SOAP Message will enter the mapping and you would need to use a XSL or Java  mapping to strip the SOAP Envlope in the mapping for the request and like wise in the response mapping you would need to add the SOAP Enevlope to the response.
    For the fault message mapping you need not add the SOAP Envelope.
    Not a standard solution, but can be tried if the requirement is really worth it. Otherwise I think the Fault Message will continue to be sent as the payload in the the SOAP Enevlope as this is how the SOAP adapter works.
    Regards
    Bhavesh

  • SOAP Adapter Sender PI7.1: 400 Bad HTTP request

    Hello,
    I have a problem with a SOAP adapter sender communication channel.
    I'm trying to migrate a scenario from XI 3.0 to PI7.1 SP6 (PI_BASIS 2006_1_710 SAPKIPYN06).
    I can send messages successfully to the old system using the URL
        http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_Name:CC_SOAP_Sender
    On PI7.1 I get
        400 Bad HTTP request
        Error: -21
        Version: 7010
        Component: HTTP_PLG
        Module: http_plgrt_mt.c
        Line: 5226
        Error Tag:
        Detail: illegal request version
    I have created a Sender Agreement, generated the wsdl from that and tried the URL in there.
    Surprisingly it has the old format, namely
        http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_Name&receiverParty=&receiverService=&interface=myInterface&interfaceNamespace=urn:my.Interface:ns
    although the 7.1 documentation describes the ?channel=party:service:channel style only.
    Anyway, the result remains the same.
    I tried some other approaches like escaping the colons in the URL without success.
    The user has the role SAP_XI_DEVELOPER_J2EE assigned.
    Any idea what's wrong here?
    Thanks in advance
    Rainer

    >>In RWB the channel appears as "started but inactive".
    Yeah,it will be like that because you are posting messages directly to Integration server."Propose URL" does that.You are bypassing the adapter engine when you use the URL generated by "Propose URL" button.
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    The above blog gives the reason for this,if you want to bypass the adapter engine,then generate the URL as given in the above blog
    /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    This blog explains how to post message to adapter engine,here you need to change the URL,don't click on "Propose URL" button.You can monitor SOAP adapter in RWB only if you generate the URL as given in second blog
    The URL which is working for you in XI 3.0 is posting messages to adapter engine,so generate the URL in PI 7.1 in the same way,by following the second blog i have mentioned.
    Thanks
    Aamir

  • SOAP adapter in XI3.0 using J2EE adapter engine

    Folks,
    I have a scenario SOAP client -> XI 3.0
    I am using XI 3.0 and the J2EE adapter framework to configure a sender SOAP adapter. I do not have a Party, just the service and the channel.
    I tried using the following url format:
    http://<server>:50000/XISOAPAdapter/MessageServlet?channel
    =:<service name>:<channel name>
    When I use this in my SOAP client , I get an 401 forbidden error in the browser. However when I type this url directly in the browser and I get:
    Message Servlet is in Status OK
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0
    ModuleProcessorRemote not instantiated
    A couple of questions:
    1. Inspite of configuring the sender SOAP adapter, the sender service and the interface, I still cannot see the green light for the SOAP adapter in rumtime workbench->adapter monitoring.
    Although the communication channel (in intergration builder- design)shows the status of the adapter as "active"
    Does this mean that my SOAP adapter is correctly configured and active?
    2. The above mentioned url takes the ABAP engine login/password while the J2EE engine (AFW)takes a different login/password. Which authentication should the SOAP client use?
    Thanks for your help!
    Shailesh

    Post your message to following URL:
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    port is the J2EE port 50000 in your example.
    Check the newest manual for further details.
    Regards
    Stefan

  • Error in connecting to sender soap adapter

    Hi ,
    I am trying to ping the soap adapter from the browser using the URL
    http://<host>:50000/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:SIEBEL_DEV:CC_SOAP_CUST
    but getting the following error
    <b> <?xml version="1.0" ?>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
    - <detail>
    - <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
      <context>XIAdapter</context>
      <code>ADAPTER.SOAP_EXCEPTION</code>
    - <text>
    - <![CDATA[
    java.lang.Exception: Channel not found for :SIEBEL_DEV:CC_SOAP_CUST in SOAP
         at com.sap.aii.af.mp.soap.web.HelperServlet.processFindChannel(HelperServlet.java:420)
         at com.sap.aii.af.mp.soap.web.HelperServlet.doGet(HelperServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
      ]]>
      </text>
      </s:SystemError>
      </detail>
      </SOAP:Fault></b>
    To me it seems that the error has something to do with :SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0 .
    is it pointing to version 2.0 of XI . whereas we are on 3.0.
    I even chacked the meta data in repository and there also the version for SOAP adapter is 3.0
    If someone has any solution or suggestions for this error it wil be a great help
    Thanks
    Nikhil

    HI,
    What about other Adapters ? Are they are ok?
    <i>channel not found.</i>
    >>https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
    Regards,
    Moorthy

  • How to make PI 7.0 soap adapter support SOAP 1.2

    hi all:
    Is there some idea make PI 7.0 soap adapter support SOAP 1.2?
    I have look the document about soap adapter,and it specified that soap adapter only support SOAP 1.1.
    http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm.
    my scenario:
    external system send message via soap 1.2 to xi.

    for more detail about axis soap adapters refer this link[http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm]

Maybe you are looking for

  • OS 10.4.6 and display connector

    In March I got a G4 Mini to replace my old Mac. In the formidable process of getting all my functions to work on the Mini, I would have to swap computers several times, so I did not screw the connector from my monitor to the adapter on the Mini. In a

  • Wi-fi connection

    I am trying to connect to my home wireless router.  When I put in the password for the router, my phone just blinks back & forth that it is trying to connect.  My husband's phone has not problem connecting and I am wondering if there is a problem wit

  • How do i scroll a list within a window ( such as a safari page) on the ipaf?

    On some pages i navigate to, there is a scrollable frame insude the window. Whe  i try to scroll, the entire window moves.  Is there a way to "anchor" the main window so the interior frme can be scrolled?

  • Import settings to new account

    Hi guys, my main Win 7 user account has become corrupted, giving me the loop of "Windows Explorer has stopped working and is restarting". I've created a new user account and am now beginning the process of reinstalling all my software and profiles. I

  • 2010 Disable circular logging with no storage groups

    I have SBS 2008 and the backup wizard will not complete because of the error Disable circular logging in Exchange. I had previously removed most of exchange because of disk space including the databases. So there are no storage groups to remove them