IBM Integration Bus, Version 10.0.0.1 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Message flow version and keywords

When you are developing a message flow, you can define the version of the message flow and other key information that you want to be associated with the message flow.

After the message flow is deployed, you can view the properties of the message flow in the IBM® Integration Toolkit. These properties include the deployment and modification dates and times (the default information that is displayed) and any additional version or keyword information that you set.

To help the identification of message flows, you can use keywords to provide information about the message flow that is deployed.

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 is 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 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 IBM Integration Toolkit would show.

In this example, the version information is also defined by using the Version property of the object.

Property or keyword name Example value
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

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 (RCSVER is a valid keyword name).
  • $MQSI $name=Fred MQSI$ is not acceptable ($name is not a valid keyword name).

ac26550_.htm | Last updated 2015-05-28 20:50:02