db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyJMXQuickStart" by JohnHEmbretsen
Date Fri, 11 Apr 2008 07:36:11 GMT
Dear Wiki user,

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

The following page has been changed by JohnHEmbretsen:
http://wiki.apache.org/db-derby/DerbyJMXQuickStart

The comment on the change is:
Reworked the introduction

------------------------------------------------------------------------------
  
  = JMX QUICK START =
  
+ == Introduction ==
+ 
+ === What are Derby's JMX features? ===
+ 
+ In short, Derby's JMX features consist of a set of MBeans (Managed Beans) and their attributes
and operations, providing monitoring and management capabilities. MBean implementations instrument
one or more parts of a running Derby system, potentially giving you real-time access to Derby-specific
information and features from a host of your choice. The word ''potentially'' here indicates
that JMX access may depend on how you configure your JVM and (for example) Derby's security
features.
+ 
+ The documentation of each MBean describes the features in more detail, see also ["DerbyJMX"].
+ 
+ === When can I use Derby's JMX features? ===
+ 
+ Derby's JMX features were first introduced with the [:DerbyTenFourRelease:the 10.4.1 release]
in April 2008.
+ 
- Derby's JMX features are automatically available when Derby is started in a Java Virtual
Machine (JVM) supporting the [http://java.sun.com/j2se/1.5.0/docs/guide/management/overview.html#mxbeans
platform MBean Server]. This includes JVMs supporting J2SE 5.0, Java SE 6, or newer. Derby's
JMX features are not available when using J2SE 1.4.2 or Java ME (as per March 2008).
+ Derby's JMX features are automatically available when Derby is started in a Java Virtual
Machine (JVM) supporting the [http://java.sun.com/j2se/1.5.0/docs/guide/management/overview.html#mxbeans
platform MBean Server]. This includes JVMs supporting J2SE 5.0, Java SE 6, or newer. 
+ 
+ Derby's JMX features are ''not'' available when using J2SE 1.4.2 or Java ME (as per April
2008).
  
  You start Derby by loading Derby's embedded driver. If you are using Derby's Network Server,
the embedded driver is automatically loaded in the server JVM when the server is started.
  
- In short, Derby's JMX features consist of a set of MBeans (Managed Beans) and their attributes
and operations. MBean implementations instrument one or more parts of a running Derby system,
potentially giving you real-time access to Derby-specific information from a host of your
choice. The word ''potentially'' here indicates that JMX access may depend on how you configure
your JVM and (for example) Derby's security features.
+ You may access Derby's MBeans using for example an existing JMX client utility, such as
[#JConsoleAccess JConsole], or [#ProgrammaticAccess programmatically] by writing your own
Java code utilizing JMX.
  
+ === Huh? ===
+ 
- Note that if you are unfamiliar with JMX technology, it may be a good idea to take a look
at some of the references provided [:DerbyJMX#Resources:here] before you continue. 
+ If you are unfamiliar with JMX technology, it may be a good idea to take a look at some
of the references provided [:DerbyJMX#Resources:here] before you continue. 
- 
- You may access Derby's MBeans using for example an existing JMX client utility, such as
JConsole, or programmatically by writing your own Java code utilizing JMX.
  
  == Enabling JMX ==
  
@@ -87, +101 @@

  
  ''TODO - Add example policy here...''
  
+ [[Anchor(JConsoleAccess)]]
  == Using JConsole to access Derby's MBeans ==
  
  JConsole is a graphical JMX-compliant tool originally developed by Sun Microsystems, and
is available in recent versions of Sun's Java Development Kits (JDKs). JConsole enables you
to monitor and manage Java applications and virtual machines on a local or remote machine.
@@ -117, +132 @@

  
  inline:nserverGraphJConsole.png
  
- 
+ [[Anchor(ProgrammaticAccess)]]
  == Accessing Derby's MBeans using custom Java code ==
  
  Besides using generic tools as described above, it is also possible to access Derby's MBeans
programmatically, that is from a Java application. How to do this may depend on how you configure
the JVM running Derby, for example how you configure user authentication and authorization,
or from which host(s) you want to access the MBeans. 

Mime
View raw message