[jboss-cvs] JBossAS SVN: r91331 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jul 16 00:43:52 EDT 2009
Author: irooskov at redhat.com
Date: 2009-07-16 00:43:51 -0400 (Thu, 16 Jul 2009)
New Revision: 91331
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml
Log:
editing for EAP 5 release
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2009-07-16 04:34:55 UTC (rev 91330)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2009-07-16 04:43:51 UTC (rev 91331)
@@ -6,7 +6,7 @@
<title>JBoss Enterprise Application Platform 5 architecture</title>
<para>
<indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>architecture</secondary></indexterm>
- The following diagram illustrates an overview of the JBoss.org community projects including the JBoss Appplication Server and its components.
+ The following diagram illustrates an overview of the JBoss Enterprise Application Platform and its components.
<inlinemediaobject>
<imageobject>
<imagedata fileref="images/projects_communitygraph.png"/>
@@ -15,7 +15,7 @@
</para>
<para>
- The directory structure of JBoss 5 resembles that of the 4.x series with some notable differences:
+ The directory structure of JBoss Enterprise Application Platform 5 resembles that of the 4.x series with some notable differences:
<screen>
<![CDATA[-<JBOSS_HOME>/ - the path to your JBoss Enterprise Application Platform installation.
|-- bin - contains start scripts and run.jar
@@ -155,20 +155,20 @@
<sect1 id="Architecture_Server_Bootstrap">
<title>The JBoss Enterprise Application Platform Bootstrap</title>
<indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>bootstrap</secondary></indexterm>
- <para>The JBoss Enterprise Application Platform 5 bootstrap is similar to the JBoss Enterprise Application Platform 4.x and earlier versions in that the org.jboss.Main entry point loads an org.jboss.system.server.Server implementation. In JBoss Enterprise Application Platform 4.x this was a JMX based microkernel. In JBoss Enterprise Application Platform 5 this is a JBoss Microcontainer.
+ <para>The JBoss Enterprise Application Platform 5 bootstrap is similar to the JBoss Enterprise Application Platform 4.x versions in that the org.jboss.Main entry point loads an org.jboss.system.server.Server implementation. In JBoss Enterprise Application Platform 4.x this was a JMX based microkernel. In JBoss Enterprise Application Platform 5 this is a JBoss Microcontainer.
</para>
<indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>Server interface implementation</secondary></indexterm>
- <para>The default JBoss Enterprise Application Platform 5 org.jboss.system.server.Server implementation is org.jboss.bootstrap.microcontainer.ServerImpl. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in {jboss.server.config.url}/bootstrap.xml descriptors using a BasicXMLDeployer. In addition, the ServerImpl registers install callbacks for any beans that implement the org.jboss.bootstrap.spi.Bootstrap interface. The bootstrap/profile*.xml configurations include a ProfileServiceBootstrap bean that implements the Bootstrap interface.
+ <para>The default JBoss Enterprise Application Platform 5 <classname>org.jboss.system.server.Server implementation</classname> is <classname>org.jboss.bootstrap.microcontainer.ServerImpl</classname>. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in <filename>{jboss.server.config.url}/bootstrap.xml</filename> descriptors using a <classname>BasicXMLDeployer</classname>. In addition, the <classname>ServerImpl</classname> registers install callbacks for any beans that implement the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface. The <filename>bootstrap/profile*.xml</filename> configurations include a <classname>ProfileServiceBootstrap</classname> bean that implements the Bootstrap interface.
</para>
<indexterm><primary>ProfileService</primary><secondary>bootstrap</secondary></indexterm>
- <para>The org.jboss.system.server.profileservice.ProfileServiceBootstrap is an implementation of the org.jboss.bootstrap.spi.Bootstrap interface that loads the deployments associated with the current profile. The {profile-name} is the name of the profile being loaded and corresponds to the server -c command line argument. The default {profile-name} is "default". The deployers, deploy</para>
+ <para>The <classname>org.jboss.system.server.profileservice.ProfileServiceBootstrap</classname> is an implementation of the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface that loads the deployments associated with the current profile. The <emphasis>{profile-name}</emphasis> is the name of the profile being loaded and corresponds to the <code>server -c</code> command line argument. The default <emphasis>{profile-name}</emphasis> is <emphasis>default</emphasis>. The deployers, deploy</para>
</sect1>
<sect1 id="Architecture_Hotdeployment">
<title>Hot Deployment</title>
<indexterm><primary>Hot deployment</primary><secondary>implementation</secondary></indexterm>
- <para>Hot deployment in JBoss Enterprise Application Platform 5 is controlled by the Profile implementations associated with the ProfileService. The HDScanner bean deployed via the deploy/hdscanner-jboss-beans.xml MC deployment, queries the profile service for changes in application directory contents and redeploys updated content, undeploys removed content, and adds new deployment content to the current profile via the ProfileService. </para>
+ <para>Hot deployment in JBoss Enterprise Application Platform 5 is controlled by the <classname>Profile</classname> implementations associated with the <classname>ProfileService</classname>. The <classname>HDScanner</classname> bean deployed via the <filename>deploy/hdscanner-jboss-beans.xml</filename> MC deployment, queries the profile service for changes in application directory contents and redeploys updated content, undeploys removed content, and adds new deployment content to the current profile via the <classname>ProfileService</classname>. </para>
<indexterm><primary>Hot deployment</primary><secondary>disabling</secondary></indexterm>
- <para>Disabling hot deployment simply entails removing the hdscanner-jboss-beans.xml deployment.</para>
+ <para>Disabling hot deployment is achieved by removing the <filename>hdscanner-jboss-beans.xml</filename> file from deployment.</para>
</sect1>
</chapter>
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2009-07-16 04:34:55 UTC (rev 91330)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2009-07-16 04:43:51 UTC (rev 91331)
@@ -5,12 +5,12 @@
<chapter id="Deployment">
<title>Deployment</title>
- <para>Deploying applications on JBoss Enterprise Application Platform is very easy. You just need to copy the application into the JBOSS_HOME/server/default/deploy directory. You can replace default with different server profiles such as all or minimal. We will cover those later in this chapter. JBoss Enterprise Application Platform constantly scans the deploy directory to pick up new applications or any changes to existing applications. So, you can "hot deploy" application on the fly while JBoss Enterprise Application Platform is still running.</para>
+ <para>Deploying applications on JBoss Enterprise Application Platform is achieved by copy the application into the <filename>JBOSS_HOME/server/default/deploy</filename> directory. You can replace <emphasis>default</emphasis> with different server profiles such as <emphasis>all</emphasis> or <emphasis>minimal</emphasis>. We will cover those later in this chapter. The JBoss Enterprise Application Platform constantly scans the deploy directory to pick up new applications or any changes to existing applications. This enables the <emphasis>hot deployment</emphasis> of applications on the fly, while JBoss Enterprise Application Platform is still running.</para>
<section id="Deployable_Application_Types">
<title>Deployable Application Types</title>
- <para>With JBoss Enterprise Application Platform 4.x and earlier, a deployer existed to handle a specified deployment type and that was the only deployer that would process the deployment. In JBoss Enterprise Application Platform 5, multiple deployers typically transform the metadata associated with a deployment until its processed by a deployer that creates a runtime component from the metadata. The old deployment type notion based on suffix is a weaker notion. Instead, the deployment has to contain a descriptor that causes the component metadata to be added to the deployment. The types of deployments for which deployers exists by default in Enterprise Application Platform include:</para>
+ <para>With JBoss Enterprise Application Platform 4.x, a deployer existed to handle a specified deployment type and that was the only deployer that would process the deployment. In JBoss Enterprise Application Platform 5, multiple deployers transform the metadata associated with a deployment until its processed by a deployer that creates a runtime component from the metadata. Deployment has to contain a descriptor that causes the component metadata to be added to the deployment. The types of deployments for which deployers exists by default in the JBoss Enterprise Application Platform include:</para>
<itemizedlist>
<listitem>
@@ -25,7 +25,7 @@
<listitem>
<indexterm><primary>JBoss Microcontainer</primary><secondary>beans deployment type</secondary></indexterm>
- <para>The JBoss Microcontainer (MC) beans archive (typical suffixes include, .beans, .deployer) packages a POJO deployment in a JAR file with a META-INF/jboss-beans.xml descriptor. This format is commonly used by the JBoss Enterprise Application Platform component deployers.</para></listitem>
+ <para>The JBoss Microcontainer (MC) beans archive (typical suffixes include, .beans, .deployer) packages a POJO deployment in a JAR file with a <filename>META-INF/jboss-beans.xml</filename> descriptor. This format is commonly used by the JBoss Enterprise Application Platform component deployers.</para></listitem>
<listitem>
<indexterm><primary>SAR</primary><see>Service Archive</see></indexterm>
@@ -34,25 +34,25 @@
<listitem>
<indexterm><primary>DataSource</primary><secondary>deployment type</secondary></indexterm>
- <para>The *-ds.xml file defines connections to external databases. The data source can then be reused by all applications and services in JBoss Enterprise Application Platform via the internal JNDI.</para></listitem>
+ <para>The <filename>*-ds.xml</filename> file defines connections to external databases. The data source can then be reused by all applications and services in JBoss Enterprise Application Platform via the internal JNDI.</para></listitem>
<listitem>
<indexterm><primary>JBoss Microcontainer</primary><secondary>*-jboss-beans.xml deployment type</secondary></indexterm>
- <para>You can deploy *-jboss-beans.xml files with MC beans definitions. If you have the approriate JAR files available in the deploy or lib directories, the MC beans can be deployed using such a standalone XML file. This is a </para></listitem>
+ <para>You can deploy <filename>*-jboss-beans.xml</filename> files with MC beans definitions. If you have the approriate JAR files available in the deploy or lib directories, the MC beans can be deployed using such a standalone XML file. This is a </para></listitem>
<listitem>
<indexterm><primary>Service Archive</primary><secondary>*-service.xml deployment type</secondary></indexterm>
- <para>You can deploy *-service.xml files with MBean service definitions. If you have the appropriate JAR files available in the deploy or lib directories, the MBeans specified in the XML files will be started. This is the way you deploy many JBoss Enterprise Application Platform internal services that have not been updated to support POJO style deployment, such as the JMS queues.</para></listitem>
+ <para>You can deploy <filename>*-service.xml</filename> files with MBean service definitions. If you have the appropriate JAR files available in the deploy or lib directories, the MBeans specified in the XML files will be started. This is the way you deploy many JBoss Enterprise Application Platform internal services that have not been updated to support POJO style deployment, such as the JMS queues.</para></listitem>
-<listitem><para>You can also deploy JAR files containing EJBs or other service objects directly in JBoss Enterprise Application Platform. The list of suffixes that are recognized as JAR files is specified in the conf/bootstrap/deployers.xml JARStructure bean constructor set.</para></listitem>
+<listitem><para>You can also deploy JAR files containing EJBs or other service objects directly in JBoss Enterprise Application Platform. The list of suffixes that are recognized as JAR files is specified in the <filename>conf/bootstrap/deployers.xml</filename> JARStructure bean constructor set.</para></listitem>
</itemizedlist>
<note>
<title>Exploded Deployment</title>
<indexterm><primary>Exploded Deployment</primary></indexterm>
- <para>The WAR, EAR, MC beans and SAR deployment packages are really just JAR files with special XML deployment descriptors in directories like META-INF and WEB-INF. JBoss Enterprise Application Platform allows you to deploy those archives as expanded directories instead of JAR files. That allows you to make changes to web pages etc on the fly without re-deploying the entire application. If you do need to re-deploy the exploded directory without re-start the server, you can just "touch" the deployment descriptors (e.g., the WEB-INF/web.xml in a WAR and the META-INF/application.xml in an EAR) to update their timestamps.</para>
+ <para>The WAR, EAR, MC beans and SAR deployment packages are really just JAR files with special XML deployment descriptors in directories like META-INF and WEB-INF. JBoss Enterprise Application Platform allows you to deploy those archives as expanded directories instead of JAR files. That allows you to make changes to web pages etc on the fly without re-deploying the entire application. If you do need to re-deploy the exploded directory without re-start the server, you can just <code>touch</code> the deployment descriptors (e.g., the <filename>WEB-INF/web.xml</filename> in a WAR and the <filename>META-INF/application.xml</filename> in an EAR) to update their timestamps.</para>
</note>
</section>
@@ -62,8 +62,8 @@
<indexterm><primary>Server Configuration</primary><see>Server Profile</see></indexterm>
<indexterm><primary>Server Profile</primary><secondary>definition</secondary></indexterm>
- <para>The JBoss Enterprise Application Platform ships with five server profiles. You can choose which configuration to start by passing the -c parameter to the server startup script. For instance, command run.sh -c all would start the server in the all profile. Each profile is contained in a directory named <literal> JBOSS_HOME/server/[profile name]/</literal>. You can look into each server profile's directory to see the services, applications, and libraries included in the profile.</para>
- <note><para>The exact contents of the server/[profile name] directory depends on the profile service implementation and is subject to change as the management layer and embedded server evolve.</para></note>
+ <para>The JBoss Enterprise Application Platform ships with five server profiles. You can choose which configuration to start by passing the <code>-c</code> parameter to the server startup script. For instance, the <code>run.sh -c all</code> command would start the server in the <emphasis>all</emphasis> profile. Each profile is contained in a directory named <filename>JBOSS_HOME/server/[profile name]/</filename>. You can look into each server profile's directory to see the services, applications, and libraries included in the profile.</para>
+ <note><para>The exact contents of the <filename>server/[profile name]</filename> directory depends on the profile service implementation and is subject to change as the management layer and embedded server evolve.</para></note>
<itemizedlist>
<listitem>
@@ -71,20 +71,20 @@
<para>The minimal profile starts the core server container without any of the enterprise services. It is a good starting point if you want to build a customized version of JBoss Enterprise Application Platform that only contains the services you need.</para></listitem>
<listitem>
<indexterm><primary>Profiles</primary><secondary>default</secondary></indexterm>
- <para>The default profile is the mostly common used profile for application developers. It supports the standard Java EE 5.0 programming APIs (e.g., Annotations, JPA, and EJB3).</para></listitem>
+ <para>The <emphasis>default</emphasis> profile is the mostly common used profile for application developers. It supports the standard Java EE 5.0 programming APIs (e.g., Annotations, JPA, and EJB3).</para></listitem>
<listitem>
<indexterm><primary>Profiles</primary><secondary>standard</secondary></indexterm>
- <para>The standard profile is the profile that has been tested for JavaEE compliance. The major differences with the existing configurations is that call-by-value and deployment isolation are
- enabled by default, along with support for rmiiiop and juddi (taken from the all config).</para></listitem>
+ <para>The <emphasis>standard</emphasis> profile is the profile that has been tested for JavaEE compliance. The major differences with the existing configurations is that call-by-value and deployment isolation are
+ enabled by default, along with support for <filename>rmiiiop</filename> and <filename>juddi</filename> (taken from the <emphasis>all</emphasis> config).</para></listitem>
<listitem>
<indexterm><primary>Profiles</primary><secondary>all</secondary></indexterm>
- <para>The all profile is the default profile with clustering support and other enterprise extensions.</para></listitem>
+ <para>The <emphasis>all</emphasis> profile is the default profile with clustering support and other enterprise extensions.</para></listitem>
<listitem>
<indexterm><primary>Profiles</primary><secondary>web</secondary></indexterm>
- <para>The web profile is a new experimental lightweight configuration created around JBoss Web that will follow the developments of the JavaEE 6 web profile. Except for the servlet/jsp container it provides support for JTA/JCA and JPA. It also limits itself to allowing access to the server only through the http port. Please note that this configuration is not JavaEE certified and will most likely change in the following releases.</para></listitem>
+ <para>The <emphasis>web</emphasis> profile is a new experimental lightweight configuration created around JBoss Web that will follow the developments of the JavaEE 6 web profile. Except for the servlet/jsp container it provides support for JTA/JCA and JPA. It also limits itself to allowing access to the server only through the http port. Please note that this configuration is not JavaEE certified and will most likely change in the following releases.</para></listitem>
</itemizedlist>
- <para>The detailed services and APIs supported in each of those profiles will be discussed throughout this book.</para>
+ <para>The detailed services and APIs supported in each of those profiles will be discussed throughout.</para>
</section>
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2009-07-16 04:34:55 UTC (rev 91330)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2009-07-16 04:43:51 UTC (rev 91331)
@@ -9,9 +9,9 @@
JBoss Enterprise Application Platform 5 is built on top of the new JBoss Microcontainer.
The JBoss Microcontainer is a lightweight container that supports direct deployment, configuration and lifecycle of plain old Java objects (POJOs).
<indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>JMX Microkernel</secondary></indexterm>
- The JBoss Microcontainer project is standalone and replaces the JBoss JMX Microkernel used in the 3.x and 4.x JBoss Application Servers.
- Project goals include:
- </para>
+ The JBoss Microcontainer project is standalone and replaces the JBoss JMX Microkernel used in the 4.x JBoss Enterprise Application Platforms.
+<!-- Project goals include: -->
+<!-- </para>
<para>
<itemizedlist>
<listitem>
@@ -39,8 +39,8 @@
Provide POJO configuration management, support for dependencies, and support for clustering.
</para>
</listitem>
- </itemizedlist>
-
+ </itemizedlist> -->
+ <para>
The JBoss Microcontainer integrates nicely with the JBoss Aspect
Oriented Programming framework (JBoss AOP). JBoss AOP is discussed in <xref linkend="jboss_aop"/> Support for JMX in JBoss Enterprise Application Platform 5 remains strong and MBean services written against the old Microkernel are expected to work.
</para>
@@ -52,7 +52,7 @@
</para>
<para>
- A sample Java EE 5 application that can be run on top of JBoss Enterprise Application Platform 5.0.0.GA and above which demonstrates many interesting technologies is the Seam Booking Application available on <ulink url="http://seamframework.org/Documentation/RunningSeamExamplesWithJBossApplicationServer5"/>. This application makes use of the following technologies running on JBoss Enterprise Application Platform 5:
+ A sample Java EE 5 application that can be run on top of JBoss Enterprise Application Platform 5.0.0.GA and above which demonstrates many interesting technologies is the Seam Booking Application available with this distribution. This example application makes use of the following technologies running on JBoss Enterprise Application Platform 5:
<itemizedlist>
<listitem>
@@ -99,7 +99,7 @@
</para>
<para>
- Many key features of JBoss Enterprise Application Platform 5 are provided by integrating other standalone JBoss projects which include: -
+ Many key features of JBoss Enterprise Application Platform 5 are provided by integrating standalone JBoss projects which include: -
<itemizedlist>
<listitem>
<para>
@@ -147,12 +147,12 @@
</listitem>
<listitem>
<para>
- mission critical web applications likely to be clustered.
+ Mission critical web applications likely to be clustered.
</para>
</listitem>
<listitem>
<para>
- Simple web applications with JSPs/Servlets upgrade to JBoss Enterprise Application Server with tomcat embedded.
+ Simple web applications with JSPs/Servlets upgrades to JBoss Enterprise Application Platform with tomcat embedded.
</para>
</listitem>
<listitem>
@@ -162,7 +162,7 @@
</listitem>
<listitem>
<para>
- Complex web apps with JSPs/Servlets, SEAM, Enterprise Java Beans (EJB), Java Messaging (JMS), caching etc.
+ Complex web applications with JSPs/Servlets, SEAM, Enterprise Java Beans (EJB), Java Messaging (JMS), caching etc.
</para>
</listitem>
<listitem>
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml 2009-07-16 04:34:55 UTC (rev 91330)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml 2009-07-16 04:43:51 UTC (rev 91331)
@@ -4,7 +4,7 @@
<preface id="What_this_Book_Covers"><title>What this Book Covers</title>
<para>
- The primary focus of this book is the presentation of the standard JBoss Enterprise Application Platform 5.0 architecture components from both the perspective of their configuration and architecture. As a user of a standard JBoss distribution you will be given an understanding of how to configure the standard components. Note that this book is not an introduction to JavaEE or how to use JavaEE in applications. It focuses on the internal details of the JBoss server architecture and how our implementation of a given JavaEE container can be configured and extended.
+ The primary focus of this book is the presentation of the standard JBoss Enterprise Application Platform 5.0 architecture components from both the perspective of their configuration and architecture. As a user of a standard JBoss distribution you will be given an understanding of how to configure the standard components. This book is not an introduction to JavaEE or how to use JavaEE in applications. It focuses on the internal details of the JBoss server architecture and how our implementation of a given JavaEE container can be configured and extended.
</para>
<para>
As a JBoss developer, you will be given a good understanding of the architecture and integration of the standard components to enable you to extend or replace the standard components for your infrastructure needs. We also show you how to obtain the JBoss source code, along with how to build and debug the JBoss server.
More information about the jboss-cvs-commits
mailing list