[jboss-cvs] JBossAS SVN: r67557 - projects/docs/trunk/Installation_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Nov 28 08:54:00 EST 2007
Author: skittoli at redhat.com
Date: 2007-11-28 08:54:00 -0500 (Wed, 28 Nov 2007)
New Revision: 67557
Modified:
projects/docs/trunk/Installation_Guide/en-US/Getting_Started.xml
projects/docs/trunk/Installation_Guide/en-US/Installation_Alternatives.xml
projects/docs/trunk/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml
projects/docs/trunk/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
Log:
updates
Modified: projects/docs/trunk/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Getting_Started.xml 2007-11-28 13:50:41 UTC (rev 67556)
+++ projects/docs/trunk/Installation_Guide/en-US/Getting_Started.xml 2007-11-28 13:54:00 UTC (rev 67557)
@@ -14,227 +14,7 @@
<para>For the latest information on supported Operating System / JVM combinations and supported Database platforms, please refer to <ulink url="http://www.jboss.com">http://www.jboss.com</ulink>.
</para>
- <!-- <para>
- The following is a list of supported operating systems and JVM version combination:
- </para>
-
- <table>
- <title>
- Supported Operating System / JVM Combinations.
- </title>
- <tgroup cols="2">
- <colspec colnum="1" colname="OS" colwidth="1*"></colspec>
- <colspec colnum="2" colname="JVM" colwidth="1*"></colspec>
- <tbody>
- <row>
- <entry>
- <emphasis>Operating System</emphasis>
- </entry>
- <entry>
- <emphasis>JVM Version</emphasis>
- </entry>
- </row>
- <row>
- <entry>
- RHEL 4.5 x86
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- RHEL 4.5 x86_64
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- RHEL 5 x86
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- RHEL 5 x86_64
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- RHEL 4.5 x86
- </entry>
- <entry>
- BEA JRockit 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- RHEL 4.5 x86_64
- </entry>
- <entry>
- BEA JRockit 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- RHEL 5 x86
- </entry>
- <entry>
- BEA JRockit 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- RHEL 5 x86_64
- </entry>
- <entry>
- BEA JRockit 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- Solaris SPARC 9
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- MS-Windows 2003 x86
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- MS-Windows 2003 x86_64
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- MS-Windows 2003 x86
- </entry>
- <entry>
- BEA JRockit 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- MS-Windows 2003 x86_64
- </entry>
- <entry>
- BEA JRockit 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- Solaris SPARC 10
- </entry>
- <entry>
- Sun JVM 1.5 latest
- </entry>
- </row>
- <row>
- <entry>
- HP 11i 1,2 RISC
- </entry>
- <entry>
- HP JVM
- </entry>
- </row>
- <row>
- <entry>
- HP 11i, 1,2 ia64
- </entry>
- <entry>
- HP JVM
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- The following is a list of supported databases and database drivers:
- </para>
-
- <table>
- <title>
- Supported Database / Database driver Combinations.
- </title>
-
- <tgroup cols="2">
- <colspec colnum="1" colname="DB" colwidth="1*"></colspec>
- <colspec colnum="2" colname="DB_driver" colwidth="1*"></colspec>
- <tbody>
- <row>
- <entry>
- <emphasis>Database</emphasis>
- </entry>
- <entry>
- <emphasis>Database driver</emphasis>
- </entry>
- </row>
- <row>
- <entry>
- Oracle 9i
- </entry>
- <entry>
- Oracle thin driver
- </entry>
- </row>
- <row>
- <entry>
- Oracle 10g R2
- </entry>
- <entry>
- Oracle thin driver
- </entry>
- </row>
- <row>
- <entry>
- Microsoft SQL Server 2005
- </entry>
- <entry>
- Microsoft JDBC Driver
- </entry>
- </row>
- <row>
- <entry>
- MySQL 5.0
- </entry>
- <entry>
- MySQL Driver
- </entry>
- </row>
- <row>
- <entry>
- Postgres SQL 8.1
- </entry>
- <entry>
- Postgres Driver
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <note>
- <para>
- JBoss uses an embedded Tomcat and does not require a stand-alone Tomcat.
- </para>
- </note> -->
+
</section>
<section id="Pre_Requisites-Configuring_Your_Java_Environment">
@@ -260,7 +40,7 @@
</listitem>
<listitem>
<para>
- Applications that run on 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than their 32-bit cousin.
+ Applications that run on a 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than their 32-bit cousin.
</para>
</listitem>
</itemizedlist>
@@ -278,16 +58,14 @@
</listitem>
<listitem>
<para>
- Download and install the appropriate <literal>-compat RPM</literal> from <literal>JPackage</literal> <ulink url="ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/"> here</ulink>.
-
-Please ensure you choose a matching version of the <literal>-compat</literal> package to the JDK you installed.
-
+ Download and install the appropriate <literal>-compat RPM</literal> from <literal>JPackage</literal> <ulink url="ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/"> here</ulink>. Please ensure you choose a matching version of the <literal>-compat</literal> package to the JDK you installed.
</para>
</listitem>
+
<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.
+ 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
export PATH=$PATH:$JAVA_HOME/bin
</programlisting>
@@ -296,7 +74,7 @@
</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.5 installation as the default source for the <literal>java</literal> and <literal>javac</literal> executables. 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.
<itemizedlist>
<title>Select alternatives for java, javac and java_sdk_1.5.0</title>
<listitem>
Modified: projects/docs/trunk/Installation_Guide/en-US/Installation_Alternatives.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Installation_Alternatives.xml 2007-11-28 13:50:41 UTC (rev 67556)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_Alternatives.xml 2007-11-28 13:54:00 UTC (rev 67557)
@@ -5,13 +5,13 @@
<chapter id="Installation_Alternatives">
<title>Installation Alternatives</title>
<para>
- You can install the JBoss Enterprise Application Platform in one of these three modes: <itemizedlist>
+ You can install the JBoss Application Server in one of these three modes: <itemizedlist>
<listitem>
<para>
<emphasis>Graphical Installer</emphasis>
</para>
<para>
- Using the Graphical Installer can simplify the installation and configuration process for non-sophisticated users. In addition to the basic installation, the installer provides you with basic configuration capabilities, allows you to control whether the JMX interfaces are secured and the ability to enter console username/password.
+ Using the Graphical Installer can simplify the installation and configuration process for non-sophisticated users. In addition to the basic installation, the installer provides you with basic configuration capabilities, allows you to control whether the JMX interfaces are secured and the ability to enter console username/password. The graphical installer is available for <emphasis>subscribed users</emphasis> on <ulink url="https://network.jboss.com"/>.
</para>
</listitem>
<listitem>
@@ -19,7 +19,7 @@
<emphasis>ZIP download</emphasis>
</para>
<para>
- In this form of installation, simply unzip the downloaded zip file to the directory of your choice. You can unzip the platform on any operating system that supports the zip format.
+ In this form of installation, simply unzip the downloaded zip file to the directory of your choice. You can unzip the platform on any operating system that supports the zip format. The zip file is available on <ulink url="http://labs.jboss.com/jbossas/downloads/"/> and for subscribed users on <ulink url="https://network.jboss.com"/>.
</para>
</listitem>
<listitem>
@@ -27,7 +27,7 @@
<emphasis>RPM download</emphasis>
</para>
<para>
- In this form of installation, you can automatically install the platform on a &RHEL; system using the <literal>up2date</literal> command.
+ In this form of installation, you can automatically install the platform on a &RHEL; system using the <literal>up2date</literal> command. The RPM installer is available for <emphasis>subscribed users</emphasis> on the Red Hat Network (RHN) on <ulink url="http://rhn.redhat.com"/>.
</para>
</listitem>
</itemizedlist>
Modified: projects/docs/trunk/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml 2007-11-28 13:50:41 UTC (rev 67556)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml 2007-11-28 13:54:00 UTC (rev 67557)
@@ -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.
Modified: projects/docs/trunk/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2007-11-28 13:50:41 UTC (rev 67556)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2007-11-28 13:54:00 UTC (rev 67557)
@@ -21,10 +21,12 @@
<itemizedlist>
<listitem>
<para>
- Unzip <literal>jboss-4.2.2.GA.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). <programlisting>
- [vsr]$ <literal>cd jbossinstallationdir</literal>
- [vsr]$ <literal>jar -xvf jboss-4.2.2.GA.zip</literal></programlisting>
- </para>
+ Unzip <literal>jboss-4.2.2.GA.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).
+<programlisting>
+[vsr]$ <literal>mkdir jbossinstallationdir</literal>
+[vsr]$ <literal>cd jbossinstallationdir</literal>
+[vsr]$ <literal>jar -xvf jboss-4.2.2.GA.zip</literal></programlisting>
+ </para>
</listitem>
<listitem>
<para>
@@ -35,13 +37,13 @@
</para>
</section>
- <section id="Post-Installation">
+<!-- <section id="Post-Installation">
<title>
Post Installation Security Configuration
</title>
<para>
- When installed from the zip archive, all JBoss services require authentication to access most JBoss services, including administrative services. Additionally no user accounts are set up. This is to stop default user/password-based attacks.
+ When installed from the zip archive, all the HTTP and JMX services require authentication for access.
</para>
<para>
@@ -157,15 +159,18 @@
<programlisting><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>
</descriptors></programlisting>
</section>
+
+ -->
+
</chapter>
Modified: projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2007-11-28 13:50:41 UTC (rev 67556)
+++ projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2007-11-28 13:54:00 UTC (rev 67557)
@@ -5,13 +5,15 @@
<chapter id="Test_your_Installation">
<title>Test your Installation</title>
<para>
- After you have installed the JBoss Application Server, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
+ After you have installed the JBoss Application Server, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system.
+
+ <!--Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:-->
</para>
<programlisting>
[vrenish at vinux bin]$ ./run.sh
=====================================================
-
+<!--
JBoss Bootstrap Environment
JBOSS_HOME: /home/vrenish/jboss-4.2.2
@@ -36,11 +38,12 @@
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
+18:45:59,659 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml-->
+
</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.
+ Note that there is no "Server Started" 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. You may run the production This message may be observed in the <filename>server.log</filename> file located in the <filename>server/defaut/log</filename> subdirectory.
</para>
</note>
<para>
Modified: projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2007-11-28 13:50:41 UTC (rev 67556)
+++ projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2007-11-28 13:54:00 UTC (rev 67557)
@@ -5,7 +5,12 @@
<chapter id="Uninstall_JBoss">
<title>Uninstall JBoss</title>
<para>
- If you used the GUI installer to install &JBEAP;, then an automatic uninstaller is also installed. From the GUI the uninstaller can be selected from the JBoss program group, if one was created at installation time. A second option is to run this uninstaller from the command line. Within the &JBEAP; Installation directory you will find a directory called <filename>Uninstaller</filename>. Inside the <filename>Uninstaller</filename> directory you will find a jar file named <filename>uninstaller.jar</filename>. Run the uninstaller from the command line using the <literal>jar</literal> utility.
+ If you used the GUI installer to install JBoss Application Server, then an automatic uninstaller is also installed. From the GUI the uninstaller can be selected from the JBoss program group, if one was created at installation time.
+<note><title>Note</title><para>
+If you installed on a linux system and did not set <emphasis>JAVA_HOME</emphasis> in environment, this method will not work as it invokes: <filename>/bin/sh -c '$JAVA_HOME/bin/java -jar /home/cdan/EnterprisePlatform-4.2.0.GA_CP01_Release/Uninstaller/uninstaller.jar' </filename></para></note>
+
+
+ A second option is to run the uninstaller from the command line. Within the JBoss Application Server Installation directory you will find a directory called <filename>Uninstaller</filename>. Inside the <filename>Uninstaller</filename> directory you will find a jar file named <filename>uninstaller.jar</filename>. Run the uninstaller from the command line using the <literal>jar</literal> utility.
<programlisting>
[vsr]$ java -jar uninstaller.jar
</programlisting>
@@ -21,7 +26,7 @@
</para>
<para>
- If no uninstaller is available, and &JBEAP; was installed using the zip file, it may be uninstalled by simply deleting the &JBEAP; installed directory. <!-- If JBoss was installed using the rpms -->
+ If no uninstaller is available, and JBoss Application Server was installed using the zip file, it may be uninstalled by simply deleting the JBoss Application Server's installation directory. <!-- If JBoss was installed using the rpms -->
</para>
</chapter>
More information about the jboss-cvs-commits
mailing list