[jboss-cvs] JBossAS SVN: r93113 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.

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

Author: irooskov at redhat.com
Date: 2009-09-01 23:06:29 -0400 (Tue, 01 Sep 2009)
New Revision: 93113

Modified:
   projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml
Log:
updated through tech review


Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml	2009-09-02 02:49:53 UTC (rev 93112)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml	2009-09-02 03:06:29 UTC (rev 93113)
@@ -108,14 +108,14 @@
            involves a few simple steps:</para>
            
            <itemizedlist>
-           <listitem>
+		   <listitem id="clustering-prep-dualconfig">
 		   <para><emphasis role="bold">Install JBoss Enterprise Application Platform on all your servers.</emphasis> 
               In its simplest form, this is just a matter of unzipping the JBoss 
               download onto the filesystem on each server. <!-- See the 
               <emphasis>Administration and Configuration Guide</emphasis> for 
               full details.--></para>
               
-              <para id="clustering-prep-dualconfig">If you want to run multiple 
+              <para>If you want to run multiple 
 		      JBoss Enterprise Application Platform instances on a single server, you can either install the 
               full JBoss distribution onto multiple locations on your filesystem, 
               or you can simply make copies of the <literal>all</literal> 
@@ -157,8 +157,8 @@
               </note>
            </listitem>
            
-           <listitem> 
-              <para id="clustering-prep-serverpeerid"><emphasis role="bold">Determine a unique integer "ServerPeerID" for each
+	   <listitem id="clustering-prep-serverpeerid"> 
+              <para><emphasis role="bold">Determine a unique integer "ServerPeerID" for each
               node.</emphasis>  This is needed for JBoss Messaging clustering,
               and can be skipped if you will not be running JBoss Messaging 
               (i.e. you will remove JBM from your server 
@@ -219,7 +219,7 @@
            <para>Let's look at a few different scenarios for doing this. In each
            scenario we'll be creating a two node cluster, where the ServerPeerID
            for the first node is <literal>1</literal> and for the second node is
-	   <literal>2</literal> (see <xref linkend="clustering-prep-serverpeerid"/>). We've decided to call our cluster "DocsPartition"
+	   <literal>2</literal> <!--(see <xref linkend="clustering-prep-serverpeerid"/>)-->. We've decided to call our cluster "DocsPartition"
            and to use <literal>239.255.100.100</literal> as our multicast address. 
            These scenarios are meant to be illustrative; the use of a two node
            cluster shouldn't be taken to mean that is the best size for a cluster;
@@ -277,8 +277,8 @@
 	    each Enterprise Application Platform instance has its own work area. So, instead of using
             the <literal>all</literal> config, we are going to use the
             <literal>node1</literal> and <literal>node2</literal> configs we
-            copied from <literal>all</literal> in 
-            <xref linkend="clustering-prep-dualconfig"/><!--the previous section-->.</para>
+            copied from <literal>all</literal> earlier in <!--
+            <xref linkend="clustering-prep-dualconfig"/>-->the previous section.</para>
             
             <para>To launch the first instance, open a console window and:</para>
             <programlisting>