[jboss-cvs] JBossAS SVN: r94131 - projects/docs/enterprise/5.0/Installation_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 29 20:10:33 EDT 2009
Author: smcgowan at redhat.com
Date: 2009-09-29 20:10:33 -0400 (Tue, 29 Sep 2009)
New Revision: 94131
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:
Migration Guide updates
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-09-29 22:27:30 UTC (rev 94130)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml 2009-09-30 00:10:33 UTC (rev 94131)
@@ -490,14 +490,15 @@
</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>
+ <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>
@@ -657,8 +658,8 @@
</tbody>
</tgroup>
</table>
- </para> -->
- </section>
+ </para>
+ </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-09-29 22:27:30 UTC (rev 94130)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Migration.xml 2009-09-30 00:10:33 UTC (rev 94131)
@@ -16,14 +16,15 @@
<section id="migration.change.as510">
<title>JBoss Application Server 5.1.0.GA</title>
<para>
- The JBoss Application Server (AS) features the <application>JBoss MicroContainer</application>, which remains compatible with the 4.x-based JMX kernel. The kernel's primary responsibility is to link Plain Old Java Objects (POJOs). The kernel uses unified interceptors, which can be used in conjunction with any container.
+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.
+
</para>
<itemizedlist>
<listitem>
<para>
<emphasis>ProfileService-based Deployment Configuration</emphasis>
</para>
- <para>
+ <para>The definition of the non-kernel deployers and deployment is now defined 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>
@@ -31,7 +32,7 @@
</para>
<itemizedlist>
<listitem>
- <para><emphasis>bootstrap</emphasis> — represents <filename>conf/jboss-service.xml</filename></para>
+ <para><emphasis>bootstrap</emphasis> — representing <filename>conf/jboss-service.xml</filename></para>
</listitem>
<listitem>
<para><emphasis>deployers</emphasis> — the <filename>deployers/</filename> directory</para>
@@ -41,65 +42,28 @@
</listitem>
</itemizedlist>
<para>
- 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.
+ 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>
<para>
- <emphasis>Virtual Deployment Framework</emphasis>
+ <emphasis>Enterprise Java Beans (EJB) 3.0</emphasis>
</para>
<para>
- JBoss AS 5 Virtual Deployment Framework applies aspect-oriented design to the deployment layer. It has been rebased from Java Management Extensions to the POJO MicroContainer.
+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>
<para>
- <emphasis>Classloading</emphasis>
+ <emphasis>Java Enterprise Edition 5 Compliance</emphasis>
</para>
<para>
- The new <literal>ClassLoader</literal> is fully backwards compatible, with <ulink url="http://www.jboss.org/community/docs/DOC-12840">one exception that does not affect common use</ulink>. All classloading configurations from JBoss AS 4.x will still work with the new implementation, and most default settings retain the behaviour of the previous version.
+ 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>
- <para>
- The new <literal>ClassLoader</literal> shares many design and implementation details with the original <literal>UnifiedClassLoader</literal>, but makes the following improvements:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- the classloader no longer depends upon JMX, so it can be used in any environment as a standalone.
- </para>
- </listitem>
- <listitem>
- <para>
- it is much easier to implement your own classloader policy.
- </para>
- </listitem>
- <listitem>
- <para>
- increased control over which classloaders your classloader delegates to.
- </para>
- </listitem>
- <listitem>
- <para>
- increased control over which classes are visible to other classloaders.
- </para>
- </listitem>
- <listitem>
- <para>
- heirarchical repositories have been replaced by domains, and can now extend beyond a single level.
- </para>
- </listitem>
- </itemizedlist>
</listitem>
<listitem>
<para>
- <emphasis>Java EE 5 Compliance</emphasis>
- </para>
- <para>
- Enterprise Application Platform 5.0 is a fully-certified Java EE 5 Implementation. For further certification details, read the <ulink url="http://java.sun.com/javaee/overview/compatibility.jsp">Java EE Compatibility</ulink> page.
- </para>
- </listitem>
- <listitem>
- <para>
<emphasis>Seam 2.2.0.GA</emphasis>
</para>
</listitem>
@@ -113,10 +77,10 @@
</listitem>
<listitem>
<para>
- <emphasis>Enhanced GUI Installer</emphasis>
+ <emphasis>Enhanced Enterprise GUI Installer</emphasis>
</para>
<para>
- The Enterprise Installer retains the familiar Enterprise Application Platform 4.3 interface, and 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.
+ 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.
@@ -127,7 +91,7 @@
<emphasis>Enterprise Application Platform Administration Console</emphasis>
</para>
<para>
- A new administration console has been provided in this release to enable configuration and management of a single Enterprise Application Platform server instance.
+ 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>
@@ -138,22 +102,45 @@
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>
+ <para>
+ <emphasis>Distribution with Red Hat Signed Jars</emphasis>
+ </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>
- The complete technology component matrix and version information for Enterprise Application Platform 5.0 can be found in the Release Notes.
- </para>
- </section>
+ <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 id="migration.config">
- <title>Configuration Information</title>
+ <title>What's Different in Enterprise Application Server 5.0</title>
<para>
- The contents of the Enterprise Application Platform 5.0 distribution are similar to those of version 4.x. This section outlines some of the changes in configuration.
+ 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.
</para>
<section id="migration.config.lib">
- <title>Shared Library Locations</title>
+ <title>Differences in the Distribution Layout</title>
<para>
- Many of the libraries common to various configurations have been moved to a new shared location: <filename>$JBOSS_HOME/common/lib/</filename>. This eliminates the need for multiple copies of the same library in the distribution.
+ The directory structure of <filename>jboss-as</filename> directory is summarized below.
</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>/bin</filename> — starts scripts and <filename>run.jar</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/client</filename> — contains client JARs. <filename>jbossall-client.jar</filename> used to bundle the majority of jboss client libraries. Now they are referenced through the Class-Path manifest entry instead. It requires that you have jbossall-client.jar together with the other client/*.jar libraries so they can be found.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>/common/lib</filename> — shared libraries common to various configurations have been moved to this new shared location. This eliminates the need for multiple copies of the same library in the distribution.
+ </para>
<para>
The location of the common library directory is controlled with the following properties:
</para>
@@ -177,33 +164,15 @@
</programlisting>
<para>
The <filename>library</filename> directory of the individual directory remains in place, although in some cases (as in <filename>$JBOSS_HOME/server/default/lib/</filename>) it is an empty directory.
- </para>
- <para>
- The directory structure of <filename>jboss-as</filename> resembles that of Enterprise Application Platform 4.x, with some notable differences:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <filename>/bin</filename> — starts scripts and <filename>run.jar</filename>
</para>
</listitem>
<listitem>
<para>
- <filename>/client</filename> — contains client JARs. <filename>jbossall-client.jar</filename> now references the other client JARs, rather than including duplicates.
+ <filename>/docs</filename> — contains schemas, document type declarations, examples and licenses. Most deployment descriptors now use XML Schema Definitions (XSDs). One exception is <literal>jboss-app</literal>, which uses <filename>jboss-app_5_0.dtd</filename>. JBoss Web uses <filename>jboss-web_5_1.xsd</filename>. For Enterprise JavaBeans 3.0 deployments, <filename>jboss_5_1.xsd</filename> is the recommended schema. Enterprise JavaBeans 2.0 deployments must use <filename>jboss_x_x.dtd</filename>.
</para>
</listitem>
<listitem>
<para>
- <filename>/common/lib</filename> — contains shared libraries.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>/docs</filename> — contains schemas, document type declarations, examples and licences.
- </para>
- </listitem>
- <listitem>
- <para>
<filename>/lib</filename> — contains the core bootstrap JARs. These have been changed slightly to accomodate the Microcontainer and the division of <filename>jboss-common</filename>.
</para>
</listitem>
@@ -486,7 +455,7 @@
<section id="migration.config.new">
<title>Standard and Web Configuration</title>
<para>
- Enterprise Application Platform 5.0 introduces two new configuration types: <literal>standard</literal> and <literal>web</literal>.
+ Two additional server configurations are distributed with Enterprise Application Platform 5.0: <literal>standard</literal> and <literal>web</literal>.
</para>
<para>
<literal>standard</literal> configuration is certified for Java EE 5 compliance. This configuration enables both call-by-value and deployment isolation by default. Support for RMI-IIOP (Remote Method Invocation over the Internet Inter-Orb Protocol) and Java UDDI (Universal Description, Discovery and Integration), as in the <literal>all</literal> configuration type, is also enabled.
@@ -543,24 +512,18 @@
</listitem>
</itemizedlist>
<para>
- The <literal>web</literal> configuration provides the services required for web application deployment, and includes a subset of Java EE technology. This profile does not include JBoss Transaction JTS or XTS, Enterprise Java Bean 1.x or 2.x capabilities, JBoss Messaging, JCA, or JBoss IIOP.
+ The <literal>web</literal> configuration is a new lightweight configuration created around JBoss Web and provides the services required for web application deployment and only a subset of Java EE technologies. This profile does not include JBoss Transaction JTS or XTS, Enterprise Java Bean 1.x or 2.x capabilities, JBoss Messaging, JCA, or JBoss IIOP.
</para>
</section>
<section id="migration.config.as">
- <title>Changes to Application Server Configuration</title>
+ <title>Differences in Application Server Configuration Files</title>
<section id="migration.config.as-gen">
<title>General</title>
<itemizedlist>
<listitem>
<para>
- Distributions are now signed. This lets you verify that your product was distributed by JBoss from Red Hat, and ensures that users are made aware of any packages that do not come from JBoss by Red Hat.
+ A reminder that the <filename>rpm</filename> and <filename>zip</filename> distributions of the Enterprise Application Platform are shipped with authentication enabled for the JMX Console, Web Console, JMX Invoker, Administration Console, HTTP Invoker and Profile Service. No user accounts are active by default to assist in preventing default user and password-based attacks.
</para>
- </listitem>
- <!--Not a change; more of a reminder:
- <listitem>
- <para>
- By default, the <filename>rpm</filename> and <filename>zip</filename> distributions of the Enterprise Application Platform are shipped with authentication enabled for the JMX Console, Web Console, JMX Invoker, Administration Console, HTTP Invoker and Profile Service. No user accounts are active by default, which assists in preventing default user and password-based attacks.
- </para>
</listitem>-->
<listitem>
<para>
@@ -718,7 +681,7 @@
</listitem>
<listitem>
<para>
- The new <varname>jboss.server.log.threshold</varname> system property can be used to control the <filename>log/server/log</filename> threshold. The default value is <literal>INFO</literal>.
+ The new <varname>jboss.server.log.threshold</varname> system property can be used to control the <filename>log/server.log</filename> threshold. The default value is <literal>INFO</literal>.
</para>
</listitem>
<listitem>
@@ -776,7 +739,7 @@
<section id="migration.admin">
<title>Administration</title>
<para>
- The first release of the Enterprise Application Platform Administration Console (<literal>admin-console</literal>) provided the following administrative features:
+ The first release of the Enterprise Application Platform Administration Console (<literal>admin-console</literal>) provides the following administrative features:
</para>
<itemizedlist>
<listitem>
@@ -883,24 +846,22 @@
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>
- For a quick reference guide to the use of the Enterprise Application Platform 5.0 Administraton Console, see the <ulink url="http://www.jboss.org/community/docs/DOC-13711">Administration Console QuickStart Guide</ulink>.
+ <!-- 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.
</para>
</section>
<section id="migration.apps">
<title>Applications</title>
<para>
- Enterprise Application Platform 5.0 is a fully-compliant implementation of the Java Enterprise Edition 5 (Java EE 5) Platform Specification. Java EE 5 aims to define the metadata associations of the Java language, which can be used to annotate application code and eliminate the need for deployment descriptors wherever possible. This is known as <emphasis>configuration by exception</emphasis>.
+ As noted earlier, Enterprise Application Platform 5.0 is a fully-compliant implementation of the Java Enterprise Edition 5 (Java EE 5) Platform Specification. Java EE 5 defines the metadata associations of the Java language which can be used to annotate application code and eliminate the need for deployment descriptors wherever possible. Default behavior is also defined with the ability to override as needed. This is known as <emphasis>configuration by exception</emphasis>.
</para>
<para>
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>
- Most deployment descriptors now use XML Schema Definitions (XSDs). One exception is <literal>jboss-app</literal>, which uses <filename>jboss-app_5_0.dtd</filename>. JBoss Web uses <filename>jboss-web_5_1.xsd</filename>. For Enterprise JavaBeans 3.0 deployments, <filename>jboss_5_1.xsd</filename> is the recommended schema. Enterprise JavaBeans 2.0 deployments must use <filename>jboss_x_x.dtd</filename>.
+ 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.
</para>
<para>
- Java EE 5 applications can take advantage of the simplified packaging rules available in Enterprise Application Platform 5.0. Enterprise Archives (EARs) no longer require an <filename>application.xml</filename> file. 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.
</para>
<para>
@@ -917,19 +878,42 @@
<para>
If an enterprise archive contains only an application client and refers to EJBs, you must also add the <literal></ignore-dependency></literal> element to the <literal>ejb-ref</literal> or <literal>ejb-local-ref</literal> definitions in the <filename>jboss-client.xml</filename> deployment descriptor. This informs the deployer to deploy the archive without resolving the referenced dependencies.
</para>
- <section id="migration.app.scoping">
- <title>EAR Scoping</title>
- <para>
- You can control how class isolation between deployments behave with the <varname>isolated</varname> property in <filename>deployers/ear-deployer-jboss-beans.xml</filename>, as follows:
- </para>
- <programlisting role="XML"><!-- A flag indicating if ear deployments should have their own scoped class loader to isolate theirclasses from other deployments. -->
- <property name="isolated">false</property>
- </programlisting>
- </section>
<section id="migration.app.loader">
<title>Classloading</title>
- <para>
- <literal>useJBossWebClassLoader="true"</literal> is not used in Enterprise Application Platform 5.0. All WAR classloaders in Enterprise Application Platform 5.0 are JBoss <literal>ClassLoader</literal>s, so the <literal>WarDeployer</literal> no longer handles the configuration details for web applications.
+ <para>
+ The new <literal>ClassLoader</literal> is fully backwards compatible, with <ulink url="http://www.jboss.org/community/docs/DOC-12840">one exception that does not affect common use</ulink>. All classloading configurations from JBoss AS 4.x will still work with the new implementation, and most default settings retain the behaviour of the previous version.
+ </para>
+ <para>
+ The new <literal>ClassLoader</literal> shares many design and implementation details with the original <literal>UnifiedClassLoader</literal>, but makes the following improvements:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the classloader no longer depends upon JMX, so it can be used in any environment as a standalone.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ it is much easier to implement your own classloader policy.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ increased control over which classloaders your classloader delegates to.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ increased control over which classes are visible to other classloaders.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ heirarchical repositories have been replaced by domains, and can now extend beyond a single level.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>One thing to note. <literal>useJBossWebClassLoader="true"</literal> is not used in Enterprise Application Platform 5.0. All WAR classloaders in Enterprise Application Platform 5.0 are JBoss <literal>ClassLoader</literal>s, so the <literal>WarDeployer</literal> no longer handles the configuration details for web applications.
</para>
<para>
There are several methods available to change the classloading configuration of a WAR:
@@ -958,5 +942,14 @@
This lets you define how the WAR's classloader is constructed. In this case, the WAR's classloader has been placed in the <literal>DefaultDomain</literal>, which is shared with all other applications that do not define their own domain. <varname>import-all</varname> is enabled, which means the classloader will look at all other classes exported by other applications. <varname>export-all</varname> is set to expose all classes in our application to other classes.
</para>
</section>
+ <section id="migration.app.scoping">
+ <title>EAR Scoping</title>
+ <para>
+ You can control how class isolation between deployments behave with the <varname>isolated</varname> property in <filename>deployers/ear-deployer-jboss-beans.xml</filename>, as follows:
+ </para>
+ <programlisting role="XML"><!-- A flag indicating if ear deployments should have their own scoped class loader to isolate theirclasses from other deployments. -->
+ <property name="isolated">false</property>
+ </programlisting>
+ </section>
</section>
</chapter>
More information about the jboss-cvs-commits
mailing list