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


Converting subflows that include other legacy resources

You can convert a subflow created as a .msgflow file to a .subflow file by using the Convert to subflow function in IBM® Integration Bus. If the subflow includes other legacy resources, you must convert them before you can convert your subflow.

Before you begin

Set up the initial configuration Creating the initial configuration for the MembersMFP sample.

Procedure

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

  1. In the Application Development view, identify the Integration project located under the Independent resources folder that contains the subflow that you want to convert. Select the subflow, in our example, MembersMFPFlow.msgflow.

    This figure shows that the main message flow contains an MQInput node, a subflow named MembersMFPFlow, and an MQOutput node.

  2. Right-click the subflow and select Convert to subflow.

    This figure shows graphically the steps to start the conversion process. Identify the subflow that you want to convert, right-click it, and select Convert to subflow.

  3. An error window opens that tells you that you cannot convert the subflow. The subflow contains a legacy Mapping node that you must convert before you can select Convert to subflow.

    This figure shows the error window that opens when you try to convert a subflow created as a .msgflow file that includes a WebSphere Message Broker Version 7 Mapping node. The error says: The Mapping node in the message flow is not valid in a subflow.

  4. In the Application development view, identify the Integration project located under the Independent resources folder that contains the subflow that you want to convert. Identify the map that needs to be converted. In our example, it is the MembersMFPFlow_Mapping.msgmap. Select Convert Mesage Map from .msgmap to .map.

    This figure shows graphically the steps that you need to follow to convert the legacy map. Identify the map, right-click it, and select Convert Message Map from .msgmap to .map.

  5. The Message map conversion progress window opens and details the results from converting your map. Click Close.

    This figure shows the message that the map conversion displays when it is completed. The message says: Message map conversion completed.

  6. After you click Close, the Convert Mesage Map from .msgmap to .map function completes. You can see your converted map in the Application Development view, in the Maps folder under your Integration project. The converted map has a .map file extension.

    This figure shows that after you have converted the map, you have two copies of the map: one is a map with a .map file extension, the second one is a backup of the original map and it has a .backup extension.

  7. After you convert the map, you need to fix the following errors:
    • Errors related with transformation functions that require manual conversion steps to finalize its conversion. For more information, see Scenario: Converting a message map to a graphical data map.
    • The error related to the Mapping node that had the legacy map configured. The node is a legacy node, and needs to be replaced by the IBM Integration Bus Mapping node.

      This figure shows how the original Mapping node in the main message flow displays in error. You get the following message: Unable to locate map named "MembersMFPFlow_Mapping" in default broker schema within the project or a referenced project.

  8. To replaced the legacy Mapping node with the IBM Integration Bus Mapping node, complete the following steps:
    • Identify the new Mapping node in the Palette.

    • Drag and drop the Mapping node onto the message flow canvas.

      This figure shows graphically how you must drag and drop a Mapping node into the main message flow, so that you can replace the old Mapping node with the new one.

    • Select the map that you want to associate to the Mapping node. This is the map you just finished converting.

      This figure shows the window you get to validate the map that you associate with the new Mapping node, that is, the map that you have converted in previous steps.

    • Delete the old Mapping node.

      This figure shows the steps to delete the old Mapping node. Right-click the old Mapping node and select Delete.

    • Connect the new Mapping node where you just removed the old Mapping node.

      This figure shows how you connect the new Mapping node in the same positions as the old Mapping node.

  9. After you have converted your legacy map and replaced the old Mapping node with the new one, select the MembersMFPFlow.msgflow subflow. Right-click the subflow and select Convert to subflow.

    This figure shows the steps to start again the conversion of the subflow, after you have replaced the legacy map. Right-click the subflow and select Convert to subflow.

  10. 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.

  11. Optional: If the Conversion Failure window opens, click Ok.

    This figure shows one of the messages that you can get if the conversion process fails. The message reads as follows: Subflow conversion requires that the workspace resources has been built. Please enable "Project -> Build automatically" or "Project -> Clean" before running the subflow conversion.

    Then, select Project > Clean.

    This figure shows graphically how to start the Clean process. Select Project> Clean.

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 MembersMFPFlow.subflow 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_27_.htm | Last updated 2019-07-13 07:48:35