[jboss-cvs] JBossAS SVN: r99880 - projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jan 25 02:55:38 EST 2010
Author: laubai
Date: 2010-01-25 02:55:38 -0500 (Mon, 25 Jan 2010)
New Revision: 99880
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
Log:
Corrected Deploy.xml for EWP5.
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2010-01-25 07:38:24 UTC (rev 99879)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2010-01-25 07:55:38 UTC (rev 99880)
@@ -5,32 +5,34 @@
<chapter id="Deployment">
<title>Deployment</title>
- <para>Deploying applications on JBoss Enterprise Web 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 Web 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 Web Platform is still running.</para>
+ <para>Deploying applications on JBoss Enterprise Web Platform is achieved by copy the application into the <filename>$JBOSS_HOME/server/$PROFILE/deploy</filename> directory, where <literal>$PROFILE</literal> is the server profile you wish to use. The JBoss Enterprise Web Platform constantly scans the <filename>deploy</filename> 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 Web Platform is still running.</para>
<section id="Deployable_Application_Types">
<title>Deployable Application Types</title>
- <para>With JBoss Enterprise Web 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 Web 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 Web Platform include:</para>
+ <para>
+ JBoss Enterprise Web Platform uses mutiple deployers to transform the metadata associated with a deployment until the deployment is processed by a deployer that creates a runtime component from the metadata. Deployments must contain a descriptor that cause component metadata to be added to the deployment. Deployers for the following deployment types are available in JBoss Enterprise Web Platform by default:
+ </para>
<itemizedlist>
<listitem>
<indexterm><primary>WAR</primary><see>Web Application</see></indexterm>
<indexterm><primary>Web Application</primary><secondary>deployment type</secondary></indexterm>
- <para>The WAR application archive (e.g., myapp.war) packages a Java EE web application in a JAR file. It contains servlet classes, view pages, libraries, and deployment descriptors in WEB-INF such as web.xml, faces-config.xml, and jboss-web.xml etc.<!-- Please see more in <xref linkend="Web_Applications-The_Tomcat_Service"/>-->.</para></listitem>
+ <para>The WAR application archive (that is, deployments of the form <filename>myapp.war</filename>) packages a Java EE web application in a JAR file. It contains servlet classes, view pages, libraries, and deployment descriptors in <filename>WEB-INF</filename> such as <filename>web.xml</filename>, <filename>faces-config.xml</filename>, and <filename>jboss-web.xml</filename>, etc.<!-- Please see more in <xref linkend="Web_Applications-The_Tomcat_Service"/>-->.</para></listitem>
<listitem>
<indexterm><primary>EAR</primary><see>Enterprise Application</see></indexterm>
<indexterm><primary>Enterprise Application</primary><secondary>deployment type</secondary></indexterm>
- <para>The EAR application archive (e.g., myapp.ear) packages a Java EE enterprise application in a JAR file. It typically contains a WAR file for the web module, JAR files for EJB modules, as well as META-INF deployment descriptors such as application.xml and jboss-app.xml etc.</para></listitem>
+ <para>The EAR application archive (that is, deployments of the form <filename>myapp.ear</filename>) packages a Java EE enterprise application in a JAR file. It typically contains a WAR file for the web module, JAR files for EJB modules, as well as <filename>META-INF</filename> deployment descriptors such as <filename>application.xml</filename> and <filename>jboss-app.xml</filename>, etc.</para></listitem>
<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 <filename>META-INF/jboss-beans.xml</filename> descriptor. This format is commonly used by the JBoss Enterprise Web Platform component deployers.</para></listitem>
+ <para>The JBoss Microcontainer (MC) beans archive (typical suffixes include, <filename>.beans</filename> and <filename>.deployer</filename>) 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 Web Platform component deployers.</para></listitem>
<listitem>
<indexterm><primary>SAR</primary><see>Service Archive</see></indexterm>
<indexterm><primary>Service Archive</primary><secondary>deployment type</secondary></indexterm>
- <para>The SAR application archive (e.g., myservice.sar) packages a JBoss service in a JAR file. It is mostly used by JBoss Enterprise Web Platform internal services that have not been updated to support MC beans style deployments.</para></listitem>
+ <para>The SAR application archive (that is, deployments of the form <filename>myservice.sar</filename>) packages a JBoss service in a JAR file. It is mostly used by JBoss Enterprise Web Platform internal services that have not been updated to support MC beans style deployments.</para></listitem>
<listitem>
<indexterm><primary>DataSource</primary><secondary>deployment type</secondary></indexterm>
@@ -38,21 +40,21 @@
<listitem>
<indexterm><primary>JBoss Microcontainer</primary><secondary>*-jboss-beans.xml deployment type</secondary></indexterm>
- <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.</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 <filename>deploy</filename> or <filename>lib</filename> directories, the MC beans can be deployed using such a standalone XML file.</para></listitem>
<listitem>
<indexterm><primary>Service Archive</primary><secondary>*-service.xml deployment type</secondary></indexterm>
<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 Web 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 Web 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>
+<listitem><para>You can also deploy JAR files containing EJBs or other service objects directly in JBoss Enterprise Web Platform. The list of suffixes that are recognized as JAR files is specified in the <filename>conf/bootstrap/deployers.xml</filename> <literal>JARStructure</literal> 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 Web 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>
+ <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 Web 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 (for example, 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,34 +64,33 @@
<indexterm><primary>Server Configuration</primary><see>Server Profile</see></indexterm>
<indexterm><primary>Server Profile</primary><secondary>definition</secondary></indexterm>
- <para>The JBoss Enterprise Web Platform ships with six 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>
+ <para>The JBoss Enterprise Web Platform ships with six 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 <literal>all</literal> 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</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>
+ <!--<listitem>
<indexterm><primary>Profiles</primary><secondary>minimal</secondary></indexterm>
- <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 Web Platform that only contains the services you need.</para></listitem>
+ <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 Web Platform that only contains the services you need.</para></listitem>-->
<listitem>
<indexterm><primary>Profiles</primary><secondary>default</secondary></indexterm>
- <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>
+ <para>The <literal>default</literal> profile is the mostly common used profile for application developers. It supports the standard Java EE 5.0 programming APIs (for example, Annotations, JPA, and EJB3).</para></listitem>
+<!-- <listitem>
<indexterm><primary>Profiles</primary><secondary>standard</secondary></indexterm>
<para>The <emphasis>standard</emphasis> profile is the profile that has been tested for Java EE 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 <emphasis>all</emphasis> 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>production</secondary></indexterm>
- <para>The <emphasis>production</emphasis> profile is based on the all profile but optimized for production environments.</para></listitem>
- <listitem>
+ <para>The <literal>production</literal> profile has the features of the <literal>default</literal> profile with added clustering support and enterprise extensions. It is optimized for production environments.</para></listitem>
+ <!--<listitem>
<indexterm><primary>Profiles</primary><secondary>web</secondary></indexterm>
- <para>The <emphasis>web</emphasis> profile is a new experimental lightweight configuration created around JBoss Web that will follow the developments of the Java EE 6 web profile. Except for the <filename>servlet/jsp</filename> 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 Java EE 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 Java EE 6 web profile. Except for the <filename>servlet/jsp</filename> 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 Java EE 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.</para>
+ <para>The detailed services and APIs supported in each of these profiles will be discussed throughout.</para>
</section>
</chapter>
-
More information about the jboss-cvs-commits
mailing list