在 DEV、QA 和 PROD 环境之间移动 IBM Message Broker 组件的最佳方法是什么？
在 SOA 项目中，我们开始使用 IBM WebSphere Message Broker 来编排基于 .NET 的 Web 服务。我们为正在开发的系统提供独特的 DEV、QA 和 PROD 环境。
WebSphere Message Broker Toolkit 将用于在 DEV 中开发消息流。有了 DEV，一切都或多或少变得清晰了。
对于 QA 和 PROD，我们的目标是拥有可重复、自动化且可能的部署过程。对于 .NET 部分来说，这几乎是理所当然的事情，但部署到 Message Broker 似乎需要大量的手动工作，这并不好。
对于部署到 WebSphere Message Broker 有哪些建议？打包 Message Broker 组件的最佳方式是什么？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您的组件（流程等）将打包为 Broker Archive (.bar) 文件。例如，您可以使用 Ant 编写环境之间这些组件部署的脚本。
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.
使用脚本。
正如 Andy Piper 所说，Ant 工作得很好。
另请注意，您可以使用 CMP API，该 API 已被重新标记为 Message Broker API，它非常全面，可让您比各种 Broker 命令更有效地获取和修改 Broker Archive (BAR) 文件中的信息您可以从脚本调用。
Use scripts.
As Andy Piper says Ant works quite well.
Also be aware that you can use the CMP API which has been rebadged as the Message Broker API its quite comprehensive and lets you get at and modify information in you Broker Archive(BAR) files to a much more significant extent that just the various Broker commands you can invoke from a script.