Author: smumford Date: 2010-12-01 01:09:43 -0500 (Wed, 01 Dec 2010) New Revision: 5396 Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/ClusteringConfiguration.xml epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting_Started.xml epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Installation.xml epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_Installation.xml Log: JBEPP-515: Updated as per feedback from BNE Docs QE Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/ClusteringConfiguration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/ClusteringConfiguration.xml 2010-12-01 04:25:29 UTC (rev 5395) +++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/ClusteringConfiguration.xml 2010-12-01 06:09:43 UTC (rev 5396) @@ -97,7 +97,7 @@ </itemizedlist> <para> The default property file would look like the following: - <programlisting># Data +<programlisting># Data gatein.data.dir=/mnt/shared/mylocation # DB @@ -121,15 +121,17 @@ <title>Running with the cluster profile</title> <para>To run the portal in high-availability mode, you would need to start all nodes with an extra profile configuration as follows:</para> <formalpara><title>In Linux</title> - <para> - <literal>run.sh -c all -Dexo.profiles=cluster</literal> - </para> +<para> +<programlisting><command>run.sh -c all -Dexo.profiles=cluster</command> +</programlisting> +</para> </formalpara> <formalpara><title>In Windows</title> - <para> - <literal>run.bat -c all -Dexo.profiles=cluster</literal> - </para> +<para> +<programlisting><command>run.bat -c all -Dexo.profiles=cluster</command> +</programlisting> +</para> </formalpara> </section> </section> Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting_Started.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting_Started.xml 2010-12-01 04:25:29 UTC (rev 5395) +++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting_Started.xml 2010-12-01 06:09:43 UTC (rev 5396) @@ -23,7 +23,7 @@ <section id="Getting_Started-Pre_Requisites"> <title>Pre-Requisites</title> <para> - You must have adequate disk space to install a JDK and &PRODUCT; (about 520MB) while also allowing enough space for your applications. Before installing &PRODUCT; you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. + You must have adequate disk space to install a JDK and &PRODUCT; (about 550MB) while also allowing enough space for your applications. Before installing &PRODUCT; you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. </para> <section id="Pre_Requisites-EAP"> <title>Enterprise Application Platform</title> @@ -36,7 +36,7 @@ <formalpara> <title>Minimum Installation Requirements</title> <para> - The minimum hard disk space required to support the installation of the JBoss Enterprise Portal Platform is about 550MB. 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. + The minimum hard disk space required to support the installation of the JBoss Enterprise Portal Platform is about 550MB. Additional space is required for the installation of the JDK upon which the JBoss Application Server depends. The JDK installation size is currently up to 150MB. </para> </formalpara> <formalpara> Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Installation.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Installation.xml 2010-12-01 04:25:29 UTC (rev 5395) +++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Installation.xml 2010-12-01 06:09:43 UTC (rev 5396) @@ -24,9 +24,11 @@ <itemizedlist> <listitem> <para> - Unzip <literal>jboss-epp-<replaceable>&lt;release&gt;</replaceable>.zip</literal> to extract the archive contents into the location of your choice. You can do this using the JDK <literal>jar</literal> tool (or any other ZIP extraction tool). <programlisting> - [vsr]$ <literal>cd jbeppinstallationdir</literal> - [vsr]$ <literal>jar -xvf jboss-epp-<replaceable>&lt;release&gt;</replaceable>.zip</literal></programlisting> + Unzip <literal>jboss-epp-<replaceable>&lt;release&gt;</replaceable>.zip</literal> to extract the archive contents into the location of your choice. You can do this using the JDK <literal>jar</literal> tool (or any other ZIP extraction tool). +<programlisting> +[vsr]$ <literal>cd jbeppinstallationdir</literal> +[vsr]$ <literal>jar -xvf jboss-epp-<replaceable>&lt;release&gt;</replaceable>.zip</literal> +</programlisting> </para> </listitem> <listitem> @@ -39,8 +41,10 @@ <note> <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. + 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>. + </para> + <para> + The &JBEAP; <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_... Started Guide</ulink> explains in detail the different server configuration file sets. </para> </note> Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_Installation.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_Installation.xml 2010-12-01 04:25:29 UTC (rev 5395) +++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_Installation.xml 2010-12-01 06:09:43 UTC (rev 5396) @@ -32,10 +32,14 @@ </title> <para> Create an environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: <filename>C:\jboss-epp-5.0\jboss-as\</filename>. - In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: <filename>C:\jboss-epp-5.0\jboss-as\bin</filename>. - You may set these variables by going to the System Properties window then select the Advanced tab and finally click on the Environment Variables button. </para> </formalpara> + <para> + In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: <filename>C:\jboss-epp-5.0\jboss-as\bin</filename>. + </para> + <para> + You may set these variables by going to the System Properties window then select the Advanced tab and finally click on the Environment Variables button. + </para> </section> <section id="Adjust_Memory_Settings"> @@ -53,7 +57,7 @@ <para> If the server is running out of memory, you may adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.conf</filename> on Linux or <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.conf.bat</filename> on Windows. The default values don't take into account the memory requirements of your applications: <programlisting> - -Xms1303m -Xmx1303m -XX:MaxPermSize=256m .... +-Xms1303m -Xmx1303m -XX:MaxPermSize=256m .... </programlisting> </para> </section> @@ -152,8 +156,6 @@ role JBossAdmin to access the HTML JMX console web application &lt;/description&gt; &lt;url-pattern&gt;/*&lt;/url-pattern&gt; - &lt;http-method&gt;GET&lt;/http-method&gt; - &lt;http-method&gt;POST&lt;/http-method&gt; &lt;/web-resource-collection&gt; &lt;auth-constraint&gt; &lt;role-name&gt;JBossAdmin&lt;/role-name&gt;