WebSphere Message Brokers
File: af03880_
Writer: John Morris-Smith

Task topic

This build: July 31, 2007 21:29:17

Adding files to a broker archive

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 and message sets 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 or message definitions. Likewise, if you check Include source files, the source files for all message flows or message sets in the project are included; you can manually remove the ones 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 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.

If a parent flow and subflow are displayed in the Build dialogue, subflows are added automatically, and so you have to add only 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 they are required by the 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 Broker 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 Build.
  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 Include source files.
  6. Optional: If you want to compile ESQL so that it is compatible with Version 2.1 brokers, check Compile ESQL for brokers version 2.1.
  7. Optional: If you want to compile ESQL so that it is compatible with Version 2.1 brokers, check Build ESQL for brokers version 2.1.
  8. 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.

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.

Related concepts
Message flow application deployment
Broker archive
Related tasks
Deploying
Resolving problems when you use the workbench
Resolving problems when deploying message flows or message sets
Editing configurable properties
Adding multiple instances of a message flow to a broker archive
Related reference
Broker Archive editor
Broker Administration perspective
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:17

af03880_ This topic's URL is: