Index Changes
This is version 1. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]
ESB Console Home

How do I enable Common Management and Monitoring support for a Glassfish v3 with Fuji instance

To enable Common Management and Monitoring support for a Glassfish v3 with Fuji instance, you need the following:

  1. Install the fuji-management-hk2 archive that enables the management backend in your Fuji runtime - can be built from esb-console/fuji-management-hk2
  2. Install the FujiEventManagementWebApp archive in your Fuji runtime - A backend web application implementation (eventmanagement-webapp) that pushes alerts to subscribed clients through reverse-ajax - can be built from esb-console/extended/alerts/eventmanagement-webapp.

You would then need to use the Common Management and Monitoring API and write client code to access the functionality.

  • You will need jbi-admin-common.jar in your client side classpath
  • Include the archive that enables the extended core management client side API in your client side classpath - can be built from esb-console/extended/api/ - and include it in your client classpath.

The previously mentioned jars are mandatory for any client side code. In addition, you'd also want to include other Common Management and Monitoring API client side jars. For e.g., to receive alerts, you need to include the archive in your client side classpath - that enables the alert reception, and management client side API - can be built from esb-console/extended/api/ - in you client side classpath. There are a number of APIs available under esb-console/extended/api/. Have a peek and use the ones you need while writing your client code.


It is always better to Checkout and Build from scratch. However, if you want to try out the Management and Monitoring capabilities without having to build it from scratch, I will infrequently upload a jar file at my convenience that you can download from here fuji-standalone-manmon.jar(info) that you can deploy to your standalone Fuji instance and test according to instructions mentioned below:


Step 1: - Download and extract the pre-built jars

Extract the jar into a directory of your choice:
jar -xvf fuji-standalone-manmon.jar
The contents are expanded to a core folder which has an backend folder that contains the fuji-management archive, and the FujiEventManagementWebApp archive. There is also a client folder that contains the archives that have to be included in your client classpath for you to exercise the management capabilities remotely, viz., jbi-admin-common.jar, and the archive.
 Directory of E:\core

09/17/2009  07:46 AM    <DIR>          .
09/17/2009  07:46 AM    <DIR>          ..
09/17/2009  07:39 AM    <DIR>          backend
09/17/2009  07:41 AM    <DIR>          client
               0 File(s)              0 bytes

 Directory of E:\core\backend

09/17/2009  07:39 AM    <DIR>          .
09/17/2009  07:39 AM    <DIR>          ..
09/06/2009  07:28 PM         1,346,171 fuji-management-1.0-SNAPSHOT.jar
08/30/2009  03:19 PM           259,023 FujiEventManagementWebApp-1.0-SNAPSHOT.jar
               2 File(s)      1,605,194 bytes

 Directory of E:\core\client

09/17/2009  07:41 AM    <DIR>          .
09/17/2009  07:41 AM    <DIR>          ..
09/10/2009  03:41 AM           482,191
05/14/2009  01:20 AM           360,075 jbi-admin-common.jar
               2 File(s)        842,266 bytes

     Total Files Listed:
               4 File(s)      2,447,460 bytes

Start the Standalone Fuji instance making sure you provide an environment variable called com.sun.jbi.fuji.admin.jmx.connectorPort which points to a port that you'd like to use as your RMI Administration connector as shown. For e.g., as follows:

java -jar -Dcom.sun.jbi.fuji.admin.jmx.connectorPort=8585 ./bin/felix.jar

Once Fuji comes up, install the jars onto the Fuji runtime

-> install file:///E:\core\backend\fuji-management-1.0-SNAPSHOT.jar
Bundle ID: 69
-> start 69
-> install file:///E:\core\backend\FujiEventManagementWebApp-1.0-SNAPSHOT.jar
Bundle ID: 70
-> start 70

You can then exercise the management and monitoring capabilities of the runtime using the management and monitoring API. Make sure you client side code includes the mandatory client jars available in the client folder in addition to any other jar file you use in your client classpath.

Back to to How Tos

Number of visits: 26

JSPWiki v2.4.100
« Home Index Changes Prefs
This particular version was published on 17-Sep-09 09:29 AM, -0700 by Gopalan Suresh Raj