Moving an ESQL file

• Drag the ESQL file that you want to move from its current location to a broker schema within the same or another integration project.

  If the target location that you have chosen is not valid (for example, if an ESQL file of this name exists in the broker schema), the invalid icon is displayed and the move is not completed. 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 .

• Right-click the ESQL file and click Move, or click File > Move. The Move dialog is displayed.

  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.

Check the Problems view for errors (indicated by the error icon ) or warnings (indicated by the warning icon ) generated by the move.

The errors in the Problems view include those errors 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 integration project, all references are still valid. If you have moved the file to another broker schema in the same or another integration project, the references are broken. If you have moved the file to the same named broker schema in another integration 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.