HTTP Publish-Subscribe Server Management

Overview of Server and Domain Tasks 9-5 For more information, see: ■ Chapter 18, Managing Multi-Server Domains ■ Section 18.2, Managing Oracle Coherence ■ Section 3.4.5, Multi-Server Domains and Configuration History Management ■ Administrating Oracle CEP Multi-Server Domains in the Oracle Complex Event Processing Administrators Guide

9.9 Event Inspector Service Management

Using the Event Inspector service, you can: ■ View the events flowing out of any stage in the EPN ■ Inject events into any stage in the EPN You can use the Event Inspector service to test and debug Oracle CQL queries during development. For more information, see: ■ Chapter 15, Managing the Event Inspector Service ■ Chapter 4.4, Tracing and Injecting Events in the EPN ■ Testing Applications With the Event Inspector in the Oracle Complex Event Processing Developers Guide for Eclipse

9.10 Cache Management

A cache is a temporary storage area for events, created exclusively to improve the overall performance of your Oracle CEP application; it is not necessary for the application to function correctly. Oracle CEP applications can optionally publish or consume events to and from a cache to increase the availability of the events and increase the performance of their applications. A caching system refers to a configured instance of a caching implementation. A caching system defines a named set of configured caches as well as the configuration for remote communication if any of the caches are distributed across multiple machines. Oracle CEP supports the following caching systems: Note: Any changes to rules and Oracle high availability adapters are propagated to the other servers in the same group. That is, all rule and and Oracle high availability adapter configurations is automatically synchronized. Other configuration changes are not synchronized. For example, if you change recordplayback or JMS adapter configuration on one server in a multi-server domain, then these changes are not synchronized with the other servers in the same group. For more information, see: ■ Chapter 6, Managing Oracle CQL Rules ■ Chapter 7, Managing EPL Rules ■ Section 4.2, Viewing and Editing the Configuration of a Stage 9-6 Oracle Complex Event Processing Visualizer Users Guide ■ Oracle CEP local cache: a local, in-memory single-JVM cache. ■ Oracle Coherence: a JCache-compliant in-memory distributed data grid solution for clustered applications and application servers. It coordinates updates to the data using cluster-wide concurrency control, replicates data modifications across the cluster using the highest performing clustered protocol available, and delivers notifications of data modifications to any servers that request them. You take advantage of Oracle Coherence features using the standard Java collections API to access and modify data, and use the standard JavaBean event model to receive data change notifications. ■ Third-party caches: you can create a plug-in to allow Oracle CEP to work with other, third-party cache implementations. For more information, see: ■ Section 18.2, Managing Oracle Coherence ■ Configuring Oracle CEP Caching in the Oracle Complex Event Processing Developers Guide for Eclipse

9.11 Log Management

Oracle CEP Visualizer allows you to change the server-wide logging configuration, such as the severity of log messages you want the server to print out, the name of the log file, and so on. You can also view and modify the logging level of individual components and configure logging for new components.. For more information, see: ■ Chapter 19, Managing Oracle CEP Server Logs ■ Configuring Logging and Debugging for Oracle CEP in the Oracle Complex Event Processing Administrators Guide Note: Before you can use Oracle CEP with Oracle Coherence, you must obtain a valid Oracle Coherence license such as a license for Coherence Enterprise Edition, Coherence Grid Edition, or Oracle WebLogic Application Grid. For more information on Oracle Coherence, see http:www.oracle.comtechnologyproductscoherence index.html .