Skip to Content
avatar image
Former Member

How to HTTP-Post different XML messages to one receiving URL on XI side?


I have a problem with a HTTP => XI => IDoc scenario.

A client want to send 4 different XML documents to only 1 receiving URL on the XI side. How can I handle this in XI???

To send XML data via HTTP to XI you have to specify the namespace, interface and service in the URL. But I only can specify 1 namespace, interface and namespace in the URL...

But how can I define a generic message interface for all 4 messages.

The solution with 4 receiving URL's is easy, but not workable for the client 😔



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Nov 27, 2008 at 11:06 PM

    Try with:

    - Multimapping on Sender Side

    - Enhanced Receiver Determination if needed to call different receiver depending on the message sent.

    Add comment
    10|10000 characters needed characters exceeded

    • You can do following:

      Create an interface with an artificial root node like this:


      - structure message 1

      - structure message 2

      - structure message 3

      - ...

      A simple XSLT/Java mapping adds that root node to every message.

      Create different mappings based on the structure if the different mappings and do routing based on the same.

      Another option: Upgrade to PI 7.1. Here you can simply create a service interface with different operations and routing/mapping based on the operations.



  • Feb 10, 2009 at 04:58 PM

    I am new to HTTP adapter configuration, can you please provide me the steps for receiving po which is cxml with DTD and map to IDOC and send to R/3. My company doesnt want ot use webservices.Please advice.


    Add comment
    10|10000 characters needed characters exceeded

  • Feb 10, 2009 at 05:21 PM

    Hi Tobias,

    the solution is quite easy: Just do nothing, he, he. Interfaces are not validated, so create a dummy outbound interface (one field is enough) and put conditions on interface determination. Message Mapping is now avoided, the only disadvantage (is this a handicap?) - you have the choice between Java, ABAP and XSLT.



    aeh, sorry, the old thread was brought to the top be Menaga, i didnt see it was already solved

    Edited by: Udo Martens on Feb 10, 2009 6:24 PM

    Add comment
    10|10000 characters needed characters exceeded