Before you start:
Create a broker archive (bar) file for each configuration that you want to deploy.
To deploy files to an execution group, you first include them in a broker archive (bar). The bar file is deployed by sending it to the Configuration Manager, and from there, its contents are sent to the execution group on a broker.
You can add message flows only at the project level. However, after you have added the project to the bar file, you can click Remove to remove individual message flows. Likewise, if you check Include source files, the source files for all message flows in the project are included; you can manually remove the ones that you do not want.
If a parent flow and subflow are displayed in the Add dialogue, subflows are added automatically, and so you have to add only the parent flow.
You cannot read deployed files back from broker execution groups. Therefore, keep a copy of the deployed bar file, or of the individual files within it.
Follow these steps to add files to a broker archive (bar) file using the Message Brokers Toolkit:
A list of the files that are now in your bar file is displayed in the Content editor. You can choose not to display your message flow source files by clearing the Show source files box at the bottom of the Content editor pane.
Next:
The next step is to deploy your broker archive (bar) file, but you might first want to edit configurable properties. You can also edit the contents of your bar file manually.
If you want to have multiple instances of a flow with different values for the configurable properties see Adding multiple instances of a message flow to a broker archive.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
af03880_ |