In IBM WebSphere Message Broker Version 8.0, you use subflows to group common functionality that you want to use several times within multiple integration solutions. You can create subflows as a .subflow file or as a .msgflow file, although creating a .subflow file is the recommended approach for new developments. Subflows created as a .msgflow file are maintained for compatibility with earlier versions. You should convert these subflows into .subflow files.

The scenario Reusing common application logic in multiple integration solutions explains how WebSphere Message Broker Version 8.0 handles subflows created as a .subflow file and as a .msgflow file; provides guidance on how to design a subflow depending on the type; and demonstrates how to convert legacy subflows into WebSphere Message Broker Version 8.0 subflows.

If you have any suggestions for other scenarios associated with the use of subflows, please let us know by adding a comment.

Related posts

Join The Discussion

Your email address will not be published. Required fields are marked *