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 only add message flows at the project level. However, after you have added the project to the bar file, you can use the Remove icon to remove individual message flows or message definitions, if required. Likewise, if you check the Include message flow source box, the source for all the message flows in the project are included but you can manually remove the source files for the message flows that you do not want.
To deploy XML, XSL, and JAR files inside a broker archive, the connected Configuration Manager and target broker must be Version 6.0 or later.
If there is a parent flow and subflow displayed in the Add dialogue, subflows are added automatically, so you only have to add the parent flow.
It is not possible to 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.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
af03880_ |