Versioning a subflow by using a keyword as a Passthrough node name

To define the version of a subflow, you can set the version of a subflow by adding a Passthrough node to the subflow with a keyword as the node name.

Before you begin

Set up the initial configuration. See Creating the initial configuration for the Error Handler sample.

About this task

When you set a subflow version by adding a Passthrough node to the subflow with a keyword as the node name, you can check the value at run time in the IBM® Integration Console and in the IBM Integration Explorer.

Procedure

To define the version of a subflow, you must complete the following steps in the IBM Integration Toolkit:

  1. Open the subflow in the Message Flow editor.
  2. Add a Passthrough node to a subflow.
  3. Connect the Passthrough node to other nodes in the subflow or leave it unconnected.
  4. Define a keyword. For more information, see Defining a keyword to be used as the container of a subflow version.
  5. Set the keyword in the Node name property of the Passthrough node.

Example

For example, in the Error Handler sample provided with IBM Integration Bus, you can add and check the version of the subflow as follows:
  1. In the IBM Integration Toolkit, open the Error_Handler.subflow subflow in the Message Flow editor:

    In the Application Development view, right-click the name of the subflow, and then select Open with > Message Flow editor.

  2. In the Error_Handler.subflow, connect a Passthrough node.

    This image shows the Error_Handler.subflow subflow with an additional Passthrough node inserted in the subflow after the Input node.

  3. In the Properties tab of the Passthrough node, use the Node name field to set the subflow version. This must be in the format:

    $MQSI name of your subflow Subflow Version = Version xxxx MQSI$.

    where name of your subflow is the name of your subflow; and xxxx is your subflow version identifier.

    This figure shows how by setting the Node name of a Passthrough node, you rename the node so that you can see the keyword that you have defined to set the version as the name of the node.

  4. Create a BAR file that includes the Main_flow.msgflow.

    This figure shows you the options selected to create a BAR file that you can then use to deploy the sample in the run time.

  5. Deploy the message flow into an integration node. For more information, see Deploying integration solutions to a production environment.
  6. In the Integration console, run the mqsireadbar command to check the version of the subflow.

    You run the command using the following syntax:

    mqsireadbar -b your BAR file name

    where your BAR file name is the name of the BAR file you have created to deploy the sample into the run time.

    This figure shows the output of running the mqsireadbar command in the IBM Integration Console.

What to do next

After you set the version of a subflow, create a BAR file. For more information, see Creating a BAR file that includes a subflow created as a .subflow file or Creating a BAR file that includes a subflow created as a .msgflow file.