< prev index next >

src/java.management/share/classes/javax/management/package.html

Print this page
rev 60127 : 8249205: Remove unnecessary trademark symbols


  13 
  14 This code is distributed in the hope that it will be useful, but WITHOUT
  15 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
  16 FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
  17 version 2 for more details (a copy is included in the LICENSE file that
  18 accompanied this code).
  19 
  20 You should have received a copy of the GNU General Public License version
  21 2 along with this work; if not, write to the Free Software Foundation,
  22 Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
  23 
  24 Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
  25 or visit www.oracle.com if you need additional information or have any
  26 questions.
  27         -->
  28     </head>
  29     <body bgcolor="white">
  30         <p>Provides the core classes for the Java Management Extensions.</p>
  31 
  32         <p>The Java Management Extensions
  33             (JMX&trade;) API is a standard
  34         API for management and monitoring.  Typical uses include:</p>
  35 
  36         <ul>
  37             <li>consulting and changing application configuration</li>
  38 
  39             <li>accumulating statistics about application behavior and
  40             making them available</li>
  41 
  42             <li>notifying of state changes and erroneous conditions.</li>
  43         </ul>
  44 
  45         <p>The JMX API can also be used as part of a solution for
  46         managing systems, networks, and so on.</p>
  47 
  48         <p>The API includes remote access, so a remote management
  49             program can interact with a running application for these
  50         purposes.</p>
  51 
  52         <h2>MBeans</h2>
  53 


  70             configuration items.  Reading the <code>CacheSize</code>
  71             attribute would return the current value of that item.
  72             Writing it would update the item, potentially changing the
  73             behavior of the running application.  An operation such as
  74             <code>save</code> could store the current configuration
  75             persistently.  A notification such as
  76             <code>ConfigurationChangedNotification</code> could be sent
  77         every time the configuration is changed.</p>
  78 
  79         <p>In the standard usage of the JMX API, MBeans are implemented
  80             as Java objects.  However, as explained below, these objects are
  81         not usually referenced directly.</p>
  82 
  83 
  84         <h3>Standard MBeans</h3>
  85 
  86         <p>To make MBean implementation simple, the JMX API includes the
  87             notion of <em>Standard MBeans</em>.  A Standard MBean is one
  88             whose attributes and operations are deduced from a Java
  89             interface using certain naming patterns, similar to those used
  90             by JavaBeans&trade;.  For example, consider an interface like this:</p>
  91 
  92         <pre>
  93     public interface ConfigurationMBean {
  94          public int getCacheSize();
  95          public void setCacheSize(int size);
  96          public long getLastChangedTime();
  97          public void save();
  98     }
  99         </pre>
 100 
 101         <p>The methods <code>getCacheSize</code> and
 102             <code>setCacheSize</code> define a read-write attribute of
 103             type <code>int</code> called <code>CacheSize</code> (with an
 104         initial capital, unlike the JavaBeans convention).</p>
 105 
 106         <p>The method <code>getLastChangedTime</code> defines an
 107             attribute of type <code>long</code> called
 108             <code>LastChangedTime</code>.  This is a read-only attribute,
 109         since there is no method <code>setLastChangedTime</code>.</p>
 110 




  13 
  14 This code is distributed in the hope that it will be useful, but WITHOUT
  15 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
  16 FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
  17 version 2 for more details (a copy is included in the LICENSE file that
  18 accompanied this code).
  19 
  20 You should have received a copy of the GNU General Public License version
  21 2 along with this work; if not, write to the Free Software Foundation,
  22 Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
  23 
  24 Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
  25 or visit www.oracle.com if you need additional information or have any
  26 questions.
  27         -->
  28     </head>
  29     <body bgcolor="white">
  30         <p>Provides the core classes for the Java Management Extensions.</p>
  31 
  32         <p>The Java Management Extensions
  33             (JMX) API is a standard
  34         API for management and monitoring.  Typical uses include:</p>
  35 
  36         <ul>
  37             <li>consulting and changing application configuration</li>
  38 
  39             <li>accumulating statistics about application behavior and
  40             making them available</li>
  41 
  42             <li>notifying of state changes and erroneous conditions.</li>
  43         </ul>
  44 
  45         <p>The JMX API can also be used as part of a solution for
  46         managing systems, networks, and so on.</p>
  47 
  48         <p>The API includes remote access, so a remote management
  49             program can interact with a running application for these
  50         purposes.</p>
  51 
  52         <h2>MBeans</h2>
  53 


  70             configuration items.  Reading the <code>CacheSize</code>
  71             attribute would return the current value of that item.
  72             Writing it would update the item, potentially changing the
  73             behavior of the running application.  An operation such as
  74             <code>save</code> could store the current configuration
  75             persistently.  A notification such as
  76             <code>ConfigurationChangedNotification</code> could be sent
  77         every time the configuration is changed.</p>
  78 
  79         <p>In the standard usage of the JMX API, MBeans are implemented
  80             as Java objects.  However, as explained below, these objects are
  81         not usually referenced directly.</p>
  82 
  83 
  84         <h3>Standard MBeans</h3>
  85 
  86         <p>To make MBean implementation simple, the JMX API includes the
  87             notion of <em>Standard MBeans</em>.  A Standard MBean is one
  88             whose attributes and operations are deduced from a Java
  89             interface using certain naming patterns, similar to those used
  90             by JavaBeans.  For example, consider an interface like this:</p>
  91 
  92         <pre>
  93     public interface ConfigurationMBean {
  94          public int getCacheSize();
  95          public void setCacheSize(int size);
  96          public long getLastChangedTime();
  97          public void save();
  98     }
  99         </pre>
 100 
 101         <p>The methods <code>getCacheSize</code> and
 102             <code>setCacheSize</code> define a read-write attribute of
 103             type <code>int</code> called <code>CacheSize</code> (with an
 104         initial capital, unlike the JavaBeans convention).</p>
 105 
 106         <p>The method <code>getLastChangedTime</code> defines an
 107             attribute of type <code>long</code> called
 108             <code>LastChangedTime</code>.  This is a read-only attribute,
 109         since there is no method <code>setLastChangedTime</code>.</p>
 110 


< prev index next >