jManage Features

jManage 1.5 beta has the following features:

- Easy to use Web based interface, which allows jManage to be used from behind firewall.

- Web and command line based JMX console.

- Dashboard framework to build custom dashboards. Customized dashboards can be tailored to specific objectives. These dashboards are,
a. Live -> automatically refreshed to provide latest information.
b. Customized -> users can build a dashboard from scratch or customize an existing one to suit their needs.

- Connector framework for monitoring/managing non-JMX based environments. This framework can be used to expose necessary information on a non-JMX based environment as an application of MBeans. These applications can be registered, monitored and managed through jManage.

- MBean Info layering framework to provide additional information for MBeans. JDK 1.5 MBeans now get presented with MBean, attribute and operation descriptions

- Production level security.

- Command line interface - Useful for scripting and automation.

- Application Cluster Support - Change attribute values and perform operations across the cluster.

- Authentication and fine-grained Authorization to control access to different MBean attributes and operations.

- Support for various J2EE app servers, JDK1.5 and other JSR160 enabled applications.

- Custom Graphs.

- MBean attribute value monitoring.

- Email and console alerts based on MBean notifications and MBean attribute monitors.

- Support for Open MBean types: CompositeData and TabularData

- Basic SNMP support (SNMP 1.0)

- Framework to define custom DataFormat classes for custom objects.

- Support for external login modules (JAAS based with name and password callback)

- jManage can be accessed via Java APIs, which allows jManage to be used as a backend system and also allows applications to register themselves as they come online.

jManage is being built keeping security in mind, as one of the usages of jManage is in the production environment. Production environments usually have limited access and are managed by an operations team. jManage lets the operations team monitor the production environment (via browser or command line) and also allows the operations team to give controlled access to developers, QA and others. Operations team can create jManage users and assign roles to these users. Access to different features can be controlled by assigining permissions to various roles. Permission can be granted even at the level of MBean attributes or operations.