HTTPS Sender Configurations

Hi All,
What are the configurations that are to be done in PI to accept an HTTPS request from an external system  and send back a response . The receiving side would be and SAP system - BAPI. So it is a Synchronous interface .
Do i have to get the certificate of encyrption used by  the sending system  and load it in XI BOX using the transaction STRUST.
Do i have to create a seperate service in smicm for accpeting an incoming HTTPS connection
How far is the URL going to different from that of a plain HTTP Connection
What else has to be done
Please give your suggestions
Thanks & Regards,
Rahul

HI Rahul
You need to have a service user that can post on the URL
You can use both HTTPS without client authentication as well as with authentication.
Posting to the URL don't need to install certificates.
URL will be similar to Plain HTTP
Queries entering the plain HTTP adapter must have the following syntax:
http://<hostname:port>/<path>?<query-string>
The query string contains the following data:
&#9679;      Sender namespace ?namespace=<namespace>
&#9679;      Sender interface &interface=<interface>
&#9679;      Sender service &service=<service>
&#9679;      Sender party (optional) &party=<party>
&#9679;      Sender agency (optional) &agency=<agency>
&#9679;      Sender scheme (optional) &scheme=<scheme>
If you do not enter values for agency and scheme, the following default values are used:
&#9675;       agency=http://sap.com/xi/XI
&#9675;       scheme=XIParty
&#9679;      Quality of Service (BE, EO, or EOIO) (optional) &qos=<EO|BE|EOIO>
Thanks
Gaurav Bhargava

Similar Messages

  • Refresh HTTP Sender configuration without reboot on MDM 2.0.1

    Hello,
    I've noticed that when I try to change a XAI HTTP Sender parameter (i.e. HTTP URL 1), the new parameter does not take effect until the server is restarted.
    Is there anyway to refresh the Sender configuration without restarting the server?
    Thanks.

    That's the reason you use 'MPL Refresh Sender' option, to release/refresh all the Sender definitions. Make sure to provide the correct port number.

  • How to configure the Http sender adapter

    Now i have look through the sap lib about the http sender adapter
    and i know the url is
    http://hostname:port/path?namespace=<...>
    &interface=<...>&service=<...>&cmd=T&loaderXML=< message object >&end=yes
    My questions are:
    1)the path in the URL is "/sap/xi/adapter_plain", if not, what is it?
    2)the message payload is right?
    any reply is appreciated
    Thank you very much

    Hi Leo,
    For a HHTP Scenario:
    DESIGN:
    1. Create DataTypes for source and Destinations. Create elements for all the text fields of your HTTP Client so that they can all be mapped into the destination file
    2. Create MessageTypes for the two datatypes.
    3. Create Message Interfaces. The One for HTTP is the sender, Asynchronous ( as no response is expected) and one for File is receiver, asynchronous.
    4. Do the mapping. It will be mostly a one to one mapping of the fields.
    5. Create the Interface Mapping.
    Configuration:
    1. Import your Business System under your Configuration Scenario.
    2. Create 2 communication channels. One for Http as a sender and one for your receiver say IDoc.
    Check these links for the configuration part.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    3. Do the Receiver Agreement for Idoc. HTTP doesn’t need a sender agreement.
    4. DO the Receiver Determination and Interface Determination.
    Weblog which talk about the same scenario:-
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
    aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
    (use case) and explained it...
    Check this SDN tv demo, it has detail of HTTP adapter setup.
    https://media.sdn.sap.com/SDNTV/main.asp?mediaId=107
    Refer to this link for adapter settings.
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
    You should also have a HTTP client to send message to XI. In the connecting parameters to XI u have to use the URL in the pattern mentioned . U have to give all the configuration details in the URL.
    If you give me your mail id or if you can mail me at [email protected], i can send you a HTTP CLIENT.....In which you need to view the source code and change the username and password to send message to XI.
    Regards,
    Abhy

  • How to Configure HTTPs sender communication in XI

    Hi,
    I have a request for new interface setup, in which i need to configure HTTPs sender communication from a B2B server to SAP system. Scenario is to receive XML 0rders from HTTPs B2B system and convert to Idoc and post it to SAP.
    Please could some one help on what needs to be done in XI for receiving XML order files from a HTTPs connection and what further needs to be done for processing to Idoc.
    Thanks in advance,

    HI,
    For testing purpose you can use the HTTP client and paste your payload.
    Refer the below pdf for HTTP client what you do is copy and paste the code in note pade and save as .html file.
    This link gives you a sample HTML code to create HTTP Client:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
    Thnx
    Chirag Gohil

  • AS2 over HTTP Send port question.

    I have an application that builds and  sends flat and EDI files to FTP, FILE, SqlAdapter send ports and now they want AS2 over an HTTP port, I understand the AS2 settings (using party resolution, etc.) what I don't get is how/what exactly is receiving
    the message on the other side... They don't have a web service nor a page, I created a site to test but what do I do? Send an edi file to a url????
    Bico Bielich

    From your question I understand, you have been asked to send message through AS2. Do they also going to receive message through AS2 from their party? Is your question is about how to receive the message through AS2 which you also want to send over AS2?
    You can configure
    BTSHTTPReceive.dll to receive messages over HTTP and configure the Receive location with AS2 EDI pipeline component to receive messages over AS2 into BizTalk which can be subscribed by your send port filter or Orchestration ( if you have any process
    to be applied before sending the message over AS2 send).
    Check the Tutorial-3 part of AS2 which illustrate an example which receives an AS2 message through BTSHTTPReceive.dll. 
    Tutorial 3: AS2 Tutorial
    And following references shall help you configure the BTSHTTPReceive.dll:
    How to Configure IIS for an HTTP Receive Location
    Configuring BTSHTTPReceive.dll to work on IIS 7 
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • OTA-HTTP-SEND-401 Error

    Hi,
    We're getting a 401 error message from a Trading Partner (TP). They say there is no password required to get to their website. From their end, the request doesn't send a certificate with it. The TP certificate has 2048 keysize, while the wallet and our other TPs have 1024 keysize.
    Could the problem be with the transport endpoint or the TP certificate?
    Here is the error from the b2b.log:
    2009.05.05 at 15:06:03:520: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Invoking PackMessage
    2009.05.05 at 15:06:03:520: Thread-15: B2B - (DEBUG) MimePackaging:pack:Enter
    2009.05.05 at 15:06:03:525: Thread-15: B2B - (DEBUG) MimePackaging:createMimeMessage:Enter
    2009.05.05 at 15:06:03:535: Thread-15: B2B - (DEBUG) MimePackaging:createMimeMessage:number of pc components: 1
    2009.05.05 at 15:06:03:535: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:Enter
    2009.05.05 at 15:06:03:560: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:header name-value: Content-Type-application/EDI-X12; name=004010
    2009.05.05 at 15:06:03:560: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:header name-value: Content-Disposition-attachment; filename=004010
    2009.05.05 at 15:06:03:561: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:header name-value: Content-Transfer-Encoding-binary
    2009.05.05 at 15:06:03:562: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Enter
    2009.05.05 at 15:06:03:562: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Exit
    2009.05.05 at 15:06:03:563: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:Exit
    2009.05.05 at 15:06:03:690: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:03:691: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:03:785: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Enter
    2009.05.05 at 15:06:03:786: Thread-15: B2B - (DEBUG) MimePackaging:createSignedMimeBodyPart:Enter
    2009.05.05 at 15:06:03:787: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Entering...
    2009.05.05 at 15:06:03:788: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Leaving...
    2009.05.05 at 15:06:03:788: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setSignatureAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:03:788: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setSignatureAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:03:789: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:03:789: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:03:789: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign Entering...
    2009.05.05 at 15:06:03:790: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign Sign using the configured certificate
    2009.05.05 at 15:06:03:790: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign wrl: /hub02/app/oracle/product/64bit/OAS101/Apache/Apache/conf/ssl.wlt/default
    2009.05.05 at 15:06:03:802: Thread-15: B2B - (DEBUG) Utility:getPrivateKey:Enter
    2009.05.05 at 15:06:04:928: Thread-15: B2B - (DEBUG) Utility:getPrivateKey:matching private key found
    2009.05.05 at 15:06:04:931: Thread-15: B2B - (DEBUG) Utility:getPrivateKey:Exit
    2009.05.05 at 15:06:04:964: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Entering...
    2009.05.05 at 15:06:04:964: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Leaving...
    2009.05.05 at 15:06:04:965: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Entering...
    2009.05.05 at 15:06:04:965: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Leaving...
    2009.05.05 at 15:06:04:965: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: encode Entering...
    2009.05.05 at 15:06:04:966: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: encode Leaving...
    2009.05.05 at 15:06:04:967: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign Leaving...
    2009.05.05 at 15:06:04:967: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: printErrorInfo Entering...
    2009.05.05 at 15:06:04:968: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: printErrorInfo Leaving...
    2009.05.05 at 15:06:04:982: Thread-15: B2B - (DEBUG) MimePackaging:createSignedMimeBodyPart:Exit
    2009.05.05 at 15:06:04:982: Thread-15: B2B - (DEBUG) MimePackaging:createEncryptedMimeBodyPart:Enter
    2009.05.05 at 15:06:04:985: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Entering...
    2009.05.05 at 15:06:04:985: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Leaving...
    2009.05.05 at 15:06:04:986: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:04:986: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:04:987: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionCertificate Entering...
    2009.05.05 at 15:06:04:988: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Entering...
    2009.05.05 at 15:06:04:988: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Leaving...
    2009.05.05 at 15:06:04:989: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Entering...
    2009.05.05 at 15:06:04:989: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Leaving...
    2009.05.05 at 15:06:04:989: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: decode Entering...
    2009.05.05 at 15:06:04:997: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: decode Entering...
    2009.05.05 at 15:06:04:997: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionCertificate Leaving...
    2009.05.05 at 15:06:04:997: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: encrypt Entering...
    2009.05.05 at 15:06:05:006: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: encrypt Leaving...
    2009.05.05 at 15:06:05:007: Thread-15: B2B - (DEBUG) MimePackaging:createEncryptedMimeBodyPart:Exit
    2009.05.05 at 15:06:05:007: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Exit
    2009.05.05 at 15:06:05:008: Thread-15: B2B - (DEBUG) MimePackaging:createMimeMessage:Exit
    2009.05.05 at 15:06:05:013: Thread-15: B2B - (DEBUG) MimePackaging:getMimeContent:Enter
    2009.05.05 at 15:06:05:014: Thread-15: B2B - (DEBUG) MimePackaging:getMimeContent:Exit
    2009.05.05 at 15:06:05:014: Thread-15: B2B - (DEBUG) MimePackaging:pack:Exit
    2009.05.05 at 15:06:05:019: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Invoking Pre-Transmit
    2009.05.05 at 15:06:05:019: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Enter
    2009.05.05 at 15:06:05:020: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Log & Update Database Tables
    2009.05.05 at 15:06:05:020: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Update the Message Table Row with message state Wait for Incoming Acknowledgment
    2009.05.05 at 15:06:05:021: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Create a Native Event Table row for outgoing Request Message
    2009.05.05 at 15:06:05:021: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(3 params) Enter
    2009.05.05 at 15:06:05:023: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:insertNativeEvtTblRow msgInfo.id = <1396700:0:221@096997515>
    2009.05.05 at 15:06:05:023: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:protocl id set A
    2009.05.05 at 15:06:05:024: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:insertNativeEvtTblRow protocolCollabId = null
    2009.05.05 at 15:06:05:357: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:05:357: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
    2009.05.05 at 15:06:05:366: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
    2009.05.05 at 15:06:05:387: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:05:388: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: createWireMessage
    2009.05.05 at 15:06:05:408: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: createWireMessage
    2009.05.05 at 15:06:05:408: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(3 params) Exit
    2009.05.05 at 15:06:05:419: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:05:420: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
    2009.05.05 at 15:06:05:431: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
    2009.05.05 at 15:06:05:432: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Create Event Table row for Message Retries
    2009.05.05 at 15:06:05:433: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit timeToAck = Wed Dec 31 18:00:00 PST 1969
    2009.05.05 at 15:06:05:437: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Enter
    2009.05.05 at 15:06:05:463: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Event Type = 2
    2009.05.05 at 15:06:05:463: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow EventId = 12
    2009.05.05 at 15:06:05:463: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Id = 1396700:0:221
    2009.05.05 at 15:06:05:468: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Exit
    2009.05.05 at 15:06:05:472: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Current TimeStamp isTue May 05 15:06:05 PDT 2009
    2009.05.05 at 15:06:05:473: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Retry shall happen at Tue May 05 17:06:05 PDT 2009
    2009.05.05 at 15:06:05:473: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit business transaction info name null revision null
    2009.05.05 at 15:06:05:474: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Exit
    2009.05.05 at 15:06:05:474: Thread-15: B2B - (DEBUG) DBContext commit: Enter
    2009.05.05 at 15:06:05:482: Thread-15: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.05.05 at 15:06:05:483: Thread-15: B2B - (DEBUG) DBContext commit: Leave
    2009.05.05 at 15:06:05:483: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Calling Send to transmit the message
    2009.05.05 at 15:06:05:484: Thread-15: B2B - (DEBUG) Protocol Name: HTTPS
    2009.05.05 at 15:06:05:484: Thread-15: B2B - (DEBUG) Version Name: 1.1
    2009.05.05 at 15:06:05:484: Thread-15: B2B - (DEBUG) Endpoint: https://tp.com:88/invoke/tp.receive/as2
    2009.05.05 at 15:06:05:485: Thread-15: B2B - (DEBUG) using SSL
    2009.05.05 at 15:06:05:486: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send URL: HTTPS://TP.COM:88/INVOKE/TP.RECEIVE/AS2
    2009.05.05 at 15:06:05:487: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send TO Endpoint: 502 https://tp.com:88/invoke/tp.receive/as2
    2009.05.05 at 15:06:05:487: Thread-15: B2B - (DEBUG)
    Protocol = HTTPS
    Version = 1.1
    Transport Header
    Content-Transfer-Encoding:binary
    Message-ID:<1396700:0:221@096997515>
    MIME-version:1.0
    Receipt-Delivery-Option:https://b2bserver.edu:55/b2b.IP_OUT_QUEUE
    From:096997515
    Disposition-Notification-To:[email protected]
    AS2-To:ZZ043073964T
    User-Agent:AS2 Server
    Date:Tue, 05 May 2009 22:06:01 GMT
    Disposition-Notification-Options:signed-receipt-protocol=required, pkcs7-signature; signed-receipt-micalg=required, sha1
    AS2-From:096997515
    AS2-Version:1.1
    Content-Type:application/pkcs7-mime; smime-type="enveloped-data"
    Connection:close
    Parameters
    -- listing properties --
    http.sender.timeout=0
    2009.05.05 at 15:06:05:847: Thread-15: B2B - (DEBUG) scheme null userName null realm null
    2009.05.05 at 15:06:07:519: Thread-15: B2B - (WARNING)
    Message Transmission Transport Exception
    Transport Error Code is OTA-HTTP-SEND-401
    StackTrace oracle.tip.transport.TransportException: [IPT_HttpSendError] HTTP encounters send error :401
    at oracle.tip.transport.TransportException.create(TransportException.java:91)
    at oracle.tip.transport.basic.HTTPSender.createTransportResponse(HTTPSender.java:748)
    at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:560)
    at oracle.tip.transport.b2b.B2BTransport.send(B2BTransport.java:284)
    at oracle.tip.adapter.b2b.transport.TransportInterface.send(TransportInterface.java:837)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1666)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:900)
    at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1082)
    at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:126)
    at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:331)
    at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:206)
    2009.05.05 at 15:06:07:520: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Error in sending message
    2009.05.05 at 15:06:07:520: Thread-15: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Request Message Transmission failed
    2009.05.05 at 15:06:07:521: Thread-15: B2B - (DEBUG) DBContext beginTransaction: Enter
    2009.05.05 at 15:06:07:521: Thread-15: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2009.05.05 at 15:06:07:522: Thread-15: B2B - (DEBUG) DBContext beginTransaction: Leave
    2009.05.05 at 15:06:07:523: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab [IPT_HttpSendError] HTTP encounters send error :401
    [IPT_HttpSendError] HTTP encounters send error :401
    2009.05.05 at 15:06:07:532: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:07:533: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
    2009.05.05 at 15:06:07:540: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
    2009.05.05 at 15:06:07:540: Thread-15: B2B - (DEBUG) DBContext commit: Enter
    2009.05.05 at 15:06:07:543: Thread-15: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.05.05 at 15:06:07:544: Thread-15: B2B - (DEBUG) DBContext commit: Leave
    2009.05.05 at 15:06:07:544: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
    2009.05.05 at 15:06:07:545: Thread-15: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
    ***** REQUEST MESSAGE *****
    Exchange Protocol: AS2 Version 1.1
    Transport Protocol: HTTPS
    Unique Message ID: <1396700:0:221@096997515>
    Trading Partner: ZZ043073964T
    Message Signed: RSA
    Payload encrypted: 3DES
    Attachment: None
    ***** REQUEST MESSAGE *****
    2009.05.05 at 15:06:07:546: Thread-15: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Exit
    2009.05.05 at 15:06:07:546: Thread-15: B2B - (DEBUG) DBContext commit: Enter
    2009.05.05 at 15:06:07:546: Thread-15: B2B - (DEBUG) DBContext commit: Leave
    2009.05.05 at 15:06:07:548: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppInterfaceListener:onMessage processOutgoingMessage was successful, returning transport ACK to the transport layer
    Thankyou,
    Lavar

    When I telnet to the host, I get (Connection to tp.com closed by foreign host.
    I went to the TP URL and save the certificate as Base 64. I then loaded that into my wallet as a Trusted Certificate.
    I see TP.com in the wallet as a Trusted Certificate with an expiration date of July 28, 2010 and Key Size 2048.
    We still get the same 401 error message. The TP is saying that we are not receiving a certificate on their end. I guess that means there is a problem with encoding and encryption.
    I loaded the TP Verisign certificate into my browser as a CA Root.
    Now I get a pop up box, when I go to the website that wants me to choose a digital certificate.
    There are not any digital certificates to choose from, so I can only click OK or Cancel.
    After clicking OK or Cancel, I get prompted for a password.
    There seems to be trust isses between our server and the TP's server. :)
    I asked the trading partner to send me their Root certificate, in case they have a different Verisign certificate.
    Thank you,
    Lavar

  • HTTP Sender and HTTP Receiver adapter. Pls advice urgent

    Hi All,
    There is one Third Party that wants to send XML data and receive XML data with XI.
    Please let me know can I use HTTP for that.
    How to use HTTP Sender part?
    How to use HTTP Receiver Adapter?
    Pls send blogs/doc for that
    Thanks and Regards

    hi.,
    Check this thread for the code for a HTTP Client,
    /message/266750#266750 [original link is broken]
    Also, check these blogs. They use HTTP adapters for their configuration,
    /people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
    /people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    Check these links for the configuration part.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    Weblog :
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
    aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
    note:reward points if solution found helpfull.....
    regards
    chandrakanth.k

  • URL in HTTP sender adapter

    Hi,
    I have a scenario where I want to configure a HTTP sender adapter.
    I have a HTTP PUT url of a 3rd party application from where the HTTP adapter should poll and pull the files into PI.
    Is this possible? If yes, where and how do I mentioon the URL?
    Please help!
    Thanks,
    Pratibha.

    Hi,
    That means, the sender aplication has to write a http://<hostname:port>/<path>?<query-string> type query?
    Is there no other option?
    Is it not possible with the SOAP sender adapter also?
    Thanks,
    Pratibha.

  • HTTP Sender - how to read URL Parameter USER id into Mapping

    Hi,
    My scenario is HTTP - XI - ABAP Proxy.
    I wanted to capture USER id of the person who posted(HTTP) into XI(Mapping). How to read/evaluate the value of sap-user from querystring of URL ?
    http://HOST:8008/sap/xi/adapter_plain?namespace=http%3A//abc.com/sales_oa&interface=MI_sales_OA&service=DEV_D&party=&agency=&scheme=&QOS=EO&<b>sap-user=SM9999</b>&sap-password=xxxxx&sap-client=001&sap-language=EN
    please help.

    Mallik,
    Try  URL Parameters in HTTP sender communication channel.
    In the sender communication channel set Adapter Specific Message Attributes. Click on Apply URL Parameters. In Parameter1 put sap-user (U can query any URL parameter by giving its name as in the HTTP URL).
    Now in SXMB_MONI, in inbound payload SOAP Header, under Dynamic configuration u can see the value of the user. Query the same in Mapping using Dynamic Configuration using keyName as UrlParamOne.
    Regards,
    Sudharshan N A
    Message was edited by:
            Sudharshan Aravamudan

  • HTTP sender adapter and receiver adapter

    Hi guys,
    I have a scenario that I have to communicate with an HTTP server with XML over HTTP.
    When the communication is opened by me I will use an HTTP receiver adapter and give the connection parameters.
    a) Do I have to use a different HTTP receiver communication channel for each different type of XML that I want to send??
    b) When the communication is opened from the HTTP server, they have to type the URL in order to invoke the correct scenario on my side, right? I know that I do not have to use an HTTP sender adapter. They have to call the http URL, followed by the sender business system, sender interface name/namespace etc.
    That means that the URL in the format: http://XIhostname:port/ is not enough right?
    Is there a way to figure out from the type of the XML sent which scenario will be executed in XI?
    Because it is difficult for them to use different URL when they are sending me different type of XML's, i.e. different requests.
    Evaggelos

    >>Do I have to use a different HTTP receiver communication channel for each different type of XML that I want to send??
    Yes,receiver adapter is linked to receiver agreement,if you have different inbound interfaces then it means you need to have diferrent receiver agreement,hence different receiver communication channels.
    >>That means that the URL in the format: http://XIhostname:port/ is not enough right?
    No,its not,there is a test tool on SDN called "HTTP test tool".just search for that and download on your desktop,it will help you generate the correct URL as well as test the scenario by sending sample HTTP request.
    One thing you need to keep in mind is that HTTP scenarios don't require and sender communication channel or sender agreement.they only need configurations on receiver side
    Thanx
    Aamir
    FYI:Here is the test tool
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
    Edited by: Aamir Suhail on Jul 3, 2008 12:18 PM

  • HTTP Sender Adapter parameters

    Hi,
    I'm doing the HTTP to IDoc Scenario.
    Receiving side is SAP ECC through receiver IDoc.
    Third party system, they are asking to give the URL, so that they will include that URL in their program & it will post to SAP.
    Can anybody guide me on this.. what parameters i've to get from the third party and what preparations i've to do in XI & ECC 6.0, so that i can give proper inputs to them.
    And if sender CC is HTTP, any receiving IDoc CC configuration is required? Pls let me know the steps hw to proceed on this.
    Thanks in Advance.
    rgds,
    balu

    HI
    Sender HTTP
    You need to have a sap user for the third party in PI to post content on HTTP sender adapter channel
    URL that you need to give to third party vendor
    http://<hostname:port>/<path>?namespace=<namespace>&interface=<interface>&service=<service>(optional) &party=<party>(optional) &agency=<agency>(optional) &scheme=<scheme>(optional) &qos=<EO|BE|EOIO>
    Receiver IDOC
    Create RFC destination in SM59 for R3 system.and port in IDX1 for R3 system
    IDX2 Improt IDOC metadata.
    Thanks
    Gaurav

  • HTTP Receiver To HTTP Sender

    Hello,
    i have the following scenario:
    System A  --> [XI1 -> http-receiver] -
    > [ http-sender --> XI2]
    So i send an IDoc from A to my XI1 and then i want to send it with the http-receiver to
    the http-sender of an other XI2.
    In my http-receiver i want to use a rfc-connection.
    The adress of the http sender is something like:
    http://xisystem:8000/sap/xi/adapter_plain?interface=INVOIC.INVOIC01&service=BS_HTTP_SENDER...
    My question is how can i configure the parameters like 'service' from the sender in the http-receiver.
    Thanks and regards
    Patrick

    Hi Patrick,
    as URL parameter of the http-address, you have it there: sercice=BS_HTTP_SENDER. You need as well parameter interface, namespace and QOS=EO. The rfc destination will give you a warning for that - ignore it.
    Regards,
    Udo

  • Clarification for HTTP and HTTPS Sender Adapter

    Hello together,
    after some investigating concering scenarios with HTTP and HTTPS sender there are still some points that are not absolutely clear for me.
    I know that it is not necessary to configure an HTTP sender communication channel. However if I want to enforce HTTPS sender communication I think I need to add an HTTP sender communication channel with security settings enabled as well as a sender agreement.
    To my understanding these settings are activated on the Adapter Engine (Java Stack), HTTP requests however call the ABAP stack directly. How does this work exactly?
    Thank you very much for your additional explanation.

    Hi,
    see below is the format for HTTP URL
    http://<hostname:port>/<path>?<query-string>
    now query straing can only have values as given in the below link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    a way around can be to specify the payload for &party or &agency or &schema(if you are not using them) but then XI should be able to identify them correctly(which i m not sure how it will do),secondly the length can be a constraint coz if you add the whole payload ,the URL will become really long.
    so i would suggest you not to use it but if you really have to,then explore it properly first and then only use
    plz reward points
    thnq

  • Enabling SSL for HTTP Sender Adapter

    Hi Experts,
    I'd like to have a step by step process in enabling HTTPS for Plain_HTTP Sender Adapter. I've already read the enabling HTTPS on SAP Help, but it does not provide much detail. Would the steps be the same for enabling HTTPS for Plain_HTTP Receiver which are:
    1. Install the certificates using STRUST
    2. Configure an RFC Destination using SM59
    3. Call your RFC Destination in Receiver HTTP Adapter (not valid for http sender adapter)
    The connection for setting up http is http://<hostname>:port/<path>?<query string>
    but what about https? Would it be connecting to the webdispatcher first?
    Hope you can help me,
    Regards,

    Hi,
    as HTTP Adapter is on ABAB stack you will need to configure with STRUST.
    http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
    The URL should start then with https, but you could test with this sample client:
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
    Regards
    Patrick

  • Http sender adapater

    Hi All
    when I am trying to send request through url for http sender adapter configuration between CLM(E-sourcing) system and PI, I am getting the following error.
    Can any body help me out to resolve this issue.
    The scenario is CLM - PI - SRM (HTTP - RFC scenario). CLM is the sender system and SRM is the receiver system.
    I have checked each and every parameter in the url.
    URL:
    http://usaoadbld004:50000/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_OA&service=CLM_BUSINESS_COMPONENT&QOS=BE&sap-user=PIAPPLUSER&sap-password=&sap-client=001&sap-language=EN.
    Error:
    E-Sourcing was unable to publish Red Book Agreement to SRM. class java.io.IOException Server returned HTTP response code: 500 for URL: 
    Thanks & Regards
    MGREDDY

    Can u check following:-
    1. URL used for sending message to PI.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/frameset.htm
    2. check HTTP port from SMICM tcode - Go- Services and use the same one.
    chirag

Maybe you are looking for