Implementing the solution: Converting legacy subflows

To convert legacy subflows into subflows created as .subflow files, you use the Convert to subflow function in IBM® Integration Bus.

About this task

The following conditions apply when you convert a subflow created as a .msgflow file into a subflow created as a .subflow file:
  • If the subflow contains subflows that are defined as .msgflow files, you must convert these subflows to .subflow files.
  • If the subflow is used by a message flow, you must update the parent message flow so that it references the new .subflow file.
  • If the subflow contains other legacy resources such as the WebSphere® Message Broker Version 7.0 Mapping node, you must convert these resources before you can run the Convert to subflow function.
Note: Subflows created as .subflow files are the recommended type of subflow in IBM Integration Bus. You should convert your subflows created as .msgflows files into .subflow files.

Procedure

Complete the following steps to convert a legacy subflow:

  1. Learn how IBM Integration Bus handles your legacy subflows at deployment and run time. For more information, see Implementing the solution: Creating a subflow as a .msgflow file.
  2. Learn how IBM Integration Bus handles subflows created as .subflow files at deployment and run time. For more information, see Implementing the solution: Creating a subflow as a .subflow file.
  3. Identify other resources included in your subflow that require conversion:
    • WebSphere Message Broker Version 7.0 Mapping nodes: You must convert a message map from a previous version of WebSphere Message Broker to a graphical data map. For more information, see Converting a message map from a .msgmap file to a .map file.
    • User-defined nodes created from subflows in WebSphere Message Broker Version 7: If you have a user defined node that was created from a subflow, you cannot use it in a subflow created as a .subflow file. There is no automatic conversion for these nodes. You must implement a new subflow to replace the user defined node or convert the original subflow that you used to create a user-defined node. For more information, see Using a subflow as a user-defined node.
    • MQOptimizedFlow nodes: These are deprecated nodes in WebSphere Message Broker Version 8, IBM Integration Bus Version 9.0, and later versions.
    • Nodes representing subflows that are created as .msgflow files: You must convert all the subflows included in your subflow.
  4. Convert your legacy subflows created as .msgflow files to .subflow files. For more information, see Converting subflows.
  5. Update existing solutions to use the converted subflow instead of the legacy subflow.

    When you convert a subflow created as a .msgflow file into a .subflow file, all the subflow references that you have in parent message flows and other subflows to this subflow are automatically converted.

Results