There are many times when we need Technical Context Objects like MESSAGE_ID in our BPM:
- we want to create a file with a message_id as it's name
- we need message_id to correlate request and response messages inside the BPM
*************************************************************************************
Unfortunately some of those technical objecs (like message id for instance) are not available in the BPM
(you can't retrieve then in a Transformation step).
The only way to get them is to use additional mapping step in the Interface determination.
*************************************************************************************
1. Let's suppose we have a simple BPM.
2. We've decided that we want to have incomming message ID in you of the fields of your abstract interface.
We create a Simple Java function to that will map the MESSAGE_ID to one of the fields of our absrtract interface.
3. The code of the simple java function:
String constant;
java.util.Map map;
map = container.getTransformationParameters();
constant = (String) map.get(StreamTransformationConstants.MESSAGE_ID);
return constant;
4. We create mapping interface on the basis ot the mapping program that we've just prepared.
5. Now we have to add interface mapping to our interface determination step in XI Directory.
Then after we send the message we can easily see that we got MESSAGE_ID in our abstract interface (so in the BPM).
The message id is ready to be used in our integration process.
Hope this information will be usefull to some of you:)
阅读(1146) | 评论(0) | 转发(0) |