Use the mqsicreatebar command to create deployable broker archive (BAR) files containing message flows and dictionaries.
If you use a repository to store your message flows and dictionaries, you can write scripts that use the mqsicreatebar command and the repository's command-line tools to deploy your message flow applications.
>>-mqsicreatebar-- -data--WorkSpace--+--------------+-----------> '- -b -BarName-' >--+--------------+--+--------------------------+---------------> '- -cleanBuild-' '- -version -VersionString-' >--+----------+--+--------------------------+-------------------> '- -Esql21-' | .-----------------. | | V | | '- -p -----ProjectName---+-' >--+----------------------+--+------------------+---------------> '- -a -ApplicationName-' '- -deployAsSource-' >--+---------------+--+------------------+----------------------> '- -compileOnly-' '- -l -LibraryName-' >--+----------------------------+--+---------------+------------> '- -d -ApplicationDomainName-' '- -o -FilePath-' >--+--------------------+--+-----------------------------+----->< '- -skipWSErrorCheck ' '- -trace - -v -traceFilePath-'
The workspace location is also the default location for projects. Relative paths are interpreted as being relative to the directory from which the command was started.
This parameter is required if the -compileOnly parameter is not used.
The projects defined must already exist in the folder defined in the -data parameter, and must include all projects and their reference projects that a deployable resource, defined in the -o parameter, needs.
The -p parameter is optional with an existing workspace, but you should use -p, together with a new workspace, in a build environment. If you specify multiple projects, you must use the -p parameter once only, for example: -p projectname1 projectname2.
If a project that you specify is part of your workspace but is currently closed, the command opens and builds the project so that the files in the project can be included in the BAR file.
You can add more than one application by using the following format: -a ApplicationName1 ApplicationName2 .... ApplicationName'n'
When the -deployAsSource parameter is used, any applicable resources are added to the BAR file as source files, and are not compiled into message flow .cmf files.
You cannot include both the compiled (.cmf) and source (.msgflow) versions of a message flow in a BAR file.
If this parameter is specified with the -b parameter and one or more of the -a, -l, -d, or -o parameters, the command generates both the compiled resources and the specified BAR file.
You can add more than one library by using the following format: -l LibraryName1 LibraryName2 .... LibraryName'n'
You can add more than one application domain by using the following format: -d ApplicationDomainName1 ApplicationDomainName2 .... ApplicationDomainName1'n'
You can add more than one deployable file to this command by using the following format: -o FilePath1 FilePath2 .... FilePath'n'
The -trace parameter writes trace information into the system output stream, in the language specified by the system locale. When you add one or more applications or libraries to the BAR file, the specified application or library and all referenced projects are opened in the workspace. The trace function records this information so that you can see whether any referenced projects are missing.
If you specify the file name or relative path, the file is created in the default working directory. To use this parameter, you must also set the -trace parameter. You cannot specify the -v parameter on its own.
If you do not run the command from a privileged environment, you are asked to confirm that you want to continue. When you click OK, a new privileged command console is created and the command completed, but all responses are written to the privileged environment and are lost when that console closes when the command completes.
On Linux on x86, the user ID must have write access to the -data (workspace) and -b (BAR file location) directories.
The -b parameter specifies the name of the BAR file and an optional alternative path for BAR file generation. When a path is not specified as part of the -b parameter, the location in the file structure where the mqsicreatebar command runs specifies where the BAR file is created. For example, if you are currently in C:\> and run the mqsicreatebar command, the BAR file is created on C:\. However, if you run the mqsicreatebar with -b c:\myfiles\myflow.bar specified, the BAR file is created in the myfiles directory.
mqsicreatebar -data C:\Workspace -b myflow.bar -p TestFlowProject -o TestFlowProject\TestFlow\Test.msgflow
mqsicreatebar -data C:\Workspace -b C:\myfiles\myflow.bar -p TestFlowProject -o TestFlowProject\TestFlow\Test.msgflow -deployAsSource
mqsicreatebar -data C:\Workspace -b mySet.bar -o TestSetProject\TestSet\messageSet.mset
mqsicreatebar -data C:\Workspace -b mySet.bar -o TestFlowProject\TestFlow\Test.msgflow
TestSetProject\TestSet\messageSet.mset
mqsicreatebar -data C:\Workspace -b myflow.bar -a Application1 -trace