[jboss-cvs] JBossAS SVN: r79007 - projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 2 02:17:24 EDT 2008
Author: skittoli at redhat.com
Date: 2008-10-02 02:17:23 -0400 (Thu, 02 Oct 2008)
New Revision: 79007
Modified:
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml
Log:
updates
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml 2008-10-01 23:54:48 UTC (rev 79006)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml 2008-10-02 06:17:23 UTC (rev 79007)
@@ -1050,7 +1050,7 @@
<section id="Getting_Started-Pre_Requisites">
<title>Pre-Requisites</title>
<para>
- You must have adequate disk space to install JDK and JBoss Application Server while also allowing enough space for your applications. Before installing JBoss Application Server 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"/> for more information.
+ You must have adequate disk space to install JDK and JBoss Application Server while also allowing enough space for your applications. Before installing JBoss Application Server 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.
</para>
<section id="Pre_Requisites-Hardware_and_Operating_System_Requirements">
<title>Hardware and Operating System Requirements</title>
@@ -1063,7 +1063,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> before you install JBoss Application Server. 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 on a 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>JDK 1.5</emphasis> or <emphasis>JDK 1.6</emphasis> before you install JBoss Application Server. 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 on a 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>
@@ -1088,15 +1088,15 @@
</listitem>
</itemizedlist>
<itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_Linux">
- <title>Installing and Configuring 32-bit Sun JDK 5.0 on Linux</title>
+ <title>Installing and Configuring 32-bit Sun JDK 5.0 or JDK 6.0 on Linux</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"/>. 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 5.0 or JDK 6 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"/> for JDK 5.0 or <ulink url="http://java.sun.com/javase/downloads/"/> for JDK 6.0. Select the JDK 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>
<para>
- If you don't want to use SysV service scripts you can install the "self-extracting file" for Linux instead of choosing the "RPM in self-extracting" 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.
+ If you do not want to use SysV service scripts you can install the "self-extracting file" for Linux instead of choosing the "RPM in self-extracting" 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.
</para>
</listitem>
<listitem>
@@ -1108,8 +1108,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_14 is the JDK installation directory.
-export JAVA_HOME=/usr/java/jdk1.5.0_14
+<programlisting>#In this example /usr/java/jdk1.6.0_07 is the JDK installation directory.
+export JAVA_HOME=/usr/java/jdk1.6.0_07
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.
@@ -1117,9 +1117,9 @@
</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 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.
+ If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.5 or JDK1.6 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>
+ <title>Select alternatives for java, javac and java_sdk_1.<x></title>
<listitem>
<para>
As root, type the following command at the shell prompt and you should see something like this: <programlisting>
@@ -1136,7 +1136,7 @@
</listitem>
<listitem>
<para>
- Repeat the same for javac and java_sdk_1.5.0. <programlisting>
+ Repeat the same for javac and java_sdk_1.<x> <programlisting>
[root at vsr ~]$ /usr/sbin/alternatives --config javac
There are 1 programs which provide 'javac'.
Selection Command
@@ -1152,7 +1152,7 @@
*+ 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.
+ You should verify that java, javac and java_sdk_1.<x> all point to the same manufacturer and version.
</para>
</listitem>
</itemizedlist>
@@ -1175,10 +1175,10 @@
</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>
+ <title>Installing and Configuring 32-bit Sun JDK 5.0 or 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"/>. 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 5.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"/> for JDK 5.0 or <ulink url="http://java.sun.com/javase/downloads/"/> for JDK 6.0. Choose the JDK 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>
@@ -1215,6 +1215,20 @@
<para>
In this form of installation, simply unzip the downloaded zip file to the directory of your choice. You can unzip the JBoss Application Server on any operating system that supports the zip format. The zip file is available on <ulink url="http://labs.jboss.com/jbossas/downloads/"/>. Please ensure you have met the pre-requisites required before proceeding with your installation. Pre-requisites are discussed in <xref linkend="Getting_Started-Pre_Requisites"/>. Further details on installation using the Binary files are discussed in <xref linkend="binary_installation"/>
</para>
+ <para>
+ JBossAS 5.0.0 can be compiled with both Java5 and Java6. The Java5 compiled binary is our primary/recommended binary distribution. It has undergone rigorous testing and can run under both a Java 5 and a Java 6 runtime. When running
+ under Java 6 you need to manually copy the following libraries from the <filename>JBOSS_HOME/client</filename> directory to the <filename>JBOSS_HOME/lib/endorsed</filename> directory, so that the JAX-WS 2.0 apis supported by JBossWS are used:
+ </para>
+<screen>* jbossws-native-saaj.jar
+* jbossws-native-jaxrpc.jar
+* jbossws-native-jaxws.jar
+* jbossws-native-jaxws-ext.jar </screen>
+ <para>
+ Another alternative is to download the jdk6 distribution <ulink url="http://downloads.sourceforge.net/jboss/jboss-5.0.0.CR2-jdk6.zip?modtime=1221686600&big_mirror=1">(<filename>jboss-5.0.0.CR2-jdk6.zip</filename>)</ulink> in which case no configuration changes are required.
+
+ Please refer to the <ulink url="http://sourceforge.net/project/shownotes.php?release_id=627020&group_id=22866">release notes</ulink> for additional information about running with JDK 6.
+ </para>
+
</listitem>
<listitem>
@@ -1239,7 +1253,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 rpm/zip archive.
</para>-->
<para>
- Four types of server configurations will be included in your installation - <emphasis>minimal</emphasis>, <emphasis>default</emphasis>, and <emphasis>all</emphasis>.
+ Three types of server configurations will be included in your installation - <emphasis>minimal</emphasis>, <emphasis>default</emphasis>, and <emphasis>all</emphasis>.
</para>
</chapter>
<chapter id="binary_installation">
@@ -1249,10 +1263,25 @@
<title>Download and Installation</title>
<para>
- You can download the Binary zip file from <ulink url="http://labs.jboss.com/jbossas/downloads/">http://labs.jboss.com/jbossas/downloads/</ulink>.
+ You can download the Binary zip files from <ulink url="http://labs.jboss.com/jbossas/downloads/">http://labs.jboss.com/jbossas/downloads/</ulink>.
</para>
-
<para>
+ There are two binary distributions available:
+ </para>
+<orderedlist>
+ <listitem>
+ <para>
+ <ulink url="http://downloads.sourceforge.net/jboss/jboss-5.0.0.CR2.zip?modtime=1221686752&big_mirror=1">jboss-5.0.0.CR2.zip</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://downloads.sourceforge.net/jboss/jboss-5.0.0.CR2-jdk6.zip?modtime=1221686600&big_mirror=1">jboss-5.0.0.CR2-jdk6.zip</ulink>
+ </para>
+ </listitem>
+</orderedlist>
+
+ <para>
In this form of installation, simply unzip the downloaded zip file to the directory of your choice on any operating system that supports the zip format.
<itemizedlist>
<listitem>
@@ -1304,16 +1333,18 @@
<section><title>Installing and configuring ANT</title>
<para>
- <ulink url="http://ant.apache.org/">Apache Ant</ulink> is a Java-based build tool. Instead of using an extended model using shell-based commands, Ant is extended using Java classes that uses XML-based configuration files. The configuration files call out a target tree that executes various tasks. Each task is run by an object that implements a particular Task interface.
+ <ulink url="http://ant.apache.org/">Apache Ant</ulink> is a Java-based build tool. Instead of using an extended model using shell-based commands, Ant is extended using Java classes that use XML-based configuration files. The configuration files call out a target tree that executes various tasks. Each task is run by an object that implements a particular Task interface.
This gives you the ability to perform cross platform builds. Please also note that if needed, Ant provides an <exec> task that allows commands to be executed based on the Operating System it is executing on. For more information on Apache ANT please click <ulink url="http://ant.apache.org/">here</ulink>.
</para>
<para>
- You will need to build your JBoss Application Server source files before you can run the application server. Firstly please download and install Apache Ant version 1.5 or 1.6 from the <ulink url="http://ant.apache.org/">Apache Ant Archive</ulink>. Apache Ant versions 1.5 and 1.6 have been tested on JBoss Application Server 5.0.0.
-
-</para>
+ You will need to build your JBoss Application Server source files before you can run the application server. Apache Ant is shipped with the JBoss Application Server source files and can be executed from the <filename><source_directory>/tools/bin</filename> directory.
+ </para>
+ <para>
+ The source files can also be built using Apache Maven which is also shipped with the JBoss Application Server source files under <filename><source_directory>/tools/maven</filename> directory. For more information about Apache Maven, please refer to <ulink url="">http://maven.apache.org/</ulink>.
+ </para>
-<para>
- On downloading ANT, please unzip the compressed file and copy to the desired location. Like Java, you also need to set the environment variables for Apache ANT. The following example illustrates a desirable configuration for the <filename>.bashrc</filename> file. In the example the file is edited using the gnome text editor (<command>gnome</command>).
+ <para>
+ Like Java, you also need to set the environment variables for Apache ANT and/or Apache Maven. The following example illustrates a desirable configuration for the <filename>.bashrc</filename> file. In the example the file is edited using the gnome text editor (<command>gedit</command>).
<screen>[user at localhost ~]$ gedit .bashrc
@@ -1323,15 +1354,18 @@
fi
......
# User specific aliases and functions
-# The following are the environment variables for Java, ANT and JBoss
-
-export JAVA_HOME=/usr/java/jdk1.5.0_14
+# The following are the environment variables for Java , ANT and Maven
+
+export JAVA_HOME=/usr/java/jdk1.6.0_07/
export PATH=$PATH:$JAVA_HOME/bin
-export ANT_HOME=/usr/ant/apache-ant-1.6.0
+export ANT_HOME=/home/downloads/jboss-<source_directory>/tools/
export PATH=$PATH:$ANT_HOME/bin
+
+export MAVEN_HOME=/home/downloads/jboss-<source_directory>/tools/maven
+export PATH=$PATH:$MAVEN_HOME/bin
</screen>
-
+
</para>
<para>
To implement the changes you've made to the <filename>.bashrc</filename> file, type the following on a terminal.
@@ -1341,18 +1375,18 @@
If any errors are displayed, please check your <filename>.bashrc</filename> file for errors and ensure that all directory paths are correct.
</para>
-
-
</section>
-
- <section><title>Building with Apache ANT</title>
+
+<section><title>Building with Apache ANT</title>
<para>
To build the JBoss Application Server source files with Apache ANT, from a terminal change directory to where the unzipped source files are. In the following example we are assuming that the source files were copied and unzipped in the logged in user's <filename>downloads</filename> folder.
<screen>[user at localhost]$ cd /home/user/downloads/<literal>jboss-<release>-src</literal>/build
[user at localhost build]$ ls
-build.bat build.log build.sh build.xml eclipse.psf local.properties VersionRelease.java
-build-distr.xml build-release.xml build-thirdparty.xml docs etc output
+aspects component-matrix docbook-support iiop jmx mbeans security system-jmx tools
+bootstrap connector ejb3 j2se jmx-remoting messaging server testsuite varia
+build console embedded jbossas main pom.xml spring-int thirdparty webservices
+cluster deployment hibernate-int jbossmq management profileservice system tomcat
</screen>
From the contents of the <filename>build</filename> directory above, you can see the <filename>build.xml</filename> file which is used by Apache ANT as a configuration file when building your source files.
The next step is to perform the build using Apache ANT as illustrated below.
@@ -1372,13 +1406,19 @@
BUILD SUCCESSFUL
Total time: 2 seconds</screen>
-A successful build will have the above message. If your build fails, please check the error log and ensure that your configuration files and environment variables are correctly set. The JBoss Application Server files are built under the <filename>build/jboss-<release></filename> directory as indicated below.
+A successful build will have the above message. If your build fails, please check the error log and ensure that your configuration files and environment variables are correctly set. The JBoss Application Server files are built under the <filename>build/output/jboss-<release></filename> directory as indicated below.
+<note><title>Note</title>
+ <para>At this point the JBoss Application Server source files build is a hybrid one (builds in both Ant and Maven) because it declares all JBoss dependencies as maven2 artifacts, however after the dependencies are resolved/imported the legacy ant based build is used to compile and build the distribution. The JBoss Application Server source files will change to a full maven build soon.
+ </para>
+</note>
+
<screen>[user at localhost build]$ ls
-build.bat build.log build.sh build.xml eclipse.psf jboss-<release> local.properties VersionRelease.java
-build-distr.xml build-release.xml build-thirdparty.xml docs etc outputjboss-<release>
+build.bat build-old.xml build-thirdparty-old.xml eclipse.psf output
+build-distr.xml build-release.xml build.xml etc pom.xml
+build.log build.sh docs local.properties VersionRelease.java
-[user at localhost build]$ cd jboss-<release>
+[user at localhost build]$ cd output/jboss-<release>
[user at localhost build]$ ls
bin client docs lib server
</screen>
@@ -1461,38 +1501,39 @@
<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, open the <filename>JBOSS_DIST/jboss-<release>/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.
</para>
+ <para>
+ Your output should look similar to the following (accounting for installation directory differences) and contain no error or exception messages:
+ </para>
<screen>
[samson at dhcp-1-150 bin]$ sh run.sh
=========================================================================
-
-JBoss Bootstrap Environment
-
-JBOSS_HOME: /downloads/jboss-5.0.0.Beta
-
-JAVA: /usr/java/jdk1.5.0_14/bin/java
-
-JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
-
-CLASSPATH: /downloads/jboss-5.0.0.Beta/bin/run.jar:/usr/java/jdk1.5.0_14/lib/tools.jar
-
+ JBoss Bootstrap Environment
+
+ JBOSS_HOME: /downloads/jboss-5.0.0.CR2
+
+ JAVA: /usr/local/jdk1.6.0_07//bin/java
+ JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
+
+ CLASSPATH: /downloads/jboss-5.0.0.CR2/bin/run.jar:/usr/local/jdk1.6.0_07//lib/tools.jar
=========================================================================
-
-09:52:23,793 INFO [ServerImpl] Starting JBoss (Microcontainer)...
+
+15:23:05,038 INFO [ServerImpl] Starting JBoss (Microcontainer)...
+15:23:05,042 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)
.
-.
.
-09:56:59,231 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
-09:56:59,246 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200803061035)] Started in 4m:35s:367ms
-</screen>
- <note>
+...output truncated
+.
+.
+15:25:18,401 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
+15:25:18,556 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
+15:25:18,620 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)] Started in 2m:13s:511ms</screen>
+ <!--<note>
<para>
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. This message may be observed in the <filename>server.log</filename> file located in the <filename>server/defaut/log</filename> subdirectory.
</para>
- </note>
+ </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>
Note that on some machines, the name localhost may not resolve properly and you may need to use the local loopback address 127.0.0.1 instead.</para></footnote> The contents of your page should look similar to the following: <xref linkend="Test_your_Installation-Test_your_Installation"/>.
More information about the jboss-cvs-commits
mailing list