Using Query Designer
Note:
Apama queries are deprecated and will be removed in a future release.
Apama's Query Designer editor provides a graphical environment that business analysts can use to define and update Apama queries without the need to write source code. An Apama query monitors a very large number of real-world entities and processes events on a per-entity basis, for example, all events related to one credit card account.
See
Use cases for queries which describes some of the use cases for using queries.
Query Designer provides two views of a query definition:
Design — Business analysts define and update query definitions in this view. The
Design tab provides an event palette and a canvas for defining an event pattern of interest. Toolbars, tooltips, and dialogs make it easy to define the events of interest to the query as well as any required parameters, conditions for finding matches, aggregate calculations and actions to take when a match set is found.
Source — Application developers can examine and update query definition source code in the EPL code editor available from the
Source tab.
Query Designer keeps the two views synchronized. Any changes made in the Design view are reflected in the Source view and vice versa.
See also:
Defining Queries, which describes the EPL constructs for writing query code, and
Deploying and Managing Queries.