HTTP Receiver Adapter parameters

Dear All
I am trying to POST an HTTP URL in teh following format but the query string doesnt get populated up when I parameterise it.
http://<hostname:80>/<path>?<query-string>
e.g.
http://hello:80/world?myname=haik&myapplication=XI&mycompany=SAP
when I include the query-string as part of the path i.e. path = world?myname=haik&myapplication=XI&mycompany=SAP it work without a problem.
But when I enter it as parameter 1 , Parameter 2 and etc I get the impression they get ignored.
i.e path = world
paremeter1 = myname=haik
parameter2=myapplication=XI
At least that's what the network level logs show. teh logs show that the URI is only the path value.
We run SAP XI3.0 with SP16
Do I need to configure something to enable teh parametarisation of a URL?
Can you please help?
Thanks
Haik

Pragya
Thanks for the quick reply.
where do I disable the "http adapter parameters"?
Can you please elaborate?
Just to add that the reason that I prefer to use parameters is because my next plan is to populate the parameter values through message Mapping.
however my first task is to establish that the parametrs act as part of the "query-string".
Thanks,
Haik

Similar Messages

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 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
   HttpVersion: 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
                         Contentlength: 12345
                         Contenttype: 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=HTTPSOXTA
   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 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

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

Parameter in HTTP receiver adapter

Hey
My requirements are:
I am sending an XML to an external system. Documentation says: "XML should be in a parameter in your request called 'xmlInput'".
How do I actually put my XML in this parameter? Does this have anything to do with the URL Parameters in comm channel configuration?
I have configured a client proxy, http receiver adapter and a communication channel in sm59 and they work OK, but it seems as I don't send the XML in this parameter.
Appreciate your help!
regards Ole

Hey!
Thanks for your answers.
Nana, are you sure of this, that java proxy is the only way I can put the XML in a parameter? I only need to confirm this because there is no place in their documentation that this is stated explicitly, I have only been told this via their technical person...:)
I agree that this is a limitation of the receiving system, and I know that this system is not up to date as I can tell from what they are saying and their documentation.
regards Ole

Paramter setting in URL in the case of HTTP receiver adapter

I have the following requirment: Can you anyone please help me how to define DATATYPE and configure in HTTP adapter:
The web page is developed in JSP page its body contains parameter(for example:<textarea name="xml" cols="70" rows="150" wrap="off">) to pass to the URL.
In this suitation,1) how can define my datatype in XI repository. ,Root element should be start with "xml" tag? 2). what are configuration parameters in HTTP receiver adapter.
3). Using HTTP post application.
Your response is highly appreciated.
Thanks
Venkat

I have the following requirment: Can you anyone please help me how to define DATATYPE and configure in HTTP adapter:
The web page is developed in JSP page its body contains parameter(for example:<textarea name="xml" cols="70" rows="150" wrap="off">) to pass to the URL.
In this suitation,1) how can define my datatype in XI repository. ,Root element should be start with "xml" tag? 2). what are configuration parameters in HTTP receiver adapter.
3). Using HTTP post application.
Your response is highly appreciated.
Thanks
Venkat

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:
 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).
 Specifications for addressing using an HTTP destination:
HTTP destination
 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

Testing HTTP Receiver adapter.

Hi Everyone,
Would anyone Please provide the sample details required for testing the HTTP Receiver adapter to check its fuctionality and the required output.
Any Help would be appreciated.
Regards,
Varun

Hi Varun,
Check this for HTTP Adapter ..
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
HTTP to RFC - A Starter Kit
regards
Kishore

Regarding Http Receiver Adapter Details.

Hi Everyone.
When do we use http Receiver Adapter?
I want to configure File to HTTP Scenario.
For Receiver Adapter, What should i Specify Addressing Type .If I select the URL Address
What I need to give values for Target Host, Service Number, Path and Similarlly If I select Addressing Type as HTTP Destination, What I need to give value for HTTP Destination.
Regards,
Varun

Hi,
check this blog
Push Data to MVC Architectured application using XI
XI - SAP Business Connector integration using the HTTP adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/79973cc73af456e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
CSV File Lookup With Http Request and Response in XI
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
Regards
vasu

HTTPS Receiver Adapter POST with FILE TYPE parameter

Hello,
I need to do a POST to a URL service that validates content of a file. It receives user and password as string parameters and a FILE as a mime type parameter.
I'll appreciate any help.
Regards,
Diego.

Hi.
Using Http Receiver Adapter , you can try out this.
This blog may give some idea-
/people/amol.joshi2/blog/2006/06/28/must-fire-a-http-get-from-xi---try-this
Otherwise, try out with callinng this service via SOAP Adapter i.e webservice.
Rgds,
moorthy

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

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

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 Adapter parameters

Similar Messages

Maybe you are looking for