This section contains information on the following subjects:
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:
config.xml
, manually. You See Configuring the Server by Manually Editing the config.xml File.
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.
See Managing Applications, Servers, and Domains Using MBeans and the Javadoc for details about the Oracle CEP MBeans.
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 update this file
You can configure the following server objects and features using the config.xml
file; the referenced sections describe the exact elements you must add or update:
See Configuring and Using Oracle CEP Multi-Server Domains.
See Configuring Jetty for Oracle Complex Event Processing.
See Configuring Access to a Relational Database.
wlevs.Admin
utility.See Configuring JMX for Oracle Complex Event Processing.
See Configuring the HTTP Publish-Subscribe Server.
NOTICE
.
The following sample config.xml
, from the ORACLE_CEP_HOME
/user_projects/domains/wlevs30_domain/defaultserver
template domain, shows how to configure some of these services:
<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy v2007 sp2 (http://www.altova.com)-->
<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>NetIO</name>
<port>9002</port>
</netio>
<netio>
<name>sslNetIo</name>
<ssl-config-bean-name>sslConfig</ssl-config-bean-name>
<port>9003</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>
<rmi>
<name>RMI</name>
<http-service-name>JettyServer</http-service-name>
</rmi>
<jndi-context>
<name>JNDI</name>
</jndi-context>
<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>9004</rmi-registry-port>
</jmx>
<ssl>
<name>sslConfig</name>
<key-store>./ssl/evsidentity.jks</key-store>
<key-store-pass>
<password>{Salted-3DES}j4XEtuXmmvEl4M/NInwq0A==</password>
</key-store-pass>
<key-store-alias>evsidentity</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>/pubsub</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>
<cluster>
<server-name>productionServer</server-name>
</cluster>
<domain>
<name>wlevs30_domain</name>
</domain>
WARNING: | If you update the config.xml file manually to change the configuration of Oracle CEP, you must restart the server for the change to take effect. |