You are here

Activating the Oracle JMX agent and local JMX connectivity

When using Tomcat and a Oracle JVM together for monitoring, you can configure Alfresco and Tomcat to share the JVM's own platform MBean server. The pre-registered MXBeans give a detailed view of the JVM's health, usage and throughput; in areas including class loading, hot spot compilation, garbage collection, and thread activity.
Oracle's MBean server also provides a convenient local connection method, allowing the Alfresco process to be automatically 'discovered' by a JMX client such as JConsole without manual configuration of connection details.
The Oracle JMX agent can also be activated in remote mode (where a connection is made through an RMI lookup). However, since Alfresco is always preconfigured to allow a secure remote JMX connection on any JVM, it is most likely that you will choose to activate the Oracle JMX agent in local mode. This means the platform MBean Server is shared by Alfresco and still be available for remote connections through the RMI connector.
Restrict JMX RMI connections to an internal administration group, due to security vulnerabilities. JMX/RMI deserializes data from a client before authentication, which means that password protection does not provide adequate security.
  • To activate the Oracle JMX agent in local mode, ensure that the following system property is set:

    For example, in your Tomcat startup script, you could use the following line:

    export JAVA_OPTS="${JAVA_OPTS}"

  • Refer to the Oracle documentation for more information on all the possible configuration options.

Sending feedback to the Alfresco documentation team

You don't appear to have JavaScript enabled in your browser. With JavaScript enabled, you can provide feedback to us using our simple form. Here are some instructions on how to enable JavaScript in your web browser.