From do-not-reply at jboss.org Tue Apr 13 00:49:19 2010 Content-Type: multipart/mixed; boundary="===============2537554687766264860==" MIME-Version: 1.0 From: do-not-reply at jboss.org To: gatein-commits at lists.jboss.org Subject: [gatein-commits] gatein SVN: r2593 - portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US. Date: Tue, 13 Apr 2010 00:49:19 -0400 Message-ID: <201004130449.o3D4nJe2019859@svn01.web.mwc.hst.phx2.redhat.com> --===============2537554687766264860== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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_Install= ation_Guide/en-US/Configuration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install= ation_Guide/en-US/Databases.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install= ation_Guide/en-US/Getting_Started.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install= ation_Guide/en-US/Installation.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install= ation_Guide/en-US/Installation_Guide.ent portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install= ation_Guide/en-US/Post_Installation.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install= ation_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 =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 --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal= lation_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_Instal= lation_Guide/en-US/Configuration.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -5,29 +5,11 @@ ]> Database Configuration - = + =
Installing an RDBMS JDBC connector A relational database management system (RDBMS) Java Database Connectiv= ity (JDBC) connector is required for &PRODUCT; to communicate with a databa= se. - &PRODUCT; comes bundled with Hypersonic SQL (HSQL) database so that use= rs can get started up and running quickly without having to setup = - database initially. However, HSQL should not be used in production en= vironment. Removing HSQL is simply a matter of removing = - JBOSS_DIST/jboss-as/server/$CONFIG/deploy/portal-hsql-ds.xm= l. Test suites have been run against = - the Oracle 9, Oracle 10, Microsoft SQL Server, = - MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases are re= commended for production use. Please refer to your database documentation f= or the correct = - RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be downloade= d from , = and the - PostgreSQL RDBMS JDBC connector can be downloaded from . - - - Refer to the help files in each download for installation instructions.= In most cases, the RDBMS JDBC connector comes as a .jar file. Copy this file into the $JBOSS_HOME/server/<= replaceable>configuration/lib/ directory. - -
- = - &START_EDIT; -
- Installing an RDBMS JDBC connector - - A relational database management system (RDBMS) Java Database Connectiv= ity (JDBC) connector is required for &PRODUCT; to communicate with a databa= se. &PRODUCT; comes bundled with Hypersonic SQL (HSQL) database so that use= rs can get up and running quickly without having to initially set up = a database. However, HSQL should not be used in a production environm= ent. Removing HSQL is simply a matter of removing = JBOSS_DIST/jboss-as/server/$CONFIG/deploy/hsql-ds.x= ml. @@ -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 .jar file within the downloaded zip file. Copy this file into the= $JBOSS_HOME/server/$CONFIG/lib/ directory.
- &END_EDIT; + =
Datasource Descriptors - A Datasource descriptor is required for JBoss Portal to communicate wit= h a database. Sample Datasource descriptor files are provided for the Hyper= sonic SQL, Microsoft SQL Server= , MySQL, Oracle, and PostgreSQL= databases. These can be found in the /jboss-as/docs/portal/setup= / subdirectory where the EPP x.x.x<= /replaceable> binary distribution file was extracted to. F= or example, if EPP was extracted into the /jboss/ dire= ctory, the sample Datasource descriptors would be in the /jboss/j= boss-epp-x.x.x/jboss-as/docs/portal/setup directory. - - - The sample Datasource descriptors will work with default installations = of external databases; however, you may need to configure the correct usern= ame and password. As well, the sample MySQL and PostgreSQL Datasource descr= iptors assume the name of the database to be jbossportal. - - - When copying a Datasource descriptor for MySQL, Microsoft SQL Server, PostgreSQL, or Oracle databases, change the &l= t;user-name>portal</user-name> and <password>portalpassword</password> sections to reflect the corre= ct username and password for the user who has access to the jbossportal dat= abase. - - - Different Datasource Descriptors - - Only have one Datasource descriptor in the $JBOSS_HOME/serve= r/configuration/deploy/ directory. Fo= r example, if you want to use a MySQL database, remove the portal= -hsqldb-ds.xml file, and other descriptors, if they exists. - - - - The following is an example Datasource descriptor file for MySQL 5: - - - -<?xml version=3D"1.0" encoding=3D"UTF-8"?> -<datasources> - <local-tx-datasource> - <jndi-name>PortalDS</jndi-name> - <connection-url>jdbc:mysql://localhost:3306/jbossportal? - useServerPrepStmts=3Dfalse&amp;jdbcCompliantTruncation=3Dfalse= </connection-url> - <driver-class>com.mysql.jdbc.Driver</driver-class> - <user-name><replaceable>portal</replaceable></user= -name> - <password><replaceable>portalpassword</replaceable>&l= t;/password> = - </local-tx-datasource> -</datasources> - - -
- = - &START_EDIT; -
- Datasource Descriptors - A Datasource descriptor is required for JBoss Portal to communicate wit= h a database. Sample Datasource descriptor files are provided for the Hyper= sonic SQL, Microsoft SQL Server= , MySQL, Oracle, and PostgreSQL= databases. These can be found in the $JBOSS_HOME/jboss-a= s/docs/examples/jca directory. The sample Datasource descriptors will work with default installations = of external databases; however, you may need to configure the correct usern= ame and password. As indicated in the mysql-ds.xml file displayed below, th= e sample MySQL and PostgreSQL Datasource descriptors assume the name of the= database to be jbossdb. - Copy the required Datasource descriptor file to $JBOSS_HOME/s= erver/$CONFIG/deploy/ directory. When= copying a Datasource descriptor for MySQL, Microsoft SQL Server, PostgreSQL, or Oracle databases, change the <user-na= me>portal</user-name> = and <password>portalpassword</password> sections to reflect the correct userna= me and password of the user who has access to the jbossportal database. + Copy the required Datasource descriptor file to the $JBOSS_HO= ME/server/$CONFIG/deploy/ directory. = When copying a Datasource descriptor for MySQL, Microsoft SQL Server, PostgreSQL, or Oracle databases, change the <use= r-name>portal</user-name> and <password>portalpassword</password> sections to reflect the correct us= ername and password of the user who has access to the jbossportal database. - Different Datasource Descriptors + Important: Various Datasource Descriptors - Ensure that there is only one Datasource descriptor in the $= JBOSS_HOME/server/$CONFIG/deploy/ dir= ectory. For example, if you want to use a MySQL database, remove the hsqldb-ds.xml file, and other descriptors, if they exists. F= or a default configuration this will require removing the gatein-= ds.xml and hsqldb-ds.xml files. + Ensure that there is only one Datasource descriptor in the $= JBOSS_HOME/server/$CONFIG/deploy/ dir= ectory. For example, if you want to use a MySQL database, remove the hsqldb-ds.xml file and any other descriptors. For a default = configuration this will require removing the gatein-ds.xml and hsqldb-ds.xml files to use a MySQL database. The following is an example Datasource descriptor file for MySQL 5: + Note to Reviewer + This is copied directly from th sample provided in jboss-as/docs= /examples/jca/ + End Note to Reviewer <?xml version=3D"1.0" encoding=3D"UTF-8"?> = @@ -144,7 +91,6 @@ </datasources>
- &END_EDIT; = = Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Installation_Guide/en-US/Databases.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 --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal= lation_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_Instal= lation_Guide/en-US/Databases.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -7,8 +7,7 @@ Databases - 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 M= ySQL database and the database user. =
@@ -19,26 +18,7 @@ The RDBMS JDBC MySQL connector is required for JBoss Portal to use a = MySQL database: - - - - Navigate to the JDBC MySQL connector section of dev.mysql.com. Downlo= ad the Source and Binaries (zip) file. - - - - - Unzip the mysql-java-connector into the desired = directory. It does not matter which directory is used. - - - - - Change into the directory where the mysql-java-connector was extracted to. Copy the mysql-connector-java-version-number-bin.jar file into the $JBOSS_HOME/server/configuration/lib/ directory. - - - = - &START_EDIT; - = @@ -56,9 +36,7 @@ - = - &END_EDIT; - = + = Data Truncation Errors @@ -71,25 +49,10 @@ - If you are running MySQL in strict mode, remove STRICT_= TRANS_TABLES from the sql-mode=3D line, in the my.cnf file if you are running L= inux, and from the my.cfg file if you are running Windows. For further information, p= lease see . - - &START_EDIT; - = - - Data Truncation Errors - - If you are running MySQL 5, data truncation errors such as the followi= ng may occur: - - - - -ERROR JDBCExceptionReporter Data truncation: Data too long for column '= ;jbp_viewrealemail' at row 1 - - - If you are running MySQL in strict mode, remove STRICT_= TRANS_TABLES from the sql-mode =3D<= /computeroutput> line of the relevant configuration file. For Linux= , this is the my.cnf file. For Windows, edit the my.cfg file. Fo= r further information, please see . - &END_EDIT; + = + Creating a MySQL Database @@ -151,89 +114,6 @@ - Add a new user and give that user access to the jbossportal database.= The following example adds a new user named portal, with the password portalpassword, and gives the portal user access to the jbossportal database. It is reco= mmended that you change the password. Change portalpassword to change the password: - - - -mysql> GRANT ALL PRIVILEGES ON jbossportal.* TO 'porta= l'@'localhost' = -IDENTIFIED BY 'portalpassword' WITH GRA= NT OPTION; - - - - The output should be similar to the following: - - - -Query OK, 0 rows affected (0.00 sec) - - - - If you changed the portal user's password, also change the passwo= rd in the MySQL Datasource descriptor. - - - - &START_EDIT; - - Creating a MySQL Database - - If you have just installed MySQL, make sure the MySQL server is runnin= g, and then run the following command to set the root user password: - - - - -mysqladmin -u root password 'new-root-user-password' - - - - - - Run the following command to log in to MySQL. Enter the root user pas= sword when prompted: - - - -mysql -u root -p - - - - - - Use the CREATE DATABASE command to create a new jb= ossportal database. Note: the rest of this guide, and configuration example= s following here after, assume the database name to be jbossportal. If you = change the database name, please change the name in all necessary configura= tion files: - - - -mysql> CREATE DATABASE jbossportal; - - - - The output should be similar to the following: - - - -Query OK, 1 row affected (0.00 sec) - - - - At this point, the SHOW DATABASES; command should = display the jbossportal database: - - - -mysql> SHOW DATABASES; -+--------------------+ -| Database | -+--------------------+ -| information_schema | = -| jbossportal | = -| mysql | = -+--------------------+ -3 rows in set (0.00 sec) - - - - It is safe to ignore the other databases. - - - - Add a new user and give that user access to the jbossportal database.= The following example adds a new user named portal, with the password portalpassword. It is recommended that you choose a different password to the one suppli= ed here by changing portalpassword to some other= password: CREATE USER 'portal'@'localhost' IDENTIFIED BY 'portalpassword= '; @@ -263,7 +143,7 @@ - &END_EDIT; + = MySQL Datasource Descriptor @@ -273,25 +153,6 @@ - Change into the setup subdirectory where JBoss P= ortal was extracted to. Copy the MySQL Datasource descriptor into the $JBOSS_HOME/server/configuration/deploy/ directory. If you are running MySQL 5, use portal-mysql5= -ds.xml, otherwise use portal-mysql-ds.xml. - - - - - Update the <user-name>portal</user-name> and <passwor= d>portalpassword</password> sections in the Datasource descriptor to reflect the correct username= and password for the user who has access to the jbossportal database. - - - - &START_EDIT; - - MySQL Datasource Descriptor - - To install the MySQL Datasource descriptor: - - - - - Copy the MySQL Datasource descriptor - $JBOSS_HOME/docs/exa= mples/jca/mysql-ds.xml - into the $JBOSS_HOME/server/<= replaceable>$CONFIG/deploy/ directory. @@ -329,7 +190,7 @@ - This example uses the portalpassword pas= sword. Enter this or the password chosen at . + This example uses the portalpassword pas= sword. Enter this or the password chosen at . = @@ -339,7 +200,6 @@ - &END_EDIT; = MySQL Table Errors Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Installation_Guide/en-US/Getting_Started.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 --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal= lation_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_Instal= lation_Guide/en-US/Getting_Started.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -241,15 +241,10 @@ =
Configuring Your Java Environment - - You must have a working installation of JDK 1.= 5 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 in= stall a 32-bit Sun JDK 5.0 using RHN, on a generic Linux Platform and Micro= soft Windows Platform. But before we do that let's take a look at some of t= he benefits of using a 64-bit JVM. - - &START_EDIT; = You must have a working installation of JDK 1.= 6 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 in= stall a 32-bit Sun JDK 6.0 using RHN, on a generic Linux Platform and Micro= soft Windows Platform. But before we do that let's take a look at some of t= he benefits of using a 64-bit JVM. - &END_EDIT; = Benefits of 64-bit JVM on 64-bit OS and Hardware: @@ -274,56 +269,7 @@ - - Installing and Configuring 32-bit Sun JDK 5.0 using RHN - - - Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplemen= tary channel for your Linux variant and architecture. Depending on the arch= itecture, the channel names are: - - - rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementa= ry-5 - - - The java-1.5.0-bea, - java-1.5.0-ibm and - java-1.5.0-sun SDKs are availa= ble from - these channels. Make sure you also install the - -devel subpackages. - - - = - - - Selecting alternatives for java, javac and java_sdk_1.5.0 (setting java_sdk_1.5.0 is optional). = - - = - - 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 JAVA_HOME environment vari= able. - - = - - The alternatives system allows= different versions of Java, from different sources, to co-exist on your sy= stem. You should make sure the desired one is selected so that the service = script uses the one you want. - - = - - As root, issue the following command: - - - /usr/sbin/alternatives --config java - - - and make sure the desired one is selected (marked with a '+'), or s= elect it by entering its number as prompted. - - = - - Make sure you do the same for javac and java_sdk_1.5.0. We recommend= that all point to the same manufacturer and version. - - - - &START_EDIT; + = Installing and Configuring JDK 6.0 using RHN @@ -387,9 +333,7 @@ As root, issue the following command: - - /usr/sbin/alternatives --config java - + /usr/sbin/alternatives --config j= ava and make sure the desired one is selected (marked with a '+'), or s= elect it by entering its number as prompted. @@ -399,97 +343,7 @@ - &END_EDIT; - - Installing and Configuring 32-bit Sun JDK 5.0 on a generic Lin= ux platform - - - Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's we= bsite: <= /ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update nu= mber) for download and then select "RPM in self-extracting" file for Linux<= footnote>Make sure you choose the appropriate file for your platform.= . Read the instructions on Sun's website for installi= ng the JDK. - - - - - If you don't want to use SysV service scripts you can install t= he "self-extracting file" for Linux instead of choosing the "RPM in self-ex= tracting" 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. - - - - - Download and install the appropriate -compat RPM= from JPackage here. - -Please ensure you choose a matching version of the -compat package to the JDK you installed. - - - - - - Create an environment variable that points to the JDK installation = directory and call it JAVA_HOME. Add $JAVA_HOME= /bin to the system path to be able to run java= from the command line. You can do this by adding the following lines to th= e .bashrc file in your home directory. -#In this example /usr/java/jdk1.5.0_11 is the JDK installation directory. -export JAVA_HOME=3D/usr/java/jdk1.5.0_11 -export PATH=3D$PATH:$JAVA_HOME/bin - - Set this variable for the user account doing the installation and = also for the user account that will run the server. - - - - - 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 ja= va and javac. You can do this using the altern= atives system. The alternatives system allows different versions of Java, f= rom different sources to co-exist on your system. - - Select alternatives for java, javac and java_sdk_1.5.0</tit= le> - <listitem> - <para> - As root, type the following command at the shell prompt and you = should see something like this: <programlisting> -[root(a)vsr ~]$ /usr/sbin/alternatives --config java -There are 2 programs which provide 'java'. -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 '+' 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(a)vsr ~]$ /usr/sbin/alternatives --config javac -There are 1 programs which provide 'javac'. - 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(a)vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0 -There are 1 programs which provide 'java_sdk_1.5.0'. - 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_HOM= E</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 pa= th and that you are using an appropriate version. To verify your Java envir= onment, type <literal>java -version</literal> at the shell prompt and you s= hould see something like this: <programlisting> -[root(a)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=3D"Configuring_Your_Java_Environment-Installing_and_C= onfiguring_JDK_6.0_on_a_generic_Linux_platform"> <title>Installing and Configuring JDK 6.0 on a generic Linux platform= @@ -530,11 +384,11 @@ Download and install the appropriate -compat RPM= from JPackage here. Please ensure you = choose a matching version of the -compat package to the = JDK you installed. - &START_NOTE; + Note to Reviewer The latest JDK available from Sun's site is update 19. The jpackag= e site linked to above lists the latest -compat rpm at u= pdate 6 (java-1.6.0-sun-compat-1.6.0.06-1jpp.i586.rpm). So there is a confl= ict here as the downloaded package and the -compat rpm cannot be matched as= stated above. - &END_NOTE; + End Note to Reviewer @@ -559,21 +413,26 @@ = - As root, type the following command at the shell prompt and you = should see something like this: -[root(a)vsr ~]$ /usr/sbin/alternatives --config java + As root, type the following command at the shell prompt and you = should see something like this: + + [root(a)vsr ~]$ /usr/sbin/alternatives --config java There are 2 programs which provide 'java'. 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: + = + = Make sure the Sun version [jre-1.6.0-sun in = this case] is selected (marked with a '+' in the output), or select= it by entering its number as prompted. - Repeat the same for javac and java_sdk_1.6.0. + Repeat the same for javac and java_sdk_1.6.0. = + + [root(a)vsr ~]$ /usr/sbin/alternatives --config javac There are 1 programs which provide 'javac'. 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: + You should verify that java, java= c 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; + Note to Reviewer + Better to use java-1.6.0-variant rather th= an java-1.6.0-sun as could be sun or openjdk. Also include openJDK download= site info http://openjdk.java.net/install/ ? + End Note to Reviewer @@ -609,21 +469,7 @@ - &END_EDIT; - - Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Win= dows - - - Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's we= bsite: <= /ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update nu= mber) for download and then select your Windows Platform options to perform= the installation. - - - - - Create an environment variable called JAVA_HOME = that points to the JDK installation directory, for example: C:\Pro= gram Files\Java\jdk1.5.0_11\. In order to run java from the comma= nd line add the jre\bin directory to your path, for exam= ple: C:\Program Files\Java\jdk1.5.0_11\jre\bin. To do th= is, open the Control Panel from the Start Menu, switch to Classic View if n= ecessary, open the System Control Panel applet, select the Advanced Tab, an= d click on the Environment Variables button. - - - - &START_EDIT; + = Installing and Configuring JDK 6.0 on Microsoft Windows @@ -686,7 +532,6 @@ - &END_EDIT;
=
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Installation_Guide/en-US/Installation.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 --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal= lation_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_Instal= lation_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 (C= SP), located at https://network.jb= oss.com. = - = + =
Installing = - To install from a zip file, simply unzip the downloaded file to a dire= ctory of your choice. You can unzip the platform on any operating system th= at supports the zip format. Four types of server configurations will be inc= luded in your installation - minimal, default, production and all. = - The Getting Started Guide of &JBEAP; as well as http://www.jboss.org/co= mmunity/docs/DOC-12942 explain in detail the different server configuration= file sets. = - = - - - - Unzip jboss-epp-<release>.= zip to extract the archive contents into the location of your cho= ice. You can do this using the JDK jar tool (or any othe= r ZIP extraction tool). - [vsr]$ cd jbeppinstallationdir - [vsr]$ jar -xvf jboss-epp-<release>.zip - - - - - You are done with the installation! You should now have a directory = called jboss-epp-<release>. Refer to the Getting Started Guide to understand and explore the Pla= tform Directory Structure. - - - - = -
- = - &START_EDIT; -
- Installing - = - To install from a zip file, simply unzip the downloaded file to a dire= ctory of your choice. You can unzip the platform on any operating system th= at supports the zip format. Six types of server configurations will be incl= uded in your installation - minimal, default, production, all, standard and= web. = The Getting Started Guide of &JBEAP; as well as http://www.jboss.org/co= mmunity/docs/DOC-12942 explain in detail the different server configuration= file sets. = = @@ -63,7 +38,7 @@ =
- &END_EDIT; + =
Choosing a server configuration @@ -72,43 +47,6 @@ - minimal server configuration has no Portal bits. = It's there for the sake of consistency with &JBEAP; - - - - - default server configuration has non-clustered Po= rtal bits jboss-portal.sar in = - deploy folder. = - - - - - all server configuration has clustered Portal bit= s jboss-portal-ha.sar in = - deploy folder. = - - - - - production server configuration has clustered Por= tal bits jboss-portal-ha.sar and this is = - the sever that gets started by default. This server configuration ha= s several optimizations such as logging, memory size etc. - If you do not need clustered portal version and want to use this opt= imized server configuration, you simply need to copy the directory - jboss-portal.sar from default/deploy to production/deploy. Don't forget to - remove jboss-portal-ha.sar though. = - - = - - -
- &START_EDIT; - = -
- Choosing a server configuration - - The important differences as far as Portal is concerned are: - - - - the minimal, web and = standard server configurations do not contain any Portal relevant= components. These directories exist for the sake of consistency with &JBEA= P; @@ -138,8 +76,5 @@
- = - &END_EDIT; - = = Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Installation_Guide/en-US/Installation_Guide.ent =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 --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal= lation_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_Instal= lation_Guide/en-US/Installation_Guide.ent 2010-04-13 04:49:17 UTC (rev 2593) @@ -5,7 +5,7 @@ -<!-- Start Edit"> -End Edit -->"> -<!-- Start Note to Reviewer= "> -End Note to Reviewer -->"> +<remark><!-- Start Edit</remark= >"> +<remark>End Edit --></remark></ti= tle><para></para></formalpara>"> +<!ENTITY START_NOTE "<formalpara><title><remark><!-- Start Note to Revi= ewer</remark>"> +<remark>End Note to Reviewer --><= /remark>"> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Installation_Guide/en-US/Post_Installation.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 --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal= lation_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_Instal= lation_Guide/en-US/Post_Installation.xml 2010-04-13 04:49:17 UTC (rev 2593) @@ -4,39 +4,11 @@ %BOOK_ENTITIES; ]> - Post Installation Configuration + Post Installation Configuration =
Set JBOSS_HOME Environment Variable - - - On a Linux Platform - - - Create an environment variable that points to the installation directo= ry (JBOSS_DIST/jboss-as) and call it JBOSS_HO= ME. Add $JBOSS_HOME/bin 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 .bashrc file in your home d= irectory. - -#In this example /home/user/jboss-epp-4.3/jboss-as is the installation dir= ectory. - export JBOSS_HOME=3D/home/user/jboss-epp-4.3/jboss-as - export PATH=3D$PATH:$JBOSS_HOME/bin = - - Set this variable for the user account(s) that will run the server. = - - - - - On Microsoft Windows - - - Create an environment variable called JBOSS_HOME th= at points to the installation directory, for example: C:\Program Files\jbos= s-epp-4.3\jboss-as\. In order to run the server from the command line add t= he bin 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 Contro= l Panel applet, select the Advanced Tab, and click on the Environment Varia= bles button. - - -
= - &START_EDIT; = -
- - Set JBOSS_HOME Environment Variable - Minor edit changed 4.3 to 5.0 in path to installation dire= ctory. @@ -60,8 +32,7 @@ Create an environment variable called <literal>JBOSS_HOME</literal> th= at points to the installation directory, for example: C:\Program Files\jbos= s-epp-5.0\jboss-as\. In order to run the server from the command line add t= he <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 Contro= l Panel applet, select the Advanced Tab, and click on the Environment Varia= bles button. </para> </formalpara> - </section> = - &END_EDIT; + </section> = = <section id=3D"Adjust_Memory_Settings"> <title>Adjust memory settings @@ -69,20 +40,6 @@ The default configuration for the server to start with, if no other con= figuration is specified, is the production configuration. It is recommended= to run the example Seam applications that are included with the documentat= ion using the production configuration. = - To avoid memory issues, adjust the memory settings before deploying the= applications. You can do this by updating JAVA_OPTS set= tings in the file JBOSS_DIST/jboss-as/server/production/run.conf<= /filename> with these recommended values: = - - -Xms1303m -Xmx1303m -XX:PermSize=3D256m -XX:MaxPermSize=3D256m - - -
- &START_EDIT; - = -
- Adjust memory settings - - The default configuration for the server to start with, if no other con= figuration is specified, is the production configuration. It is recommended= to run the example Seam applications that are included with the documentat= ion using the production configuration. = - - To avoid memory issues, adjust the memory settings before deploying the= applications. You can do this by updating JAVA_OPTS set= tings in the file JBOSS_DIST/jboss-as/bin/run.conf wit= h these recommended values: = -Xms1303m -Xmx1303m -XX:MaxPermSize=3D256m .... @@ -91,70 +48,13 @@ This is the default so the "adjust" statement is not corre= ct. Should it be set higher than 256m?
= - &END_EDIT; = + =
Post Installation Security Configuration - When installed from the zip archive, all JBoss services require authent= ication to access most JBoss services, including administrative services. A= dditionally no user accounts are set up. This is to stop default user/passw= ord-based attacks. - - = - - Set up Accounts for <literal>jmx-console</literal> and the invok= ers by modifying: - - - $JBOSS_HOME/server/$CONFIG/conf/props/jmx-console-users.properties - - - - - Set up Accounts for <literal>web-console</literal> users by modi= fying: - - - $JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr.sar/ - web-console.war/WEB-INF/classes/web-console-users.properties - - Where $JBOSS_HOME is the install directory and $CONFIG is the server configuration being used. - - - - Set SuckerPassword for JBoss Messaging: - - JBoss Messaging makes internal connections between nodes in order to r= edistribute messages between clustered destinations. These connections are = made with the user name of a special reserved user whose password is specif= ied by this parameter SuckerPassword in the Server Peer = configuration file: - - $JBOSS_HOME/server/$CONFIG/deploy/jboss-messaging.sar/messaging-service.= xml - - Where $JBOSS_HOME is the install directory and $CONFIG is the server configuration being used. - To avoid a security risk, you MUST specify the value of the attribute = SuckerPassword, 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 uncomment= ed and modified: - - <mbean code=3D"org.jboss.jms.server.ServerPeer" - name=3D"jboss.messaging:service=3DServerPeer" - xmbean-dd=3D"xmdesc/ServerPeer-xmbean.xml"> - ... - ... - ... - ... - <!-- The password used by the message sucker connections to create c= onnections. - THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM = --> - <attribute name=3D"SuckerPassword"></attribute> - - ... - ... - ... - </mbean> = - - - -
- = - &START_EDIT; -
- - Post Installation Security Configuration - - When installed from the zip archive, authentication is required to acce= ss the majority of JBoss services, including administrative services. User = accounts have not been set up to eliminate the possibility of default usern= ame/password based attacks. Default admin user configuration @@ -221,12 +121,12 @@ - edit $JBOSS_HOME/server/$CONFIG/deploy/messaging/messaging= -jboss-beans.xml as well? = - <property name=3D"suckerPassword">CHANGE ME= !!</property> - Also can't see jmx console or admin-console in th= e interface so is section this relevant? + Note to Reviewer + edit $JBOSS_HOME/server/$CONFIG/deploy/messaging/messaging-jboss-b= eans.xml as well? = + <property name=3D"suckerPassword">CHANGE ME!!</p= roperty> + End Note to Reviewer
= - &END_EDIT;
Disabling Authentication = No changes here as all paths and files are the same Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Installation_Guide/en-US/Test_Your_Installation.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 --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal= lation_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_Instal= lation_Guide/en-US/Test_Your_Installation.xml 2010-04-13 04:49:17 UTC (rev = 2593) @@ -6,46 +6,7 @@ = Test your Installation - = - - After you have installed the JBoss Enterprise Portal Platform, it is wis= e to perform a simple startup test to validate that there are no major prob= lems with your Java VM/operating system combination. Make sure you have set= the JBOSS_HOME envirnoment variables as explained in . To test your installation, = move to JBOSS_DIST/jboss-as/bin directory and execute = the run.bat (for Windows) or run.sh (for Linux) script, as appropriate for your operating system. Your outpu= t should look like the following (accounting for installation directory dif= ferences) and contain no error or exception messages: - - -[user(a)localhost bin]$ ./run.sh = -=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 = - 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=3Drun.sh -server -Xms1503m -Xmx1503m -Dsun.rmi= .dgc.cli ent.gcInterval=3D3600000 = - -Dsun.rmi.dgc.server.gcInterval=3D3600000 -Djava.net.prefer I= Pv4Stack=3Dtrue - - CLASSPATH: /home/user/jboss-eap-4.3/jboss-as/bin/run.jar:/u sr/java/jdk1= .5.0_11/lib/tools.jar - -=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 - -18:45:49,550 INFO [Server] Starting JBoss (MX MicroKernel)... -. -. -. -. -18:45:50,449 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems In= c. -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 - - - - Note that there is no "Server Started" message shown at the console whe= n the server is started using the production profile, wh= ich is the default profile used when no other is specified. This message ma= y be observed in the server.log file located in the server/production/log subdirectory. - - - = - &START_EDIT; After you have installed the JBoss Enterprise Portal Platform, it is wis= e to perform a simple startup test to validate that there are no major prob= lems with your Java VM/operating system combination. Make sure you have set= the JBOSS_HOME environment variables as explained in . @@ -63,7 +24,7 @@ - Ensure that you run the configuration corresponding to the <= filename>$JBOSS_HOME/server/$CONFIG/ chosen in + Ensure that you run the configuration corresponding to the <= filename>$JBOSS_HOME/server/$CONFIG/ chosen in = @@ -112,10 +73,15 @@ Note that there is no "Server Started" message shown at the console whe= n the server is started using the production profile. Th= is message may be observed in the server.log file loca= ted in the server/production/log subdirectory. - &END_EDIT; + - Now open http://localhost:8080/portal in your web bro= wser. (Make sure you dont have anything else already on your machine using = that port). - Note that on some machines, the name localhost won=E2=80=99t resolve pro= perly and you should use the local loopback address 127.0.0.1 instead. The contents of your page should look similar to this: . + Ensure that port 8080 is not already in use and open http://loc= alhost:8080/portal in your web browser. + + + Note that on some machines, the name localhost won=E2=80=99t resolve= properly and you should use the local loopback address 127.0.0.1 instead. + + = + The contents of your page should look similar to this: .
--===============2537554687766264860==--