BAR file contents

The .appzip 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.

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.

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.

• If you select Compile and in-line resources in the BAR File editor, a .cmf file is added to the BAR file for each message flow. This file is a compiled version of the message flow.
  The following limitations apply when you are testing compiled message flows:

  • You cannot use the Flow Exerciser with compiled message flows.
  • The flow diagram that is shown in the web user interface does not match how the flow is shown in the IBM® App Connect Enterprise Toolkit.
  • Monitoring events and statistics records do not match the points in the original flow diagram.
• If you do not select Compile and in-line resources in the BAR File editor, a .msgflow file is added to the BAR file for each message flow. This file contains a definition for the message flow. This file is not compiled.

Subflows that are defined in .msgflow files are not displayed in the BAR file as separate items, and are added to the BAR file automatically when the BAR file is built. To include these subflows, you must add only the parent flow. Subflows that are defined in .subflow files are displayed in the BAR file as separate items and can be deployed as individual resources.

.NET assemblies that are required by .NETCompute nodes in message flows are added to the BAR file from your integration project automatically when you add the message flow.

• A .xsd file for each DFDL or XML schema file that is defined in an application or library.
• XSD compressed files (.xsdzip) for each XML schema and WSDL that is defined in a message set.

XML and XSL files are added to the BAR file automatically if they are required by the flow

JAR files that are required by JavaCompute nodes in message flows are added to the BAR file from your Java™ project or integration project automatically when you add the message flow.

JAR files that are available to the integration server include JAR files that you deployed and JAR files that exist in the classes directories in the installation directory. For example, the files IntegrationAPI.jar, jplugin2.jar, and javacompute.jar are always visible to the integration server, and do not have to be deployed separately.

• If you select Compile and in-line resources in the BAR File editor, ESQL code is embedded in the .cmf file that references it.
• If you do not select Compile and in-line resources in the BAR File editor, ESQL files (.esql) are added to the BAR file as individual resources.

If your BAR file contains a mixture of resources that are compiled and resources that are not compiled, you might see unexpected results. For example, if you select the Compile and in-line resources option to create a BAR file that contains an ESQL file and a message flow, the ESQL is embedded in the compiled message flow (.cmf) file. If you then update the ESQL and add it to the BAR file with the Compile and in-line resources option cleared, the ESQL file is added as an individual resource, but the .cmf file uses the original ESQL because the original ESQL remains embedded in the .cmf file. To ensure that all your resources are either compiled or not compiled, when you change the Compile and in-line resources option, also select Remove contents of BAR before building, and rebuild the BAR file.

The .policyxml file contains a list of property values that override, at run time, properties that are set on deployed message flows, message flow nodes, or the integration server.