Deleting a message flow

You can delete a message flow that you have created in a message flow project if you no longer need it.

Deleting a message flow in the workbench deletes the project and its resources, and the Configuration Manager does not hold a copy. If you are using a shared repository, the repository might retain a copy of a deleted resource.

In previous releases you could remove resources from the Control Center, which removed the reference in your workspace, but retained the resource in the Configuration Manager repository.

Before you start

To complete this task, you must have completed the following task:

To delete a message flow:

  1. Switch to the Broker Application Development perspective.
  2. Select the message flow in the Navigator view (<message_flow_name>.msgflow) and press the Delete key. A confirmation dialog is displayed.

    You can also right-click the message flow in the Navigator view and click Delete, or click Edit > Delete. The same dialog is displayed.

  3. Click Yes to delete the message flow definition file 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 very careful to select the correct resource when you complete this task.

  4. Check the Tasks view for any errors that are caused by the deletion. Errors are generated if you delete a message flow that is embedded within another flow because the reference is no longer valid.
    1. Click the error in the Tasks view This opens the message flow that now has a non-valid reference.
    2. Either remove the node that represents the deleted message flow from the parent message flow, or create a new message flow with the same name to provide whatever processing is required.
Related concepts
Message flows overview
Related tasks
Developing message flows
Creating a message flow
Related reference
Built-in nodes