Deleting a message flow or subflow

Delete message flows or subflows from your application, library, or integration project when you no longer need them.

Before you begin

Deleting a message flow in the IBM® Integration Toolkit deletes the project and its resources. If you are using a shared repository, the repository might retain a copy of a deleted resource.

This task assumes that you have created a message flow or subflow. For more information, see Creating a message flow or Creating a subflow.

About this task

The Application Development view is populated with all the applications, libraries, and integration projects to which you have access. Message flows and subflows are contained in these containers. Message flow files are called message_flow_name.msgflow. Subflow files are called subflow_name.subflow. Applications and libraries are listed at the top level of the Application Development view; integration projects are listed in the Independent Resources folder.

To delete a message flow or subflow, complete the following steps.


  1. In the Application Development view, expand the appropriate application, library, or integration project.
  2. Select the message flow or subflow that you want to delete, then click Edit > Delete.
    A confirmation dialog box is displayed.
  3. Click Yes to delete the message flow or subflow, or No to cancel the delete request.
    When you click Yes, the requested objects are deleted.

    If you maintain resources in a shared repository, a copy is retained in that repository. You can follow the instructions provided by the repository supplier to retrieve the resource if required.

    If you are using the local file system or a shared file system to store your resources, no copy of the resource is retained. Be careful to select the correct resource when you complete this task.

  4. Check the Problems view to see if errors have been returned to the delete request.
    Errors are generated if you delete a message flow or subflow that is embedded in another flow, because the reference is no longer valid.
    1. Click the error in the Problems view.
      The flow that now has a non-valid reference is displayed.
    2. Either remove the node that represents the deleted flow from the parent flow, or create another message flow or subflow with the same name to provide whatever processing is required.


When you delete the message flow or subflow, the files that are associated with the flow (the ESQL and mapping files, if present) are not deleted by this action. If you want to delete these files also, you must do so explicitly.