From portal-commits at lists.jboss.org Wed Jul 2 03:01:58 2008 Content-Type: multipart/mixed; boundary="===============6844898222162494328==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r11254 - docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules. Date: Wed, 02 Jul 2008 03:01:58 -0400 Message-ID: --===============6844898222162494328== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: mmcallis Date: 2008-07-02 03:01:58 -0400 (Wed, 02 Jul 2008) New Revision: 11254 Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/installa= tion.xml Log: manually merging changes from 2.6 that are missing in 2.7 Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/i= nstallation.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/install= ation.xml 2008-07-02 06:24:02 UTC (rev 11253) +++ docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/install= ation.xml 2008-07-02 07:01:58 UTC (rev 11254) @@ -20,12 +20,12 @@ - Extract the bundle: extract th= e ZIP archive. It does not matter which directory is used. On Windows, the recommended directory is C:\jboss-version-number. + Extract the bundle: extract th= e ZIP archive. It does not matter which directory is used. On Windows, the = recommended directory is C:\jboss-version-number. - Start the server: change into = the JBOSS_PORTAL_INSTALLATION_DIRECTORY/bin/ directory= . On Windows, execute = run.bat. On Linux, ru= n the sh run.sh command. To specify a configuration to u= se, for example, the default configuration, append the -c default= option to the run.bat or sh run.sh commands. + Start the server: change into = the JBOSS_PORTAL_INSTALLATION_DIRECTORY/bin/ directory= . On Windows, execute run.bat. On Linux, run the sh run.sh command. To specify a configuration to use, for examp= le, the default configuration, append the -c default op= tion to the run.bat or sh run.sh comm= ands. @@ -89,7 +89,7 @@ Database Setup - A database is required for JBoss Portal to run. JBoss EAP and JBoss AS = include an embedded Hypersonic SQL database that JBoss Portal can use; howe= ver, this is only recommended for developer use. The following databases ar= e recommended for production use, and have had test suites run against them= : MySQL 4 and 5, Microsoft SQL= Server, PostgreSQL 8, Oracle Database 9, and Oracle Database 10. JBoss Portal can use any database that is supported by Hibe= rnate. + A database is required for JBoss Portal to run. JBoss EAP and JBoss AS = include an embedded Hypersonic SQL database that JBoss Portal can use; howe= ver, this is only recommended for developer use. The following databases ar= e recommended for production use, and have had test suites run against them= : MySQL 4 and 5, Microsoft SQL Server, PostgreSQL 8, and Oracle Database 9 = and 10. JBoss Portal can use any database that is supported by Hibernate. To configure a database to use with JBoss Portal: @@ -117,7 +117,7 @@ Datasource Descriptors - The JBoss Portal binary download that was extracted in , contains pre-configured Datasource descriptors = for the more popular databases. Datasource descriptors are provided for the= MySQL 4 and 5, PostgreSQL, Microsoft SQL Server, and Oracle<= /trademark> databases, and can be found in the setup s= ubdirectory where the JBoss Portal binary was extracted to: + The JBoss Portal binary download that was extracted in , contains pre-configured Datasource descriptors = for the more popular databases. Datasource descriptors are provided for the= MySQL 4 and 5, PostgreSQL, Microsoft SQL Server, and Oracle databases, and= can be found in the setup subdirectory where the JBos= s Portal binary was extracted to: @@ -161,7 +161,7 @@ - Start the server: change into the <= filename>$JBOSS_HOME/bin/ directory. On Windows, execute run.bat. On Linux, run the sh run.sh command. To specify a configuration to use, for example, the default = configuration, append the -c default option to the run.bat or sh run.sh commands. + Start the server: change into the <= filename>$JBOSS_HOME/bin/ directory. On Windows, execute run.bat. On Linux, run the sh run.sh command= . To specify a configuration to use, for example, the default configuration= , append the -c default option to the run.bat<= /command> or sh run.sh commands. @@ -327,7 +327,7 @@ Replace proxy-hostname with the proxy server= 's hostname, and proxy-port with the correct pro= xy server port number. - To build and deploy JBoss Portal from the sources, change into the = JBOSS_PORTAL_SOURCE_DIRECTORY/build/ directory, where= JBOSS_PORTAL_SOURCE_DIRECTORY is the directory where = the JBoss Portal source code was downloaded to. Then, Windows, users need t= o run the build.bat deploy command, and Linux users need= to run the sh build.sh deploy command. + To build and deploy JBoss Portal from the sources, change into the = JBOSS_PORTAL_SOURCE_DIRECTORY/build/ directory, where= JBOSS_PORTAL_SOURCE_DIRECTORY is the directory where = the JBoss Portal source code was downloaded to. Then, Windows users need to= run the build.bat deploy command, and Linux users need = to run the sh build.sh deploy command. At the end of the build process, the jboss-portal.sar file is copied into the $JBOSS_HOME/server/default/deploy/ directory: @@ -348,7 +348,7 @@ - To build the clustered version on Li= nux operating systems: + To build the clustered version on Linux operating systems: @@ -378,7 +378,7 @@ - To build the clustered version on Windo= ws, repeat the previous steps, replacing sh build.sh with build.bat. + To build the clustered version on Windows, repeat the previous steps, r= eplacing sh build.sh with build.bat. --===============6844898222162494328==--