9:09 p.m.
Author: irooskov(a)redhat.com
Date: 2010-06-06 22:09:45 -0400 (Sun, 06 Jun 2010)
New Revision: 22592
Modified:
branches/3.2.helios/jmx/docs/reference/en-US/introduction.xml
branches/3.2.helios/jmx/docs/reference/en-US/tasks.xml
Log:
updated to correct build errors
Modified: branches/3.2.helios/jmx/docs/reference/en-US/introduction.xml
===================================================================
--- branches/3.2.helios/jmx/docs/reference/en-US/introduction.xml 2010-06-07 00:03:03 UTC
(rev 22591)
+++ branches/3.2.helios/jmx/docs/reference/en-US/introduction.xml 2010-06-07 02:09:45 UTC
(rev 22592)
@@ -1,4 +1,3 @@
-<<<<<<< .mine
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="intruduction" xreflabel="introduction">
<?dbhtml filename="introduction.html"?>
@@ -22,142 +21,8 @@
<para>
Using the JMX technology, a given resource is instrumented by one or more Java objects
known as Managed Beans, or MBeans. These MBeans are registered in a core-managed object
server, known as an MBean server. The MBean server acts as a management agent and can run
on most devices that have been enabled for the Java programming language.
</para>
-
- <para>
-The specifications define JMX agents that you use to manage any resources that have been
correctly configured for management. A JMX agent consists of an MBean server, in which
MBeans are registered, and a set of services for handling the MBeans. In this way, JMX
agents directly control resources and make them available to remote management
applications.
-</para>
- <para>
-The way in which resources are instrumented is completely independent from the management
infrastructure. Resources can therefore be rendered manageable regardless of how their
management applications are implemented.
-</para>
- <para>
-The JMX technology defines standard connectors (known as JMX connectors) that enable you
to access JMX agents from remote management applications. JMX connectors using different
protocols provide the same management interface. Consequently, a management application
can manage resources transparently, regardless of the communication protocol used. JMX
agents can also be used by systems or applications that are not compliant with the JMX
specification, as long as those systems or applications support JMX agents.
-</para>
-<ulink
-
url="http://java.sun.com/docs/books/tutorial/jmx/overview/index.html...
more about JMX</ulink>.
- </section>
-
- <section>
- <title>What is JMX Tools?</title>
- <para><property>JBoss JMX Tools</property> allow to setup multiple
JMX connections and provide view
- for exploring the JMX tree and execute operations directly from
Eclipse.</para>
- <para>This chapter covers the basics of working with <property>JMX
plugin</property>, which is
- used to manage Java applications (with Managed Beans) through JMX and its RMI
Connector.</para>
-
- <figure>
- <title>JMX Tools</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eclipse-jmx_0.2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section><title>Key Features of JMX Tools</title>
- <para>For a start, we propose you to look through the table of main features of
JBoss JMX Tools:</para>
- <table>
-
- <title>Key Functionality for JBoss JMX Tools</title>
- <tgroup cols="3">
-
- <colspec colnum="1" align="left"
colwidth="2*"/>
- <colspec colnum="2" colwidth="4*"/>
- <colspec colnum="3" align="left"
colwidth="2*"/>
-
- <thead>
- <row>
- <entry>Feature</entry>
- <entry>Benefit</entry>
- <entry>Chapter</entry>
- </row>
- </thead>
-
- <tbody>
-
- <row>
- <entry><para>MBean Explorer</para></entry>
- <entry><para>MBean Explorer is a useful view with a text filter
that displays domains, mbeans, attributes, and operations inside a
connection.</para></entry>
- <entry>
- <link linkend="mbean_explorer">MBean Explorer</link>
- </entry>
- </row>
-
- <row>
- <entry><para>MBean Editor</para></entry>
- <entry><para>MBean Editor is a multi-page editor to manage
MBeans.</para></entry>
- <entry>
- <link linkend="mbean_editor">MBean Editor</link>
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </section>
-
- <section>
- <title>Requirements and Installation</title>
- <section>
- <title> Requirements</title>
- <para>Requirements to use <property>JBoss JMX Tools</property> are
the following:</para>
-
- <itemizedlist>
- <listitem>
- <para><property>JBoss JMX Tools</property> is developed on
Eclipse 3.4.x milestones</para>
- </listitem>
- <listitem>
- <para><property>JBoss JMX Tools</property> requires that
Eclipse is run on a JDK 1.5.0 or above
- (due to dependencies on JMX packages which were introduced in Java
1.5.0)</para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Installation</title>
- <para>Here, we are going to explain how to install the <property>JMX
plugin</property> into
- Eclipse.</para>
-
- <para><property>JBoss JMX Tools</property> is one module of the
<property>JBoss Tools</property>
- project. <property> JBoss JMX Tools</property> has no dependency on any
other part of <property>JBoss
- Tools</property>, and can be downloaded as a standalone Eclipse plugin.
Even though the <property>JMX
- Tools</property> have no dependencies on other plugins, such as
<property>AS Tools</property>,
- <property>JBoss JMX Tools</property> do depend on the JMX Tooling and
even extend it. </para>
-
- <para>You can find the <property>JBoss JBoss Tools</property>
plugins over at the <ulink
- url="http://labs.jboss.com/tools/download.html">download
pages</ulink>. The only
- package you'll need to get is the JBoss JMX Tooling, however the
<property>AS
- Tools</property> would give you a wider experience and more options when
using JMX with JBoss Servers.
- You can find further download and installation instructions on the JBoss Wiki in
the <ulink
-
url="http://www.jboss.org/tools/download/installation">Insta...
- section.</para>
- </section>
- </section>
-</chapter>
-=======
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<chapter id="intruduction" xreflabel="introduction">
- <?dbhtml filename="introduction.html"?>
-
- <title>Introduction</title>
- <para><property>JBoss Tools</property>' JMX project is a
fork of <ulink
- url="http://code.google.com/p/eclipse-jmx/">eclipse-jmx</...;, a
project by Jeff Mesnil.
- It was forked with permission. </para>
-
- <section>
- <title>What is JMX?</title>
<para>
-The Java Management Extensions (JMX) technology is a standard part of the Java Platform,
Standard Edition (Java SE platform). The JMX technology was added to the platform in the
Java 2 Platform, Standard Edition (J2SE) 5.0 release.
-</para>
- <para>
-The JMX technology provides a simple, standard way of managing resources such as
applications, devices, and services. Because the JMX technology is dynamic, you can use it
to monitor and manage resources as they are created, installed and implemented. You can
also use the JMX technology to monitor and manage the Java Virtual Machine (Java VM).
-</para>
- <para>
-The JMX specification defines the architecture, design patterns, APIs, and services in
the Java programming language for management and monitoring of applications and networks.
-</para>
- <para>
-Using the JMX technology, a given resource is instrumented by one or more Java objects
known as Managed Beans, or MBeans. These MBeans are registered in a core-managed object
server, known as an MBean server. The MBean server acts as a management agent and can run
on most devices that have been enabled for the Java programming language.
-</para>
-
- <para>
The specifications define JMX agents that you use to manage any resources that have been
correctly configured for management. A JMX agent consists of an MBean server, in which
MBeans are registered, and a set of services for handling the MBeans. In this way, JMX
agents directly control resources and make them available to remote management
applications.
</para>
<para>
@@ -166,8 +31,10 @@
<para>
The JMX technology defines standard connectors (known as JMX connectors) that enable you
to access JMX agents from remote management applications. JMX connectors using different
protocols provide the same management interface. Consequently, a management application
can manage resources transparently, regardless of the communication protocol used. JMX
agents can also be used by systems or applications that are not compliant with the JMX
specification, as long as those systems or applications support JMX agents.
</para>
+<para>
<ulink
url="http://java.sun.com/docs/books/tutorial/jmx/overview/index.html...
more about JMX</ulink>.
+</para>
</section>
<section>
@@ -265,4 +132,4 @@
section.</para>
</section>
</section>
-</chapter>>>>>>>> .r22100
+</chapter>
Modified: branches/3.2.helios/jmx/docs/reference/en-US/tasks.xml
===================================================================
--- branches/3.2.helios/jmx/docs/reference/en-US/tasks.xml 2010-06-07 00:03:03 UTC (rev
22591)
+++ branches/3.2.helios/jmx/docs/reference/en-US/tasks.xml 2010-06-07 02:09:45 UTC (rev
22592)
@@ -41,7 +41,7 @@
a sample Java application and run the <property>sayHello()</property> method
remotely from inside of the <property>MBean Explorer</property>.</para>
<orderedlist>
-http://java.sun.com/docs/books/tutorial/jmx/examples/jmx_examples.zip
+<!--http://java.sun.com/docs/books/tutorial/jmx/examples/jmx_examples.zip-->
<listitem><para>Save the bundle of JMX API sample classes, <ulink
url="http://java.sun.com/docs/books/tutorial/jmx/examples/jmx_exampl...;,
to your working directory</para></listitem>
<listitem><para>Unzip the bundle of sample
classes.</para></listitem>