[jboss-cvs] JBossAS SVN: r65736 - projects/docs/trunk/Installation_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Oct 1 20:08:05 EDT 2007
Author: mhideo at redhat.com
Date: 2007-10-01 20:08:05 -0400 (Mon, 01 Oct 2007)
New Revision: 65736
Removed:
projects/docs/trunk/Installation_Guide/en-US/Book_Info.xml
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_Guide.xml
projects/docs/trunk/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml
projects/docs/trunk/Installation_Guide/en-US/Installation_With_RHN.xml
projects/docs/trunk/Installation_Guide/en-US/Installation_With_RPM_Download.xml
projects/docs/trunk/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
projects/docs/trunk/Installation_Guide/en-US/Introduction.xml
projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
Log:
removing redundant data due to directory structure change
Deleted: projects/docs/trunk/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Book_Info.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Book_Info.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,34 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<bookinfo id="JBOSS_Enterprise_Application_Platform">
- <title>JBoss Enterprise Application Platform</title>
- <subtitle>Installation Guide</subtitle>
- <issuenum>4.2</issuenum>
- <productnumber>1</productnumber>
- <pubdate>Sep, 2007</pubdate>
- <isbn>N/A</isbn>
- <abstract><para>This Installation Guide documents relevant information regarding
-the installation of JBoss Enterprise Application Platform 4.2.0.CP01</para></abstract>
- <mediaobject>
- <imageobject>
- <imagedata fileref="Common_Content/images/rhlogo-chapter-title.png" />
- </imageobject>
- </mediaobject>
- <publisher>
- <publishername>
- <inlinemediaobject>
- <imageobject>
- <imagedata fileref="Common_Content/imagesrhlogo-title.png" />
- </imageobject>
- </inlinemediaobject>
- </publishername>
- </publisher>
- <copyright>
- <year>&YEAR;</year>
- <holder>&FORMAL-RHI;</holder>
- </copyright>
- <xi:include href="Common_Content/Boilerplate.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</bookinfo>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Getting_Started.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Getting_Started.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,544 +0,0 @@
-<?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="Getting_Started">
- <title>Getting Started</title>
- <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.
- </para>
- <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements">
- <title>Hardware and Operating System Requirements</title>
-
- <para>For the latest information on supported Operating System / JVM combinations and supported Database platforms, please refer to <ulink url="http://www.redhat.com/jboss/platforms/application/">http://www.redhat.com/jboss/platforms/application/</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">
- <title>Configuring Your Java Environment</title>
- <para>
- You must have a working installation of <emphasis role="bold">JDK 1.5</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 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>
- <para>
- Wider datapath: The pipe between RAM and CPU is doubled, which improves the performance of memory-bound applications.
- </para>
- </listitem>
- <listitem>
- <para>
- 64-bit memory addressing gives virtually unlimited (1 exabyte) heap allocation. However large heaps affect garbage collection.
- </para>
- </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.
- </para>
- </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.
- </para>
- </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>
- <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.
- </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.
- </para>
- </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.
-
- </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.
-export JAVA_HOME=/usr/java/jdk1.5.0_11
-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.
- </para>
- </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.
- <itemizedlist>
- <title>Select alternatives for java, javac and java_sdk_1.5.0</title>
- <listitem>
- <para>
- As root, type the following command at the shell prompt and you should see something like this: <programlisting>
-[root at 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 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
-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'.
- 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_HOME</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 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)
-</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>
- <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.
- </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.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </section>
-
- </section>
-
- <section id="Getting_Started-Components_of_JBoss_Enterprise_Application_Platform_version_4.2">
- <title>Components of &JBEAP; &JBEAPVERS;</title>
-
- <para>For current information on the revision level of included components please refer to <ulink url="http://www.redhat.com/jboss/platforms/application/">http://www.redhat.com/jboss/platforms/application/</ulink>.
- </para>
-
- <!--<para>
- Below is a listing of the components of &JBEAP; and their revision level at the time of writing. For an updated list of component revision levels please refer to <ulink url="http://www.redhat.com/docs/manuals/jboss">http://www.redhat.com/docs/manuals/jboss</ulink>.
- </para>
-
- <para>
- <table id="Components_of_JBoss_Enterprise_Application_Platform_version_4.2-Application_Platform_4.2">
- <title>Application Platform 4.2</title>
- <tgroup cols="2">
- <colspec colname="Project" colnum="1" colwidth="4*"></colspec>
- <colspec colname="Version" colnum="2" colwidth="4*"></colspec>
- <thead>
- <row>
- <entry>
- Project
- </entry>
- <entry>
- Version
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- Hibernate
- </entry>
- <entry>
- 3.2.4.SP1_CP01
- </entry>
- </row>
- <row>
- <entry>
- Hibernate Entity Manager
- </entry>
- <entry>
- 3.2.1
- </entry>
- </row>
- <row>
- <entry>
- Hibernate Annotations
- </entry>
- <entry>
- 3.2.1
- </entry>
- </row>
- <row>
- <entry>
- JBoss AS
- </entry>
- <entry>
- 4.2.0
- </entry>
- </row>
- <row>
- <entry>
- JBoss MQ
- </entry>
- <entry>
- 4.2.0
- </entry>
- </row>
- <row>
- <entry>
- JBoss Web
- </entry>
- <entry>
- 2.0.0
- </entry>
- </row>
- <row>
- <entry>
- JBoss Transactions
- </entry>
- <entry>
- 4.2.3.SP4
- </entry>
- </row>
- <row>
- <entry>
- JTA
- </entry>
- <entry>
- 1.0.1B
- </entry>
- </row>
- <row>
- <entry>
- JBoss EJB3
- </entry>
- <entry>
- RC10
- </entry>
- </row>
- <row>
- <entry>
- JBoss WS
- </entry>
- <entry>
- 1.2.1
- </entry>
- </row>
- <row>
- <entry>
- JBoss AOP
- </entry>
- <entry>
- 1.5.5
- </entry>
- </row>
- <row>
- <entry>
- JBoss Remoting
- </entry>
- <entry>
- 2.0.0.SP4
- </entry>
- </row>
- <row>
- <entry>
- JBoss Serialization
- </entry>
- <entry>
- 1.0.3
- </entry>
- </row>
- <row>
- <entry>
- JBoss Cache
- </entry>
- <entry>
- 1.4.1.SP3
- </entry>
- </row>
- <row>
- <entry>
- JGroups
- </entry>
- <entry>
- 2.4.1.SP3
- </entry>
- </row>
- <row>
- <entry>
- JBoss Seam
- </entry>
- <entry>
- 1.2.0.AP
- </entry>
- </row>
- <row>
- <entry>
- jBPM (JPDL)
- </entry>
- <entry>
- 3.1.4 (Seam dependency)
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </para> -->
- </section>
-
-</chapter>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Installation_Alternatives.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Installation_Alternatives.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_Alternatives.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,42 +0,0 @@
-<?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="Installation_Alternatives">
- <title>Installation Alternatives</title>
- <para>
- You can install the JBoss Enterprise Application Platform 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.
- </para>
- </listitem>
- <listitem>
- <para>
- <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.
- </para>
- </listitem>
- <listitem>
- <para>
- <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.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- <para>
- 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>, <emphasis>production</emphasis> and <emphasis>all</emphasis>. The Getting Started Guide explains in detail the different server configuration file sets.
- </para>
-</chapter>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Installation_Guide.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Installation_Guide.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_Guide.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,16 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Installation_Alternatives.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Installation_Using_Graphical_Installer.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Installation_With_ZIP_Download.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Installation_With_RHN.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" />
-</book>
-
Deleted: 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-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,151 +0,0 @@
-<?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="Installation_Using_Graphical_Installer">
- <title>Installation Using The Graphical Installer</title>
- <itemizedlist id="Installation_Using_Graphical_Installer-Launching_the_Graphical_Installer">
- <title>Launching the Graphical Installer</title>
- <listitem>
- <para>
- The installer is an executable JAR file named <filename>enterprise-installer-<replaceable><release></replaceable>.jar</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- On many operating systems, you can run executable JARs by double-clicking them. If your system doesn't support that, you can run the installer directly from the command line: <programlisting>[vsr]$ java -jar enterprise-installer-<replaceable><release></replaceable>.jar</programlisting>
- </para>
- </listitem>
- <listitem>
- <para>
- The installer will then guide you through a series of installation steps explained in detail in the following section. You can quit the installation process any time before you confirm the final installation.
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist id="Installation_Using_Graphical_Installer-Installation_Steps">
- <title>Installation Steps</title>
- <listitem>
- <para>
- Choose the language to be used for the installation instructions and press the OK button.
- </para>
- </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.
- </para>
- </listitem>
- <listitem>
- <para>
- Select the Installation Path where you would like &JBEAP; 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>
- <para>
- It does not matter where on your system you install &JBEAP;, however note that installing &JBEAP; 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.
- </para>
- </note>
- <figure id="Installation_Steps-Select_Installation_Path">
- <title>Select Installation Path</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/step3.png" />
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>
- Configure JMX Security - In this section you can control the security settings for the JMX interfaces. You can choose to secure the following services:
- </para>
- <para>
- <simplelist type="inline">
- <member>
- <emphasis role="bold">jmx-console.war</emphasis>
- </member>
- <member>
- <emphasis role="bold">web-console.war</emphasis>
- </member>
- <member>
- <emphasis role="bold">jmx-invoker-services</emphasis>
- </member>
- <member>
- <emphasis role="bold">http invoker</emphasis>
- </member>
- </simplelist>
- </para>
- <para>
- It is recommended that you click to enable security for all services and change the username/password from the default <literal>admin</literal>/<literal>admin</literal> values.
- </para>
- <figure id="Installation_Steps-Configure_JMX_Security">
- <title>Configure JMX Security</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/step4.png" />
- </imageobject>
- </mediaobject>
- </figure>
- <note>
- <para>
- The JMX and web console would ask for your password if you install from the GUI installer.
- </para>
- </note>
- </listitem>
- <listitem>
- <para>
- You can find the latest release notes available here: <ulink url="http://www.redhat.com/docs/manuals/jboss">http://www.redhat.com/docs/manuals/jboss</ulink>. Read the release notes information carefully to know about important compatibility and configuration issues, library updates, feature requests and bugs, links to additional documentation and license information.
- </para>
- </listitem>
- <listitem>
- <para>
- &JBEAP; is now ready to install. Verify the installation path displayed in the summary screen before you hit the Next button. Pressing the Next button will begin the installation.
- </para>
- </listitem>
- <listitem>
- <para>
- You can add the JBoss Platform menu in the XDG menu and also choose to create shortcuts on the desktop. If you select the "Create additional shortcuts on the desktop" checkbox, the installer will create the following shortcuts: <itemizedlist>
- <listitem>
- <para>
- Shortcut to Start the application server
- </para>
- </listitem>
- <listitem>
- <para>
- Shortcut to Stop the application server
- </para>
- </listitem>
- <listitem>
- <para>
- Shortcut to the documentation
- </para>
- </listitem>
- <listitem>
- <para>
- Shortcut to the JMX Console
- </para>
- </listitem>
- <listitem>
- <para>
- Shortcut to start the demo application
- </para>
- </listitem>
- </itemizedlist>
- </para>
- <para>
- If you run the installer as the root user you can choose to create these shortcuts for all users.
- </para>
- <figure id="Installation_Steps-Create_Desktop_Shortcuts">
- <title>Create Desktop Shortcuts</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/step8.png" />
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>
- You are done with the installation! You should now have a directory called <filename>EnterprisePlatform-4.2.0.GA_CP01</filename>, or whatever other name you specified. To explore the Platform directory structure and to understand the layout in detail, refer to the Getting Started Guide.
- </para>
- </listitem>
- </itemizedlist>
-</chapter>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Installation_With_RHN.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Installation_With_RHN.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_With_RHN.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,142 +0,0 @@
-<?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="Installation_With_RHN">
- <title>Installation With RHN</title>
-
- <section id="Introduction_to_RHN">
- <title>Introduction</title>
- <para>
- The Red Hat Network is an Internet solution for managing a single Red Hat Enterprise Linux system or a network of Red Hat Enterprise Linux systems. All Security Alerts, Bug Fix Alerts, and Enhancement Alerts (collectively known as Errata Alerts) can be downloaded directly from Red Hat or your own custom collection. You can even schedule updates for delivery to your system immediately after release.
- </para>
-
- <para>
- The Red Hat Update Agent <command>up2date</command> provides your initial connection to Red Hat Network. Red Hat Enterprise Linux 4 and newer systems use the Red Hat Update Agent to register with RHN. Registration involves creating a unique RHN username and password, probing the hardware on your system to create a Hardware Profile, and probing the software packages installed on your system to create a Package Profile. This information is sent to RHN and RHN returns a unique System ID to your system. Once registered, the Red Hat Update Agent enables channel subscription, package installs, and management of System Profiles.
- </para>
-
- <para>
- The Red Hat Update Agent, as the base component of RHN, is designed to manage a single system. It allows the system's superuser to view and apply Errata to the system. The RHN web interface facilitates the management, monitoring, and provisioning of a large deployment of systems, including the configuration of the Red Hat Update Agent for each system. More information about the RHN can be viewed on <ulink url="https://www.redhat.com/rhn/">https://www.redhat.com/rhn/</ulink>.
- </para>
- </section>
- <section id="Install_using_RHN"><title>Installation using RHN</title>
- <para>
- To be able to install &JBEAP; using RHN, please firstly ensure that you have met the pre-requisites described in <xref linkend="Getting_Started-Pre_Requisites"/> and subscribe to the appropriate child channel (refer to the instructions that follow).
- </para>
- <para>
- Software channels provide a well-defined method to determine which packages should be available to a system for installation or upgrade, based upon its operating systems, packages, and functionality. After logging in to your account on the RHN website at <ulink url="http://rhn.redhat.com">http://rhn.redhat.com</ulink> you can click on a channel name to view its Channel Details page.
- </para>
- <para>
- You can use the following steps to subscribe a system to the Application Platform channel. This channel will only be available for a valid subscription. Use the Channels tab to view the software channels available for your account.
- </para>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- For a system that is already registered to Red Hat Network (RHN), log in to your account.
- </para>
- </listitem>
- <listitem>
- <para>
- Select the Systems tab along the top menu. This will bring up the System Overview.
- </para>
- </listitem>
- <listitem>
- <para>
- If the System Overview menu shows System Groups, select View Systems, to see the Systems list.
- </para>
- </listitem>
- <listitem>
- <para>
- Select the desired system by clicking the system name link under the System column.
- </para>
- </listitem>
- <listitem>
- <para>
- Select the Alter Channel Subscriptions link under the Subscribed Channels section (on the right side of the page).
- </para>
- </listitem>
- <listitem>
- <para>
- To modify the child channels associated with this system, use the checkboxes next to the channels and click the Change Subscriptions button. You will receive a success message or be notified of any errors.
- </para>
- </listitem>
- </itemizedlist>
- </para>
-<!--Not sure how this works with yum for RHEL5 , so commenting out now -->
- <!--<para>
- To verify that the child channel is now associated with the system, use the up2date command with the - -show-channels option from the system. For example:
- </para>
-
-<screen><command>up2date - -show-channels</command></screen>
-<para>
- Please ensure that <filename>jbappplatform-*-rpm</filename> is listed in your channels.
- </para>
--->
- <formalpara>
- <title>
- On Red Hat Enterprise Linux 4:
- </title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- Subscribe to the child channel: <filename>jbappplatform-4-[i386|x86_64]-[as|es]-4-rpm</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- Run the following command:
-<screen><command>up2date --installall jbappplatform-4-[i386|x86_64]-[as|es]-4-rpm</command></screen>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>
- On Red Hat Enterprise Linux 5:
- </title>
- <para>
-<itemizedlist>
- <listitem>
- <para>
- Subscribe to the child channel: <filename>jbappplatform-4-[i386|x86_64]-server-5-rpm</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- Run the following command:
-<screen><command>yum install jbossas jboss-seam rh-eap-docs jboss-profiler</command></screen>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
-
-
-<!--
-
-
-<screen><command>up2date - -installall jbappplatform-4-x86_64-server-5-rpm</command></screen>
-
- For an i386 architecture running Red Hat Enterprise Linux Advanced Server 5 the following syntax will be used:
-
-<screen><command>up2date - -installall jbappplatform-4-i386-server-5-rpm</command></screen>-->
-
- <!--jbossas</command></screen>-->
-
- <!--Red Hat Application Stack V.1.1, includes two versions of JBossAS. The package 'jbossas' will function with both 1.4 and 5 JVMs. The package 'jbossas-ejb3' includes a technology preview of EJB3 (1.0.0-RC9) and requires a working Java 5 installation. Only one version may be installed at a time.
-
- If you are upgrading from version 1 of Red Hat Application Stack and want to install the EJB3 package you must uninstall the 'jbossas' package first, and install a Java 5 JVM.
-
- Please note that in order to use EJB3 ('jbossas-ejb3') you will need a working Java 1.5 installation. 'jbossas' can be used with 1.4.2 as before.-->
-
-
- <!-- <para>
- </para> -->
-
-
- </section>
-</chapter>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Installation_With_RPM_Download.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Installation_With_RPM_Download.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_With_RPM_Download.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,28 +0,0 @@
-<?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="Installation_With_RPM_Download">
- <title>Installation With RPM Download</title>
- <para>
- In this form of installation, install the RPMs to the directory of your choice. <itemizedlist>
- <listitem>
- <para>
- Install the rpms to the location of your choice. You can do this using the following command. <programlisting>
-[vsr]$ <literal>rpm -ivf <rpm filename></literal></programlisting>
- </para>
- </listitem>
- <listitem>
- <para>
- You are done with the installation! You should now have a directory called <literal>jboss-eap-4.2</literal>. Please refer to the Directory Structure section to understand and explore the Platform Directory Structure.
- </para>
- </listitem>
- <listitem>
- <para>
- When installed from the rpm file, all JBoss services are left in a developer-friendly state requiring no authentication to access most JBoss services, including administrative services. The JMX-console and the Web-Console are not secured with a password.
- </para>
- </listitem>
- </itemizedlist>
- </para>
-</chapter>
-
Deleted: 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-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,172 +0,0 @@
-<?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="Installation_With_ZIP_Download">
- <title>Installation With ZIP Download</title>
-
- <section id="Download">
- <title>Download</title>
-
- <para>
- You can download the zip file from the JBoss Customer Service Portal (CSP), located at <ulink url="https://network.jboss.com">https://network.jboss.com</ulink>.
- </para>
- </section>
-
- <section id="Installation">
- <title>Installation</title>
-
- <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.
-
- <itemizedlist>
- <listitem>
- <para>
- Unzip <literal>jboss-eap-4.2.0-<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). <programlisting>
- [vsr]$ <literal>cd jbeapinstallationdir</literal>
- [vsr]$ <literal>jar -xvf jboss-eap-4.2.0-<replaceable><release></replaceable>.zip</literal></programlisting>
- </para>
- </listitem>
- <listitem>
- <para>
- You are done with the installation! You should now have a directory called <filename>jboss-eap-4.2</filename>. Refer to the Getting Started Guide to understand and explore the Platform Directory Structure.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </section>
-
- <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.
- </para>
-
- <para>
- Accounts for the <literal>jmx-console</literal> and the invokers can be set up by modifying:
- </para>
-
- <programlisting>$JBOSS_HOME/server/$CONFIG/conf/props/jmx-console-users.properties</programlisting>
-
- <para>
- Accounts for <literal>web-console</literal> users can be set up by modifying:
- </para>
-
-<programlisting>
-$JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr.sar/
- web-console.war/WEB-INF/classes/web-console-users.properties
-</programlisting>
-
- <para>
- Where <literal>$JBOSS_HOME</literal> is the install directory and <literal>$CONFIG</literal> is the server configuration being used.
- </para>
-
- <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>.
- </para>
-
- <para>
- To disable authentication for the JMX console, edit the following file and comment out the security-constraint section:
- </para>
-
- <programlisting>server/$CONFIG/deploy/jmx-console.war/WEB-INF/web.xml</programlisting>
-
- <para>
- The following fragment should be commented out:
- </para>
-
- <programlisting><security-constraint>
- <web-resource-collection>
- <web-resource-name>HtmlAdaptor</web-resource-name>
- <description>An example security config that only allows
-users with the
-role JBossAdmin to access the HTML JMX console web application
- </description>
- <url-pattern>/*</url-pattern>
- <http-method>GET</http-method>
- <http-method>POST</http-method>
- </web-resource-collection>
- <auth-constraint>
- <role-name>JBossAdmin</role-name>
- </auth-constraint>
-</security-constraint></programlisting>
-
- <para>
- To disable authentication for the Web console, edit the following file to comment out the security-constraint section:
- </para>
-
-<programlisting>
-server/$CONFIG/deploy/management/console-mgr.sar/web-console.war/WEB-INF/web.xml
-</programlisting>
-
- <para>
- The following fragment should be commented out:
- </para>
-
-<programlisting><security-constraint>
- <web-resource-collection>
- <web-resource-name>HtmlAdaptor</web-resource-name>
- <description>An example security config that only allows
-users with the role JBossAdmin to access the HTML JMX console web application
- </description>
- <url-pattern>/*</url-pattern>
- <http-method>GET</http-method>
- <http-method>POST</http-method>
- </web-resource-collection>
- <auth-constraint>
- <role-name>JBossAdmin</role-name>
- </auth-constraint>
-</security-constraint></programlisting>
-
- <para>
- To disable authentication for the http invoker, <literal>JNDIFactory</literal>, <literal>EJBInvokerServlet</literal>, and <literal>JMXInvokerServlet</literal> need to be removed from the security realm in the file:
- </para>
-
- <programlisting>server/$CONFIG/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml</programlisting>
-
- <para>
- For example, the security-constraint element should look as follows:
- </para>
-
- <programlisting><security-constraint>
- <web-resource-collection>
- <web-resource-name>HttpInvokers</web-resource-name>
- <description>An example security config that only allows
-users with the role HttpInvoker to access the HTTP invoker servlets
- </description>
- <url-pattern>/restricted/*</url-pattern>
- <http-method>GET</http-method>
- <http-method>POST</http-method>
- </web-resource-collection>
- <auth-constraint>
- <role-name>HttpInvoker</role-name>
- </auth-constraint>
- </security-constraint></programlisting>
-
- <para>
- To disable authentication for the JMX invoker, edit the following file to comment out the security interceptor passthrough:
- </para>
-
- <programlisting>server/$CONFIG/deploy/jmx-invoker-service.xml</programlisting>
-
- <para>
- 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:
- </para>
-
- <programlisting><descriptors>
- <interceptors>
- <!-- 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 code="org.jboss.jmx.connector.invoker.SerializableInterceptor"
- policyClass="StripModelMBeanInfoPolicy"/>
- </interceptors>
-</descriptors></programlisting>
-
- </section>
-</chapter>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Introduction.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Introduction.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,53 +0,0 @@
-<?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="Introduction">
- <title>Introduction</title>
- <para>
- &JBEAP; is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. It's easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
- </para>
- <para>
- Because it is Java-based, &JBEAP; is cross-platform, easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
- </para>
- <para>
- Installing &JBEAP; is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist>
- <listitem>
- <para>
- How to install &JBEAP;
- </para>
- </listitem>
- <listitem>
- <para>
- How to Start and Stop your JBoss AS instance
- </para>
- </listitem>
- <listitem>
- <para>
- The Directory structure
- </para>
- </listitem>
- <listitem>
- <para>
- The key services and configuration files
- </para>
- </listitem>
- </itemizedlist>-->
- </para>
- <section id="Introduction-Feedback">
- <title>Feedback</title>
- <para>
- If you spot a typo in the &JBEAP; Installation Guide, or if you have thought of a way to make this manual better, we would love to hear from you! Submit a report in <ulink url="http://bugzilla.redhat.com/bugzilla/">Bugzilla</ulink> against the Product: &JBEAP;, Version: <version>, Component: Installation_Guide. If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, include the section number and some of the surrounding text so we can find it easily.
- </para>
- </section>
-
- <section id="Introduction-Other_Manuals">
- <title>Other Manuals</title>
- <para>
- If you are looking for detailed product information refer to the manuals available online at <ulink url="http://www.redhat.com/docs/manuals/jboss"></ulink>.
- <!--TODO mention about the other guides attached-->
- </para>
- </section>
-
-</chapter>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,75 +0,0 @@
-<?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="Test_your_Installation">
- <title>Test your Installation</title>
- <para>
- After you have installed the JBoss Enterprise Application Platform, 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-eap-4.2/jboss-as
-
- JAVA: /usr/java/jdk1.5.0_11/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.2/jboss-as/bin/run.jar:/u sr/java/jdk1.5.0_11/lib/tools.jar
-
-=====================================================
-
-18:45:49,550 INFO [Server] Starting JBoss (MX MicroKernel)...
-18:45:49,551 INFO [Server] Release ID: JBoss [EAP] 4.2.0.GA_CP01 (build: SVNTag =JBPAPP_4_2_0_GA_CP01
- date=200708310047)
-18:45:49,584 INFO [Server] Home Dir: /home/vrenish/jboss-eap-4.2/jboss-as
-18:45:49,584 INFO [Server] Home URL: file:/home/vrenish/jboss-eap-4.2/jboss-as/
-18:45:49,617 INFO [Server] Patch URL: null
-18:45:49,617 INFO [Server] Server Name: production
-18:45:49,685 INFO [Server] Server Home Dir:
- /home/vrenish/jboss-eap-4.2/jboss-as/server/production
-18:45:49,686 INFO [Server] Server Home URL:
- file:/home/vrenish/jboss-eap-4.2/jboss-as/server/production/
-18:45:49,686 INFO [Server] Server Log Dir:
- /home/vrenish/jboss-eap-4.2/jboss-as/server/production/log
-18:45:49,726 INFO [Server] Server Temp Dir:
- /home/vrenish/jboss-eap-4.2/jboss-as/server/production/tmp
-18:45:49,726 INFO [Server] Root Deployment Filename: jboss-service.xml
-18:45:50,449 INFO [ServerInfo] Java version: 1.5.0_11,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
-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
-
-</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.
- </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>
- Note that on some machines, the name localhost won’t resolve properly and you should use the local loopback address 127.0.0.1 instead.</para></footnote> The contents of your page should look similar to this: <xref linkend="Test_your_Installation-Test_your_Installation" />.
- </para>
- <para>
- <figure id="Test_your_Installation-Test_your_Installation">
- <title>Test your Installation</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/test_install.png" />
- </imageobject>
- </mediaobject>
- </figure>
- </para>
- <para>
- You are now ready to use the JBoss Enterprise Application Platform. Refer to the Getting Started Guide for more information about the platform layout and example applications showcasing JBoss in action.
- </para>
-</chapter>
-
Deleted: projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
===================================================================
--- projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2007-10-02 00:07:11 UTC (rev 65735)
+++ projects/docs/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2007-10-02 00:08:05 UTC (rev 65736)
@@ -1,27 +0,0 @@
-<?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="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.
-<programlisting>
-[vsr]$ java -jar uninstaller.jar
-</programlisting>
- This command will launch the uninstaller program. If you wish to delete the installation directory and all its contents select the check box "Force the deletion of <installation_directory>" and hit the Uninstall button.
- <figure id="Uninstall_JBoss-Uninstaller">
- <title>Uninstaller</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/uninstall.png" />
- </imageobject>
- </mediaobject>
- </figure>
- </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 -->
- </para>
-</chapter>
-
More information about the jboss-cvs-commits
mailing list