Moving a message flow or subflow

You can move a message flow or subflow from one application, library, or integration project to another. You might want to move a flow, for example, if you are reorganizing the resources in your projects.

Before you begin

This task assumes that you have already created a message flow or subflow; for more information about creating a message flow, see Creating a message flow. For more information about creating a subflow, see 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.

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

Procedure

  1. In the Application Development view, expand the appropriate application, library, or integration project, then expand the broker schema folder.
  2. Right-click the message flow or subflow that you want to move, click Move, then select the destination application, library, or integration project.
    Alternatively, you can drag the flow to a new location.

    If the location to which you have dragged a flow is not valid, a no entry symbol is displayed, and the message flow or subflow is not moved.

    If you have created an empty broker schema for this purpose, it might not be visible in the Application Development view if category mode is selected. To see an empty schema in the Application Development view, click Hide Categories The Hide Categories toolbar icon.

  3. Check the Problems view for errors or warnings that are generated by the move.
    Errors are indicated by the error icon The error icon (white cross in a red circle) and warnings are indicated by the warning icon The warning icon (black exclamation mark in a yellow triangle). The Problems view includes errors that are caused by integration node references. When the move is complete, all references to this flow (for example, if this message flow is a reusable error routine that you have embedded in another message flow) are checked.
  4. Double-click each error or warning to correct it.
    The message flow or subflow that contains the error is opened in the editor view and the node in error is highlighted.

Results

When you move a message flow or subflow, the associated files (for example, all ESQL or mapping files) are not automatically moved to the target broker schema. To move these files as well, you must follow the procedure in this topic for each file.