To deploy files to an execution group, you must first include them in a broker archive.
Before you start:
Create a broker archive (BAR) file for each configuration that you want to deploy.
You can add message flows to a BAR file 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 select Include source files, the source files for all message flows in the project are included; you can manually remove the resources that you do not want.
For further information about the files that you can include in a broker archive, see Broker archive.
If a parent flow and subflow are displayed in the Add dialog, 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 using the workbench:
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:
If you use configurable properties, see Editing configurable properties.
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.
To make further changes to your BAR file, see Editing a broker archive file manually.
When your BAR file is complete, the next task is: Deploying a broker archive file.