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


Context

This scenario explains how you can use subflows to reuse common logic in an integration solution; how a subflow behaves at run time based on its design and implementation; and how you convert a legacy subflow into an IBM® Integration Bus subflow.

When wanting to reuse common functionality in new integration solutions, there are a number of different points you might be starting from. This scenario covers the following situations:
Regardless of your starting point, this scenario has been divided into sub-scenarios to help you understand how to use subflows in IBM Integration Bus:

Creating a new subflow as a .subflow file

This is the recommended approach for creating subflows.

To comply with the corporate requirement, you can design and implement an audit subflow that can be used by any message flow. You can create a subflow as a .subflow file or as a .msgflow file. However, you are recommended to create the subflow as a .subflow file. The subflow defines new functionality that will be reused by other solutions.

Creating a new subflow as a .msgflow file

This option is maintained for subflow compatibility with previous releases.

You continue to create subflows as .msgflow files whenever these subflows include existing subflows. In any other cases, you create your new subflows as .subflow files.

Converting a legacy subflow

You convert your subflows created as .msgflow files into .subflow files by using the conversion function provided by IBM Integration Bus.


scnsubflows_01_03_.htm | Last updated 2015-11-25 08:25:25