[jboss-cvs] JBossAS SVN: r91999 - projects/docs/enterprise/5.0/Installation_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Aug 5 00:17:04 EDT 2009
Author: irooskov at redhat.com
Date: 2009-08-05 00:17:02 -0400 (Wed, 05 Aug 2009)
New Revision: 91999
Added:
projects/docs/enterprise/5.0/Installation_Guide/en-US/Running_An_Installation.xml
Modified:
projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Alternatives.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Guide.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml
Log:
updated install guide with most of changes from JBPAPP-2320
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml 2009-08-05 02:58:46 UTC (rev 91998)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -7,7 +7,7 @@
<section id="Getting_Started-Pre_Requisites">
<title>Pre-Requisites</title>
<para>
- You must have adequate disk space<!--TODO how much --> to install JDK and &JBEAP; while also allowing enough space for your applications. Before installing &JBEAP; you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. However there are a few Operating System-specific issues that you must be aware of. Refer to <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossOperatingSystemSpecificIssues"></ulink> for more information.
+ You must have adequate disk space<!--TODO how much --> to install JDK and &JBEAP; while also allowing enough space for your applications. Before installing &JBEAP; you must have a working installation of Java and a C runtime. The JBos Enterprise Application Platform 5 includes offerings of JBoss Native and mod_jk which require a C runtime to be installed. <!--Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. However there are a few Operating System-specific issues that you must be aware of.--> Refer to <ulink url="http://www.jboss.org/community/wiki/JBossOperatingSystemSpecificIssues"></ulink> for more information.
</para>
<section id="Pre_Requisites-Hardware_and_Operating_System_Requirements">
<title>Hardware and Operating System Requirements</title>
@@ -257,7 +257,7 @@
<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> or <emphasis role="bold">JDK 1.6</emphasis> before you install &JBEAP;. 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.
+ You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install &JBEAP;. 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.
<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>
<listitem>
@@ -272,7 +272,7 @@
</listitem>
<listitem>
<para>
- Applications that run with more than 1.5GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM.
+ Applications that require more than 1GB of Java memory could utilize the 64-bit JVM.
</para>
</listitem>
<listitem>
@@ -281,8 +281,8 @@
</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>
+ <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_6.0_using_RHN">
+ <title>Installing and Configuring 32-bit Sun JDK 6.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:
@@ -291,9 +291,8 @@
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
+ <command moreinfo="none">java-1.6.0-bea</command>, <command moreinfo="none">java-1.6.0-openjdk</command> <command moreinfo="none">java-1.6.0-ibm</command> and
+ <command moreinfo="none">java-1.6.0-sun</command> SDKs are available from
these channels. Make sure you also install the
<command moreinfo="none">-devel</command> subpackages.
</para>
@@ -301,7 +300,7 @@
<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).
+ Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0</command> (setting <command moreinfo="none">java_sdk_1.6.0</command> is optional).
</para>
<para>
@@ -326,15 +325,15 @@
</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.
+ Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0.</command> We recommend that all point to the same manufacturer and version.
</para>
</listitem>
</itemizedlist>
- <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>
+ <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_6.0_on_a_generic_Linux_platform">
+ <title>Installing and Configuring 32-bit Sun JDK 6.0 on a generic Linux platform</title>
<listitem>
<para>
- Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"></ulink>. Choose "JDK 5.0 Update <x>" (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's website for installing the JDK.
+ Download the Sun JDK 6.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp"></ulink>. Choose "JDK 6.0 Update <x>" (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's website for installing the JDK.
</para>
</listitem>
<listitem>
@@ -353,8 +352,8 @@
<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
+#In this example /usr/java/jdk1.6.0_15 is the JDK installation directory.
+export JAVA_HOME=/usr/java/jdk1.6.0_15
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.
@@ -362,10 +361,10 @@
</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.
+ If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.6 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.
</para>
<itemizedlist>
- <title>Select alternatives for java, javac and java_sdk_1.5.0</title>
+ <title>Select alternatives for java, javac and java_sdk_1.6.0</title>
<listitem>
<para>
As root, type the following command at the shell prompt and you should see something like this: <programlisting>
@@ -374,31 +373,31 @@
Selection Command
-----------------------------------------------
1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java
-*+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java
+*+ 2 /usr/lib/jvm/jre-1.6.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.
+ Make sure the Sun version [<literal>jre-1.6.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>
+ Repeat the same for javac and java_sdk_1.6.0. <programlisting>
[root at 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
+*+ 1 /usr/lib/jvm/java-1.6.0-sun/bin/javac
Enter to keep the current selection[+], or type selection number:
</programlisting>
<programlisting>
-[root at vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0
-There are 1 programs which provide 'java_sdk_1.5.0'.
+[root at vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.6.0
+There are 1 programs which provide 'java_sdk_1.6.0'.
Selection Command
-----------------------------------------------
-*+ 1 /usr/lib/jvm/java-1.5.0-sun
+*+ 1 /usr/lib/jvm/java-1.6.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.
+ You should verify that java, javac and java_sdk_1.6.0 all point to the same manufacturer and version.
</para>
</listitem>
</itemizedlist>
@@ -413,23 +412,23 @@
<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 at 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)
+java version "1.6.0_15"
+Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0_15)
+Java HotSpot(TM) Client VM (build 1.6.0_15, mixed mode, sharing)
</programlisting>
</para>
</listitem>
</itemizedlist>
- <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>
+ <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_6.0_on_Microsoft_Windows">
+ <title>Installing and Configuring 32-bit Sun JDK 6.0 on Microsoft Windows</title>
<listitem>
<para>
- Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"></ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update number) for download and then select your Windows Platform options to perform the installation.
+ Download the Sun JDK 6.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp"></ulink>. Choose "JDK 6.0 Update <x>" (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.
+ Create a System environment variable called <literal>JAVA_HOME</literal> that points to the JDK installation directory, for example: <literal>C:\Program Files\Java\jdk1.6.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.6.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>
@@ -441,7 +440,7 @@
<section id="Getting_Started-Components_of_JBoss_Enterprise_Application_Platform">
<title>Components of &JBEAP;</title>
- <para>For current information on the revision level of included components please refer to <ulink url="http://www.jboss.com/products/platforms/application/components">http://www.jboss.com/products/platforms/application/components</ulink>.
+ <para>For current information on the revision level of included components please refer to <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html</ulink>.
</para>
<!--<para>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Alternatives.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Alternatives.xml 2009-08-05 02:58:46 UTC (rev 91998)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Alternatives.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -23,32 +23,32 @@
</listitem>
<listitem>
<para>
- Solaris™ 9 32-bit systems
+ Solaris™ 9 (32-bit systems)
</para>
</listitem>
<listitem>
<para>
- Solaris™ 10 32-bit systems and 64-bit systems
+ Solaris™ 10 (32-bit systems and 64-bit systems)
</para>
</listitem>
<listitem>
<para>
- Microsoft® Windows Server® 2008 R2 32-bit systems and 64-bit systems
+ Microsoft® Windows Server® 2008 R2 (32-bit systems and 64-bit systems)
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>
- Microsoft® Windows Vista™ Ultimate 32-bit systems 64-bit systems (all Service Pack editions)
+ Microsoft® Windows Vista™ Ultimate (32-bit systems 64-bit systems)
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
- Microsoft® Windows® XP 32-bit systems and 64-bit systems (all Service Pack editions)
+ Microsoft® Windows® XP (32-bit systems and 64-bit systems)
</para>
</listitem>
<listitem>
<para>
- Microsoft® Windows Server® 2003 32-bit systems and 64-bit systems
+ Microsoft® Windows Server® 2003 (32-bit systems and 64-bit systems)
</para>
</listitem>
</itemizedlist>
@@ -84,7 +84,7 @@
When you install from the installer, you get a smaller install image that is more tuned for your environment. However, the directory structure will be slightly different than when using the zip archive. <!--rpm archive-->
</para>
<para>
- Four types of server configurations will be included in your installation - <emphasis>minimal</emphasis>, <emphasis>default</emphasis>, <emphasis>production</emphasis> and <emphasis>all</emphasis>. The Getting Started Guide explains in detail the different server configuration file sets.
+ Five types of server profiles will be included in your installation - <emphasis>minimal</emphasis>, <emphasis>default</emphasis>, <emphasis>web</emphasis>, <emphasis>production</emphasis> and <emphasis>all</emphasis>. The Getting Started Guide explains in detail the different server profile sets.
</para>
</chapter>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Guide.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Guide.xml 2009-08-05 02:58:46 UTC (rev 91998)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Guide.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -13,6 +13,7 @@
<xi:include href="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<xi:include href="Running_An_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
</book>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml 2009-08-05 02:58:46 UTC (rev 91998)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -24,11 +24,11 @@
</itemizedlist>
<itemizedlist id="Installation_Using_Graphical_Installer-Installation_Steps">
<title>Installation Steps</title>
- <listitem>
+ <!-- <listitem>
<para>
Choose the language to be used for the installation instructions and press the OK button.
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
Read the License Agreement carefully. If you agree to the terms of the agreement select "I accept the terms of this license agreement" option and press the Next button. If you do not accept to the terms then choose "I do not accept to the terms of this license agreement" option. If you choose the second option you will not be able to proceed with the installation.
@@ -38,11 +38,11 @@
<para>
Select the Installation Path where you would like the JBoss Enterprise Application Platform to be installed. You can either type the complete path or browse for it. If the directory corresponding to the path you entered does not exist, the installer will create the target directory in the specified path. If the directory corresponding to the path you entered exists already, the installer will overwrite the contents of the directory. In either case the installer will prompt you to confirm the action.
</para>
- <note>
+ <warning>
<para>
- It does not matter where on your system you install the JBoss Enterprise Application Platform, however note that installing the JBoss Enterprise Application Platform into a directory that has a name containing spaces causes problems in some situations with Sun-based VMs. This is caused by bugs with file URLs not correctly escaping the spaces in the resulting URL.
+ Install the JBoss Enterprise Application Platform into a directory path that does not contain spaces. This will avoid issues with file URLs not correctly escaping the spaces in the directory path.
</para>
- </note>
+ </warning>
<figure id="Installation_Steps-Select_Installation_Path">
<title>Select Installation Path</title>
<mediaobject>
@@ -57,7 +57,7 @@
At this point you now have the choice of installing optional components. Currently the JBoss Enterprise Application Platform is distributed with an optional <package>Native</package> package.
</para>
<para>
- The <package>Native</package> package will be of interest for users who wish to use a HTTPd and Tomcat configuration. This package includes JBoss Native and mod_jk; for more information refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html">release notes</ulink>.
+ The <package>Native</package> package will be of interest for users who wish to use a HTTPd and Tomcat or JBoss Web configuration. This package includes JBoss Native and mod_jk; for more information refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html">release notes</ulink>.
</para>
<para>
If you choose to install the <package>Native</package> package, make sure to select the option that coralates to your Operating System and architecture.
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2009-08-05 02:58:46 UTC (rev 91998)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -22,10 +22,10 @@
<itemizedlist>
<listitem>
<para>
- Unzip <literal>jboss-eap-<replaceable><release></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).</para>
+ Unzip <literal>jboss-eap-<replaceable><release></replaceable>.zip</literal> to extract the archive contents into the location of your choice.</para>
<programlisting>
[vsr]$ <literal>cd /directory/to/install/in</literal>
-[vsr]$ <literal>jar -xvf jboss-eap-<replaceable><release></replaceable>.zip jboss-eap-native-5.0.0-<replaceable><operating_system>-<system_architecture></replaceable>.zip</literal>
+[vsr]$ <literal>unzip jboss-eap-<replaceable><release></replaceable>.zip jboss-eap-native-5.0.0-<replaceable><operating_system>-<system_architecture></replaceable>.zip</literal>
</programlisting>
</listitem>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml 2009-08-05 02:58:46 UTC (rev 91998)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -14,8 +14,8 @@
<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/vrenish/EnterprisePlatform-4.3.0/jboss-as is the installation directory.
- export JBOSS_HOME=/home/vrenish/EnterprisePlatform-4.3.0/jboss-as
+#In this example /home/<username>/EnterprisePlatform-5.0.0/jboss-as is the installation directory.
+export JBOSS_HOME=/home/<username>/EnterprisePlatform-5.0.0/jboss-as
export PATH=$PATH:$JBOSS_HOME/bin
</programlisting>
Set this variable for the user account(s) that will run the server.
@@ -26,24 +26,31 @@
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\EnterprisePlatform-4.3.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\EnterprisePlatform-4.3.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.
+ Create a System environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: C:\EnterprisePlatform-5.0.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:\EnterprisePlatform-5.0.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>
+ <important>
+ <para>
+ On Windows there is a difference between
+ User and System environment variables. Always
+ use System so the variables can be used by other accounts.
+ </para>
+ </important>
</section>
<section id="Adjust_Memory_Settings">
<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.
+ The default profile for the server to start with, if no other profile is specified, is the profile called default. It is recommended to run the example Seam applications that are included with the documentation using the production profile.
</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:
+ 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> to match your application requirements. The default settings are:
<programlisting>
-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m
</programlisting>
</para>
<important>
<para>
- If you are running the JBoss Enterprise Application Platform on a Windows operating system then you will need to update the <filename>run.bat</filename> file with the above values instead.
+ If you are running the JBoss Enterprise Application Platform on a Windows operating system then you will need to update the <filename>JBOSS_DIST/jboss-as/bin/run.conf.bat</filename> file to match your application requirements.
</para>
</important>
</section>
@@ -66,19 +73,23 @@
<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>
+<programlisting>
+$JBOSS_HOME/server/$CONFIG/conf/props/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>
+ <important>
+ <para>
+ Login credentials for the <literal>admin-console</literal> are the same as those used for the JMX console.
+ </para>
+ </important>
<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:
+ 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 configuration file:
<programlisting>
- $JBOSS_HOME/server/$CONFIG/deploy/jboss-messaging.sar/messaging-service.xml
+ $JBOSS_HOME/server/$CONFIG/messaging/messaging-jboss-beans.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:
@@ -102,7 +113,7 @@
</para>
</formalpara>
</section>
- <section id="Disabling_Authentication">
+<!-- <section id="Disabling_Authentication">
<title>Disabling Authentication</title>
<para>
It is also possible to disable authentication on specific services. All specified paths in the sections below are relative to <literal>$JBOSS_HOME</literal>.
@@ -194,13 +205,13 @@
server/$CONFIG/deploy/jmx-invoker-service.xml
</programlisting>
Locate the mbean section with the class <literal>org.jboss.jmx.connector.invoker.InvokerAdaptorService</literal>. In that section comment out the line that relates to authenticated users:
- <programlisting>
+ <programlisting> Add in comment out tags if this block is uncommented
<descriptors>
<interceptors>
- <!-- Uncomment to require authenticated users -->
+ <! Uncomment to require authenticated users >
<interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor"
securityDomain="java:/jaas/jmx-console"/>
- <!-- Interceptor that deals with non-serializable results -->
+ <! Interceptor that deals with non-serializable results >
<interceptor code="org.jboss.jmx.connector.invoker.SerializableInterceptor"
policyClass="StripModelMBeanInfoPolicy"/>
</interceptors>
@@ -208,5 +219,5 @@
</programlisting>
</para>
</formalpara>
- </section>
+ </section> -->
</chapter>
\ No newline at end of file
Added: projects/docs/enterprise/5.0/Installation_Guide/en-US/Running_An_Installation.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Running_An_Installation.xml (rev 0)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Running_An_Installation.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -0,0 +1,61 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+<chapter id="Running_An_Installation">
+ <title>Running An Installation</title>
+
+ <section id="Running_a_ZIP_Installation">
+ <title>Running a ZIP Installation</title>
+ <formalpara id="Running_the_mod_jk_zip">
+ <title>Running the mod_jk</title>
+ <para>
+ To load the mod_jk module, the file <filename>httpd/conf/httpd.conf</filename> needs to be updated, and a <filename>workers.properties</filename> file needs to be added in that directory. See <filename>doc/mod_jk/mod_jk.conf.sample</filename> and <filename>doc/mod_jk//workers.properties.sample</filename> for examples of how this can be achieved.
+ </para>
+ </formalpara>
+ <!-- <formalpara>
+ <title>Running Apache Tomcat Native</title>
+ <para>
+ The native library for Tomcat 6 is setup to be used by default, with the <varname>LD_LIBRARY_PATH</varname> and <varname>-Djava.library.path</varname> having been set accordingly within the <filename>catalina.sh</filename> file.
+ </para>
+ </formalpara> -->
+ <!-- <para>
+ For Tomcat 5 set the following:
+ </para>
+ <programlisting>
+ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CATALINA_HOME/server/lib
+ </programlisting>
+ <para>
+ For Tomcat 6 set the following:
+ </para>
+ <programlisting>
+ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CATALINA_HOME/lib
+ </programlisting> -->
+ <!-- <para>
+ Since it depends on the <filename>apr</filename> package, it is best to install <filename>libapr-1.so</filename> at the same place as the above library.
+ </para> -->
+ <!-- <para>
+ For Tomcat 6, start the service and check that you see a message similar to:
+ </para>
+ <screen>
+ Feb 8, 2008 12:27:41 PM org.apache.catalina.core.?AprLifecycleListener init
+ INFO: Loaded APR based Apache Tomcat Native library 1.x.y.
+ Feb 8, 2008 12:27:41 PM org.apache.catalina.core.?AprLifecycleListener init
+ INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
+ Feb 8, 2008 12:27:41 PM org.apache.coyote.http11.?Http11AprProtocol init
+ INFO: Initializing Coyote HTTP/1.1 on http-8080
+ </screen>
+
+ <para>
+ For Tomcat 5, start the service and if the tomcat native library is not used, a message similar to the one below will appear:
+ </para>
+ <screen>
+ INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path
+ </screen>
+ <formalpara>
+ <title>Running log4j for logging in a zip installation of Tomcat 6 </title>
+ <para>
+ In order to use <classname>log4j</classname> logging in Tomcat 6, copy the content of the <filename>extras/</filename> directory into the <filename>lib/</filename> directory and restart Tomcat.
+ </para>
+ </formalpara> -->
+ </section>
+</chapter>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml 2009-08-05 02:58:46 UTC (rev 91998)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Test_Your_Installation.xml 2009-08-05 04:17:02 UTC (rev 91999)
@@ -13,14 +13,14 @@
JBoss Bootstrap Environment
- JBOSS_HOME: /home/vrenish/jboss-eap-4.3/jboss-as
+ JBOSS_HOME: /home/<username>/jboss-eap-5.0/jboss-as
- JAVA: /usr/java/jdk1.5.0_11/bin/java
+ JAVA: /usr/java/jdk1.6.0_15/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/vrenish/jboss-eap-4.3/jboss-as/bin/run.jar:/u sr/java/jdk1.5.0_11/lib/tools.jar
+CLASSPATH: /home/<username>/jboss-eap-5.0/jboss-as/bin/run.jar:/u sr/java/jdk1.6.0_15/lib/tools.jar
=====================================================
@@ -29,7 +29,7 @@
.
.
.
-18:45:50,449 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
+18:45:50,449 INFO [ServerInfo] Java version: 1.6.0_15,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
@@ -38,8 +38,11 @@
</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.
+ There is no <emphasis>Server Started</emphasis> message shown at the console when the server is started using the <literal>default</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/default/log</filename> subdirectory.
</para>
+ <para>
+ In order to start the sever using the <literal>production</literal> profile run the command <code>./run.sh -c production</code> in the console.
+ </para>
</note>
<para>
Now open <literal>http://localhost:8080</literal> in your web browser. (Make sure you dont have anything else already on your machine using that port).<footnote><para>
More information about the jboss-cvs-commits
mailing list