[jboss-cvs] JBossAS SVN: r59895 - branches/Branch_4_2/tomcat/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Jan 21 15:15:57 EST 2007
Author: dimitris at jboss.org
Date: 2007-01-21 15:15:57 -0500 (Sun, 21 Jan 2007)
New Revision: 59895
Modified:
branches/Branch_4_2/tomcat/docs/jboss-web-clustering.xml
Log:
tomcat -> JBossWeb
Modified: branches/Branch_4_2/tomcat/docs/jboss-web-clustering.xml
===================================================================
--- branches/Branch_4_2/tomcat/docs/jboss-web-clustering.xml 2007-01-21 20:12:52 UTC (rev 59894)
+++ branches/Branch_4_2/tomcat/docs/jboss-web-clustering.xml 2007-01-21 20:15:57 UTC (rev 59895)
@@ -295,7 +295,7 @@
<title id="s22">JBossCache level aspect</title>
<para>The main configuration file is
- <literal>tc5-cluster-service.xml</literal> of which is basically a
+ <literal>jboss-web-cluster-service.xml</literal> of which is basically a
minimum version of JBossCache configuration xml file (more details
later). <itemizedlist>
<listitem>
@@ -338,7 +338,7 @@
<para><literal>replication-type</literal> in
<literal>jboss-web.xml.</literal> User should directly configure
the replication type from
- <literal>tc5-cluster-service.xml</literal> with the element
+ <literal>jboss-web-cluster-service.xml</literal> with the element
<literal><literal>CacheMode</literal></literal>.</para>
</listitem>
@@ -357,15 +357,15 @@
<para>JBossCache can be configured through a xml configuration and
deployed under JBoss3.2.6 as a MBean service. Since JBossCache is used not
only for clustering but also for <literal>SSO</literal> (single sign on)
- replication as well, we have introduced a JBossCache tc5 clustering MBean
+ replication as well, we have introduced a JBossCache clustering MBean
service for everyone to share (such as <literal>SSO</literal>
replication). The xml configuration file will be called
- <literal>tc5-cluster-service.xml</literal>. Once the file is deployed, a
+ <literal>jboss-web-cluster-service.xml</literal>. Once the file is deployed, a
MBean called <literal>TomcatClusteringCache</literal> will be
created.</para>
<para>In the file, there are JBossCache configuration parameters but
- customized for the tc5 clustering. Here is a snippet of the xml:</para>
+ customized for the JBossWeb clustering. Here is a snippet of the xml:</para>
<programlisting><server>
<mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=TomcatClusteringCache">
@@ -424,7 +424,7 @@
for http session replication. User should refer to other documentation on
how to setup a front end load balancer (e.g., Apache mod_jk(2)).</para>
- <para>To run a web application session replication under the new tc5
+ <para>To run a web application session replication under the new JBossWeb
clustering, you will need to set the application to be distributable as
usual. For example, in <literal>web.xml</literal> (under the web app
<literal>WEB-INF</literal> directory), <programlisting><web-app>
@@ -446,8 +446,8 @@
<para>In addition, you will need to start jboss from
<literal>all</literal> configuration directory. Under the new
<literal>all</literal> configuration, it includes the JBossCache library
- and also the <literal>tc5-cluster-service.xml</literal>file to deploy the
- cache as a specific tc5 clustering MBean service.</para>
+ and also the <literal>jboss-web-cluster-service.xml</literal>file to deploy the
+ cache as a specific JBossWeb clustering MBean service.</para>
<para>Finally, before you start JBoss, you can edit
<literal>jboss-service.xml</literal> under
More information about the jboss-cvs-commits
mailing list