This section contains information on the following subjects:
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.
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
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:
See Example of Configuring JMX for a sample of using each of the preceding configuration objects.
The following table describes the configuration information for the
<jmx> element in the
The WebLogic Event Server RMI service provides:
The following table shows the parameters of the
<rmi> configuration object that you use to export server-side objects to remote clients.
The name of the HTTP service used to register remote objects (such as Jetty, see Overview Of Jetty Support in WebLogic Event Server).
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:
Use the following configuration object to configure the
<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
The name of the RMI service that should be used to serve this JNDI context over the network. It must match an existing
config.xml snippet shows an example of configuring JMX; only relevant parts of the file are shown.