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

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

Author: benlc
Date: 2010-02-25 23:27:57 -0500 (Thu, 25 Feb 2010)
New Revision: 101514

Modified:
   projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
   projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml
   projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml
Log:
'minor changes'


Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml	2010-02-26 04:27:25 UTC (rev 101513)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml	2010-02-26 04:27:57 UTC (rev 101514)
@@ -36,13 +36,13 @@
 					<para>
 						You should now have a directory called <filename>jboss-eap-<replaceable>&lt;release&gt;</replaceable></filename>. Refer to <xref linkend="sect-Installation_With_Zip_Download-JBoss_Native_Installation"/> for information regarding the installation of the JBoss Native package.
 					</para>	
-				<note><title>Platform Directory Structure</title>
-				  <para>		 
-			        Refer to the Getting Started Guide to understand and explore the Platform Directory Structure.
-				  </para>
-				</note>
 				</listitem>
 			</itemizedlist>
+			<note><title>Platform Directory Structure</title>
+		      <para>		 
+			    Refer to the Getting Started Guide to understand and explore the Platform Directory Structure.
+			  </para>
+			</note>
 			<important>
 				<para>
 					On Windows Server 2008 when installing the JBoss Enterprise Application Platform service, open Windows Explorer and right click on <filename>C:\Windows\System32\cmd.exe</filename> and select <guimenuitem>Run As Administrator</guimenuitem>. Then change directory to the root of your installation directory (<filename>%JBOSS_HOME%\bin</filename>) and install the service using the command:

Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml	2010-02-26 04:27:25 UTC (rev 101513)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml	2010-02-26 04:27:57 UTC (rev 101514)
@@ -110,21 +110,18 @@
 				<filename>$JBOSS_HOME/server/$CONFIG/conf/props/jmx-console-users.properties</filename>
 			</para>
 		</formalpara>
-		<para>
-		  Change the # admin=JBossAdmin,HttpInvoker to user=JBossAdmin,HttpInvoker
-		</para>
 		<formalpara>
 			<title>Set up Accounts for <literal>web-console</literal> users by modifying:</title>
 			<para>
 				<filename>$JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties</filename>, where <literal>$JBOSS_HOME</literal> is the install directory and the <literal>$CONFIG</literal> is the server configuration being used.
 			</para>
 		</formalpara>
+		-->
 		<important>
 			<para>
 				Login credentials for the <literal>admin-console</literal> are the same as those used for the JMX console.
 			</para>
 		</important>
-		-->
 		<!-- *|*|*|
 		  <remark>SuckerPassword changed to suckerPassword</remark>
 		-->
@@ -134,12 +131,10 @@
 				JBoss Messaging makes internal connections between nodes in order to redistribute messages between clustered destinations. These connections are made with the user name of a special reserved user whose password is specified by this parameter <literal>suckerPassword</literal> in the configuration file:
 		    </para>
 		    </formalpara>
-				<programlisting>
-				<!-- *|*|*|
-				  <remark>changed the path here "deploy" was not included</remark>
-				-->
-					$JBOSS_HOME/server/$CONFIG/deploy/messaging/messaging-jboss-beans.xml
-				</programlisting>
+		    <!-- *|*|*|
+			  <remark>changed the path here "deploy" was not included</remark>
+			-->
+				<programlisting>$JBOSS_HOME/server/$CONFIG/deploy/messaging/messaging-jboss-beans.xml</programlisting>
 				<!--  Where <literal>$JBOSS_HOME</literal> is the install directory and <literal>$CONFIG</literal> is the server configuration being used.
 				-->
 			<para>

Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml	2010-02-26 04:27:25 UTC (rev 101513)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml	2010-02-26 04:27:57 UTC (rev 101514)
@@ -85,7 +85,7 @@
 	<para>
 	  Clicking on the <guilabel>Administration Console</guilabel> link will redirect the user to a login page. Entering the username and password as configured in <xref linkend="Post-Installation"/> will result in the display of the administration console. If this is not the case, check that the server has been started in one of the <quote>out of the box</quote> supported configurations (see <xref linkend="migration.admin"/>) and that the user accounts have been correctly set up as per the instructions in <xref linkend="Post-Installation"/>.   
 	</para>
-	<formalpara><title>The Administration Console and SystemFactoryInfo Messages</title>
+	<formalpara><title>The Administration Console and SystemInfoFactory Messages</title>
   <para>
     When accessing the administration console, the following warnings may be displayed or logged:
    <programlisting>WARN [SystemInfoFactory] System info API not accessible on this platform (native shared library not found in java.library.path).