Moving a message flow

You can move a message flow from one broker schema to another within the same project or to a broker schema in another project. You might want to do this, for example, if you are reorganizing the resources in your projects.

Before you start

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

To move a message flow:

  1. Switch to the Broker Application Development perspective.
  2. Drag and drop the message flow that you want to move from its current location to a broker schema within the same or another message flow project. If the target location that you have chosen is not valid, a black no-entry icon appears over the target, an error dialog is displayed, and the message flow is not moved.

    You can move a message flow to another schema in the same project or to a schema in another message flow project.

  3. If you prefer, you can:
    1. Right-click the message flow that you want to move (<message_flow_name>.msgflow) in the Navigator view and click Move, or File > Move The Move dialog is displayed. This contains a list of all valid projects to which you can move this message flow.
    2. Select the project and the broker schema within the project to which you want to move the message flow. You can move a message flow to another schema in the same project or to a schema in another message flow project.
    3. Click OK to complete the move, or Cancel to cancel the move. If you click OK, the message flow is moved to its new location.
  4. Check the Tasks view for any errors (indicated by the error icon The error icon (white cross in a red circle)) or warnings (indicated by the warning icon The warning icon (black exclamation mark in a yellow triangle)) generated by the move. The errors in the Tasks view include those caused by broker references. When the move is done, all references to this message flow (for example, if this is a reusable error message flow that you have embedded in another message flow) are checked.

    If you have moved the message flow within the same broker schema (in the same or another project), all references are still valid.

    However, if you move the message flow from one broker schema to another (in the same or a different project), the references are broken.

    This is because the resources are linked by a fully-qualified name of which the broker schema is a part. Information about any broken references is written to the Tasks view, for example, Linked or nested flow mflow1 cannot be located.

  5. Double-click each error or warning to correct it. This opens the message flow that has the error in the editor view and highlights the node in error.
Related concepts
By name linking
Message flows overview
Related tasks
Developing message flows
Opening an existing message flow
Defining message flow content
Related reference
Broker Application Development perspective
Built-in nodes