Author: mmcallis Date: 2008-01-31 19:44:39 -0500 (Thu, 31 Jan 2008) New Revision: 9692 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml Log: rephrasing and adding a bit more content to 2.2.2. Deploying JBoss Portal Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-02-01 00:02:29 UTC (rev 9691) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-02-01 00:44:39 UTC (rev 9692) @@ -2,12 +2,13 @@ <chapter id="installation"> <title>Installation</title> <para>Depending on your needs, there are several different methods to install JBoss Portal. Pre-configured clustered versions (<computeroutput>JBoss Portal Binary (Clustered)</computeroutput>) are available from the - <ulink url="http://labs.jboss.com/portal/jbossportal/download/index.html&qu... Portal Downloads</ulink> page. Clustered versions of JBoss Portal must be deployed in the <filename><replaceable>JBOSS_INSTALLATION_DIRECTORY</replaceable>/server/all/deploy/</filename> directory. All JBoss AS instances must reference the same datasource. See <xref linkend="clustering"/> for details on how to configure JBoss Portal for clustering. + <ulink url="http://labs.jboss.com/portal/jbossportal/download/index.html&qu... Portal Downloads</ulink> page. Clustered versions of JBoss Portal must be deployed in the <filename>JBOSS_INSTALLATION_DIRECTORY/server/all/deploy/</filename> directory. All JBoss AS instances must reference the same datasource. See <xref linkend="clustering"/> for details on how to configure JBoss Portal for clustering. </para> <sect1 id="install_bundle"> <title>JBoss Portal and JBoss AS Bundle</title> <para>This is the easiest and fastest way to get JBoss Portal installed and running. The JBoss Portal and JBoss AS bundle contains JBoss AS, JBoss Portal, and the embedded Hypersonic SQL database. To install the JBoss Portal and JBoss AS bundle: </para> + <para> <orderedlist> <listitem> <para> @@ -21,7 +22,7 @@ </listitem> <listitem> <para> - <emphasis role="bold">Start the server:</emphasis> change into the <filename><replaceable>JBOSS_INSTALLATION_DIRECTORY</replaceable>/bin</filename> directory. On Microsoft Windows, execute <command>run.bat</command>. On Linux, run the <command>./run.sh</command> command. + <emphasis role="bold">Start the server:</emphasis> change into the <filename>JBOSS_INSTALLATION_DIRECTORY/bin/</filename> directory. On Microsoft Windows, execute <command>run.bat</command>. On Linux, run the <command>./run.sh</command> command. </para> </listitem> <listitem> @@ -30,27 +31,28 @@ </para> </listitem> </orderedlist> + </para> <note> <title>SQL Errors</title> <para> Tables are automatically created the first time JBoss Portal starts. When deployed for the first time, JBoss Portal checks for the existence of the initial tables, which have not been created yet. This causes errors such as the following, which can safely be ignored: </para> <para> - <programlisting> + <programlisting><![CDATA[ WARN [JDBCExceptionReporter] SQL Error: -22, SQLState: S0002 ERROR [JDBCExceptionReporter] Table not found in statement ... WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02 ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_repositoryentry' doesn't exist WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02 ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_version_refs' doesn't exist - </programlisting> + ]]></programlisting> </para> </note> </sect1> <sect1 id="install_binary"> <title>Installing the Binary Download</title> <para>The binary package typically consists of the - <filename>jboss-portal.sar</filename> directory, documentation such as the JBoss Portal User Guide and the JBoss Portal Reference Guide, and a set of pre-configured Datasource descriptors that allow + <filename>jboss-portal.sar/</filename> directory, documentation such as the JBoss Portal User Guide and the JBoss Portal Reference Guide, and a set of pre-configured Datasource descriptors that allow JBoss Portal to communicate with an external database. This installation method is recommended for users who already have JBoss EAP or JBoss AS installed, or those who need to install JBoss Portal in a clustered environment.</para> <sect2> <title>Setting up your Environment</title> @@ -89,6 +91,7 @@ <para> To configure a database to use with JBoss Portal: </para> + <para> <orderedlist> <listitem> <para> @@ -106,6 +109,7 @@ </para> </listitem> </orderedlist> + </para> </sect3> <sect3> <title>Datasource Configuration</title> @@ -142,39 +146,44 @@ </sect2> <sect2> <title>Deploying JBoss Portal</title> + <para> + To start JBoss EAP or JBoss AS and deploy JBoss Portal: + </para> <para> <orderedlist> <listitem> <para> - <emphasis role="bold">Deploy:</emphasis> - Copy the datasource descriptor file (*-ds.xml) you modified above AND the - <emphasis>jboss-portal.sar</emphasis> - from the download folder to - <filename>JBOSS_INSTALL_DIRECTORY/server/default/deploy/.</filename> - </para> - </listitem> - <listitem> - <para> - <emphasis role="bold">Start the Server:</emphasis> - Go to <filename>JBOSS_INSTALL_DIRECTORY/bin</filename> and execute <command>run.bat</command> (<command>run.sh</command>, if - Linux) - </para> - </listitem> - </orderedlist> - <note>During the first boot (ever), SQL errors in the log, like the one below, can be safely ignored. They - are thrown when the portal checks for the existence of the initial tables, before it creates them for - you. - <programlisting><![CDATA[16:43:39,234 WARN [JDBCExceptionReporter] SQL Error: -22, SQLState: S0002 -16:43:39,234 ERROR [JDBCExceptionReporter] Table not found in statement ...]]></programlisting> - </note> - Point your browser to - <emphasis>http://localhost:8080/portal</emphasis> - , and you should see the Portal HomePage. You can now login using one of the two default accounts: - <emphasis>user/user</emphasis> - or - <emphasis>admin/admin</emphasis> - . - </para> + <emphasis role="bold">Datasource descriptor:</emphasis> if you have not done so already, change into the <filename>setup</filename> subdirectory where the JBoss Portal binary was extracted to. Copy the correct Datasource descriptor file (<filename>*-ds.xml</filename>) you modified in the previous steps into the <filename>JBOSS_INSTALLATION_DIRECTORY/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. + </para> + </listitem> + <listitem> + <para> + <emphasis role="bold">Start the server:</emphasis> change into the <filename>JBOSS_INSTALLATION_DIRECTORY/bin/</filename> directory. On Microsoft Windows, execute <command>run.bat</command>. On Linux, run the <command>./run.sh</command> command. + </para> + </listitem> + <listitem> + <para> + <emphasis role="bold">Log in to JBoss Portal:</emphasis> using a Web browser, navigate to <computeroutput>http://localhost:8080/portal</computeroutput> to open the JBoss Portal homepage. Log in using one of the two default accounts: username <emphasis>user</emphasis>, password <emphasis>user</emphasis>, or username <emphasis>admin</emphasis>, password <emphasis>admin</emphasis>. + </para> + </listitem> + </orderedlist> + </para> + <note> + <title>SQL Errors</title> + <para> + Tables are automatically created the first time JBoss Portal starts. When deployed for the first time, JBoss Portal checks for the existence of the initial tables, which have not been created yet. This causes errors such as the following, which can safely be ignored: + </para> + <para> +<programlisting><![CDATA[ +WARN [JDBCExceptionReporter] SQL Error: -22, SQLState: S0002 +ERROR [JDBCExceptionReporter] Table not found in statement ... +WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02 +ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_repositoryentry' doesn't exist +WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02 +ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_version_refs' doesn't exist +]]></programlisting> + </para> + </note> </sect2> </sect1> <sect1 id="install_source">