Accessing the Oracle CEP JMX Server

12-6 Oracle Complex Event Processing Administrators Guide

12.1.3.2 Oracle CEP Runtime MBeans

You can also gather monitoring information for each component in the EPN using runtime MBeans. Oracle CEP server defines the following metrics that you can monitor for each component: ■ Throughput—The number of events processed by the component. The parameters for this metric are: throughput time interval, aggregation time interval, the unit of time for the intervals. ■ Average Latency—The average amount of time it takes an event to pass through a component, or latency. Parameters: aggregation time interval, the unit of time for the interval. ■ Maximum Latency—The maximum amount of time it takes an event to pass through a component. Parameters: aggregation time interval, the unit of time for the interval. ■ Average Latency Threshold—Specifies whether the average latency of events between the start- and end-points of a component crosses a specified threshold. Parameters: aggregation time interval, threshold, the unit of time for the interval.

12.1.3.2.1 Runtime MBean Naming Runtime MBeans are named using the same pattern

as with configuration mbeans except for one extra property: Direction. This property has two valid values: OUTBOUND or INBOUND that refer to the point at which you want to gather the statistic OUTBOUND means that you want to gather throughput or latency as events flow out of the specified component; similarly INBOUND means you want to gather the monitoring information as events flow into a component. For example, the object name of the runtime MBean corresponding to a processor called myprocessor in the application myapplication, in which events will be monitored as they flow into the component, is as follows: com.bea.wlevs:Name=myprocessor,Type=EPLProcessor,Application=myapplication,Direction=INBOUND See Section 12.1.3.1.1, Configuration MBean Naming for details about configuration MBean naming.

12.1.3.3 Oracle CEP MBean Hierarchy

Figure 12–1 describes the Oracle CEP MBean tree. Figure 12–1 Oracle CEP MBean Tree Configuring JMX for Oracle CEP 12-7 All MBeans must be registered in an MBean server under an object name of type javax.management.ObjectName. Oracle CEP follows a convention in which object names for child MBeans contain part of its parent MBean object name. There are two main MBean roots: DomainMBean and DomainRuntimeMBean. The former includes configuration MBeans for the entire domain, the latter contains runtime information, such as statistics, and local services, such as Monitor, that are generally scoped to a single server instance. ApplicationMBean is a child of the DomainMBean instead of the ServerMBean. This is because an application is unique within a domain, and can span multiple servers. Figure 12–2 shows the main classes and relationships that make up the object model. Figure 12–2 Oracle CEP MBean Object Model Most MBeans are notification emitters that generate AttributeChangeNotifications. In other words, a JMX client can register to receive attribute change notifications regarding changes to application state, insertion and removal of applications at the domain, channel size and thread changes, insertion and removal of rules, and so on.

12.2 Configuring JMX

You configure the Oracle CEP JMX service using the following elements in the config.xml file that describes your Oracle CEP domain: ■ jmx: See Section 12.2.1, jmx Configuration Object for details. ■ rmi: See Section 12.2.2, rmi Configuration Object for details. ■ jndi-context: See Section 12.2.3, jndi-context Configuration Object for details. ■ exported-jndi-context: See Section 12.2.4, exported-jndi-context Configuration Object for details For information on security configuration tasks that affect JMX, see Section 10.8.2, Configuring JMX Security .