mqsicreatebar's little brother: mqsipackagebar
ThomasBien 060001PQVD Visits (11145)
WebSphere Message Broker (WMB) version 8 has seen several new features arrive in its first fixpack, 188.8.131.52. One of these is the ability to create deployable BAR files in your runtime environment.
Previously, a WMB Toolkit installation was needed to create BAR files through either the GUI or the 'mqsicreatebar' command. This command would compile all of your runtime resources (message flows, message sets, Java™ projects, etc) and place them in a single deployable file, that would then be interpreted by either the Configuration Manager (in older versions), or the Broker itself.
WMB 184.108.40.206 introduces the ability to deploy message flows without needing to compile them into *.cmf files. As a result, the 'mqsipackagebar' command was created. This command is shipped with the WMB runtime, not the Toolkit. This means you do not need the Toolkit installed to create a bar file. With the proper configuration, you can even run this command on machines that do not have a WMB runtime installed.
However, 'mqsipackagebar' isn't as powerful as its older brother: you will still need to compile your message sets and Java projects prior to using this command. The 'mqsipackagebar' command can be used to add these pre-compiled resources to a BAR file, but it cannot actually compile them. For the same reason, when you add a message flow or ESQL to a BAR file with 'mqsipackagebar', it will not be compiled into a .cmf, but will appear as a *.msgflow or *.esql file.