SOAP Adapter - Guaranteed delivery

Hi ppl,
I have a requirment where we are exploring the possibility of the source system being able to expose its data in http format so that we can get use XI SOAP adapter to get the same over https. As SOAP adapter would access the data through WAN, what would happen to the data if the WAN is broken? How does the guaranteed delivery work in case of SOAP adapter?

>
Ethan Hunt wrote:
> thanks for your reply. For inbound messages, how will the data be recieved by SOAP adapter in case of broken WAN. If the source system is exposing the data once in every minute and the WAN is broken for 10 min, when it comes up again, will SOAP adapter recieve all the messages sent by the source system during the connectivity failure? I am not sure how the expose of data in http format works.
From your comments, it seems that the source system acts as a client, and PI (SOAP Adapter) will receive the data from the client.
You can configure the "Quality of Service" of the sender soap adapter with 3 possible options:
- Exactly once (async)
- Exactly once in order (async)
- Best effort (synchronous)
In the first two cases, your client will get an HTTP 200 response (with an empy SOAP message), while in the last case it will get as a response the message you have configured in PI. Take into account that in the first two cases, even if there is an internal error in PI (mapping error for example) your SOAP adapter will still have delivered an HTTP 200 response, as the SOAP adapter did its mission (received the message and delivered it to the Integration Server).
If the client can't reach PI, it won't get an HTTP 200, it will get an HTTP 500 or other error code, so it's your client responsability to retry sending the message until it gets the proper response.
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Edited by: Jorge Lopez on Jul 13, 2009 3:20 PM

Similar Messages

  • SOAP over JMS and Guaranteed Delivery

    How to I configure a Web Service that uses the JMS Transport, and has guaranteed
    delivery messaging? In other words, how do I configure the Web Service so that
    when the Client invokes the Web Service, if the implementation of the Web Service
    (such as a stateless session bean) is down, that the message will sit on the JMS
    queue until the Web Service becomes available again? Am I supposed to use reliable
    SOAP Messaging, or am I supposed to use “document” instead of “rpc” as the style
    of the Web Service? Thank you.

    Hello,
    Also see this example [1] and for extra credit :-) give the secure RM
    example a spin.
    HTH,
    Bruce
    [1]
    http://webservice.bea.com/reliable.zip
    [2]
    http://webservice.bea.com/secureRM.zip
    David Karr wrote:
    >
    I haven't done this, but I was in the middle of reading the "Programming WebLogic
    Web Services" manual, so I'm somewhat familiar with this.
    It appears that the configuration for using a JMS transport is somewhat independent
    of reliable delivery (it's funny they call it "reliable" and not "guaranteed").
    Using reliable delivery requires configuration of a JMS store on both the the
    receiver and sender. If I were you, I'd completely read chapters 9 and 10 of
    the aforementioned manual. Assuming all the instructions are correct, it seems
    detailed enough.
    Please tell us whether you get this to work.
    "Ethan Henderson" <[email protected]> wrote:
    How to I configure a Web Service that uses the JMS Transport, and has
    guaranteed
    delivery messaging? In other words, how do I configure the Web Service
    so that
    when the Client invokes the Web Service, if the implementation of the
    Web Service
    (such as a stateless session bean) is down, that the message will sit
    on the JMS
    queue until the Web Service becomes available again? Am I supposed to
    use reliable
    SOAP Messaging, or am I supposed to use “document” instead of “rpc” as
    the style
    of the Web Service? Thank you.

  • Sender Axis SOAP Adapter EOIO

    My PI Sender Axis SOAP Adapter is giving me the following error when I try and use an EOIO quality of service:
    The XI SequenceId must be uppercase and 1-16 characters long.; nested exception is:
    com.sap.engine.interfaces.messaging.api.exception.InvalidParamException: The XI SequenceId must be uppercase and 1-16 characters long.
    If I use EO then the adapter works fine. Does anyone know if EOIO is supported in the Sender Axis SOAP Adapter? I did notice when I select EOIO there is no text box for the Queue Name.

    Hi Krishneel,
    ExactlyOnceInOrder means that the constructed XI message has its QualityOfService value ExactlyOnceInOrder and it is processed synchronously to the persistence layer of the adapter engine and asynchronously to the target service in the order of persistence.
    To guarantee the exactly once delivery of a message, the client must supply a unique message ID for the message.
    More on this can be found in the SAP Note 1039369 (FAQ XI Axis Adapter)
    Also refer this link on basic info on Sender Axis SOAP Adapter.
    http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
    rgds
    Ven

  • SOAP Adapter Java Null Pointer, Receiver receive mutiple times of message

    Hi,
    My scenario is Proxy -> PI 7.1 -> Soap receiver.
    The scenario was working before , and recently we got System Fails in adapter:
    ********************Adapter Audit Log****************************
    2010-01-11 10:41:16 Information The message was successfully received by the messaging system. Protocol: XI URL: http://hdrpidev01.bchydro.bc.ca:51100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2010-01-11 10:41:16 Information Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2010-01-11 10:41:16 Information Message successfully put into the queue.
    2010-01-11 10:41:16 Information The message was successfully retrieved from the receive queue.
    2010-01-11 10:41:16 Information The message status was set to DLNG.
    2010-01-11 10:41:16 Information Delivering to channel: ESB_CostCenter_SOAP_Receiver
    2010-01-11 10:41:16 Information SOAP: request message entering the adapter with user J2EE_GUEST
    2010-01-11 10:41:16 Information SOAP: completed the processing
    2010-01-11 10:41:16 Information SOAP: sending a delivery ack ...
    2010-01-11 10:41:16 Information SOAP: sent a delivery ack
    2010-01-11 10:41:16 Error Adapter Framework caught exception: null
    2010-01-11 10:41:16 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException.
    2010-01-11 10:41:16 Information The message status was set to WAIT.
    2010-01-11 10:41:16 Information The asynchronous message was successfully scheduled to be delivered at Mon Jan 11 10:46:16 PST 2010. .....
    The log has another three reties which I did not listed above.
    The question is that the receiver system received the message and received 4 times.
    I future go to the je22 engine log viewer, then I got following error message :
    ********************J2EE Log Viewer****************************
    Message:
    Marked transaction for rollback for meesage 4b47ad05-9df9-0176-e100-8000ac190651(INBOUND). Reason: java.lang.NullPointerException
    Date: 2010-01-11
    Time: 10:41:09:732
    Category: com.sap.engine.messaging.impl.core.queue.consumer.ReceiveConsumer
    Location:
    com.sap.engine.messaging.impl.core.queue.consumer.ReceiveConsumer.invokeHandler(QueueMessage, MessageController)
    Application:Thread: MS Queue Worker [SOAP_http://sap.com/xi/XI/SystemRecv]
    Data Source:
    j2ee/cluster/server0/log/defaultTrace_00.trc
    Arguments:
    DSR Transaction: 0f3437c0fcc911de826200145ec71b45
    Message Code: 
    Session: 0
    Transaction: SAP J2EE Engine JTA Transaction : [6ffffffab3c2602ffffffa564]
    User: J2EE_GUEST
    Time Zone: 0-800
    CSN Component: BC-XI-CON-MSG
    DC Component: com.sap.aii.af.ms.svc
    Correlation ID: 111885350000000004
    DSR Root Context ID: 0F3437C0FCC911DE826200145EC71B45
    DSR Connection: 0f3437c0fcc911de826200145ec71b45
    DSR Counter: 0
    Log ID: 00145EC71B45510B0000000100137042
    Host: hdrpidev01
    System: DI1
    Instance: DVEBMGS11
    Node: server0
    ********************End of J2EE Log Viewer****************************
    We never came cross the situation of sending mutiple message out while there is system error in adapter.
    Any ideas and comments ?
    Thanks in advance
    Liang

    Solved by creating new adapter.

  • 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

  • Error in applying security settings in Receiver SOAP Adapter

    Hi,
    I've used Web Services Security (Oasis standard) and the digital signature and encryption certificate in receiver SOAP adapter and the corresponding Sender Agreement, for adding digital signature and encrypting the message. While sending the message we are getting an error in the adapter engine as below. If anyone can throw light on this it'll be highly appreciated :
    2008-07-18 17:00:21 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run().. To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run()..
    2008-07-18 17:00:21 Error Exception caught by adapter framework: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii
    2008-07-18 17:00:21 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: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXExce.
    Thanks,
    Dipankar

    hi dipanker,
    check the note 856597
    its usefull
    regards
    kummari

  • Error in Adapter engine of receiver soap adapter

    Hi All,
    There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
    Below is the description i am getting in audit logs.
    Success SOAP: completed the processing
    Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
    Success SOAP: sending a delivery error ack ...
    Success SOAP: sent a delivery error ack
    Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
    Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
    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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
    Error The message status set to NDLV.
    Moreover this is a production issue and  interface was running fine till last friday.
    Has someone ever faced this issue ?
    Please provide your valuable inputs on this.
    Thanks
    Anku

    Hi,
    Search in sdn with your error message string,you will find ton of links.
    HTTP401 error occurs for many reasons.
    still no solution let us know..
    Regards,
    Raj

  • SOAP adapter engine with system error, problem with fault message.

    HI,
    I have IDOC -> PI -> SOAP scenario.
    Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
    The error is at PI -> SOAP.
    I have wsdl provided by the receiver webservice. Which I have imported.
    And created a service interface against this wsdl. I tried changing it to both sync and async.
    I have also provided fault message.
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
    action = processDocument. Also provided user id and password.
    I have a
    Sender Agreement
    Receiver determination
    Interface determination
    Receiver Agreement
    I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
    When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
    with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
    How does the receiver know which service interface is it? The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
    Service interface name which I created in the  ER. Where in the document the Reciever interface name is sent?
    Where can I see the generated soap document for the receiver?
    Is there some setting/configuration required in PI for this to work?
    I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
    then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
    When I provide the service interface name in the communication channel I get a valid fault message.
    Similarly
    When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
    instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
    The fault message what I see in SOAPUI has the below format.
    <soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
             <faultcode>axis2ns1:Server</faultcode>
             <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                                database default values were set. See the associated message for more information.
               BMXAA4190E - Country NZ is not in the value list.</faultstring>
             <detail>
                <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                          - Validation failed when the database default values were set. See the associated message for more information.
         BMXAA4190E - Country NZ is not in the value list.
                /Exception>
             </detail>
      </soapenv:Fault>
    And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
    the above. Is this the problem? Can I change the data type here to be the same as above?
    Audit log in the RWB adapter engine.
    Time Stamp Type Description
    30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
    30.09.2011 15:10:57 Information SOAP: completed the processing
    30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
    30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
    30.09.2011 15:10:57 Error MP: exception caught with cause
    com.sap.engine.interfaces.messaging.api.exception.MessagingException
    30.09.2011 15:10:57 Error Adapter Framework caught exception: null
    30.09.2011 15:10:57 Error Delivering the message to the application using connection
    SOAP_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    30.09.2011 15:10:57 Information The message status was set to WAIT.
    30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
    15:15:57 NZDT 2011.

    I tried changing it to both sync and async.
    I have also provided fault message.
    dont feel that you need to do above steps.
    I have a
    Sender Agreement
    ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
    When I see the message content, the SOap document shows me the details about IDOC
    this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
    How does the receiver know which service interface is it?
    receiver need not know about the SI created in PI.
    The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same?
    you should the WSDL (external definition) as the Request Message in your service interface.
    Is there some setting/configuration required in PI for this to work?
    nothing specific...AFAIK
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
    can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
    Things to check:
    WSDL structure in PI and in target system is exactly the same.
    does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
    target system is up and running?

  • Problems with Soap Adapter

    Hi!
    I need to implement the following scenario:
    In SAP an user exit calls an RFC which uses a TCP/IP Connection (SM59) to the XI and sends data over this connection to it. The XI connects via a SOAP adapter my server program and sends the data in a soap stream to this server.
    This works sometimes ok and sometimes not.
    The status for those messages in the XI is "scheduled for outbound processing" with a little black arrow pointing to the right.
    The error message in the Runtime Workbench for such a job is:
    SOAP: request message entering the adapter
    SOAP: call failed
    SOAP: sending a delivery error ack ...
    SOAP: sent a delivery error ack
    How can I find out what the problem is?
    Thanks,
    Konrad

    Hi,
    When a message is scheduled for outbound processing, it is normally sent automatically.
    does it always sit at this status or does it change after a while ?
    If it is an issue with the connectivity from the Integration Server to the Adapter Framework you would get a different error message.
    If it is an issue with connectivity from the SOAP adapter to your target, you would also get a different error - it is likely to be shown as an outright failure. Plus the error shown in the message is likely to be
    "com.sap.aii.af.ra.ms.api.DeliveryException: java.net.ConnectException: Connection refused"
    Hope this helps.
    i think you need to get Basis involved to see why messages are not getting sent from the rfc queues automatically all the time.
    Cheers
    Colin.

  • SOAP adapter Module Issue

    Hi,
    i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
    now the issue is while execute teh scenario, it works fine at DEV but shows error at QA as given below
    "Delivery exception: Object not found in Lookup of Replace XML tag"
    please let me know how to resolve this issue.
    Thanks in advance....

    > i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
    > "Delivery exception: Object not found in Lookup of Replace XML tag"
    Have you spelled this correct? The name in the error message seems to be different from th module name.

  • Receiver SOAP Adapter Problem-HTTP 401 Unauthorized

    We are using XI-7.0. We have scenario IDOC >> XI >> SOAP by making asynchornous call.
    Vendor has two web server - A and B. Both the servers set up are identical in the vendor system.
    Web server "A" works fine from XML spy tool as well as XI for sending service order SOAP messages.
    Web server "B", we are able to send SOAP messages from XML spy successfully and vendor also confirms that it updates database in their system.
    But we are not able to send SOAP messages from XI on Server "B". We are getting following error message in the adpter engine.
    Can someone please help me?   Thanks!
    <i>SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
    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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized.</i>
    Thanks!
    MP

    Hi Riya,
    For SSL configuration you can check,
    Rajendra's blog http://scn.sap.com/people/rajendra.badi/blog/2011/11/23/pi-711-transport-level-secuirty-communicating-with-external-web-service-from-soap-adapter-through-ssl
    Khade's blog http://scn.sap.com/people/s.khade/blog/2011/09/06/secured-connection-to-external-web-service-using-sap-xipi.
    Regards.

  • SOAP adapter error: invalid content type for SOAP: TEXT/HTML.

    Dear SAP experts,
    Need your help again here.
    Currently, i am getting this specific error in my RWB logs.
    The connection is from SAP XI going to Trading Partner via SOAP adapter.
    The specific error is:
    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: java.io.IOException: invalid content type for SOAP: TEXT/HTML.
    I've already searched on what is causing the issue and it seems majority of the information is that, the error might be due to incorrect/wrong URL that was set in the configurations in the SAP XI communication channel.
    Can you confirm this one?
    DO you have any thoughts on this error?
    Please help.
    Thank you very much!
    Fred

    Hi Freddiesan,
    First of all, test your URL acessing it from SAP PI server's local browser to check firewall and router settings.
    If it works, check these blogs:
    Regards,
    Rogério
    Edited by: Rogério Tambellini on Jul 3, 2009 12:52 PM

  • Urgent ---- SOAP Adapter

    Hai,
    The scenario that we are working now is <b>IDOC-XI-SOAP</b>.
    We are having problem at SOAP Adapter.
    SOAP Adapter Receiver configurations:
    TargetUrl : .net webservice
    proxy settings : done
    soap action : given
    In the audit log error code is : General Error
    giving error that : soap call failed
    any inputs would be highly appreciated.
    Thanks
    Sri Krishna Charan

    Hai All,
    <b>
    How can i check whether my .net webservice is accessible or not in xi server....
    bcause xi server is runnig on remote host</b>
    Audit log information in message monitor is:
    Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
    Success Using connection AFW. Trying to put the message into the receive queue.
    Success Message successfully put into the queue.
    Success The message was successfully retrieved from the receive queue.
    Success The message status set to DLNG.
    Success Delivering to channel: TEST_VONDELSOAP_DEMO
    Success SOAP: request message entering the adapter
    Success SOAP: call failed
    Success SOAP: sending a delivery error ack ...
    Success SOAP: sent a delivery error ack

  • SOAP adapter - WS authorization

    Hello,
    I am trying to expose an RFC as a web service using the SOAP Adapter.
    The problem is that in order to consume this web service, authorization is required by the client application(Otherwise the call returns code 401 - Unauthorized)
    Is it possible to allow anonymous calls to the WS ?
    If not, can anyone instruct me how to provide authorization data during the call to the WS (using C#) ?
    Thanks,
    Elad.

    Hi,
    From the thread , <u><b>User Names and Passwords in SOAP adapter
    <i>in order to turn off the authentication for SOAP interface, please remove the authentication
    restriction in web.xml for aii_af_soapadapter.sda.
    Extract the SOAP-adapters WAR-file from the corresponding sda. Then extract the deployment-descriptor from the war-file and delete the related security-constraint, login-config and security-role sections (makes absolutely sense to save the original descriptor beforehand). ZIP the files again with the new deployment descriptor and deploy the SDA via SDM.
    comment the following portion.( It's already commented below).
    <! security-constraint >
    <><security-constraint>
    <display-name>message</display-name>
    <web-resource-collection>
    <web-resource-name>message</web-resource-name>
    <url-pattern>MessageServlet</url-pattern>
    </web-resource-collection>
    <auth-constraint>
    <role-name>xi_adapter_soap_message</role-name>
    </auth-constraint>
    </security-constraint>
    <security-constraint>
    <display-name>helper</display-name>
    <web-resource-collection>
    <web-resource-name>helper</web-resource-name>
    <url-pattern>HelperServlet</url-pattern>
    </web-resource-collection>
    <auth-constraint>
    <role-name>xi_adapter_soap_helper</role-name>
    </auth-constraint>
    </security-constraint>
    >
    <! login-config >
    <><login-config>
    <auth-method>BASIC</auth-method>
    <realm-name>XISOAPApps</realm-name>
    </login-config>
    >
    <! security-role >
    <><security-role>
    <role-name>xi_adapter_soap_message</role-name>
    </security-role>
    <security-role>
    <role-name>xi_adapter_soap_helper</role-name>
    </security-role>
    >
    The safest way to change this web.xml is described as followed, you
    could do the changes also direct on the file system, but it will need
    reboot of J2EE and does not guarantee to work.
    The web.xml is located in the aii_af_soapadapter.sda, please extract
    this sda file with normal zip function. There is one
    aii_af_soapadapter.war inside, please extract this war file again,
    change the web.xml as described above. Please zip the folder with
    modified web.xml for aii_af_soapadapter.war and than for the
    aii_af_soapadapter.sda. Please do not modify the folder structure.
    Deploy this modified sda with SDM. After the deployment you can double
    check whether changes for web.xml is done on the file system, this
    web.xml is located under
    /usr/sap/xxx/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap
    .aii.af.soapadapter/servlet_jsp/XISOAPAdapter/root/WEB-INF.
    I am not sure whether you will need to restart the J2EE after this
    deployment to make the changes from web.xml active, please try it out.</i>
    Regards,
    Bhavesh

Maybe you are looking for

  • Deactivate an Enhancement to a standard program

    Dear all, I'm facing the following problem. Our programmer apply an Enhancement to to a standard FI program. Now I would to deactivete this Enhancement: what is the t-code that allow me to do this? Sap Version: ECC 6.0 Thanks in advance Alberto

  • File path selected by the user!!! (File Download)

    Hi, Does exist a component, code line or any thing which emulate the Windows option <b>SAVE AS:</b> when the user does right click, but using a button to do this? If somebody knows? I will appreciate it. Thanks in advance!!! Tokio Franco Chang

  • Empty Objectlist in ABAP Workbench (Trial version) after installation

    Hi, In ABAP Workbench/Object Navigator I (BCUSER) don't see the dropdown control (object list). The slot containing the objects is empty and disabled. The system state is after new installation of the Trial version without any problems or errors, no

  • Screen Programming * removed_by_moderator *

    Hi everyone, I'm very new for screen programming in OOP's . Can any one tell me how to implement the screens in our report? plz tel me how to write attributes, element list and flow logic and also how the flow logic is implemented using layout? give

  • Emergency help please

    MX2004 closes down after error message. "Cache file missing or corrupt and will be recreated". Isn't there a certain file I can find and delete, and DW will create a new file? Assistance will really be appreciated.