Oracle CEP Visualizer Panels that Require Refresh

Overview of Oracle CEP Visualizer 1-9 Event Processing Network EPN, application lifecycle, and Oracle CQL and EPL rules. For more information, see: ■ Chapter 3, Overview of Application Tasks ■ Section 1.3.1.1, The com.bea.wlevs.dataservices Application

1.3.1.1 The com.bea.wlevs.dataservices Application

The com.bea.wlevs.dataservices application, called dataservices for short, is internal to Oracle CEP Visualizer and is automatically deployed every time you start an Oracle CEP server instance. You are not allowed to uninstall the dataservices application. The purpose of this application is to provide a filter for diagnostic monitoring metrics. The application is itself an Oracle CEP application made up of adapters, streams, and a processor. The processor includes the following default EPL rule used to filter the metrics; this rule determines which event show up in the Diagnostics dashboard. The rule is as follows: SELECT FROM DSMonitorEvent RETAIN 1 EVENT WHERE metric 10000 You can change this rule if you want to customize the filtering of events. See Section 7.4, Changing the dataservices Application Event Filter Rule Using EPL for details.

1.3.2 Managing Oracle CEP Servers

Using Oracle CEP Visualizer, you can manage Oracle CEP server instances and the services they provide such as JMX, data sources, Jetty Web server, work managers, the persistent event store, event type repository, HTTP publish-subscribe server, and logs. For more information, see Chapter 9, Overview of Server and Domain Tasks .

1.3.3 Managing Security

Using Oracle CEP Visualizer, you can manage Oracle CEP server and application security including users, groups, and roles, SSL, and HTTP publish-subscribe server access. For more information, see Chapter 20, Overview of Security Tasks .

1.3.4 Updating Configuration Data

Although you can update much of the configuration of an Oracle CEP instance and its deployed applications, not all fields can be updated. The following rules determine what fields can be updated: ■ Information in the EPN assembly file is static and thus read-only. Examples of this type of information include the stages of the EPN and how they are wired together. ■ Information in the component configuration files can be modified, although not typically added to or deleted from; the next bullet lists the two exceptions. Examples of this type of information include the maximum size and threads of a stream.