12-2 Oracle Complex Event Processing Administrators Guide
You can dynamically configure each component in the EPN using managed beans, or MBeans. Typical configuration tasks include adding and removing Oracle CQL or EPL
rules, changing channel max size, subscribing to notifications, and executing operations.
You manipulate the MBeans using any of the following:
■
Oracle CEP Visualizer: the Oracle CEP graphical administration console. For more information, see Oracle Complex Event Processing Visualizer Users Guide.
■
wlevs.Admin: the Oracle CEP command-line administration utility. For more information, see
Appendix A, wlevs.Admin Command-Line Reference .
■
Deployer: the Oracle CEP command-line deployment utility. For more information, see
Appendix B, Deployer Command-Line Reference .
■
jconsole: the JMX console that the Java JDK provides.
■
Your own Java code using standard JMX APIs: http:java.sun.comjavasetechnologiescoremntr-mgmtjavama
nagement.
This section describes:
■
Section 12.1.2.1, Accessing the Oracle CEP JMX Server
■
Section 12.1.2.2, Accessing Configuration MBeans
■
Section 12.1.2.3, Accessing Oracle CEP Runtime MBeans For more information, see:
■
Section 12.1.3, Understanding Oracle CEP MBeans
■
Section 12.3, Managing With JMX
12.1.2.1 Accessing the Oracle CEP JMX Server
To access Oracle CEP MBeans, you must first connect to the Oracle CEP JMX server. Oracle CEP does not support the JRMP protocol. Instead, JMX clients must use the
more secure MSA protocol for both local and remote access to the Oracle CEP JMX server.
When you connect to the Oracle CEP JMX server that is running on localhost or on a remote host, you must copy the following Oracle CEP server JAR files to the client
classpath of the host from which you want to connect to the Oracle CEP server:
■
ORACLE_CEP_HOME \modules\com.bea.core.jmx_8.0.0.0.jar
■
ORACLE_CEP_HOME \modules\com.bea.core.rmi_7.0.0.0.jar
■
ORACLE_CEP_HOME \modules\com.bea.core.jndi.context_8.0.0.0.jar
■
ORACLE_CEP_HOME \modules\com.bea.core.logging_1.8.0.0.jar
■
ORACLE_CEP_HOME \modules\com.bea.core.bootbundle_11.0.0.0.jar
Note: Components are also sometimes referred to as stages, in
particular in the management Javadocs. However, for consistency with the rest of the Oracle CEP documentation, this section uses the
term components.
Configuring JMX for Oracle CEP 12-3
Where ORACLE_CEP_HOME refers to the directory in which you installed Oracle CEP such as d:\oracle_home.
You must launch your JMX client such as jconsole using the following command line options and classpath split for readability; in practice, the command should be on
one line:
prompt java -Djmx.remote.protocol.provider.pkgs=com.bea.core.jmx.remote.provider -Dmx4j.remote.resolver.pkgs=com.bea.core.jmx.remote.resolver
-Djava.naming.factory.initial=com.bea.core.jndi.context.ContextFactory -classpath JAVA_HOME\lib\jconsole.jar;MODULE_HOME\modules\com.bea.core.jmx_
8.0.0.0.jar; MODULE_HOME
\modules\com.bea.core.rmi_7.0.0.0.jar;MODULE_ HOME
\modules\com.bea.core.jndi.context_7.0.0.0.jar; MODULE_HOME
\modules\com.bea.core.logging_1.5.0.0.jar;MODULE_ HOME
\modules\com.bea.core.bootbundle_8.0.0.0.jar sun.tools.jconsole.JConsole
Where MODULE_HOME is the directory you copied the
Oracle CEP
server JAR files to. To connect to the Oracle CEP JMX server, you must use the JMX URL
service:jmx:msarmi:HOST-NAME:portjndijmxconnector so that you are always using the MSA connector where HOST-NAME is either localhost or the
name of the remote host and port is the Oracle CEP server JNDI port .
For more information, see:
■
Section 12.3.1, How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client
■
Section 12.3.6, How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Disabled
12.1.2.2 Accessing Configuration MBeans
You can also perform some configuration and application life cycle management of the server, domain, and deployed applications using MBeans, although this section
predominantly describes configuring individual application components. However, because server, domain, and application configuration is also done using MBeans,
much of the information in this section is applicable.
Each component in a deployed application adapter, channel, or processor has a configuration MBean that manages the underlying configuration of the component.
Each type of component has its own set of manageable artifacts. For example, you can dynamically configure the maximum number of threads for a channel or the Oracle
CQL rules associated with a processor.
12.1.2.3 Accessing Oracle CEP Runtime MBeans
You can also gather monitoring information for each component in the EPN using runtime MBeans. Monitoring information includes throughput number of events
passing through a component and latency how long it takes an event to pass through a component.
12.1.3 Understanding Oracle CEP MBeans
Oracle CEP exposes the following types of MBeans:
■
Configuration MBeans —Contain information about the configuration of
components in an EPN, a deployed Oracle CEP application, the server and domain configurations. These MBeans have a fixed management interface and represent
