[jboss-cvs] jboss-portal-docs/referenceGuide/en/modules ...

[Rali Genova]

  User: rgenova 
  Date: 06/07/13 17:13:33

  Modified:    referenceGuide/en/modules  clustering.xml
  Log:
  updated mod_jk apache config link
  
  Revision  Changes    Path
  1.15      +14 -14    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.14
  retrieving revision 1.15
  diff -u -b -r1.14 -r1.15
  --- clustering.xml	13 Jul 2006 20:08:27 -0000	1.14
  +++ clustering.xml	13 Jul 2006 21:13:33 -0000	1.15
  @@ -112,8 +112,8 @@
            <title>Hibernate clustering</title>
            <para>JBoss Portal leverages hibernate for its database access. In order to improve performances it uses
            the caching features provided by hibernate. On a cluster the cache needs to be replicated in order
  -         to avoid state inconsistencies. Hibernate is configured with JBoss Cache which perform that synchronization transparently.
  -         Therefore the different hibernate services must be configured to use JBoss Cache, the following hibernate configurations
  +         to avoid state inconsistencies. Hibernate is configured with JBoss Cache which performs that synchronization transparently.
  +         Therefore the different hibernate services must be configured to use JBoss Cache. The following hibernate configurations
            needs to use a replicated JBoss Cache :
            <itemizedlist>
               <listitem><emphasis>jboss-portal.sar/conf/hibernate/user/hibernate.cfg.xml</emphasis></listitem>
  @@ -197,53 +197,53 @@
         <title>Setup</title>
         <para>We are going to outline how to setup a two node cluster on the same machine in order to test JBoss Portal HA. The only
         missing part from the full fledged setup is the addition of a load balancer in front of Tomcat. However a lot of documentation
  -      exist on the subject.</para>
  +      exist on the subject. A detailed step by step setup of Apache and mod_jk is available from the  <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss">JBoss Wiki</ulink>.</para>
         <para>As we need two application servers running at the same time, we must avoid any conflict. For instance we will
         need Tomcat to bind its socket on two different ports otherwise a network conflict will occur. We will leverage
         the service binding manager <ulink url="http://docs.jboss.org/jbossas/jboss4guide/r3/html/ch10.html">this chapter</ulink> of
         the JBoss AS documentation.</para>
         <para>The first step is to copy the <emphasis>all</emphasis> configuration of JBoss into two separate
  -      configuration that we name <emphasis>ports-01</emphasis> and <emphasis>ports-02</emphasis> :
  +      configurations that we name <emphasis>node-01</emphasis> and <emphasis>node-02</emphasis> :
            <programlisting><![CDATA[
   >cd $JBOSS_HOME/server
  ->cp -r all ports-01
  ->cp -r all ports-02
  +>cp -r all node-01
  +>cp -r all node-02
   ]]></programlisting>
         </para>
  -      <para>Edit the file <emphasis>$JBOSS_HOME/server/ports-01/conf/jboss-service.xml</emphasis> and uncomment
  +      <para>Edit the file <emphasis>$JBOSS_HOME/server/node-01/conf/jboss-service.xml</emphasis> and uncomment
         the service binding manager :
         <programlisting><![CDATA[
   <mbean code="org.jboss.services.binding.ServiceBindingManager"
      name="jboss.system:service=ServiceBindingManager">
  -   <attribute name="ServerName">ports-01</attribute>
  +   <attribute name="ServerName">node-01</attribute>
      <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute>
      <attribute name="StoreFactoryClassName">org.jboss.services.binding.XMLServicesStoreFactory</attribute>
   </mbean>
   ]]></programlisting>
         </para>
  -      <para>Edit the file <emphasis>$JBOSS_HOME/server/ports-02/conf/jboss-service.xml</emphasis>, uncomment
  -         the service binding manager and change the value <emphasis>ports-01</emphasis> into <emphasis>ports-02</emphasis>:
  +      <para>Edit the file <emphasis>$JBOSS_HOME/server/node-02/conf/jboss-service.xml</emphasis>, uncomment
  +         the service binding manager and change the value <emphasis>ports-01</emphasis> into <emphasis>node-02</emphasis>:
            <programlisting><![CDATA[
   <mbean code="org.jboss.services.binding.ServiceBindingManager"
      name="jboss.system:service=ServiceBindingManager">
  -   <attribute name="ServerName">ports-02</attribute>
  +   <attribute name="ServerName">node-02</attribute>
      <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute>
      <attribute name="StoreFactoryClassName">org.jboss.services.binding.XMLServicesStoreFactory</attribute>
   </mbean>]]></programlisting>
         </para>
         <para>Setup a database that will be shared by the two nodes and obviously we cannot use
         an embedded database. For instance using postgresql we would copy the file <emphasis>portal-postgresql-ds.xml</emphasis>
  -      into <emphasis>$JBOSS_HOME/server/ports-01/default</emphasis> and <emphasis>$JBOSS_HOME/server/ports-02/default</emphasis>.
  +      into <emphasis>$JBOSS_HOME/server/node-01/default</emphasis> and <emphasis>$JBOSS_HOME/server/node-02/default</emphasis>.
         </para>
         <para>Copy JBoss Portal HA to the deploy directory of the two configurations.</para>
         <para>Finally we can start both servers, open two shells and execute :
            <programlisting><![CDATA[
   >cd $JBOSS_HOME/bin
  ->./run.sh -c ports-01
  +>./run.sh -c node-01
   ]]></programlisting>
            <programlisting><![CDATA[
   >cd $JBOSS_HOME/bin
  ->./run.sh -c ports-02
  +>./run.sh -c node-02
   ]]></programlisting>
         </para>
      </sect1>