Transformation Options for WebSphere Message Broker V6

From the developerWorks archives

Andy Piper

Date archived: April 21, 2017 | First published: August 30, 2006

With the release of WebSphere Message Broker V6, the range of options for message transformation has expanded. The existing options of Extended Structured Query Language (ESQL), graphical message mapping, and eXtensible Stylesheet Language Transformations (XSLT) have all been enhanced. In addition, a JavaCompute node has been added, and it enables message flow developers to quickly manipulate messages using Java directly inside the message flow. All four of these technologies work within the common message model in WebSphere Message Broker, and all of them can be used within the same message flow if required. This article describes the pros and cons of each transformation technology, and supplements the detailed how-to information in the product information center.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

ArticleTitle=Transformation Options for WebSphere Message Broker V6