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


Converting subflows

Use the Error Handler sample to convert a subflow created as a .msgflow file to a .subflow file by using the Convert to subflow function in IBM® Integration Bus.

Before you begin

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

About this task

The Error Handler sample has been migrated from WebSphere® Message Broker Version 7. It includes a legacy subflow that needs to be converted to a subflow created as a .subflow file. This subflow does not contain additional legacy resources that might require conversion before you can convert it. The following figure illustrates the starting point before conversion where your starting point is a message flow named Main_Flow.msgflow and a subflow named Error_Handler.msgflow:

This figure shows graphically the staring point that you use to step through the conversion steps. You start with a Main_Flow.msgflow as the main flow and a Error_Handler.msgflow as the subflow.

Procedure

You must complete the following steps to convert the Error_Handler.msgflow subflow into a subflow created as a .subflow file:

  1. In the Application development view, identify the Integration project located under the Independendent resources folder that contains the subflow that you want to convert. Select the subflow, in our example, Error_Handler.msgflow. Right-click the subflow and select Convert to subflow.

    This figure shows graphically the menu that you must follow to start a conversion process. In the Application Development view, right-click the subflow that you want to convert. Select Convert to subflow.

  2. In the Convert message flow to subflow window, select Update all files, and click Ok. The conversion starts.

    After you select Convert to subflow, a new window opens where you choose Update all files and then select Ok to finish the conversion.

What to do next

You must verify that the converted subflow is created and available:
  1. After the conversion completes, verify that the initial subflow disappears from the Flows folder, and the converted subflow appears under the Subflows folder.

    This figure shows the output of the conversion process, that is, the Error_Handler subflow displays now under subflows as a .subflow file.

  2. Verify that the message flow includes the subflow as a node.

    This figure shows the main message flow opened in the Message Flow editor so you can verify that the subflow does not display any errors.


scnsubflows_01_17_.htm | Last updated 2017-07-17 12:25:08