[jboss-cvs] JBossAS SVN: r105702 - projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Jun 4 02:03:12 EDT 2010
Author: misty at redhat.com
Date: 2010-06-04 02:03:11 -0400 (Fri, 04 Jun 2010)
New Revision: 105702
Modified:
projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Getting_Started.xml
projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
Log:
JBPAPP-3820
Modified: projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Getting_Started.xml 2010-06-04 05:54:36 UTC (rev 105701)
+++ projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Getting_Started.xml 2010-06-04 06:03:11 UTC (rev 105702)
@@ -7,14 +7,14 @@
<section id="Getting_Started-Pre_Requisites">
<title>Pre-Requisites</title>
<para>
- You must have adequate disk space<!--TODO how much --> to install JDK and JBoss Enterprise Web Platform (JBoss EWP) while also allowing enough space for your applications. Before installing JBoss EWP you must have a working installation of Java and a C runtime. The JBoss EWP 5 includes offerings of JBoss Native and mod_jk which require a C runtime to be installed. <!--Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. However there are a few Operating System-specific issues that you must be aware of. Refer to <ulink url="http://www.jboss.org/community/wiki/JBossOperatingSystemSpecificIssues"></ulink> for more information.-->
+ You must have adequate disk space<!--TODO how much --> to install JDK and JBoss Enterprise Web Platform while also allowing enough space for your applications. Before installing JBoss Enterprise Web Platform you must have a working installation of Java and a C runtime. The JBoss Enterprise Web Platform 5 includes offerings of JBoss Native and mod_jk which require a C runtime to be installed. <!--Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. However there are a few Operating System-specific issues that you must be aware of.--> Refer to <ulink url="http://www.jboss.org/community/wiki/JBossOperatingSystemSpecificIssues"></ulink> for more information.
</para>
<section id="Pre_Requisites-Hardware_and_Operating_System_Requirements">
<title>Hardware, Operating System, and JVM Requirements</title>
<formalpara>
<title>Hardware Requirements</title>
<para>
- The following table details the minimum hardware requirements for a basic JBoss EWP installation that allows for all examples to be run correctly.
+ The following table details the minimum hardware requirements for a basic JBoss Enterprise Web Platform installation that allows for all examples to be run correctly.
</para>
</formalpara>
<table>
@@ -46,7 +46,7 @@
<!-- <formalpara>
<title>Minimum Hardware Requirements</title>
<para>
- Detailed in this section are the minimum hardware requirements in reguards to a server using the <classname>production</classname> configuration shipped with the JBoss EWP.
+ Detailed in this section are the minimum hardware requirements in reguards to a server using the <classname>production</classname> configuration shipped with the JBoss Enterprise Application Platform.
</para>
</formalpara>
<itemizedlist>
@@ -95,7 +95,7 @@
</listitem>
<!-- <listitem>
<para>
- Microsoft® Windows Vista™ Ultimate (32-bit systems and 64-bit systems)
+ Microsoft® Windows Vista™ Ultimate (32-bit systems 64-bit systems)
</para>
</listitem> -->
<listitem>
@@ -341,7 +341,7 @@
<section id="Pre_Requisites-Configuring_Your_Java_Environment">
<title>Configuring Your Java Environment</title>
<para>
- Enterprise Application Platform 5 requires Java SE 6. You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install JBoss EWP. You can install the 32-bit or 64-bit JVM as per your requirements.
+ Enterprise Web Platform 5 requires Java SE 6. You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install JBoss EWP. You can install the 32-bit or 64-bit JVM as per your requirements.
</para>
<itemizedlist id="Configuring_Your_Java_Environment-Benefits_of_64_bit_JVM_on_64_bit_OS_and_Hardware">
<title>Benefits of 64-bit JVM on 64-bit OS and Hardware:</title>
Modified: projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2010-06-04 05:54:36 UTC (rev 105701)
+++ projects/docs/enterprise/EWP/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2010-06-04 06:03:11 UTC (rev 105702)
@@ -4,69 +4,45 @@
<chapter id="Test_your_Installation">
<title>Test your Installation</title>
+ <!-- *|*|*| = Leaving these remarks in as they relate to a reviewed update performed on 26/02/10. i.e. "Waveriders" note this is current (as at Feb 10) material.
+ <remark>Change here: referred only to JBOSS_HOME. Removed reference to JBOSS_DIST/jboss-as/bin</remark>
+ -->
<para>
After you have installed the JBoss Enterprise Web Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> environment variable as explained in <xref linkend="Post_Installation_Configuration"/>. To test your installation, move to <filename>$JBOSS_HOME/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
</para>
-<!-- <programlisting>
-[vrenish at vinux bin]$ ./run.sh
-=====================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /home/<username>/jboss-ewp-5.0/jboss-as
-
- JAVA: /usr/java/jdk1.6.0_15/bin/java
-
- JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.cli ent.gcInterval=3600000
- -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.prefer IPv4Stack=true
-
-CLASSPATH: /home/<username>/jboss-ewp-5.0/jboss-as/bin/run.jar:/u sr/java/jdk1.6.0_15/lib/tools.jar
-
-=====================================================
-
-18:45:49,550 INFO [Server] Starting JBoss (MX MicroKernel)...
-.
-.
-.
-.
-18:45:50,449 INFO [ServerInfo] Java version: 1.6.0_15,Sun Microsystems Inc.
-18:45:50,449 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03 ,Sun Microsystems Inc.
-18:45:50,449 INFO [ServerInfo] OS-System: Linux 2.6.9-42.0.3.EL,i386
-18:45:51,824 INFO [Server] Core system initialized
-18:45:59,622 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 /
-18:45:59,659 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml
-</programlisting> -->
-
+ <!-- This output is somewhat mocked up to be a little less version-specific -->
<programlisting>
-[<username>@machine jboss-as-web]$ ./bin/run.sh
-=========================================================================
+ [user at host JBOSS_HOME]$ ./run.sh
+ =========================================================================
JBoss Bootstrap Environment
- JBOSS_HOME: /home/<username>/dist/ewp/jboss-ewp-5.0/jboss-as-web
+ JBOSS_HOME: <replaceable>$JBOSS_HOME</replaceable>/jboss-as-web
- JAVA: /usr/java/jdk1.6.0_17/bin/java
+ JAVA: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64//bin/java
- JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true
--Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
--Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true
+ JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true
- CLASSPATH: /home/<username>/dist/ewp/jboss-ewp-5.0/jboss-as-web/bin/run.jar:/usr/java/jdk1.6.0_17/lib/tools.jar
+ CLASSPATH: <replaceable>$JBOSS_HOME</replaceable>/jboss-as-web/bin/run.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64//lib/tools.jar
-=========================================================================
+ =========================================================================
-14:57:53,572 INFO [ServerImpl] Starting JBoss (Microcontainer)...
-.
-.
-.
-14:57:56,663 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.
-14:57:56,663 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
-14:57:56,663 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 14.3-b01,Sun Microsystems Inc.
-14:57:56,663 INFO [ServerInfo] OS-System: Linux 2.6.30.10-105.2.23.fc11.x86_64,amd64
-14:57:56,663 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms1303m -Xmx1303m -XX:MaxPermSize=256m ...
-14:57:56,692 INFO [JMXKernel] Legacy JMX core initialized
-</programlisting>
+ 15:46:24,061 INFO [ServerImpl] Starting JBoss (Microcontainer)...
+... (Other initialization messages) ...
+ 15:46:55,714 INFO [ServerImpl] JBoss (Microcontainer) Started in 31s:649ms
+</programlisting>
+
+<formalpara><title>APR Message</title>
+ <para>
+ When using the JBoss Native zip installation, install apr and apr-util as discussed in <xref linkend="sect-Installation_With_Zip_Download-JBoss_Native_Installation"/> if the following message is displayed when starting the server:
+ <programlisting>WARN [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/user/installLocation/jboss-eap-5.0/native/lib.
+ </programlisting>
+ </para>
+</formalpara>
+<!-- *|*|*|
+ <remark>... to here */</remark>
+-->
<note>
<para>
There is no <emphasis>Server Started</emphasis> message shown at the console when the server is started using the <literal>production</literal> profile. This message can be observed in the <filename>server.log</filename> file located in the <filename>server/production/log</filename> subdirectory.
@@ -76,8 +52,13 @@
</para>
</note>
<para>
- Now open <literal>http://localhost:8080</literal> in your web browser. (Make sure you dont have anything else already on your machine using that port).<footnote><para>
- Note that on some machines, the name localhost won’t resolve properly and you should use the local loopback address 127.0.0.1 instead.</para></footnote> The contents of your page should look similar to this: <xref linkend="Test_your_Installation-Test_your_Installation" />.
+ Now open <literal>http://localhost:8080</literal> in your web browser. (Ensure that the port is not already in use.)
+ <footnote>
+ <para>
+ Note that on some machines, the name localhost won’t resolve properly and you should use the local loopback address 127.0.0.1 instead.
+ </para>
+ </footnote> <!-- Commented out because the screenshot is out of date and unnecessary
+ The contents of your page should look similar to this: <xref linkend="Test_your_Installation-Test_your_Installation" />.
</para>
<para>
<figure id="Test_your_Installation-Test_your_Installation">
@@ -87,9 +68,33 @@
<imagedata align="center" fileref="images/test_install.png" />
</imageobject>
</mediaobject>
- </figure>
+ </figure>-->
</para>
+ <!-- *|*|*|
+ <remark>/* Added from here ... JBPAPP-3280</remark>
+ -->
<para>
+ Clicking on the <guilabel>Admin 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 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).
+INFO [PluginContainerResourceManager] Discovering Resources...
+WARN [JMXDiscoveryComponent] Unable to complete base jmx server discovery (enable DEBUG for stack): java.lang.UnsupportedOperationException: No native library available - Cannot get the process table information without native support
+ </programlisting>
+ </para>
+ </formalpara>
+ <para>
+ These warnings relate to the inability of <application>RHQ</application> to perform process table scans as <application>SIGAR</application>, which is used to monitor external processes, is not packaged with <application>RHQ</application>. These messages are returned due to the fact that <application>RHQ</application> is embedded in the administration console. The messages can therefore be ignored as external process monitoring is not a function performed by the administration console.
+ </para>
+ <!-- *|*|*|
+ <remark>...to here */</remark>
+ -->
+ <para>
You are now ready to use the JBoss Enterprise Web Platform. Refer to the Getting Started Guide for more information about the platform layout and example applications showcasing JBoss in action.
</para>
+
+
</chapter>
+
More information about the jboss-cvs-commits
mailing list