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

[Rali Genova]

  User: rgenova 
  Date: 06/07/14 12:24:11

  Modified:    referenceGuide/en/modules  clustering.xml
  Log:
  updated clustering deploy dir from default to all in section 8.4
  
  Revision  Changes    Path
  1.16      +10 -10    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.15
  retrieving revision 1.16
  diff -u -b -r1.15 -r1.16
  --- clustering.xml	13 Jul 2006 21:13:33 -0000	1.15
  +++ clustering.xml	14 Jul 2006 16:24:10 -0000	1.16
  @@ -203,26 +203,26 @@
         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
  -      configurations that we name <emphasis>node-01</emphasis> and <emphasis>node-02</emphasis> :
  +      configurations that we name <emphasis>ports-01</emphasis> and <emphasis>ports-02</emphasis> :
            <programlisting><![CDATA[
   >cd $JBOSS_HOME/server
  ->cp -r all node-01
  ->cp -r all node-02
  +>cp -r all ports-01
  +>cp -r all ports-02
   ]]></programlisting>
         </para>
  -      <para>Edit the file <emphasis>$JBOSS_HOME/server/node-01/conf/jboss-service.xml</emphasis> and uncomment
  +      <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">node-01</attribute>
  +   <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/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>:
  +      <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">
  @@ -233,17 +233,17 @@
         </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/node-01/default</emphasis> and <emphasis>$JBOSS_HOME/server/node-02/default</emphasis>.
  +      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>
         <para>Finally we can start both servers, open two shells and execute :
            <programlisting><![CDATA[
   >cd $JBOSS_HOME/bin
  ->./run.sh -c node-01
  +>./run.sh -c ports-01
   ]]></programlisting>
            <programlisting><![CDATA[
   >cd $JBOSS_HOME/bin
  ->./run.sh -c node-02
  +>./run.sh -c ports-02
   ]]></programlisting>
         </para>
      </sect1>