When updating a subflow, you need to check the subflow
version, and understand how you can deploy a new version of the subflow
to the WebSphere® Message
Broker run time. For example, if a subflow is deployed as part of
an application or a service, then you need to update your applications
or services to include the new subflow version, and then redeploy
the application or service.
Procedure
To update a subflow, complete the following steps:
- Check the version of a subflow. For more information, see Checking the Version of a subflow at run time.
- Update the value of the subflow version.
You update the version of a subflow manually in the WebSphere Message Broker Toolkit. You can
modify the Label property of the Passthrough
node, the Name property of the Passthrough
node, or the Version property of a subflow.
For more information on how to define the version of a subflow, see Versioning a subflow.
- Update the subflow implementation to include the new requirements,
for example, add new nodes or modify the logic of a Compute node.
- Update the BAR file and refresh its contents. For more
information, see Refreshing the contents of a broker archive.
- Deploy the BAR file into the WebSphere Message Broker run time. For
more information, see Deploying a broker archive file
.
For subflows
created as a
.subflow file, you must consider
the following behaviour when deploying a new version of a subflow:
- If the subflow is deployed as part of an application, a service,
or a library, then you need to update your applications, services,
and libraries to include the new subflow version, and redeploy them.
Note: If the application, service, or library has been deployed before,
redeploying it removes the currently deployed application, service,
or library and its contents, and replaces it with the deployed application,
service, or library.
- If the subflow is deployed separately from any of the message
flows that use this subflow and you deploy a new version of the subflow,
then all the message flows are updated automatically.
For subflows created as a
.msgflow file, you must consider the following behaviour when deploying a
new version of a subflow:
- You need to update your applications, services, and independent
resources that use the subflow to include the new subflow version,
and redeploy them.
Note: Legacy subflows can only be updated at
run time when the parent message flow is recompiled and deployed.
What to do next
Configure a message flow that includes subflows created
as .subflow files. For more information, see Configuring a message flow that includes subflows.