You are here

Runtime administration with a JMX client

By default, you can reconfigure Alfresco by shutting down the server, editing the relevant property in the configuration files, and then restarting the server. There are some support operations that can be performed on-demand at runtime without needing to restart the server.

The Java Management Extension (JMX) interface allows you to access Alfresco through a standard JMX console that supports JMX Remoting (JSR-160). This lets you:

  • Manage Alfresco subsystems
  • Change log levels
  • Enable or disable file servers (FTP/CIFS/NFS)
  • Set server read-only mode
  • Set server single-user mode
  • Set server maximum user limit - including ability to prevent further logins
  • Count user sessions/tickets
  • User session/ticket invalidation
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.

Example consoles include:

  • JConsole (supplied with Java SE 5.0 and higher)
  • MC4J
  • JManage

Some of these consoles also provide basic graphs and/or alerts for monitoring JMX-managed attributes.

Note: If you have a clustered environment in which each node in the cluster needs a unique configuration, then the configuration values for each node must be set via the properties file, and not via Share admin console or JMX.