[jboss-cvs] jboss-portal-docs/referenceGuide/en/modules ...
Julien Viet
julien at jboss.com
Thu Jul 13 14:08:46 EDT 2006
User: julien
Date: 06/07/13 14:08:46
Modified: referenceGuide/en/modules clustering.xml
Log:
- added cms clustering image
Revision Changes Path
1.13 +10 -7 jboss-portal-docs/referenceGuide/en/modules/clustering.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: clustering.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-portal-docs/referenceGuide/en/modules/clustering.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- clustering.xml 13 Jul 2006 17:13:47 -0000 1.12
+++ clustering.xml 13 Jul 2006 18:08:46 -0000 1.13
@@ -160,6 +160,7 @@
<depends optional-attribute-name="CacheName">portal:service=TreeCache,type=hibernate</depends>
</mbean>
]]></programlisting>
+ More information can be found <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate">here</ulink>.
</para>
</sect2>
@@ -174,20 +175,22 @@
<programlisting><![CDATA[
<Valve className="org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn" />
]]></programlisting>
+ More information can be found <ulink url="http://www.jboss.org/wiki/Wiki.jsp?page=SingleSignOn">here</ulink>.
</para>
</sect2>
<sect2>
- <title>HA Singleton</title>
- <anchor id="HASingleton"/>
- </sect2>
-
- <sect2>
<title>CMS clustering</title>
<para>The CMS backend storage relies on the Apache Jackrabbit project. Jackrabbit does not support clustering out of the box.
- So the portal runs it only on one node of the cluster using the <link linkend="HASingleton">HA Singleton</link> technology.
+ So the portal run the Jackrabbit servicey on one node of the cluster using the
+ <ulink url="http://www.onjava.com/pub/a/onjava/2003/08/20/jboss_clustering.html">HA-Singleton</ulink> technology.
The file <emphasis>jboss-portal.sar/portal-cms.sar/META-INF/jboss-service.xml</emphasis> contains the configuration. We will
- not reproduce it in this documentation as the changes are quite complex and numerous.</para>
+ not reproduce it in this documentation as the changes are quite complex and numerous. Access from all nodes of the cluster
+ is provided by a proxy bound in HA-JNDI. In order to avoid any bottleneck JBoss Cache is leveraged to cache CMS content cluster
+ wide.</para>
+ <imageobject>
+ <imagedata fileref="images/clustering/cms.png" format="png"/>
+ </imageobject>
</sect2>
</sect1>
More information about the jboss-cvs-commits
mailing list