When you deploy a subflow, you must deploy the application,
the service, or the library where the subflow is contained.
You deploy a subflow to an execution group by sending a broker
archive (BAR) file to an execution group in a broker, which unpacks
and stores the contents ready for when your message flows are started.
You can deploy subflows created as
.subflow files in any of the following ways:
- Deploy a subflow as part of an application.
- Deploy a subflow as part of a service.
- Deploy a subflow as part of a library.
The following conditions apply when you deploy a subflow created
as a
.subflow file as part of an integration
solution:
- If you deploy a subflow that is contained in an application, you
must deploy the application to an execution group, which results in
a complete deployment of the application.
- If you deploy a subflow that is contained in a service, you must
deploy the service to an execution group, which results in a complete
deployment of the service.
- If you deploy a subflow that is contained in a library, you must
deploy the library directly to an execution group or deploy the library
as part of the application or service that references this library