Websphere Transformation Error Handling in Websphere Message Broker

How to catch Websphere Transformation Extender Error in Websphere Message Broker:

I have created a flow that will validate a message (WTX Validate) and also catch any error:

The Transformation Errors can be put on a Queue to be consumed by an Monitoring tool, Exported to a file for debugging.

4 Comments

  1. Nagesh says:

    With WMB v8 Mapping node available, do you think WTX is still relevant ?

  2. Thys Michels says:

    The new Data Format Description Language (DFDL) -based parser which provides an open standard-based, efficient means of accessing, parsing, and transforming data held in many different formats. Using the DFDL standard, clients may choose to build and reuse their own custom transforms.

    And so yes WTX is not relevant anymore. Everything can now be done in Message Broker V8.

  3. Arun V says:

    Hey! Could you mail me the test flow here if you still have it. I am working on setting up alerts from WMB flow which calls WTX maps using the WTX mapper node. I need to get the errors raised by WTX (using FAIL calls etc). I guess yours should help.

Leave a Comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s