[jboss-cvs] JBossAS SVN: r101505 - projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Thu Feb 25 19:56:46 EST 2010


Author: laubai
Date: 2010-02-25 19:56:46 -0500 (Thu, 25 Feb 2010)
New Revision: 101505

Modified:
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Deployment.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
Log:
Added EWP component image as per JBPAPP-3361.

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -9,7 +9,7 @@
 	The following diagram illustrates an overview of the JBoss Enterprise Web Platform and its components.
 	<inlinemediaobject>
 		<imageobject><!--image must be replaced by RT#59811: https://engineering.redhat.com/rt3/Ticket/Display.html?id=59811-->
-			<imagedata fileref="images/jboss-as-components.png"/>
+			<imagedata fileref="images/jboss-as-components-ewp.png"/>
 		</imageobject>
 	</inlinemediaobject>
 </para>

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -7,7 +7,7 @@
 	<subtitle>for JBoss Enterprise Web Platform 5.0</subtitle>	
 	<edition>1</edition>
 	<issuenum>1</issuenum>
-	<pubsnumber>1.8</pubsnumber>
+	<pubsnumber>1.9</pubsnumber>
 	<productname>JBoss Enterprise Web Platform</productname>
 	<productnumber>5.0</productnumber>
 <!--	<pubdate>, 2009</pubdate> -->

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -97,7 +97,7 @@
            <section id="clustering-blocks-jgroups-stdconfigs">
                 <title>Standard Protocol Stack Configurations</title>
                 <para>
-					  The standard protocol stack configurations that ship with Enterprise Web Platform 5 are described below. Note that not all of these are actually used; many are included as a convenience to users who may wish to alter the default server configuration profile. The configurations used in a pristine Enterprise Web Platform 5 <literal>all</literal> configuration are <literal>udp</literal>, <literal>jbm-control</literal> and <literal>jbm-data</literal>, with all clustering services other than JBoss Messaging using <literal>udp</literal>.
+					  The standard protocol stack configurations that ship with Enterprise Web Platform 5 are described below. Note that not all of these are actually used; many are included as a convenience to users who may wish to alter the default server configuration profile. The configuration used in a pristine Enterprise Web Platform 5 <literal>production</literal> configuration is <literal>udp</literal>.
 			          </para>
 				  <para>
 					  You can add a new stack configuration by adding a new <literal>stack</literal> element to the <filename>server/all/deploy/cluster/jgroups-channelfactory.sar/META-INF/jgroups-channelfactory-stacks.xml</filename> file. You can alter the behavior of an existing configuration by editing this file. Before doing this though, see the other standard configurations shipped with the Enterprise Web Platform to determine whether they will meet your requirements.
@@ -174,7 +174,7 @@
 	               <para>As the number of JGroups-based clustering services running in 
 		               the Enterprise Web Platform has risen over the years, the need to share the resources 
 		               (particularly sockets and threads) used by these channels became 
-		               a glaring problem. A pristine Enterprise Web Platform 5 <literal>all</literal>
+		               a glaring problem. A pristine Enterprise Web Platform 5 <literal>production</literal>
 		               configuration will connect four JGroups channels during startup, and a total of 
 		               seven or eight will be connected if distributable web applications, clustered EJB3 
 		               SFSBs and a clustered JPA or Hibernate second level cache are all used. 

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -32,14 +32,14 @@
 		On the same Enterprise Web Platform instance, different services 
     can create their own <classname>Channel</classname>. In a standard startup 
     of the Enterprise Web Platform 5 <literal>production</literal> configuration, 
-    two different services create a total of four different channels &#8212; 
-    JBoss Messaging creates two, and a core general purpose clustering service 
-    known as <classname>HAPartition</classname> creates two more. If you deploy clustered web applications 
+<!--    two different services create a total of four different channels &#8212; 
+    JBoss Messaging creates two, and--> a core general purpose clustering service 
+    known as <classname>HAPartition</classname> creates two channels. If you deploy clustered web applications 
     <!--clustered EJB3 SFSBs--> or a clustered JPA/Hibernate entity cache, additional 
     channels will be created. The channels the Enterprise Web Platform connects 
-    can be divided into three broad categories: a general purpose channel used 
-    by the <classname>HAPartition</classname> service, channels created by JBoss Cache for special 
-    purpose caching and cluster wide state replication, and two channels used by JBoss Messaging.
+    can be divided into two broad categories: a general purpose channel used 
+    by the <classname>HAPartition</classname> service, and channels created by JBoss Cache for special 
+    purpose caching and cluster wide state replication.
 	</para>
 	<para>
 		So, if you go to two Enterprise Web Platform 5 instances and execute <code>run -c production</code>, 

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Deployment.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Deployment.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Deployment.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -390,7 +390,7 @@
     </para>
     
     <para>
-      Farming is enabled by default in the <literal>all</literal> configuration in 
+      Farming is enabled by default in the <literal>production</literal> configuration in 
       JBoss Enterprise Web Platform and thus requires no manual setup. The required 
       <filename>farm-deployment-jboss-beans.xml</filename> and 
       <filename>timestamps-jboss-beans.xml</filename> configuration files are located 

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -16,7 +16,7 @@
         </listitem>
       </itemizedlist>
       <para>State replication is directly handled by JBoss. When you run JBoss 
-      in the <literal>all</literal> configuration, session state replication is 
+      in the <literal>production</literal> configuration, session state replication is 
       enabled by default. Just configure your web application as 
       <literal>&lt;distributable&gt;</literal> in its <filename>web.xml</filename> (see <xref linkend="clustering-http-state"/>), 
       deploy it, and its session state is automatically replicated across all 

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -19,7 +19,7 @@
       <para>
 	      The JBoss Enterprise Web Platform comes with clustering support out of 
 	      the box, as part of the <literal>production</literal> configuration. The
-	      <literal>all</literal> configuration includes support for the following:
+	      <literal>production</literal> configuration includes support for the following:
 	      
 	      <itemizedlist>
 	      
@@ -291,7 +291,7 @@
 	    each Enterprise Web Platform instance has its own work area. So, instead of using
             the <literal>production</literal> config, we are going to use the
             <literal>node1</literal> and <literal>node2</literal> configs we
-            copied from <literal>all</literal> in <!--
+            copied from <literal>production</literal> in <!--
             <xref linkend="clustering-prep-dualconfig"/>-->the previous section.</para>
             
             <para>To launch the first instance, open a console window and:</para>

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -1629,7 +1629,7 @@
         must also use different multicast ports.  Unfortunately, setting the 
         multicast ports is not as simple as <code>-g</code> and 
         <literal>-u</literal>. By default, a JBoss AS instance
-        running the <literal>all</literal> configuration will use up to two different instances of
+        running the <literal>production</literal> configuration will use up to two different instances of
         the JGroups UDP transport protocol, and will therefore open two
         multicast sockets. You can control the ports those sockets use
         by using system properties on the command line. For example,

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml	2010-02-26 00:53:18 UTC (rev 101504)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml	2010-02-26 00:56:46 UTC (rev 101505)
@@ -8,7 +8,7 @@
          <simpara>
                 <revhistory>
                         <revision>
-                                <revnumber>2.8</revnumber>
+                                <revnumber>2.9</revnumber>
                                 <date>Thu Feb 25 2010</date>
                                 <author>
                                         <firstname>Laura</firstname>




More information about the jboss-cvs-commits mailing list