WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Creating a broker archive (BAR) file

Create a separate broker archive (BAR) file for each configuration that you want to deploy to execution groups on your brokers.

Before you start:
When you create a BAR file, by default it is created in a Message Broker project called BARfiles. You can choose an alternative location when you use the New BAR file wizard, but you can also customize the default location for the BAR files that you create.
  1. Click Window > Preferences.
  2. Expand Broker Development, then select Build Broker Archive.
The default behavior is to create BAR files in the project called BARfiles. You can change the name of the default project. Alternatively, you can choose to create BAR files in whichever application, library, or Message Broker project is selected in the Broker Development view when you open the New BAR file wizard.

Using the WebSphere Message Broker Toolkit

Follow these steps to create a BAR file by using the WebSphere® Message Broker Toolkit:

  1. Click File > New > BAR file.
  2. Select the location for your BAR file.

    The default location depends on the preferences that you have set; for more information, see the Before you start section of this topic. You can select an existing application, library, or Message Broker project, or you can create a new Message Broker project by clicking New.

  3. Enter a name for the BAR file that you are creating.
  4. Click Finish.

A file with a .bar extension is created and is displayed under the application, library, or Message Broker project, in a folder called BARs. The BAR file editor opens. All BAR files are also shown in a separate category in the Broker Development view called BARs. Each BAR file listed here displays information about the project in which the BAR file is stored.

Next:
Add files to the BAR file and deploy the BAR file by following the instructions in the following topics:
  1. Adding files to a broker archive
  2. Deploying a broker archive file

Using the mqsipackagebar command

Before you start:

If you want to use the mqsipackagebar command to create your BAR file, you must compile any message sets or Java™ code before you create the BAR file. For more information, see Compiling resources for the mqsipackagebar command.

You can create broker archive (BAR) files on machines that do not have WebSphere Message Broker installed, by using the mqsipackagebar command. To configure your environment so that you can run the mqsipackagebar command on a machine that does not have WebSphere Message Broker installed, see Configuring environments without the Broker component installed.

When you create BAR files by using the mqsipackagebar command, add deployable resources to ensure that your BAR file can be deployed.

To create a BAR file by using the mqsipackagebar command, complete the following steps:

  1. Open a command window that is configured for your environment.
  2. Enter the command, typed on a single line. For example:
    mqsipackagebar -a barName -k applicationNames -v traceFile

    You must specify the -a (BAR file name) parameter. The -k (application names) parameter is optional. You can also use the -o parameter to specify the path for a specific file, or the -y parameter to specify a library. For further details, see mqsipackagebar command.

    To see trace information for BAR file deployment, add the -v parameter.

    A file with a .bar extension is created.

Using the mqsicreatebar command

Follow these steps to create a BAR file by using the mqsicreatebar command:

  1. Open a command window that is configured for your environment.
  2. Enter the command, typed on a single line. For example:
    mqsicreatebar -b barName -a applicationNames -trace

    You must specify the -b (BAR file name) parameter. The -a (application names) parameter is optional. You can also use the -o parameter to specify the path for a specific file, or the -l parameter to specify a library. For further details, see mqsicreatebar command.

    If you have changed resources in the BAR file by using external tools, add the -cleanBuild parameter to refresh all the projects and run a clean build.

    To see trace information for BAR file deployment, add the -trace parameter. To force compilation of the BAR file if errors exist in the workspace, add the -skipWSErrorCheck parameter.

    A file with a .bar extension is created.

Next:
Add files to the BAR file and deploy the BAR file by following the instructions in the following topics:
  1. Adding files to a broker archive
  2. Deploying a broker archive file
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:02


Task topicTask topic | Version 8.0.0.7 | af03870_