I have no idea how many of you are using BAM technology to send “messages” to different systems via XI but the number of those who do may soon rise significantly since the introduction of the BAM Trace Monitor. Attention BAM TRACE monitor is available in WAS 7.10 but it was backported to WAS 7.0 (Note 955684 – Down port of BAM trace to 700) What is this BAM trace monitor? It allows you to trace with many detail levels all of your BAM events. How to configure this trace monitor? Step 1 – at first you need to create a BAM event and link it with your objects (as shown in my weblog: XI: BAM – Episode I – Introduction) Step 2 – then you need to create a new trace in transaction SWF_BAM_TRC (remember it’s only available from WAS 7.0) – inside the trace specify: a) trace level b) object you need/want to monitor In my example I created a trace for Material creation (the event will be invoked via material creation – transaction MM01) – as you see once the trace is created is becomes active (but you can deactivate it if necessary later on) Step 2 – create the object that will invoke your event (in my example I create a material) As you can see since I turned OFF the XI machine the system signals an error so we can see why the message was not generated and sent to the XI. but this is not the best thing yet! The best thing here is that by clicking on the “X” value in the data exists section we can get all the details about our event! When we click on the error we can see much more details: Obviously we can also see the content of your event. This is not only great for debugging purposes but also allows us to see the content (values) populated by the event with no debugging necessary. Hope such tools like this BAM trace monitor show that using BAM technology is not only easy to use but also easy to develop and debug.