[gatein-commits] gatein SVN: r8243 - epp/docs/branches/5.2/Installation_Guide/en-US.

Author: smumford Date: 2011-12-13 02:25:12 -0500 (Tue, 13 Dec 2011) New Revision: 8243 Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml Log: JBEPP-1431: Actioning QA feedback. Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>3</pubsnumber> + <pubsnumber>4</pubsnumber> <abstract> <para> This book provides information about obtaining, installing and running JBoss Enterprise Portal Platform. It forms part of the complete document suite along with the <emphasis role="bold">User Guide</emphasis> and <emphasis role="bold">Reference Guide</emphasis> available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf... />. Modified: epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -97,14 +97,15 @@ </itemizedlist> <para> The default property file would look like the following: -<programlisting># Data -gatein.data.dir=/mnt/shared/mylocation +<programlisting># +gatein.conf.dir=${jboss.server.home.dir}/conf/gatein +gatein.data.dir=${jboss.server.data.dir}/gatein # DB gatein.db.data.dir=${gatein.data.dir}/db # JCR -gatein.jcr.config.type=cluster +gatein.jcr.config.type=local gatein.jcr.datasource.name=java:gatein-jcr gatein.jcr.datasource.dialect=auto @@ -113,7 +114,7 @@ gatein.jcr.cache.config=war:/conf/jcr/jbosscache/${gatein.jcr.config.type}/config.xml gatein.jcr.lock.cache.config=war:/conf/jcr/jbosscache/${gatein.jcr.config.type}/lock-config.xml gatein.jcr.index.data.dir=${gatein.jcr.data.dir}/lucene -gatein.jcr.index.changefilterclass=org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter +gatein.jcr.index.changefilterclass=org.exoplatform.services.jcr.impl.core.query.DefaultChangesFilter gatein.jcr.index.cache.config=war:/conf/jcr/jbosscache/cluster/indexer-config.xml gatein.jcr.jgroups.config=classpath:/jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml gatein.jcr.workspace.default=collaboration Modified: epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -41,7 +41,7 @@ datasource descriptor located at <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/deploy/gatein-ds.xml</filename>: <programlisting language="XML" role="XML"> -&lt;local-tx-datasource&gt; +&lt;no-tx-datasource&gt; &lt;jndi-name&gt;gatein-jcr&lt;/jndi-name&gt; &lt;connection-url&gt; jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-jcr-localDB @@ -54,7 +54,7 @@ &lt;max-pool-size&gt;20&lt;/max-pool-size&gt; &lt;idle-timeout-minutes&gt;0&lt;/idle-timeout-minutes&gt; &lt;prepared-statement-cache-size&gt;32&lt;/prepared-statement-cache-size&gt; -&lt;/local-tx-datasource&gt; +&lt;/no-tx-datasource&gt; </programlisting> </para> @@ -82,7 +82,7 @@ datasource descriptor located at <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/deploy/gatein-ds.xml</filename>: <programlisting language="XML" role="XML"> -&lt;local-tx-datasource&gt; +&lt;no-tx-datasource&gt; &lt;jndi-name&gt;gatein-idm&lt;/jndi-name&gt; &lt;connection-url&gt; jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-idm-localDB @@ -95,7 +95,7 @@ &lt;max-pool-size&gt;20&lt;/max-pool-size&gt; &lt;idle-timeout-minutes&gt;0&lt;/idle-timeout-minutes&gt; &lt;prepared-statement-cache-size&gt;32&lt;/prepared-statement-cache-size&gt; -&lt;/local-tx-datasource&gt; +&lt;/no-tx-datasource&gt; </programlisting> </para> @@ -175,7 +175,7 @@ </para> <note><title>Note: Database names</title> <para> - The remainder of this guide, and the configuration examples that follow assume the database names to be gateinjcr and gateinidm. If you change the database names, please update gatein-ds.xml accordingly (for each server configuration used). + The remainder of this guide, and the configuration examples that follow assume the database names to be gateinjcr and gateinidm. If you change the database names, please update <filename>gatein-ds.xml</filename> accordingly (for each server configuration used). </para> </note> <para> @@ -309,7 +309,7 @@ <para><filename>gatein-ds.xml</filename> will then look like:</para> <programlisting language="XML" role="XML"><![CDATA[<datasources> - <local-tx-datasource> + <no-tx-datasource> <jndi-name>gatein-idm</jndi-name> <connection-url>jdbc:mysql://mysql-hostname:3306/gateinidm</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> @@ -320,9 +320,9 @@ <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> <prepared-statement-cache-size>32</prepared-statement-cache-size> - </local-tx-datasource> + </no-tx-datasource> - <local-tx-datasource> + <no-tx-datasource> <jndi-name>gatein-jcr</jndi-name> <connection-url>jdbc:mysql://mysql-hostname:3306/gateinjcr</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> @@ -333,7 +333,7 @@ <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> <prepared-statement-cache-size>32</prepared-statement-cache-size> - </local-tx-datasource> + </no-tx-datasource> </datasources>]]> </programlisting> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -5,7 +5,7 @@ ]> <chapter id="Getting_Started"> - <title>Getting Started</title> + <title>Getting Started</title> <section id="sect-Installation_Guide-Getting_Started-Upgrading_Previous_Installations"> <title>Upgrading and Add-ons</title> @@ -15,16 +15,16 @@ <important> <title>Upgrading JBoss Enterprise Portal Platform</title> <para> - It is possible to upgrade from JBoss Enterprise Portal Platform version 5.0 or 5.1.0 to JBoss Enterprise Portal Platform 5.1.1. + It is possible to upgrade from JBoss Enterprise Portal Platform version 5.0 or 5.1.0 to JBoss Enterprise Portal Platform &VZ;. </para> <para> - To upgrade, copy any customized configuration files and database settings from your existing JBoss Enterprise Portal Platform installation to the corresponding location of the 5.1.1 installation. + To upgrade, copy any customized configuration files and database settings from your existing JBoss Enterprise Portal Platform installation to the corresponding location of the &VZ; installation. </para> </important> <important> <title>Add-ons</title> <para> - The <emphasis role="bold">Site Publisher</emphasis> add-on that is part of the &VZ; release can only be installed into a <emphasis>clean</emphasis> installation of JBoss Enterprise Portal Platform version 5.1 or later. + The <emphasis role="bold">Site Publisher</emphasis> add-on that is part of the &VZ; release can only be installed into a <emphasis>clean</emphasis> installation of JBoss Enterprise Portal Platform version 5.1 or later. </para> <itemizedlist> <listitem> @@ -37,475 +37,491 @@ Likewise, Site Publisher <emphasis role="bold">cannot</emphasis> be installed onto JBoss Enterprise Portal Platform 5.0 or 5.0.1 versions (including installations that include the technical preview release of the Site Publisher extension). </para> <para> - You must deploy a new instance of JBoss Enterprise Portal Platform 5.1.1 in order to use the Site Publisher add-on. + You must deploy a new instance of JBoss Enterprise Portal Platform &VZ; in order to use the Site Publisher add-on. </para> </listitem> </itemizedlist> </important> - </section> + </section> - <section id="Getting_Started-Pre_Requisites"> - <title>Pre-Requisites</title> - <para> - You must have adequate disk space to install a JDK and JBoss Enterprise Portal Platform (about 550MB) while also allowing enough space for your applications. Before installing JBoss Enterprise Portal Platform 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> - <para>JBoss Enterprise Portal Platform is built upon JBoss Enterprise Application Platform. For more details about the underlying platform please refer to - the EAP installation guide available at: <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_... - </para> + <section id="Getting_Started-Pre_Requisites"> + <title>Pre-Requisites</title> + <para> + You must have adequate disk space to install a JDK and JBoss Enterprise Portal Platform (about 550MB) while also allowing enough space for your applications. Before installing JBoss Enterprise Portal Platform 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> + <para>JBoss Enterprise Portal Platform is built upon JBoss Enterprise Application Platform. For more details about the underlying platform please refer to + the EAP installation guide available at: <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_... + </para> </section> - <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements"> - <title>System Requirements</title> - <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 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: 1.5 GB - </para> - <itemizedlist> - <listitem> - <para> - The default server log file storage configuration is 500MB. - </para> - </listitem> - <listitem> - <para> - The remaining 500 MB is allocated to the server installation (240 MB), the required JDK (150 MB) and some additional space for applications (110 MB). - </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: 1.5 GB - </para> - <itemizedlist> - <listitem> - <para> - RAM installations of 2 GB or more will be required to run a server upon which small to medium applications are deployed. 4 GB 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> - <indexterm> - <primary>System Requirements</primary> - <secondary>OS/JVM</secondary> - </indexterm> - <table> - <title> - Supported Operating System / JVM Combinations. - </title> - <tgroup cols="2"> - <colspec colnum="1" colname="OS" colwidth="1*"></colspec> - <colspec colnum="2" colname="JVM" colwidth="1*"></colspec> - - <thead> - <row> - <entry> - <emphasis>Operating System</emphasis> - </entry> - <entry> - <emphasis>JVM Version</emphasis> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - Red Hat Enterprise Linux 5 x86 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86 - </entry> - <entry> - OpenJDK 1.6.0-b09 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86 - </entry> - <entry> - IBM JDK 1.6.0 SR5 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86_64 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86_64 - </entry> - <entry> - OpenJDK 1.6.0-b09 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86_64 - </entry> - <entry> - IBM JDK 1.6.0 SR5 - </entry> - </row> - <row> - <entry> - Microsoft Windows 2008 x86 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Microsoft Windows 2008 x86_64 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Solaris 10 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - </tbody> - </tgroup> - </table> - - <para> + <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements"> + <title>System Requirements</title> + <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 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: 1.5 GB + </para> + <itemizedlist> + <listitem> + <para> + The default server log file storage configuration is 500MB. + </para> + </listitem> + <listitem> + <para> + The remaining 500 MB is allocated to the server installation (240 MB), the required JDK (150 MB) and some additional space for applications (110 MB). + </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: 1.5 GB + </para> + <itemizedlist> + <listitem> + <para> + RAM installations of 2 GB or more will be required to run a server upon which small to medium applications are deployed. 4 GB 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> + <indexterm> + <primary>System Requirements</primary> + <secondary>OS/JVM</secondary> + </indexterm> + <table> + <title> + Supported Operating System / JVM Combinations. + </title> + <tgroup cols="2"> + <colspec colnum="1" colname="OS" colwidth="1*"></colspec> + <colspec colnum="2" colname="JVM" colwidth="1*"></colspec> + + <thead> + <row> + <entry> + <emphasis>Operating System</emphasis> + </entry> + <entry> + <emphasis>JVM Version</emphasis> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + Red Hat Enterprise Linux 6 + </entry> + <entry> + OpenJDK + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 6 + </entry> + <entry> + SunJDK + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86 + </entry> + <entry> + OpenJDK 1.6.0-b09 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86 + </entry> + <entry> + IBM JDK 1.6.0 SR5 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86_64 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86_64 + </entry> + <entry> + OpenJDK 1.6.0-b09 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86_64 + </entry> + <entry> + IBM JDK 1.6.0 SR5 + </entry> + </row> + <row> + <entry> + Microsoft Windows 2008 x86 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Microsoft Windows 2008 x86_64 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Solaris 10 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + </tbody> + </tgroup> + </table> + + <para> The following is a cumulative table of supported databases and JDBC drivers. </para> <para> Entries shown for each release are supported <emphasis role="bold">in addition to those in previous releases</emphasis>: - </para> - <indexterm> - <primary>System Requirements</primary> - <secondary>Database</secondary> - </indexterm> - <indexterm> - <primary>Database</primary> - <secondary>System Requirements</secondary> - </indexterm> - <table> - <title>Supported Database and JDBC driver Combinations</title> - <tgroup cols="2"> - <colspec colnum="1" colname="c1" colwidth="1*"></colspec> - <colspec colnum="2" colname="c2" colwidth="1*"></colspec> + </para> + <indexterm> + <primary>System Requirements</primary> + <secondary>Database</secondary> + </indexterm> + <indexterm> + <primary>Database</primary> + <secondary>System Requirements</secondary> + </indexterm> + <table> + <title>Supported Database and JDBC driver Combinations</title> + <tgroup cols="2"> + <colspec colnum="1" colname="c1" colwidth="1*"></colspec> + <colspec colnum="2" colname="c2" colwidth="1*"></colspec> <spanspec spanname="hspan" namest="c1" nameend="c2" align="left"></spanspec> - <thead> - <row> - <entry> - <emphasis>Database</emphasis> - </entry> - <entry> - <emphasis>Database driver</emphasis> - </entry> - </row> - </thead> - <tbody> + <thead> + <row> + <entry> + <emphasis>Database</emphasis> + </entry> + <entry> + <emphasis>Database driver</emphasis> + </entry> + </row> + </thead> + <tbody> <row> - <entry spanname="hspan"> + <entry spanname="hspan"> <emphasis><emphasis role="bold">JBoss Enterprise Portal Platform 5.0</emphasis></emphasis> - </entry> + </entry> </row> - <row> - <entry> - MySQL 5.1 - </entry> - <entry> - MySQL Connector/J 5.1.8 - </entry> - </row> - <row> - <entry> + <row> + <entry> + MySQL 5.1 + </entry> + <entry> + MySQL Connector/J 5.1.8 + </entry> + </row> + <row> + <entry> Oracle 10g R2 <!--(10.2.0.4)--> - </entry> - <entry> + </entry> + <entry> 10g R2 <!--(10.2.0.4)--> - </entry> - </row> - <row> - <entry> + </entry> + </row> + <row> + <entry> Oracle 11g R1 <!-- (11.1.0.7.0) -->(Supported) - </entry> - <entry> + </entry> + <entry> 11g R1 <!--(11.1.0.7.0)--> - </entry> - </row> - <row> - <entry> + </entry> + </row> + <row> + <entry> Oracle 11g RAC <!--(11.1.0.7.0)--> (Supported) - </entry> - <entry> + </entry> + <entry> 11g R1 <!--(11.1.0.7.0)--> - </entry> - </row> - <row> - <entry> - Microsoft SQL Server 2005 SP3 - </entry> - <entry> - Microsoft JDBC Driver 2.0 - </entry> - </row> - <row> - <entry> - Microsoft SQL Server 2008 SP1 - </entry> - <entry> - Microsoft JDBC Driver 2.0 - </entry> - </row> - <row> - <entry> - PostgresSQL 8.3.7 - </entry> - <entry> - PostgresSQL Driver JDBC4, 8.3-605 - </entry> - </row> - <row> - <entry> - PostgresSQL 8.2.4 (Supported) - </entry> - <entry> - PostgresSQL Driver JDBC4, 8.2-510 - </entry> - </row> - <row> - <entry> - DB2 9.7 - </entry> - <entry> - IBM Data Server Driver for JDBC and SQLJ (JCC Driver) Version: 9.1 (fixpack 3a) - </entry> - </row> - <row> - <entry> - Sybase 15.0.2 - </entry> - <entry> + </entry> + </row> + <row> + <entry> + Microsoft SQL Server 2005 SP3 + </entry> + <entry> + Microsoft JDBC Driver 2.0 + </entry> + </row> + <row> + <entry> + Microsoft SQL Server 2008 SP1 + </entry> + <entry> + Microsoft JDBC Driver 2.0 + </entry> + </row> + <row> + <entry> + PostgresSQL 8.3.7 + </entry> + <entry> + PostgresSQL Driver JDBC4, 8.3-605 + </entry> + </row> + <row> + <entry> + PostgresSQL 8.2.4 (Supported) + </entry> + <entry> + PostgresSQL Driver JDBC4, 8.2-510 + </entry> + </row> + <row> + <entry> + DB2 9.7 + </entry> + <entry> + IBM Data Server Driver for JDBC and SQLJ (JCC Driver) Version: 9.1 (fixpack 3a) + </entry> + </row> + <row> + <entry> + Sybase 15.0.2 + </entry> + <entry> JConnect v6.0.5 <!--(Build 26564 / 11 Jun 2009) --> - </entry> - </row> + </entry> + </row> <row> - <entry spanname="hspan"> + <entry spanname="hspan"> <emphasis><emphasis role="bold">JBoss Enterprise Portal Platform 5.1</emphasis></emphasis> - </entry> + </entry> </row> <row> - <entry> - Oracle 11g R2 - </entry> - <entry> - 11g R2 - </entry> - </row> - <row> - <entry> - Oracle 11g R2 RAC - </entry> - <entry> - 11g R2 RAC - </entry> - </row> - </tbody> - </tgroup> - </table> + <entry> + Oracle 11g R2 + </entry> + <entry> + 11g R2 + </entry> + </row> + <row> + <entry> + Oracle 11g R2 RAC + </entry> + <entry> + 11g R2 RAC + </entry> + </row> + </tbody> + </tgroup> + </table> - <indexterm> - <primary>System Requirements</primary> - <secondary>Directory server</secondary> - </indexterm> - <para> - The following is a list of supported directory servers: - </para> - - <table> - <title>Supported and Certified directory servers</title> - <tgroup cols="2"> - <colspec colnum="1" colname="LDAP" colwidth="1*"></colspec> - <thead> - <row> - <entry> - <emphasis>Directory Server</emphasis> - </entry> + <indexterm> + <primary>System Requirements</primary> + <secondary>Directory server</secondary> + </indexterm> + <para> + The following is a list of supported directory servers: + </para> + + <table> + <title>Supported and Certified directory servers</title> + <tgroup cols="2"> + <colspec colnum="1" colname="LDAP" colwidth="1*"></colspec> + <thead> + <row> + <entry> + <emphasis>Directory Server</emphasis> + </entry> <entry> <emphasis>Version</emphasis> </entry> - </row> - </thead> - <tbody> - <row> - <entry> - OpenDS - </entry> + </row> + </thead> + <tbody> + <row> + <entry> + OpenDS + </entry> <entry> 1.2 </entry> - </row> - <row> - <entry> - OpenDS - </entry> + </row> + <row> + <entry> + OpenDS + </entry> <entry> 2.0 </entry> - </row> - <row> - <entry> - OpenLDAP - </entry> + </row> + <row> + <entry> + OpenLDAP + </entry> <entry> 2.4 </entry> - </row> - <row> - <entry> - Red Hat Directory Server - </entry> + </row> + <row> + <entry> + Red Hat Directory Server + </entry> <entry> 7.1 </entry> - </row> - <row> - <entry> - MS Active Directory - </entry> + </row> + <row> + <entry> + MS Active Directory + </entry> <entry> Windows Server 2008 </entry> - </row> - </tbody> - </tgroup> - </table> + </row> + </tbody> + </tgroup> + </table> <!-- - <note> - <para> - JBoss uses an embedded Tomcat and does not require a stand-alone Tomcat. - </para> - </note> + <note> + <para> + JBoss uses an embedded Tomcat and does not require a stand-alone Tomcat. + </para> + </note> --> - </section> - - <section id="Pre_Requisites-Configuring_Your_Java_Environment"> - <title>Configuring Your Java Environment</title> - - <para> - You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install JBoss Enterprise Portal Platform. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 6.0 using RHN, on a generic Linux Platform and Microsoft Windows Platform. But before we do that let's take a look at some of the benefits of using a 64-bit JVM. - </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> - <listitem> - <para> - Wider datapath: The pipe between RAM and CPU is doubled, which improves the performance of memory-bound applications. - </para> - </listitem> - <listitem> - <para> - 64-bit memory addressing gives virtually unlimited (1 exabyte) heap allocation. However large heaps affect garbage collection. - </para> - </listitem> - <listitem> - <para> - Applications that run with more than 1.5 GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM. - </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> - <para> - 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>Red Hat Enterprise Linux 5 Java SDKs</title> + </section> + + <section id="Pre_Requisites-Configuring_Your_Java_Environment"> + <title>Configuring Your Java Environment</title> + + <para> + You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install JBoss Enterprise Portal Platform. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 6.0 using RHN, on a generic Linux Platform and Microsoft Windows Platform. But before we do that let's take a look at some of the benefits of using a 64-bit JVM. + </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> + <listitem> + <para> + Wider datapath: The pipe between RAM and CPU is doubled, which improves the performance of memory-bound applications. + </para> + </listitem> + <listitem> + <para> + 64-bit memory addressing gives virtually unlimited (1 exabyte) heap allocation. However large heaps affect garbage collection. + </para> + </listitem> + <listitem> + <para> + Applications that run with more than 1.5 GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM. + </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> + <para> + 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>Red Hat Enterprise Linux 5 Java SDKs</title> <varlistentry> <term> Channel: rhel-&lt;arch&gt;-server-5 </term> <listitem> <para> - java-1.6.0-openjdk + java-1.6.0-openjdk </para> </listitem> </varlistentry> @@ -515,11 +531,11 @@ </term> <listitem> <para> - java-1.6.0-sun (Sun) + java-1.6.0-sun (Sun) </para> <para> - java-1.6.0-ibm (IBM) + java-1.6.0-ibm (IBM) </para> </listitem> </varlistentry> @@ -527,113 +543,113 @@ <para> Ensure that the -devel packages are also installed. </para> - </listitem> - - <listitem> - <para> - Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0</command> (setting <command moreinfo="none">java_sdk_1.6.0</command> is optional). - </para> - - <para> - This is only needed if you want to use the SysV service script - and/or want this installed SDK to be the default java and javac - in the system. This choice can often be overridden by setting - the <command moreinfo="none">JAVA_HOME</command> environment variable. - </para> - - <para> - The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources, to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want. - </para> - - <para> - As root, issue the following command: - </para> - <screen><command moreinfo="none">/usr/sbin/alternatives --config java</command></screen> - <para> - and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted. - </para> - - <para> - Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0.</command> We recommend that all point to the same manufacturer and version. - </para> - </listitem> - </itemizedlist> - - <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_a_generic_Linux_platform"> - <title>Installing and Configuring JDK 6.0 on a generic Linux platform</title> - <listitem> - <para> - Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp#need">&l...;. - </para> - </listitem> - <listitem> - <para> - From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://java.sun.com/javase/downloads/widget/jdk6.jsp">&...;. - </para> - </listitem> - <listitem> - <para> - Follow the instructions presented on this page including selecting the appropriate platform and architecture. - </para> - </listitem> - <listitem> - <para> - Clicking the <guibutton>Continue</guibutton> button will display the download options (depending on whether the user chooses to register): - </para> - <itemizedlist> - <listitem> - <para> - jdk-6u&lt;update number&gt;-linux-&lt;arch&gt;-rpm.bin or; - </para> - </listitem> - <listitem> - <para> - jdk-6u&lt;update number&gt;-linux-&lt;arch&gt;.bin - </para> - </listitem> - </itemizedlist> - <para>If installing the JDK on Red Hat Enterprise Linux, Fedora, or another RPM-based Linux system, it is recommended that the self-extracting file containing the RPM package is selected. This option will set up and use the SysV service scripts in addition to installing the JDK. The RPM option is also recommended if the JBoss Enterprise Portal Platform is being set up in a production environment. - </para> - </listitem> -<!-- <listitem> - <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> - <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> - 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> - Create an environment variable that points to the JDK installation directory and call it <literal>JAVA_HOME</literal>. Add <literal>$JAVA_HOME/bin</literal> to the system path to be able to run <literal>java</literal> from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. <programlisting> + </listitem> + + <listitem> + <para> + Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0</command> (setting <command moreinfo="none">java_sdk_1.6.0</command> is optional). + </para> + + <para> + This is only needed if you want to use the SysV service script + and/or want this installed SDK to be the default java and javac + in the system. This choice can often be overridden by setting + the <command moreinfo="none">JAVA_HOME</command> environment variable. + </para> + + <para> + The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources, to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want. + </para> + + <para> + As root, issue the following command: + </para> + <screen><command moreinfo="none">/usr/sbin/alternatives --config java</command></screen> + <para> + and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted. + </para> + + <para> + Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0.</command> We recommend that all point to the same manufacturer and version. + </para> + </listitem> + </itemizedlist> + + <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_a_generic_Linux_platform"> + <title>Installing and Configuring JDK 6.0 on a generic Linux platform</title> + <listitem> + <para> + Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp#need">&l...;. + </para> + </listitem> + <listitem> + <para> + From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://java.sun.com/javase/downloads/widget/jdk6.jsp">&...;. + </para> + </listitem> + <listitem> + <para> + Follow the instructions presented on this page including selecting the appropriate platform and architecture. + </para> + </listitem> + <listitem> + <para> + Clicking the <guibutton>Continue</guibutton> button will display the download options (depending on whether the user chooses to register): + </para> + <itemizedlist> + <listitem> + <para> + jdk-6u&lt;update number&gt;-linux-&lt;arch&gt;-rpm.bin or; + </para> + </listitem> + <listitem> + <para> + jdk-6u&lt;update number&gt;-linux-&lt;arch&gt;.bin + </para> + </listitem> + </itemizedlist> + <para>If installing the JDK on Red Hat Enterprise Linux, Fedora, or another RPM-based Linux system, it is recommended that the self-extracting file containing the RPM package is selected. This option will set up and use the SysV service scripts in addition to installing the JDK. The RPM option is also recommended if the JBoss Enterprise Portal Platform is being set up in a production environment. + </para> + </listitem> +<!-- <listitem> + <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> + <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> + 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> + Create an environment variable that points to the JDK installation directory and call it <literal>JAVA_HOME</literal>. Add <literal>$JAVA_HOME/bin</literal> to the system path to be able to run <literal>java</literal> from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. <programlisting> #In this example /usr/java/jdk1.6.0_19 is the JDK installation directory. export JAVA_HOME=/usr/java/jdk1.6.0_19 export PATH=$PATH:$JAVA_HOME/bin </programlisting> - Set this variable for the user account performing the installation and also for the user account that will run the server. - </para> - </listitem> - <listitem> - <para> - If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.6 installation as the default <literal>java</literal> and <literal>javac</literal>. You can do this using the alternatives system. The alternatives system allows different versions of Java, from different sources to co-exist on your system. - <note> - <para> - Selecting alternatives as decribed below can be avoided by setting the <literal>JAVA_HOME</literal> environment variable as explained in the previous step. - </para> - </note> - <itemizedlist> - <title>Select alternatives for java, javac and java_sdk_1.6.0</title> - - <listitem> - <para> - As root, type the following command at the shell prompt and you should see something like this: - </para> + Set this variable for the user account performing the installation and also for the user account that will run the server. + </para> + </listitem> + <listitem> + <para> + If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.6 installation as the default <literal>java</literal> and <literal>javac</literal>. You can do this using the alternatives system. The alternatives system allows different versions of Java, from different sources to co-exist on your system. + <note> + <para> + Selecting alternatives as decribed below can be avoided by setting the <literal>JAVA_HOME</literal> environment variable as explained in the previous step. + </para> + </note> + <itemizedlist> + <title>Select alternatives for java, javac and java_sdk_1.6.0</title> + + <listitem> + <para> + As root, type the following command at the shell prompt and you should see something like this: + </para> <programlisting>[root@vsr ~]$ /usr/sbin/alternatives --config java There are 2 programs which provide 'java'. Selection Command @@ -644,17 +660,17 @@ </programlisting> <para> - Make sure the Sun version - <literal>jre-1.6.0-sun</literal> in this case - is selected (marked with a '+' in the output), or select it by entering its number as prompted. - </para> - </listitem> - <listitem> - <para> - Repeat the same for javac and java_sdk_1.6.0. - </para> - <programlisting> + Make sure the Sun version - <literal>jre-1.6.0-sun</literal> in this case - is selected (marked with a '+' in the output), or select it by entering its number as prompted. + </para> + </listitem> + <listitem> + <para> + Repeat the same for javac and java_sdk_1.6.0. + </para> + <programlisting> [root@vsr ~]$ /usr/sbin/alternatives --config javac There are 1 programs which provide 'javac'. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.6.0-sun/bin/javac Enter to keep the current selection[+], or type selection number: @@ -662,84 +678,84 @@ <programlisting> [root@vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.6.0 There are 1 programs which provide 'java_sdk_1.6.0'. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.6.0-sun Enter to keep the current selection[+], or type selection number: </programlisting> <para> You should verify that java, javac and java_sdk_1.6.0 all point to the same manufacturer and version. - </para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para> - Make sure that the <literal>java</literal> executable is in your path and that you are using an appropriate version. To verify your Java environment, type <literal>java -version</literal> at the shell prompt and you should see something like this: <programlisting> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + <listitem> + <para> + Make sure that the <literal>java</literal> executable is in your path and that you are using an appropriate version. To verify your Java environment, type <literal>java -version</literal> at the shell prompt and you should see something like this: <programlisting> [root@vsr ~]$ java -version java version "1.6.0_19" Java(TM) SE Runtime Environment (build 1.6.0_19-b01) Java HotSpot(TM) Server VM (build 14.2-b01, mixed mode) </programlisting> - </para> - </listitem> - </itemizedlist> - - <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_Microsoft_Windows"> - <title>Installing and Configuring JDK 6.0 on Microsoft Windows</title> - <listitem> - <para> - Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp#need">&l...;. - </para> - </listitem> - <listitem> - <para> - From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://java.sun.com/javase/downloads/widget/jdk6.jsp">&...;. - </para> - </listitem> - <listitem> - <para> - Follow the instructions presented on this page including selecting the appropriate platform and architecture. - </para> - </listitem> - <listitem> - <para> - Clicking the <guibutton>Continue</guibutton> button will display the download option (depending on whether the user chooses to register): - </para> - <itemizedlist> - <listitem> - <para> - jdk-6u&lt;update number&gt;-windows-&lt;arch&gt;.exe - </para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para> - Create an environment variable called <literal>JAVA_HOME</literal> that points to the JDK installation directory, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\</literal>. - </para> - </listitem> - <listitem> - <para> - In order to run java from the command line add the <literal>jre\bin</literal> directory to your path, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\jre\bin</literal>. 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> - </listitem> - </itemizedlist> - </section> + </para> + </listitem> + </itemizedlist> + + <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_Microsoft_Windows"> + <title>Installing and Configuring JDK 6.0 on Microsoft Windows</title> + <listitem> + <para> + Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Oracle's website: <ulink type="http" url="http://www.oracle.com/technetwork/java/javase/downloads/index.h...;. + </para> + </listitem> + <listitem> + <para> + From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://www.oracle.com/technetwork/java/javase/downloads/jdk6-js...;. + </para> + </listitem> + <listitem> + <para> + Follow the instructions presented on this page including selecting the appropriate platform and architecture. + </para> + </listitem> + <listitem> + <para> + Clicking the <guibutton>Continue</guibutton> button will display the download option (depending on whether the user chooses to register): + </para> + <itemizedlist> + <listitem> + <para> + jdk-6u&lt;update number&gt;-windows-&lt;arch&gt;.exe + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para> + Create an environment variable called <literal>JAVA_HOME</literal> that points to the JDK installation directory, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\</literal>. + </para> + </listitem> + <listitem> + <para> + In order to run java from the command line add the <literal>jre\bin</literal> directory to your path, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\jre\bin</literal>. 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> + </listitem> + </itemizedlist> + </section> - </section> + </section> <section> - <title>Recommended Practices</title> - <para> - JBoss Enterprise Portal Platform includes four pre-configured user accounts for testing and evaluation purposes. These accounts can be used for direct access to the portal. - </para> - <para> - For security reasons, before going in production, you should restrict the access to the login servlet to POST. - </para> - <para> + <title>Recommended Practices</title> + <para> + JBoss Enterprise Portal Platform includes four pre-configured user accounts for testing and evaluation purposes. These accounts can be used for direct access to the portal. + </para> + <para> + For security reasons, before going in production, you should restrict the access to the login servlet to POST. + </para> + <para> To do so, edit the file <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add: - </para> + </para> <programlisting language="XML" role="XML"><![CDATA[ <security-constraint> <web-resource-collection> @@ -754,10 +770,10 @@ </web-resource-collection> <auth-constraint/> </security-constraint> ]]></programlisting> - <para> - Doing this will render the login links provided on the front page inactive. - </para> - - </section> + <para> + Doing this will render the login links provided on the front page inactive. + </para> + + </section> </chapter> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -226,7 +226,7 @@ <formalpara> <title>Disabling Authentication for JMX Invoker:</title> <para> - To disable authentication for the JMX invoker, edit the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/jmx-invoker-service.xml</filename> file to comment out the security interceptor passthrough: + To disable authentication for the JMX invoker, edit the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/deploy/jmx-invoker-service.xml</filename> file to comment out the security interceptor passthrough: </para> </formalpara> <para> @@ -255,7 +255,7 @@ For security reasons, before going in production, you should restrict the access to the login servlet to POST. </para> <para> - To do so, edit the file <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add: + To do so, edit the file <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add: </para> <programlisting language="XML" role="XML"><![CDATA[ <security-constraint> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -9,6 +9,20 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.0-4</revnumber> + <date>Tue Dec 13 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>JBEPP-1431: Actioning QA feedback.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-3</revnumber> <date>Tue Nov 15 2011</date> <author> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -5,100 +5,97 @@ ]> <chapter id="Test_your_Installation"> - <title>Test your Installation</title> + <title>Test your Installation</title> - <para> - After you have installed the JBoss Enterprise Portal Platform, it is wise to perform a simple start up 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 variables as explained in <xref linkend="Post_Installation_Configuration"/>. - </para> - <para> - To test your installation: - <itemizedlist> - <listitem> - <para> + <para> + After you have installed the JBoss Enterprise Portal Platform, it is wise to perform a simple start up 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 variables as explained in <xref linkend="Post_Installation_Configuration"/>. + </para> + <para> + To test your installation: + <itemizedlist> + <listitem> + <para> move to the <filename><replaceable>JBOSS_HOME</replaceable>/bin</filename> directory; - </para> - </listitem> - <listitem> - <para> - execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system; - <itemizedlist> - <listitem> - <para> + </para> + </listitem> + <listitem> + <para> + execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system; + <itemizedlist> + <listitem> + <para> Ensure that you run the configuration corresponding to the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/</filename> chosen in <xref linkend="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_Database"></xref> - </para> - </listitem> - </itemizedlist> - </para> - </listitem> - </itemizedlist> - </para> - <para> - The example below uses the production configuration. Your output should look like the following (accounting for installation directory differences and version numbers) and should not contain any error or exception messages: - </para> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + </itemizedlist> + </para> + <para> + The example below uses the production configuration. Your output should look like the following (accounting for installation directory differences and version numbers) and should not contain any error or exception messages: + </para> <programlisting> [user@localhost bin]$ ./run.sh -c production ========================================================================= JBoss Bootstrap Environment - JBOSS_HOME: /home/user/jboss-epp-5.0/jboss-as + JBOSS_HOME: /var/jboss-epp/jboss-as - JAVA: /usr/java/jdk1.6.0_16/bin/java + JAVA: 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 - -Dexo.conf.dir.name=gatein -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/user/jboss-epp-5.0/jboss-as/bin/run.jar/usr/java/jdk1.6.0_16/lib/tools.jar + CLASSPATH: /var/jboss-epp/jboss-as/bin/run.jar ========================================================================= -16:59:41,401 INFO [ServerImpl] Starting JBoss (Microcontainer)... -16:59:41,401 INFO [ServerImpl] Release ID: JBoss [EAP] 5.0.0.GA (build: SVNTag=JBPAPP_5_0_0_GA date=200910202128) -16:59:41,402 INFO [ServerImpl] Bootstrap URL: null -16:59:41,402 INFO [ServerImpl] Home Dir: /home/user/jboss-epp-5.0/jboss-as -16:59:41,402 INFO [ServerImpl] Home URL: file:/home/user/jboss-epp-5.0/jboss-as/ -16:59:41,402 INFO [ServerImpl] Library URL: file:/home/user/jboss-epp-5.0/jboss-as/lib/ -16:59:41,403 INFO [ServerImpl] Patch URL: null -16:59:41,403 INFO [ServerImpl] Common Base URL: file:/home/user/jboss-epp-5.0/jboss-as/common/ -16:59:41,404 INFO [ServerImpl] Common Library URL: file:/home/user/jboss-epp-5.0/jboss-as/common/lib/ -16:59:41,404 INFO [ServerImpl] Server Name: production +23:27:30,376 INFO [ServerImpl] Starting JBoss (Microcontainer)... +23:27:30,376 INFO [ServerImpl] Release ID: JBoss [EPP] JBoss-EPP 5.2.0.GA (build: SVNTag=5.2.0.GA date=201112080623) +23:27:30,376 INFO [ServerImpl] Bootstrap URL: null +23:27:30,377 INFO [ServerImpl] Home Dir: /var/jboss-epp/jboss-as +23:27:30,377 INFO [ServerImpl] Home URL: file:/var/jboss-epp/jboss-as/ +23:27:30,377 INFO [ServerImpl] Library URL: file:/var/jboss-epp/jboss-as/lib/ +23:27:30,377 INFO [ServerImpl] Patch URL: null +23:27:30,377 INFO [ServerImpl] Common Base URL: file:/var/jboss-epp/jboss-as/common/ +23:27:30,377 INFO [ServerImpl] Common Library URL: file:/var/jboss-epp/jboss-as/common/lib/ +23:27:30,377 INFO [ServerImpl] Server Name: default ... ... -16:59:44,345 INFO [JMXKernel] Legacy JMX core initialized +23:27:32,061 INFO [JMXKernel] Legacy JMX core initialized </programlisting> - <note><title>Note: Production server log file</title> - <para> - There is no "Server Started" message shown at the console when the server is started using the <literal>production</literal> profile. This message may be observed in the <filename>server.log</filename> file located in the <filename><replaceable>JBOSS_HOME</replaceable>/server/production/log</filename> subdirectory. - </para> - </note> + <note><title>Note: Production server log file</title> + <para> + There is no "Server Started" message shown at the console when the server is started using the <literal>production</literal> profile. This message may be observed in the <filename>server.log</filename> file located in the <filename><replaceable>JBOSS_HOME</replaceable>/server/production/log</filename> subdirectory. + </para> + </note> - <para> - Ensure that port 8080 is not already in use and open <literal>http://localhost:8080/portal</literal> in your web browser. - <note> - <para> + <para> + Ensure that port 8080 is not already in use and open <literal>http://localhost:8080/portal</literal> in your web browser. + <note> + <para> On some machines, the name localhost won’t resolve properly and you should use the local loopback address <ulink type="http" url="127.0.0.1">127.0.0.1</ulink> instead. - </para> - </note> - 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"> - <title>Test your Installation</title> - <mediaobject> - <imageobject role="html"> - <imagedata fileref="images/test_install.png" format="PNG" align="center" scale="100" /> - </imageobject> - <imageobject role="fo"> - <imagedata fileref="images/test_install.png" format="PNG" align="center" contentwidth="444px" /> - </imageobject> - </mediaobject> - </figure> - </para> - <para> - You are now ready to use JBoss Enterprise Portal Platform. Refer to the User Guide and Reference Guide for more information about the product's feature set and example applications showcasing JBoss Enterprise Portal Platform in action. - </para> - + </para> + </note> + 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"> + <title>Test your Installation</title> + <mediaobject> + <imageobject role="html"> + <imagedata fileref="images/test_install.png" format="PNG" align="center" scale="100" /> + </imageobject> + <imageobject role="fo"> + <imagedata fileref="images/test_install.png" format="PNG" align="center" contentwidth="444px" /> + </imageobject> + </mediaobject> + </figure> + </para> + <para> + You are now ready to use JBoss Enterprise Portal Platform. Refer to the User Guide and Reference Guide for more information about the product's feature set and example applications showcasing JBoss Enterprise Portal Platform in action. + </para> + </chapter>