Simple java code in graphical mapping - XI

This Weblog presents two things:

1) the use of trace
2) the use of Technical Context Objects

in the message mappings.

1. There are times (like debugging) when you want to add a trace to your message mapping.
No problem, you can do it quite easily by adding some code in your user defined function:

MappingTrace importanttrace; importanttrace = container.getTrace(); importanttrace.addWarning("The value of the tag [TheOne]is:" + variable);

and then in the SOAP Header - Trace (Message monitoring) you can see:

<trace level="1" type="T">Value of the tag [TheOne] is: 123456 </trace>

for traces that can be written to the Trace please take a look at section
"Trace Level of the Pipeline and Mapping Trace" on page:

http://help.sap.com/saphelp_nw04/helpdata/en/c8/98e7d5c1620642973565ea3dd319d1/content.htm

2. You can also easily get the names of the Technical Context Objects (like MESSAGE_ID or INTERFACE_NAMESPACE)

String constant; java.util.Map map; map = container.getTransformationParameters(); constant = (String) map.get(StreamTransformationConstants.INTERFACE_NAMESPACE); return constant;

a list of the Technical Context Objects names can be found here:

http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/content.htm


**************************Remember**************************
You can't see the Technical Context Objects like MESSAGE_ID
when you're testing your mapping in the XI Repository.
You can only see this in message monitoring when you post a message.
************************************************************