[jboss-cvs] JBossAS SVN: r100954 - projects/docs/enterprise/5.0/mod_cluster/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 15 02:39:52 EST 2010
Author: laubai
Date: 2010-02-15 02:39:52 -0500 (Mon, 15 Feb 2010)
New Revision: 100954
Added:
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.xml
Removed:
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
Modified:
projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
Log:
Corrected acronym use and standardised JBoss Web references.
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml 2010-02-15 07:27:32 UTC (rev 100953)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml 2010-02-15 07:39:52 UTC (rev 100954)
@@ -516,7 +516,7 @@
<classname>JVMRoute</classname>
</entry>
<entry>
- In fact <application>JBossWEB</application> via the <classname>JVMRoute</classname> in the Engine will add it
+ In fact <application>JBoss Web</application> via the <classname>JVMRoute</classname> in the Engine will add it
</entry>
</row>
<row>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-02-15 07:27:32 UTC (rev 100953)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-02-15 07:39:52 UTC (rev 100954)
@@ -91,7 +91,7 @@
</listitem>
<listitem>
<para>
- <application>JBoss EAP 5.0+</application>
+ <application>JBoss Enterprise Application 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 EAP, refer to the relavant chapter in this publication.
+ To configure for JBoss Enterprise Application Platform, 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 EAP 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 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.
</para>
</section>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-02-15 07:27:32 UTC (rev 100953)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-02-15 07:39:52 UTC (rev 100954)
@@ -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 EAP</application>, <application>JBossWeb</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 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.
</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 EAP is used and the <literal>-u</literal> startup switch is included in the EAP 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 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.
</para>
</listitem>
</varlistentry>
@@ -430,7 +430,7 @@
<formalpara>
<title>mod_proxy configuration</title>
<para>
- mod_proxy directives, such as <command>ProxyIOBufferSize</command>, could be used to configure mod_cluster. There is no need to use <command>ProxyPass</command> directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB.
+ mod_proxy directives, such as <command>ProxyIOBufferSize</command>, could be used to configure mod_cluster. There is no need to use <command>ProxyPass</command> directives because mod_cluster automatically configures which URLs have to be forwarded to JBoss Web.
</para>
</formalpara>
@@ -572,7 +572,7 @@
<term>ManagerBalancerName</term>
<listitem>
<para>
- <filename>ManagerBalancerName</filename> is the name of balancer to use when the JBoss AEP/JBossWeb/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 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>
</para>
</listitem>
</varlistentry>
@@ -643,7 +643,7 @@
<term>ServerAdvertise On</term>
<listitem>
<para>
- Use the advertise mechanism to tell the JBoss EAP/JBossWeb/Tomcat to whom it should send the cluster information.
+ Use the advertise mechanism to tell the JBoss Enterprise Application 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 EAP/JBossWeb/Tomcat configuration. Note that if JBoss EAP is used and the <literal>-u</literal> startup switch is included in the EAP 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 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.
</para>
</listitem>
</varlistentry>
@@ -683,7 +683,7 @@
<term>AdvertiseSecurityKey value</term>
<listitem>
<para>
- The key string to identify the mod_cluster in JBossWEB. Default: No default value. Information not sent.
+ The key string to identify the mod_cluster in JBoss Web. Default: No default value. Information not sent.
</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 EAP/JBossWeb/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 Application 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 EAP or JBossWeb/Tomcat.
+ The next step depends on whether your target server is JBoss Enterprise Application Platform 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 EAP 5.0</title>
+ <title>Installing in JBoss Enterprise Application Platform 5.0</title>
<para>
- Assume that <filename>$JBOSS_HOME </filename> indicates the root of your JBoss EAP 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 Enterprise Application Platform install and that you want to use mod_cluster in the <literal>production</literal> profile:
</para>
</formalpara>
@@ -729,32 +729,32 @@
<formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_Web_or_Tomcat">
<title>Installing in JBoss Web or Tomcat</title>
<para>
- Assume <filename>$CATALINA_HOME</filename> indicates the root of your JBossWeb or Tomcat install:
+ Assume <filename>$CATALINA_HOME</filename> indicates the root of your JBoss Web or Tomcat install:
</para>
</formalpara>
<programlisting>
-cp -r /tmp/mod-cluster/JBossWeb-Tomcat/lib/* $CATALINA_HOME/lib/
+cp -r /tmp/mod-cluster/JBoss Web-Tomcat/lib/* $CATALINA_HOME/lib/
</programlisting>
<!--<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 EAP 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 Enterprise Application Platform install and that you want to use mod_cluster in the <literal>production</literal> profile:
</para>
</formalpara>
<programlisting>
-cp -r /tmp/mod-cluster/JBossWeb-Tomcat/lib/mod-cluster.jar $JBOSS_HOME/server/all/deploy/jboss-web.deployer
+cp -r /tmp/mod-cluster/JBoss Web-Tomcat/lib/mod-cluster.jar $JBOSS_HOME/server/all/deploy/jboss-web.deployer
</programlisting> -->
</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Configuring_JBoss_AS_JBoss_Web_or_Tomcat">
- <title>Configuring JBoss EAP, JBoss Web or Tomcat</title>
+ <title>Configuring JBoss Enterprise Application Platform, 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>
<formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_JBoss_ASs_embedded_JBossWeb">
- <title>Integrate mod_cluster with JBoss AS's embedded JBossWeb</title>
+ <title>Integrate mod_cluster with JBoss AS's embedded JBoss Web</title>
<para>
Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the <literal>production</literal> profile:
<orderedlist>
@@ -781,7 +781,7 @@
</para>
</formalpara>
<formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_standalone_JBossWeb_or_Tomcat">
- <title>Integrate mod_cluster with standalone JBossWeb or Tomcat</title>
+ <title>Integrate mod_cluster with standalone JBoss Web or Tomcat</title>
<para>
Edit the <filename>$CATALINA_HOME/conf/server.xml</filename> file, adding the following next to the other <application>LifecycleListener</application> elements:
</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 EAP</title>
+ <title>Starting JBoss Enterprise Application Platform</title>
<para>
- To start <application>JBoss EAP</application> enter the following:
+ To start <application>JBoss Enterprise Application Platform</application> enter the following:
</para>
</formalpara>
@@ -842,9 +842,9 @@
./run.sh -c prodution
</programlisting>
<formalpara id="form-mod_cluster-Start_the_back_end_server-Starting_JBossWeb_or_Tomcat">
- <title>Starting JBossWeb or Tomcat</title>
+ <title>Starting JBoss Web or Tomcat</title>
<para>
- To start <application>JBossWEB</application> or <application>Tomcat</application> enter the following:
+ To start <application>JBoss Web</application> or <application>Tomcat</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 JBossWeb/Tomcat/JBoss EAP. 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 Enterprise Application Platform. The <filename>war</filename> includes a number of servlets:
<itemizedlist>
<listitem>
<para>
@@ -906,7 +906,7 @@
<note>
<para>
- The demo application does not actually depend on mod_cluster in any way. Its only dependency is on JBossWeb/Tomcat. The demo could therefore be used to demonstrate the effect of different server-side scenarios on the routing decisions made by any load balancer, including mod_jk, mod_proxy or the various hardware load balancers.
+ The demo application does not actually depend on mod_cluster in any way. Its only dependency is on JBoss Web/Tomcat. The demo could therefore be used to demonstrate the effect of different server-side scenarios on the routing decisions made by any load balancer, including mod_jk, mod_proxy or the various hardware load balancers.
</para>
</note>
<note>
@@ -934,17 +934,17 @@
</listitem>
<listitem>
<para>
- Install mod_cluster into your JBossEAP/JBossWeb/Tomcat servers as described at Installation on the Java side.
+ Install mod_cluster into your JBoss Enterprise Application Platform/JBoss Web/Tomcat servers as described at Installation on the Java side.
</para>
</listitem>
<listitem>
<para>
- Start httpd and your JBossEAP/JBossWeb/Tomcat servers.
+ Start httpd and your JBoss Enterprise Application Platform/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 JBossEAP/JBossWeb/Tomcat servers.
+ 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.
</para>
</listitem>
<listitem>
@@ -981,22 +981,22 @@
</listitem>
<listitem>
<para>
- Switch to the Request Balancing tab to see how many requests are going to each of your JBoss EAP/JBossWeb/Tomcat servers.
+ 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.
</para>
</listitem>
<listitem>
<para>
- Switch to the "Session Balancing" tab to see how many active <literal>sessions</literal> are being hosted by each of your JBossEAP/JBossWeb/Tomcat servers.
+ Switch to the "Session Balancing" tab to see how many active <literal>sessions</literal> are being hosted by each of your JBossEnterprise Application Platform/JBoss Web/Tomcat servers.
</para>
</listitem>
<listitem>
<para>
- Stop some of your JBoss EAP/JBossWeb/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 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.
</para>
</listitem>
<listitem>
<para>
- Restart some of your JBoss EAP/JBossWeb/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 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.
</para>
</listitem>
<listitem>
@@ -1113,7 +1113,7 @@
</listitem>
<listitem>
<para>
- If the JBoss EAP/JBossWeb/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 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.
</para>
</listitem>
</orderedlist>
Deleted: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent 2010-02-15 07:27:32 UTC (rev 100953)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent 2010-02-15 07:39:52 UTC (rev 100954)
@@ -1,4 +0,0 @@
-<!ENTITY PRODUCT "Documentation">
-<!ENTITY BOOKID "mod_cluster">
-<!ENTITY YEAR "2009">
-<!ENTITY HOLDER "Red Hat Inc.">
Deleted: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml 2010-02-15 07:27:32 UTC (rev 100953)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml 2010-02-15 07:39:52 UTC (rev 100954)
@@ -1,15 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-<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="Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
- <xi:include href="Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="QuickStartGuide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="MigratingFromModJK.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ConfigurationForJBossAS.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
-</book>
-
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.ent 2010-02-15 07:39:52 UTC (rev 100954)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss Enterprise Application Platform">
+<!ENTITY BOOKID "mod_cluster_User_Guide">
+<!ENTITY YEAR "2010">
+<!ENTITY HOLDER "Red Hat, Inc">
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster_User_Guide.xml 2010-02-15 07:39:52 UTC (rev 100954)
@@ -0,0 +1,15 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<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="Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+ <xi:include href="Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="QuickStartGuide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="MigratingFromModJK.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ConfigurationForJBossAS.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <index />
+</book>
+
More information about the jboss-cvs-commits
mailing list