WebSphere Message Broker Version 8.0.0.5 Betriebssysteme: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

Sehen Sie sich die Informationen zur aktuellen Produktversion im IBM Integration Bus Version 9.0 an.

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 WebSphere® Message Broker 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, a service, or a Message Broker 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 WebSphere Message Broker Version 8.0, you create a subflow to group common functionality so it can be used by one or more solutions. You create new subflows as .subflow files. 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 WebSphere Message Broker. These legacy subflows can be reused in new integration solution developments in WebSphere Message Broker Version 8.0, 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 whast are the performance parameters that you can tune on a subflow.

What to do next