Message flow version and keywords

When you are developing a message flow, you can define the version of the message flow as well as any other key information that you need to be associated to it. After the message flow has been deployed, the Configuration Manager can be used to display the properties of the message flow. This includes the deployment and modification dates and times (the default information that is displayed) as well as any additional version or keyword information that you have set.

You can define information to give details on the message flow that has been deployed, therefore you can check that it is the message flow that you expect.

Version

You can set the version of the message flow in the Version property. This is in the Properties dialog.

You can also define a default message flow version in the Default version tag of the message flow preferences. All new message flows that are created after this has been set have this default applied to the Version property at the message flow level.

Keywords

Keywords are extracted from the compiled message flow (the .cmf file) rather than the message flow source (the .msgflow file). Not all of the source properties are added to the compiled file. Therefore, add message flow keywords in only these places:
  • The label property of a passthrough node
  • ESQL comments or string literals
  • The Long Description property of the message flow

Any keywords that you define need to follow certain rules to ensure that the information can be parsed. The following is an example of what you can define in the Long Description property:

$MQSI Author=John Smith MQSI$
$MQSI Subflow 1 Version=v1.3.2 MQSI$

The information the Configuration Manager will show is:

Message flow name  
Deployment Time 28-Aug-2004 15:04
Modification Time 28-Aug-2004 14:27
Version v1.0
Author John Smith
Subflow 1 Version v1.3.2

In this display the version information has also been defined using the Version property of the object. If the version information has not been defined using the property, it is omitted from this display.

If message flows contain subflows, you can embed keywords in each subflow.

Related concepts
Viewing version and keyword information for deployable objects
Adding keywords to ESQL files
Adding keywords to subflows
Related tasks
Using subflows
Adding keywords to JAR files
Related reference
Guidance for defining keywords
Description properties for a message flow
Message flow preferences
Passthrough node
Adding keywords to XSL stylesheets