Implementing the solution: Creating a subflow as a .msgflow file

Designing a subflow created as a .msgflow file
If you are migrating subflows from earlier versions of IBM Integration Bus, you need to understand how to define a subflow created as a .msgflow file in IBM Integration Bus.

Versioning a subflow
To enable version control of a subflow at run time, you can set the version by using a keyword or by setting the subflow Version property.

Creating a BAR file that includes a subflow created as a .msgflow file
When deploying a subflow created as a .msgflow file, you need to understand how IBM Integration Bus packages subflows into BAR files, and what are the configurations that you can create to deploy into the IBM Integration Bus run time.

Deploying a subflow created as a .msgflow file
You deploy a subflow created as a .msgflow file to an integration server by sending a broker archive (BAR) file to an integration server in an integration node, which unpacks and stores the contents ready for when your message flows are started.

Updating a subflow
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 IBM Integration Bus run time. For example, if a subflow is deployed as part of an application or an integration service, then you need to update your applications or integration services to include the new subflow version, and then redeploy the application or integration service.

Configuring a message flow that includes subflows
Depending on your subflow design, that is, the number of Input nodes that you have modeled, and how you configure the overall message flow BAR file deployment properties and the Input node deployment properties, IBM Integration Bus handles threads at run time differently. This can impact your solution performance and your message parallel processing behavior at run time.