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.