WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Technical solution
To reuse common application logic in multiple integration solutions, you create a subflow. You must choose whether you create the subflow as a .subflow file or as a .msgflow file, or whether you must convert your legacy subflow to a .subflow file. You must understand how WebSphere® Message Broker handles subflows at the deployment and run time, so that you can configure the subflow properties based on your solution requirements.
The following table summarizes the recommendations regarding subflow type in WebSphere Message Broker:
New subflow created as a .subflow file | New subflow created as a .msgflow file | Legacy subflow (.msgflow file) | |
---|---|---|---|
WebSphere Message Broker Version 6 | NOT supported | Supported | Supported |
WebSphere Message Broker Version 7 | NOT supported | Supported | Supported |
WebSphere Message Broker Version 8 | Supported and recommended for all new developments | Supported, but not recommended for new developments (This option is available for compatibility with earlier versions.) | Supported, however, you are recommended to convert your legacy subflows to a .subflow file |
The scenario has been divided into three sub-scenarios that explain
the different subflow adoption options: