WebLogic Event Server Administration and Configuration Guide

Configuring JMX for WebLogic Event Server

This section contains information on the following subjects:

Overview of JMX Support in WebLogic Event Server

WebLogic Event Server provides standards-based interfaces that are fully compliant with the Java Management Extensions (JMX) specification. Software vendors can use these interfaces to monitor WebLogic Server MBeans, to change the configuration of a WebLogic Server domain, and to and monitor the distribution (activation) of those changes to all server instances in the domain.

The wlevs.Admin utility uses JMX to connect to a server so you can manipulate its MBean instances, in particular to view, add, and update the EPL rules associated with the processors of a particular WebLogic Event Server application.

However, to use the wlevs.Admin utility, and the JMX interfaces in general, you must configure WebLogic Event Server with the JMX configuration information in the config.xml file.

Configuring JMX

You use the following configuration objects to configure an instance of the Jetty HTTP server in the config.xml file that describes your WebLogic Event Server domain:

<jmx>: See jmx Configuration Object for details.
<rmi>: See rmi Configuration Object for details.
<jndi-context>: See jndi-context Configuration Object for details.
<exported-jndi-context>: See exported-jndi-context Configuration Object for details

See Example of Configuring JMX for a sample of using each of the preceding configuration objects.

jmx Configuration Object

The following table describes the configuration information for the <jmx> element in the config.xml file.

Table 8-1 Configuration Parameters for <jmx>
Parameter	Type	Description
`rmi-service-name`	`String`	The name of the RMI service with which the jmx server will register to receive calls.
`rmi-jrmp-port`	`int`	The port on which to listen for RMI JRMP JMX requests
`jndi-service-name`	String	The name of the JNDI service to which the jmx server will bind its object.
`rmi-registry-port`	int	The port on which to start the RMIRegistry

rmi Configuration Object

The WebLogic Event Server RMI service provides:

Ability to register a POJO interface in a server for remote method invocation from a client.
Ability to register for any context propagation from the client to the server on a remote method invocation, intercept, and act on this propagated context in the server.

The following table shows the parameters of the <rmi> configuration object that you use to export server-side objects to remote clients.

Table 8-2 Configuration Parameters for <rmi>
Parameter	Type	Description
`heartbeat-period`	`int`	The number of failed heartbeat attempts before triggering disconnect notifications to all registered listeners.
`http-service-name`	`String`	The name of the HTTP service used to register remote objects (such as Jetty, see Overview Of Jetty Support in WebLogic Event Server).
`heartbeat-interval`	`int`	The amount of time, in milliseconds, between heartbeats. Once the number of unsuccessful heartbeat attempts has reached the value specified by the `HeartbeatPeriod` parameter, all registered `DisconnectListener` instances are notified.
name	String	The name of this configuration object.

jndi-context Configuration Object

The JNDI Factory Manager is responsible for supporting JNDI in an OSGi environment. It allows JNDI providers to be supplied as OSGi bundles, and for code running inside OSGi bundles to have full access to the JNDI environment.

The Factory Manager consists of two components:

An OSGi bundle, which provides the OSGi-specific factory management code, to look up JNDI objects using the appropriate OSGi classloader.
JNDI "glue code," internal to WebLogic Event Server, that initializes the JNDI environment to support the factory manager bundle.

Use the following configuration object to configure the <jndi-context> configuration object.

Table 8-3 Configuration Parameters for <jndi-context>
Parameter	Type	Description
`default-provider`	`boolean`	If `true`, the default WebLogic Event Server JNDI provider is used. Default value is `true`.
name	String	The name of this configuration object.

exported-jndi-context Configuration Object

Note:

Requires a configured jndi-context Configuration Object.

Use this configuration object to export a remote JNDI service to a client using RMI. A JNDI context is registered with the RMI service to provide remote access to clients that pass a "provider URL" parameter in their InitialContext object.

Table 8-4 Configuration Parameters for <exported-jndi-context>
Parameter	Type	Description
rmi-service-name	String	The name of the RMI service that should be used to serve this JNDI context over the network. It must match an existing `<rmi>` configuration object. See rmi Configuration Object.
name	String	The name of this configuration object. The value of this element must be different from the value of the `<name>` child element of `<jndi-context>` in the same `config.xml` file.

Example of Configuring JMX

The following config.xml snippet shows an example of configuring JMX; only relevant parts of the file are shown.

Listing 8-1

<config>

  <netio>
    <name>JettyNetio</name>
    <port>12345</port>
  </netio>

  <work-manager>
    <name>WM</name>
    <fairshare>5</fairshare>
    <min-threads-constraint>1</min-threads-constraint>
    <max-threads-constraint>4</max-threads-constraint>
  </work-manager>

  <jetty>
    <name>TestJetty</name>
    <work-manager-name>WM</work-manager-name>
    <network-io-name>JettyNetio</network-io-name>
  </jetty>

  <rmi>
    <name>RMI</name>
    <http-service-name>TestJetty</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>
    <jndi-service-name>JNDI</jndi-service-name>
    <rmi-service-name>RMI</rmi-service-name>
    <rmi-registry-port>10099</rmi-registry-port>
    <rmi-jrmp-port>9999</rmi-jrmp-port>
  </jmx>

</config>