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

[Julien Viet]

  User: julien  
  Date: 06/07/13 16:08:27

  Modified:    referenceGuide/en/modules  clustering.xml
  Log:
  added clustering 2 nodes on same machine in the chapter
  
  Revision  Changes    Path
  1.14      +58 -5     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.13
  retrieving revision 1.14
  diff -u -b -r1.13 -r1.14
  --- clustering.xml	13 Jul 2006 18:08:46 -0000	1.13
  +++ clustering.xml	13 Jul 2006 20:08:27 -0000	1.14
  @@ -22,9 +22,7 @@
            <itemizedlist>
               <listitem>
                  <para>
  -                  <emphasis role="bold">
  -                     JBoss Cache:
  -                  </emphasis>
  +                  <emphasis role="bold">JBoss Cache:</emphasis>
                     Used to replicate data among the different hibernate session factories that are deployed in
                     each node of the cluster.
                  </para>
  @@ -170,7 +168,7 @@
            is authenticated on one particular node he will have to reauthenticate again if he use another node of the cluster (during
            a failover for instance). This is valid only for the <emphasis>FORM</emphasis> based authentication which is the default
            form of authentication that JBoss Portal uses. Fortunately JBoss provides transparent reauthentication of the user called
  -         JBoss clustered SSO. Its configuration is in the file <emphasis>JBOSS_HOME/server/all/deploy/jbossweb-tomcat55.sar/server.xml</emphasis>
  +         JBoss clustered SSO. Its configuration is in the file <emphasis>$JBOSS_HOME/server/all/deploy/jbossweb-tomcat55.sar/server.xml</emphasis>
            and the clustered sso valve shall be uncommented
               <programlisting><![CDATA[
   <Valve className="org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn" />
  @@ -195,6 +193,61 @@
   
      </sect1>
   
  +   <sect1>
  +      <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>
  +      <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> :
  +         <programlisting><![CDATA[
  +>cd $JBOSS_HOME/server
  +>cp -r all ports-01
  +>cp -r all ports-02
  +]]></programlisting>
  +      </para>
  +      <para>Edit the file <emphasis>$JBOSS_HOME/server/ports-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="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>:
  +         <programlisting><![CDATA[
  +<mbean code="org.jboss.services.binding.ServiceBindingManager"
  +   name="jboss.system:service=ServiceBindingManager">
  +   <attribute name="ServerName">ports-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>.
  +      </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
  +]]></programlisting>
  +         <programlisting><![CDATA[
  +>cd $JBOSS_HOME/bin
  +>./run.sh -c ports-02
  +]]></programlisting>
  +      </para>
  +   </sect1>
  +
      <sect1 id="portlet_session_replication">
         <title>Portlet Session Replication</title>
         <para>Web containers offer the capability to replicate sessions of web applications. In the context of a portal using portlets the use case is different. The portal itself is a web application