[jboss-cvs] JBossAS SVN: r82328 - projects/docs/community/5/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Dec 16 19:23:41 EST 2008
Author: scott.stark at jboss.org
Date: 2008-12-16 19:23:41 -0500 (Tue, 16 Dec 2008)
New Revision: 82328
Modified:
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml
Log:
JBAS-6280, restore inclusion of the perf tuning section and add an index
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2008-12-17 00:22:57 UTC (rev 82327)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2008-12-17 00:23:41 UTC (rev 82328)
@@ -125,8 +125,8 @@
| `-- work
| `-- jboss.web
| `-- localhost
- `-- minimal - a
- |-- conf
+ `-- minimal - a minimal server configuration
+ | |-- conf - contains server configuration files used when starting the server.
| |-- bootstrap/
| | | |-- aop.xml
| | | |-- classloader.xml
@@ -137,16 +137,16 @@
| |-- jboss-log4j.xml
| |-- jboss-service.xml
| |-- jndi.properties
- | `-- xmdesc
+ | |-- xmdesc
| |-- NamingBean-xmbean.xml
| `-- NamingService-xmbean.xml
- |-- deploy/
- |-- deploy/hdscanner-jboss-beans.xml
- |-- deployers/
- `-- lib
- |-- jboss-minimal.jar
- |-- jnpserver.jar
- `-- log4j.jar
+ | |-- deploy/
+ | | |-- hdscanner-jboss-beans.xml
+ | |-- deployers/
+ | |-- lib
+ | | |-- jboss-minimal.jar
+ | | |-- jnpserver.jar
+ | | |-- log4j.jar
]]></screen>
</para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml 2008-12-17 00:22:57 UTC (rev 82327)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml 2008-12-17 00:23:41 UTC (rev 82328)
@@ -1,5 +1,5 @@
<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<chapter id="Deployment">
@@ -7,35 +7,38 @@
<para>Deploying applications on JBoss AS 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 AS 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 AS is still running.</para>
- <section>
+ <section id="Deployable_Application_Types">
<title>Deployable Application Types</title>
- <para>You can deploy several different types of enterprise applications in JBoss AS:</para>
-
-
+ <para>With JBossAS 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 JBossAS 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 JBoss AS include:</para>
+
<itemizedlist>
- <listitem><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 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>
+ <listitem><para>The WAR <indexterm><primary>WAR</primary><seealso>Web Application</seealso></indexterm> 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>
<listitem><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 deployment descriptors such as application.xml and jboss-app.xml etc.</para></listitem>
- <listitem><para>The SAR application archive (e.g., myservice.sar) packages a JBoss service in a JAR file. It is mostly used by JBoss internal services.</para></listitem>
+ <listitem><para>The JBoss Microcontainer (MC) beans archive (typical suffixes include, .beans, .deployer) packages a POJO deployment in a JAR file. This format is commonly used by the JBossAS component deployers.</para></listitem>
+ <listitem><para>The SAR application archive (e.g., myservice.sar) packages a JBoss service in a JAR file. It is mostly used by JBossAS internal services that have not been updated to support MC style deployments.</para></listitem>
+
<listitem><para>The *-ds.xml file defines connections to external databases. The data source can then be reused by all applications and services in JBoss AS via the internal JNDI.</para></listitem>
+
+ <listitem><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>
+
+ <listitem><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 AS internal services that have not been updated to support POJO style deployment, such as the JMS queues.</para></listitem>
- <listitem><para>You can deploy 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 how you start many JBoss AS internal services, such as the JMS queues.</para></listitem>
+ <listitem><para>You can also deploy JAR files containing EJBs or other service objects directly in JBoss AS. 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 AS.</para></listitem>
-
</itemizedlist>
<note>
<title>Exploded Deployment</title>
- <para>The WAR, EAR, and SAR deployment packages are really just JAR files with special XML deployment descriptors in directories like META-INF and WEB-INF. JBoss AS 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 AS 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>
</note>
</section>
- <section>
+ <section id="Standard_Server_Profiles">
<title>Standard Server Configurations</title>
<para>The JBoss Application Server ships with three server configurations. 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 configuration. Each configuration is contained in a directory named <literal> JBOSS_HOME/server/[config name]/</literal>. You can look into each server configuration's directory to see the default services, applications, and libraries supported in the configuration.</para>
More information about the jboss-cvs-commits
mailing list