on 04-02-2008 6:27 PM
Gurus,
I have a scenario wherein I have a message that is required to be converted to temp message using the Java Mapping and then map to a different message to call an RFC.
Is this possible?
A simplistic view of what i am tring to achieve
eg:Source Message
<EMP>
<Name1/>
<Name2/>
</EMP>
I am using java mapping to get the Temp Message
eg: Temp Message
<EMPLOYEE>
<FullName/>
</EMPLOYEE>
Map the temp message to RFC
eg: Target Message
<EMPLOYEE>
<FullName/>
<some additional message/>
-
-
</EMPLOYEE>
Regards
Unni
Hi,
Yes this kind of multi mapping is possible.
For Source message to Temp message ...you will be using one mapping and then in 2nd mapping will be the Temp message to Target Message.
As the structure of Source message ..temp message and Target message is specific and directly/indirectly three end points will be there in sequence as
Source message -
Now I think you need to use BPM for this kind of contineaous mapping. or have to create two scenarios as in 1st source to temap message..and then Temp to Target message.
Thanks
Swarup
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Swarup:
First we should be clear that this is not called mutli mapping, it can be called interface mapping with multiple mapping programs.
Secondly, I do not think BPM needed for this reason, this is just one interface mapping. Creating two scenarios is also unnecessary.
I have done with Java + Message Mapping, XLST + Messge Mapping etc.
Your comments are welcomed.
Liang
Hi,
Yes you are right ...but still its not clear..as per the requirment there is Temp Message has to be created in between...so even you can use Java + Message Mapping...in interface mapping you can give only Sender and target..how will be handling the Temp Message...either this Temp message also needs to be stored somewhere...
It can be interpreted as both way..either as you have said about combination of Mappings or the sequecne as I had mentioned in my post...
I think we should wait till these things will not be clear...and then we could have solid solution with either of the way
Thanks
Swarup
Hi Unni,
I saw the details you had sent...
You will be getting the source message and that you are passing to Temp message with Java Mapping...
i.e. mt_test to mt_temp_jdbc
now while mapping Target message you are adding additianl message mapping and calling it to RFC ..is it ... mt_temp_jdbc to RFC (ZXL00....)
Here the 2nd mapping will not be executed as the mt_temp_jdbc is not at all related with the Source Interface.
This kind of combination will work out...when you will directly pass some of the fields from source to Target via Java mapping and remaining fields to be mapped as Message Mapping between Source and Target messages..no need to temp message..
Try this kind of combination.
Thanks
Swarup
Thanks Liang.
The below was my commmunication with Liang over email
1. DT / MT / MI_Src for your temp file - Remeber this
2. DT / MT / MI _tar for your target system.
3. Design your MM , test it
4. Import your jave achives
5. Create Interface Mapping - MI_Src --- MI_tar
6. Add your jave mapping as your firt mapping program
7. Add you MM as your second program.
Additionally I had a small issue with my Namespace in my java mapping
regards
Unni
Hi, Unni:
This is possible.
Since in Interface mapping, you can specify any number of mapping programs.
The output of prior mapping program is input of subsequent mapping program.
When you use your java mapping, you can use DOM / SAX to create tmp message structure.
Then the structure is source msg structure of your second mapping.
Anyway, this is not called Multi-Mapping, your message still is 1 in, 1 out, called 1:1.
Hope this clear your doubts.
Liang
Edited by: Liang Ji on Apr 2, 2008 8:07 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.