[jboss-cvs] JBossAS SVN: r101701 - projects/docs/enterprise/EWP_5.0/mod_cluster/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Mar 2 01:21:05 EST 2010
Author: gmeintjes
Date: 2010-03-02 01:21:05 -0500 (Tue, 02 Mar 2010)
New Revision: 101701
Modified:
projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Author_Group.xml
projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Book_Info.xml
projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Overview.xml
projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/QuickStartGuide.xml
projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Revision_History.xml
projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent
Log:
Conversion from EAP Document first pass
Modified: projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Author_Group.xml 2010-03-02 06:17:02 UTC (rev 101700)
+++ projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Author_Group.xml 2010-03-02 06:21:05 UTC (rev 101701)
@@ -4,7 +4,7 @@
<authorgroup>
- <othercredit>
+ <!-- <othercredit>
<firstname>Permaine</firstname>
<surname>Cheung</surname>
<contrib>Technical Review
@@ -25,7 +25,7 @@
<surname>Husar</surname>
<contrib>Technical Review
</contrib>
- </othercredit>
+ </othercredit> -->
<editor>
Modified: projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Book_Info.xml 2010-03-02 06:17:02 UTC (rev 101700)
+++ projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Book_Info.xml 2010-03-02 06:21:05 UTC (rev 101701)
@@ -3,14 +3,14 @@
]>
<bookinfo id="mod_cluster_User_Guide">
<title>mod_cluster User Guide</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 5.0</subtitle>
- <productname>JBoss Enterprise Application Platform</productname>
+ <subtitle>for Use with JBoss Enterprise Web Platform 5.0</subtitle>
+ <productname>JBoss Enterprise Web Platform</productname>
<productnumber>5.0</productnumber>
<edition>1</edition>
- <pubsnumber>2.3</pubsnumber>
+ <pubsnumber>0.1</pubsnumber>
<abstract>
<para>
-mod_cluster is an httpd-based load balancer that uses a
+mod_cluster Is an httpd-based load balancer that uses a
communication channel to forward requests from httpd to one of a
set of application server nodes.
</para>
Modified: projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-03-02 06:17:02 UTC (rev 101700)
+++ projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-03-02 06:21:05 UTC (rev 101701)
@@ -2,7 +2,7 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<chapter id="chap-mod_cluster-Configuring_for_JBoss_AS">
- <title>Configuring for JBoss AS</title>
+ <title>Configuring mod_cluster</title>
<!-- <note>
<para>
mod_cluster currently works with <application>JBoss AS 5.0</application>.
@@ -11,7 +11,7 @@
<section id="sect-mod_cluster-Configuring_for_JBoss_AS-Common_Configuration">
<title>Common Configuration</title>
<para>
- To begin configuring for JBoss AS, edit the following file:
+ To begin configuring for JBoss Enterprise Web Platform (EWP), edit the following file:
<filename>$JBOSS_HOME/server/$PROFILE/deploy/jbossweb.sar/server.xml</filename>
</para>
@@ -54,9 +54,9 @@
</section>
<section id="sect-mod_cluster-Configuring_for_JBoss_AS-JBoss_AS_Integration">
- <title>JBoss AS Integration</title>
+ <title>JBoss EWP Integration</title>
<para>
- The server.xml lifecycle listener used by mod_cluster in JBoss AS functions as a simple bridge delegating all lifecycle events to a bean deployed in the JBoss microcontainer.
+ The server.xml lifecycle listener used by mod_cluster in JBoss EWP functions as a simple bridge delegating all lifecycle events to a bean deployed in the JBoss microcontainer.
</para>
<programlisting>
@@ -177,7 +177,7 @@
</listitem>
</orderedlist> -->
<para>
- If your application server already uses other clustering services (e.g. session replication), then you should consider running mod_cluster in clustered-mode. If your application server is stateless (i.e. no sessions), or you are not using other clustering services, then non-clustered mode may be more appropriate.
+ If your web platform already uses other clustering services (e.g. session replication), then you should consider running mod_cluster in clustered-mode. If your web platform is stateless (i.e. no sessions), or you are not using other clustering services, then non-clustered mode may be more appropriate.
</para>
<para>
The <classname>HAModClusterService</classname> bean descriptor is found in the following file:
@@ -213,7 +213,7 @@
</para>
</listitem>
</varlistentry>
- <varlistentry><term>An <classname>HAModClusterConfig</classname> bean, defining containing the configuration properties.</term>
+ <varlistentry><term>An <classname>HAModClusterConfig</classname> bean, defining the configuration properties.</term>
<listitem>
<para>
For the complete list of configuration properties available to ModClusterService, refer to the following in Configuration Properties:
Modified: projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Overview.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Overview.xml 2010-03-02 06:17:02 UTC (rev 101700)
+++ projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Overview.xml 2010-03-02 06:21:05 UTC (rev 101701)
@@ -91,7 +91,7 @@
</listitem>
<listitem>
<para>
- <application>JBoss Enterprise Application Platform 5.0+</application>
+ <application>JBoss Enterprise Web Platform 5.0+</application>
</para>
</listitem>
</itemizedlist>
@@ -105,7 +105,7 @@
<section id="sect-mod_cluster-Overview-Configuration">
<title>Configuration</title>
<para>
- To configure for JBoss Enterprise Application Platform, refer to the relavant chapter in this publication.
+ To configure for JBoss Enterprise Web Platform (EWP), refer to the relavant chapter in this publication.
</para>
</section>
@@ -119,7 +119,7 @@
<section id="sect-mod_cluster-Overview-Load_Balancing_Demo_Application">
<title>Load Balancing Demo Application</title>
<para>
- The mod_cluster binary distribution for JBoss Enterprise Application Platform includes a demo application that helps demonstrate how different server-side scenarios affect the routing of client requests by the load balancer. The demo application is located in the mod_cluster distribution's demo directory.
+ The mod_cluster binary distribution for JBoss EWP includes a demo application that helps demonstrate how different server-side scenarios affect the routing of client requests by the load balancer. The demo application is located in the mod_cluster distribution's demo directory.
</para>
</section>
Modified: projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/QuickStartGuide.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-03-02 06:17:02 UTC (rev 101700)
+++ projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-03-02 06:21:05 UTC (rev 101701)
@@ -4,7 +4,7 @@
<chapter id="chap-mod_cluster-Quick_Start_Guide">
<title>Quick Start Guide</title>
<para>
- The following steps are required to set up a minimal working installation of mod_cluster on a single <application>httpd</application> server and a single back end server, either <application>JBoss Enterprise Application Platform</application>, <application>JBoss Web</application> or <application>Tomcat</application>. The steps can be repeated to add as many httpd servers or back end servers to your cluster as desired.
+ The following steps are required to set up a minimal working installation of mod_cluster on a single <application>httpd</application> server and a single back end server, either <application>JBoss Enterprise Web Platform</application>, <application>JBoss Web</application> or <application>Tomcat</application>. The steps can be repeated to add as many httpd servers or back end servers to your cluster as desired.
</para>
<para>
The steps shown here are not intended to demonstrate how to set up a production install of mod_cluster; for example using <application>SSL</application> to secure access to the httpd-side mod_manager component is not covered. See the <citetitle>httpd-side</citetitle> and <citetitle>Java-side configuration documentation</citetitle> for the full set of configuration options.
@@ -258,7 +258,7 @@
<term>AdvertiseGroup IP:port </term>
<listitem>
<para>
- That is the multicast address to use (something like 232.0.0.2:8888 for example). IP should correspond to <varname>AdvertiseGroupAddress</varname> and port to <literal>AdvertisePort</literal> in the JBoss EAP/JBossWeb/Tomcat configuration. Note that if JBoss Enterprise Application Platform is used and the <literal>-u</literal> startup switch is included in the Enterprise Application Platform startup command, the default <varname>AdvertiseGroupAddress</varname> is the value passed via the <literal>-u</literal>. Default: 224.0.1.105:23364. If port is missing the default port will be used: 23364.
+ That is the multicast address to use (something like 232.0.0.2:8888 for example). IP should correspond to <varname>AdvertiseGroupAddress</varname> and port to <literal>AdvertisePort</literal> in the JBoss EAP/JBossWeb/Tomcat configuration. Note that if JBoss EWP is used and the <literal>-u</literal> startup switch is included in the Enterprise Application Platform startup command, the default <varname>AdvertiseGroupAddress</varname> is the value passed via the <literal>-u</literal>. Default: 224.0.1.105:23364. If port is missing the default port will be used: 23364.
</para>
</listitem>
</varlistentry>
@@ -572,7 +572,7 @@
<term>ManagerBalancerName</term>
<listitem>
<para>
- <filename>ManagerBalancerName</filename> is the name of balancer to use when the JBoss AEP/JBoss Web/Tomcat doesn't provide a balancer name. That is not supported in the current version. (Default value is used). Default: <filename>mycluster</filename>
+ <filename>ManagerBalancerName</filename> is the name of balancer to use when JBoss EWP/JBoss Web/Tomcat doesn't provide a balancer name. That is not supported in the current version. (Default value is used). Default: <filename>mycluster</filename>
</para>
</listitem>
</varlistentry>
@@ -643,7 +643,7 @@
<term>ServerAdvertise On</term>
<listitem>
<para>
- Use the advertise mechanism to tell the JBoss Enterprise Application Platform/JBoss Web/Tomcat to whom it should send the cluster information.
+ Use the advertise mechanism to tell the JBoss Enterprise Web Platform/JBoss Web/Tomcat to whom it should send the cluster information.
</para>
</listitem>
</varlistentry>
@@ -667,7 +667,7 @@
<term>AdvertiseGroup IP:port </term>
<listitem>
<para>
- That is the multicast address to use (something like 232.0.0.2:8888 for example). IP should correspond to <varname>AdvertiseGroupAddress</varname> and port to <literal>AdvertisePort</literal> in the JBoss Enterprise Application Platform/JBoss Web/Tomcat configuration. Note that if JBoss Enterprise Application Platform is used and the <literal>-u</literal> startup switch is included in the Enterprise Application Platform startup command, the default <varname>AdvertiseGroupAddress</varname> is the value passed via the <literal>-u</literal>. Default: 224.0.1.105:23364. If port is missing the default port will be used: 23364.
+ That is the multicast address to use (something like 232.0.0.2:8888 for example). IP should correspond to <varname>AdvertiseGroupAddress</varname> and port to <literal>AdvertisePort</literal> in the JBoss Enterprise Web Platform/JBoss Web/Tomcat configuration. Note that if JBoss Enterprise Web Platform is used and the <literal>-u</literal> startup switch is included in the Enterprise Web Platform startup command, the default <varname>AdvertiseGroupAddress</varname> is the value passed via the <literal>-u</literal>. Default: 224.0.1.105:23364. If port is missing the default port will be used: 23364.
</para>
</listitem>
</varlistentry>
@@ -691,7 +691,7 @@
<term>AdvertiseManagerUrl value</term>
<listitem>
<para>
- Not used in this version (It is sent in the X-Manager-Url: value header). That is the URL that JBoss Enterprise Application Platform/JBoss Web/Tomcat should use to send information to mod_cluster. Default: No default value. Information not sent.
+ Not used in this version (It is sent in the X-Manager-Url: value header). That is the URL that JBoss Enterprise Web Platform/JBoss Web/Tomcat should use to send information to mod_cluster. Default: No default value. Information not sent.
</para>
</listitem>
</varlistentry>
@@ -714,12 +714,12 @@
Extract the <classname>Java-side</classname> binary to a temporary directory. The following assumes it was extracted to <filename>/tmp/mod-cluster</filename>.
</para>
<para>
- The next step depends on whether your target server is JBoss Enterprise Application Platform or JBoss Web/Tomcat.
+ The next step depends on whether your target server is JBoss EWP or JBoss Web/Tomcat.
</para>
<formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_AS_5.x_and_up">
- <title>Installing in JBoss Enterprise Application Platform 5.0</title>
+ <title>Installing in JBoss EWP 5.0</title>
<para>
- Assume that <filename>$JBOSS_HOME </filename> indicates the root of your JBoss Enterprise Application Platform install and that you want to use mod_cluster in the <literal>production</literal> profile:
+ Assume that <filename>$JBOSS_HOME </filename> indicates the root of your JBoss EWP install and that you want to use mod_cluster in the <literal>production</literal> profile:
</para>
</formalpara>
@@ -739,7 +739,7 @@
<!--<formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_AS_4.2.x_or_4.3.x">
<title>Installing in JBoss AS 4.2.x or 4.3.x</title>
<para>
- Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss Enterprise Application Platform install and that you want to use mod_cluster in the <literal>production</literal> profile:
+ Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss EWP install and that you want to use mod_cluster in the <literal>production</literal> profile:
</para>
</formalpara>
@@ -749,7 +749,7 @@
</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Configuring_JBoss_AS_JBoss_Web_or_Tomcat">
- <title>Configuring JBoss Enterprise Application Platform, JBoss Web or Tomcat</title>
+ <title>Configuring JBoss EWP, JBoss Web or Tomcat</title>
<para>
mod_cluster is integrated into the web server by adding an implementation of the <application>Tomcat LifecycleListener</application> interface to the server's configuration, and by giving each node a unique name.
</para>
@@ -831,9 +831,9 @@
<section id="sect-mod_cluster-Quick_Start_Guide-Start_the_back_end_server">
<title>Start the back end server</title>
<formalpara id="form-mod_cluster-Start_the_back_end_server-Starting_JBoss_AS">
- <title>Starting JBoss Enterprise Application Platform</title>
+ <title>Starting JBoss EWP</title>
<para>
- To start <application>JBoss Enterprise Application Platform</application> enter the following:
+ To start <application>JBoss EWP</application> enter the following:
</para>
</formalpara>
@@ -878,7 +878,7 @@
<orderedlist>
<listitem>
<para>
- The first component is a <filename>war</filename> file that needs to be deployed in JBoss Web/Tomcat/JBoss Enterprise Application Platform. The <filename>war</filename> includes a number of servlets:
+ The first component is a <filename>war</filename> file that needs to be deployed in JBoss Web/Tomcat/JBoss EWP. The <filename>war</filename> includes a number of servlets:
<itemizedlist>
<listitem>
<para>
@@ -934,17 +934,17 @@
</listitem>
<listitem>
<para>
- Install mod_cluster into your JBoss Enterprise Application Platform/JBoss Web/Tomcat servers as described at Installation on the Java side.
+ Install mod_cluster into your JBoss EWP/JBoss Web/Tomcat servers as described at Installation on the Java side.
</para>
</listitem>
<listitem>
<para>
- Start httpd and your JBoss Enterprise Application Platform/JBoss Web/Tomcat servers.
+ Start httpd and your JBoss EWP/JBoss Web/Tomcat servers.
</para>
</listitem>
<listitem>
<para>
- Deploy the <filename>load-demo.war</filename> found in the distribution's <filename class='directory'>demo/server</filename>folder to your JBoss Enterprise Application Platform/JBoss Web/Tomcat servers.
+ Deploy the <filename>load-demo.war</filename> found in the distribution's <filename class='directory'>demo/server</filename>folder to your JBoss EWP/JBoss Web/Tomcat servers.
</para>
</listitem>
<listitem>
@@ -981,7 +981,7 @@
</listitem>
<listitem>
<para>
- Switch to the Request Balancing tab to see how many requests are going to each of your JBoss Enterprise Application Platform/JBoss Web/Tomcat servers.
+ Switch to the Request Balancing tab to see how many requests are going to each of your JBoss EWP/JBoss Web/Tomcat servers.
</para>
</listitem>
<listitem>
@@ -991,12 +991,12 @@
</listitem>
<listitem>
<para>
- Stop some of your JBoss Enterprise Application Platform/JBoss Web/Tomcat servers and/or undeploy the <filename>load-demo.war</filename> from some of the servers and see the effect this has on load balancing.
+ Stop some of your JBoss EWP/JBoss Web/Tomcat servers and/or undeploy the <filename>load-demo.war</filename> from some of the servers and see the effect this has on load balancing.
</para>
</listitem>
<listitem>
<para>
- Restart some of your JBoss Enterprise Application Platform/JBoss Web/Tomcat servers and/or re-deploy the <filename>load-demo.war</filename> to some of the servers and see the effect this has on load balancing.
+ Restart some of your JBoss EWP/JBoss Web/Tomcat servers and/or re-deploy the <filename>load-demo.war</filename> to some of the servers and see the effect this has on load balancing.
</para>
</listitem>
<listitem>
@@ -1113,7 +1113,7 @@
</listitem>
<listitem>
<para>
- If the JBoss Enterprise Application Platform/JBoss Web/Tomcat servers are running the HttpConnector as well as the AJP connector, you can specify the address and port on which a particular server's HttpConnector is listening. The standard port is 8080.
+ If the JBoss EWP/JBoss Web/Tomcat servers are running the HttpConnector as well as the AJP connector, you can specify the address and port on which a particular server's HttpConnector is listening. The standard port is 8080.
</para>
</listitem>
</orderedlist>
Modified: projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Revision_History.xml 2010-03-02 06:17:02 UTC (rev 101700)
+++ projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/Revision_History.xml 2010-03-02 06:21:05 UTC (rev 101701)
@@ -6,8 +6,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>2.3</revnumber>
- <date>Mon 15 Feb 2010</date>
+ <revnumber>0.1</revnumber>
+ <date>Tue 02 Mar 2010</date>
<author>
<firstname>Gary</firstname>
<surname>Meintjes</surname>
@@ -15,7 +15,7 @@
</author>
<revdescription>
<simplelist>
- <member>Final document.</member>
+ <member>Conversion first pass.</member>
</simplelist>
</revdescription>
</revision>
Modified: projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent
===================================================================
--- projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent 2010-03-02 06:17:02 UTC (rev 101700)
+++ projects/docs/enterprise/EWP_5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent 2010-03-02 06:21:05 UTC (rev 101701)
@@ -1,4 +1,4 @@
-<!ENTITY PRODUCT "JBoss Enterprise Application Platform">
+<!ENTITY PRODUCT "JBoss Enterprise Web Platform">
<!ENTITY BOOKID "mod_cluster_User_Guide">
<!ENTITY YEAR "2010">
<!ENTITY HOLDER "Red Hat, Inc">
More information about the jboss-cvs-commits
mailing list