[jopr-commits] JOPR SVN: r1196 - docs/enterprise/JON/2.3/Installation_Guide/en-US.
jopr-commits at lists.jboss.org
jopr-commits at lists.jboss.org
Mon Sep 14 23:12:42 EDT 2009
Author: smeehan
Date: 2009-09-14 23:12:41 -0400 (Mon, 14 Sep 2009)
New Revision: 1196
Modified:
docs/enterprise/JON/2.3/Installation_Guide/en-US/Book_Info.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/Command_Line_Interface_Installation.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/Download.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/Installation_Guide.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Agent_Installation.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Best_Practices.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Server_Installation.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/Prerequisites.xml
docs/enterprise/JON/2.3/Installation_Guide/en-US/Running_the_JON_Agent.xml
Log:
Spellcheck
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/Book_Info.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/Book_Info.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -8,7 +8,7 @@
<productname>JBoss Operations Network</productname>
<productnumber>2.3</productnumber>
<edition>1</edition>
- <pubsnumber>19</pubsnumber>
+ <pubsnumber>24</pubsnumber>
<abstract>
<para>A guide to the download, installation and initial setup of the JBoss Operations Network 2.x product and management agent.</para>
</abstract>
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/Command_Line_Interface_Installation.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/Command_Line_Interface_Installation.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/Command_Line_Interface_Installation.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -67,7 +67,7 @@
<para>
The JBoss ON CLI is a standalone Java application that uses the <ulink url="http://java.sun.com/javase/6/docs/api/javax/script/package-summary.html">Java Scripting API</ulink>. This requires Java 6 or later. The CLI enables you to further integrate JBoss ON into your environment by allowing you to interact with JBoss ON programmatically. Java 6 ships with the <ulink url="http://www.mozilla.org/rhino/">Rhino</ulink>
- JavaScript engine, and as such, JavaScript is the supported scripting language in the CLI. A large subset of JBoss ON functionality is exposed in the CLI including...
+ JavaScript engine, and as such, JavaScript is the supported scripting language in the CLI. A large subset of JBoss ON functionality is exposed in the CLI.
</para>
</section>
@@ -370,7 +370,7 @@
<para>
- This connects you to the CLI, logs you into the Jboss ON server running on localhost, executes the command in quotes, and redirects the output to the file <filename>resource_types.txt</filename>. This is a detailed command so we will explain each section. We will start with <command>ResourceTypeManager.findResourceTypesByCriteria(new ResourceTypeCriteria())</command>. This invokes the <command>findResourceTypesByCriteria</command> operation on <command>ResourceTypeManager</command>. A new <command>ResourceTypeCriteria</command> object is passed as the argument.
+ This connects you to the CLI, logs you into the JBoss ON server running on localhost, executes the command in quotes, and redirects the output to the file <filename>resource_types.txt</filename>. This is a detailed command so we will explain each section. We will start with <command>ResourceTypeManager.findResourceTypesByCriteria(new ResourceTypeCriteria())</command>. This invokes the <command>findResourceTypesByCriteria</command> operation on <command>ResourceTypeManager</command>. A new <command>ResourceTypeCriteria</command> object is passed as the argument.
Nothing has been specified on the criteria object so all resource types will be returned. We will now look at the <command>pretty.print(...)</command> portion. An implicit object made available to commands and scripts by the CLI, <command>pretty</command> is useful for outputting objects in a readable, tabular format, designed with enhanced capabilities for domain objects. This single command provides a nicely formatted, text-based report of the resource types in your inventory.
@@ -806,7 +806,7 @@
</entry>
<entry>
<para>
- TODO
+
</para>
</entry>
<entry>
@@ -871,7 +871,7 @@
</entry>
<entry>
<para>
- TODO
+
</para>
</entry>
<entry>
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/Download.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/Download.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/Download.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -6,7 +6,7 @@
<title>Download JBoss ON</title>
<section id="Installation_Guide-Download-Red_Hat_Customers">
- <title>Red Hat Customers</title>
+ <title>Red Hat customers</title>
<para>
JBoss Operations Network 2.3 is available for download from the <ulink url="http://network.jboss.com/">Customer Support Portal</ulink>.
</para>
@@ -36,7 +36,7 @@
<para>Download the <emphasis role="bold">JBoss Operations Network 2.3 Base Distribution</emphasis> by clicking on the <application>Download</application> icon.</para>
</listitem>
<listitem>
- <para>You will also need to download the required <emphasis role="bold">plugin pack</emphasis> for JBoss ON 2.3 by navigating to the required <guilabel>JBoss Operations Network</guilabel> software download. For example, to download the plugin pack for JBoss ON for EAP navigate to the <guilabel>JBoss ON for EAP</guilabel> software download in the <guilabel>Product</guilabel> drop-down box. Then click on the <application>Download</application> icon next to the <guilabel>EAP PLugin Pack for Jboss ON 2.3</guilabel> link.</para>
+ <para>You will also need to download the required <emphasis role="bold">plugin pack</emphasis> for JBoss ON 2.3 by navigating to the required <guilabel>JBoss Operations Network</guilabel> software download. For example, to download the plugin pack for JBoss ON for EAP navigate to the <guilabel>JBoss ON for EAP</guilabel> software download in the <guilabel>Product</guilabel> drop-down box. Then click on the <application>Download</application> icon next to the <guilabel>EAP Plugin Pack for JBoss ON 2.3</guilabel> link.</para>
</listitem>
</itemizedlist>
<para>
@@ -45,7 +45,7 @@
</step>
<step>
- <para>Next you will need to dowload the JBoss ON license. There are three types of licenses available:</para>
+ <para>Next you will need to download the JBoss ON license. There are three types of licenses available:</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">License With Monitoring</emphasis> - this license gives you access to all features of JBoss ON (Monitoring, Inventory, Configuration, Alerts, Control Operations and Software feeds)</para>
@@ -69,7 +69,7 @@
</section>
<section id="Installation_Guide-Download-Open_Source_Community">
- <title>Open Source Community</title>
+ <title>Open source community</title>
<para>
Jopr is the open source and unsupported release of the JBoss Operations Network. The <ulink url="http://support.rhq-project.org/display/RHQ/Home">RHQ project</ulink> also provides an open source release of JBoss ON. The license file for RHQ and Jopr is either located in the SVN repository or is generated by the code.
</para>
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/Installation_Guide.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/Installation_Guide.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/Installation_Guide.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -2,7 +2,7 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<book status="draft">
+<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Download.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
@@ -11,9 +11,9 @@
<xi:include href="JON_Server_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="JON_Agent_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Running_the_JON_Agent.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Command_Line_Interface_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Initial_Auto_discovery_and_Import.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="High_Availability_Configurations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Command_Line_Interface_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="JON_Best_Practices.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Agent_Installation.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Agent_Installation.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Agent_Installation.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -120,7 +120,7 @@
</section>
<section id="Installation_Guide-Running_on_Windows-Configuring_the_Agent">
- <title>Installation Preparation</title>
+ <title>Installation preparation</title>
<para>
When the JON Agent is first executed, it enters into setup mode. In order for the JON Agent to contact the JON Server, you must enter values for the following parameters.
@@ -204,36 +204,36 @@
<para>Run the <command>rhq-agent.bat</command> script in a console and follow the prompts, entering the appropriate values. If you need help on a particular preference setting, enter <literal>!?</literal> at the setup prompt for a description of that preference.
</para>
- <programlisting>
- C:\rhq-agent-2.3.0.GA\bin> rhq-agent.bat
- </programlisting>
+<programlisting>
+C:\rhq-agent-2.3.0.GA\bin> rhq-agent.bat
+</programlisting>
<para>Option 2</para>
<para>
Edit the <filename>agent-configuration.xml</filename> and ensure to enter the correct settings. Run the <command>rhq-agent.bat</command> script and specifiy the <filename>agent-configuration.xml</filename>. For example:
</para>
- <programlisting>
- C:\rhq-agent-2.3.0.GA\bin> rhq-agent.bat --config ..\conf\agent-configuration.xml
- </programlisting>
+<programlisting>
+C:\rhq-agent-2.3.0.GA\bin> rhq-agent.bat --config ..\conf\agent-configuration.xml
+</programlisting>
<para>Option 3</para>
<para>
Run the <filename>rhq-agent.bat</filename> script and specify a valid file containing the values of all the setup parameters. For example, the command below uses a file called <filename>myAnswers.txt</filename>.
</para>
- <programlisting>
- C:\rhq-agent-2.3.0.GA\bin> rhq-agent.bat --input myAnswers.txt --nonative
- </programlisting>
+<programlisting>
+C:\rhq-agent-2.3.0.GA\bin> rhq-agent.bat --input myAnswers.txt --nonative
+</programlisting>
<para>
The <option>--nonative</option> temporarily disables the native system to allow reading input from a file. The contents of the <filename>myAnswers.txt</filename> file used in the example above is shown below. Each answer must be on its own line. To enable reading from standard input again, the last line must read <literal>native enable</literal>.
</para>
- <screen>
- [Agent Name] agentdomain.example.com
- [Agent Hostname or IP Address] agentdomain.example.com
- [Agent Port] 16163
- [RHQ Server Hostname or IP Address] serverdomain.example.com
- [RHQ Server Port] 7080
- native enable
- </screen>
+<screen>
+[Agent Name] agentdomain.example.com
+[Agent Hostname or IP Address] agentdomain.example.com
+[Agent Port] 16163
+[RHQ Server Hostname or IP Address] serverdomain.example.com
+[RHQ Server Port] 7080
+native enable
+</screen>
</step>
<step>
<para>After the agent has connected to the server, the agent command prompt appears. Enter the command <command>identify</command> to identify the RHQ Server.</para>
@@ -305,7 +305,7 @@
<section id="Installation_Guide-JON_Agent_Installation-Preparing_the_Agent">
- <title>Preparing the Agent for Auto-Update</title>
+ <title>Preparing the Agent for auto-update</title>
@@ -551,7 +551,7 @@
<section id="Installation_Guide-JON_Agent_Installation-Agent_Auto_Update">
- <title>Agent Auto-Update</title>
+ <title>Agent auto-update</title>
<para>
There is really nothing you have to do when an agent needs to be updated and it is able to auto-update itself. As long as you have configured your server and agents to allow for auto-agent updates (they are configured this way by default), it all happens automatically at the appropriate time.
@@ -619,10 +619,10 @@
<para>
If you are running the Agent on Windows and installed the original Agent as a Windows service, uninstall the Windows service:
</para>
- <screen>
- cd <old-agent-install-dir>/bin
- ./rhq-agent-wrapper.bat remove
- </screen>
+<screen>
+cd <old-agent-install-dir>/bin
+./rhq-agent-wrapper.bat remove
+</screen>
</listitem>
<listitem>
@@ -656,9 +656,9 @@
<para>
Extract the new JBoss ON Agent from the agent update binary by running the following command:
</para>
- <screen>
- java -jar <agent-update-binary.jar> --upgrade
- </screen>
+<screen>
+java -jar <agent-update-binary.jar> --upgrade
+</screen>
<para>
This will tell the agent update binary to extract the JBoss ON Agent distribution and update your currently existing agent that is found in "rhq-agent" subdirectory. At this point, you will have a fully upgraded JBoss ON Agent located in the original "rhq-agent" directory. The old agent has been backed up to the "rhq-agent-old" directory. If the upgrade encounters errors, you'll find log files that contain log messages that can help to diagnose the problem.
@@ -816,7 +816,7 @@
<section id="Installation_Guide-Preconfiguring_the_JON_Agent-Building_the_Preconfigured_Agent_Bundle">
- <title>Building the Preconfigured Agent Bundle</title>
+ <title>Building the preconfigured Agent bundle</title>
<para>
After you have preconfigured the <filename>agent-configuration.xml</filename> for all of your agents to use, you need to bundle it into what is known as a "agent update binary". Out-of-box, the JBoss ON Server already comes with the standard agent update binary (one that is not preconfigured). You have the option of preconfiguring the agent update binary. Once the JBoss ON Server has your preconfigured agent update binary, everyone who gets the agent from your JBoss ON Servers will get your preconfigured agents.
@@ -840,9 +840,9 @@
<para>
Extract the <<filename>agent-distro.zip</filename>> by unjar'ing it from the <<filename>agent-update-binary.jar</filename>>
- <screen>
- jar xvf <agent-update-binary.jar> <agent-distro.zip>
- </screen>
+<screen>
+jar xvf <agent-update-binary.jar> <agent-distro.zip>
+</screen>
</para>
</listitem>
@@ -850,9 +850,9 @@
<para>
If you have a preconfigured <filename>agent-configuration.xml</filename>, place a copy of it under the directory <filename>rhq-agent/conf</filename> next to your <<filename>agent-distro.zip</filename>> that you just extracted. If you do not yet have your own preconfigured <filename>agent-configuration.xml</filename>, you can extract the default configuration file from the <<filename>agent-distro.zip</filename>>:
- <screen>
- jar xvf <agent-distro.zip> rhq-agent/conf/agent-configuration.xml
- </screen>
+<screen>
+jar xvf <agent-distro.zip> rhq-agent/conf/agent-configuration.xml
+</screen>
</para>
<para>
@@ -865,9 +865,9 @@
<para>
Update the agent distribution <filename>.zip</filename> with your custom, preconfigured <filename>rhq-agent/conf/agent-configuration.xml</filename> file:
- <screen>
- jar uvf <agent-distro.zip> rhq-agent/conf/agent-configuration.xml
- </screen>
+<screen>
+jar uvf <agent-distro.zip> rhq-agent/conf/agent-configuration.xml
+</screen>
</para>
</listitem>
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Best_Practices.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Best_Practices.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Best_Practices.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -12,7 +12,7 @@
<section id="Installation_Guide-JON_Best_Practices-JBoss_App_Servers">
- <title>Best Practices for Managing JBoss Application Servers</title>
+ <title>Best practices for managing JBoss Application Servers</title>
<section id="Installation_Guide-JBoss_App_Servers-DynaGroups">
<title>DynaGroups</title>
@@ -48,7 +48,7 @@
<section id="Installation_Guide-JBoss_App_Servers-Useful_Alerts">
- <title>Useful Alerts</title>
+ <title>Useful alerts</title>
<formalpara>
@@ -149,7 +149,7 @@
</section>
<section id="Installation_Guide-JBoss_App_Servers-JBoss_App_Server_Setup">
- <title>JBoss Application Server Setup</title>
+ <title>JBoss Application Server setup</title>
<formalpara>
<title>Management invoker security</title>
@@ -327,7 +327,7 @@
<section id="Installation_Guide-JON_Best_Practices-JBoss_Tomcat_Servers">
- <title>Best Practices for Managing JBoss Tomcat Servers</title>
+ <title>Best Practices for managing JBoss Tomcat Servers</title>
<para>
The Tomcat plugin manages Tomcat servers provided by Apache or JBoss EWS. The earliest Tomcat5 version tested with this plugin is 5.5.23. The earliest Tomcat6 version tested with this plugin is 6.0.18.
@@ -389,7 +389,7 @@
<section id="Installation_Guide-JBoss_Tomcat_Servers-Response_Times_Tomcat_Server">
- <title>Enabling Response Time metrics for your Tomcat Server</title>
+ <title>Enabling response time metrics for your Tomcat Server</title>
<para>
Before enabling Response Time metric collection in your Tomcat Server Monitoring Schedules you need to add a servlet filter to your application's web.xml and add the filter jar, provided by JBoss ON.
@@ -504,7 +504,7 @@
<section id="Installation_Guide-Response_Times_Tomcat_Server-Filter_Mapping">
- <title>Filter Mapping</title>
+ <title>Filter mapping</title>
<screen>
@@ -530,7 +530,7 @@
<section id="Installation_Guide-Response_Times_Tomcat_Server-Jar_File_Placement">
- <title>Jar File Placement</title>
+ <title>Jar file placement</title>
<para>
The connector-rtfilter.zip file contains two jar files:
@@ -555,7 +555,7 @@
<table id="tabl-Installation_Guide-Jar_File_Placement">
- <title>Jar File Placement</title>
+ <title>Jar file placement</title>
<tgroup cols="2">
<thead>
<row>
@@ -594,7 +594,7 @@
</section>
</section>
<section id="Installation_Guide-JON_Best_Practices-Remote_Clients">
- <title>Best Practices for Remote Clients</title>
+ <title>Best practices for remote clients</title>
<section id="Installation_Guide-Remote_Clients-Remote_Client_Approach">
<title>Deciding on a Remote Client Approach</title>
@@ -622,7 +622,7 @@
</itemizedlist>
<section id="Installation_Guide-Remote_Client_Approach-CLI">
- <title>Command Line Interface (CLI)</title>
+ <title>Command line interface (CLI)</title>
<para>
The CLI is a powerful scripting tool for interacting with the JBoss ON Server. It offers Rhino Javascript as the scripting environment. Rhino is a Java-backed implementation of Javascript. Communication with the JBoss ON Server is through JBoss Remoting.
@@ -635,7 +635,7 @@
</section>
<section id="Installation_Guide-Remote_Client_Approach-Java_Client">
- <title>Java Client</title>
+ <title>Java client</title>
<para>
@@ -655,7 +655,7 @@
</section>
<section id="Installation_Guide-Remote_Client_Approach-Web_Services">
- <title>Web Services</title>
+ <title>Web services</title>
<para>
For programmatic remote clients written in languages other than Java the JBoss ON Remote API methods are available as Web Services. Or, if for some reason a Java client does not want to utilize the Client object as mentioned above, a Web Service Java client is a possibility.
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Server_Installation.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Server_Installation.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/JON_Server_Installation.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -112,31 +112,7 @@
</formalpara>
- <formalpara id="Installation_Guide-Preparation-Monitoring_the_JON_Server">
- <title>Monitoring the JON Server</title>
-
- <para>
- The JBoss ON server is capable of monitoring itself. If you intend to do this, choose one of the following two options:
- </para>
- </formalpara>
- <itemizedlist>
- <listitem>
- <para>Install a standalone agent like you would on any other machine in the network.</para>
- </listitem>
- <listitem>
- <para>Use the embedded agent that runs inside the JON Server.</para>
- </listitem>
- </itemizedlist>
-
- <para>
- Using the embedded agent frees you from having to install and maintain a separate, standalone agent. The embedded agent starts when the JON Server starts and remains running as long as the JON Server is running. If you wish to use the embedded agent, indicate in the installer to start the Agent along with the Server. Refer to the <citetitle>Embedded JON Agent</citetitle> section in the <citetitle>JON Agent Guide</citetitle> for more information.
- </para>
-
- <important>
- <para>
- The embedded agent is for monitoring the JBoss ON Server itself. If you have another JBoss Application Server instance that you would like to monitor on the same machine as the JON Server, select the standalone agent option.
- </para>
- </important>
+
</section>
@@ -451,7 +427,7 @@
<warning><title>Supported upgrades</title>
<para>
- Upgrade is not supported for version JON 1.x or any other version of JON prior to JON 2.0.0.GA. Perform a fresh JON installation if moving from a pre-JON 2.0.0.GA version.
+ Upgrade is not supported for version JON 1.x or any other version of JON prior to JON 2.x GA. Perform a fresh JON installation if moving from a pre-JON 2.x GA version.
</para>
</warning>
@@ -811,16 +787,19 @@
<para><parameter>rhq.server.database.driver-class</parameter></para>
- <para>The fully qualified class name of the JDBC driver that the RHQ Server will use to communicate with the database. An example is <emphasis role="bold">org.postgresql.Driver</emphasis> or <emphasis role="bold">com.oracle.driver.Driver</emphasis>.</para>
+ <para>The fully qualified class name of the JDBC driver that the RHQ Server will use to communicate with the database. An example is <emphasis role="bold">oracle.jdbc.driver.OracleDriver</emphasis></para>
<bridgehead>Database XA DataSource class</bridgehead>
<para><parameter>rhq.server.database.xa-datasource-class</parameter></para>
- <para>The fully qualified class name of the JDBC driver that the RHQ Server will use to communicate with the database. An example is <emphasis role="bold">org.postgresql.Driver</emphasis> or <emphasis role="bold">com.oracle.driver.Driver</emphasis>.</para>
+ <para>The fully qualified class name of the JDBC driver that the RHQ Server will use to communicate with the database. Example of this are <emphasis role="bold">org.postgresql.xa.PGXADataSource </emphasis> or <emphasis role="bold">oracle.jdbc.xa.client.OracleXADatasource</emphasis>.</para>
-
+
+
+
+
<bridgehead>Database user name</bridgehead>
<para><parameter>rhq.server.database.user-name</parameter></para>
@@ -1584,56 +1563,7 @@
</section>
-<section id="Installation_Guide-Startup_Properties-Embedded_RHQ_Agent">
- <title>Embedded RHQ Agent</title>
-
- <para>
- You have the option of installing the RHQ Agent embedded directly in the RHQ Server, as opposed to installing and running a separate process for the RHQ Agent. The embedded agent operates just like its standalone counterpart, the only difference is it is running in the same Java virtual machine as the RHQ Server. Note that if you do this, you will not have the option of a command line interface to the agent, as you would have with a standalone RHQ Agent.
-
- </para>
-
- <bridgehead>Embedded RHQ Agent Enabled</bridgehead>
- <para><parameter>rhq.server.embedded-agent.enabled</parameter></para>
-
-
- <para>
- Set this to <literal>true</literal> if you want to run the embedded RHQ Agent inside this RHQ Server. Set this to false if you want to run the RHQ Agent as a separate process or if you do not want a RHQ Agent running on the same machine as your RHQ Server.
- </para>
-
-
- <bridgehead>Embedded RHQ Agent name</bridgehead>
-
- <para><parameter>rhq.server.embedded-agent.name</parameter></para>
-
- <para>
- The name that the embedded RHQ Agent will register itself as.
- </para>
-
-
- <bridgehead>Embedded RHQ Agent disable native system</bridgehead>
-
- <para><parameter>rhq.server.embedded-agent.disable-native-system</parameter></para>
-
- <para>
- The RHQ Agent has JNI native components that is used to perform some tasks. If you are having problems with the native components, you can completely disable their usage by setting this to true. Typically, you can leave this as false under normal conditions.
- </para>
-
- <para>
- If you change this value, you must shutdown and restart the RHQ Server in order for the change to take effect.
- </para>
-
-
- <bridgehead>Embedded RHQ Agent reset configuration</bridgehead>
-
- <para><parameter>rhq.server.embedded-agent.reset-configuration</parameter></para>
-
- <para>
- If this is set to true, the embedded agent will reset its configuration at startup. Resetting the configuration means it will clear out any configuration settings currently persisted in the preferences store and reload the configuration from its built-in configuration file (i.e. the defaults it shipped with out-of-box). If false, the embedded agent will retain the configuration it had when it last was running - which may be different from its original configuration if a user changed those configuration settings from the RHQ Console. Note that this setting will <emphasis>not</emphasis> effect those configuration settings that are explicitly defined in or are derived from the <emphasis>rhq-server.properties</emphasis> startup properties file. This includes things like the Embedded RHQ Agent Disable Native System (rhq.server.embedded-agent.disable-native-system) and Incoming Agent Communications Transport (rhq.communications.connector.transport) (which tells the embedded age!
nt how to talk to the server) and the like.
- </para>
-
-</section>
-
<section id="Installation_Guide-Startup_Properties-Outgoing_Email">
<title>Outgoing email</title>
@@ -1795,7 +1725,7 @@
</section>
<section id="Installation_Guide-JON_Server_Installation_Guide-Adding_and_Updating_Agent_Plugins">
- <title>Adding and Updating Agent Plugins</title>
+ <title>Adding and updating Agent plugins</title>
<para>
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/Prerequisites.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/Prerequisites.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/Prerequisites.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -3,13 +3,13 @@
]>
<chapter id="Installation_Guide-Prerequisites">
- <title>JON 2.x Prerequisites</title>
+ <title>JON 2.x prerequisites</title>
<section id="Installation_Guide-Prerequisites-Operating_System">
- <title>Operating System</title>
+ <title>Operating system</title>
<para>
- JBoss ON 2.0 Server and Agent are supported on Linux and Windows with the amd64, i686 and ia64 architectures. Other platforms that support Java 5 are supported, but you must disable native support as this impacts upon the functionality of the JON Agent.
+ JBoss ON 2.x Server and Agent are supported on Linux and Windows with the amd64, i686 and ia64 architectures. Other platforms that support Java 5 are supported, but you must disable native support as this impacts upon the functionality of the JON Agent.
</para>
<note>
<para>All 64-bit platforms, with the exception of Linux on x64, are only supported by JBoss ON when the operating system is in 32-bit compatibility mode.</para>
@@ -201,7 +201,7 @@
<title>PostgreSQL version</title>
<para>
- JBoss ON currently supports versions 8.2.4 or later of PostgreSQL. Earlier 8.2 versions are not recommended. Postgres 8.1 is not supported.
+ JBoss ON currently supports versions 8.2.4-8.4.x of PostgreSQL. Earlier 8.2 versions are not recommended. Postgres 8.1 is not supported.
</para>
</warning>
@@ -404,7 +404,7 @@
<section id="Installation_Guide-Oracle-Oracle_Preparation">
- <title>Oracle Preparation</title>
+ <title>Oracle preparation</title>
<para>
To use Oracle with JBoss ON, you will need to follow the following three steps. More preparation is required if the advanced Oracle setup will be used. Please refer to <xref linkend="Installation_Guide-Oracle-Advanced_Oracle_Configuration" />.
@@ -491,7 +491,6 @@
GRANT SELECT ON sys.pending_trans$ TO jon;
GRANT SELECT ON sys.dba_2pc_pending TO jon;
GRANT EXECUTE ON sys.dbms_system TO jon;
-GRANT SELECT ON v$xatrans$ TO jon;
</screen>
<important>
@@ -504,7 +503,7 @@
</section>
<section id="Installation_Guide-Oracle-Sessions_and_Processes">
- <title>Sessions and Processes</title>
+ <title>Sessions and processes</title>
@@ -579,7 +578,7 @@
<section id="Installation_Guide-Oracle-SGA_and_PGA_Sizes">
- <title>SGA and PGA Sizes</title>
+ <title>SGA and PGA sizes</title>
<para>
Oracle settings for SGA and PGA sizes are very important in the performance of JBoss ON. If they are too small, your database will perform very slow, affecting JBoss ON in a very negative way. Talk to your DBA for proper sizing of your Oracle's SGA and PGA requirements. The settings you need to tune are <parameter>sga_target</parameter> and <parameter>pga_aggregate_target</parameter>.
@@ -588,7 +587,7 @@
</section>
<section id="Installation_Guide-Oracle-Tuning_Open_Cursors">
- <title>Tuning Open Cursors</title>
+ <title>Tuning open cursors</title>
<para>
If the following sql:
@@ -641,9 +640,9 @@
</para>
</warning>
- <para>
+ <!--<para>
<guilabel>Redo Logging</guilabel> should be turned <guilabel>OFF</guilabel> for all tablespaces by specifying the <command>NOLOGGING</command> clause when creating the tablespaces. In fact, <guilabel>Redo Logging</guilabel> should be turned off for <emphasis role="bold">all</emphasis> the tablespaces in the same database. This is a major bottleneck for the database, and, in our scenario, we need high throughput, which comes at the expense of recoverability. In other words, export data and back it up when you want to recover.
- </para>
+ </para>-->
</step>
<step>
<para>
Modified: docs/enterprise/JON/2.3/Installation_Guide/en-US/Running_the_JON_Agent.xml
===================================================================
--- docs/enterprise/JON/2.3/Installation_Guide/en-US/Running_the_JON_Agent.xml 2009-09-15 02:56:45 UTC (rev 1195)
+++ docs/enterprise/JON/2.3/Installation_Guide/en-US/Running_the_JON_Agent.xml 2009-09-15 03:12:41 UTC (rev 1196)
@@ -671,7 +671,7 @@
</important>
<section id="Installation_Guide-Using_the_Agent_Plugin-Inventoring_the_Agent_Server_and_its_Services">
- <title>Inventoring the Agent Server and its services</title>
+ <title>Inventorying the Agent Server and its services</title>
<para>
When you import the agent, you will get one main top-level resource and several child services added to your inventory. Some of these services are platform-specific; that is, some services are only deployed in the agent when running on Windows or when running on UNIX. All of the resources provide specialized monitoring, configuration and control of the agent. These resources are described in more detail below.
More information about the jopr-commits
mailing list