[jboss-svn-commits] JBoss Portal SVN: r5408 - docs/branches/JBoss_Portal_Branch_2_4/referenceGuide/en/modules

[jboss-svn-commits at lists.jboss.org]

Author: sohil.shah at jboss.com
Date: 2006-10-10 16:41:20 -0400 (Tue, 10 Oct 2006)
New Revision: 5408

Modified:
   docs/branches/JBoss_Portal_Branch_2_4/referenceGuide/en/modules/clustering.xml
Log:


Modified: docs/branches/JBoss_Portal_Branch_2_4/referenceGuide/en/modules/clustering.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_4/referenceGuide/en/modules/clustering.xml	2006-10-10 19:09:24 UTC (rev 5407)
+++ docs/branches/JBoss_Portal_Branch_2_4/referenceGuide/en/modules/clustering.xml	2006-10-10 20:41:20 UTC (rev 5408)
@@ -236,6 +236,63 @@
       into <emphasis>$JBOSS_HOME/server/ports-01/all</emphasis> and <emphasis>$JBOSS_HOME/server/ports-02/all</emphasis>.
       </para>
       <para>Copy JBoss Portal HA to the deploy directory of the two configurations.</para>
+      
+      <!--  adding instruction about jboss cache versioning -->
+      <para>
+      	<emphasis>JBoss Cache Configuration Note :</emphasis> To improve CMS performance JBoss Cache is leveraged to cache the content cluster wide.
+      	We recommend that you use the following version of JBoss Cache for best performance:
+      	<itemizedlist>
+            <listitem><emphasis>JBoss Cache 1.4.0.SP1 and above</emphasis></listitem>
+            <listitem><emphasis>JGroups 2.2.7 or 2.2.8</emphasis></listitem>            
+         </itemizedlist> 
+         When building from source the following command: {core}/build.xml deploy-ha automatically upgrades your JBoss
+         Cache version.     	
+      </para>
+      <para>
+      	<emphasis>Alternative: </emphasis> If upgrading your JBoss Cache version is not an option, the following configuration
+      	change is needed in the jboss-portal-ha.sar/portal-cms.sar/META-INF/jboss-service.xml.
+      	Replace the following configuration in the <emphasis>cms.pm.cache:service=TreeCache</emphasis> Mbean:
+      	<programlisting><![CDATA[
+		  <!--
+           		Configuring the PortalCMSCacheLoader
+           		
+           		CacheLoader configuration for 1.4.0
+           -->           
+           <attribute name="CacheLoaderConfiguration">
+               <config>                
+                   <passivation>false</passivation>
+                   <preload></preload>
+                   <shared>false</shared>
+                   <cacheloader>
+                       <class>org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader</class>
+                       <properties></properties>
+                       <async>false</async>
+                       <fetchPersistentState>false</fetchPersistentState>
+                       <ignoreModifications>false</ignoreModifications>
+                   </cacheloader>
+               </config>
+           </attribute>
+		]]>
+	  </programlisting>
+      with the following configuration:
+      <programlisting><![CDATA[
+		  <!--
+           		Configuring the PortalCMSCacheLoader
+           		
+           		CacheLoader configuratoon for 1.2.4SP2
+           --> 
+           <attribute name="CacheLoaderClass">org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader</attribute>       
+           <attribute name="CacheLoaderConfig" replace="false"></attribute>
+           <attribute name="CacheLoaderPassivation">false</attribute>
+           <attribute name="CacheLoaderPreload"></attribute>
+           <attribute name="CacheLoaderShared">false</attribute>           
+           <attribute name="CacheLoaderFetchTransientState">false</attribute>
+           <attribute name="CacheLoaderFetchPersistentState">false</attribute>
+           <attribute name="CacheLoaderAsynchronous">false</attribute>        
+	]]></programlisting>
+      
+      </para>
+      
       <para>Finally we can start both servers, open two shells and execute :
          <programlisting><![CDATA[
 >cd $JBOSS_HOME/bin
@@ -246,6 +303,8 @@
 >./run.sh -c ports-02
 ]]></programlisting>
       </para>
+            
+      
    </sect1>
 
    <sect1 id="portlet_session_replication">