Thursday, November 16, 2006

jManage 2.0 beta is now available

We are very excited to announce the availability of jManage 2.0 beta.

We have decided to change the version number from 1.5 to 2.0 to better reflect the level of maturity and stability in this release, as well as many new features which transform jManage from a JMX console to a management platform.

2.0 beta contains the following major features:
- Improved dashboard framework, with two Java 5 dashboards.
- Connector framework for non-JMX applications, with a sample Oracle database connector.
- Application downtime tracking with ability to setup alerts when an application goes down.
- WebLogic 9.x support is now part of this release. This was earlier provided as a patch.
- UI Improvements.

There is documentation available on dashboards and connectors at

A number of bugs found in 1.5 beta, have been fixed in this release. Please see the release notes for more info:

You can download this release from:

We will now be working towards the next 2.0 release with:
a) Historical graphing.
b) Dashboards for major J2EE application servers.
c) More Bug fixes.

Best Regards,

The jManage Team

Wednesday, August 02, 2006

jManage 1.5 beta is now available

This is a beta release of the awaited 1.5 version that introduces,

1. 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 personalize an existing one to suit their needs.

This also comes with a default Java5 dashboard and we will be adding more dashboards in the future releases.

2. 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.

This release also comes with a primitive Oracle connector

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

Please use the following installation guide:

Saturday, May 20, 2006

jManage 1.0 Documentation

jManage Documentation is now being maintained on the following wiki:

You can also make changes to this documentation after you login.

Thursday, April 27, 2006

Hibernate Stats with jManage

You can configure Hibernate to expose statistics of a Hibernate SessionFactory via JMX. Please see the hibernate documentation for more information:

Before you can look at Hibernate stats via jManage, you need to copy hibernate-3.1.jar to JMANAGE_HOME/lib folder, and restart jManage.

Following is an example of getting Second Level Cache statistics for a cached entity.

Friday, March 24, 2006

Weblogic 9.x support in jManage 1.0.4

The following patch file adds Weblogic 9.x support to jManage 1.0.4:

This file is available as part of the jManage 1.0.4 release:

After applying the patch, you will have to copy WL_HOME\server\lib\weblogic.jar to JMANAGE_HOME\modules\weblogic9.

Saturday, March 18, 2006

SNMP Support in jManage 1.0.4

jManage 1.0.4 supports SNMP version 1 with "public" community string. As jManage tries to map the SNMP information to MBeans, it uses file to map SNMP OIDs to MBean attribute names.

Currently, file contains Solaris OIDs. If you add more OIDs here, please share them with the community.

SNMP support is primitive at this point, and we are looking to get some feedback from you. Please let us know if you use jManage to connect to a SNMP device, and what improvements you are looking for.

jManage is not a replacement for a Network Management System like OpenNMS, but it tries to provide read-only view of some interesting attribute values.

Friday, March 17, 2006

jManage 1.0.4 released

jManage 1.0.4 is a maintenance release in the 1.0 series, with some bug fixes and improved support for SNMP.

Currently jManage only supports SNMP version 1 with "public" community name. The SNMP OIDs are configured in Currently, this file only contains Solaris OIDs. You can add more OIDs to this file.

You can download jManage 1.0.4 at:


Bugs fixed:

1392503 - SNMP port entered through UI is not being used
1445291 - .sh files do not work with cygwin
1431102 - Allow other users with admin access to unlock "admin" user
1445126 - jManage fails with quoted object names
1452904 - Rename "weblogic61" to "weblogic" in application-type-config

Feature Requests:

1419292 - Allow users to add custom classpath to jmanage classpath
1452896 - SNMP: Support for Solaris OIDs

Friday, March 10, 2006

Nominate jManage for 2006 Community Choice Awards

SourceForge is collecting nominations for 2006 Community Choice Awards. If you like jManage,
please take a second to nominate jManage:

Nominations must be entered by March 15th.

Tuesday, March 07, 2006

jManage Alerts with JBoss

Before setting up Alerts in jManage for JBoss, you need to copy "jmanage-jboss.jar" from <jmanage-home>/modules/jboss to <jboss-server-config>/lib.

For example, if you are running the "default" JBoss server configuration, copy this jar to: <jboss-home>/server/default/lib.

You will need to restart JBoss, after copying the file.

Also note that jManage comes with JBoss 3.2.4 jars. If you are connecting to JBoss 4.0, you need to copy the 4.0 jars to <jmanage-home>/modules/jboss directory.

Friday, January 20, 2006

jManage configuration files you should know about

jManage configuration files can be found under the config directory. You can modify some of these files to customize jManage for your needs.

Following is a list of important jManage configuration files and their usages:

This files contains the configured applications, alerts, graphs, etc.
You will normaly not edit this file by hand.

This file contains the key encrypted using the admin password.

Contains jManage users.

Edit this file to add more roles.
Contains access control list. See this doc for more information.

The Jetty configuration file. You will need to edit this file if you want to change the default port for jManage. See Jetty documentation for more information.
General jManage configurations.
jManage uses JDK logging system. This the JDK logging configuration file.
Data format configurations for web interface.
Data format configurations for command-line interface.

JAAS authentication configuration file.
User to role mapping, if you have configured a different authentication module in jmanage-auth.conf.

Monday, January 16, 2006

An introduction to jManage 1.0

There is a good article on JavaWorld which introduces readers to the features of jManage JMX client using J2SE 5.0 MBeans as examples. You can read the article here.

Wednesday, January 11, 2006

Connecting to a "Cluster" using jManage

Zarar Siddiqi has written an article titled "Using JMX and J2SE 5.0 to Securely Manage Web Applications". This article includes the cluster
management feature of jmanage:

Sunday, January 08, 2006

Adding Custom Login Modules to jManage

Use case
I already have a set of users categorized under various groups. How can I configure jManage to use this (external) user base for authentication and authorization?

Prepare jManage to use a custom login module by configuring the login module class in jmanage-auth.conf file. Custom login module should implement and login() method, where the actual authentication logic goes, should use NameCallback and PasswordCallback of package to retrieve the wrapped username and password respectively. A sample LoginModule for reference.

1. jManage comes with two pre-configured groups, Administrator and User. More such groups can be added by configuring the same in jmanage-user-roles.xml file.

2. In order to make jManage aware of various user to group relationships, the same should be configured in file. This file stores the necessary user-groups mapping for external users and it comes with a default configuration where in all users are mapped to Administrator group. One should edit this file to make appropriate changes.

User X belongs to groups A and B, then the relationship should be configured in file as X=A,B.