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
Whether you create a subflow as a .subflow file or as a .msgflow file, or whether you convert your legacy subflow to a .subflow file, you must understand how WebSphere® Message Broker handles subflows at deployment and run time, so that you can design and configure your subflow based on your solution requirements.
Before you begin
Read the Technical solution section, and decide which type of subflow you want to create.
Procedure
Follow the relevant sub-scenario:
- If you are developing a new subflow in WebSphere Message Broker, follow the sub-scenario: Creating a subflow as a .subflow file.
- If you have legacy subflows from earlier versions, and you still want to develop a new subflow in WebSphere Message Broker as a .msgflow file, follow the sub-scenario: Creating a subflow as a .msgflow file.
- If you want to convert your legacy subflows, follow the sub-scenario: Converting legacy subflows.
What to do next
When you know which type of subflow you want to create
or whether you want to convert a legacy subflow, follow the relevant
sub-scenario:
- If you want to create a subflow as a .subflow file, see Implementing the solution: Creating a subflow as a .subflow file.
- If you want to create a subflow as a .msgflow file, see Implementing the solution: Creating a subflow as a .msgflow file.
- If you want to convert a legacy subflow, see Implementing the solution: Converting legacy subflows.