cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cocoon Wiki] Update of "OGSiJMXConsole" by PhilippSchmidt
Date Sat, 20 May 2006 13:49:32 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cocoon Wiki" for change notification.

The following page has been changed by PhilippSchmidt:
http://wiki.apache.org/cocoon/OGSiJMXConsole

------------------------------------------------------------------------------
      
  == Benefits for the Community ==
      
- The goal is to make the management of Cocoon based applications easier and provide a single
interface for management and logging.
- With OGSi as the plattform for the next generation of Cocoon, every feature will be realized
as a block (read OGSi bundle).
- The Integration of JMX would allow remote managmenant of the OGSi shell and logging at runtime
over an web interface.
- The JMX functionality will be realised as an an optional Cocoon Block and could be disabled,
the perfomance impact should be minimal
- since normal calls don't go trough JMX.
-     
+ The goal is to make the management of Cocoon based applications easier and provide a single
interface for management and logging. With OGSi as the plattform for the next generation of
Cocoon, every feature will be realized as a block (read OGSi bundle). The Integration of JMX
would allow remote managmenant of the OGSi shell and logging at runtime. The JMX functionality
will be realised as an an optional Cocoon Block and could be disabled, the perfomance impact
should be minimal since normal calls don't go trough JMX.
+ 
+ == Design / Approach ===
+ 
+ JMX will be bundled as a Cocoon Block (read OGSi bundle). This bundle contains an JMX MBeanServer
with the DynamicBeans that represent the different OGSi Services. An external JMX Console
would request this service to get all the registered MBeans.
+ 
+ For JMX functionality MX4J ( http://mx4j.sf.net ) will be used. 
+ For the implementation of the JMX Management Console MC4J would be an option ( http://mc4j.sf.net
) since it has a rich feature set and an Apache 2.0 License.
+  
  == Deliverables ==
      
-  * An Cocoon JMX Block as described to access to the OGSi shell.
+  * An Cocoon JMX Block as described to access OGSi.
-  * A web interface for remote management.
+  * JMX Console Implementation
   * Documentation of usage in the Cocoon Zone (Daisy).
      
  == Timeline ==

Mime
View raw message