Handling Dynamic pay loads using a Single URL

Question

Hi All,
I need to integrate SAP R/3 to a Third party web portal using SAP XI. Portal will communicate with 15+ messages. The third party portal is asking me to provide a single URL to send tje XML Messages. the problem is each message is having different structure from other. We have to recognize the message by seeing the header. The header (root node) will contain message number (like Msg01, Msg02, Msg03 and so on...) , . They have provided us a XSD file, which contains all the messages as complex type , which i can able to upload as External Definitaion. But in the message interface only one message i can use at a time as output message. i,e msg01 or msg03 or msg03 etc... . But the third part portal will send any of message out of 15 messages. So how can i generate single URL to accept dynamically any of 15 message. Also i am getting a confusion which sender adapter to use . Can anybody guide me how to handle this situation?

Answer 1

Hi,
you can use one java mapping in the advanced receiver determination as I mentioned. Which does not need to have a unified message format.
Enhanced Receiver Determination
Use
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
After Java Mapping you have already assigned the 15+ different messages to the right receiver you intend to send the request. You can just carry on with normal configuration from here, perform mapping if you need in the interface determination step. etc. Since you don't have one unified Message format for the 15 different messages, you probably need implemented all mappings in Java. Because message mapping does not work, since you have only one outbound interface from Portal (15 different requests are labeld with same interface name). Nevertheless, with java mapping it is not a problem to check the root node at first and carry out the wished mapping.
Summarize here a bit:
1. defined ONE Message Outbound interface e.g. MI_OUT_Portal for different Portal request (you could define this interface based on some random MT, does not matter at this point)
2. define one Interface mapping which map the MI_OUT_Portal to Receivers, Receivers is located in SAP BASIS (standard XI content from SAP)
In this interface you should have to refer one java mapping which read the XML payload from portal request and find out who is the receiver. This should be quite easy. You could even configure it in one external Database which msg goes to which receiver and find out it in the runtime.
3. You need mapping from different message typ to the wished receiver, these 15 request messages will probably has 15 different inbound interfaces, you will need 15 different interface mapping if every request message has to be mapped  before it can pass through to the receiver application. These mappings could be done in one java mapping again.
4. configure Receiver Determination with advanced RD in Configuration with the Interface mapping which implemented in step2
5. configure Interface determination and receiver agreement
regards,
Hai