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

Similar Messages

HTTP Receiver Adapter - Post HTTPS to non-sap system

I plan on doing an https post to a non-sap system using the http rec adapter. Will I need to make some config changes to enable ssl communication on the XI system? Will I need the certificate of the target system?
Thanks,
Mark

Hi Mark,
You will need Certificate to enable SSL communication.
And once you install your certifictaes on the systems according to the above blog then there are few changes which needs to done on XI side.
On XI Server - Go to SM59 and Create HTTP destination to the system with SSL enabled in that destination.Select active option for SSL.
In confguration - Go to HTTP rec channel and select HTTP destination and here give the one which u have created in last step.

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

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

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,

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

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" ?>
- 
- <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

How to trace HTTP receiver adapter error

Hi All,
My scenario is to send PO details to vendor site (HTTPS URL). MY SSL configuration is complete and I have used the SSL certificates in RFC destination of type 'G'. When I test RFC destination connection, it gives me the correct response as '200'.
This RFC destination is used in HTTP receiver adapter of XI to connect to site and post PO xml document. It is passing successfully through Integration Server, as I get success flag in 'SXMB_MONI'. But, it is not reaching our vendor's site.
Can someone help me, with what's going wrong, or how can I trace the error.
Thanks & Regards,
Amit

Hi Sadhna,
It's a B2B scenario, where my sender is configured correctly and the receiver as well.
In sxmb_moni, I am getting successfull status. But, it is not reaching receiver.
Thanks & Regards,
Amit

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

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

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

HTTPS Receiver Adapter POST with FILE TYPE parameter

Similar Messages

Maybe you are looking for