HTTP Receiver Adapter payload as single line plain text with out any tags.

Hi PI experts,
I have a strange problem in http receiver adapter.
Sender RFC (SAP)  Receiver: HTTP.
Receiver system expects the output from XI in the below format in a single line plain text with out any tags in the payload. and the content type should be application/x-www-form-urlencoded
Group=Test&Sentinel=Web%20Server&Facility=5345&Order Number=XT-XWHM-Y-NA&Serial Number=123456&@LABEL_QUANTITY=5&@LABEL_NAME=111114_Q
Is there any way to achieve this using http receiver adapter. Business is not ready to accept the output from XI not even in a single element instead they only need it as a JUST a plain text.
Appreciate early response on this.
Thanks in Advance,
Jitender

Dear Ola,
Could you elaborate how you achieved in catching the response data from the receiver in case of HTTP receiver adapter?
The target service is not a WebService but some python script that must to receive some paramters via POST request.
     HOW can I post this parameters?
Here you entered the fields of the message type of the request in the header parameters of the receiver adapter? Thats fine.
But what about the message type and vice versa of the response from the receiver?
Regards
Rebecca

Similar Messages

  • HTTP Receiver Adapter: Payload in SXI Monitor

    Hi
    We have a scenario where System A is sending information by HTTP to SAP XI    (No Sender HTTP Adapter required). SAP XI is posting an Idoc in R/3 and sending back two fields to same sender.
    We have defined 2 Receiver determination, one for Idoc and another for response for the same sender. Further also seprate mapping program, Interface mapping and Message interface has been defined for them (No BPM is required).
    When we are running the test,everything goes successful and the incoming messages has two receivers, the Idoc is posted and also a response is send back to the sender system(which becomes receiver now). I can see successful flag for both of them and further the receiving system also is able to receive the response successfully, but I cannot see the response payload in Monitor for HTTP receiver, it shows the incoming payload and transformed Idoc after mapping, but it does not show the response message for HTTP receiver and only shows the incoming payload.
    How can I see the outgoing payload for the same (as HTTP Adapter does not exist on AE) and thus RWB - AE monitoring is not possible. Can someone help me out how to check the outgoing payload for HTTP receiver in Monitor.
    System A --> SAP XI --> SAP R/3 (IDoc)
                             I----
    >  System A (HTTP Receiver)
    BR / Swetank

    Hi
    I am not bothered about Idoc part. The sender is sending supposing 3 fields
    a,b,c. The idoc is posted with those two fields.
    And a message is again send to Sender system (Which now becomes receiver) with two fields only (a,b) that we have received this field A( order number). This is not transport acknowledgement, but a payload which is send back.
    Separate Mappings have been defined for Idoc and HTTP receiver and my query is that I cannot see the outgoing payload in monitor. Even though on verifying with the receiver system, they receive the actual transformed payload.
    So I do I see the outgoing payload in Monitor for HTTP receiver in Monitor ?
    BR / Swetank

  • Exporting to Tagged PDF: Why would every single line of text come out as a separate Span tag?

    I've inherited an InDesign file for which I have to generate a 508-compliant PDF. Normally this is pretty smooth with InDesign, and most issues have historically been pretty easy to fix.
    With this document, though, every single individual line is exporting to tagged PDF as a separate <Span> tag.
    I've turned off overrides and hyphenation, and looked for manual line breaks. I've also tried exporting it out to IDML and opening that, and the resulting PDF was no better.
    If anyone has an idea of whether there's some odd setting I'm missing that could explain why this is happening, that would be very helpful!

    Thank you for being so helpful and constructive.
    I tried to look at the ASDL settings, john46 but it's asking me for my HomeHub password... the only password I have is for our wireless network and that one doesn't work. 
    I can't test the phone line right now because I'll have to disconnect the internet and I'm currently working on another computer whilst chatting on this one with you. However I will do that later. I'll also look at the RogerB link you provided. 
    Truth is, we're pensioners who use the internet but we havent a grain of technical understanding between us. We're old fashioned enough to admit that we just want someone who knows what he's doing to come here and fix it for us. It's already cost us £130 for an engineer to come out from OpenReach to tell us the phone line is OK and it's the router causing the problem. Best case scenario is that another BT engineer who knows about broadband comes out and does it because the last BT person that I spoke to in Delhi did actually confirm that there is a fault on the BT side. I'm getting so frustrated right now I'll probably call out an independant I find in Yellow Pages and get charged an arm and a leg again and I'll then cancel with BT in a fit of pique.

  • Plain http receiver adapter question

    Guys,
    Is there any way to see the actual https request that I am sending out with the Plain http receiver adapter?
    I am getting back an application level error response, but not sure what is wrong with my message, I would like to see it the way it was sent out.
    I know about SMICM where I can look at the trace file but it doesn't show me the actual https request - unless I'm missing something.
    Thanks a lot,
    Viktor

    Have you tried with some sniffers like TCPGateway.
    /people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway
    Regards,
    Prateek

  • HTTPS communication using HTTP receiver adapter URL address as Address Type

    Hi All,
    If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can you please guide me what are the steps need to be done.
    Note : Address type is a parameter in HTTP adapter setup .
    Regards,
    Reddy

    Hi,
    Check this,
    Configurations in Integration Directory
    The plain HTTP adapter gives the receiver system the following specifications:
    &#151; Specifications for addressing using a URL address:
    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).
    &#151; Specifications for addressing using an HTTP destination:
    HTTP destination
    &#151; Parameters from the communication channel for technical routing
    Content type (the entry text/XML is expected as default)
    Specifies the format that the message contents (the payload) should have.
    Optional header fields for the receiver-specific protocol
    Attributes for the query string
    1. Sender party
    2. Sender service
    3. Receiver Interface
    4. Message ID
    5. Quality of service
    6. Queue ID
    All attributes are selected except for the queue ID. If you do not want a value to be
    transferred to the receiver, deselect it. The queue ID is only required if the quality of
    service is EOIO.
    Specifications for payload manipulation
    XML code (default UFT-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).
    Enhancing the Payload
    Regards
    Seshagiri

  • 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

  • SOAP receiver adapter - payload inside the soap envelop

    Hi,
    We have to send a SOAP message to 3rd party from PI 7.1. Using SOAP receiver adapter - we are trying to achieve this. 3rd party software is unable to accept payload as an attachment of the main envelop - they want it enside the main envelop.
    I tried with "Keep attachment" option - but PI still keping the payload as an attachment. I think this option is for handling "extra" attachment.
    Is there any way we can keep the payload inside the envelop?
    In run-time WB, at the moment envelop looks like
    <SOAP:Envelope xmlns:SOAP="http://schemas....
    <SOAP:Body>
    <sap:Payload xlink:type="simple" xlink:href="cid:payload-d6518670ca1311debbd9ca347000800b...">
    </SOAP:Body>
    </SOAP:Envelope>
    And the payload d6518670ca1311debbd9ca347000800b... ( again viewed from RWB) - contains the data.
    <?xml version="1.0" encoding="UTF-8" ?>
    <ns2:Order> ....
    </ns2:Order>
    Can we insert this payload directly inside the SOAP:Envelope body instead of a link there?
    Regards,
    Sudhin

    Hi!
    It seems to me that this 3rd party is expecting only XML not SOAP.
    If this is the case, you should use the HTTP Receiver adapter instead of SOAP.
    Some systems 'say' they can speak SOAP but they can only speak XML. Not to blame, it's a mistake many make these days.
    The only way you use SOAP Receiver adapter with this 3rd party, is that if someone from the 3rd party hands you a WSDL file.
    Ricardo Sancio Lóra
    Brazil

  • 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.

  • 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

  • HTTP Receiver adapter with post

    Hello,
    I have following scenario.
    XI (http receiver adapater) -
    > 3rd party web based application.
    The 3rd party application expects XI payload to be part of URL with POST Method.
    When HTTP receiver adapter sends request to 3rd party application, the URL looks like as follows.
    http://myserver:6789/myapplication/name1=value1&name2=value2&.....&name27=value27
    I looked at HTTP receiver adpater document on SDN. I see some attributes such as headerfiled1, headerfiled2..... headerfield6 and urlfield1....urlfield6. I have about over 25 fields to be passed with URL.
    Now I have following questions.
    1. How to make XI payload as name value pairs and part of URL.?
    2. I think the default for http adapater is GET, How to configure http adaper to use POST?
    I appreciate your help.
    Thank you,
    Balaji

    > 1. How to make XI payload as name value pairs and part of URL.?
    You should create the whole URL in a user defined function in mapping.
    > 2. I think the default for http adapater is GET, How to configure http adaper to use POST?
    HTTP adapter (and SOAP adapter) use HTTP POST. GET is not supported.
    Regards
    Stefan

  • HTTP receiver adapter: dynamic configuration

    I was told that if I have a URL and some parameters, I can use a sync HTTP receiver adapter to call a site.
    I know this can be done using some kind of dynamic configuration, but I am not familiar with this adapter.
    The most important question here is that I need to know if this can be done throw PI, so my question is:
    Is there a parameter limit in the HTTP adapter? If so, what is the quantity of parameters that I can give to the adapter?

    for the ASMA parameters you can use for the HTTP receiver adapter check
    Configuring the Receiver Plain HTTP Adapter - http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/frameset.htm

  • Hi,about http receiver adapter.

    i use http receiver adapter.
    the message was sent from send to receiver via http adatper of integratio engine.
    but how should i get payload of message?
    i can not get the payload data in receiver application.
    i set prolog as "&loaderXML=".
    and then the parameter name of payload is "loaderXML"
    but i can not get  the parameter name "loaderXML"   from http reques

    Tcode - Sxmb_moni go to , Double click the message - HTTP receiver one, Right side --go to - Request Message Mapping ..go for the pay load content,
    HI.
    there are not "Request Messge Mapping" entry in right side.

  • Hi! I need steps for HTTP Receiver adapter

    My scenario is like this:
    HTTP(HTTP Sender adapter)->XI->File(File adapter).
    For this Iam sending the data as payload in the body of HTTP. Now What am i going to do is the opposite of above scenario:
    File(FileAdapter)->XI->(HTTP Receiver Adapter)HTTP.
    I would like to know what are the steps to transfer a file(xml) from File adapter to XI and from there to Http.
    How to send the data using File adapter. Please suggest me some steps.
    Hoping a quick response!!!
    Thanks in advance!

    Hi Datta,
    For a HHTP -> XI -> FILE 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 File as a receiver.
    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 file. 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 by Alex. U have to give all the configuration details in the URL.
    Regards,
    Abhy
    Message was edited by: Abhy Thomas

  • 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 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

Maybe you are looking for