Deployment unit of broker is called as broker archive or a BAR file.
This broker archive or a BAR file is a compressed file that contains a huge number of various files:
- A .cmf file for each message flow, this file is a compiled version of the message flow. One can have as many number of these files within a BAR file.
- One or more JAR files, if required by JavaCompute nodes in the message flows you have added to this BAR.
- One or more XSD compressed files (.xsdzip), if XML Schema and WSDL are defined within a message set.
- One or more PHP script files (.php), if required by PHPCompute nodes in the message flows you have added to this BAR.
- One or more XML files (.xml), style sheets (.xsl), and XSLT files (.xlst), if required by nodes in the message flows you have added to this BAR. The XSLTransform node is one that might require these files.
- 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.
- A .dictionary file for each message set dictionary. One can have as many number of these files within a BAR file.
- A broker.xml file, this file is called the broker deployment descriptor. One can have only one of these files within a BAR file. This file, in XML format, resides in the META-INF folder of the compressed file and can be modified by using a text editor or a shell script.
- 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.
Related Articles
This post first appeared on IBM Websphere Message Broker Online Training, please read the originial post: here
