Adding files to a broker archive

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 and message sets 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/set source box, the source for all the message flows or message sets in the project are included but you can manually remove the source files for the message flows or message sets 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.

You can manually add XML, XSL, and JAR files by following these steps. However, JAR files that are required by JavaCompute nodes within message flows are added automatically from your Java project when you add the message flow. Similarly, XML and XSL files are automatically added if required by the 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:

  1. Switch to the Broker Administration perspective.
  2. Double-click your bar file in the Broker Administration Navigator view to open it. The contents of the bar file are shown in the Content editor. (If the bar file is new, this view is empty.)
  3. Click the Add icon.
  4. Check the boxes for the message flows, message sets, and other files that you want to include. (Duplicates within a bar file are automatically removed.)
  5. Optional: If you want to include your message flow and message set source files, check the Include message flow/set source box.
  6. Optional: If you want to compile ESQL so that it is compatible with Version 2.1 brokers, check the Compile ESQL for brokers version 2.1 box.
  7. Click OK.

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 and message set 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.

Related concepts
Message flow application deployment
Broker archive
Related tasks
Deploying
Deploying a message flow application
Resolving problems when using the workbench
Resolving problems when deploying message flows or message sets
Related reference
Broker Archive editor
Broker Administration perspective