Configuring an Oracle CEP Local Cache as an Event Source

12-16 Oracle Complex Event Processing Developers Guide The caching system is responsible for creating the cache associated with a particular name and returning a reference to the cache. The resulting cache bean implements the java.util.Map interface. For more information, see Section 12.3.5, Configuring a Shared Oracle Coherence Cache . 4. Configure the caching system and its caches by updating the caching configuration file for the application. See Section 12.3.1, Configuring the Oracle Coherence Caching System and Caches. 5. Optionally, override the default cache configuration by updating the EPN assembly file with one or more additional cache element child elements. ■ Specify that a cache is an event sink by configuring it as a listener to another component in the event processing network. See Section 12.3.1, Configuring the Oracle Coherence Caching System and Caches. ■ Specify that a cache is an event source to which another component in the event processing network listens. See Section 12.3.2, Configuring an Oracle Coherence Cache as an Event Listener. ■ Configure either a wlevs:cache-loader or a wlevs:cache-store child element of the wlevs:cache element in the EPN assembly file, but not both. This is because Oracle Coherence combines the loader and store into a single component. You specify a cache loader when the backing store is read-only and a cache store when the backing store is read-write See Section 12.3.4, Configuring an Oracle Coherence Cache Loader or Store. 6. Access the Oracle Coherence cache: – Optionally reference the Oracle Coherence cache in a query statement. See: Section 12.5, Accessing a Cache From an Oracle CQL Statement Section 12.6, Accessing a Cache From an EPL Statement – Optionally configure and program a custom adapter, business POJO, or Oracle CQL or EPL user-defined function to access the Oracle Coherence cache. The configuration is done in the EPN assembly file and the programming is done in the Java file that implements the adapter, POJO, or user-defined function. See: Section 12.7, Accessing a Cache From an Adapter Section 12.8, Accessing a Cache From a Business POJO Section 12.9, Accessing a Cache From an Oracle CQL User-Defined Function Section 12.10, Accessing a Cache From an EPL User-Defined Function – Optionally, access the Oracle Coherence cache using JMX.