HTTP Receiver adapter error ?

HI Guys,
I have configured the IDOC-HTTP. I have defined a bsuiness service on the receiver side as the receiver is not in our landscape and he is our business partner.
I have created a RFC connection of type G and it is working properly but the HTTP reciver adapter gives the error as below
I'm getting an error when I go to "sxmb_moni" which says
Error Category = PLAINHTTP_ADAPTER
Error ID = ATTRIBUTE_SERVER
Kindly help..
Thanks,
Raj
Message was edited by:
        raj reddy

Hi Raj,
<b>Error Category = PLAINHTTP_ADAPTER
Error ID = ATTRIBUTE_SERVER</b>
as far as i know this problem is due to high  traffic.When the data comes in bulk some of the message are failing or when they are not able to connect to reciever server.So it gives error.
u can look @ these threads of similer taste
PLAINHTTP_ADAPTER.ATTRIBUTE_SERVER error
PLAIN HTTP ADAPTER -ATTRIBUTE_SERVER ERROR
Plain HTTP adapter error
PLAINHTTP_ADAPTER  -  ATTRIBUTE_SERVER
and also look @
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
Regards
biplab

Similar Messages

  • 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

  • Http receiver adapter error : ICM_HTTP_CONNECTION_FAILED

    Hi all.
    I have set up a receiver http adapter and for the life of me can't get it to work. In sxmb_moni I get the following error in the Call adapter step of the pipeline:
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP client. Code 400 reason ICM_HTTP_CONNECTION_FAILED</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    It does not matter where I try and post to, it comes back with this. I am using "Url address" for Addressing type.
    Help appreciated.

    You should check whether the HTTP service is working on your system.
    transaction smicm -> goto ->  services.  check the entry for  HTTP. If necessary, a restart of the J2EE server might help.
    Also check the http adapter is active.
    transaction sicf -> default_host->sap->xi->adapter_plain
    Cheers
    Manish

  • ICM_HTTP_TIMEOUT error in HTTP Receiver adapter

    Hi
    I am doing HTTP Receiver adapter and File Sender adapter for my scenario.
    I am getting the following error in SXMB_MONI.
    - <!--  Call Adapter
      -->
    - <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>402</SAP:P1>
      <SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP client. Code 402 reason ICM_HTTP_TIMEOUT</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error
    Help needed,

    Hi Ganesh,
    Check this weblog...
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Check this thread with similar issue...
    ICM_HTTP_TIMEOUT
    Regards,
    Sridhar

  • Code 110 Reason Error in HTTP Receiver adapter

    Hello
    I am having proxy to HTTP Receiver scenario in which i am calling the target application URL through HTTP Receiver Adapter. This interface is async interface and hence i am not expecting any response from the target system.
    When i execute my interface the target system receives data from XI but in SXMB_MONI it sets the status of the message as "<b>Automatic Restart</b>" with the error description as "<b>HTTP client. Code 110 reason</b>"  in HTML Code area <b><SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code></b>
    This is causing multiple messages stuck in the queue and presently i am manually clearing all the messages.
    i checked the quality of service of the incoming message which is correctly setted as <b>Exactly Once</b>.
    Is there any configuration missing?
    Thanks in advance.
    Regards
    Rajeev

    Hi Rajeev,
    1.)Check in SMICM if your HTTP service is running or not.
    2.)If its running fine then you can check whether your SSL certificate is configured properly or not.
    Also follow the below mentioned links :
    HTTP 110
    HTTP Receiver Adapter -> HTTP client code 110 reason error when sending
    *Pls reward with points if helpful*
    Regards,
    Shibani

  • When i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

    when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

    Hi, Michal
    I have read your Weblog. It makes sense to me. Thanks a lot for your help! However, I still have some questions and listed them as following. Could you please help to answer them?
    <b>Q1:</b> I am new to SAP-XI. So I have no idea about TCODE-SXMB_ADM. Could you introduce more details about it?
    <b>Q2:</b> The XI system I am using is running on SAP-ICC's machine. The tools I can use are:
    <b>1.</b>Builder for Integration Repository
    <b>2.</b>Builder for Integration Configuration
    <b>3.</b>System Landscape Directory
    <b>4.</b>Runtime Workbench
    <b>5.</b>Administration System (for Repository, Directory, Runtime)
    Please note that I do not have a complete control on this SAP-XI. Do you think whether or not I can set the timeout parameter by following the instructions provided in your Weblog?
    For more details about my SAP-XI, please access the following Web page:
    http://iccxi.sap.com:58000/rep/support/admin/index.html
    <b>Q3:</b> The following messages are extracted from the SAP-XI. Wish they are hepful to solving my problem.
    2006-06-19 05:12:16 Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
    2006-06-19 05:12:16 Success Using connection AFW. Trying to put the message into the request queue.
    2006-06-19 05:12:16 Success Message successfully put into the queue.
    2006-06-19 05:12:16 Success The message was successfully retrieved from the request queue.
    2006-06-19 05:12:16 Success The message status set to DLNG.
    2006-06-19 05:12:16 Success Delivering to channel: ValidationRequestHandlerServiceChannel
    2006-06-19 05:12:16 Success SOAP: request message entering the adapter
    2006-06-19 05:12:37 Success SOAP: call failed
    2006-06-19 05:12:37 Error SOAP: error occured: java.net.ConnectException: Connection timed out: connect
    2006-06-19 05:12:37 Error Exception caught by adapter framework: Connection timed out: connect
    Thanks
    Menghua Li

  • 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 : Dynamic URL

    Hi,
    I have a scenario where I wish to build a dynamic URL for the HTTP Receiver Adapter. The URL will contain a customer number which is present in the mapping.
    The help seems to suggest that this is possible :
    <i>If you want to use an HTTP destination or URL set by the mapping, set the URL or HTTP Destination indicator. (The indicator displayed depends on the Addressing Type you selected above). If you set the indicator, the URL or HTTP destination set dynamically is called by HTTP.
    If the message header does not contain the URL or the HTTP destination, and you have set the Fail If Adapter-Specific Message Attributes Missing indicator, the XI message is set to status System Error. If you do not set the indicator, the URL or HTTP destination defined statically in the communication channel is used.</i>
    However, it is not very clear where the URL needs to be set dynamically.
    Does anyone know how to achieve this ?
    Cheers
    Colin.

    hello to all,
    We have a unique issue with one of our customers that is limited to 100 character URL.  The current url is http://mycompany.com/sap/xi/adapter_plain?namespace=urn%3Agoodyear%2Ecom%3AAIT%3AInventoryCheck&interface=AITInventoryCheck_Abs&service=HTTP_AIT_InvChk&QOS=BE&sap-client=010&sap-language=EN
    Is there a way to have a URL like
    http://mycompany.com/sap/xi/adapter_plain?namespace=urn%3Agoodyear%2Ecom%3AAIT%3AInventoryCheck
    and then somewhere in the process add... &interface=AITInventoryCheck_Abs&service=HTTP_AIT_InvChk&QOS=BE&sap-client=010&sap-language=EN
    So the data comes to an F5 through the DMZ to the SAP webdispatcher then to the SAP XI system.
    Any ideas if this is possible or how you could start with a shorter URL?
    Thanks,
    Dede

  • 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

  • HTTP - Receiver - PLAINHTTP_ADAPTER Error

    hi,
    I have configured a HTTP Receiver. I get the following error in the SXMB_MONI - HTTP Client 110 Reason.
    I set the Trace Level high using SMICM and looking at the log, it seems like its connecting to the host that i specified in the HTTP Receiver Adapter but at the end i get this error:
    ERROR => PlugInHandleNetData: client: premature EOS - header not complete in response [http_plg_mt. 2470]
    [Thr 13] PlugInHandleNetData: read response header
    [Thr 13] PlugInHandleNetData: header termination not found
    [Thr 13] PlugInHandleNetData: need more data (0/-1)
    [Thr 13] IcmPlCheckRetVal: Next status: READ_RESPONSE(2)
    Any idea why i am getting this error?
    Thanks,
    Tirumal

    Moorthy -
    I am seeing this error in the log file when i use the SMICM tcode.
    I am getting the error while sending a request to the HTTP Receiver.
    Let me know if you have more information.
    Meanwhile, will go through the blog and see if i can do more troubleshooting.
    Thanks,
    Tirumal

  • 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

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

  • 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

Maybe you are looking for