Previously, I wrote about how to dump Service Message Objects to the SystemOut log using a custom mediation. This solution involved using a small amount of Java code.
In later revisions of WebSphere Integration Developer 6.0.2, and in version 6.1, it is now possible to do this with a visual snippet, which makes it even easier. Place a custom mediation in your flow, and use the ‘Visual’ mode. The key to this technique is the pre-supplied print BO to log visual snippet in the utility section of the standard supplied visual snippets. If you hook this up to the smo input (and add a constant string print for good measure, to make reading the log easier), your visual custom mediation will look a bit like this:
This will provide output similar to that shown in the previous tip.
(Note: in fact, you can use this standard visual snippet to print any Business Object, not just a Service Message Object).
March 12, 2008 at 1:28 am
Thank you very much for this tip. I’m using it to figure out why a XSLT transformation only “works” when the ESB test environment is started up in debug mode.
If I put this custom module just before the XSLT module, the mediation works fine and the transformation is done OK, but if I took away the log module, then the XSLT transformation don’t do anything and output just the root node of my SMO.
BTW, if I start the server in debug mode, everything works fine, with or without log module…
weird, right?
April 15, 2008 at 4:12 pm
[...] probably want to connect your export to a mediation flow – initially, you can just display the SMO to see whether it’s working as [...]
September 9, 2008 at 10:39 am
[...] or a custom mediation, for example. Here’s an example of what the SMO looks like when dumped out in the middle of the mediation flow. The value of the WS-A To header is [...]