Conditions that apply when you deploy a subflow created as
a .subflow file
When you deploy a subflow, you must deploy the application,
the integration service, or the library where the subflow is contained.
You deploy a subflow to an integration server by
sending a BAR file
to an integration server in
an integration node,
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 an integration 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 integration server,
which results in a complete deployment of the application.
- If you deploy a subflow that is contained in an integration service,
you must deploy the integration service to an integration server,
which results in a complete deployment of the integration service.
- If you deploy a subflow that is contained in a library, you must
deploy the library directly to an integration server or
deploy the library as part of the application or the integration service
that references this library