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 or .shlibzip files
for the referenced libraries are also added to the BAR file.
- A .libzip file for each static library.
This file contains all resources that belong to the static library,
such as .msgflow, .cmf, .esql, .map, .xsd,
and any message set .dictionary and .xsdzip files.
If a static library refers to other static libraries, .libzip files
for the referenced libraries are also added to the BAR file.
- A .shlibzip file for each shared
library. This file contains all resources that belong to the shared
library, such as .cmf, .esql, .map, .xsd,
and any message set .dictionary and .xsdzip files.
If a shared library refers to other shared libraries, .shlibzip files
for the referenced libraries are also added to the BAR file.
- A .cmf file for each message flow if, in
the BAR File editor, you 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 BAR File
editor, you 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 if they are contained in integration projects. 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 in your BAR file.
- One or more XSD compressed files (.xsdzip),
if XML schema and WSDL are defined in a message set.
- A broker.xml file. This file is called the integration
node deployment descriptor.
You can have only one of these files in 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 that you have added to this BAR file. The XSLTransform node might require
these files.
- One or more JAR files, if required by JavaCompute nodes in the message
flows that 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 that you have added to this BAR file.
- A .esql file for each ESQL file,
unless in the BAR File editor
you have selected Compile and in-line resources.
- A .map file for each graphical data
mapping routine.
- A .xsd file for each DFDL or 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.
You can customize the default location of BAR files.