If you move a message flow from one broker schema to another, or from one project to another, you might want to move any ESQL file that is associated with that message flow.
Before you start
To complete this task, you must have completed the following task:
To move an ESQL file:
If the target location that you have chosen is not valid (for example, if an ESQL file of this name already exists in the broker schema), the invalid icon is displayed and the move is not completed.
Select the project and the broker schema from the list of valid targets that is shown in the dialog.
Click OK to complete the move, or Cancel to cancel the request.
If you click OK, the ESQL file is moved to its new location.
The errors in the Tasks view include those caused by broken references. When the move is completed, all references to this ESQL file are checked. If you have moved the file within the same named broker schema within the same message flow project, all references are still valid. If you have moved the file to another broker schema in the same or another message flow project, the references are broken. If you have moved the file to the same named broker schema in another message flow project, the references might be broken if the project references are not set correctly to recognize external references in this file. These errors occur because resources are linked by a fully-qualified name.
When you move an ESQL file, its associated files (for example, the message flow file) are not automatically moved to the same target broker schema. You must move these files yourself.
Related concepts
Project references
Message flows
Mappings
Broker schema
ESQL modules
Related tasks
Developing message flow applications
Related reference
Built-in nodes
ESQL
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ak09122_ |