What the best way to move IBM Message Broker components between DEV, QA and PROD environments?

Question

On a SOA project we start to employ IBM WebSphere Message Broker to orchestrate .NET-based web services. We have distinct DEV, QA and PROD environments for the system being developed.

WebSphere Message Broker Toolkit would be used to develop message flows in DEV. And with DEV everything is more or less clear.

For QA and PROD we aim to have repeatable and as automated and possible deployment procedure. With .NET portion it almost a no-brainer, but deployment to Message Broker seem to require substantial manual effort, which is not good.

What are recommendations for deployment to WebSphere Message Broker? What is the best way to package Message Broker components?

Answer 1

You components (flows and so forth) will be packaged up as Broker Archive (.bar) files. You can use Ant to script the deployment of these components between environments, for example.