Not logged in | Login
ESB Console Enable Common Management And Monitoring Support For Glassfish V 3 With Fuji
To enable Common Management and Monitoring support for a Glassfish v3 with Fuji instance, you need the following:
You would then need to use the Common Management and Monitoring API and write client code to access the functionality.
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 extended.management.api.alerts archive in your client side classpath - that enables the alert reception, and management client side API - can be built from esb-console/extended/api/extended.management.api.alerts - 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.
jar -xvf fuji-standalone-manmon.jarThe 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 extended.management.api.core 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 extended.management.api.core-1.0-SNAPSHOT.jar 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 ManagementAPIActivator:start() E:\runtimes\osgi\felix\m8\fuji E:\runtimes\osgi\felix\m8\fuji -> -> install file:///E:\core\backend\FujiEventManagementWebApp-1.0-SNAPSHOT.jar Bundle ID: 70 -> start 70 FujiEventManagementWebApp:start() ->
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.