Monitoring and management

You can monitor and manage Liberator at run time in several ways:

  • Through JMX monitoring, using a JMX-enabled client, such as the Caplin Management Console.

  • By directly viewing or extracting the contents of log files (see Logging).

  • Through the Liberator status web page and Liberator Explorer.

    The Liberator status web page and Liberator Explorer are only intended for development environments, as they aren’t secure enough to use in production systems. A JMX monitoring client application can be designed so that it logs in to the Liberator securely through Caplin KeyMaster, and this would make such a monitoring client suitable for production systems.
Contents:

JMX Monitoring

Liberator is supplied with a built-in Liberator JMX Config blade that you can activate to make it send status data across to JMX clients, such as to the Caplin Management Console. The standard DataSource monitored items are available (see DataSource monitoring and management), plus the following Liberator specific items:

  • System data: aggregated information about the total number of sessions, objects subscribed to, and data throughput, plus information about any configured clusters.

  • User data: information about all connected users and their sessions, including latency and object subscription details. You can also eject and revalidate users, and cancel subscriptions.

  • Object data: details of all objects in the system: their type, stale status, update times, subscription counts, and which sessions are viewing each object.

  • Licence status and licence related messages.

See also: