SAP PI SOAP Sender Adatper using HTTPS Without Authentification

Dears experts,
I have a requirement where i need to implement the next flow:
POS (Java code to web service soap) ---> (SOAP HTTPS - SAP PI - XI) --->ECC (XI)
So, have configured my SOAP sender adapter as:
Transport protocol: HTTP
Message protocol: SOAP 1.1
HTTP Security Level: HTTPS without Client Authentication
But as i have read i see that Basis team should configure this to permit HTTPS into PI, but i would like to do it by my self...
Following a lot of forums, manuals, etc... I have configured the transaction STRUST importing the certificated that i attached to you (PRTG Demo Certificate), succesfully in my server... and i tried to find how to configure netweaver but in this i didnt find it...
Then i tried again using SOAP UI but when i sent the message to HTTPS://www.piserver.com:50001 i still getting error without connection...
Wed Jun 25 18:27:13 CDT 2014:ERROR:An error occurred [Connection to https://piserver:50001 refused], see error log for details
Can you help me to end this, please?...
Best regards,
Azael

Hi,
The certificates should be installed under TrustedCA's in NWA (Netweaver Administrator). Aside from that, you should be posting to either:
https://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c where p=party, s=service and c=channel
or
https://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&sen
derService=FS&interface=IF&receiverParty=TP&receiverService=TS&in
terfaceNamespace=IFNamespace
Hope this helps,
Mark

Similar Messages

  • Invocation of SOAP Sender Adapter using Apache SOAP

    Hi,
    I'm trying to invoke the XI SOAP Sender Adapter using the Apache SOAP API. It seems that my message header is missing a few parameters (see exception below). Does anybody know which to set?
    Regards,
    Heiko
    ==========
    Exception:
    <?xml version='1.0'?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
      <SOAP:Body>
        <SOAP:Fault>
          <faultcode>SOAP:Server</faultcode>
          <faultstring>Server Error</faultstring>
          <detail>
            <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
              <context>XIAdapter</context>
              <code>Exception</code>
              <text><![CDATA[
    com.sap.aii.af.mp.module.ModuleException
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:502)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
         at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:507)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged1(Native Method)
         at java.security.AccessController.doPrivileged(AccessController.java:321)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: java.lang.Exception: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.getParaRequired(XISOAPAdapterBean.java:895)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createDefaultMessageHeader(XISOAPAdapterBean.java:942)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:214)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:496)
         ... 22 more
              ]]></text>
            </s:SystemError>
          </detail>
        </SOAP:Fault>
      </SOAP:Body>
    </SOAP:Envelope>

    Hi Heiko,
    You are missing the Namespace Parameter in the sender soap adapter configuration in XI3.0
    Thanks
    Prasad

  • How to send attachments using HTTP Binding Adapter?

    How to send attachments using HTTP Binding Adapter in Jdeveloper?
    Requirement: I need to send attachments to a system which can communicate with the middleware using https only.
    Kindly suggest..
    Edited by: Richa Juneja on Jan 28, 2013 4:03 AM

    Hi,
    Following links may help U
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    http://help.sap.com/saphelp_nw04/helpdata/en/3c/b4a6490a08cd41a8c91759c3d2f401/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm
    to know the basics about soap adapter u cn check out this link
    /people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
    to get in detail about the attachments chk out this link
    hi i am unable to attach an attachment in File to mail scenario
    Regards
    Pullarao

  • SAP PI  Soap Send adapter  is not available.

    Hi  Experts：
    i encounter a issue when use Soap sender adapter.  i configured  soap sender adapter senario and generate  wsdl  in the id  .
    and then  import wsdl document to the  soapui to test the webservice.  but throw some exception blow:
    <!see the documentation>
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>java.lang.NullPointerException
    +     at com.sap.aii.af.sdk.xi.mo.xmb.XMBMessageOperator.getQualityOfServiceAsString(XMBMessageOperator.java:2109)+
    +     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:943)+
    +     at sun.reflect.GeneratedMethodAccessor1126.invoke(Unknown Source)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:585)+
    +     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)+
    +     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)+
    +     at $Proxy3087.process(Unknown Source)+
    +     at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275)+
    +     at sun.reflect.GeneratedMethodAccessor518.invoke(Unknown Source)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:585)+
    +     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)+
    +     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
    +     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)+
    +     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)+
    +     at $Proxy330.process(Unknown Source)+
    +     at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:175)+
    +     at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470)+
    +     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)+
    +     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
    +     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)+
    +     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)+
    +     at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)+
    +     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)+
    +     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)+
    +     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)+
    +     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)+
    +     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)+
    +     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)+
    +     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)+
    +     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:457)+
    +     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)+
    +     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)+
    +     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)+
    +     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)</text>+
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    nd the find a note :sapnote_0001239995  can solve the problem in the pi 7.10 .but my pi is 7.11 .anybody know which note  should be apply to solve the problem in the pi7.11 .thanks .

    hi,
    Either you are using an incomplete URL
    you can however try with this URL format:
    http://<IPAddress OR ServerName>:<PORT_No>/XISOAPAdapter/MessageServlet?channel=:<SenderBusinessService>:<SenderSOAPCC>&version=3.0&Sender.Service=<SenderBusinessService>&Interface=<SenderInterfaceNamespace>%5E<SenderMI>
    refer blog related ur issue:
    ADAPTER.JAVA_EXCEPTION: Sender soap adapter PI 7.11
    thanks,

  • SAP Connection with a Website using HTTPS

    SAP Gurus,
    We are on SAP 4.7.  Requesting you to revert whether it is possible to connect SAP 4.7 with HTTPS (Secured) thru some BAPI or BADI.
    Details:
    1. The Business Process expected to be set is for Vendor Transactions.
    2. That is, the Vendor liability document is expected to be posted from the data that would flow thru Internet HTTPS.
    3. The request would originate from a website (that is NOT SAP).
    4. It would have the Vendor Party credentials.
    5. The Line Item Data would come to SAP thru HTTPS and it is expected that SAP would accept the request and process it.
    6. After successful process of the file, the system would generate Accounting Document.
    7. This Accounting Document is expected to be sent back to the originator website, using the same HTTPS connection.
    8. The entire leg is expected to be completed in 180 seconds.
    Qs:
    a. Is it possible to achieve this with using some BAPI or BADI?
    b. Whether it is possible to connect to SAP with some RFC (RFC may not be the right technical word, please recommend what else) using the Secured connection, that is HTTPS?
    Many Thanks

    Hi,
    Thanks for ur reply.
    I am facing the following problem.(I am using Https protocol)
    1.A runtime exception is thrown at line no 5. This is the main problem i am facing and as i am not able to establish the connection with the server, i was able to proceeed further.
    2. I need help for setting the content type(Remember i am using Https)
    3. As u said at server side file has to be decompressed but that is not under my scope so it is not a problem for me.
    4. once connection is established, I need to create a byte stream and write to destination and then i have to check the response sent by the server.
    I am looking for an idea how to establish the connection with the server. any references let me know.
    Code written by me:
    URL url = new URL("https://www.sun.com");
    URLConnection conn = url.openConnection();
    conn.setRequestProperty("content-type","Application/x-zip-compressed"); // I dont think this is correct way of setting the header var
    conn.connect(); // an exception is raised here
    conn.setDoOutput(true);
    OutputStream ostream = conn.getOutputStream();
    Message was edited by:
    vbr3650

  • SOAP Sender Adatper - Read custom http header field

    Hello,
    i try to read a custom http header into the dynamic configuration of a message - but it is not working as expected - in ASMA i configured to get the value of MYHEADER1 into XHEADERNAME1 - when testing with a MYHEADER1 value, the value is not put into XHEADERNAME1.
    Is it possible to get custom HTTP Headers in the message?
    bf
    franz

    I have quite the same problem!
    I try to make the receiver determination based on the content of XHeaderName1, but none of the Dynamic Configuration parameters is shown in the sxi_monitor.
    I've described my scenario in more detail in this thread
    http://scn.sap.com/message/13586532#13586532
    Does anyone have an idea?

  • How to send email using u201CSO_DOCUMENT_SEND_API1u201D without attachment.

    Dear Expert,
    I am using the folowing code to get the content of smartform as otfdata :
          CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
            EXPORTING
              formname           = v_formname
            IMPORTING
              fm_name            = v_fm_name
            EXCEPTIONS
              no_form            = 1
              no_function_module = 2
              OTHERS             = 3.
          CALL FUNCTION v_fm_name
            EXPORTING
             control_parameters         = control_parameters
             output_options             = output_options
          orderadm_h = orderadm_h
          activity_h =  activity_h
          status_i = status_i
          working_set_e_s_bbp = working_set_e_s_bbp
          language = l_langu  "sY-LANGU
           IMPORTING
             document_output_info       = document_output_info
             job_output_info            = job_output_info
             job_output_options         = job_output_options
           EXCEPTIONS
             formatting_error           =  1
             internal_error             =  2
             send_error                 =  3
             user_canceled              =  4
             OTHERS                     =  5
    How can I send the data in job_output_info-otfdata in the email body without putting it into attachment?
    I am using the function u201CSO_DOCUMENT_SEND_API1u201D.
    I am sending also a normal text in the email and I want to put the data in the job_output_info-otfdata at the end of the text.
    Thank for very much in advance.
    Best regards
    Ahmed Hadi

    Hi Ahmed,
    I believe this blog will help you:
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417800%29ID1330314450DB01968839116473008128End?blog=/pub/wlg/2273
    Kind regards,
    Garcia

  • SOAP sender adapter with HTTPS

    Hi All,
    We have a requirement where we need to add message security to messages sent by sender SOAP adapter.
    To achieve this, I understand that I need to the following steps:
    1. Check 'Configure Certificate Authentation'
    2. Get the SSL certifiate given by receiver system and import it into SAP, and select it in SOAP Comunication channel
    3. 'Keystore VIEW' - What should i select here?
    4. Security Parameters/Security Profile - Do I have to check this option and select a security profile?
    Please let me know IF I missed something here.
    Thanks,
    Chandra

    Hi Chandra,
    One pre-requisite would be you need to install the SAP cryptographic library for using SSL.
    In the keystore view, you will select the view of the keystorage where the SSL certificate has loaded.
    Please check the sap help below for more details, als sap note 891877.
    http://help.sap.com/saphelp_nwpi711/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm
    regards,
    francis

  • Set up https SOAP Sender adapter

    Hello, I am doing the Webservice -- XI --   RFC
    I have successfully configured the whole scenerio and it works when the SOAP Sender adapter is set to HTTP security
    But when I set it to HTTPS without client auth or with I can not get it to work, I redid the wsdl entering in a url of https and get the following error
    Wed Feb 27 11:02:56 PST 2008:ERROR:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
       javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(Unknown Source)
            at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source)
            at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
    via soapui
    Does anyone have any suggestions or documentation or success in successfully setting up the SOAP adapter to use https?
    I also always reward points
    Cheers
    Devlin

    have you checked that:
    https://service.sap.com/sap/support/notes/891877
    https://service.sap.com/sap/support/notes/856597
    * Q: Can I use SSL for my sender adapter?
               A: Yes. Normally, the SOAP adapter servlet runs on the engines HTTP port. But you can activate the engine's HTTPS port so that this servlet can receive messages sent to the HTTPS port. See the documentation about the J2EE engine's security configuration.
    /wg

  • HTTP Error 501 with SOAP Sender channel

    Hello,
    i've am simple Question:
    I want to call the following SAP XI SOAP Sender channel "MySoapSenderChannel":
    XI-Parameters:
    namespace: <myInterfaceNamespace>
    Interface:   <myAsynchInterface>
    QoS: Exactly Once in Order
    Queue: MY_QUEUE
    We do not care about the Response - so the processing is asynchron.
    Thus my interface mapping maps to asynch interfaces. The desitnation
    is an ABAP Proxy. The configuration has been done and tested.
    Here my question:
    according the documentation, the URL has the following syntax:
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel.
    In our case:
    http://<myHost>:8002/XISOAPAdapter/MessageServlet?channel=:MyService:MySoapSenderChannel.
    But when i generate a WSDL for the interface out of the Configuration, the address is:
    <soap:address location="http://<myHost>:8002/sap/xi/engine?type=entry&amp;version=3.0&amp;Sender.Service=MyService&amp;Interface=...
    and so forth.
    But was is the difference between these 2 possibilities?
    Why do i get HTTP Error 501 when i use the URL from the documentation (the first one)?
    Thanx in advance
    Gunnar

    Gunnar,
    I will suggest you to go through it once to check all your connection.
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Regards,
    Sarvesh

  • SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

    Hi,
    I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
    https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
    This is the error that I get when sending a message to the interface
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
    <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
         at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
    Thanks,
    Rashmi.

    Hi Rashmi,
    I also think your problem is data related.
    Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
    Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
    Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
    Best Regards, Trevor

  • Polling with HTTPS (SOAP sender adapter)

    Hi,
    we are using SAP PI 7.1 EHP 1 and we have to set up a scenario, in which a business partner is going to send us IDocs over HTTPS.
    Now our security team has objections, that incoming messages could be too risky. So we have to figure out if it's also possible, to set up a polling over HTTPS. Unfortunately there's no availability to insert an URL in the SOAP sender adapter, so I think it's NOT possible.
    Any other ideas or agreements?
    Thanks in advance,
    Juergen

    I think SOAP sender adapter supports HTTPS (w/ and w/o client certificate) ... But you'll need to complete the security setup (root CA, etc) before, and then give the "to-be-called" URL to yout partner.
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
    Rgds
    Chris

  • SOAP Sender with HTTP(with SSL)=HTTPS with Client Authentication config

    Hi All,
    I have a Web-service-XI-Proxy scenario where we use SOAP Sender Adapter with HTTPs.  Double authentication (client- server) sertificate shall be used.
    Testing simple HTTP and XI user name/password works fine.
    Now I installed requred sertificates in TrustedCA and ssl-provider in VIsualadmin.
    But i can't see how i can configure certificates in SOAP sender Adapter. I've just did SOAP receiver for another scenario and there I could give keystore entry.
    I also doesn't know how to disable asking for name/password.  I am using XI 7.0.
    Please advise.
    Thanks,
    Nataliya

    Hi Nataliya,
    Go to SOAP Adapter> Inbound Security Checks-> HTTP Security Level--> Here you can specify  option "HTTP with Client Authentication. 
    One more thing HTTP Security level option is always available in Sender Adapter.
    For more clarity about HTTPS find below link.
    http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm
    To enable the TrustedCA in SOAP Sender adapter. Go SOAP Sender> Security Parameter> Security Profile--> Web Service
    security. Then go to sender agreement there you need to give key store entry.

  • HTTPs without client authentication, error while posting through Altova

    Hi Experts
    I am doing a SOAP- XI-Proxy synchronous scenario where i have to use HTTPs without client authentication for the first time in my system.
    I have made the scenario and WSDL out of it.
    When i am trying to test it through Altova, i am getting the following error:
    <?xml version="1.0"?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
        <SOAP:Body>
            <SOAP:Fault>
                <faultcode>SOAP:Server</faultcode>
                <faultstring>Server Error</faultstring>
                <detail>
                    <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                        <context>XIAdapter</context>
                        <code>ADAPTER.JAVA_EXCEPTION</code>
                        <text><![CDATA[
    java.security.AccessControlException: https scheme required
        at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:918)
        at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)
        at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:296)
        at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
        at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:187)
        at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:496)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
              ]]></text>
                    </s:SystemError>
                </detail>
            </SOAP:Fault>
        </SOAP:Body>
    </SOAP:Envelope>
    i saw a few discussion on web but nowhere the solution was provided.
    the url is
    http://abc.sap.point:1234/XISOAPAdapter/MessageServlet?channel=:system:communicationchannel&amp;version=3.0&amp;Sender.Service=x&amp;Interface=x%5Ex
    i changed it to https also but in that case it was not even posting the request.
    i have set the sender adapter like this
    is there any setting that i am missing.
    What is the setting the i need to do in SM59.
    Please help me getting through this.
    Your help is highly appreciated. Thanks in advance.
    Neha

    HI Neha,
    1. Enable the https service in the ICM: you can follow the way to do it like is pointed out in the page 4 of this document (PI 7.1 and PI 7.0 has the same smicm abap transaction) http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60ff2883-70c5-2c10-f090-a744def2ba66?overridelayout=t…
    2. Generate the certificate. Use the STRUST transaction. Chech this document SSL Configuration in SAP ABAP AS and JAVA AS – Step-by-step procedure
    Hope this helps.
    Regards.

  • Invokation of Webservices using HTTP

    Can I invoke webservices in SAP using HTTP instead of SOAP? If so How?

    Hi Vijay,
    yes we can do it with HTTP
    Configuring the Receiver Plain HTTP Adapter
    Use
    The plain HTTP outbound channel is a service provided by the Integration Engine. The system is addressed when technical routing determines a corresponding communication channel for the logical receiver from logical routing. The system sends the payload of the message to an HTTP address using HTTP, without being enhanced with an envelope.
    Integration
    You configure the adapter on the Parameters tab page during the definition of a communication channel in the Integration Server.
    Activities
    The plain HTTP adapter gives the receiver system the following specifications:
    Transport Protocol
    HTTP 1.0
    Message Protocol
    XI payload in HTTP body
    Adapter Engine
    Integration Server
    Addressing Type
    URL Address
    HTTP Destination
    Specify the target host, service number, and path prefix including query string:
    http://<hostname:port>/<path>?<query-string>
    You can identify the target host (HTTP port) of a SAP Web Application Server using the ICM monitor.
    Host and port of the HTTP proxy (optional if there is a firewall between the plain HTTP adapter and the receiver system)
    Authentication data for the receiver system, see also: transaction Display and Maintain RFC Destinations (SM59)
    Specify the RFC destination.
    Parameters from the Communication Channel for Technical Routing
    ●      Content type (the entry text/XML is expected as default)
    Specifies the content format  (payload) that the message should have.
    ●      (Optional) header fields for the receiver-specific protocol
    ●      Select Additional Query String Attributes:
    ○       Sender party
    ○       Sender service
    ○       Receiver interface
    ○       Message ID
    ○       Quality of service
    ○       Queue ID
    The queue ID is only required if the quality of service is EOIO.
    ●      Specifications for payload manipulation
    ○       XML code (default UTF-8)
    Specifies the character set.
    ○       URL escaping
    Presents the XML in a URL-enabled format.
    Special characters that could be interpreted as control characters are replaced with escape characters (masked).
    ○       Prolog
    Enhances the payload for particular servers (optional, see below).
    ○       Epilog
    Enhances the payload for particular servers (optional, see below).
    Adapter-Specific Message Attributes
    ●      To evaluate adapter attributes in the message header of the XI message, select Set Adapter-Specific Message Attributes.
    ●      If you want missing message attributes to trigger an error message, select Fail If Adapter-Specific Message Attributes Missing.
    If the indicator is set and the header for adapter-specific message attributes or one of the set attributes is missing from the message, this leads to a system error (red flag).
    If you do not set the indicator, and message attributes are missing, the adapter accesses information from the adapter configuration.
    ●      If you want to use an HTTP destination or URL set by the mapping, select URL orHTTP Destination.
    (The indicator displayed depends on the Addressing Type you selected above). If you set the indicator, the URL or HTTP destination set dynamically is called by HTTP.
    If the message header does not contain the URL or the HTTP destination, and you have set the Fail If Adapter-Specific Message Attributes Missingindicator, the XI message is set to status System Error.
    If you do not set the indicator, the URL or HTTP destination defined statically in the communication channel is used.
    The technical names of the fields are:
    ○       URL: TargetURL
    ○       HTTP Destination: HTTPDest
    ●      If you want to use HTTP header fields, select Apply HTTP Header Fields and enter the fields in Field 1 to Field 6.
    The fields are embedded in the HTTP request under the names you enter here.
    The technical names of the fields are HeaderFieldOne, .... HeaderFieldSix.
    ●      If you want to use URL parameters, select Apply URL Parameters and enter the parameters in the fields Parameter 1 to Parameter 6.
    The parameters are included in the HTTP request under the names specified here.
    The technical names of the fields are URLParamOne, u2026, URLParamSix.
    ●      If you want to save HTTP header fields from the synchronous response in the XI message header, choose HTTP Header Fields (Synchronous Response) and enter the fields in the fields Field 1 to Field 6.
    The fields must have the same names as the fields that are also to be sent in the HTTP response.
    The technical names of the fields are HeaderFieldOne,...,HeaderFieldSix.
    ●      The attribute namespace for the adapter is http://sap.com/xi/XI/System/HTTP.

Maybe you are looking for

  • I am unable to fully connect to a wireless hot spot with Z10

    I am unable to fully connect to a wireless hot spot at work with my z10. We use Cisco access points. Once connected to the AP, users are redirected to https://2.2.2.2/login.html this page allows users to type a username and password and then click a

  • PO print before last release

    Hi guru, i need help to allow PO print by ME9F tcode, before last release. there is an abap way for solve it? I try by customizing but it's not possible. eg i've got 4 release step and I want to print after the 3rd but before the 4th.

  • Other network iCall users cannot see my iPhone cloud

    Hi, When I work with iCal on my G5 it shows my workstation agenda called 'Agenda David'. Above it shows 'Agenda David iPhone'. 'Agenda David' will not sync with 'Agenda David iPhone. So I won't use 'Agenda David', only my iPhone iCal agenda. This way

  • Archivelink - how to set valid in only some clients, not in others?

    Hi, We’re building an ASP-solution, where storage of outgoing documents will be an optional service, where the customers that choose to use the functionality will have to pay for it. Each customer will run in a separate client in the same instance. N

  • For those concerned:  The iSight camera is lower quality.

    I really do not care, but it is noticeably "softer" or less focused/clear than the MBP or my iMac.