From portal-commits at lists.jboss.org Mon Feb 4 02:32:18 2008 Content-Type: multipart/mixed; boundary="===============6167406001658610663==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r9728 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules. Date: Mon, 04 Feb 2008 02:32:18 -0500 Message-ID: --===============6167406001658610663== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: mmcallis Date: 2008-02-04 02:32:17 -0500 (Mon, 04 Feb 2008) New Revision: 9728 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installa= tion.xml Log: adding para on jboss_home, changing all jboss_install_directories to $JBOSS_HOME Modified: docs/branches/JBoss_Portal_Branch_2_6/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_6/referenceGuide/en/modules/install= ation.xml 2008-02-04 06:49:33 UTC (rev 9727) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/install= ation.xml 2008-02-04 07:32:17 UTC (rev 9728) @@ -2,8 +2,11 @@ Installation Depending on your needs, there are several different methods to i= nstall JBoss Portal. Pre-configured clustered versions (JBo= ss Portal Binary (Clustered)) are available from the - JBoss Portal Downloads page. Clustered versions of JBoss Port= al must be deployed in the JBOSS_INSTALLATION_DIRECTORY/server/al= l/deploy/ directory. All JBoss AS instances must reference the s= ame datasource. See for details on how to co= nfigure JBoss Portal for clustering. + JBoss Portal Downloads page. Clustered versions of JBoss Port= al must be deployed in the JBOSS_INSTALLATION_DIRECTORY/server/al= l/deploy/ directory. All JBoss AS instances must reference the s= ame datasource. See for details on h= ow to configure JBoss Portal for clustering. + + An environment variable, JBOSS_HOME, is = configured in . References to $JBOSS_HOME assume this to be your J= BOSS_INSTALLATION_DIRECTORY. + The JBoss Portal and JBoss AS Bundle This is the easiest and fastest way to get JBoss Portal instal= led and running. The JBoss Portal and JBoss AS bundle contains JBoss AS, JB= oss Portal, and the embedded Hypersonic SQL database. To install the JBoss = Portal and JBoss AS bundle: @@ -105,7 +108,7 @@ - Deploy a RDBMS JDBC connector: = a RDBMS JDBC connector is required for JBoss Portal to communicate with a d= atabase. Copy the connector into the JBOSS_INSTALL_DIRECTORY/serv= er/default/lib/ directory. For example, a RDBMS JDBC connector f= or MySQL can be download from . For the correct RDMBS JDBC connector, please refer t= o the database documentation. + Deploy a RDBMS JDBC connector: = a RDBMS JDBC connector is required for JBoss Portal to communicate with a d= atabase. Copy the connector into the $JBOSS_HOME/server/default/l= ib/ directory. For example, a RDBMS JDBC connector for MySQL can= be download from . For the correct RDMBS JDBC connector, please refer to the databa= se documentation. @@ -122,7 +125,7 @@ - Copy the Datasource descriptor that matches your database into th= e JBOSS_INSTALLATION_DIRECTORY/server/configuration<= /replaceable>/deploy/ directory, where configuratio= n is either all, default, minimal, or production. For example= , if you are using the production configuration, copy the Datasource descri= ptor into the JBOSS_INSTALLATION_DIRECTORY/server/production/depl= oy/ directory. + Copy the Datasource descriptor that matches your database into th= e $JBOSS_HOME/server/configuration/dep= loy/ directory, where configuration i= s either all, default, minimal, or production. For example, if you are usin= g the production configuration, copy the Datasource descriptor into the $JBOSS_HOME/server/production/deploy/ directory. After the Datasource descriptor has been copied into the deploy directory, make sure the username, password, connection= -url, and driver-class are correct for your chosen database. Datasource des= criptor files can be deployed to test before being used in production. The = following is an example Datasource descriptor for the PostgreSQL database: @@ -153,12 +156,12 @@ - Datasource descriptor: if you have= not done so already, change into the setup subdirecto= ry where the JBoss Portal binary was extracted to. Copy the correct Datasou= rce descriptor file (*-ds.xml) you modified in the pre= vious steps into the JBOSS_INSTALLATION_DIRECTORY/server/configuration/deploy/ directory. + Datasource descriptor: if you have= not done so already, change into the setup subdirecto= ry where the JBoss Portal binary was extracted to. Copy the correct Datasou= rce descriptor file (*-ds.xml) you modified in the pre= vious steps into the $JBOSS_HOME/server/configuratio= n/deploy/ directory. - Start the server: change into the <= filename>JBOSS_INSTALLATION_DIRECTORY/bin/ directory. On Microso= ft Windows, execute run.bat. On Linux, run the = ./run.sh command. + Start the server: change into the <= filename>$JBOSS_HOME/bin/ directory. On Microsoft Windows, execu= te run.bat. On Linux, run the ./run.sh command. @@ -327,7 +330,7 @@ Building and Deploying from the Sources During the first build, third-party libraries will be obtained from an = online - repository, so you must be connected to the Internet, and if you are be= hind a proxy server, you need to define your proxy server address and proxy= server port number. If you are running Linux, add the following line to th= e JBOSS_INSTALLATION_DIRECTORY/bin/run.sh file: + repository, so you must be connected to the Internet, and if you are be= hind a proxy server, you need to define your proxy server address and proxy= server port number. If you are running Linux, add the following line to th= e $JBOSS_HOME/bin/run.sh file: @@ -335,7 +338,7 @@ - Replace proxy-hostname with the proxy server= 's hostname, and proxy-port with the correct pro= xy server port number. If you are running Microsoft Windows, add the follow= ing line to the JBOSS_INSTALLATION_DIRECTORY/bin/run.bat file: + Replace proxy-hostname with the proxy server= 's hostname, and proxy-port with the correct pro= xy server port number. If you are running Microsoft Windows, add the follow= ing line to the $JBOSS_HOME/bin/run.bat file: @@ -348,7 +351,7 @@ To build and deploy JBoss Portal from the sources, change into the= JBOSS_PORTAL_HOME_DIRECTORY/build/ directory. Then, = Microsoft Windows users need to run the build.bat deploy= command, and Linux users need to run the ./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: + At the end of the build process, the jboss-portal.sar file is copied into the $JBOSS_HOME/server/default/deploy/ directory: @@ -390,7 +393,7 @@ = - After the ./build.sh deploy-ha command completes, = the jboss-portal-ha.sar file is copied into the JBOSS_HOME/server/all/deploy/ directory. + After the ./build.sh deploy-ha command completes, = the jboss-portal-ha.sar file is copied into the $JBOSS_HOME/server/all/deploy/ directory. @@ -421,7 +424,7 @@ - Deploy a RDBMS JDBC connector:= a RDBMS JDBC connector is required for JBoss Portal to communicate with a = database. Copy the connector into the JBOSS_INSTALL_DIRECTORY/ser= ver/default/lib/ directory. For example, a RDBMS JDBC connector = for MySQL can be download from . For the correct RDMBS JDBC connector, please refer = to the database documentation. + Deploy a RDBMS JDBC connector:= a RDBMS JDBC connector is required for JBoss Portal to communicate with a = database. Copy the connector into the $JBOSS_HOME/server/default/= lib/ directory. For example, a RDBMS JDBC connector for MySQL ca= n be download from . For the correct RDMBS JDBC connector, please refer to the datab= ase documentation. @@ -438,7 +441,7 @@ - Copy the Datasource descriptor that matches your database into the JBOSS_INSTALLATION_DIRECTORY/server/configuration/deploy/ directory, where configuration is either all, default, minimal, or production. For example, if = you are using the production configuration, copy the Datasource descriptor = into the JBOSS_INSTALLATION_DIRECTORY/server/production/deploy/ directory. + Copy the Datasource descriptor that matches your database into the $JBOSS_HOME/server/configuration/deploy/<= /filename> directory, where configuration is eit= her all, default, minimal, or production. For example, if you are using the= production configuration, copy the Datasource descriptor into the $JBOSS_HOME/server/production/deploy/ directory. After the Datasource descriptor has been copied into the dep= loy directory, make sure the username, password, connection-url,= and driver-class are correct for your chosen database. Datasource descript= or files can be deployed to test before being used in production. The follo= wing is an example Datasource descriptor for the PostgreSQL database: @@ -469,12 +472,12 @@ - Datasource descriptor: if yo= u have not done so already, change into the setup subd= irectory where the JBoss Portal binary was extracted to. Copy the correct D= atasource descriptor file (*-ds.xml) you modified in t= he previous steps into the JBOSS_INSTALLATION_DIRECTORY/server/configuration/deploy/ directory. + Datasource descriptor: if yo= u have not done so already, change into the setup subd= irectory where the JBoss Portal binary was extracted to. Copy the correct D= atasource descriptor file (*-ds.xml) you modified in t= he previous steps into the $JBOSS_HOME/server/config= uration/deploy/ directory. - Start the server: change int= o the JBOSS_INSTALLATION_DIRECTORY/bin/ directory. On = Microsoft Windows, execute run.bat. On Linux, run the ./run.sh command. + Start the server: change int= o the $JBOSS_HOME/bin/ directory. On Microsoft Windows= , execute run.bat. On Linux, run the ./run.sh command. --===============6167406001658610663==--