HTTPS config in SOAP receiver adapter ?

Hi Guys,
I have configured the soap receiver adapter with the URL
*https://xxxx.abcd.com/xyzv/bbbb.asmx with the user  authentication *
I have tested the url and the user and pw in the browser and they are working fine but the messages are failing the soap receiver adapter with the 401 unautorized error as the message from the Audit log in the RWB.
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: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized. Setting message to status failed.
Do i need to configure the Java Stack for HTTPS ? The communicaion is between the XI system and a third part system internally.
any help would be appreciated ?
Thanks,
Srini

Hi Guys,
I have solved the problem and NTLM works with PI 7.0 but we need to configure soap axis adapter
The Windows NTLM authentication is supported by Axis's CommonsHTTPSender handler and consequently it is supported by the Axis adapter's corresponding handler com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender. Read about How Can I use CommonsHTTPSender as the transport handler? if CommonsHTTPSender is not enabled on your system. Once it is enabled, you can use com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender instead of default com.sap.aii.adapter.axis.ra.transport.http.HTTPSender as the transport handler in the module configuration and set the authentication setting to NTLM and enter usename as domain\username in the channel configuration
To use CommonsHTTPHandler, the optional Jakarta-Commons-Net, Jakarta-Commons-HttpClient, Jakarta-Commons-Codec libraries are required. Make sure that these libraries are available for the Axis adapter at the deployment check page  If these components are not available, you will need to include the corresponding jar files (commons-codec-1.3.jar, commons-httpclient-3.0.jar, and commons-net-1.0.0-dev.jar from the Axis 1.4 release) in aii_af_axisprovider.sda and deploy this archive (see How to prepare aii_af_axisprovider.sda?).
The provider.xml file must include the jar-name entries for these jar files, as shown in:
    <jars>
       <jar-name>commons-net-1.0.0-dev.jar</jar-name>
       <jar-name>commons-codec-1.3.jar</jar-name>
       <jar-name>commons-httpclient-3.0.jar</jar-name>
    </jars>
Once you do all the above settings, NTLM works fine
Thanks,
Srini

Similar Messages

  • Enable communication HTTPS in SOAP Receiver Adapter

    Hi gurus,
    I have configured the soap receiver adapter with the URL:
    "https://www.xxxx.com/yyyyyyyyyy.asmx" without the user authentication.
    I have executed the webservice since SOAP-UI and works well. But if I run the webservice from SAP XI does not work. In the transaction SXMB_MONI shows the following error:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection closed by remote host.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>"
    What is happening?
    Thanks,
    Jose.

    Jose,
    client certificate is the "top" authentication mechanism during SSL handshake, like this :
    - XI authenticate the SSL certificate (server) issued by target server against a (trusted) list of known certification authority, then target will ask XI to present its own certificate (client) and it will make sure this client certificate can be trusted (verifying it has been certified by a known authority). Handshake is "done"
    but you can also have
    - "anonymous" mode (XI will make sure SSL cert provided by the target has been issued - and so can be trusted - by a (well)known certification authority), that's it. Target does not expected any other security feature
    - user/pwd over a SSL connection (like above, but you'll also have to provide a user and pwd for authentication at target level)
    Hope this helps
    Chris

  • Soap receiver adapter exception

    Hi,
    I am using SOAP receiver adapter to access a web service that is hosted on SAP Web AS (in this case it is the integration server Web AS). I use the web services navigator to test the web service and the web service works fine. The name of the web service is 'RemoteCrossReferenceProcessor' and it has one operation 'crossReference'.
    But with the soap adapter, I am getting OperationNotFoundException in the logs and my web service is not getting accessed. Here is the server log:
    <u><i>An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:RemoteCrossReferenceProcessor'; Key name:'SoapRequestWrapper' key value:'crossReference'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
    #1.5#0003BA0FF9EA0022000000840000688D0003F9349A3C2D61#1118429251382#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######b40aca80d9be11d994360003ba0ff9ea#SAPEngine_System_Thread[impl:5]_47##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:#http://sapsand1:8000/sap/xi/engine?type=entry#</i></u>
    Here is adapter configuration:
    Transport Protocol:HTTP
    Message Protocol:SOAP 1.1
    Adapter Engine:Integration Engine
    Target URL: http://<server_name>>:50000/RemoteCrossReferenceProcessor/Config?style=document
    User:
    Password:
    Default SOAP Action:
    I imported the WSDL into the external definition and used the messages from the WSDL for defining my interface mappings.
    I am using XI 3.0 SR1 (SP 09).
    I am out of ideas as to why the SOAP adapter is not calling my web service. Please help me with your suggestions.
    Thanks and Regards.

    HI Dani,
    I was looking for this error and I found this post AXIS SOAP Receiver. This post says about other errors, but sugests many ideas to found the soluction, like:
    1- non-deployed all AXIS jars; (but in this case it deployed all)
    2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).
    3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".
    By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.
    I hope this helps,
    Romerito Silva

  • SOAP receiver adapter digest authentization

    Hallo,
    I have scenario with SOAP receiver adapter configured as follow:
    Adapter Type: SOAP
    Transport Protocol: HTTP
    Message Protocol: SOAP 1.1
    Adapter Engine: Integration Serer
    Target URL: http://localhost:8099/webservices/test_v1_1_2
    Configure User Authentication
    User: ****
    Pasword:****
    but WS need digest HTTP authentication and SOAP adapter send in header Authentication: Basic.
    Hou can I change authentication method for SOAP protocol?
    Thx

    Hallo,
    I solved this problem by using AXIS framework. I hope that this short instruction help to someone.
    1. In SOAP receiver CC you have to set up Transport Protocol to HTTP(AXIS) and Message protocol to AXIS
    2. Now you can switch Authentication to Digest (NOW adapter will still send Basic!!!  Digest Authorization is Supported only by the following handler: com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
    3. On Module tabs in section Module configuration change type HTTPSender to CommonHTTPSender:
         (trp  handler.type  java:com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
    4. Save and Activate
    Before you start to use AXIS framefork you have to deploy necessary library.
    This thread help:
    Re: How to install SOAP Axis adapter and where is it available  ??
    Be carefull, for digest authorization you have to linked Optional library "Jakarta-Commons HttpClient" too.
    Good luck.
    JK

  • Soap Receiver Adapter Error. Pls advice urgent

    Hi All,
    While using Soap Receiver Adapter for synchronous communication
    *My Soap Request is:*
    <?xml version="1.0" encoding="UTF-8" ?>
    <ns1:SendMessage xmlns:ns1="urn:MMWebSrvService">
    <strFrom>XI</strFrom>
    </ns1:SendMessage>
    *My Soap Response from server is:*
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!-- Inbound Message
    -->
    <tns:SendMessageResponse xmlns:tns="urn:MMWebSrvService" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <return xsi:type="xsd:int">-1</return>
    <strErrorDescription xsi:type="xsd:string">String reference not set to an instance of a String. Parameter name: s</strErrorDescription>
    </tns:SendMessageResponse>
    How to resolve the error.
    Regards

    Henry,
    Your xml message is not xsd compliant...see if you can generate a xml message using your wsdl with random values, compare that to your imcoming msg..and thats your issue..
    Hope that helps
    Regards
    Ravi Raman
    Reward points if helpful !

  • SOAP Receiver adapter error. SOAP CALL Failed

    Hi ,
        I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
    SOAP: call failed
    SOAP: error occured: java.net.ConnectException: Connection timed out
    Message log is as below.
    Any clue ?
    Thanks & Regards,
    Mathew
    2005-10-31 18:59:58
    Success
    output
    1130810398454
    The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
    2005-10-31 18:59:58
    Success
    output
    1130810398458
    Using connection AFW. Trying to put the message into the request queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398458
    Message successfully put into the queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398459
    The message was successfully retrieved from the request queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398459
    The message status set to DLNG.
    2005-10-31 18:59:58
    Success
    output
    1130810398460
    Delivering to channel: CC_CALCULATOR
    2005-10-31 18:59:58
    Success
    output
    1130810398564
    SOAP: request message entering the adapter
    2005-10-31 19:03:07
    Success
    output
    1130810587497
    SOAP: call failed
    2005-10-31 19:03:07
    Error
    output
    1130810587497
    SOAP: error occured: java.net.ConnectException: Connection timed out
    2005-10-31 19:03:07
    Error
    output
    1130810587498
    Exception caught by adapter framework: Connection timed out

    Hi Mathew,
    Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
    Prasad

  • SOAP receiver adapter for Axis

    Hi,
    I used SOAP receiver adapter for Axis  like below:
    Transport Prorocol : HTTP
    Message Protocol : Axis
    Url: http://<IP>:<Port>/xxx/WebService/services/Head/yyy
    Authentication : Basic
    User: <user>
    Password: <password>
    SOAP Version : 1.1
    SOAP Action: : <method>
    Encapsulation Format : MIME
    Payload Extraction : SOAP Body
    When i drive PI message it generates error below.
    What must i do to solve this problem?
    Thanks.
    Error message
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@20715646 for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException

    *Url:*  http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest
    When i use Url with *?wsdl* it generates below (it'is very long. I give part of it)
    wsdl
    <?xml version="1.0" encoding="UTF-8" ?>
    - <wsdl:definitions targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:intf="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:tns1="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" xmlns:tns2="http://schemas.hp.com/AssetManager/R51/ACMetaData" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    - <!--
    WSDL created by Apache Axis version: 1.2.1
    Built on Jun 14, 2005 (09:15:57 EDT)
      -->
    - <wsdl:types>
    - <schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:AdministrationTypes="http://schemas.hp.com/AssetManager/Custom/Head/Administration/Types" xmlns:CableTypes="http://schemas.hp.com/AssetManager/Custom/Head/Cable/Types" xmlns:CatalogTypes="http://schemas.hp.com/AssetManager/Custom/Head/Catalog/Types" xmlns:ChargebackTypes="http://schemas.hp.com/AssetManager/Custom/Head/Chargeback/Types"
      <import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" />
      <import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" />
    - <annotation>
      <documentation>Auto-generated schema for AssetCenter web services for Head/SapTest Implementation</documentation>
      </annotation>
      <import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SAM/Types" schemaLocation="../../schema/Head/SAM/SAMTypes.xsd" />
      <import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" ......
    <wsdl:operation name="retrieveAllBusinessAPIListByName">
      <wsdlsoap:operation soapAction="retrieveAllBusinessAPIListByName" />
    <wsdl:input name="retrieveAllBusinessAPIListByNameRequest">
      <wsdlsoap:body use="literal" />
      </wsdl:input>
    <wsdl:output name="retrieveAllBusinessAPIListByNameResponse">
      <wsdlsoap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    <wsdl:service name="SapTestService">
    <wsdl:port binding="impl:SapTestSoapBinding" name="SapTest">
      <wsdlsoap:address location="http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>

  • SOAP Receiver Adapter using SSL - PI 7.0

    Hi all,
    i am currently faced with a .net WCF webservice integration using https via SOAP Receiver Adapter in PI 7.0.
    Can anybody tell me into which Visual Administrator view i have to import my certificate in order to get https working ?
    Thanks in advance,
    Martin

    It must be the View you have created for your partners. There is usually a Trusted view where you have your own certificate. And there are other views where partners cerificates are stored. There you have to store the certificate.
    Regards,
    Prateek

  • Soap receiver adapter payload with certficate signature

    I have a requirement.. where XI calls external webservice using SOAP.
    I have configured SOAP receiver adapter, but the webservice wants the certificate authentication.. From XI we sent the certficate to external webservice and then in the comm channel I did activate the 'certficate' check box. It did not work.
    For test purpose now they have deactivated the certficate authentication in their end.. it works if they deactivate. It means there is no issue with request structure.. purely the issue is when I use the certficate.
    External webservice sent me the copy of the soap request which works for them.. <b>that has security signature inside the payload.</b>  ( I have atteched below).
    If anybody has done it have an idea how to do it please let me know.
    - <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    - <soapenv:Header>
    - <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
      <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-62149565">MIIGOzCCBaSgAwIBAgIQIKVRaj76KNaG5Dl6P5X7wzANBgkqhkiG9w0BAQUFADCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MDMyMzAwMDAwMFoXDTA4MDMyMjIzNTk1OVowUDEgMB4GA1UEChQXSGV3bGV0dC1QYWNrYXJkIENvbXBhbnkxEDAOBgNVBAsUB1NlcnZlcnMxGjAYBgNVBAMTEWl0Zy5lcHJpbWUuaHAuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDVGa1x5j/RJHHkqYzEb9NIQGChffTb1D0LiYAP5arbxz0trCp8ZeG4FCH71jc6x9Ks3gC4YdWgQbOCz64wnpM8NvEVCZBHuxvdnPZpziPWQqDr0yvwSoCXg8mkeJrHql0MSm7TNiyhzCAzlmB9JgmoHrRtArJdXMRpHjdZQK3QIDAQABo4IDxTCCA8EwDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBaAwHwYDVR0jBBgwFoAUSlYfvIpRj/SDE8naXHlUyAK6q58wHQYDVR0OBBYEFE99o7D6AITUcqWVmeYzu/2k66VEMIIBKAYDVR0fBIIBHzCCARswggEXoIIBE6CCAQGUWh0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL0hld2xldHRQYWNrYXJkQ29tcGFueUlUSW5mcmFzdHJ1Y3R1cmUvTGF0ZXN0Q1JMLmNybIaBuWxkYXA6Ly9sZGFwLmhwLmNvbS9DTj1IZXdsZXR0LVBhY2thcmQlMjBQcmltYXJ5JTIwQ2xhc3MlMjAyJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eSxPPUhld2xldHQtUGFja2FyZCUyMENvbXBhbnksQz1VUyxPVT1JVCUyMEluZnJhc3RydWN0dXJlLE89aHAuY29tP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5MCoGA1UdJQEB/wQgMB4GCCsGAQUFBwMBBggrBgEFBQcDAgYIKwYBBQUHAwQwggEWBgNVHSAEggENMIAwgAYKKwYBBAELBAMCATCAMCkGCCsGAQUFBwIBFh1odHRwOi8vZGlnaXRhbGJhZGdlLmhwLmNvbS9jcDCABggrBgEFBQcCAjCAMB4WF0hld2xldHQtUGFja2FyZCBDb21wYW55MAMCAQIagZVBdXRob3JpdHkgdG8gYmluZCBIZXdsZXR0LVBhY2thcmQgQ29tcGFueSBkb2VzIG5vdCBjb3JyZXNwb25kIHdpdGggdXNlIG9yIHBvc3Nlc3Npb24gb2YgdGhpcyBjZXJ0aWZpY2F0ZS4gSXNzdWVkIHRvIGZhY2lsaXRhdGUgY29tbXVuaWNhdGlvbiB3aXRoIEhQLgAAAAAAAAAAAAAwge4GCCsGAQUFBwEBBIHhMIHeMCsGCCsGAQUFBzABhh9odHRwOi8vb25zaXRlLW9jc3AudmVyaXNpZ24uY29tMIGuBggrBgEFBQcwAqSBoTCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MA0GCSqGSIb3DQEBBQUAA4GBAMB3vOFZYe26MaZ8mpnoZwhWbLBFV/lxtefZT1uT7mKZiaHjVqwu3tN1eAYAUXtJQHVJTnCnbDm9zFunlvuEzGMt9PwXS61MK6GwPmtjEsevRnGIA7arvpjSJ1/EQlD620I7icM9BNXbElYFfsnZjlWKFTZz3VX1OT2qmJtVWpD</wsse:BinarySecurityToken>
    - <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
    - <ds:SignedInfo>
      <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
      <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
    - <ds:Reference URI="#id-24819136">
    - <ds:Transforms>
      <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
      </ds:Transforms>
      <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
      <ds:DigestValue>6Mzpm7P8k3f8UuxbBMP4ZTC83Yc=</ds:DigestValue>
      </ds:Reference>
      </ds:SignedInfo>
      <ds:SignatureValue>HcqMChOzlHFXTRRAf7kyTSQ5Jd53Yiu7oFLjkh5P3vayo2G4sjFv/qFKHX0E6a5xkBMTIRrW+30t7IdB4X0x35FPO1dTulz37KM1/jpLSGVxnjnWWeFZvseVjJsk5NTPiSE6GAjO7rFW/Vled2djATTmZsIgJCIfhLYVp112Uis=</ds:SignatureValue>
    - <ds:KeyInfo Id="KeyId-21369792">
    - <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-29015968">
      <wsse:Reference URI="#CertId-62149565" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
      </wsse:SecurityTokenReference>
      </ds:KeyInfo>
      </ds:Signature>
      </wsse:Security>

    go through this webinar and follow the steps...It will solve your problem..
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1b657d59-0c01-0010-4fa8-f792fa412823
    Regards,
    Ravi

  • Soap Receiver Adapter - No Response Message

    Hi, I've got the following scenario: Idoc - XI - Webservice. I've imported the WSDL from the .NET webservice and used the input and output messages in a syncronous interface.  I've setup a SOAP Receiver adapter with the Webservice details.  Everything is working fine when I call the webservice and the data is received 100% at the target system, but I am not getting ANY response back on XI.
    RECEIVER SOAP ADAPTER Audit LOG:
    2008-01-24 16:41:57 Success SOAP: request message entering the adapter with user J2EE_GUEST
    2008-01-24 16:41:57 Success MP_LEAVE1
    2008-01-24 16:41:57 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
    2008-01-24 16:41:57 Success Acknowledgement creation triggered for type: AckNotSupported
    2008-01-24 16:41:57 Success SOAP: completed the processing
    2008-01-24 16:41:57 Success SOAP: continuing to response message 83638fb0-ca8a-11dc-b36c-00145eed9500
    2008-01-24 16:41:57 Success SOAP: sending a delivery ack ...
    2008-01-24 16:41:57 Success SOAP: sent a delivery ack
    2008-01-24 16:41:57 Success The message status set to DLVD.
    2008-01-24 16:41:57 Success Acknowledgement sent successfully for type: AckNotSupported
    Has it got anything to do with the "AckNotSupported" type?  Is "AckNotSupported" the default setting for the receiver SOAP adapter?  If so, where do I change this setting?
    When I call the webservice with the exact same input using a standalone tool, I get the response message back 100%.  Any help will be appreciated.
    Thanks
    Rudi

    Hey
    you are confusing between a response and an acknowledgement.
    response and acknowledgement and not one and the same thing.
    response is basically used when you send some query to the receiver system and expect a set of value(s) for your query.for e.g sending a query to a Database(JDBC) or SAP system(RFC)
    and acknowledgement is just a notification that the message was receiver by the receiver correctly,it does not returns you a set of value(s).
    now coming to your question,ALEAUDIT IDOC is generated when an IDOC is posted,since in your case you are not posting and IDOC,instead your are sending it ,i m not sure if ALEAUDIT will be generated or not,one thing that will come to your rescue is that every receiver SOAP adapter expects a HTTP response(irrespective of you explicitly asking it or not).
    a HTTP 200 means that messages were posted successfully,and HTTP 500 means application error,get this HTTP response and send it back to the SAP system,most probably you would need to use BPM for this.
    Thanx
    Aamir
    Edited by: Aamir Suhail on Jan 24, 2008 11:26 AM

  • SOAP Receiver Adapter issue

    Hello there,
    I am using a SOAP receiver adapter. The URL contains the format - https://<XYZ.com>/car/soap/Sync?login=username&pass=password
    Now, if I configure the channel by using the "Configure User Authentication", the data is not getting posted at target.
    But if I provide the user id / pwd in the URL, it gets posted.
    I don't want to use the user id / pwd in the URL but at the sametime, the WS team is not ready to change the format of the URL.
    Can I use "Query String" to handle that? If yes, how? If no, what options I have?
    Thanks for your precious input and time.
    Abhi

    Thanks Suraj!
    Have you tried this:
    url : https://<XYZ.com>/car/soap/Sync
    and Configure User Authentication option set
    I haven't tried it that way. I am not sure whether that will work, as WS team told me that I am required to put in the whole URL. But thanks for your suggestion, I will give it a try that way.
    also try specifying the SOAP action as per your wsdl file
    SOAP Action is not Mandatory, so I am not using that.
    Thanks,
    Abhi

  • SOAP Receiver Adapter Always "Running"

    I have a SOAP receiver adapter that is working fine.  I call an MDM web service, which sends a response, but I do not need it.  I have tried a synchronous and asyncronous interface.  Both work fine.
    But...with both, the communication channel monitor in RWB always shows a Short Log of "running". 
    Is this right?  I expected that the Short Log value would reset to inactive or something.
    Processing Details...
    2009-01-28 10:13:29 Success Message successfully received by messaging system. Profile: XI URL: http://snadc80i:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2009-01-28 10:13:29 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2009-01-28 10:13:29 Success Message successfully put into the queue.
    2009-01-28 10:13:29 Success The message was successfully retrieved from the receive queue.
    2009-01-28 10:13:29 Success The message status set to DLNG.
    2009-01-28 10:13:29 Success Delivering to channel: SOAP_MDMIn_MDMUpdateRecord
    2009-01-28 10:13:29 Success MP: Entering module processor
    2009-01-28 10:13:29 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    2009-01-28 10:13:29 Success SOAP: request message entering the adapter with user J2EE_GUEST
    2009-01-28 10:13:29 Success SOAP: completed the processing
    2009-01-28 10:13:29 Success SOAP: sending a delivery ack ...
    2009-01-28 10:13:29 Success SOAP: sent a delivery ack 2009-01-28 10:13:29 Success MP: Leaving module processor
    2009-01-28 10:13:29 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System. 2009-01-28 10:13:29 Success The message status set to DLVD.
    Thanks,
    Keith

    Short Log only displays the status of communication channel. So if it says running, then it would mean that the channel is in running status. When not in use, it doesn't get deactivated itself. I guess "running" is what people wait to see
    Regards,
    Prateek

  • SOAP Receiver Adapter Target system down

    Hi All,
    My scenario is SOAP Receiver adapter --- > Portal system (Target system.).
    Now team is taking restart of target system. It will take around 1 hr. So my question what will happen to the messages which is received by SOAP Receiver adapter in this time frame. ?

    Hi Rajhans ,
    All the messages during that period of time will fail with System Error ,We   have to re-send  these messages manually once the target system is up. In stead of selecting one by one you can set Multiple Selection On option to select the messages in RWB
    .Please refer the weblog  will give you some idea about the standard reports which can also be used to reprocess the messages.
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414700)ID1051765250DB10924207601714756238End?blog=/pub/wlg/2728
    do you have synchronous soap receiver or async?
    Regards,
    Srinivas

  • SOAP Receiver Adapter - Read Header data on Synchronous Response

    I have a scenario - flat file to SOAP. The web service provider sends a response that contains data in the Header that I need to access. I have tried to use the "Do Not Use SOAP envelope" option on my receiver SOAP adapter, and I have configured my request message type to include the soap envelope elements. However I'm getting the following error from the web service
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'application/xml' was not the expected type 'text/xml; charset=utf-8'.
    I've read some inputs on this error that say to use the Transform bean to adjust the content to text/xml. However I'm not sure how to do that. If that is the correct resolution to my problem, can someone provide detailed steps on how to add the Transform bean to the adapter module. I have no experience with adding items to the module tab.
    If there are other ways to tackle this scenario to get access to the SOAP Header from the SOAP receiver adapter, please share those as well.
    Thanks in advance.
    Chris

    Resolved with the following blog
    /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

  • SOAP Receiver Adapter - Target URL

    Hi,
    We have a web service scenario, where the Sender is a III Party Java system and PI is the middleware and ECC as our receiver system.  We have a wsdl binding generated from SOAMANAGER.  We are using the WSDL Endpoint as the Target URL in our SOAP Receiver Adapter.  The scenario works perfect with desired results.
    Now that webdispatcher comes into place for load balancing and the BASIS team has given a different URL to use in the Target URL of the SOAP Reciver Adapter.  The scenario throws the following eorr:-
    Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
    Has anyone come acrossed such issues.  Looking forward for a solution.
    Thanks & Best Regards.
    Kris

    > Now that webdispatcher comes into place for load balancing and the BASIS team has given a different URL to use in the Target URL of the SOAP Reciver Adapter.  The scenario throws the following eorr:-
    >
    > Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
    >
    > Has anyone come acrossed such issues.  Looking forward for a solution.
    I wonder why your basis team is not able to help you.
    It seems that the web dispatcher is not set up correctly.
    http://en.wikipedia.org/wiki/HTTP_302

Maybe you are looking for

  • Previewing page in Firefox

    I downloaded Firefox 3.6 for Mac this morning and now when I try to Preview the html page in Firefox, the browser goes directly to the "landing page" I've set in my Firefox prefs instead of the Firefox page displaying my "local" file. Trashed the new

  • WebI document output

    Hi I have a question. Whenevr a WebI document is refreshed or run manually in InfoView, and saved on the repository, is there a way to get the output file from the server? Does  BO save a copy of the file anywhere on server? I dont want to schedule t

  • Thoughts: Versioning, Class Reloading, ClassLoaders

    Recently on Ted Neward's weblog there was a discussion about the limitations of the ClassLoader architecture: http://neward.net/ted/weblog/index.jsp?date=20030215 Ted offers some suggestion for improving the architecture, and it got me to thinking ab

  • Reporting an App error?  EA Sudoku update doesn't work

    Does anyone know how to report an iPhone App error? I've been using EA's Sudoku App for weeks now with no issue. This morning I downloaded the latest update and now the game doesn't work. It loads fine but when it brings you to the board it is popula

  • Enhanced Interface Determination gives Empty Payload

    Hi, I am using Enhanced Interface Determination in my scenario. 1:3 Message Types(Interfaces). The thing is that split occurs, but after Message Mapping I get empty Payloads.. I am using External Definitions instead of Message types. Another question