Java Management Extensions Guide

Java Management Extensions are a technology for remote management and monitoring of servers.

When the 1060 Netkernel is deployed with the optional 1060jmx.jar and started using the supplied scripts the kernel implements a JMX Service Interface. This allows generic management tools to connect.

1060jmx.jar also contains a specialised JMX client for connecting to 1060 Netkernel instances. It provides an interface for remote control and monitoring.

JMX support is provided by MX4J.

JMX Configuration

The JMX connection is configured with the final class JMXEnv:

package com.ten60.netkernel.jmx;

/**Default settings for the JMX session.  Assumes a local instance of the dexter server
 * with a local client.  Also includes constants for MX4J and JNDI MBean names.
 * @author  pjr
 */
public final class JMXEnv {
    
    //Server Settings
    public static final String JMX_KERNEL_JNDI_NAME="ten60:kernel=container";
    public static final String JMX_RMI_CONNECTION_JNDI_NAME="jrmp";
    public static final int JMX_DEFAULT_PORT=10600;
    public static final int RMI_DEFAULT_PORT=1099;
    public static final String RMI_DEFAULT_HOST="localhost";
    
    //Logger Settings
    public static final String JMX_LOGGER_JNDI_NAME="ten60:kernel=logger";
    public static final String JMX_LOGGER_TOKEN="ten60.kernel.log";
    
    //JMX Specific
    public static final String JMX_INITIAL_CONTEXT_FACTORY="com.sun.jndi.rmi.registry.RegistryContextFactory";
    
    //MX4J Specific
    public static final String MX4J_NAMING_SERVICE="Naming:type=rmiregistry";
    public static final String MX4J_NAMING_SERVICE_CLASS="mx4j.tools.naming.NamingService";
    public static final String MX4J_ADAPTOR_JRMP="Adaptor:protocol=JRMP";
    public static final String MX4J_ADAPTOR_JRMP_CLASS="mx4j.adaptor.rmi.jrmp.JRMPAdaptor";
    public static final String MX4J_ADAPTOR_HTTP="Adaptor:protocol=HttpAdaptor";
}

If you wish to reconfigure the JMX settings you only need to change the ports and hostname. The important items are:

• RMI_DEFAULT_HOST is the host that is running the server.
• JMX_DEFAULT_PORT is the TCP/IP port that the JNDI service is running on.
• RMI_DEFAULT_PORT is the TCP/IP port that RMI connections to the server are made on.

The JMXServer and JMXConsole use JMXEnv to ensure they are both configured the same. You may edit and rebuild the JMXEnv to change the default ports to suit your system.

Console

The Management Console provides a suite of functionality for controlling and monitoring instances of 1060 Netkernel. The main panel contains two tabs, the first [Log] tab contains the list of logging entries. The second [System Status] tab contains a pane that can show one of a number of system reports.

The menu actions available are:

• Connection
  • New... create settings to connect to a new server.
  • Open open previously saved settings.
  • Save save modified settings.
  • Save As... save modified settings as another name.
  • Edit... edit current settings.
  • Open Last Connection on Startup when checked the console will automatically open connections to the current settings at startup. If connections are lost it will reconnect automatically too.
  • Exit close the console prompting to save if necessary.
• View
  • Logging Level > this sub-menu contains a set of checkboxes to enable or disable the various logging levels. The default values are specified in the system config.
    • Fine enable/disable logging
    • Info enable/disable logging
    • Warning enable/disable logging
    • Severe enable/disable logging
  • Clear Log clears the [Log] tab.
• Tools
  • StartStarts a currently stopped server.
  • RestartStops then immediately restarts server.
  • StopStops the server.
  • Advanced >
    • Kill Server... Permanently stops the server by ending the process.
• Help
  • About... about box!

System Status Reports

The console can show simplified versions the following key status reports:

• Transaction Summary
• Installed Applications
• Cache Snapshot