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

BAR builder behavior for subflows created as .subflow files

Learn how a BAR file is created based on your message flow design, the subflows that you created as .msgflow files, and the build options that you choose. Notice the differences between WebSphere® Message Broker Version 8.0.0.0 and WebSphere Message Broker Version 8.0.0.1.

Packaging considerations in WebSphere Message Broker Version 8.0.0.0

When you build a BAR file in WebSphere Message Broker Toolkit, you must consider the following BAR builder behavior:
  • When you add a message flow to a BAR file, the BAR builder will automatically include any required subflows.
  • Message flows are included in the BAR file as compiled objects, that is, as .cmf files.
    Note: The BAR file creation option Compile and in-line resources is not available in WebSphere Message Broker Version 8.0.0.0, which means that a message flow is always added to a BAR file in its compiled form.
  • If a subflow created as a .subflow file is included in a message flow, then the BAR builder creates a compiled message flow for the message flow and includes the subflow source file for the subflow created as a .subflow file.

Packaging considerations in WebSphere Message Broker Version 8.0.0.1 and later versions

When you build a BAR file in WebSphere Message Broker Toolkit, you must consider the following BAR builder behavior:
  • When you add an application or a service to a BAR file, the BAR builder will automatically include any resources defined within the application project, or the service project, including all the required subflows.
    This figure shows all the resources that are selected when you select an application in the Prepare tab of the BAR editor.
  • You can leave the BAR file creation option Compile and in-line resources option not selected, so that a message flow is added to a BAR file as a .msgflow source file. Subflows created as .msgflow files cannot be embedded in the message flow. You can only add subflows created as .subflow files to the BAR file.
    Note: This is the recommended approach to creating a BAR file that includes message flows and subflows created as .subflow files.
    This figure shows how the different resources included in the application are stored in the BAR file with the Compile and in-line resources option not selected during the BAR file build.
    Note: If you try to create a BAR file with the option Compile and in-line resources not selected, where the message flow has embedded subflows created as .msgflow files, you get the following error:
    If you try to create a BAR file with the option Compile and in-line resources not selected, where the message flow has embedded subflows created as .msgflow files, you get a BIP0841E error.
  • You can choose to select the BAR file creation option Compile and in-line resources so that a message flow is added to a BAR file in its compiled form. Message flows are included in the BAR file as compiled objects, that is, .cmf files. Subflows are included as .subflow source files.
    Note: This is not a recommended approach. It is available for compatibility with previous releases of WebSphere Message Broker.
    This figure shows how the different resources included in the application are stored in the BAR file with the Compile and in-line resources option selected during the BAR file build.