Index Changes

At line 18 changed 1 line.
[{Image src='attach/ESBConsoleGettingStarted/download.gif' link='attach/ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji/alert-client-installer.jar' align='left' }] It is always better to [Checkout and Build|ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji#section-ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji-DoingItAllFromScratch] 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 [alert-client-installer.jar|ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji/alert-client-installer.jar] that you can deploy to your standalone Fuji instance and test according to instructions mentioned below:
[{Image src='attach/ESBConsoleGettingStarted/download.gif' link='attach/ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji/fuji-standalone-manmon.jar' align='left' }] It is always better to [Checkout and Build|ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji#section-ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji-DoingItAllFromScratch] 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|ESBConsoleEnableCommonManagementAndMonitoringSupportForStandaloneFuji/fuji-standalone-manmon.jar] that you can deploy to your standalone Fuji instance and test according to instructions mentioned below:
At line 24 changed 1 line.
jar -xvf alert-client-installer.jar
jar -xvf fuji-standalone-manmon.jar
At line 26 changed 1 line.
The contents are expanded to an alerts folder which has an installer folder that contains the eventmanagement-webapp installation, and a client folder that contains the Alert Client Sample.
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 extended.management.api.core archive.
At line 28 removed 1 line.
Start the Standalone Fuji instance as follows:
At line 29 added 30 lines.
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:
{{{
At line 35 changed 2 lines.
install file:///E:\workspace\esb-console\fuji-management\target\fuji-management-1.0-SNAPSHOT.jar
install file:///E:\workspace\esb-console\extended\alerts\FujiEventManagementWebApp\target\FujiEventManagementWebApp-1.0-SNAPSHOT.jar
->
-> 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()
->
At line 39 changed 1 line.
You can then exercise the management and monitoring capabilities of the runtime using the management and monitoring API.
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.
At line 81 added 7 lines.
!! URLs of interest
! [Java CAPS Management and Monitoring APIs| http://developers.sun.com/docs/javacaps/reference/uclcm.uclcm_intro.html]
! [Java CAPS Common Management and Monitoring API JavaDocs|https://esb-console.dev.java.net/public/javadocs/managementapi/core/overview-summary.html]
! [The Extended Java CAPS Management and Monitoring API JavaDocs|https://esb-console.dev.java.net/public/javadocs/managementapi/extended/overview-summary.html]
! [Java CAPS Management and Monitoring APIs PDF|ESBConsoleHowTos/820-3388-Java CAPS Management and Monitoring APIs.pdf]

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-9) was last changed on 07-Nov-09 14:50 PM, -0800 by Gopalan Suresh Raj