Create a .subflow file, in which you can define subflow content to include in your message flow applications. Use .subflow files to create subflows that you can deploy to an integration server as individual resources, independent of the message flows that use the subflow. You can create one or more subflows and deploy them to one or more integration servers.
You can create subflows to define content that provides a subset of function (for example, a reusable error processing routine) that you can reuse in your message flow applications. You can create subflows either in .subflow files or in .msgflow files. For more information about subflows and the differences between subflows that are defined in .subflow files and subflows that are defined in .msgflow files, see Subflows. The information in this topic describes how to create a .subflow file.
The subflow and its resources are stored in a file system or in a shared repository. A file system can be on the local drive, or a shared drive. If you store files in a repository, you can use all the available repositories that are supported by Eclipse; for example, CVS.
The mode that your integration node is working in can affect the number of message flows that you can use; see Restrictions that apply in each operation mode.
To create a .subflow file, complete the following steps: