Skip to Content
avatar image
Former Member

SAP PI Java AAE HTTP Receiver

Dear Experts,

I'm fairly new to the HTTP receiver adapter. I'm trying to test a HTTP post (upload the xml file from PI mapping) to the URL - through SAP PI.

I configured my HTTP receiver channel params as Target host -, port - 80, path - /data, User Authentication - Anonymous Logon

But its not posting the data. So please help me understand the below points.

1. Set Form - If I check this what value should I provide for the Main Payload Parameter Name? I understand this is the variable name that contains the whole data in case of HTTP sender.
But incase of HTTP receiver, where can I find this value in PI? And in which scenario should I use this option?

2. I'm just trying to check Set Multipart and Specify Content Details as Character Encoding - UTF-8 and Content Type - text/xml . Is this correct?

3. Do I need to make any other setting? Or change the xml in Java Mapping to different format?

Thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • May 25, 2017 at 11:03 AM


    Can you check the ping test on the channel to find if the connectivity exists with the host URL

    If there is no issue, then probably use HTTP POST addon on chrome to make a dummy test. This will help you to further drill on the issue.

    Verify first on the connectivity test. What is the error you receive in channel when you post.

    provide more details.


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 25, 2017 at 02:16 PM

    Yes, the ping test works fine. I infact tested through CURL from PI dev OS - and it works fine. I understand if I manipulate the output for this URL from PI, it should work. But my requirement is to post the XML data from the ABAP proxy. Please help.

    Add comment
    10|10000 characters needed characters exceeded

    • Hello,

      What error do you see in channel when you try to post.. Do you have more information on the error you see. in channel. This will help for further to investigate.

      point 2. character encoding - UTF-8 and content type - text/xml : This is correct.

      Lastly you can trace via XPI_INSPECTOR to gather more information.