Version and keyword information for deployable objects

Object version in the Broker Archive editor

You cannot edit the Version column.

You can use the mqsireadbar command to list the keywords that are defined for each deployable file within a deployable archive file. For more information, see mqsireadbar command.

Adding version information to an application or library at deployment time

At deployment time, you can manually assign a version to an application or library. That version is not necessarily associated with the content of a particular file in the source control system. You can manually assign a version by creating a file called META-INF/keywords.txt inside the .appzip or .libzip file in the BAR file. You can add a literal string to the text file; for example, $MQSI_VERSION=v1.0 MQSI$. You can use this method to assign to an application or library a version that is independent of the versions of the resources in the application or library.

Adding version and other keyword information to a DFDL or XML Schema file

As with other deployed objects, you can add version and keyword information to your DFDL or XML Schema files by including literal strings.

$MQSI_VERSION=v1.0 MQSI$ $MQSI Author=DFDL Modeler MQSI$

<xsd:documentation>$MQSI_VERSION=v1.1 MQSI$ $MQSI Author=XML Modeler MQSI$</xsd:documentation>

Version, deployment time, and keywords of deployed objects

If the keyword information is not available, a message is displayed in the Properties view to indicate the reason; for example, if keyword resolution has not been enabled at deployment time, the Properties view displays the message Deployed with keyword search disabled.

Path and Comment columns

If you add source files, the Path column on the Manage tab is populated automatically.

To add a comment, double-click the Comment column and type the text that you require.