Right-click the broker schema within the message flow project to
which you want to copy the message flow and click Paste. You can copy the message flow within the same broker schema within the
same message flow, or to a different broker schema within the same message
flow project, or to a broker schema in a different message flow project. When you copy a message flow, the associated files (ESQL and
mapping, if present) are not automatically copied to the same target message
flow project. If you want these files copied as well, you must do this explicitly
following this procedure.
You might also need to update
nodes that have associated ESQL or mappings, to ensure that modules are unique.
For example, if you have created a message flow (Test1 for example)
that contains a single Compute node, and you copy message flow Test1 and its
associated .esql file to the same broker schema within the same message flow
project (and give the new copy a different name, for example Test2), there
are now two modules named Test1_Compute within the single schema. One is within Test1.esql,
the second within Test2.esql.
This
is not supported, and an error message is written to the Tasks view when you
have completed the copy action. You must rename the associated ESQL modules
within the .esql file and update the matching node properties to ensure that
every module within a broker schema is unique.