SOAP RECEIVER SSL Problems

Dear Community,
   I have configured a SOAP Receiver to an external web service (https://server:7002/service). I have use IE to get the certificate of the server and have imported it into the keystore of the j2ee (using VA). I have imported it to the all current views available. We have SAP PI 7.0 SP18. The problem is that the SSL handshaking is not performed correctly. I have placed a tcp gateway monitor tool to see the messages pass through. As soon as the first message is send to the above URL and a response is received, I get a XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. Also, in the default trace log I get a no private key found.... Do I need extra steps to configure SSL in the SOAP Receiver? The service does not required a Client authentication certificate and has a certificate with  o CA root certificate (since this is only a test system and has issued its own certificate). Any ideas? Any help will be appreciated.
Regards,
S.Socratous

Hello,
Generally it's a connectivity behaviour. Check if you have setup the connection to
the receiver and also check the explanation regarding 500 Internal Server Errors:
*Description: The server encountered an unexpected condition which prevented it from fulfilling the request.
Possible Tips: Have a look into SAP Notes u2013 804124, 807000*
It may be also a problem with the SSL certificate. So, check if it's not expired;
The correct server certificate may be not present in the TrustedCA keystore view of NWA .
Please ensure you have done all the steps described in these url (this is for 7.11):
Security Configuration at Message Level
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/d1c7e690d75430e100000
00a42189b/frameset.htm
You may have not imported the certificate chain in the correct order (Own -> Intermediate -> Root);
Last, if the end point of the SOAP Call(Server) is configured to accept
a client certificate(mandatory), then make sure that it is configured
correctly in the SOAP channel and it is also within validity period.
(This certificate is the one which is sent to Server for Client
authentication)
Hope that helps.
With regards,
Caio Cagnani

Similar Messages

  • SOAP receiver exception problem

    Hi XI expert,
    I am using scenario as following:
    ABAP proxy -> xi -> soap receiver -> webservice
    in sxmb_moni, the message runs ok. but in RWB, there are some error in CC monitor.
    2007-07-07 11:33:54 Success SOAP: continuing to response message e305dd90-2c3a-11dc-95af-0015c5f7cd3b
    2007-07-07 11:33:54 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
    2007-07-07 11:33:54 Success SOAP: sending a delivery error ack ...
    2007-07-07 11:33:54 Success SOAP: sent a delivery error ack
    2007-07-07 11:33:54 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
    2007-07-07 11:33:54 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
    2007-07-07 11:33:54 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/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors.
    2007-07-07 11:33:54 Success The asynchronous message was successfully scheduled to be delivered at Sat Jul 07 11:38:54 CST 2007.
    2007-07-07 11:33:54 Success The message status set to WAIT.
    What is the problem? and how can I deal with to identify the problem?

    hi
    Go through this links
    Check out these threads..
    RFC -> XI -> External web service
    How to resolve this RFC_adapter_sender to SOAP_adapter_receiver Exception?
    Why getting "DeliveryExcetion" in SOAP->XI->RFC scenario?
    You may refer these fallowing weblogs
    /people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    Thanks & Regards
    Sridhar.Bommireddy

  • SOAP receiver / SSL

    Hello,
    I have the following scenario : R/3 -> XI -> SOAP with SSL.
    When accessing the target URL with a browser I don't have any problems. The SSL handshake is working correctly,I can download all certifcates from the chain and they are all valid.
    I imported the CA certficates into the keystore. But XI is unable to create the socket. In the logs I have the following message :
    "Attempting to create outgoing ssl connection without trusted certificates".
    We have other partners using the same scenario working correctly. I checked and the partners that are working correctly are using a 1024 public key and the new one that causes error is using only a 512 public key.
    Thanks,
    Bela

    Hi Bela,
    Did you ever solve the issue I'm currently facing a similar problem when trying to use SSL to call a web service

  • SOAP receiver inactive problem

    Hi Gurus,
    I am using a SOAP receiver channel, I actived this SOAP CC in ID , but when I go to RWB and goto Communication Channel monitor, found the SOAP receiver channel status is "Channel started but inactive" with a yellow triangle.
    Our XI version is PI7.0 SP11.

    Hi,
    send the first message with it and check again
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Soap Receiver Adapter problem. very urgent..

    Hi,
    When I am sending data from XI to CRM through soap receiver communication channel I am getting error:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Authority check failed
    Pls advice urgent.
    Regards

    Hi Rick,
    At fist did  you create SOAP fault message mapping in your scenario?
    If not then plz do that.
    Some links for ur help:
    Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 *** - have a look into this to troubleshoot your SOAP
    Fault Message Types - A Demo (Part 1)
    Receiver SOAP adapter scenarios:
    RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
    RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
    Regards,
    Vinod.

  • SOAP Receiver Adatper Problem

    I've configured a soap receiver adapter, which is asynchronous.
    The outside web service is implemented by AXIS2. After the XI send the soap to the web service, the web service does it's function and then give back a empty response, which cause the "system error" status of the message.
    How can I solve this?
    Thanks and B'Rgds,
    YiNing

    Barry,
    even though the document handles the creation of an attachment, it is about a module that does that. So, in the core, it is about a module development.
    Nevertheless, the online documentation is pretty straighforward regarding that: http://help.sap.com/saphelp_nw70/helpdata/en/8b/895e407aa4c44ce10000000a1550b0/frameset.htm
    The document you have deals with the direct steps you'll have to perform in NWDS.
    The online documentation and the sample module provide sample information and coding you can use in your development.
    Regards,
    Henrique.

  • SOAP Receiver Adapter problem (client certificate required)

    My Scenario is similar to described in https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3721. [original link is broken] [original link is broken] [original link is broken] I have two PI servers running on one machine. I am trying to post message HTTPS with Client authentication via SOAP adapter from one PI system to SOAP adapter of other PI server. I have done the following configuration.
    PI Server AXD - (Client) - Receiver SOAP adapter
    PI Server AXQ - (Server) - Sender SOAP Adapter.
    Steps in AXD
    1. I have created a certificate of AXD in the service_ssl view of key storage.
    2. I have imported the AXQ public certificate in to AXD in the TrustedCAs of Key storage
    Steps in AXQ
    1. I have created a certificate of AXQ in the service_ssl view of key storage.
    2. I have imported the AXD public certificate in to AXQ in the TrustedCAs of Key storage.
    3. I have created a user in AXQ and assigned the certificate of AXD under usermangement in Security provider to this user.
    4. I have added the AXD certificate under Client Authentication tab with require client certificate option checked in the SSL Provider.
    5. I have assigned the user created in AXQ in the step above to the Sender Agreement.
    Now when I post message from AXD with Configure Client Authentication checked (Here I have selected the certificate of AXD and view as service_ssl) I am getting the following error.
    Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:884) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3
    Any pointer to solve this problem is highly appreciated.
    Thanks
    Abinash

    Hi Hemant,
    I have couple of questions. Why do we need to import certificate for SOAP WS-Security and from where I can get it?
    As far as my scenario goes I am not using message level security.
    Secondly what do you mean by TRUSTED/WebServiceSecurity? I don't see any such view inside the Key Storage.  I can see a view named just WebServiceSecuity though.
    Also I don't have a decentralized adapter installation rather I have two separate PI instances having their own central adapter engine.
    Abinash

  • SOAP Receiver Adapter problem

    Hi guys,
    I have problem with ABAP Proxy->XI->SOAP scenario. I send data from R/3 via Proxy. I see in the monitor, that message has been processed successfully, however, the SOAP adapter does not send this message to the target. I tried to run a listener on on my local machine on port 80 and sent data from SAP. Again, in monitor successful, but no action in the listener - the message did not arrive. (the adapter was set up to send data to ma local PC). The scenario is async.
    Any idea, what could be wrong?
    In the receiver SOAP adapter - hoe to set up Target URL? http://<machine>:<port> or w/o port and it is automatically sent to port 80?
    Thanx for answers!
    Olain.

    Hi guys, thanx for answers..
    All the systems are in the local network, so no proxy is there. However, in the communication channel monitoring I get error: connection timed out , can be due to invalid adress.. However, If i try to reach the WS from the SOAPui tool, this web service works...
    Any other idea?
    Olian

  • SOAP and SSL problem

    I am using JDeveloper 9.0.3 and the Oracle SOAP library which is shipped with Oracle JDeveloper.
    My application connects to a SSL enabled webservice.
    The first problem I encountered was a 'no njssl9 in java.library.path' error.
    I used the tips from Lehmann's BLogger site (http://radio.weblogs.com/0132036/2004/02/13.html).
    I could not get this working in JDeveloper 9.0.3 because JDev 9.0.3 is using java jdk 1.3 which has not JSSE built in.
    So I decided to use JDeveloper 9.0.5.2. which uses the java jdk 1.4.
    It works, however now I am stuck with an error that the certificate chain is incomplete.
    The webservice to which I connect sends only the 'last' certificate, so not the entire chain. Can this be the problem?
    I have a couple of questions:
    1) what do I have to do to ensure that my application trusts the webservice SSL certificates. I know I have to install
    the certificate somewhere in the cacerts file. But which certificate en how do I store it?
    2) Is it true that the Oracle SOAP library only works with the Oracle Wallet? Does that mean I cannot get Oracle SOAP
    to work on an Oracle Application Server with my application?
    3) Is there any way to solve the 'no njssl9 in java.library.path' error using the Oracle SOAP library in JDeveloper 9.0.3?

    2) For non-oracle wallets, you need to set the following
    # private key
    # certificate chain
    # trusted certificates
    OracleSSLCredential sslCredObj = new OracleSSLCredential();
    // Set trusted certificates
    sslCredObj.addTrustedCert(easQACA);
    // Construct certificate chain. Place CA at the top
    // and user certificate at the bottom. The order of
    // set certificates in the chain is important. You must set
    // root certificate first, then signer certificates, and finally user
    // certificate.
    sslCredObj.addCertChain(rootCA); (set root CA certificate)
    sslCredObj.addCertChain(signer CA);(set signer certificate)
    sslCredObj.addCertChain(userCert); (set user certificate)
    * Set private key
    sslCredObj.setPrivateKey(userKey, password);
    3) If you have Oracle IAS or database installation, the njssl libraries are under ORACLE_HOME\lib. Include ORACLE_HOME/lib in LD_LIBRARY_PATH or starting the javavm using
    -Djava.library.path=ORACLE_HOME/lib
    should solve the njssl error.

  • SSL in Soap receiver communication channel

    Hi,
    I have a webservices that works fine in Soap UI. The webservice provider uses the SSL, but works like a web browser, doesn´t need to install a certificate before access the webservice.
    But when i try to use SAP PI using the soap receiver communication channel, the soap adater return the follow message:
    "Peer certificate rejected by ChainVerifier"
    I read some thing about using axis to solve this problem but I can´t find anything to configure this scenario.
    If someone had this problem and solved it, i will apreciate the help.
    Thanks
    Fabricio

    I Have 2 communication channel:
    1) This works fine
    Adapter Type: SOAP
    Receiver
    Transport Protocol: HTTP
    Message Protocol: SOAP 1.1
    Adapter Engine: Integration Server
    Target URL: https://gw-homologa.serasa.com.br/wsacheixml/wsacheixml.asmx
    SOAP Action: https://sitenet05.serasa.com.br/WSAcheiXML/WSAcheiXML/ConsultaAchei
    2) This doesn´t work
    Adapter Type: SOAP
    Receiver
    Transport Protocol: HTTP
    Message Protocol: SOAP 1.1
    Adapter Engine: Integration Server
    Authentication: Basic
    User/Password
    Target URL: https://treina.spc.org.br/spc/remoting/ws/consulta/consultaWebService
    SOAP Action: blank
    Both are https and the certificate is sent at communication time (There isn´t a certificate to install in the Key Store in Visual Administrator)
    I read that Axis manage this kind of integration with webservices, because the certificate must be installed at the moment of sending http request.
    I don´t know why the first interface works fine an the another doesn´t work, then I´m trying with Axis.
    In the SOAP UI both interfaces work fine.
    Thanks

  • Problem with soap receiver adapter

    Hi All
    I have Idoc sender and soap receiver in my scenario.
    I am calling web service deployed on WAS.
    The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <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.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please anybody can help to resolve this problem. This scenario has worked without any error previously.
    Thanks in advance
    Beena

    Hi Bhavesh,
    It is an Async call where method does not return anything.
    I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.
    Following is the Audit Log in Runtime workbench :
    Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414
    Time Stamp Status Description
    2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out
    2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.
    2006-12-13 10:25:24 Success The message status set to WAIT.
    2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1
    2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.
    2006-12-13 10:30:25 Success The message status set to DLNG.
    2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack
    2006-12-13 10:30:25 Success SOAP: request message entering the adapter
    2006-12-13 10:35:28 Success SOAP: call failed
    2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...
    2006-12-13 10:35:28 Success SOAP: sent a delivery error ack
    2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out
    2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.
    2006-12-13 10:35:28 Success The message status set to WAIT.
    I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.
    Thanks
    Beena.

  • SOAP receiver problems

    Hi Folks,
    I am sending data to the webservice using SOAP receiver. In the runtime workbench I can see the message as successfull, but the end user is claiming that , he didn't get the data from XI.
    What could be the possible reason for this?
    Where might the message lost?
    And for one message which is using SOAP receiver as communication channel , In the audit log I can see the steps as below:
    SOAP: request message entering the adapter with user J2EE_GUEST
    SOAP: completed the processing
    SOAP: continuing to response message
    SOAP: sending a delivery ack
    SOAP: sent a delivery ack
    The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
    MP: Leaving module processor
    The message status set to DLVD.
    For other message I can see the log as :
    SOAP: request message entering the adapter with user J2EE_GUEST
    SOAP: completed the processing
    SOAP: continuing to response message
    SOAP: sending a delivery ack ...
    SOAP: sent a delivery ack
    MP: Leaving module processor
    The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
    The message status set to DLVD.
    Both are using same communication channel. still u can see the difference in the steps that are exicuted (check leaving module processer line in both).
    Is it mandatory that the series of steps should be same for all the messages?
    I have 2 queries, please answer both......
    Thanks SPMD

    HI
    As a first test , import the wsdl shared by third party  in soap uI/MS infopath/xml spy , fill in the test data (preferably same which you are trying to post now) and do a test :- doing this you will get to know if there is any problem in the WS iteslf. if you get http 200 ok then posting happened and ask the third party to check if they got any request.
    If you have sync soap then you will be getting the desired response back to soap ui .
    Also check if you need to put soap action also check the content type if its text/xml or app/xml  some WS dont accept App/xml u may need to use message transformation bean in modules tab.
    if there is any connectivity at ntwrk level then please try  if you can trouble shoot using this blog
    /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
    Regards
    $rinivas

  • SOAP Receiver problem

    Hi everyone.
    I'm facing a new problem with SOAP Receiver adapter.
    We have an WSDL that works perfectly using SOAP Clients such as SOAPUI or StylusStudio. End-point is HTTPS://XXXXX:XXX/XXXXX
    WSDL is like this :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Adapter
      -->
    <tes:registraEntrada0Request xmlns:tes="http://testing.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
      <asu_id>SIO7</asu_id>
      <asu_descripcion>desc</asu_descripcion>
      <uo_id>1272</uo_id>
      <nombre>nombre</nombre>
      <ape1>ape1</ape1>
      <ape2>ape2</ape2>
      <usu_id>virtualdesa</usu_id>
      <usu_pass>virtualdesa</usu_pass>
    </tes:registraEntrada0Request>
    Problem is when i try to use this webservice from XI using a SOAP Receiver communication channel. I get a strange error :
    soap fault: No Deserializer found to deserialize a ':asu_id' using encoding style 'null'. [java.lang.IllegalArgumentException]
    I don't know if the problem is because HTTPS. All the process has been defined correctly in XI and my doubt is about the configuration of the RECEIVER SOAP or the WSDL structure.
    Hope you can help me
    Regards,
    Inigo.

    hi,
    check out response by Ricardo,
    Re: Error in Receiver Soap Adapter for Google API
    maybe you need to fill some attributes in an adapter module like mentioned there
    Regards,
    michal

  • SOAP Receiver over SSL - server certificate troubles

    Hello all,
    I have a scenario with SOAP receiver communication channel with comunnication over SSL. In the URL there is a IP address for a reason I will not mention ... simply there must be IP address in URL and not a host name.
    When I access the SOAP server with internet browser it gives me a server certificate with HOST NAME in CN. I placed this certificate to the "trusted container" in J2EEVisAdmin - Key Storage.
    Now you might already suspect the trouble: the certificate CN doesn't match with URL. This is obvios error we got many times on the internet (even in e-banking sector .. but we are able to skip it with our internet browsers' possibilities.
    Could I set up something in J2EE server as same as in internet browser ???
    Thank you in advance.
    Rgds
    Tom

    Got it,
    SAP Note : 791655
    HTTPS/SSL Properties
    Property Name = [default]
    messaging.ssl.httpsHandler=iaik.protocol.https.Handler
    messaging.ssl.securityProvider=iaik.security.provider.IAIK
    messaging.ssl.trustedCACerts.viewName=TrustedCAs
    messaging.ssl.serverNameCheck=false
    Description:
    The properties "httpsHandler" and "securityProvider" specify the class names of the HTTPS handler and Security provider used. The AF only supports IAIK. Never change these values! To activate HTTP/SSL, you must install the IAIK libraries on your J2EE Engine as described in the Installation Guide.
    The property "trustedCACerts.viewName" defines which J2EE keystore is used during the SSL Handshake for trusted CA certificates. You should never change this value either. With "serverNameCheck" you can specify whether the host name in outbound HTTPS requests should be checked against the host name in the certificate of the server.
    Regards,
    Bhavesh

  • Performance Problem on Soap Receiver Side

    Hi,
    my scenario is: FTP to SOAP (asynchronous) on PI 7.31 SP11.
    The ftp sender is providing a few hundred files at once, unfortunately the processsing at productive environment takes too long, like 15-60 minutes, depending on the number of files.
    What is really strange here, the same scenario is working 100% properly at the test environment! So i did some tests to find out the bottleneck:
    FTP -> PI prod -> SOAP prod - slow
    FTP -> PI test   -> SOAP prod - fast
    FTP -> PI prod -> SOAP test   - fast
    FTP -> PI prod -> NFS prod    - fast
    So if found: Only slow, if i use the productive PI to productive soap receiver.
    The adapter configuration is 100% the same as on test system.
    I watched the slow messages and found:
    First message:
    Normal processing of the steps until "XISOAP: XI message received for processing".
    Then it takes 4 seconds before "SOAP: Processing completed". This happens withing milliseconds on test environment.
    Later messages stay longer and longer in a queue.The processing time is going up to 36 seconds (instead of 4).
    -> Something is stopping / slowing them to be processed. This "stopper" becomes worse if more messages are processed.
    Does anybody have an idea to explain this strange behaviour?
    Regards,
    Udo

    Hi Udo,
    The problem seems to be in the message system queue in the AFW in the production environment. It has sense because the SOAP pro and NFS pro are different adapters, however afaik the SOAP test channel uses the same thread pool that the SOAP pro in PI pro.
    Have you check to increase the number of threads?. You can check the number of them,
    in this URL http://host:port/MessagingSystem/monitor/systemStatus.jsp (System Status):
    Regards.

Maybe you are looking for