WebSphere Message Brokers
File: ak09122_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:32:45

Moving an ESQL file

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:

  1. Switch to the Broker Application Development perspective.
  2. Move the ESQL file in one of the following ways:
    1. Drag and drop the ESQL file 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 (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.

    2. 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.

  3. 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 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.

  4. 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.

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 overview
Message mappings overview
Broker schemas
ESQL modules
Related tasks
Developing message flows
Related reference
Built-in nodes
ESQL reference
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:32:45

ak09122_ This topic's URL is: