WebSphere Message Brokers
File: ac26550_
Writer: Bill Oppenheimer

Concept topic

This build: July 31, 2007 21:19:51

Message flow version and keywords

When you are developing a message flow, you can define the version of the message flow as well as other key information that you want to be associated with it. After the message flow has been deployed, you can view the properties of the message flow in the workbench. These properties include 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 of 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.

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 value 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 must follow certain rules to ensure that the information can be parsed. The following example shows some values that you might want to define in the Long Description property:

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

The following table contains the information that the workbench shows.

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.

Restrictions within keywords

Do not use the following characters within keywords because they cause unpredictable behavior:
^$.|\<>?+*=&[]
You can use these characters in the values that are associated with keywords; for example:
  • $MQSI RCSVER=$id$ MQSI$ is acceptable
  • $MQSI $name=Fred MQSI$ is not acceptable
Related concepts
Viewing version, keyword, comment, and path information for deployable objects
Message set version and keywords
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 style sheets
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:19:51

ac26550_ This topic's URL is: