Author: smumford Date: 2010-05-04 00:57:23 -0400 (Tue, 04 May 2010) New Revision: 2953 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml Log: JBEPP-274: Minor Edits. Added Hardware info from EAP 4.3.0CP07. Added DOC TODOs Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml 2010-05-04 03:27:34 UTC (rev 2952) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml 2010-05-04 04:57:23 UTC (rev 2953) @@ -21,12 +21,98 @@ </section> <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements"> <title>System Requirements</title> -<!-- - <para><remark>Add hardware requirements as per this section of this doc?</remark></para> - <para><ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_P... ---> - <para>For the latest information on supported Operating System / JVM combinations and supported Database platforms, please always refer to <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigura...;. + <note> + <title>DOC TODO:</title> + <para> + These requirements taken from the <ulink type="http" url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_P... 4.3.0CP07 Docs</ulink>. Are they appropriate? + </para> + </note> + <formalpara> + <title>Minimum Installation Requirements</title> + <para> + The minimum hardware required to support the installation of the JBoss Application Server is a 240MB hard disk drive. Additional space is required for the installation of the JDK upon which the the JBoss Application Server depends. The JDK installation size is currently up to 150MB. + </para> + </formalpara> + <formalpara> + <title>Minimum Operational Requirements</title> + <para> + The minimum hardware required to support an operational JBoss Application Server varies depending on the following: + </para> + </formalpara> + <itemizedlist> + <listitem> + <para> + The size and complexity of the applications being served; + </para> + </listitem> + <listitem> + <para> + The demand placed on the server by the number and frequency of client requests; + </para> + </listitem> + <listitem> + <para> + The server configuration including the selected log files, their designated size and general server tuning. + </para> + </listitem> + </itemizedlist> + <para> + The following discussion relates to the deployment of a simple application on a server experiencing minimal demand. In view of this, the absolute minimum requirements for an operational server are: </para> + <itemizedlist> + <listitem> + <para> + Disk Space: 1GB + </para> + <itemizedlist> + <listitem> + <para> + The default server log file storage configuration is 500MB. + </para> + </listitem> + <listitem> + <para> + The remaining 500MB is allocated to the server installation (240MB), the required JDK (150MB) and some additional space for applications (110MB). + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para> + CPU: Intel Pentium Processor @ 1GHz + </para> + <itemizedlist> + <listitem> + <para> + Core 2 Duo, Core 2 Quad and Intel Xeon chips will improve the performance of servers which experience high demand. + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para> + RAM: 128 MB + </para> + <itemizedlist> + <listitem> + <para> + RAM installations of 1GB or more will be required to run a server upon which small to medium applications are deployed. 4GB or more is preferable for larger applications or to run a GUI server interface. + </para> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + <important> + <para> + A server's performance must be viewed in light of the applications deployed on the server, the demand placed on the server by client requests and any post-installation server configuration or tuning. + </para> + </important> + <formalpara> + <title>Supported Installations</title> + <para> + For the latest information on supported Operating System / JVM combinations and supported Database platforms, please always refer to <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigura...;. + </para> + </formalpara> <para> The following is a list of certified operating systems and JVM version combinations: </para> @@ -55,7 +141,7 @@ <tbody> <row> <entry> - RHEL 5 x86 + &RHEL; 5 x86 </entry> <entry> Sun JVM 1.6 Update 15 @@ -63,7 +149,7 @@ </row> <row> <entry> - RHEL 5 x86 + &RHEL; 5 x86 </entry> <entry> OpenJDK 1.6.0-b09 @@ -71,7 +157,7 @@ </row> <row> <entry> - RHEL 5 x86 + &RHEL; 5 x86 </entry> <entry> IBM JDK 1.6.0 SR5 @@ -79,7 +165,7 @@ </row> <row> <entry> - RHEL 5 x86_64 + &RHEL; 5 x86_64 </entry> <entry> Sun JVM 1.6 Update 15 @@ -87,7 +173,7 @@ </row> <row> <entry> - RHEL 5 x86_64 + &RHEL; 5 x86_64 </entry> <entry> OpenJDK 1.6.0-b09 @@ -95,7 +181,7 @@ </row> <row> <entry> - RHEL 5 x86_64 + &RHEL; 5 x86_64 </entry> <entry> IBM JDK 1.6.0 SR5 @@ -326,13 +412,12 @@ Applications that run with more than 1.5GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM. </para> </listitem> - <listitem> - <para> - Applications that run on a 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than their 32-bit cousin. - </para> - </listitem> </itemizedlist> - + <note> + <para> + Applications that run on a 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than their 32-bit cousin. + </para> + </note> <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_using_RHN"> <title>Installing and Configuring JDK 6.0 using RHN</title> <listitem> @@ -340,7 +425,7 @@ Java SDKs are provided by the Red Hat Enterprise Linux 5 Base and Supplementary channels for your Linux variant and architecture. The available JDKs corresponding to each channel and architecture are listed below: </para> <variablelist> - <title>RHEL 5 Java SDKs</title> + <title>&RHEL; 5 Java SDKs</title> <varlistentry> <term> Channel: rhel-&lt;arch&gt;-server-5 @@ -441,11 +526,15 @@ <para> Download and install the appropriate <literal>-compat RPM</literal> from <literal>JPackage</literal> <ulink url="ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-f... here</ulink>. Please ensure you choose a matching version of the <literal>-compat</literal> package to the JDK you installed. </para> - <para><remark>Note to Reviewer</remark></para> + <note> + <title>DOC TODO:</title> <para> The latest JDK available from Sun's site is update 19. The jpackage site linked to above lists the latest <literal>-compat rpm</literal> at update 6 (java-1.6.0-sun-compat-1.6.0.06-1jpp.i586.rpm). So there is a conflict here as the downloaded package and the -compat rpm cannot be matched as stated above. </para> - <para><remark>End Note to Reviewer</remark></para> + <para> + QE NOTE: "Download and install the appropriate -compat RPM from JPackage here." Should we instruct users to install unsigned rpms? + </para> + </note> </listitem> <listitem> <para> @@ -511,9 +600,12 @@ </listitem> </itemizedlist> </para> - <para><remark>Note to Reviewer</remark></para> - <para>Better to use java-1.6.0-variant rather than java-1.6.0-sun as could be sun or openjdk. Also include openJDK download site info http://openjdk.java.net/install/ ?</para> - <para><remark>End Note to Reviewer</remark></para> + <note> + <title>DOC TODO:</title> + <para> + Better to use java-1.6.0-variant rather than java-1.6.0-sun as could be sun or openjdk. Also include openJDK download site info http://openjdk.java.net/install/ ? + </para> + </note> </listitem> <listitem> <para> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml 2010-05-04 03:27:34 UTC (rev 2952) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml 2010-05-04 04:57:23 UTC (rev 2953) @@ -11,7 +11,7 @@ <title>Downloading</title> <para> - The officially supported archives are available from the JBoss Customer Support Portal (CSP) located at <ulink url="https://support.redhat.com">https://support.redhat.com</ulink>. Platforms including in your Support subscription are listed in the <literal>Software</literal> section. + The officially supported versions are available from the JBoss Customer Support Portal (CSP) located at <ulink url="https://support.redhat.com/jbossnetwork/restricted/main.html&qu...;. Platforms including in your Support subscription are listed in the <literal>Software</literal> section. </para> </section> @@ -37,7 +37,7 @@ </itemizedlist> </para> <note> - <title>Note: server configurations</title> + <title>Server Configurations</title> <para> Six types of server configurations will be included in your installation: <literal>minimal</literal>, <literal>default</literal>, <literal>production</literal>, <literal>all</literal>, <literal>standard</literal> and <literal>web</literal>. The Getting Started Guide of &JBEAP; 5.0 explains in detail the different server configuration file sets. @@ -59,7 +59,7 @@ </listitem> <listitem> <para> - the <literal>default</literal> server configuration includes non-clustered Portal components. <!-- This archive (gatein.ear) is located in the <literal>deploy</literal> folder. --><remark>This is the server configuration that is started when no other configuration is specified</remark> + the <literal>default</literal> server configuration includes non-clustered Portal components. <!-- This archive (gatein.ear) is located in the <literal>deploy</literal> folder. --> This is the server configuration that is started when no other configuration is specified. </para> </listitem> <listitem> @@ -74,8 +74,7 @@ </listitem> </itemizedlist> </para> - <!--<para><remark>Added the note below to account for all gatein.ear archives.</remark></para>--> - <note><title>Note: gatein.ear archive</title> + <note><title>gatein.ear Archive</title> <para> The gatein.ear archive, which contains the Portal components, is located in the deploy folder of the <literal>default</literal>, <literal>all</literal> and <literal>production</literal> server configurations. </para> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml 2010-05-04 03:27:34 UTC (rev 2952) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml 2010-05-04 04:57:23 UTC (rev 2953) @@ -15,14 +15,17 @@ </title> <para> Create an environment variable that points to the installation directory (<filename>JBOSS_DIST/jboss-as</filename>) and call it <literal>JBOSS_HOME</literal>. Add <literal>$JBOSS_HOME/bin</literal> to the system path to be able to run the server from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. - <programlisting> + </para> + </formalpara> +<programlisting> #In this example /home/user/jboss-epp-5.0/jboss-as is the installation directory. export JBOSS_HOME=/home/user/jboss-epp-5.0/jboss-as export PATH=$PATH:$JBOSS_HOME/bin - </programlisting> +</programlisting> + <para> Set this variable for the user account(s) that will run the server. </para> - </formalpara> + <formalpara> <title> On Microsoft Windows @@ -62,9 +65,16 @@ Post Installation Security Configuration </title> <para> - When installed from the zip archive, authentication is required to access the majority of JBoss services, including administrative services. User accounts have not been set up to eliminate the possibility of default username/password based attacks. + When installed from the zip archive, authentication is required to access the majority of JBoss services, including administrative services. User accounts have not been set up to eliminate the possibility of default username/password based attacks. </para> - <important><title>Default admin user configuration</title> + <note> + <title>DOC TODO:</title> + <para> + Is this still the case in 5.0? It seems to have default accounts in place. + </para> + </note> + + <important><title>Default Admin User Configuration</title> <para> It is recommended that the admin=admin username and password configuration, which is commented out by default, not be used for a production server. The admin user is included as an example of the username/password definition format only. </para> @@ -122,24 +132,26 @@ </programlisting> </para> </formalpara> - <para><remark>Note to Reviewer</remark></para> - <para> - <filename>/server/$CONFIG/deploy/messaging/messaging-service.xml</filename> - </para> - <screen>&lt;!-- The password used by the message sucker connections to create connections. + <note> + <title>DOC TODO:</title> + <para> + <filename>/server/$CONFIG/deploy/messaging/messaging-service.xml</filename> + </para> +<screen>&lt;!-- The password used by the message sucker connections to create connections. THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM &lt;attribute name="SuckerPassword"&gt;&lt;/attribute&gt;</screen> - <para> - Question 1: Should this file also have the SuckerPassword set? - </para> - <para> - Question 2: Should I document this? - </para> - <para><remark>End Note to Reviewer</remark></para> + <para> + Question 1: Should this file also have the SuckerPassword set? + </para> + <para> + Question 2: Should I document this? + </para> + </note> </section> <section id="Disabling_Authentication"> <title>Disabling Authentication</title> + <para> Authentication is disabled by default. Once enabled, it is possible to disable authentication for specific services by following the instructions in this section. All paths specified in the sub-sections below are relative to <literal>$JBOSS_HOME</literal>.