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
Implementing the solution: Converting legacy subflows
To convert legacy subflows into subflows created as .subflow files, you use the Convert to subflow function in WebSphere® Message Broker.
About this task
The following conditions apply when you convert a subflow
created as a .msgflow file into a subflow created
as a .subflow file:
- If the subflow contains subflows that are defined as .msgflow files, you must convert these subflows to .subflow files.
- If the subflow is used by a message flow, you must update the parent message flow so that it references the new .subflow file.
- If the subflow contains other legacy resources such as the WebSphere Message Broker Version 7.0 Mapping node, you must convert these resources before you can run the Convert to subflow function.
Note: Subflows created as .subflow files are the recommended type of subflow in Websphere Message Broker.
You should convert your subflows created as .msgflows files into .subflow files.
Procedure
Complete the following steps to convert a legacy subflow:
Results
Next steps:
- To learn how to convert a subflow that does not include other legacy resources, see Converting subflows.
- To learn how to convert a subflow that does not include other legacy resources, see Converting subflows that include other legacy resources.