Enhancing flexibility of Websphere Message Broker applications by deploying application resources as source files

From the developerWorks archives

Julia Canella and Eugene Kharlamov

Date archived: January 4, 2017 | First published: September 19, 2012

WebSphere Message Broker V8 (hereafter called "Message Broker") Toolkit Fix Pack 1 makes your message flows more flexible by enabling you to update and deploy parts of a flow without recompiling and redeploying the entire flow. You can also assemble your broker archive (BAR) file on the same server where the application is deployed but where the Message Broker Toolkit (hereafter called the "Toolkit") is not available. This article shows you how to use Toolkit Fix Pack 1 to construct and configure message flows using deployable subflows, ESQL modules, and maps without compiling a flow into a compiled message flow (CMF) format, and how to modify and assemble Message Broker artifacts on a server without a Toolkit.

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 steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=836465
ArticleTitle=Enhancing flexibility of Websphere Message Broker applications by deploying application resources as source files
publish-date=09192012