This section describes the typical application tasks you can perform with Oracle CEP Visualizer, including:
The Oracle CEP Event Processing Network (EPN) represents the interconnections between the various Oracle CEP components of an Oracle CEP application. Using Oracle CEP Visualizer, you can manage the EPN, including viewing and changing the configuration of a stage, recording and playing back events, and monitoring the throughput and latency of a stage or path. Right-click a stage to select common stage-related functions from a convenient context menu.
For more information, see:
"Components of the Oracle CEP Event Processing Network" in the Oracle Complex Event Processing Developer's Guide for Eclipse
You can manage the full application lifecycle including uploading an application, deploying it, suspending and resuming the application, and undeploying the application.
For more information, see:
"Oracle CEP Application Lifecycle" in the Oracle Complex Event Processing Developer's Guide for Eclipse
You can create, replace, and delete the rules in the Oracle CQL and EPL processors of Oracle CEP applications you develop and deploy as well as applications that Oracle CEP server deploys.
It is important to note that Oracle CEP Visualizer will update your configuration file on the server with any queries that you create. However, you will not see this take effect in your application from within the Oracle CEP IDE for Eclipse, in order to make the change there you will need to copy and paste the query from Oracle CEP Visualizer into your application.
For more information, see:
Using the Oracle CEP Visualizer, you can manage the configuration changes you make to Oracle CEP components. You can review change history and you can undo (roll back) changes to an earlier version. You can perform these operations on a given resource or application in both standalone-server and multi-server domains.
Alternatively, you can manage configuration history using the wlevs.Admin command-line tool.
For more information, see:
Section 3.4.1, "Enabling and Disabling Configuration History Management"
Section 3.4.3, "Application Configuration History Management"
Section 3.4.4, "Application Lifecycle and Configuration History Management"
Section 3.4.5, "Multi-Server Domains and Configuration History Management"
"Commands for Managing Configuration History" in the Oracle Complex Event Processing Administrator's Guide
By default, Oracle CEP provides resource and application configuration history management.
Optionally, you can disable this feature by editing the CEP_SERVER/startwlevs.cmd/sh file and adding the com.oracle.ocep.config.version.enabled system property to the last line (in practice, the command should be on one line):
"$JAVA_HOME/bin/java" $JVM_ARGS $DEBUG_ARGS -Dwlevs.home="$USER_INSTALL_DIR"
-Dcom.oracle.ocep.config.version.enabled=false -Dbea.home="$BEA_HOME"
-jar "${USER_INSTALL_DIR}/bin/wlevs.jar" $ARGS
If you disable this feature, Oracle CEP cannot propagate rules amongst the Oracle CEP servers in a multi-server domain. In this case, to propagate rule changes, you must manually update the rules in all the servers of a multi-server domain.
If you disable this feature and then wish to re-enable it, you must do so as follows:
Undeploy your Oracle CEP application.
Shut down the Oracle CEP server.
Edit the startwlevs.cmd/sh file to either remove the -Dcom.oracle.ocep.config.version.enabled system property or set it to true.
Start the Oracle CEP server.
Deploy your Oracle CEP application.
Failure to do so may cause rule propagation to fail in a multi-server domain and may prevent the Oracle CEP Visualizer from maintaining a consistent view of the Oracle CEP servers in a multi-server domain.
You can manage the configuration history of the following Oracle CEP resources:
Oracle CEP high availability adapters
Oracle CQL rules
For more information, see Section 8.1, "Managing Resource Configuration History".
You can manage the configuration history for a given application. This allows you to see a summary of all the configuration changes made to all resources of a given application.
For more information, see Section 8.2, "Managing Application Configuration History".
When you deploy an application, the Oracle CEP server creates a new configuration history for the application.
When you update an application, the Oracle CEP server erases the existing configuration history and creates a new configuration history for the application.
When you uninstall an application, the Oracle CEP server erases the configuration history for the application.
For more information, see Section 3.2, "Application Lifecycle Management".
When you deploy an application to a multi-server domain, consider the following configuration history management restrictions:
For more information, see Section 9.8, "Multi-Server Domain Management".
When an Oracle CEP server joins (or rejoins) a multi-server domain, the server's existing configuration history records (if any) are deleted and replaced with the current multi-server domain configuration history when the Oracle CEP server has synchronized with the primary.
Oracle CEP does not support simultaneous configuration updates from more than one Oracle CEP server in a multi-server domain.
Make configuration changes from one Oracle CEP Visualizer instance on one node in the multi-server domain.