Use the mqsipackagebar command to create deployable broker archive (BAR) files. You can use this command to create BAR files on machines that do not have the IBM® Integration Toolkit installed.
If you use a repository to store your message flows and dictionaries, you can write scripts that use the mqsipackagebar command and the command-line tools that are available in the repository to deploy your message flow applications.
Resources that you add to a BAR file by using the mqsipackagebar command are not compiled when they are added. To deploy a BAR file that you create by using this command, you must add deployable resources to the BAR file. For example, if you want to include Java™ code or message sets in your BAR file, you must first compile these files before you use the mqsipackagebar command to add them to your BAR file. To compile these resources, see Compiling resources for the mqsipackagebar command. You cannot include both the compiled (.cmf) and source (.msgflow) versions of a message flow in a BAR file.
>>-mqsipackagebar-- -a --BarName--+--------------------+--------> '- -w --RootLocation-' .---------------------------------------------. | .--------------. | V V | | >------+- -o ------FilePath---+--------------+---+--+------+----> | .---------------------. | +- -u -+ | V | | '- -d -' +- -k ------ApplicationName---+-------+ | .-----------------. | | V | | +- -y ------LibraryName---+-----------+ | .---------------------------. | | V | | '- -n ------ApplicationDomainName---+-' >--+------+--+---------------------+--------------------------->< '- -i -' '- -v --traceFilePath-'
(Required) The name of the BAR (compressed file format) archive file where the result is stored. The BAR file is replaced if it already exists and the META-INF/broker.xml file is created.
Used together, the -o option specifies the path to deployable files and the -w option specifies the path to the project directory. For example, mqsipackagebar -w c:/MyProject -a MyBar.bar -o Flow/a.msgflow Subflow/b.subflow specifies a RootLocation of directory MyProject with the FilePath specifying deployable files a and b in the Flow and Subflow directories.
You can add more than one deployable file to this command by using the following format: -o FilePath1 FilePath2 .... FilePath'n'
By default files with only the following extensions are included in the BAR file: .xsdzip, .tblxmi, .xsd, .wsdl, .dictionary, .xsl, .xslt, .xml, .jar, .inadapter, .outadapter, .insca, .outsca, .descriptor, .php, .idl, .mqsc, .rule, .rules, .map, .esql, .msgflow, and .subflow. You can specify the -i option to include files with any extension.
You can add more than one application by using the following format: -k ApplicationName1 ApplicationName2 .... ApplicationName'n'
By default files with only the following extensions are included in the BAR file: .xsdzip, .tblxmi, .xsd, .wsdl, .dictionary, .xsl, .xslt, .xml, .jar, .inadapter, .outadapter, .insca, .outsca, .descriptor, .php, .idl, .mqsc, .rule, .rules, .map, .esql, .msgflow, and .subflow. You can specify the -i option to include files with any extension.
You can add more than one library by using the following format: -y LibraryName1 LibraryName2 .... LibraryName'n'
By default files with only the following extensions are included in the BAR file: .xsdzip, .tblxmi, .xsd, .wsdl, .dictionary, .xsl, .xslt, .xml, .jar, .inadapter, .outadapter, .insca, .outsca, .descriptor, .php, .idl, .mqsc, .rule, .rules, .map, .esql, .msgflow, and .subflow. You can specify the -i option to include files with any extension.
You can add more than one application domain by using the following format: -n ApplicationDomainName1 ApplicationDomainName2 .... ApplicationDomainName'n'
All files in the specified application domain are included in the BAR file.
Specify the resources that you want to update by using the -o, -k, -y, and -n options. If the BAR file does not exist, a new file is created.
Specify the resources that you want to delete by using the -o, -k, -y, and -n options.
If you use this option, all files specified by the -o, -k, -y, and -n options are included in your BAR file. If you do not use this option, only deployable files in the specified locations are added to the BAR file.
If you specify the file name or relative path, the file is created in the default working directory.
mqsipackagebar -w C:\Workspace -a myflow.bar -o TestFlowProject\TestFlow\Test.msgflow
mqsipackagebar -w C:\Workspace -a myflow.bar -k Application1 -v tracefile
<target name="run_mqsipackagebar" description="--> runs mqsipackagbar from an ant task">
<java classname="com.ibm.broker.config.appdev.FlowRendererBAR"
failonerror="true"
fork="true">
<arg line="-a MyBAR.bar"/>
<arg line="-k MyApplication"/>
<classpath>
<fileset dir="${MQSI_JARPATH}">
<include name="*.jar"/>
</fileset>
</classpath>
</java>
</target>