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


Introduction

You use subflows to group common functionality that you want to use several times within multiple integration solutions. This scenario provides information so that you can choose the type of subflow that meets your requirements, and how IBM® Integration Bus handles each type of subflow at the different phases of your integration project.

About this task

When you create an integration solution, you can create an application, an integration service, or an Integration project which are the containers for the message flows and subflows that define the functionality. Your solution can reuse existing functionality or can define new functionality that can be reused by other solutions in your organization.

In IBM Integration Bus, you create a subflow to group common functionality so it can be used by one or more solutions. You create new subflows as a .subflow file. Subflows created as .msgflow files are available for compatibility with earlier versions.

Your can also use legacy subflows which are subflows created as .msgflow files in earlier versions of IBM Integration Bus. These legacy subflows can be reused in new integration solution developments in IBM Integration Bus, but you should convert them to a .subflow file.

To choose which type of subflow to create, you must consider the limitations that apply when you design a subflow and how you build the BAR file for deployment. In addition, you must understand how you update a subflow, and what are the performance parameters that you can tune on a subflow.

What to do next


scnsubflows_01_01_.htm | Last updated 2015-09-24 12:22:41