[jboss-cvs] JBossAS SVN: r94929 - projects/docs/enterprise/5.0/Installation_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 15 03:37:40 EDT 2009
Author: laubai
Date: 2009-10-15 03:37:40 -0400 (Thu, 15 Oct 2009)
New Revision: 94929
Modified:
projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml
Log:
Corrected section placement in Migration.xml
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml 2009-10-15 07:26:40 UTC (rev 94928)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml 2009-10-15 07:37:40 UTC (rev 94929)
@@ -61,8 +61,7 @@
</para>
</listitem>
</itemizedlist> -->
- <formalpara>
-<formalpara>
+ <formalpara>
<title>Supported Operating Systems</title>
<para>
This release of JBoss Enterprise Application Platform is certified for the following Operating Systems:
@@ -81,17 +80,17 @@
</listitem>
<listitem>
<para>
- Solaris™ 9 (32-bit systems)
+ Solaris 9 (32-bit systems)
</para>
</listitem>
<listitem>
<para>
- Solaris™ 10 (32-bit systems and 64-bit systems)
+ Solaris 10 (32-bit systems and 64-bit systems)
</para>
</listitem>
<listitem>
<para>
- Microsoft® Windows Server® 2008 R2 (32-bit systems and 64-bit systems)
+ Microsoft Windows Server 2008 R2 (32-bit systems and 64-bit systems)
</para>
</listitem>
<!-- <listitem>
@@ -101,12 +100,12 @@
</listitem> -->
<listitem>
<para>
- Microsoft® Windows® XP (32-bit systems and 64-bit systems)
+ Microsoft Windows XP (32-bit systems and 64-bit systems)
</para>
</listitem>
<listitem>
<para>
- Microsoft® Windows Server® 2003 (32-bit systems and 64-bit systems)
+ Microsoft Windows Server 2003 (32-bit systems and 64-bit systems)
</para>
</listitem>
</itemizedlist>
@@ -343,6 +342,7 @@
<title>Configuring Your Java Environment</title>
<para>
Enterprise Application Platform 5 requires Java SE 6. You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install JBoss Enterprise Application Platform. You can install the 32-bit or 64-bit JVM as per your requirements.
+ </para>
<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>
@@ -366,349 +366,7 @@
</para>
</listitem>
</itemizedlist>
-<!--
- <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_6.0_using_RHN">
- <title>Installing and Configuring 32-bit Sun JDK 6.0 using RHN</title>
- <listitem>
- <para>
- Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplementary channel for your Linux variant and architecture. Depending on the architecture, the channel names are:
- </para>
- <para>
- rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5
- </para>
- <para>
- <command moreinfo="none">java-1.6.0-bea</command>, <command moreinfo="none">java-1.6.0-openjdk</command> <command moreinfo="none">java-1.6.0-ibm</command> and
- <command moreinfo="none">java-1.6.0-sun</command> SDKs are available from
- these channels. Make sure you also install the
- <command moreinfo="none">-devel</command> subpackages.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0</command> (setting <command moreinfo="none">java_sdk_1.6.0</command> is optional).
- </para>
-
- <para>
- This is only needed if you want to use the SysV service script
- and/or want this installed SDK to be the default java and javac
- in the system. This choice can often be overridden by setting
- the <command moreinfo="none">JAVA_HOME</command> environment variable.
- </para>
-
- <para>
- The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want.
- </para>
-
- <para>
- As root, issue the following command:
- </para>
- <screen>
- <command moreinfo="none">/usr/sbin/alternatives config java</command>
- </screen>
- <para>
- and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted.
- </para>
-
- <para>
- Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0.</command> We recommend that all point to the same manufacturer and version.
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_6.0_on_a_generic_Linux_platform">
- <title>Installing and Configuring 32-bit Sun JDK 6.0 on a generic Linux platform</title>
- <listitem>
- <para>
- Download the Sun JDK 6.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp"></ulink>. Choose "JDK 6.0 Update <x>" (where x is the latest update number) for download and then select "RPM in self-extracting" file for Linux<footnote><para>Make sure you choose the appropriate file for your platform.</para></footnote>. Read the instructions on Sun's website for installing the JDK.
- </para>
- </listitem>
- <listitem>
- <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.6.0_15 is the JDK installation directory.
-export JAVA_HOME=/usr/java/jdk1.6.0_15
-export PATH=$PATH:$JAVA_HOME/bin
-</programlisting>
- Set this variable for the user account doing the installation and also for the user account that will run the server.
- </para>
- </listitem>
- <listitem>
- <para>
- If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.6 installation as the default <literal>java</literal> and <literal>javac</literal>. You can do this using the alternatives system. The alternatives system allows different versions of Java, from different sources to co-exist on your system.
- </para>
- <itemizedlist>
- <title>Select alternatives for java, javac and java_sdk_1.6.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.6.0-sun/bin/java
-Enter to keep the current selection[+], or type selection number:
-</programlisting>
- Make sure the Sun version [<literal>jre-1.6.0-sun</literal> in this case] is selected (marked with a '+' in the output), or select it by entering its number as prompted.
- </para>
- </listitem>
- <listitem>
- <para>
- Repeat the same for javac and java_sdk_1.6.0. <programlisting>
-[root at vsr ~]$ /usr/sbin/alternatives --config javac
-There are 1 programs which provide 'javac'.
- Selection Command
------------------------------------------------
-*+ 1 /usr/lib/jvm/java-1.6.0-sun/bin/javac
-Enter to keep the current selection[+], or type selection number:
-</programlisting>
-<programlisting>
-[root at vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.6.0
-There are 1 programs which provide 'java_sdk_1.6.0'.
- Selection Command
------------------------------------------------
-*+ 1 /usr/lib/jvm/java-1.6.0-sun
-Enter to keep the current selection[+], or type selection number:
-</programlisting>
- You should verify that java, javac and java_sdk_1.6.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.6.0_15"
-Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0_15)
-Java HotSpot(TM) Client VM (build 1.6.0_15, mixed mode, sharing)
-</programlisting>
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_6.0_on_Microsoft_Windows">
- <title>Installing and Configuring 32-bit Sun JDK 6.0 on Microsoft Windows</title>
- <listitem>
- <para>
- Download the Sun JDK 6.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp"></ulink>. Choose "JDK 6.0 Update <x>" (where x is the latest update number) for download and then select your Windows Platform options to perform the installation.
- </para>
- </listitem>
- <listitem>
- <para>
- Create a System environment variable called <literal>JAVA_HOME</literal> that points to the JDK installation directory, for example: <literal>C:\Java\jdk1.6.0_11\</literal>. In order to run java from the command line add the <literal>jre\bin</literal> directory to your path, for example: <literal>C:\Java\jdk1.6.0_11\jre\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
- </para>
- <warning>
- <para>
- When installing Java and configurating PATH environment variables on Windows, make sure that the directory paths used do not contain any spaces. If an environment variable references a path with a space it may generate a <exceptionname>ClassNotFoundException</exceptionname> when starting the server.
- </para>
- </warning>
- </listitem>
- </itemizedlist>
- <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_64_bit_Sun_JDK_6.0_on_Solaris">
- <title>Installing and Configuring 64-bit Sun JDK 6.0 on Solaris</title>
- <listitem>
- <para>
- Download the Sun JDK 6.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp"></ulink>. Choose "JDK 6.0 Update <x>" (where x is the latest update number) for download and then select your Solaris options to perform the installation.
- </para>
- </listitem>
- <listitem>
- <para>
- Solarius uses a 32-bit JVM by default. In order to use a 64-bit JVM the <code>-d64</code> parameter must be added to <literal>JAVA_OPTS</literal>.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </section>
-
- </section>
-
- <section id="Getting_Started-Components_of_JBoss_Enterprise_Application_Platform">
- <title>Components of JBoss Enterprise Application Platform</title>
-
- <para>For current information on the revision level of included components please refer to <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html</ulink>.
- </para>
-
- <para>
- 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> -->
-
+ </section>
+ </section>
</chapter>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml 2009-10-15 07:26:40 UTC (rev 94928)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml 2009-10-15 07:37:40 UTC (rev 94929)
@@ -16,15 +16,12 @@
<section id="migration.change.as510">
<title>JBoss Application Server 5.1.0.GA</title>
<para>
-JBoss Application Server 5 is the next generation of the JBoss Application Server build on top of a new kernel architecture, the <application>JBoss Microcontainer</application>. The JBoss Microcontainer is a lightweight container for managing Plain Old Java Objects (POJOs), their deployment, configuration and lifecycle. While remaining compatible with the 4.x-based JMX kernel, the Microcontainer integrates nicely with the JBoss framework for Aspect Oriented Programming, JBoss AOP. Support for JMX in JBoss 5 remains strong and MBean services written against the old Microkernel should work as expected. Further, it lays the groundwork for JavaEE 6 profiles oriented configurations and JBoss AS embedded that will allow for fine grained selection of services for both unit testing and embedded scenarios.
+ JBoss Application Server 5 is the next generation of the JBoss Application Server build on top of a new kernel architecture, the <application>JBoss Microcontainer</application>. The JBoss Microcontainer is a lightweight container for managing the deployment, configuration and lifecycle of Plain Old Java Objects (POJOs). While remaining compatible with the 4.x-based JMX kernel, the Microcontainer integrates nicely with the JBoss framework for Aspect Oriented Programming, JBoss AOP. Support for JMX in JBoss 5 remains strong and MBean services written against the old Microkernel should work as expected. Further, it lays the groundwork for Java EE 6 profile-oriented configurations and embedded JBoss AS, which will allow for fine grained selection of services for both unit testing and embedded scenarios.
</para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis>ProfileService-based Deployment Configuration</emphasis>
- </para>
- <para>The definition of the non-kernel deployers and deployment is now defined a Profile obtained from the ProfileService.
+ <section id="migration.change.profile">
+ <title>ProfileService-based Deployment Configuration</title>
+ <para>The definition of the non-kernel deployers and deployment is now defined in a Profile obtained from the ProfileService.
The <application>ProfileService</application> replaces JBoss AS 4.x <emphasis>server configuration</emphasis>. In JBoss AS 4.x, a server configuration was a collection of services and applications loaded from the <filename>deploy</filename> directory by the deployment scanner service. Enterprise Application Platform 5.0 uses more active profiles, which may depend on other <emphasis>sub-profiles</emphasis>.
</para>
<para>
@@ -45,81 +42,74 @@
A profile generally represents a named collection of deployments on a server. A profile can also apply certain behaviours to the deployments that it manages. Some profiles, such as the <literal>application</literal> profile, provide hot-deployment checks and allow remote distribution of deployed applications via the <literal>DeploymentManager</literal>. Other profiles can provide a farming service to distribute deployments over a cluster. The ProfileService also provides the ManagementView for ManagedDeployments/ManagedObjects used by the Enterprise Application Administration Console (admin-console).
</para>
- </listitem>
- <listitem>
+ </section>
+ </section>
+ <section id="migration.change.ejb3">
+ <title>Enterprise Java Beans (EJB) 3.0</title>
<para>
- <emphasis>Enterprise Java Beans (EJB) 3.0</emphasis>
- </para>
- <para>
JBoss EJB 3.0, an implementation of the latest revision of the EJB specification, is a deep overhaul and simplification of earlier versions of the EJB specification achieving its' goals to simplify development, facilitate a test driven approach, and focus more on writing POJOs rather than coding against complex EJB APIs.
</para>
- </listitem>
- <listitem>
+ </section>
+ <section id="migration.change.jee5">
+ <title>Java Enterprise Edition 5 Compliance</title>
<para>
- <emphasis>Java Enterprise Edition 5 Compliance</emphasis>
- </para>
- <para>
Enterprise Application Platform 5.0 is a fully-certified Java EE 5 implementation using the microcontainer to integrate enterprise services together with a Servlet/JSP container, EJB container, deployers and management utilities in order providing a standard Java EE environment with the flexibility to simply deploy additional services on top of Java EE to for the functionality you need. For further certification details, read the <ulink url="http://java.sun.com/javaee/overview/compatibility.jsp">Java EE Compatibility</ulink> page.
</para>
- </listitem>
- <listitem>
+ </section>
+
+ <!--<section id="migration.change.seam2">
+ <title>Seam 2.2.0.GA</title>
+ <para></para>
+ </section>-->
+
+ <section id="migration.change.resteasy">
+ <title>RESTEasy 1.1.GA</title>
<para>
- <emphasis>Seam 2.2.0.GA</emphasis>
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis>RESTEasy 1.1.GA</emphasis>
- </para>
- <para>
RESTEasy provides several frameworks to help you build RESTful Web Services and RESTful Java applications. It is a fully-certified, fully-portable implementation of the <ulink url="http://jsr311.dev.java.net/">JAX-RS</ulink> specification, which defines a Java API for RESTful Web Services over the Hypertext Transfer Protocol (HTTP).
</para>
- </listitem>
- <listitem>
+ </section>
+
+ <section id="migration.change.gui">
+ <title>Enhanced Enterprise GUI Installer</title>
<para>
- <emphasis>Enhanced Enterprise GUI Installer</emphasis>
- </para>
- <para>
The Enterprise Installer retains the familiar Enterprise Application Platform 4.3 interface but includes enhancements to provide you with a complete Enterprise Application Platform 5.0 installation. This is fully-localized and provides you with secure JMX, Web and Administration consoles.
</para>
<para>
The new Enterprise Installer will also present users with the opportunity to install the optional Native package, which includes <application>JBoss Native</application> and <application>mod_jk</application>. The Native package helps users who wish to use Tomcat or JBoss Web with the HTTP daemon.
</para>
- </listitem>
- <listitem>
+ </section>
+
+ <section id="migration.change.admin">
+ <title>Enterprise Application Platform Administration Console</title>
<para>
- <emphasis>Enterprise Application Platform Administration Console</emphasis>
- </para>
- <para>
A new administration console is being introduced in this Enterprise Application Platform release. The admin-console enables configuration and management of a single Enterprise Application Platform server instance. See Section 2.3 for more information about this new management console.
</para>
- </listitem>
- <listitem>
+ </section>
+
+ <section id="migration.change.jts">
+ <title>JBoss Transactions includes Java Transaction Service</title>
<para>
- <emphasis>JBoss Transactions includes Java Transaction Service</emphasis>
- </para>
- <para>
JBoss Transactions now includes the Java Transaction Service and the XML Transaction Service. The Java Transaction Service handles distributed, interoperable transactions between Enterprise JavaBean containers. The XML Transaction service handles transactions for Web Services.
</para>
- </listitem>
- <listitem>
+ </section>
+
+ <section id="migration.change.jars">
+ <title>Distribution with Red Hat Signed Jars</title>
<para>
- <emphasis>Distribution with Red Hat Signed Jars</emphasis>
+ With Red Hat signed jars, you can be confident the contents of your product distribution is actually what was shipped by Red Hat.
</para>
- <para>
- With Red Hat signed jars, you can be confident the contents of your product distribution is actually what was shipped by Red Hat.
- </para>
- </listitem>
-
- </itemizedlist>
- <para>For the complete technology matrix and information on the revision level of included components please refer to <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html</ulink>.
- </para>
-
+
+ <para>
+ For the complete technology matrix and information on the revision level of included components please refer to <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html</ulink>.
+ </para>
+ </section>
</section>
+
+
<section id="migration.config">
<title>What's Different in Enterprise Application Server 5.0</title>
<para>
- The distribution layout and configuration information in the Enterprise Application Platform 5.0 distribution are similar to the EAP 4.x series with some notable differences. This section highlights the differences at a glance.
+ The distribution layout and configuration information in the Enterprise Application Platform 5.0 distribution are similar to the Enterprise Application Platform 4.x series with some notable differences. This section highlights the differences at a glance.
</para>
<section id="migration.config.lib">
<title>Differences in the Distribution Layout</title>
@@ -737,7 +727,7 @@
</section>
</section>
<section id="migration.admin">
- <title>Administration</title>
+ <title>Administration Console</title>
<para>
The first release of the Enterprise Application Platform Administration Console (<literal>admin-console</literal>) provides the following administrative features:
</para>
@@ -846,8 +836,10 @@
When the server has been started, you can use the <literal>admin-console</literal> to perform administrative tasks for your application server. To use the <literal>admin-console</literal>, point your browser to <literal>http://${hostname}:8080/admin-console</literal>.
</para>
<para>
- <!-- NOTE TO LAURA: - is there a document on EAP 5 Admin Console to link to?? -->
- Complete reference on use of the Enterprise Application Platform 5.0 Administraton Console, see the link TBD.
+ <!--The Quick Start Guide for the Enterprise Application Platform 5.0 Administration Console is available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html</ulink>.-->
+
+ <!-- NOTE TO LAURA: - is there a document on Enterprise Application Platform 5 Admin Console to link to?? -->
+ <!--Complete reference on use of the Enterprise Application Platform 5.0 Administraton Console, see the link TBD.-->
</para>
</section>
<section id="migration.apps">
@@ -859,7 +851,7 @@
Portable Java EE applications running on Enterprise Application Platform 4.x can be deployed to Enterprise Application Platform 5.0 without any changes. However, runtime-specific deployment information may be required when migrating from another vendor's application server to Enterprise Application Platform 5.0.
</para>
<para>
- EAP 5.0 users can take advantage of the simplified packaging and deployment rules defined in the Java EE 5 Platform Specification such as no longer requiring an <filename>application.xml</filename> file in Enterprise Archives (EARs). Additionally, a default library directory (<filename>lib</filename>) in the root directory of an EAR makes the JARs available to all components packaged within the EAR. If an <filename>application.xml</filename> file is included, the <literal>library-directory</literal> element can be used to specify the location of the <filename>lib</filename> directory.
+ Enterprise Application Platform 5.0 users can take advantage of the simplified packaging and deployment rules defined in the Java EE 5 Platform Specification such as no longer requiring an <filename>application.xml</filename> file in Enterprise Archives (EARs). Additionally, a default library directory (<filename>lib</filename>) in the root directory of an EAR makes the JARs available to all components packaged within the EAR. If an <filename>application.xml</filename> file is included, the <literal>library-directory</literal> element can be used to specify the location of the <filename>lib</filename> directory.
</para>
<para>
Enterprise Application Platform 5.0 also introduces a new deployable unit: the <emphasis>MCBeans archive</emphasis>, after JBoss Microcontainer, which typically takes the <filename>.beans</filename> or <filename>.deployer</filename> suffix. MCBeans archives package a POJO deployment in a JAR file with a <filename>META-INF/jboss-beans.xml</filename> descriptor. This format is common in Enterprise Application Platform deployers.
@@ -952,5 +944,5 @@
</programlisting>
</section>
</section>
-</section>
</chapter>
+
More information about the jboss-cvs-commits
mailing list