HTTPS Receiver

Hi,
I am trying to configure scenario IDOC->XI->HTTPS.
I have HTTP adapter at receiver side.
But I could not find any configuration for HTTPS in communication channel in Integration Directory.
You can configure URL or HTTP Destination there.
I think I need to configure HTTP Destination in SM59 for HTTPS of Type G and provide following security parameters.
Logon Procedure - No Logon
SSL - Active
But I dont know what should I provide in SSL Client certificate.
Is it possible to configure HTTPS in this way? if yes , Can somebody give steps to enable SSL on XI?
Also I would like to know if I can use SOAP Adapter by checking do not use SOAP Envelope for this scenario.
There is no web service at receiver end.
Thanks,
Beena.

Hi,
Thanks for help.
Issue Resolved.
We created HTTP Destination of Type G and created PSE of type anonymous SSL client and import certificate there.
I tried option of using 'Do not use SOAP Envelope' in Soap adapter and configured https URL there but it didnt work.
Thanks,
Beena

Similar Messages

  • PI 7.11 - Sync HTTP receiver adapter with response XML file

    Hi
    We have a File to HTTP scenario in which we need a sync HTTP interface. We send a file to the HTTP address and receive a XML acknowledge. As I read in this forum: sync HTTP interfaces are not possible with the "standard" HTTP adapter. So I found an entry which recommended to use the SOAP adapter instead.
    I configured it:
    - Do Not Use SOAP envelope
    - modules: RequestResponseBeans, CallSapAdapter, ResponseOneWayBean
    If i use this scenario, i get following error in the RWB - Message Display Tool:
    Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method com.sap.engine.interfaces.messaging.api.Message.getMessageId() of an object loaded from local variable 'message1'.
    I testet this scenario using CURL and it worked properly. Should this kind of scenario work with the SOAP adapter or do I need to buy/develop an own adapter? Is in NW7.3 possible to configure sync HTTP scenarios?
    Thanks in advance
    Michael

    Hi
    actually i use a simple HTTP receiver CC with the setting "XI Payload in HTTP Body" to send a XML datafile to a webpage (java servlet). This part works fine by now. But, this servlet would also send back a status information to the state of the received datafile, which I like to catch.
    e.g. HTTP response from the servlet (catched using CURL):
    HTTP/1.0 403 Forbidden
    Server: Apache-Coyote/1.1
    X-Powered-By: Servlet 2.4; JBoss-4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)/Tomcat-5.5
    Set-Cookie: JSESSIONID=OALHMomjR9TVgIATi8SrPQ**.ajp13_ls_1; Path=/ls
    Content-Type: text/xml
    Date: Tue, 06 Mar 2012 16:19:56 GMT
    X-Cache: MISS from proxy.xxxx.com
    Via: 1.0 proxy.xxxx.com:xxxx (http_scan/4.0.2.6.19)
    Proxy-Connection: close
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?><!DOCTYPE transportordersfromls [ <!ELEMENT transportordersfromls (userid, clntid, msgid, (transportorderfromls+ | error))> <!ATTLIST transportordersfromls vers CDATA #REQUIRED> <!ELEMENT userid (#PCDATA)> <!ELEMENT clntid (#PCDATA)> <!ELEMENT msgid (#PCDATA)> <!ELEMENT transportorderfromls (refid, status)> <!ELEMENT refid (#PCDATA)> <!ELEMENT status (ok | error+)> <!ELEMENT ok EMPTY> <!ELEMENT error EMPTY> <!ATTLIST error reason (XMLError | SystemNotAvailable | ApplicationError | OTHER) #REQUIRED message CDATA #REQUIRED> ]>
    <transportordersfromls vers="1.0">
        <userid/>
        <clntid>XXXXX</clntid>
        <msgid>0</msgid>
        <error reason="OTHER" message="Access denied"/>
    </transportordersfromls>
    Michael

  • Assign a dynamic value to a field in HTTP receiver header without IR part

    hi experts,
        I am doing a scenario in which i am to add a header  field in http receiver, whose value will vary for each transaction. and the value will be same as sender file name.
    But this all I am to do without doing Repository part.(i.e. No message interface and no mapping)
    Is it possible?  If yes help me out.
    "Useful effort will be appreciated"....
    Thanks

    Hi Jaideep,
       Hpoe the below link will help you.
    Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
    Regards,
    Leela

  • Not able to see 'Adapter specific' indicator in http receiver comm. channel

    I am not seeing the Adapter Specific Message attributes indicator in http receiver adapter where one can set a dynamic URL. Anybody any idea? Thanks.

    I have a fixed URL except that it should be formed with https instead of http. I guess the default http is used as there is no where in the communication channel to select https. I am able to invoke the https url through browser but through http receiver adapter, I get error 'http client code 110 reason'. I see in other blogs that this is due to https not enabled in the J2EE engine. But for outbound why should that matter? As long as the target URL is set to accept https, I should be able to sent the message as long as the URL gets formulated starting with https. If it was SOAP adapter, the entire URL can be entered so no issue, but with http adapter is there a way to specify entire URL including the https:// ? Thanks.

  • HTTP Receiver Adapter - delete ?xml version="1.0" encoding="UTF-8"?

    Hi,
    Is it possible to delete the part below when sending an HTTP request through HTTP receiver adapter without any java/abap/xslt mapping?
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_SELL xmlns:ns0="http://test.com/Sell">
    Thanks
    Arman

    Hi,
    <?xml version="1.0" encoding="UTF-8"?>
    Specifies that the given message is xml
    <ns0:MT_SELL xmlns:ns0="http://test.com/Sell">
    Specifies its a MessageType of the payload, without this that message is not identifies and is not processed. Its manditory to have these. Other wise error will raise.
    Regards,
    Prasanna

  • Manipulate the URL in HTTP receiver adapter possible?

    hello together,
    i have an HTTP receiver adapter. To the parameters which i can tick in XI as default (sender  party, sender service, ....) i want to add some parameters too.
    who can i do that? i have read the weblog from william li. i tried to change the parameter link the comments at the end of the blog (see kurt rasmussen) but nothing happend..... the parameters are not available....
    can somebody help me?
    thanks a lot
    alex

    hello michal,
    yes, i did. i took the information from http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm and tried to put some special information to URL. nothing to see.
    is it mandatory to use a mapping to fill the URL parameter fields, isn't it??
    i am using a port sniffer to see the URL and the fields (parameters) in it.
    thanks a lot.
    alex

  • HTTP Receiver interface returns with error code 110

    Hi All,
    We are posting the document from XI to a external server as HTTPS request.
    We are able to sucessfully post the request to external server using HTTP destination as address type but not able to post sucessfully with URL as address type.
    Here goes the details -
    We are able to post the HTTPS request successfully on the external server using the HTTP destination as address type in HTTP receiver adapter setup.
    When we setup address type as HTTP destination , we need to provide the following details -
    IN SM59 , Connection type G
    Target Host : host name (  with out "https://"  as prefix)
    Service No : 443
    Path prefix : query string
    SSL : Active
    Certificate : Select the certifacte from the client certificate list.
    We can post the request to external server using URL as address type in HTTP receiver adapter setup.
    When we setup address type as URL , we need to provide the following details -
    Address type : URL Address
    Target Host : host name (  with out "https://"  as prefix)
    Service Number : 443 ( HTTPS port setup on XI)
    Path : query string.
    When we post the same request as we did with HTTP destination as Address type , we are getting a HTTP response code as failure HTTP response code 110
    Please find the details about the return code -
    If a cache returns a stale response, either because of a max-stale directive on a request, or because the cache is configured to override the expiration time of a response, the cache MUST attach a Warning header to the stale response, using Warning 110 (Response is stale).
    110 Response is stale
    MUST be included whenever the returned response is stale.
    Please find the error message from SXMB_MONI
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP client code 110 reason</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Please let me know if some one has faced this issue.
    Regards,
    Reddy
    Edited by: Nanda kishore Reddy Narapu Reddy on Mar 11, 2008 12:35 PM

    Hi All,
    Is some one can confirm that - We can use HTTPS with Address type as URL address in HTTP receiver adapter setup.
    I can confirm that using HTTP destination as Address type in HTTP receiver adapter setup we can attain HTTPS communication with external server.
    If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can guide me what are the steps need to be done.
    Address type is a parameter in HTTP adapter setup .
    Regards,
    Reddy

  • HTTP Receiver Adapter

    Hi,
    I am working on a scenario, where I am posting xml message on https url, for which I am using HTTP receiver adapter.
    I have created RFC destination of type 'G' in sm59 to make an https call, where I have provided following details:
    In Technical Settings:
    Target Host - <Hostname>
    Service No. - 443
    Path Prefix - <url path>
    Logon Security:
    SSL - Active
    SSL Client Certificate - Default SSL Client (Standard)
    UserName - <Username>
    Password - <Password>
    I have used this RFC destination in 'HTTP Destination' of HTTP receiver adapter.
    When I test this interface, I am getting this error.
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP client. Code 110 reason</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Can you please help me resolve this issue. Please let me know, if I am following the right steps.
    Thanks in advance
    Regards,
    Amit

    Hi -
    Since you're using the http destination option in the channel, you just specify the user/pwd in the destination.
    Regarding the issue, first, for the Logon/Security option in the destination, unless you'll be using a client certificate to authenticate, you should choose option ANONYM SSL Client (Anonymous) - you still provide the user/pwd in the Logon section.  Make sure you have imported the root cert of the CA verifying the server's identity into the client certificate list within STRUST (node SSL Client (Anonymous)).
    Also, for some hints on the issue, look at the ICM trace - tcode SMICM->Goto->Trace File...     you may need to increase the trace level - SMICM->Goto->Trace Level...    After resolving the issue, make sure to set the trace level back to default.
    Regards,
    Jin

  • HTTP RECEIVER QUERY

    hello everyone,
    I have to develop a synchronous scenario, SOAP Sender to HTTP Receiver.
    Soap sender will be passing suppose 2 fields Name and Employeeid and the Http receiver will be replying back the 
    response with entire employee details (name, id, address, dateofbirth, etc).
    Http receiver has to be accessed via a URL like 
    https://abc.com/test/servlet/ServletInterface?command=getdetails&emp_name=<Name>&emp_id=<Employeeid>
    This is an https request, henc an RFC destination needs to be configured in XI and SSL has to be activated but how will i add the parameters Name and Employeeid to the URL mentioned in the RFC destination.
    i went through many blogs on SDN, but i could not figure out how to append the URL mentioned in the Http Destination. Is it possible to do dynamic configuration with SSL enabled.
    i tried passing URL https://abc.com/test/servlet/ServletInterface?command=getdetails in the HttpDestination and also configured a mapping for dynamic configuration but with no success.
    please let me know if i am on the right track. if not please suggest.
    thanks in advance.
    Edited by: praveen kalwa on Feb 22, 2008 1:33 PM

    Hi,
    XI supports only PUT method of http request. While adding parameters to the addr string is considered as a GET method.
    Refer following blog in this regard.
    /people/amol.joshi2/blog/2006/06/28/must-fire-a-http-get-from-xi---try-this
    -Kavita

  • Http receiver channel works fine. SM59 gives an error

    Hi,
    I've set up HTTP receiver communication channel with the following details:
    addressing type       : URL address
    target host                : cl-test.zzzz.nl
    service number        : 20212
    path                          : /zz/servlet/runHXML?site=sap&thread=something
    authentication data   : use logon for NON sap system.
    When i send a message it arrives at the receiver side, and i get "succesfully processed" in the sxmb_moni.
    I want to use addressing type HTTP destination instead of URL address so i created an HTTP destination (type G) in SM59 with the same details.
    But when i perform the connection test i get an Internal Server Error
    (~response_line  HTTP/1.1 500 Internal Server Error)
    I tried replacing the target hostname with the ip-address, but still the same response.
    What can be wrong?
    Kr
    Robert

    Hello Robert,
    When you try to test the HTTP destination in SM59, XI send a HTTP Post to the target system but with no payload.
    In your case I assume that the Target System cannot process this message and hence triggers a Internal server Error - HTTP 500.
    Can you use this HTTP destination and try to test the working scenario end to end. This should work.
    Regards,
    Bhavesh

  • How to set HTTP header field "cookie" with http receiver adapter?

    Hi,
    I am using http receiver adapter (not axis) in a scenario. I could not set a parameter with key cookie in http header. Is there some kind of restriction to set it? I am able to set others like connection and create custom fields using ASMA and dynamic key configuration via UDF on mapping.
    Could you please comment on, is cookie http parameter special or noneditable by PI's http adapter? I am looking for a solution without editing any abap code...
    Regards,

    I believe it is possible since axis adapter provides very same functionality. Let me summarize my scenario may be it helps:
    I am trying to call series of webservice lets say in a BPM. First service (login service) will provide me with a session id (in http header with key Set-Cookie) then I will call another service which has that session id in its http header with key cookie then I am going to logout. So I am testing the second part now, but it doest let me send cookie http header parameter.
    I hope I clarified a bit more my problem.
    Regards,

  • HTTP receiver Adapter configuration

    Hi All,
    I want to post an XML message using HTTP Receiver Adapter for my BPM scenario (Idoc to HTTP service)
    The receiver has Oracle gateway and it expects message in following format.
    HTTP Header
       Http–Version: HTTP/1.1
       Authorization: Digest username=”myusername”,
                             realm=”[email protected]”,
                             nonce=”dcd98b7102dd2f0e8b11d0f600bfb0c093”,
                             uri=”/dir/index.html”,
                             qop=auth,
                             nc=00000001,
                             cnonce=”0a4f113b”,
                             response=”6629fae49393a05397450978507c4ef1”,
                             opaque=”5ccc069c403ebaf9f0171e9517f40e41”
                             Content–length: 12345
                             Content–type: text/html
    HTTP Body
       TRANSPORT_PROTOCOL=OXTA
       TRANSPORT_PROTOCOL_VERSION=1.0
       REQUEST_TYPE=SEND
       MESSAGE_ID=A1234567890ZZ0987654321
       MESSAGE_TYPE=XML
       MESSAGE_STANDARD=OAG
       TRANSACTION_TYPE=PO
       TRANSACTION_SUBTYPE=PROCESS
       DOCUMENT_NUMBER=12345
       PARTYID=9999
       PARTY_SITE_ID=8888
       PROTOCOL_TYPE=HTTPS–OXTA
       PROTOCOL_ADDRESS=HTTPS://www.me.com/servlets/oracle.ecx.oxta.
       transportAgentServer
       USERNAME=myusername
       PASSWORD=myloginpassword
       ATTRIBUTE1=
       ATTRIBUTE2=
       ATTRIBUTE3=
       ATTRIBUTE4=
       ATTRIBUTE5=
       PAYLOAD=<xml ... ...>
    I think this is not a typical HTTP URL type of format, is it?
    And I am not sure how I can build the message. Where do I put the parameters like TRANSPORT_PROTOCOL, TRANSPORT_PROTOCOL_VERSION, REQUEST_TYPE etc in the HTTP adapter?
    Also is there any place where I can see the final actual XI message that is sent to HTTP service?
    Any help will be really appreciated.
    Thanks and regards,
    Rahul.

    Hi Rajeev,
    The receiver system should have the details about the content type it expects. I got that from the team who monitors our receiver system.
    The HTTP Body of HTTP adapter is made up of PrologPayloadEpilog.
    So I added the paramter list that receiver system expects as part of the Prolog. Refer to the HTTP body that I have posted in my earlier message. Out of that till ".....Payload=" is added to Prolog and XI then appends actual payload to it.
    To be precise -
    TRANSPORT_PROTOCOL=OXTA&TRANSPORT_PROTOCOL_VERSION=1.0&MESSAGE_TYPE=XML&MESSAGE_STANDARD=UNIVERSAL&TRANSACTION_TYPE=XXXE&TRANSACTION_SUBTYPE=ORDER_I&DOCUMENT_NUMBER=PO12345&PARTY_SITE_ID=ESAP_ORDER_I&USERNAME=***&PASSWORD=**&PAYLOAD=
    So in the end it worked out well.
    Cheers,
    Rahul.

  • Remove namespace alias for HTTP receiver adapter

    hello all,
    I have a scenario, IDOC->XML (HTTPS). Standard output of PI has ns0: as prefix for each xml tag (ns0 alias for namespace)
    I want to remove the namespace alias while preserving the namespace in the output. So removing namespace reference in external definition is not a option.
    Is there any way to use XMLAnonymizerBean for HTTP receiver adapter? What are other alternatives (java mapping)?
    Thanks,
    sachin

    Thanks stefan, prateek.
    Prateek: I checked this blog earlier. It talks about inbound processing. My scenario is outbound HTTP and I am not sure how I can use specific adapter service as mentioned in blog in outbound case as other scenarios are using standards adapter_plain service.
    Stefan: I will try this approach.
    regards,
    sachin

  • Https for SOAP and HTTP Receiver adapters in PI 7.1

    Hi,
    We need HTTPS Transport protocol is required to send the message to receiver systems.
    Currently we are using below procedures for https:
    1)     HTTP with SSL (= HTTPS) without client authentication
    2)      HTTP with SSL (= HTTPS) with client authentication
    But client donu2019t want this procedure.
    Here my question is How to enable the https Transport protocol in SOAP and HTTP Receiver adapters.

    >>Here my question is How to enable the https Transport protocol in SOAP and HTTP Receiver adapters.
    What I see is your client wants PI to send communication via HTTPS transport protocol. That means you have to apply for trusted certificate and import that certificate root node in Netweaver keystore.
    Then change the transport protocol from http to https in soap and http receiver communication channel and communicate to client via certificate authentication.
    Plenty of documents available in sdn about https certificate authentication. Please go through those links.
    check this thread.. might be helpful
    Client Certificate for PI authentication when Web Dispatcher terminates SSL

  • Dynamic URL for HTTP receiver adapter

    Hi all,
    when the XI send the http request to the target system, the format maybe like this:
    header + body the body is including: Prolog, payload and Epilog
    here is about the target system have a 'input' parameter(maybe string type)
    is it possible to pass the 'head + body' these value(or maybe the whole http request message) into input
    i mean is it possible to set the dynamic URL for http receiver adapter like this:
    http://host:port/path?input=<the header and body>
    i have searched the blog Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
    Link:[/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping]
    and the similar threads in the forum
    please give me some advice
    thanks in advance

    When a HTTP server requests the whole message as URL parameters, then I assume that the server also requests an HTTP GET, which is not supported by XI.
    Could you check this?
    Regards
    Stefan

  • Adapter specific properties (http receiver adapter)

    Hi,
    does anybody know the technical name for the HTTP destination of a http receiver adapter.
    The documentation lists only the names URLParamOne to URLParamSix and HeaderFieldOne to HeaderFieldSix.
    Neither the technical name for URL nor for a HTTP destiantion are mentioned.
    Regards,
    Marc

    Hello Moorthy,
    I know this part of the documentation.
    So I set the indicator within the communication channel.
    Now, I have to fill the dynamic configuration during my mapping. My code looks like following:
    DynamicConfigurationKey keyURL =  DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP", <b>XXXXX</b>);
    // access dynamic configuration
    DynamicConfiguration conf = (DynamicConfiguration) param.get (StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    // set value
    conf.put(keyURL, url);
    So what has to be filled instead of XXXXX ?
    Regards,
      Marc

Maybe you are looking for