The BAR file is a compressed file that can contain a number of
different files:
- A .appzip file for each application.
This file contains all resources that belong to the application, such
as .msgflow, .cmf, .esql, .map, .xsd,
and any message set .dictionary and .xsdzip files.
If an application refers to one or more libraries, .libzip files
for the referenced libraries are also added to the BAR file.
- A .libzip file for each library.
This file contains all resources that belong to the library, such
as .msgflow, .cmf, .esql, .map, .xsd,
and any message set .dictionary and .xsdzip files.
If a library refers to other libraries, .libzip files
for the referenced libraries are also added to the BAR file.
- A .cmf file for each message flow,
if in the Broker Archive editor you have selected Compile
and in-line resources. This file is a compiled version
of the message flow. You can have any number of these files within
your BAR file.
- A .msgflow file for each message
flow, unless in the Broker Archive editor you have selected Compile and in-line resources. These files
contain definitions for message flows and are not compiled.
- One or more .subflow files.
These files contain definitions for subflows and can be deployed as
individual resources. These files are not compiled.
- A .appdomainzip file
for each AppDomain. These files contain .NET assemblies used by the
message flow.
- A .dictionary file for each message set dictionary.
You can have any number of these files within your BAR file.
- One or more XSD compressed files (.xsdzip),
if XML schema and WSDL are defined within a message set.
- A broker.xml file. This file is called the broker
deployment descriptor. You can have only one of these files
within your BAR file. This file, in XML format, is contained in the META-INF folder
of the compressed file and can be modified by using a text editor
or shell script.
- One or more XML files (.xml), style sheets (.xsl), and XSLT files (.xslt), if required by nodes in the message flows you have added to this BAR file. The XSLTransform node is one that might require these files.
- One or more JAR files, if required by JavaCompute nodes in the message
flows you have added to this BAR file.
- One or more inbound or outbound adapter files (.inadapter or .outadapter),
if required by WebSphere® Adapter
nodes (for example, the SiebelInput node)
in the message flows you have added to this BAR file.
- One or more PHP script files (.php), if
required by PHPCompute nodes
in the message flows you have added to this BAR file.
- A .esql file for each ESQL file,
unless in the Broker Archive editor you have selected Compile and in-line resources.
- A .map file for each graphical data
mapping routine.
- A .xsd file for each DFDL and XML
schema file in an application or library.
- Other files that you might want to associate with this BAR file.
For example, you might want to include Java™ source
files, .msgflow files, or .wsdl files
for future reference. BAR files can contain all files types. If
you choose to include source files in the BAR file, source projects
for all applications, libraries, and other compiled resources are
added to the src folder of the BAR file.
When you create a BAR file, by default it is
created in an integration project called BARfiles. In the Application
Development view, the new BAR file is shown
under the BARfiles integration project, in
a folder called BARs. When you create the BAR
file by using the New BAR file wizard, you can
choose an alternative location, such as an existing application, library,
or integration project, or you can create an integration project to contain the BAR file.
The BAR file is shown under the application, library, or integration project, in a folder called BARs.
You
can customize the default location for the BAR files that you create.
Click , expand Integration
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 integration project is selected in the Application
Development view when you open the New
BAR file wizard.
Last updated Friday, 21 July 2017