[portal-commits] JBoss Portal SVN: r14005 - in docs/enterprise/trunk/Installation_Guide: en-US and 1 other directory.

Author: smumford Date: 2011-07-25 20:37:04 -0400 (Mon, 25 Jul 2011) New Revision: 14005 Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml docs/enterprise/trunk/Installation_Guide/publican.cfg Log: Update old or broken URLs in hyperlinks. Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -3,29 +3,28 @@ ]> <bookinfo id="Installation_Guide_JBoss_Enterprise_Portal_Platform"> - <title>Installation Guide</title> - <subtitle>An Installation Guide for &PRODUCT;</subtitle> - <edition>1</edition> - <pubsnumber>1.3</pubsnumber> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>4.3</productnumber> - <pubdate>Jan, 2009</pubdate> - <isbn>N/A</isbn> - <abstract><para>This Installation Guide documents relevant information regarding + <title>Installation Guide</title> + <subtitle>An Installation Guide for &PRODUCT;</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>4.3</productnumber> + <edition>1</edition> + <pubsnumber>1.4</pubsnumber> + + <abstract><para>This Installation Guide documents relevant information regarding the installation of JBoss Enterprise Portal Platform</para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/redhat-logo.svg" /> - </imageobject> - </inlinemediaobject> - </corpauthor> - <copyright> - <year>&YEAR;</year> - <holder>&HOLDER;</holder> - </copyright> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/redhat-logo.svg" /> + </imageobject> + </inlinemediaobject> + </corpauthor> + <copyright> + <year>&YEAR;</year> + <holder>&HOLDER;</holder> + </copyright> + <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </bookinfo> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -2,46 +2,46 @@ <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <chapter> - <title>Database Configuration</title> + <title>Database Configuration</title> - <section id="sect-Portal_EAP-Configuration-Installing_an_RDBMS_JDBC_connector"> - <title>Installing an RDBMS JDBC connector</title> - <para> - A relational database management system (RDBMS) Java Database Connectivity (JDBC) connector is required for &JBEPP; to communicate with a database. - &JBEPP; comes bundled with Hypersonic SQL (HSQL) database so that users can get started up and running quickly without having to setup - database initially. However, HSQL should not be used in production environment. Removing HSQL is simply a matter of removing - <filename>JBOSS_DIST/jboss-as/server/$CONFIG/deploy/portal-hsql-ds.xml</filename>. Test suites have been run against - the <trademark class="registered">Oracle</trademark> 9, <trademark class="registered">Oracle</trademark> 10, <trademark class="registered">Microsoft SQL Server</trademark>, - MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases are recommended for production use. Please refer to your database documentation for the correct - RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be downloaded from <ulink url="http://www.mysql.com/products/connector/j/"></ulink>;, and the - PostgreSQL RDBMS JDBC connector can be downloaded from <ulink url="http://jdbc.postgresql.org/download.html"></ulink>;. - </para> - <para> - Refer to the help files in each download for installation instructions. In most cases, the RDBMS JDBC connector comes as a <computeroutput>.jar</computeroutput> file. Copy this file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/lib/</filename> directory. - </para> - </section> - - <section id="sect-Portal_EAP-Configuration-Datasource_Descriptors"> - <title>Datasource Descriptors</title> - <para> - A Datasource descriptor is required for JBoss Portal to communicate with a database. Sample Datasource descriptor files are provided for the Hypersonic SQL, <trademark class="registered">Microsoft SQL Server</trademark>, MySQL, <trademark class="registered">Oracle</trademark>, and PostgreSQL databases. These can be found in the <filename>/jboss-as/docs/portal/setup/</filename> subdirectory where the <computeroutput>EPP <replaceable>x.x.x</replaceable> binary distribution</computeroutput> file was extracted to. For example, if EPP was extracted into the <filename>/jboss/</filename> directory, the sample Datasource descriptors would be in the <filename>/jboss/jboss-epp-<replaceable>x.x.x</replaceable>/jboss-as/docs/portal/setup</filename> directory. - </para> - <para> - The sample Datasource descriptors will work with default installations of external databases; however, you may need to configure the correct username and password. As well, the sample MySQL and PostgreSQL Datasource descriptors assume the name of the database to be <computeroutput>jbossportal</computeroutput>. - </para> - <para> - When copying a Datasource descriptor for MySQL, <trademark class="registered">Microsoft SQL Server</trademark>, PostgreSQL, or <trademark class="registered">Oracle</trademark> databases, change the <computeroutput>&lt;user-name&gt;<replaceable>portal</replaceable>&lt;/user-name&gt;</computeroutput> and <computeroutput>&lt;password&gt;<replaceable>portalpassword</replaceable>&lt;/password&gt;</computeroutput> sections to reflect the correct username and password for the user who has access to the jbossportal database. - </para> - <important> - <title>Different Datasource Descriptors</title> - <para> - Only have one Datasource descriptor in the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. For example, if you want to use a MySQL database, remove the <filename>portal-hsqldb-ds.xml</filename> file, and other descriptors, if they exists. - </para> - </important> - <para> - The following is an example Datasource descriptor file for MySQL 5: - </para> - <para> + <section id="sect-Portal_EAP-Configuration-Installing_an_RDBMS_JDBC_connector"> + <title>Installing an RDBMS JDBC connector</title> + <para> + A relational database management system (RDBMS) Java Database Connectivity (JDBC) connector is required for JBoss Enterprise Portal Platform to communicate with a database. + JBoss Enterprise Portal Platform comes bundled with Hypersonic SQL (HSQL) database so that users can get started up and running quickly without having to setup + database initially. However, HSQL should not be used in production environment. Removing HSQL is simply a matter of removing + <filename>JBOSS_DIST/jboss-as/server/$CONFIG/deploy/portal-hsql-ds.xml</filename>. Test suites have been run against + the <trademark class="registered">Oracle</trademark> 9, <trademark class="registered">Oracle</trademark> 10, <trademark class="registered">Microsoft SQL Server</trademark>, + MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases are recommended for production use. Please refer to your database documentation for the correct + RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be downloaded from <ulink url="http://www.mysql.com/products/connector/j/"></ulink>;, and the + PostgreSQL RDBMS JDBC connector can be downloaded from <ulink url="http://jdbc.postgresql.org/download.html"></ulink>;. + </para> + <para> + Refer to the help files in each download for installation instructions. In most cases, the RDBMS JDBC connector comes as a <computeroutput>.jar</computeroutput> file. Copy this file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/lib/</filename> directory. + </para> + </section> + + <section id="sect-Portal_EAP-Configuration-Datasource_Descriptors"> + <title>Datasource Descriptors</title> + <para> + A Datasource descriptor is required for JBoss Portal to communicate with a database. Sample Datasource descriptor files are provided for the Hypersonic SQL, <trademark class="registered">Microsoft SQL Server</trademark>, MySQL, <trademark class="registered">Oracle</trademark>, and PostgreSQL databases. These can be found in the <filename>/jboss-as/docs/portal/setup/</filename> subdirectory where the <computeroutput>EPP <replaceable>x.x.x</replaceable> binary distribution</computeroutput> file was extracted to. For example, if EPP was extracted into the <filename>/jboss/</filename> directory, the sample Datasource descriptors would be in the <filename>/jboss/jboss-epp-<replaceable>x.x.x</replaceable>/jboss-as/docs/portal/setup</filename> directory. + </para> + <para> + The sample Datasource descriptors will work with default installations of external databases; however, you may need to configure the correct username and password. As well, the sample MySQL and PostgreSQL Datasource descriptors assume the name of the database to be <computeroutput>jbossportal</computeroutput>. + </para> + <para> + When copying a Datasource descriptor for MySQL, <trademark class="registered">Microsoft SQL Server</trademark>, PostgreSQL, or <trademark class="registered">Oracle</trademark> databases, change the <computeroutput>&lt;user-name&gt;<replaceable>portal</replaceable>&lt;/user-name&gt;</computeroutput> and <computeroutput>&lt;password&gt;<replaceable>portalpassword</replaceable>&lt;/password&gt;</computeroutput> sections to reflect the correct username and password for the user who has access to the jbossportal database. + </para> + <important> + <title>Different Datasource Descriptors</title> + <para> + Only have one Datasource descriptor in the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. For example, if you want to use a MySQL database, remove the <filename>portal-hsqldb-ds.xml</filename> file, and other descriptors, if they exists. + </para> + </important> + <para> + The following is an example Datasource descriptor file for MySQL 5: + </para> + <para> <screen> &lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;datasources&gt; @@ -55,8 +55,8 @@ &lt;/local-tx-datasource&gt; &lt;/datasources&gt; </screen> - </para> - </section> + </para> + </section> </chapter> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -151,7 +151,7 @@ <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Table_Errors"> <title>MySQL Table Errors</title> <para> - Tables are set up automatically when JBoss Portal first starts. Initially, two users will be stored in the jbossportal MySQL database: a standard user with the username user, and the password user, and an administrative user with the username admin, and the password admin. Since the database tables are created during initial startup, errors such as the following may occur, but are safe to ignore: + Tables are set up automatically when JBoss Portal first starts. Initially, two users will be stored in the jbossportal MySQL database: a standard user with the username user, and the password user, and an administrative user with the username admin, and the password admin. Since the database tables are created during initial start up, errors such as the following may occur, but are safe to ignore: </para> </formalpara> <para> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -3,354 +3,354 @@ ]> <chapter id="Getting_Started"> - <title>Getting Started</title> - <section id="Getting_Started-Pre_Requisites"> - <title>Pre-Requisites</title> - <para> - You must have adequate disk space<!--TODO how much --> to install JDK and &JBEPP; while also allowing enough space for your applications. Before installing &JBEPP; 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. However, there are a few Operating System-specific issues that you should be aware of. Refer to <ulink url="http://www.jboss.org/community/docs/DOC-10687"></uli... for more information. - </para> - <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements"> - <title>Hardware and Operating System Requirements</title> - - <para>For the latest information on supported Operating System / JVM combinations and supported Database platforms, please refer to <ulink url="http://www.jboss.com/products/platforms/application/testedconfi...;. - </para> - <!-- <para> - The following is a list of supported operating systems and JVM version combination: - </para> - - <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> - <tbody> - <row> - <entry> - <emphasis>Operating System</emphasis> - </entry> - <entry> - <emphasis>JVM Version</emphasis> - </entry> - </row> - <row> - <entry> - RHEL 4.5 x86 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - RHEL 4.5 x86_64 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - RHEL 5 x86 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - RHEL 5 x86_64 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - RHEL 4.5 x86 - </entry> - <entry> - BEA JRockit 1.5 latest - </entry> - </row> - <row> - <entry> - RHEL 4.5 x86_64 - </entry> - <entry> - BEA JRockit 1.5 latest - </entry> - </row> - <row> - <entry> - RHEL 5 x86 - </entry> - <entry> - BEA JRockit 1.5 latest - </entry> - </row> - <row> - <entry> - RHEL 5 x86_64 - </entry> - <entry> - BEA JRockit 1.5 latest - </entry> - </row> - <row> - <entry> - Solaris SPARC 9 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - MS-Windows 2003 x86 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - MS-Windows 2003 x86_64 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - MS-Windows 2003 x86 - </entry> - <entry> - BEA JRockit 1.5 latest - </entry> - </row> - <row> - <entry> - MS-Windows 2003 x86_64 - </entry> - <entry> - BEA JRockit 1.5 latest - </entry> - </row> - <row> - <entry> - Solaris SPARC 10 - </entry> - <entry> - Sun JVM 1.5 latest - </entry> - </row> - <row> - <entry> - HP 11i 1,2 RISC - </entry> - <entry> - HP JVM - </entry> - </row> - <row> - <entry> - HP 11i, 1,2 ia64 - </entry> - <entry> - HP JVM - </entry> - </row> - </tbody> - </tgroup> - </table> - - <para> - The following is a list of supported databases and database drivers: - </para> - - <table> - <title> - Supported Database / Database driver Combinations. - </title> + <title>Getting Started</title> + <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 Portal Platform 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. However, there are a few Operating System-specific issues that you should be aware of. Refer to <ulink url="http://www.jboss.org/community/docs/DOC-10687"></uli... for more information. + </para> + <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements"> + <title>Hardware and Operating System Requirements</title> + + <para>For the latest information on supported Operating System / JVM combinations and supported Database platforms, please refer to <ulink url="http://www.jboss.com/products/platforms/application/testedconfi...;. + </para> + <!-- <para> + The following is a list of supported operating systems and JVM version combination: + </para> + + <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> + <tbody> + <row> + <entry> + <emphasis>Operating System</emphasis> + </entry> + <entry> + <emphasis>JVM Version</emphasis> + </entry> + </row> + <row> + <entry> + RHEL 4.5 x86 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + RHEL 4.5 x86_64 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + RHEL 5 x86 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + RHEL 5 x86_64 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + RHEL 4.5 x86 + </entry> + <entry> + BEA JRockit 1.5 latest + </entry> + </row> + <row> + <entry> + RHEL 4.5 x86_64 + </entry> + <entry> + BEA JRockit 1.5 latest + </entry> + </row> + <row> + <entry> + RHEL 5 x86 + </entry> + <entry> + BEA JRockit 1.5 latest + </entry> + </row> + <row> + <entry> + RHEL 5 x86_64 + </entry> + <entry> + BEA JRockit 1.5 latest + </entry> + </row> + <row> + <entry> + Solaris SPARC 9 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + MS-Windows 2003 x86 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + MS-Windows 2003 x86_64 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + MS-Windows 2003 x86 + </entry> + <entry> + BEA JRockit 1.5 latest + </entry> + </row> + <row> + <entry> + MS-Windows 2003 x86_64 + </entry> + <entry> + BEA JRockit 1.5 latest + </entry> + </row> + <row> + <entry> + Solaris SPARC 10 + </entry> + <entry> + Sun JVM 1.5 latest + </entry> + </row> + <row> + <entry> + HP 11i 1,2 RISC + </entry> + <entry> + HP JVM + </entry> + </row> + <row> + <entry> + HP 11i, 1,2 ia64 + </entry> + <entry> + HP JVM + </entry> + </row> + </tbody> + </tgroup> + </table> + + <para> + The following is a list of supported databases and database drivers: + </para> + + <table> + <title> + Supported Database / Database driver Combinations. + </title> - <tgroup cols="2"> - <colspec colnum="1" colname="DB" colwidth="1*"></colspec> - <colspec colnum="2" colname="DB_driver" colwidth="1*"></colspec> - <tbody> - <row> - <entry> - <emphasis>Database</emphasis> - </entry> - <entry> - <emphasis>Database driver</emphasis> - </entry> - </row> - <row> - <entry> - Oracle 9i - </entry> - <entry> - Oracle thin driver - </entry> - </row> - <row> - <entry> - Oracle 10g R2 - </entry> - <entry> - Oracle thin driver - </entry> - </row> - <row> - <entry> - Microsoft SQL Server 2005 - </entry> - <entry> - Microsoft JDBC Driver - </entry> - </row> - <row> - <entry> - MySQL 5.0 - </entry> - <entry> - MySQL Driver - </entry> - </row> - <row> - <entry> - Postgres SQL 8.1 - </entry> - <entry> - Postgres Driver - </entry> - </row> - </tbody> - </tgroup> - </table> - <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.5</emphasis> before you install &JBEPP;. 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 5.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. - <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.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> - <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_using_RHN"> - <title>Installing and Configuring 32-bit Sun JDK 5.0 using RHN</title> - <listitem> - <para> - Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplementary channel for your Linux variant and architecture. Depending on the architecture, the channel names are: - </para> - <para> - rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5 - </para> - <para> - The <command moreinfo="none">java-1.5.0-bea</command>, - <command moreinfo="none">java-1.5.0-ibm</command> and - <command moreinfo="none">java-1.5.0-sun</command> SDKs are available from - these channels. Make sure you also install the - <command moreinfo="none">-devel</command> subpackages. - </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.5.0</command> (setting <command moreinfo="none">java_sdk_1.5.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.5.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_32_bit_Sun_JDK_5.0_on_a_generic_Linux_platform"> - <title>Installing and Configuring 32-bit Sun JDK 5.0 on a generic Linux platform</title> - <listitem> - <para> - Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun&#39;s website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">&l...;. Choose "JDK 5.0 Update &lt;x&gt;" (where x is the latest update number) for download and then select "RPM in self-extracting" file for Linux<footnote><para>Make sure you choose the appropriate file for your platform.</para></footnote>. Read the instructions on Sun&#39;s website for installing the JDK. - </para> - </listitem> - <listitem> - <para> - If you don&#39;t want to use SysV service scripts you can install the "self-extracting file" for Linux instead of choosing the "RPM in self-extracting" file. In that case you can skip the next step mentioned here. But it is recommended to use the SysV service scripts for production servers. - </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>. + <tgroup cols="2"> + <colspec colnum="1" colname="DB" colwidth="1*"></colspec> + <colspec colnum="2" colname="DB_driver" colwidth="1*"></colspec> + <tbody> + <row> + <entry> + <emphasis>Database</emphasis> + </entry> + <entry> + <emphasis>Database driver</emphasis> + </entry> + </row> + <row> + <entry> + Oracle 9i + </entry> + <entry> + Oracle thin driver + </entry> + </row> + <row> + <entry> + Oracle 10g R2 + </entry> + <entry> + Oracle thin driver + </entry> + </row> + <row> + <entry> + Microsoft SQL Server 2005 + </entry> + <entry> + Microsoft JDBC Driver + </entry> + </row> + <row> + <entry> + MySQL 5.0 + </entry> + <entry> + MySQL Driver + </entry> + </row> + <row> + <entry> + Postgres SQL 8.1 + </entry> + <entry> + Postgres Driver + </entry> + </row> + </tbody> + </tgroup> + </table> + <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.5</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 5.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. + <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.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> + <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_using_RHN"> + <title>Installing and Configuring 32-bit Sun JDK 5.0 using RHN</title> + <listitem> + <para> + Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplementary channel for your Linux variant and architecture. Depending on the architecture, the channel names are: + </para> + <para> + rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5 + </para> + <para> + The <command moreinfo="none">java-1.5.0-bea</command>, + <command moreinfo="none">java-1.5.0-ibm</command> and + <command moreinfo="none">java-1.5.0-sun</command> SDKs are available from + these channels. Make sure you also install the + <command moreinfo="none">-devel</command> sub-packages. + </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.5.0</command> (setting <command moreinfo="none">java_sdk_1.5.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.5.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_32_bit_Sun_JDK_5.0_on_a_generic_Linux_platform"> + <title>Installing and Configuring 32-bit Sun JDK 5.0 on a generic Linux platform</title> + <listitem> + <para> + Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun&#39;s website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">&l...;. Choose "JDK 5.0 Update &lt;x&gt;" (where x is the latest update number) for download and then select "RPM in self-extracting" file for Linux<footnote><para>Make sure you choose the appropriate file for your platform.</para></footnote>. Read the instructions on Sun&#39;s website for installing the JDK. + </para> + </listitem> + <listitem> + <para> + If you don&#39;t want to use SysV service scripts you can install the "self-extracting file" for Linux instead of choosing the "RPM in self-extracting" file. In that case you can skip the next step mentioned here. But it is recommended to use the SysV service scripts for production servers. + </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> - </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> + </para> + </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.5.0_11 is the JDK installation directory. export JAVA_HOME=/usr/java/jdk1.5.0_11 export PATH=$PATH:$JAVA_HOME/bin </programlisting> - Set this variable for the user account doing 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.5 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. - <itemizedlist> - <title>Select alternatives for java, javac and java_sdk_1.5.0</title> - <listitem> - <para> - As root, type the following command at the shell prompt and you should see something like this: <programlisting> + Set this variable for the user account doing 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.5 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. + <itemizedlist> + <title>Select alternatives for java, javac and java_sdk_1.5.0</title> + <listitem> + <para> + As root, type the following command at the shell prompt and you should see something like this: <programlisting> [root@vsr ~]$ /usr/sbin/alternatives --config java There are 2 programs which provide &#39;java&#39;. Selection Command @@ -359,15 +359,15 @@ *+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java Enter to keep the current selection[+], or type selection number: </programlisting> - Make sure the Sun version [<literal>jre-1.5.0-sun</literal> in this case] is selected (marked with a &#39;+&#39; 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.5.0. <programlisting> + Make sure the Sun version [<literal>jre-1.5.0-sun</literal> in this case] is selected (marked with a &#39;+&#39; 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.5.0. <programlisting> [root@vsr ~]$ /usr/sbin/alternatives --config javac There are 1 programs which provide &#39;javac&#39;. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac Enter to keep the current selection[+], or type selection number: @@ -375,220 +375,220 @@ <programlisting> [root@vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0 There are 1 programs which provide &#39;java_sdk_1.5.0&#39;. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.5.0-sun Enter to keep the current selection[+], or type selection number: </programlisting> - You should verify that java, javac and java_sdk_1.5.0 all point to the same manufacturer and version. - </para> - </listitem> - </itemizedlist> - </para> - <note> - <para> - You can always override this step by setting the <literal>JAVA_HOME</literal> environment variable as explained in the previous step. - </para> - </note> - </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> + You should verify that java, javac and java_sdk_1.5.0 all point to the same manufacturer and version. + </para> + </listitem> + </itemizedlist> + </para> + <note> + <para> + You can always override this step by setting the <literal>JAVA_HOME</literal> environment variable as explained in the previous step. + </para> + </note> + </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.5.0_11" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing) </programlisting> - </para> - </listitem> - </itemizedlist> - <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_Microsoft_Windows"> - <title>Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Windows</title> - <listitem> - <para> - Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun&#39;s website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">&l...;. Choose "JDK 5.0 Update &lt;x&gt;" (where x is the latest update number) for download and then select your Windows Platform options to perform the installation. - </para> - </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.5.0_11\</literal>. 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.5.0_11\jre\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button. - </para> - </listitem> - </itemizedlist> - </para> - </section> + </para> + </listitem> + </itemizedlist> + <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_Microsoft_Windows"> + <title>Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Windows</title> + <listitem> + <para> + Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun&#39;s website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">&l...;. Choose "JDK 5.0 Update &lt;x&gt;" (where x is the latest update number) for download and then select your Windows Platform options to perform the installation. + </para> + </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.5.0_11\</literal>. 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.5.0_11\jre\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button. + </para> + </listitem> + </itemizedlist> + </para> + </section> - </section> - <!-- - <section id="Getting_Started-Components_of_JBoss_Enterprise_Application_Platform"> - <title>Components of &JBEPP;</title> - - <para>For current information on the revision level of included components please refer to <ulink url="http://www.jboss.com/products/platforms/portals/components"...;. - </para> - --> - <!--<para> - Below is a listing of the components of &JBEPP; and their revision level at the time of writing. For an updated list of component revision levels please refer to <ulink url="http://www.redhat.com/docs/manuals/jboss">http://www.re...;. - </para> - - <para> - <table id="Components_of_JBoss_Enterprise_Application_Platform_version_4.2-Application_Platform_4.2"> - <title>Application Platform 4.2</title> - <tgroup cols="2"> - <colspec colname="Project" colnum="1" colwidth="4*"></colspec> - <colspec colname="Version" colnum="2" colwidth="4*"></colspec> - <thead> - <row> - <entry> - Project - </entry> - <entry> - Version - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - Hibernate - </entry> - <entry> - 3.2.4.SP1_CP01 - </entry> - </row> - <row> - <entry> - Hibernate Entity Manager - </entry> - <entry> - 3.2.1 - </entry> - </row> - <row> - <entry> - Hibernate Annotations - </entry> - <entry> - 3.2.1 - </entry> - </row> - <row> - <entry> - JBoss AS - </entry> - <entry> - 4.2.0 - </entry> - </row> - <row> - <entry> - JBoss MQ - </entry> - <entry> - 4.2.0 - </entry> - </row> - <row> - <entry> - JBoss Web - </entry> - <entry> - 2.0.0 - </entry> - </row> - <row> - <entry> - JBoss Transactions - </entry> - <entry> - 4.2.3.SP4 - </entry> - </row> - <row> - <entry> - JTA - </entry> - <entry> - 1.0.1B - </entry> - </row> - <row> - <entry> - JBoss EJB3 - </entry> - <entry> - RC10 - </entry> - </row> - <row> - <entry> - JBoss WS - </entry> - <entry> - 1.2.1 - </entry> - </row> - <row> - <entry> - JBoss AOP - </entry> - <entry> - 1.5.5 - </entry> - </row> - <row> - <entry> - JBoss Remoting - </entry> - <entry> - 2.0.0.SP4 - </entry> - </row> - <row> - <entry> - JBoss Serialization - </entry> - <entry> - 1.0.3 - </entry> - </row> - <row> - <entry> - JBoss Cache - </entry> - <entry> - 1.4.1.SP3 - </entry> - </row> - <row> - <entry> - JGroups - </entry> - <entry> - 2.4.1.SP3 - </entry> - </row> - <row> - <entry> - JBoss Seam - </entry> - <entry> - 1.2.0.AP - </entry> - </row> - <row> - <entry> - jBPM (JPDL) - </entry> - <entry> - 3.1.4 (Seam dependency) - </entry> - </row> - </tbody> - </tgroup> - </table> - </para> --> - <!-- - </section> + </section> + <!-- + <section id="Getting_Started-Components_of_JBoss_Enterprise_Application_Platform"> + <title>Components of JBoss Enterprise Portal Platform</title> + + <para>For current information on the revision level of included components please refer to <ulink url="http://www.jboss.com/products/platforms/portals/components"...;. + </para> + --> + <!--<para> + Below is a listing of the components of JBoss Enterprise Portal Platform and their revision level at the time of writing. For an updated list of component revision levels please refer to <ulink url="http://www.redhat.com/docs/manuals/jboss">http://www.re...;. + </para> + + <para> + <table id="Components_of_JBoss_Enterprise_Application_Platform_version_4.2-Application_Platform_4.2"> + <title>Application Platform 4.2</title> + <tgroup cols="2"> + <colspec colname="Project" colnum="1" colwidth="4*"></colspec> + <colspec colname="Version" colnum="2" colwidth="4*"></colspec> + <thead> + <row> + <entry> + Project + </entry> + <entry> + Version + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + Hibernate + </entry> + <entry> + 3.2.4.SP1_CP01 + </entry> + </row> + <row> + <entry> + Hibernate Entity Manager + </entry> + <entry> + 3.2.1 + </entry> + </row> + <row> + <entry> + Hibernate Annotations + </entry> + <entry> + 3.2.1 + </entry> + </row> + <row> + <entry> + JBoss AS + </entry> + <entry> + 4.2.0 + </entry> + </row> + <row> + <entry> + JBoss MQ + </entry> + <entry> + 4.2.0 + </entry> + </row> + <row> + <entry> + JBoss Web + </entry> + <entry> + 2.0.0 + </entry> + </row> + <row> + <entry> + JBoss Transactions + </entry> + <entry> + 4.2.3.SP4 + </entry> + </row> + <row> + <entry> + JTA + </entry> + <entry> + 1.0.1B + </entry> + </row> + <row> + <entry> + JBoss EJB3 + </entry> + <entry> + RC10 + </entry> + </row> + <row> + <entry> + JBoss WS + </entry> + <entry> + 1.2.1 + </entry> + </row> + <row> + <entry> + JBoss AOP + </entry> + <entry> + 1.5.5 + </entry> + </row> + <row> + <entry> + JBoss Remoting + </entry> + <entry> + 2.0.0.SP4 + </entry> + </row> + <row> + <entry> + JBoss Serialization + </entry> + <entry> + 1.0.3 + </entry> + </row> + <row> + <entry> + JBoss Cache + </entry> + <entry> + 1.4.1.SP3 + </entry> + </row> + <row> + <entry> + JGroups + </entry> + <entry> + 2.4.1.SP3 + </entry> + </row> + <row> + <entry> + JBoss Seam + </entry> + <entry> + 1.2.0.AP + </entry> + </row> + <row> + <entry> + jBPM (JPDL) + </entry> + <entry> + 3.1.4 (Seam dependency) + </entry> + </row> + </tbody> + </tgroup> + </table> + </para> --> + <!-- + </section> --> </chapter> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -9,7 +9,7 @@ <title>Download</title> <para> - You can download the zip file from the <ulink url="https://access.redhat.com/jbossnetwork/restricted/listSoftware.... Customer Service Portal</ulink> (CSP). + You can download the zip file from the <ulink url="https://access.redhat.com/jbossnetwork/restricted/listSoftware.... Customer Service Portal</ulink> (CSP). </para> </section> @@ -18,7 +18,7 @@ <para> To install from a zip file, simply unzip the downloaded file to a directory of your choice. You can unzip the platform on any operating system that supports the zip format. Four types of server configurations will be included in your installation - minimal, default, production and all. - The Getting Started Guide of &JBEAP; as well as http://www.jboss.org/community/docs/DOC-12942 explain in detail the different server configuration file sets. + The JBoss Enterprise Application Platform <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. <itemizedlist> <listitem> @@ -45,7 +45,7 @@ <itemizedlist> <listitem> <para> - <literal>minimal</literal> server configuration has no Portal bits. It's there for the sake of consistency with &JBEAP; + <literal>minimal</literal> server configuration has no Portal bits. It is included for the sake of consistency with JBoss Enterprise Application Platform. </para> </listitem> <listitem> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -5,18 +5,18 @@ <chapter id="Introduction"> <title>Introduction</title> <para> - &JBEPP; is the open source implementation of the Java EE suite of services and Portal services running atop &JBEAP;. It comprises a set of offerings + JBoss Enterprise Portal Platform is the open source implementation of the Java EE suite of services and Portal services running atop JBoss Enterprise Application Platform. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. Its easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform. </para> <para> - Because it is Java-based, &JBEPP; is cross-platform and easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use. + Because it is Java-based, JBoss Enterprise Portal Platform is cross-platform and easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use. </para> <para> - Installing &JBEPP; is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist> + Installing JBoss Enterprise Portal Platform is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist> <listitem> <para> - How to install &JBEPP; + How to install JBoss Enterprise Portal Platform </para> </listitem> <listitem> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -3,9 +3,23 @@ ]> <appendix id="appe-Publican-Revision_History"> - <title>Revision History</title> - <simpara> - <revhistory> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>1-1.4</revnumber> + <date>Fri Jul 15 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Update old or broken URLs in hyperlinks.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>1-1.3</revnumber> <date>Fri Apr 08 2011</date> @@ -34,7 +48,7 @@ </simplelist> </revdescription> </revision> - </revhistory> - </simpara> + </revhistory> + </simpara> </appendix> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -5,7 +5,7 @@ <chapter id="Test_your_Installation"> <title>Test your Installation</title> <para> - After you have installed the JBoss Enterprise Portal 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> envirnoment variables as explained in <xref linkend="Post_Installation_Configuration"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/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: + 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"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/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> [user@localhost bin]$ ./run.sh @@ -42,7 +42,7 @@ </para> </note> <para> - Now open <literal>http://localhost:8080/portal</literal> in your web browser. (Make sure you dont have anything else already on your machine using that port).<footnote><para> + Now open <literal>http://localhost:8080/portal</literal> in your web browser. (Make sure you do not 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" />. </para> <para> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2011-07-26 00:37:04 UTC (rev 14005) @@ -3,9 +3,9 @@ ]> <chapter id="Uninstall_JBoss"> - <title>Uninstall JBoss</title> - <para> - As JBoss Enterprise Portal Platform was installed from a zipfile, you may uninstall it by simply deleting the &JBEPP; installed directory. - </para> + <title>Uninstall JBoss</title> + <para> + As JBoss Enterprise Portal Platform was installed from a <filename>zip</filename> file, you may uninstall it by simply deleting the JBoss Enterprise Portal Platform installed directory. + </para> </chapter> Modified: docs/enterprise/trunk/Installation_Guide/publican.cfg =================================================================== --- docs/enterprise/trunk/Installation_Guide/publican.cfg 2011-07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/publican.cfg 2011-07-26 00:37:04 UTC (rev 14005) @@ -5,3 +5,6 @@ xml_lang: en-US brand: JBoss +cvs_branch: DOCS-RHEL-6 +cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist +cvs_pkg: JBoss_Enterprise_Portal_Platform-Installation_Guide-4.3-web-__LANG__ \ No newline at end of file