Configuring Oracle Complex Event Processing

After you have created an Oracle Complex Event Processing (or Oracle CEP for short) domain along with at least a single server, you start a server instance so you can then deploy applications and begin running them. See Stopping and Starting the Server for details.

There are a variety of ways to configure a particular server instance, as follows:

Update the server configuration file, config.xml, manually.

See Configuring the Server by Manually Editing the config.xml File.

Use the wlevs.Admin utility to administer a Oracle CEP instance and to dynamically configure the EPL rules for the processors of a deployed application.

See wlevs.Admin Command-Line Reference.

Use standards-based interfaces that are fully compliant with the Java Management Extensions (JMX) specification to change the configuration of the domain and deployed applications.

See Configuring Applications and Servers Dynamically and the Javadoc for details about the Oracle CEP MBeans.

Configuring the Server by Manually Editing the config.xml File

The Oracle CEP server configuration file, config.xml, is located in the DOMAIN_DIR/servername/config directory, where DOMAIN_DIR refers to the main domain directory and servername refers to the name of the particular server instance in the domain. To change the configuration of an Oracle CEP server instance, you can update this file manually and add or remove server configuration elements.

Logging and debugging properties of the server. By default, the log security level is set to NOTICE.

See Configuring Logging and Debugging.

Jetty, an open-source, standards-based, full-featured Java Web Server.

See Configuring Jetty for Oracle Complex Event Processing.

JDBC data source, used to connect to a relational database.

See Configuring Access to a Relational Database.

JMX, required to use the wlevs.Admin utility.

See Configuring JMX for Oracle Complex Event Processing.

HTTP publish-subscribe server.

See Configuring the HTTP Publish-Subscribe Server.

The following sample config.xml, from the BEA_HOME/user_projects/domains/wlevs30_domain/defaultserver template domain, shows how to configure some of these services:

<?xml version="1.0" encoding="UTF-8"?>
<n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/server wlevs_server_config.xsd"
 xmlns:n1="http://www.bea.com/ns/wlevs/config/server" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <netio>
    <name>sslNetIo</name>
    <ssl-config-bean-name>sslConfig</ssl-config-bean-name>
    <port>4098</port>
  </netio>

  <work-manager>
    <name>JettyWorkManager</name>
    <min-threads-constraint>5</min-threads-constraint>
    <max-threads-constraint>10</max-threads-constraint>
  </work-manager>

  <jetty>
    <name>JettyServer</name>
    <network-io-name>NetIO</network-io-name>
    <work-manager-name>JettyWorkManager</work-manager-name>
    <secure-network-io-name>sslNetIo</secure-network-io-name>
  </jetty>

  <exported-jndi-context>
    <name>exportedJndi</name>
    <rmi-service-name>RMI</rmi-service-name>
  </exported-jndi-context>

  <jmx>
    <rmi-service-name>RMI</rmi-service-name>
    <rmi-jrmp-port>9999</rmi-jrmp-port>
    <jndi-service-name>JNDI</jndi-service-name>
    <rmi-registry-port>1099</rmi-registry-port>
  </jmx>

  <ssl>
    <name>sslConfig</name>
    <key-store>./ssl/dsidentity.jks</key-store>
    <key-store-pass>
        <password>changeit</password>
    </key-store-pass>
    <key-store-alias>ds</key-store-alias>
    <key-manager-algorithm>SunX509</key-manager-algorithm>
    <ssl-protocol>TLS</ssl-protocol>
    <enforce-fips>false</enforce-fips>
    <need-client-auth>false</need-client-auth>
  </ssl>

  <http-pubsub>
    <name>pubsub</name>
    <path>/pubsub</path>
    <pub-sub-bean>
      <server-config>
        <name>pubsubbean</name>
        <supported-transport>
          <types>
            <element>long-polling</element>
          </types>
        </supported-transport>
        <publish-without-connect-allowed>true</publish-without-connect-allowed>
      </server-config>
    <channels>
        <element>
          <channel-pattern>/evsmonitor</channel-pattern>
        </element>
        <element>
          <channel-pattern>/evsalert</channel-pattern>
        </element>
        <element>
          <channel-pattern>/evsdomainchange</channel-pattern>
        </element>
      </channels>
    </pub-sub-bean>
  </http-pubsub>

Administration and Configuration Guide

Configuring Oracle Complex Event Processing

Overview of Configuring Oracle Complex Event Processing

Configuring the Server by Manually Editing the config.xml File