Author: benlc Date: 2010-04-13 00:49:17 -0400 (Tue, 13 Apr 2010) New Revision: 2593 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Configuration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Databases.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation_Guide.ent portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Test_Your_Installation.xml Log: 'committing changes - removing entities to highlight edits as breaks hudson build' Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Configuration.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Configuration.xml 2010-04-13 02:06:38 UTC (rev 2592) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Configuration.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -5,29 +5,11 @@ ]> <chapter> <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 &PRODUCT; to communicate with a database. - &PRODUCT; 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> - - &START_EDIT; - <section id="sect-Portal_EAP-Configuration-Installing_an_RDBMS_JDBC_connectorE"> - <title>Installing an RDBMS JDBC connector</title> - <para> - A relational database management system (RDBMS) Java Database Connectivity (JDBC) connector is required for &PRODUCT; to communicate with a database. &PRODUCT; comes bundled with Hypersonic SQL (HSQL) database so that users can get up and running quickly without having to initially set up a database. However, HSQL should not be used in a production environment. Removing HSQL is simply a matter of removing <remark><filename>JBOSS_DIST/jboss-as/server/$CONFIG/deploy/hsql-ds.xml</filename>.</remark> @@ -43,65 +25,30 @@ 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 within the downloaded zip file. Copy this file into the <filename>$JBOSS_HOME/server/<replaceable>$CONFIG</replaceable>/lib/</filename> directory. </para> </section> - &END_EDIT; + <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; - &lt;local-tx-datasource&gt; - &lt;jndi-name&gt;PortalDS&lt;/jndi-name&gt; - &lt;connection-url&gt;jdbc:mysql://localhost:3306/jbossportal? - useServerPrepStmts=false&amp;amp&semi;jdbcCompliantTruncation=false&lt;/connection-url&gt; - &lt;driver-class&gt;com.mysql.jdbc.Driver&lt;/driver-class&gt; - &lt;user-name&gt;&lt;replaceable&gt;portal&lt;/replaceable&gt;&lt;/user-name&gt; - &lt;password&gt;&lt;replaceable&gt;portalpassword&lt;/replaceable&gt;&lt;/password&gt; - &lt;/local-tx-datasource&gt; -&lt;/datasources&gt; -</screen> - </para> - </section> - - &START_EDIT; - <section id="sect-Portal_EAP-Configuration-Datasource_DescriptorsE"> - <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 <remark><filename>$JBOSS_HOME/jboss-as/docs/examples/jca</filename></remark> 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 indicated in the mysql-ds.xml file displayed below, the sample MySQL and PostgreSQL Datasource descriptors assume the name of the database to be <remark><computeroutput>jbossdb</computeroutput></remark>. </para> <para> - Copy the required Datasource descriptor file to <filename>$JBOSS_HOME/server/<replaceable>$CONFIG</replaceable>/deploy/</filename> directory. 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 of the user who has access to the jbossportal database. + Copy the required Datasource descriptor file to the <filename>$JBOSS_HOME/server/<replaceable>$CONFIG</replaceable>/deploy/</filename> directory. 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 of the user who has access to the jbossportal database. </para> <important> - <title>Different Datasource Descriptors</title> + <title>Important: Various Datasource Descriptors</title> <para> - Ensure that there is only one Datasource descriptor in the <filename>$JBOSS_HOME/server/<replaceable>$CONFIG</replaceable>/deploy/</filename> directory. For example, if you want to use a MySQL database, remove the <filename>hsqldb-ds.xml</filename> file, and other descriptors, if they exists. For a default configuration this will require removing the <filename>gatein-ds.xml</filename> and <filename>hsqldb-ds.xml</filename> files. + Ensure that there is only one Datasource descriptor in the <filename>$JBOSS_HOME/server/<replaceable>$CONFIG</replaceable>/deploy/</filename> directory. For example, if you want to use a MySQL database, remove the <filename>hsqldb-ds.xml</filename> file and any other descriptors. For a default configuration this will require removing the <filename>gatein-ds.xml</filename> and <filename>hsqldb-ds.xml</filename> files to use a MySQL database. </para> </important> <para> The following is an example Datasource descriptor file for MySQL 5: </para> + <para><remark>Note to Reviewer</remark></para> + <para>This is copied directly from th sample provided in jboss-as/docs/examples/jca/</para> + <para><remark>End Note to Reviewer</remark></para> <para> <screen>&lt;?xml version="1.0" encoding="UTF-8"?&gt; @@ -144,7 +91,6 @@ &lt;/datasources&gt;</screen> </para> </section> - &END_EDIT; </chapter> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Databases.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Databases.xml 2010-04-13 02:06:38 UTC (rev 2592) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Databases.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -7,8 +7,7 @@ <chapter id="chap-Portal_EAP-Databases"> <title>Databases</title> <para> - The following chapter contains examples for how to use - MySQL databases to store JBoss Enterprise Portal user information. + The following chapter describes how to set up the JDBC connector, the MySQL database and the database user. </para> <section id="sect-Portal_EAP-Databases-Using_a_MySQL_Database"> @@ -19,26 +18,7 @@ The RDBMS JDBC MySQL connector is required for JBoss Portal to use a MySQL database: </para> </formalpara> - <orderedlist> - <listitem> - <para> - Navigate to the <ulink url="http://dev.mysql.com/downloads/connector/j/3.1.html">JDBC MySQL connector</ulink> section of dev.mysql.com. Download the <computeroutput>Source and Binaries (zip)</computeroutput> file. - </para> - </listitem> - <listitem> - <para> - Unzip the <filename>mysql-java-connector</filename> into the desired directory. It does not matter which directory is used. - </para> - </listitem> - <listitem> - <para> - Change into the directory where the <filename>mysql-java-connector</filename> was extracted to. Copy the <filename>mysql-connector-java-<replaceable>version-number</replaceable>-bin.jar</filename> file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/lib/</filename> directory. - </para> - </listitem> - </orderedlist> - &START_EDIT; - <orderedlist> <listitem> <para> @@ -56,9 +36,7 @@ </para> </listitem> </orderedlist> - - &END_EDIT; - + <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Data_Truncation_Errors"> <title>Data Truncation Errors</title> <para> @@ -71,25 +49,10 @@ </screen> </para> <para> - If you are running MySQL in strict mode, remove <computeroutput>STRICT_TRANS_TABLES</computeroutput> from the <computeroutput>sql-mode=</computeroutput> line, in the <filename>my.cnf</filename> file if you are running Linux, and from the <filename>my.cfg</filename> file if you are running <trademark class="registered">Windows</trademark>. For further information, please see <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=AvoidMySQL5DataTruncat...;. - </para> - &START_EDIT; - - <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Data_Truncation_ErrorsE"> - <title>Data Truncation Errors</title> - <para> - If you are running MySQL 5, data truncation errors such as the following may occur: - </para> - </formalpara> - <para> -<screen> -ERROR JDBCExceptionReporter Data truncation: Data too long for column &#39;jbp_viewrealemail&#39; at row 1 -</screen> - </para> - <para> If you are running MySQL in strict mode, remove <computeroutput>STRICT_TRANS_TABLES</computeroutput> from the <quote><computeroutput>sql-mode =</computeroutput></quote> line of the relevant configuration file. For Linux, this is the <filename>my.cnf</filename> file. For <trademark class="registered">Windows</trademark>, edit the <filename>my.cfg</filename> file. For further information, please see <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=AvoidMySQL5DataTruncat...;. </para> - &END_EDIT; + + <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_Database"> <title>Creating a MySQL Database</title> <para> @@ -151,89 +114,6 @@ </listitem> <listitem> <para> - Add a new user and give that user access to the jbossportal database. The following example adds a new user named <computeroutput>portal</computeroutput>, with the password <computeroutput>portalpassword</computeroutput>, and gives the portal user access to the jbossportal database. It is recommended that you change the password. Change <replaceable>portalpassword</replaceable> to change the password: - </para> - <para> -<screen> -mysql&gt; GRANT ALL PRIVILEGES ON jbossportal.* TO &#39;<replaceable>portal</replaceable>&#39;@&#39;localhost&#39; -IDENTIFIED BY &#39;<replaceable>portalpassword</replaceable>&#39; WITH GRANT OPTION; -</screen> - </para> - <para> - The output should be similar to the following: - </para> - <para> -<screen> -Query OK, 0 rows affected (0.00 sec) -</screen> - </para> - <para> - If you changed the portal user&#39;s password, also change the password in the MySQL Datasource descriptor. - </para> - </listitem> - </orderedlist> - &START_EDIT; - <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_DatabaseE"> - <title>Creating a MySQL Database</title> - <para> - If you have just installed MySQL, make sure the MySQL server is running, and then run the following command to set the root user password: - </para> - </formalpara> - <para> -<screen> -mysqladmin -u root password &#39;<replaceable>new-root-user-password</replaceable>&#39; -</screen> - </para> - <orderedlist> - <listitem> - <para> - Run the following command to log in to MySQL. Enter the root user password when prompted: - </para> - <para> -<screen> -mysql -u root -p -</screen> - </para> - </listitem> - <listitem> - <para> - Use the <command>CREATE DATABASE</command> command to create a new jbossportal database. Note: the rest of this guide, and configuration examples following here after, assume the database name to be jbossportal. If you change the database name, please change the name in all necessary configuration files: - </para> - <para> -<screen> -mysql&gt; CREATE DATABASE jbossportal; -</screen> - </para> - <para> - The output should be similar to the following: - </para> - <para> -<screen> -Query OK, 1 row affected (0.00 sec) -</screen> - </para> - <para> - At this point, the <command>SHOW DATABASES;</command> command should display the <command>jbossportal</command> database: - </para> - <para> -<screen> -mysql&gt; SHOW DATABASES; -+--------------------+ -| Database | -+--------------------+ -| information_schema | -| jbossportal | -| mysql | -+--------------------+ -3 rows in set (0.00 sec) -</screen> - </para> - <para> - It is safe to ignore the other databases. - </para> - </listitem> - <listitem> - <para> Add a new user and give that user access to the jbossportal database. The following example adds a new user named <computeroutput>portal</computeroutput>, with the password <computeroutput>portalpassword</computeroutput>. It is recommended that you choose a different password to the one supplied here by changing <replaceable>portalpassword</replaceable> to some other password: </para> <screen>CREATE USER 'portal'@'localhost' IDENTIFIED BY 'portalpassword';</screen> @@ -263,7 +143,7 @@ </note> </listitem> </orderedlist> - &END_EDIT; + <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Datasource_Descriptor"> <title>MySQL Datasource Descriptor</title> <para> @@ -273,25 +153,6 @@ <orderedlist> <listitem> <para> - Change into the <filename>setup</filename> subdirectory where JBoss Portal was extracted to. Copy the MySQL Datasource descriptor into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. If you are running MySQL 5, use <filename>portal-mysql5-ds.xml</filename>, otherwise use <filename>portal-mysql-ds.xml</filename>. - </para> - </listitem> - <listitem> - <para> - Update 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 in the Datasource descriptor to reflect the correct username and password for the user who has access to the jbossportal database. - </para> - </listitem> - </orderedlist> - &START_EDIT; - <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Datasource_DescriptorE"> - <title>MySQL Datasource Descriptor</title> - <para> - To install the MySQL Datasource descriptor: - </para> - </formalpara> - <orderedlist> - <listitem> - <para> Copy the MySQL Datasource descriptor - <filename>$JBOSS_HOME/docs/examples/jca/mysql-ds.xml</filename> - into the <filename>$JBOSS_HOME/server/<replaceable>$CONFIG</replaceable>/deploy/</filename> directory. </para> </listitem> @@ -329,7 +190,7 @@ <itemizedlist> <listitem> <para> - This example uses the <literal>portalpassword</literal> password. Enter this or the password chosen at <xref linkend="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_DatabaseE"></xref>. + This example uses the <literal>portalpassword</literal> password. Enter this or the password chosen at <xref linkend="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_Database"></xref>. </para> </listitem> </itemizedlist> @@ -339,7 +200,6 @@ </para> </listitem> </orderedlist> - &END_EDIT; <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Table_Errors"> <title>MySQL Table Errors</title> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml 2010-04-13 02:06:38 UTC (rev 2592) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Getting_Started.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -241,15 +241,10 @@ <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 &PRODUCT;. 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. - </para> - &START_EDIT; <para> You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install &PRODUCT;. 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> - &END_EDIT; <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> @@ -274,56 +269,7 @@ </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> - &START_EDIT; + <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> @@ -387,9 +333,7 @@ <para> As root, issue the following command: </para> - <screen> - <command moreinfo="none">/usr/sbin/alternatives --config java</command> - </screen> + <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> @@ -399,97 +343,7 @@ </para> </listitem> </itemizedlist> - &END_EDIT; - <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> -#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> -[root@vsr ~]$ /usr/sbin/alternatives --config java -There are 2 programs which provide &#39;java&#39;. -Selection Command ------------------------------------------------ - 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java -*+ 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> -[root@vsr ~]$ /usr/sbin/alternatives --config javac -There are 1 programs which provide &#39;javac&#39;. - Selection Command ------------------------------------------------ -*+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac -Enter to keep the current selection[+], or type selection number: -</programlisting> -<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 ------------------------------------------------ -*+ 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> -[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> - &START_EDIT; + <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> @@ -530,11 +384,11 @@ <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> - &START_NOTE; + <para><remark>Note to Reviewer</remark></para> <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> - &END_NOTE; + <para><remark>End Note to Reviewer</remark></para> </listitem> <listitem> <para> @@ -559,21 +413,26 @@ <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 + 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 &#39;java&#39;. Selection Command ----------------------------------------------- 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java *+ 2 /usr/lib/jvm/jre-1.6.0-sun/bin/java Enter to keep the current selection[+], or type selection number: + </programlisting> + <para> Make sure the Sun version [<literal>jre-1.6.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.6.0. <programlisting> + 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 &#39;javac&#39;. Selection Command @@ -589,14 +448,15 @@ *+ 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. - &START_NOTE; - Better to use java-1.6.0-variant rather than java-1.6.0-sun as could be sun or openjdk. Also include openJDK download site info http://openjdk.java.net/install/ ? - &END_NOTE; </para> </listitem> </itemizedlist> </para> + <para><remark>Note to Reviewer</remark></para> + <para>Better to use java-1.6.0-variant rather than java-1.6.0-sun as could be sun or openjdk. Also include openJDK download site info http://openjdk.java.net/install/ ?</para> + <para><remark>End Note to Reviewer</remark></para> </listitem> <listitem> <para> @@ -609,21 +469,7 @@ </para> </listitem> </itemizedlist> - &END_EDIT; - <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> - &START_EDIT; + <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> @@ -686,7 +532,6 @@ </para> </listitem> </itemizedlist> - &END_EDIT; </section> </section> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml 2010-04-13 02:06:38 UTC (rev 2592) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -14,36 +14,11 @@ You can download the zip file from the JBoss Customer Service Portal (CSP), located at <ulink url="https://network.jboss.com">https://network.jboss.com</ulink>. </para> </section> - + <section id="Installing"> <title>Installing</title> <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. - - <itemizedlist> - <listitem> - <para> - Unzip <literal>jboss-epp-<replaceable>&lt;release&gt;</replaceable>.zip</literal> to extract the archive contents into the location of your choice. You can do this using the JDK <literal>jar</literal> tool (or any other ZIP extraction tool). <programlisting> - [vsr]$ <literal>cd jbeppinstallationdir</literal> - [vsr]$ <literal>jar -xvf jboss-epp-<replaceable>&lt;release&gt;</replaceable>.zip</literal></programlisting> - </para> - </listitem> - <listitem> - <para> - You are done with the installation! You should now have a directory called <filename>jboss-epp-<replaceable>&lt;release&gt;</replaceable></filename>. Refer to the Getting Started Guide to understand and explore the Platform Directory Structure. - </para> - </listitem> - </itemizedlist> - </para> - </section> - - &START_EDIT; - <section id="InstallingE"> - <title>Installing</title> - - <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. Six types of server configurations will be included in your installation - minimal, default, production, all, standard and web. 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. @@ -63,7 +38,7 @@ </itemizedlist> </para> </section> - &END_EDIT; + <section id="server-config-differences"> <title>Choosing a server configuration</title> <para> @@ -72,43 +47,6 @@ <itemizedlist> <listitem> <para> - <literal>minimal</literal> server configuration has no Portal bits. It's there for the sake of consistency with &JBEAP; - </para> - </listitem> - <listitem> - <para> - <literal>default</literal> server configuration has non-clustered Portal bits <literal>jboss-portal.sar</literal> in - <literal>deploy</literal> folder. - </para> - </listitem> - <listitem> - <para> - <literal>all</literal> server configuration has clustered Portal bits <literal>jboss-portal-ha.sar</literal> in - <literal>deploy</literal> folder. - </para> - </listitem> - <listitem> - <para> - <literal>production</literal> server configuration has clustered Portal bits <literal>jboss-portal-ha.sar</literal> and this is - the sever that gets started by default. This server configuration has several optimizations such as logging, memory size etc. - If you do not need clustered portal version and want to use this optimized server configuration, you simply need to copy the directory - <literal>jboss-portal.sar</literal> from <literal>default/deploy</literal> to <literal>production/deploy</literal>. Don't forget to - remove <literal>jboss-portal-ha.sar</literal> though. - </para> - </listitem> - </itemizedlist> - </para> - </section> - &START_EDIT; - - <section id="server-config-differencesE"> - <title>Choosing a server configuration</title> - <para> - The important differences as far as Portal is concerned are: - - <itemizedlist> - <listitem> - <para> the <literal>minimal</literal>, <literal>web</literal> and <literal>standard</literal> server configurations do not contain any Portal relevant components. These directories exist for the sake of consistency with &JBEAP; </para> </listitem> @@ -138,8 +76,5 @@ </note> </para> </section> - - &END_EDIT; - </chapter> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation_Guide.ent =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation_Guide.ent 2010-04-13 02:06:38 UTC (rev 2592) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Installation_Guide.ent 2010-04-13 04:49:17 UTC (rev 2593) @@ -5,7 +5,7 @@ <!ENTITY YEAR "2010"> <!ENTITY HOLDER "Red Hat, Inc"> <!ENTITY RHEL "Red Hat Enterprise Linux"> -<!ENTITY START_EDIT "<para><remark>&lt;!-- Start Edit</remark></para>"> -<!ENTITY END_EDIT "<para><remark>End Edit --&gt;</remark></para>"> -<!ENTITY START_NOTE "<para><remark>&lt;!-- Start Note to Reviewer</remark></para>"> -<!ENTITY END_NOTE "<para><remark>End Note to Reviewer --&gt;</remark></para>"> +<!ENTITY START_EDIT "<formalpara><title><remark>&lt;!-- Start Edit</remark></title><para></para></formalpara>"> +<!ENTITY END_EDIT "<formalpara><title><remark>End Edit --&gt;</remark></title><para></para></formalpara>"> +<!ENTITY START_NOTE "<formalpara><title><remark>&lt;!-- Start Note to Reviewer</remark></title><para></para></formalpara>"> +<!ENTITY END_NOTE "<formalpara><title><remark>End Note to Reviewer --&gt;</remark></title><para></para></formalpara>"> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml 2010-04-13 02:06:38 UTC (rev 2592) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Post_Installation.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -4,39 +4,11 @@ %BOOK_ENTITIES; ]> <chapter id="Post_Installation_Configuration"> - <title>Post Installation Configuration</title> + <title>Post Installation Configuration</title> <section id="Set_JBOSS_HOME"> <title> Set JBOSS_HOME Environment Variable </title> - <formalpara> - <title> - On a Linux Platform - </title> - <para> - Create an environment variable that points to the installation directory (<filename>JBOSS_DIST/jboss-as</filename>) and call it <literal>JBOSS_HOME</literal>. Add <literal>$JBOSS_HOME/bin</literal> to the system path to be able to run the server from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. - <programlisting> -#In this example /home/user/jboss-epp-4.3/jboss-as is the installation directory. - export JBOSS_HOME=/home/user/jboss-epp-4.3/jboss-as - export PATH=$PATH:$JBOSS_HOME/bin - </programlisting> - Set this variable for the user account(s) that will run the server. - </para> - </formalpara> - <formalpara> - <title> - On Microsoft Windows - </title> - <para> - Create an environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: C:\Program Files\jboss-epp-4.3\jboss-as\. In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: C:\Program Files\jboss-epp-4.3\jboss-as\bin. 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> - </formalpara> - </section> - &START_EDIT; - <section id="Set_JBOSS_HOMEE"> - <title> - Set JBOSS_HOME Environment Variable - </title> <para><remark>Minor edit changed 4.3 to 5.0 in path to installation directory.</remark></para> <formalpara> <title> @@ -60,8 +32,7 @@ Create an environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: C:\Program Files\jboss-epp-5.0\jboss-as\. In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: C:\Program Files\jboss-epp-5.0\jboss-as\bin. 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> </formalpara> - </section> - &END_EDIT; + </section> <section id="Adjust_Memory_Settings"> <title>Adjust memory settings</title> @@ -69,20 +40,6 @@ The default configuration for the server to start with, if no other configuration is specified, is the production configuration. It is recommended to run the example Seam applications that are included with the documentation using the production configuration. </para> <para> - To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> with these recommended values: -<programlisting> - -Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m -</programlisting> - </para> - </section> - &START_EDIT; - - <section id="Adjust_Memory_SettingsE"> - <title>Adjust memory settings</title> - <para> - The default configuration for the server to start with, if no other configuration is specified, is the production configuration. It is recommended to run the example Seam applications that are included with the documentation using the production configuration. - </para> - <para> To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename>JBOSS_DIST/jboss-as/bin/run.conf</filename> with these recommended values: <programlisting> -Xms1303m -Xmx1303m -XX:MaxPermSize=256m .... @@ -91,70 +48,13 @@ <para><remark>This is the default so the "adjust" statement is not correct. Should it be set higher than 256m?</remark></para> </section> - &END_EDIT; + <section id="Post-Installation"> <title> Post Installation Security Configuration </title> <para> - When installed from the zip archive, all JBoss services require authentication to access most JBoss services, including administrative services. Additionally no user accounts are set up. This is to stop default user/password-based attacks. - </para> - - <formalpara> - <title>Set up Accounts for <literal>jmx-console</literal> and the invokers by modifying:</title> - <para> - <programlisting> - $JBOSS_HOME/server/$CONFIG/conf/props/jmx-console-users.properties - </programlisting> - </para> - </formalpara> - <formalpara> - <title>Set up Accounts for <literal>web-console</literal> users by modifying:</title> - <para> - <programlisting> - $JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr.sar/ - web-console.war/WEB-INF/classes/web-console-users.properties - </programlisting> - Where <literal>$JBOSS_HOME</literal> is the install directory and <literal>$CONFIG</literal> is the server configuration being used. - </para> - </formalpara> - <formalpara> - <title>Set SuckerPassword for JBoss Messaging:</title> - <para> - JBoss Messaging makes internal connections between nodes in order to redistribute messages between clustered destinations. These connections are made with the user name of a special reserved user whose password is specified by this parameter <literal>SuckerPassword</literal> in the Server Peer configuration file: - <programlisting> - $JBOSS_HOME/server/$CONFIG/deploy/jboss-messaging.sar/messaging-service.xml - </programlisting> - Where <literal>$JBOSS_HOME</literal> is the install directory and <literal>$CONFIG</literal> is the server configuration being used. - To avoid a security risk, you MUST specify the value of the attribute <literal>SuckerPassword</literal>, failing which the default value will be used. Any one who knows the default password will be able to gain access to any destinations on the server. The following fragment should be uncommented and modified: - <programlisting> - &lt;mbean code="org.jboss.jms.server.ServerPeer" - name="jboss.messaging:service=ServerPeer" - xmbean-dd="xmdesc/ServerPeer-xmbean.xml"&gt; - ... - ... - ... - ... - &lt;!-- The password used by the message sucker connections to create connections. - THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM --&gt; - &lt;attribute name="SuckerPassword"&gt;&lt;/attribute&gt; - - ... - ... - ... - &lt;/mbean&gt; - </programlisting> - </para> - </formalpara> - </section> - - &START_EDIT; - <section id="Post-InstallationE"> - <title> - Post Installation Security Configuration - </title> - <para> When installed from the zip archive, authentication is required to access the majority of JBoss services, including administrative services. User accounts have not been set up to eliminate the possibility of default username/password based attacks. </para> <important><title>Default admin user configuration</title> @@ -221,12 +121,12 @@ </programlisting> </para> </formalpara> - <para><remark>edit $JBOSS_HOME/server/$CONFIG/deploy/messaging/messaging-jboss-beans.xml as well?</remark></para> - <para><remark><literal>&lt;property name="suckerPassword"&gt;CHANGE ME!!&lt;/property&gt;</literal></remark></para> - <para><remark><literal>Also can't see jmx console or admin-console in the interface so is section this relevant?</literal></remark></para> + <para><remark>Note to Reviewer</remark></para> + <para>edit $JBOSS_HOME/server/$CONFIG/deploy/messaging/messaging-jboss-beans.xml as well?</para> + <para><literal>&lt;property name="suckerPassword"&gt;CHANGE ME!!&lt;/property&gt;</literal></para> + <para><remark>End Note to Reviewer</remark></para> </section> - &END_EDIT; <section id="Disabling_Authentication"> <title>Disabling Authentication</title> <para><remark>No changes here as all paths and files are the same</remark></para> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Test_Your_Installation.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Test_Your_Installation.xml 2010-04-13 02:06:38 UTC (rev 2592) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US/Test_Your_Installation.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -6,46 +6,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 <ulink url="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 -===================================================== - JBoss Bootstrap Environment - - JBOSS_HOME: /home/user/jboss-eap-4.3/jboss-as - - JAVA: /usr/java/jdk1.5.0_11/bin/java - - JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.cli ent.gcInterval=3600000 - -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.prefer IPv4Stack=true - - CLASSPATH: /home/user/jboss-eap-4.3/jboss-as/bin/run.jar:/u sr/java/jdk1.5.0_11/lib/tools.jar - -===================================================== - -18:45:49,550 INFO [Server] Starting JBoss (MX MicroKernel)... -. -. -. -. -18:45:50,449 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc. -18:45:50,449 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03 ,Sun Microsystems Inc. -18:45:50,449 INFO [ServerInfo] OS-System: Linux 2.6.9-42.0.3.EL,i386 -18:45:51,824 INFO [Server] Core system initialized -18:45:59,622 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 / -18:45:59,659 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml -</programlisting> - <note> - <para> - Note that there is no "Server Started" message shown at the console when the server is started using the <literal>production</literal> profile, which is the default profile used when no other is specified. This message may be observed in the <filename>server.log</filename> file located in the <filename>server/production/log</filename> subdirectory. - </para> - </note> - - &START_EDIT; <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> environment variables as explained in <ulink url="Post_Installation_Configuration"/>. </para> @@ -63,7 +24,7 @@ <itemizedlist> <listitem> <para> - Ensure that you run the configuration corresponding to the <filename>$JBOSS_HOME/server/$CONFIG/</filename> chosen in <xref linkend="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_DatabaseE"></xref> + Ensure that you run the configuration corresponding to the <filename>$JBOSS_HOME/server/$CONFIG/</filename> chosen in <xref linkend="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_Database"></xref> </para> </listitem> </itemizedlist> @@ -112,10 +73,15 @@ Note that 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>server/production/log</filename> subdirectory. </para> </note> - &END_EDIT; + <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> - 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" />. + Ensure that port 8080 is not already in use and open <literal>http://localhost:8080/portal</literal> in your web browser. + <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> <figure id="Test_your_Installation-Test_your_Installation">