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:Complete the following
task:
- Switch to the Broker Application Development perspective.
- Drag the message flow that you want to move from its current location
to a broker schema in 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 box 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.
Alternatively,
you can use the following method:
- Right-click the message flow that you want to move (message_flow_name.msgflow)
in the Broker Development view and click Move, or . The
Move dialog box is displayed. This contains a list of all valid projects to
which you can move this message flow.
- Select the project and the broker schema in 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.
- 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.
- Check the Tasks view for any errors (indicated by the error icon
) or warnings (indicated by the warning icon
) that are generated by the
move. The errors in the Tasks view include those that are caused
by broker references. When the move is complete, 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
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.
- Double-click each error or warning to correct it. The
message flow that contains the error is opened in the editor view and the
node in error is highlighted.
When you move a message flow, the
associated files (for example, any ESQL or mapping files) are not automatically
moved to the target broker schema. If you want to move these files as well,
you must do so explicitly by following the procedure in this topic.