12:17 a.m.
Author: irooskov(a)redhat.com
Date: 2012-05-24 01:17:48 -0400 (Thu, 24 May 2012)
New Revision: 41328
Modified:
trunk/jmx/docs/reference/en-US/Book_Info.xml
trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent
trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml
trunk/jmx/docs/reference/en-US/introduction.xml
trunk/jmx/docs/reference/en-US/tasks.xml
Log:
updated with QE feedback
Modified: trunk/jmx/docs/reference/en-US/Book_Info.xml
===================================================================
--- trunk/jmx/docs/reference/en-US/Book_Info.xml 2012-05-23 23:53:30 UTC (rev 41327)
+++ trunk/jmx/docs/reference/en-US/Book_Info.xml 2012-05-24 05:17:48 UTC (rev 41328)
@@ -5,9 +5,9 @@
<title>JMX Tools Reference Guide</title>
<subtitle>Provides information relating to the JMX Tools module.</subtitle>
<productname>JBoss Developer Studio</productname>
- <productnumber>4.1</productnumber>
- <edition>4.1.0</edition>
- <pubsnumber>1</pubsnumber>
+ <productnumber>5.0.Beta</productnumber>
+ <edition>5.0.0</edition>
+ <pubsnumber>2</pubsnumber>
<abstract>
<para>The JMX Tools Reference Guide explains how to use the JMX Tools module to
setup multiple JMX connections and explore the JMX tree and execute
operations.</para>
</abstract>
Modified: trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent
===================================================================
--- trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent 2012-05-23 23:53:30 UTC
(rev 41327)
+++ trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent 2012-05-24 05:17:48 UTC
(rev 41328)
@@ -4,4 +4,4 @@
<!ENTITY HOLDER "Red Hat">
<!ENTITY BZPRODUCT "JBoss Developer Studio">
<!ENTITY BZCOMPONENT "JMX Tools Reference Guide">
-<!ENTITY BZURL "<ulink
url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&perc...
+<!ENTITY BZURL "<ulink
url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&perc...
Modified: trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml
===================================================================
--- trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml 2012-05-23 23:53:30 UTC
(rev 41327)
+++ trunk/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml 2012-05-24 05:17:48 UTC
(rev 41328)
@@ -7,7 +7,7 @@
<xi:include href="introduction.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="tasks.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="references.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-<xi:include href="summary.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<!--<xi:include href="summary.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g...
<!--
<xi:include href="connection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="how_to.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
Modified: trunk/jmx/docs/reference/en-US/introduction.xml
===================================================================
--- trunk/jmx/docs/reference/en-US/introduction.xml 2012-05-23 23:53:30 UTC (rev 41327)
+++ trunk/jmx/docs/reference/en-US/introduction.xml 2012-05-24 05:17:48 UTC (rev 41328)
@@ -31,9 +31,9 @@
<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>
+ <!-- <para>
<ulink
url="http://java.sun.com/docs/books/tutorial/jmx/overview/index.html...
more about JMX</ulink>.
- </para>
+ </para> -->
</section>
<section>
@@ -106,7 +106,7 @@
</table>
</section>
- <section>
+<!-- <section>
<title>Requirements and Installation</title>
<section>
<title> Requirements</title>
@@ -136,5 +136,5 @@
You can find the <productname>JBoss Tools</productname> plugins over at
the <ulink url="http://labs.jboss.com/tools/download.html">download
pages</ulink>. The only package you will need to get is the JBoss JMX Tooling,
however the <productname>AS Tools</productname> 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>
+ </section> -->
</chapter>
\ No newline at end of file
Modified: trunk/jmx/docs/reference/en-US/tasks.xml
===================================================================
--- trunk/jmx/docs/reference/en-US/tasks.xml 2012-05-23 23:53:30 UTC (rev 41327)
+++ trunk/jmx/docs/reference/en-US/tasks.xml 2012-05-24 05:17:48 UTC (rev 41328)
@@ -158,10 +158,10 @@
Using SSL for authentication is not supported: you need to make sure that the System
property <guilabel>com.sun.management.jmxremote.ssl</guilabel> is set to
false.
</para>
<para>
- More information to manage Tomcat can be found in the <ulink
url="http://tomcat.apache.org/tomcat-6.0-doc/">Tomcat management
documentation</ulink>.
+ More information to manage Tomcat can be found in the <ulink
url="http://tomcat.apache.org/tomcat-7.0-doc/">Tomcat management
documentation</ulink>.
</para>
<para>
- Instructions to remotely manage Tomcat are available in <ulink
url="http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html"&g...
monitoring documentation</ulink>.
+ Instructions to remotely manage Tomcat are available in <ulink
url="http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html"&g...
monitoring documentation</ulink>.
</para>
@@ -223,10 +223,10 @@
<section>
- <title>Managing JBoss AS</title>
+ <title>Managing a JBoss application server</title>
<para>
- Managing JBoss instances is not supported with the <guilabel>JMX
Tools</guilabel> alone. You must also download and install the <guilabel>AS
Tools</guilabel> portion of the <guilabel>JBoss Tools</guilabel>
distribution. Even after installing the proper tooling, you cannot create a JBoss JMX
connection yourself or through the Connection Wizard. The first step is to create a JBoss
Server. The full instructions for this can be found in the AS Tools section, however, the
short summary is:
+ Managing JBoss instances is not supported with the <guilabel>JMX
Tools</guilabel> alone. <!-- You must also download and install the
<guilabel>AS Tools</guilabel> portion of the <guilabel>JBoss
Tools</guilabel> distribution Even after installing the proper tooling, you cannot
create a JBoss JMX connection yourself or through the Connection Wizard. --> The first
step is to create a JBoss Server. The full instructions for this can be found in the
application server Tools section; however, the short summary is:
</para>
<orderedlist>
<listitem>
@@ -263,10 +263,10 @@
</section>
<section>
- <title>Managing JBoss AS Remotely</title>
+ <title>Managing a JBoss application server Remotely</title>
<para>
- The JBoss JMX Tools allow you to easily access and manage a JBoss AS server remotely.
In order to connect to the instance of JBoss AS remotely you need to run the server or
make sure the server is launched.
+ The JBoss JMX Tools allow you to easily access and manage a JBoss AS server remotely.
In order to connect to an instance of a JBoss server remotely, you need to run the server
or make sure the server is launched.
</para>
<orderedlist>
<listitem>
@@ -296,7 +296,7 @@
<para>This section will outline how to contribute your own Server type with some
default behavior.</para>
<section>
- <title>Why we should do that?</title>
+ <title>Why you extend the framework</title>
<para>
You might be asking yourself why you would need to extend this framework if JMX is a
standard. Perhaps you want a connection to be automatically created after some specific
action, or perhaps you want your connection wizard to do more than simply set a host and
port. JBoss, for example, requires setting some credentials on the client machine, but
uses JBoss classes to do it. This requires that the connection has access to the JBoss
JARs.
@@ -332,7 +332,6 @@
<para>
<code>org.jboss.tools.jmx.ui.attribute.controls</code> - allows you to
map class types to some Control to present them in the MBean Editor
</para>
- <para>We hope this guide helped you to get started with the JBoss JMX Tools.
For additional information you are welcome on the <ulink
url="http://www.jboss.com/index.html?module=bb&op=viewforum&...
forum</ulink>.</para>
</listitem>
</itemizedlist>
</section>
@@ -364,7 +363,7 @@
The simple method is to specify the host, port (and optionally user name and
password) and click the <guibutton>OK</guibutton> button.
</para>
<para>
- On the <guilabel>Advanced</guilabel> tab you can set the sever name (it
will be displayed in <guilabel>MBean Explorer</guilabel>), and a URL to the
remote server. For example, to connect to JBoss AS you need to set the <guilabel>JMX
URL</guilabel> to
+ On the <guilabel>Advanced</guilabel> tab you can set the server name (it
will be displayed in <guilabel>MBean Explorer</guilabel>), and a URL to the
remote server. For example, to connect to JBoss AS you need to set the <guilabel>JMX
URL</guilabel> to
</para>
<programlisting
role="XML"><![CDATA[service:jmx:rmi://localhost/jndi/rmi://localhost:1090/jmxconnector]]></programlisting>
<para>If it is required you can enter user name and password for the server
connection. </para>