Understanding Oracle CEP Servers and Domains

1-2 Oracle Complex Event Processing Administrators Guide ■ Standalone-server domain—A domain that contains a single server. This is the type of domain created by default by the Configuration Wizard and is the starting point for a multi-server domain. For more information, see Chapter 3, Administrating Oracle CEP Standalone-Server Domains . ■ Multi-server domain—A domain that contains two or more servers that share the same multicast address and port and share a security provider. Multi-server domains enable high availability for Oracle CEP applications. When you deploy an application to a multi-server domain, the application is replicated to each server in the domain. The servers in a multi-server domain can be located on the same computer or on separate computers; what ties the servers together in a multi-server domain is that they have the same multicast address and port and belong to the same domain, all of which are configured in the servers config.xml file. For more information, see: – Chapter 6, Administrating Multi-Server Domains With Oracle Coherence – Chapter 7, Administrating Multi-Server Domains With Oracle CEP Native Clustering

1.2 Understanding Oracle CEP Server Lifecycle

Figure 1–1 shows a state diagram for the Oracle CEP server lifecycle. In this diagram, the state names STARTING, RUNNING, and SHUTTING_DOWN correspond to the ServerRuntimeMBean method getState return values. These states are specific to Oracle CEP; they are not OSGi bundle states. Figure 1–1 Oracle CEP Server Lifecycle State Diagram This section describes the lifecycle of an application deployed to Oracle CEP and the sequence of com.bea.wlevs.ede.api API callbacks. The lifecycle description is broken down into actions that a user performs, including: Note: For information on Oracle CEP application lifecycle, see Oracle CEP Application Lifecycle in the Oracle Complex Event Processing Developers Guide for Eclipse. Overview of Oracle CEP Server Administration 1-3 ■ Section 1.2.1, User Action: Start Oracle CEP Server ■ Section 1.2.2, User Action: Stop Oracle CEP Server This information explains how Oracle CEP manages an applications lifecycle so that you can better use the lifecycle APIs in your application. For a description of these APIs such as RunnableBean and SuspendableBean, see: ■ Oracle CEP APIs in the Oracle Complex Event Processing Developers Guide for Eclipse ■ Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing

1.2.1 User Action: Start Oracle CEP Server

After you start the Oracle CEP server, it performs the following actions: 1. Starts core engine bundles. 2. Starts Oracle CEP bundles. 3. Registers MBeans. 4. Oracle CEP server state is now STARTING. 5. Starts application bundles. 6. Oracle CEP server state is now RUNNING.

1.2.2 User Action: Stop Oracle CEP Server

After you shutdown the Oracle CEP server, it performs the following actions: 1. Oracle CEP server state is SHUTTING_DOWN. 2. Unregister ServerRuntimeMBean. Oracle CEP server ceases to have a state. 3. Shuts down Oracle CEP bundles. 4. Shuts down application bundles. 5. Shuts down core engine bundles.

1.3 Understanding Oracle CEP Server Configuration

Oracle CEP server configuration falls into two categories: ■ configuring a server ■ configuring the applications you deploy to a server For each configuration category, you can perform the configuration task: ■ Statically: by editing an XML file manually. Using this approach, you must restart the server or redeploy the application after making a change. ■ Dynamically: by manipulating management beans MBeans using Oracle CEP Visualizer, wlevs.Admin command-line utility, or programmatically using JMX, Using this approach, you do not have to restart the server or redeploy the application after making a change You configure the server statically by: