Edit XML before receiving by Receiving HTTPS Receiver

Hello
I need to connect to target system using HTTPS and I have used a DTD given by the target system.
The target system expects an HTTPS request in an XML format.
This XML shall have a DOCTYPE comment immediately after first line of XML declaration.
Ex:
<?xml version="1.0"?>
<!DOCTYPE method_name PUBLIC "-//method_path" "http://dtd.doamin_name.com/method_name.dtd">
I used Message Mapping to acheive mapping and it failed while testing.
The SXMB_MONI shows that the DOCTYPE is missing and it must be declared.
Is there any way to change the XML message - add the DOCTYPE comment - before the message reaches the HTTPS Receiver?
Please help.
Thx
Alkesh

Hi Srinivas,
This error occurs when the maximum duration of the connection is exceeded than the specified value.
Check this forum:
Error code 402:-ICM_HTTP_TIMEOUT in R/3
Regards,
Supriya.

Similar Messages

PI 7.11 - Sync HTTP receiver adapter with response XML file

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

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

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

Hi,
I have a HTTP Receiver scenario. I get the data from a Webservice and sent the data with a HTTP Request to our customer. So far we have no problem. Our customer is returning a payload structure like the one below.
Now the problem here is, there is a <start>, <end> tag and "0" and "OK" before and after the XML structure as you can see below. How can I parse these type of messages?
<start>
0
OK
<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE AMS_XML_DATA SYSTEM "Group1.dtd"><AMS_XML_DATA><Header><ErrorCode>0</ErrorCode><ErrorMessage>OK</ErrorMessage><Version>1.0</Version><SourceId>XXX</SourceId><MessageId>XXX99998888777766665555</MessageId></Header><Segment><IgnoreFg></IgnoreFg><ErrorCode>555</ErrorCode><ErrorMessage>PR DA FO</ErrorMessage><TransactionType>N</TransactionType><TransactionId>XXX99998888777766665555</TransactionId></Segment></AMS_XML_DATA>
<end>
Thank you in advance.
Best Regards,
Arman

I think to parse this message is impossible, because it's not well formed.
<start>
0
OK
<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE AMS_XML_DATA SYSTEM "Group1.dtd"><AMS_XML_DATA><Header><ErrorCode>0</ErrorCode><ErrorMessage>OK</ErrorMessage><Version>1.0</Version><SourceId>XXX</SourceId><MessageId>XXX99998888777766665555</MessageId></Header><Segment><IgnoreFg></IgnoreFg><ErrorCode>555</ErrorCode><ErrorMessage>PR DA FO</ErrorMessage><TransactionType>N</TransactionType><TransactionId>XXX99998888777766665555</TransactionId></Segment></AMS_XML_DATA>
<end>
A declaration of DOCTYPE outside the header / prolog is not allowed.
Aditionally the start and end tags are not closed. So the basic question is, why does the sender transfers a not well formed XML?

Simple HTTP Receiver - HTTP server code 405 reason Not Allowed explanation

Hi, I am using simple HTTP Receiver to receive the XML file from the below url http://www.bank-ua.com/export/currrate.xml
But receiving the below error in SXMB_MONI
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>405</SAP:P1>
<SAP:P2>Not Allowed</SAP:P2>
<SAP:P3><html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 405 reason Not Allowed explanation <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Initially the same URL was working could you advice what to change to make this working?
Thanks,
Dhill

Hi Senthil,
There is a way, you can expose the function module HTTP_GET as an rfc-enabled FM and use it to call the webservice. Here is a POC I made before:
Proof of Concept: An Alternative HTTP GET using a Remote-Enabled Version of the Function Module HTTP_GET
Another is to create a UDF that uses an HTTP Client class to call the webservice.
Regards,
Mark

ICM_HTTP_CONNECTION_FAILED error on http receive method

Hi,
I am trying to read a XML via http. I have developed a code referencing this blog:
/people/rashid.javed/blog/2007/03/11/cricket-world-cup-http-client-and-simple-transformations
When http receive method is executed it gives me an error.
On executiong of: CALL METHOD client->receive it gives error:
code:    400 message: ICM_HTTP_CONNECTION_FAILED
I treid changing host and buf in code below both to http://www.google.com to rule out the possibility of bad url. Also tried setting time out to 500 in send method. Still no luck.
ICM trace shows following:
Thr 4864] *** WARNING => Connection request from (16/6462/1) to host: http://www.google.com/, service: 80 failed (NIEHOST_UNKNO
How do I solve this error, please give me some tips.
I was looking forum for this issue but was not able to find a solution.
Here is complete code:
DATA: client TYPE REF TO if_http_client.
DATA: host TYPE string.
* DATA: proxyh TYPE string VALUE 'IfYouHave.Proxy.com',
*      proxyp TYPE string VALUE '8080'.
DATA: buff TYPE string,
      respd TYPE string.
DATA: subrc TYPE sysubrc.
CALL METHOD cl_http_client=>create
EXPORTING
    host               = 'http://www.google.com/ig/api'
*    SERVICE            =
*    proxy_host         = proxyh
*    proxy_service      = proxyp
*    SCHEME             = SCHEMETYPE_HTTP
*    SSL_ID             =
*    SAP_USERNAME       =
*    SAP_CLIENT         =
IMPORTING
    client             = client
EXCEPTIONS
    argument_not_found = 1
    plugin_not_active = 2
    internal_error     = 3
    OTHERS             = 4
IF sy-subrc <> 0.
WRITE:/ ' cl_http_client=>create, subrc = ', sy-subrc.
EXIT.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
buff = 'GET'.
CALL METHOD client->request->set_header_field
    EXPORTING
      name = '~request_method'
      value = buff.
buff = 'http://www.google.com/ig/api?weather=21218&hl=en'.
cl_http_utility=>set_request_uri( request = client->request
                                    uri     = buff ).
subrc = cl_http_utility=>get_last_error( ).
IF subrc <> 0.
    WRITE: / 'Wrong URI format'.
    EXIT.
ENDIF.
ENDIF.
CALL METHOD client->send
* EXPORTING
*    TIMEOUT                    = CO_TIMEOUT_DEFAULT
EXCEPTIONS
    http_communication_failure = 1
    http_invalid_state         = 2
    http_processing_failed     = 3
    http_invalid_timeout       = 4
    OTHERS                     = 5
IF sy-subrc <> 0.
CALL METHOD client->get_last_error
    IMPORTING
      code    = subrc
      MESSAGE = buff.
WRITE: / 'communication_error( send )',
         / 'code: ', subrc, 'message: ', buff.
EXIT.
ENDIF.
CALL METHOD client->receive
EXCEPTIONS
    http_communication_failure = 1
    http_invalid_state         = 2
    http_processing_failed     = 3
    OTHERS                     = 4.
IF sy-subrc <> 0.
CALL METHOD client->get_last_error
    IMPORTING
      code    = subrc
      MESSAGE = buff.
FORMAT COLOR COL_BACKGROUND.
WRITE: / 'communication_error( receive )',
         / 'code: ', subrc, 'message: ', buff.
WRITE: / 'communication_error'.
EXIT.
ENDIF.
respd = client->response->get_cdata( ).
WRITE:/ respd.
Thanks in advance,
CD
Edited by: CD on Feb 19, 2009 1:46 PM

Check this link..
[HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED;

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

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

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

HTTP RECEIVER QUERY

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

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

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

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

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

HTTP receiver Adapter configuration

Hi All,
I want to post an XML message using HTTP Receiver Adapter for my BPM scenario (Idoc to HTTP service)
The receiver has Oracle gateway and it expects message in following format.
HTTP Header
   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.

Remove namespace alias for HTTP receiver adapter

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

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

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

HTTP RECEIVER Stopping on CALL ADAPTER

Hi All,
I'm having a problem with HTTP Receiver adapter, It's an IDOC that need to send to a HTTP Listener. Everything works until send the XML to the http listener, I have made a single listener in java to verify how this XML is coming from adapter.
I got the follow information:
POST /?msgguid=45ECD392770B0046020000000AA00D4B&service=MYSERVICE&namespace=urn%3amynamespace%3atest%3aintegration&interface=MI_ED_MYIDOC_IB&qos=EO HTTP/1.0
content-type: text/xml
content-length: 1550
connection: close
accept: */*
user-agent: SAP Web Application Server (1.0;640)
host: 10.10.10.10:5556
accept-encoding: gzip
<?xml version="1.0" encoding="UTF-8"?>
It stops on first line of XML <b><?xml version="1.0" encoding="UTF-8"?></b> and stay stoped until I break the connection.
The server is SAP XI 3.0 SP15.

Hi Renjith, yes it's a custom java program and I'm trying to write on the console the stream on the console.
What I need to do is certify if SAP XI is delivering the message to the legacy system. So, I know that all configuration on scenario for integration between this legacy system and SAP R/3 is correct. And I'm almost sure that error is on the legacy system side that I don't have credentials to verify.
Look at the source code below:
import java.io.*;
import java.net.*;
class SocketServer {
   ServerSocket server = null;
   Socket client = null;
   BufferedReader in = null;
   PrintWriter out = null;
   String line;
   SocketServer(){ //Begin Constructor
     this.listenSocket();
   } //End Constructor
public void listenSocket(){
    try{
      server = new ServerSocket(5556);
    } catch (IOException e) {
      System.out.println("Could not listen on port 5556");
      System.exit(-1);
    try{
      client = server.accept();
    } catch (IOException e) {
      System.out.println("Accept failed: 5556");
      System.exit(-1);
    try{
      in = new BufferedReader(new InputStreamReader(client.getInputStream()));
      out = new PrintWriter(client.getOutputStream(), true);
    } catch (IOException e) {
      System.out.println("Accept failed: 5556");
      System.exit(-1);
    try{
      int i = 0;
      while((line = in.readLine()) != null){
        line = in.readLine();
     System.out.println(i+":"+line);
        i++;
      //this.finalize();
    } catch (IOException e) {
      System.out.println("Read failed");
      System.exit(-1);
protected void finalize(){
//Clean up
     try{
        in.close();
        out.close();
        server.close();
    } catch (IOException e) {
        System.out.println("Could not close.");
        System.exit(-1);
public static void main(String[] args){
        SocketServer frame = new SocketServer();
Thanks,
Daniel

Edit XML before receiving by Receiving HTTPS Receiver

Similar Messages

Maybe you are looking for