[Jakarta HiveMind Wiki] Updated: JmxDoc

[hi...@jakarta.apache.org]

   Date: 2005-03-01T09:39:15
   Editor: AchimHuegen
   Wiki: Jakarta HiveMind Wiki
   Page: JmxDoc
   URL: http://wiki.apache.org/jakarta-hivemind/JmxDoc

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -71,12 +71,17 @@
 the application.
 
 [[Anchor(Intro)]]
-= Introduction =
+= Tutorial =
+
+This chapter describes more detailed how to build jmx support into your hivemind application.
+Actually it's just plug and play. There are a lot of default services and settings that may be
+sufficient for your use case.
+You will need a MBean server, at least one connector and of course some beans to manage.
 
 == MBean Server ==
 
-First of all you will need a running MBean Server in your application. Since JMX 1.2 there is a standardized factory for finding running servers and starting new ones.
-HiveMind first tries to find a running server. This could be provided by an application server or servlet engine (like Tomcat 5) or your J2SE 1.5 runtime environment.
+First of all you need a running MBean Server in your application. Since JMX 1.2 there is a standardized factory for finding running servers and starting new ones.
+HiveMind first tries to find a running server. This could be provided by an application server or servlet engine (like Tomcat 5) or your J2SE 1.5 runtime environment. Add these lines to your module descriptor:
 
 {{{
   <contribution configuration-id="hivemind.EagerLoad">
@@ -84,12 +89,30 @@
   </contribution>
 }}}
 
+Connecting to a running server results in a unified management of infrastructure (like tomcat) and your applications mbeans. If no running server has been found, a new one is started. 
+
 == Connectors ==
 
-There are different ways to connect to a jmx enabled application. HiveMind offers preconfigured support for HTML and JSR 160 connectors.
+There are different ways to connect to a jmx enabled application. HiveMind offers preconfigured support for HTML and JSR 160 connectors. 
 
 == HTML Connector ==
 
+HTML Connectors are always specific for the jmx library you are using (that is J2SE 1.5, Sun RI, MX4J).
+
+MX4J:
+{{{
+}}}
+
+Change the HTTP port using the symbol "management...."
+
+{{{
+}}}
+
+Now you can connect to your application using a standard browser.
+
+== JSR 160 Connector ==
+
+to be done ..
 
 
 == Export services as MBeans ==
@@ -148,15 +171,6 @@
 It is depending on MX4J but is working fine with Sun RI and J2SE 1.5 too.
 The dependency could be broken up, but there is no standardized way for creating an HTMLAdaptor.
 
-= Remarks =
-
-== Services as MBeans ==
-
-It doesn't always make sense to use the service interface as MBean interface like in the calculator example. It would be nice to separate between service and management interface. Problem: As soon as an service model other that primitive is used or the service is intercepted, the management interface is no longer accessible. 
-The reason is, that interceptors and proxies are limited to a single interface. This is already a problem for standard MBeans, that implement MBean lifecycle events.
-There are two possible solutions:
- * Interceptors and proxies populate multiple/all interfaces of a service. This was already discussed on the mailing list
- * There must be a way to access the core service instance 
 
 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org