When you edit your ESQL file, you can save it both to preserve the additions and modifications that you have made and to force the editor to validate the file's content.
Before you start
To complete this task, you must have completed the following task:
To save an ESQL file:
You can request additional validation when you set ESQL preferences. Click
. The Preferences dialog is displayed.Validating message definitions can impact response times in the editor, particularly if you have complicated ESQL that makes many references to a complex message definition. You might choose to delay this validation. However, you are recommended to invoke it when you have finished developing the message flow and are about to deploy it, to avoid runtime errors.
For each error found, the editor writes an entry in the Tasks view, providing both the code line number and the reason for the error.The editor might also
find potential error situations, that it highlights as warnings (with the
warning icon), which it also writes to the tasks view. For example,
you might have included a BROKER SCHEMA statement that references
an invalid schema (namespace).
Check your code, and make the corrections required by that statement or function.
You can save a copy of this ESQL file by using
.If you want to save this ESQL file in another project, the project must already exist (you can only select from the list of existing projects). You can save the file with the same or another name in another project.
Related concepts
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
![]() ![]() |
ak09035_ |