[jboss-cvs] JBossAS SVN: r82030 - projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Dec 4 02:00:40 EST 2008
Author: scott.stark at jboss.org
Date: 2008-12-04 02:00:39 -0500 (Thu, 04 Dec 2008)
New Revision: 82030
Modified:
projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml
Log:
JBAS-6280, an initial update of the quick tour section
Modified: projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml
===================================================================
--- projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml 2008-12-04 05:49:00 UTC (rev 82029)
+++ projects/docs/community/5/Installation_And_Getting_Started_Guide/en-US/resolved.xml 2008-12-04 07:00:39 UTC (rev 82030)
@@ -1509,26 +1509,28 @@
<screen>
[samson at dhcp-1-150 bin]$ sh run.sh
=========================================================================
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /downloads/jboss-5.0.0.CR2
-
- JAVA: /usr/local/jdk1.6.0_07//bin/java
- JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
-
- CLASSPATH: /downloads/jboss-5.0.0.CR2/bin/run.jar:/usr/local/jdk1.6.0_07//lib/tools.jar
+
+JBoss Bootstrap Environment
+
+JBOSS_HOME: /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.GA
+
+JAVA: /Library/Java/Home/bin/java
+
+JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
+
+CLASSPATH: /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.GA/bin/run.jar
+
=========================================================================
-
-15:23:05,038 INFO [ServerImpl] Starting JBoss (Microcontainer)...
-15:23:05,042 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)
+
+21:47:23,874 INFO [ServerImpl] Starting JBoss (Microcontainer)...
+21:47:23,875 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812011226)
.
.
...output truncated
.
.
-15:25:18,401 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
-15:25:18,556 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
-15:25:18,620 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)] Started in 2m:13s:511ms</screen>
+21:47:46,090 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
+21:47:46,112 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812011226)] Started in 22s:227ms
<!--<note>
<para>
Note that there is no "Server Started" message shown at the console when the server is started using the <literal>default</literal> profile, which is the default profile used when no other is specified. This message may be observed in the <filename>server.log</filename> file located in the <filename>server/defaut/log</filename> subdirectory.
@@ -1567,16 +1569,18 @@
<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations">
<title>Server Configurations</title>
<para>
- Fundamentally, the JBoss architecture consists of the JMX MBean server, the microkernel, and a set of pluggable component services - the MBeans. This makes it easy to assemble different configurations and gives you the flexibility to tailor them to meet your requirements.
+ Fundamentally, the JBoss architecture consists of the microcontainer, bootstrap beans loaded into the micrcontainer, a collection of deployers for loading various deployment types, and various mcbean(-jboss-beans.xml) and legacy mbean(jboss-service.xml) deployments.
+ This makes it easy to assemble different configurations and gives you the flexibility to tailor them to meet your requirements.
</para>
<para>
You don’t have to run a large, monolithic server all the time; you can remove the components you don’t need (which can also reduce the server startup time considerably) and you can also integrate additional services into JBoss by writing your own MBeans. You certainly do not need to do this to be able to run standard Java EE 5 applications though.
</para>
<para>
- You don’t need a detailed understanding of JMX to use JBoss, but it’s worth keeping a picture of this basic architecture in mind as it is central to the way JBoss works.
+ You don’t need a detailed understanding of the microcontainer to use JBoss, but it’s worth keeping a picture of this basic architecture in mind as it is central to the way JBoss works.
</para>
<para>
- The JBoss Application Server ships with three different server configurations. Within the <literal><JBoss_Home>/server</literal> directory, you will find four subdirectories: <literal>minimal</literal>, <literal>default</literal> and <literal>all</literal> - one for each server configuration. Each of these configurations provide a different set of services. The <literal>default</literal> configuration is the one used if you don’t specify another one when starting up the server.
+ The JBoss Application Server ships with three different server configurations. Within the <literal><JBoss_Home>/server</literal> directory, you will find five subdirectories:
+ <literal>minimal</literal>, <literal>default</literal>, <literal>standard</literal>, <literal>all</literal> and <literal>web</literal> - one for each server configuration. Each of these configurations provide a different set of services. The <literal>default</literal> configuration is the one used if you don’t specify another one when starting up the server.
</para>
<para>
<variablelist>
@@ -1604,19 +1608,75 @@
</para>
</listitem>
</varlistentry>
-
+ <varlistentry>
+ <term>standard</term>
+ <listitem>
+ <para>
+ is the JavaEE 5 certified configuration of services.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>web</term>
+ <listitem>
+ <para>
+ is a lightweight web container oriented profile that previews the JavaEE 6 web profile.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</para>
<para>
- If you want to know which services are configured in each of these instances, look at the <filename>jboss-service.xml</filename> file in the <filename class="directory"><JBoss_Home>/server/<instance-name>/conf/</filename> directory and also the configuration files in the <filename class="directory"><JBoss_Home>/server/<instance-name>/deploy</filename> directory.
+ If you want to know which services are configured in each of these instances, the primary differences will be in the <filename class="directory"><JBoss_Home>/server/<instance-name>/deployers/</filename> directory and also the services deployments in the <filename class="directory"><JBoss_Home>/server/<instance-name>/deploy</filename> directory. For example, the default profile deployers and deploy directory contents are:
<programlisting>
-[usr at localhost <JBoss_Home>]$<literal>ls server/default/conf </literal>
-bootstrap-beans.xml jboss-log4j.xml login-config.xml xmdesc
-bootstrap-repo-beans.xml jboss-minimal.xml props
-jax-ws-catalog.xml jboss-service.xml standardjbosscmp-jdbc.xml
- jbossjta-properties.xml jndi.properties standardjboss.xml
-
+[usr at localhost <JBoss_Home>]$<literal>ls server/default/deployers </literal>
+alias-deployers-jboss-beans.xml jboss-aop-jboss5.deployer
+bsh.deployer jboss-jca.deployer
+clustering-deployer-jboss-beans.xml jbossweb.deployer
+dependency-deployers-jboss-beans.xml jbossws.deployer
+directory-deployer-jboss-beans.xml j sr77-deployers-jboss-beans.xml
+ear-deployer-jboss-beans.xml metadata-deployer-jboss-beans.xml
+ejb-deployer-jboss-beans.xml seam.deployer
+ejb3.deployer security-deployer-jboss-beans.xml
+hibernate-deployer-jboss-beans.xml
+[usr at localhost <JBoss_Home>]$<literal>ls server/default/deploy </literal>
+ROOT.war jsr88-service.xml
+cache-invalidation-service.xml legacy-invokers-service.xml
+ejb2-container-jboss-beans.xml mail-ra.rar
+ejb2-timer-service.xml mail-service.xml
+ejb3-connectors-jboss-beans.xml management
+ejb3-container-jboss-beans.xml messaging
+ejb3-interceptors-aop.xml monitoring-service.xml
+ejb3-timer-service.xml profileservice-jboss-beans.xml
+hdscanner-jboss-beans.xml properties-service.xml
+hsqldb-ds.xml quartz-ra.rar
+http-invoker.sar remoting-jboss-beans.xml
+jboss-local-jdbc.rar schedule-manager-service.xml
+jboss-xa-jdbc.rar scheduler-service.xml
+jbossweb.sar security
+jbossws.sar sqlexception-service.xml
+jca-jboss-beans.xml transaction-jboss-beans.xml
+jms-ra.rar transaction-service.xml
+jmx-console.war uuid-key-generator.sar
+jmx-invoker-service.xml vfs-jboss-beans.xml
+jmx-remoting.sar
</programlisting>
+ while the web profile deployers and deploy directory contents are:
+<programlisting>
+[usr at localhost <JBoss_Home>]$<literal>ls server/web/deployers </literal>
+alias-deployers-jboss-beans.xml jbossweb.deployer
+ejb3.deployer metadata-deployer-jboss-beans.xml
+jboss-aop-jboss5.deployer security-deployer-jboss-beans.xml
+jboss-jca.deployer
+[usr at localhost <JBoss_Home>]$<literal>ls server/web/deployers </literal>
+ROOT.war jbossweb.sar
+ejb3-container-jboss-beans.xml jca-jboss-beans.xml
+hdscanner-jboss-beans.xml jmx-console.war
+hsqldb-ds.xml jmx-invoker-service.xml
+http-invoker.sar security
+jboss-local-jdbc.rar transaction-jboss-beans.xml
+jboss-xa-jdbc.rar
+</programlisting>
</para>
<note>
<para>
@@ -1653,7 +1713,7 @@
<filename class="directory">conf</filename>
</entry>
<entry>
- The <filename class="directory">conf</filename> directory contains the <filename>jboss-service.xml</filename> bootstrap descriptor file for a given server configuration. This defines the core services that are fixed for the lifetime of the server.
+ The <filename class="directory">conf</filename> directory contains the <filename>bootstrap.xml</filename> bootstrap descriptor file for a given server configuration. This defines the core microcontainer beans that are fixed for the lifetime of the server.
</entry>
</row>
<row>
@@ -1677,7 +1737,7 @@
<filename class="directory">lib</filename>
</entry>
<entry>
- This directory contains JAR files (Java libraries that should not be hot deployed) needed by this server configuration. You can add required library files here for JDBC drivers etc. All JARs in this directory are loaded into the shared classpath at startup.
+ This directory contains JAR files (Java libraries that should not be hot deployed) needed by this server configuration. You can add required library files here for JDBC drivers etc. All JARs in this directory are loaded into the shared classpath at startup. Note that this directory only contains those jars unique to the server configuration. Jars common across the server configurations are now located in <filename class="directory"><JBoss_Home>/common/lib</filename>.
</entry>
</row>
<row>
@@ -1716,6 +1776,10 @@
<screen>[user at localhost <JBoss_Home>]$ tree
|-- bin
|-- client
+|-- common
+| |-- lib
+| | |-- antlr.jar
+| | |-- ... many more jars
|-- docs
| |-- dtd
| |-- examples
@@ -1751,9 +1815,22 @@
`-- server
|-- all
| |-- conf
+| | |-- bootstrap/
+| | | |-- aop.xml
+| | | |-- bindings.xml
+| | | |-- aop.xml
+| | | |-- classloader.xml
+| | | |-- deployers.xml
+| | | |-- jmx.xml
+| | | |-- profile-repository.xml
+| | | |-- profile.xml
+| | | |-- vfs.xml
+| | |-- bootstrap.xml
+| | |-- bootstrap-norepo.xml
| | |-- jacorb.properties
+| | |-- java.policy
+| | |-- jax-ws-catalog.xml
| | |-- jboss-log4j.xml
-| | |-- jboss-minimal.xml
| | |-- jboss-service.xml
| | |-- jbossjta-properties.xml
| | |-- jndi.properties
@@ -1769,13 +1846,26 @@
| |-- deploy
| |-- deploy-hasingleton
| | `-- jms
-| |-- farm
-| | `-- cluster-examples-service.xml
+| |-- deployers
| `-- lib
|-- default
| |-- conf
+| | |-- bootstrap/
+| | | |-- aop.xml
+| | | |-- bindings.xml
+| | | |-- aop.xml
+| | | |-- classloader.xml
+| | | |-- deployers.xml
+| | | |-- jmx.xml
+| | | |-- profile-repository.xml
+| | | |-- profile.xml
+| | | |-- vfs.xml
+| | |-- bootstrap.xml
+| | |-- bootstrap-norepo.xml
+| | |-- jacorb.properties
+| | |-- java.policy
+| | |-- jax-ws-catalog.xml
| | |-- jboss-log4j.xml
-| | |-- jboss-minimal.xml
| | |-- jboss-service.xml
| | |-- jbossjta-properties.xml
| | |-- jndi.properties
@@ -1815,18 +1905,26 @@
| `-- localhost
`-- minimal
|-- conf
+| |-- bootstrap/
+| |-- bootstrap/aop.xml
+| |-- bootstrap/classloader.xml
+| |-- bootstrap/deployers.xml
+| |-- bootstrap/jmx.xml
+| |-- bootstrap/profile.xml
+| |-- bootstrap.xml
| |-- jboss-log4j.xml
| |-- jboss-service.xml
| |-- jndi.properties
| `-- xmdesc
| |-- NamingBean-xmbean.xml
| `-- NamingService-xmbean.xml
-|-- deploy
+|-- deploy/
+|-- deploy/hdscanner-jboss-beans.xml
+|-- deployers/
`-- lib
-|-- jboss-management.jar
|-- jboss-minimal.jar
|-- jnpserver.jar
- `-- log4j.jar</screen>
+`-- log4j.jar</screen>
</para>
<section id="The_default_Server_Configuration_File_Set-Contents_of_conf_directory">
@@ -1853,22 +1951,38 @@
<tbody>
<row>
<entry>
- <literal>jboss-minimal.xml</literal>
+ <literal>bootstrap.xml</literal>
</entry>
<entry>
- This is a minimalist example of the <literal>jboss-service.xml</literal> configuration file. (This is the <literal>jboss-service.xml</literal> file used in the <literal>minimal</literal> configuration file set)
+ This is the <literal>bootstrap.xml</literal> file that defines which additional microcontainer deployments will be loaded as part of the bootstrap phase.
</entry>
</row>
<row>
<entry>
+ <literal>bootstrap/*</literal>
+ </entry>
+ <entry>
+ This directory contains the microcontainer bootstrap descriptors that are referenced from the <literal>bootstrap.xml</literal> file.
+ </entry>
+ </row>
+ <row>
+ <entry>
<literal>jboss-service.xml</literal>
</entry>
<entry>
- <literal>jboss-service.xml</literal> defines the core services and their configurations.
+ <literal>jboss-service.xml</literal> legacy core mbeans that have yet to be ported to either bootstrap deployments, or deploy services. This file will go away in the near future.
</entry>
</row>
<row>
<entry>
+ <literal>jbossjta-properties.xml</literal>
+ </entry>
+ <entry>
+ <literal>jbossjta-properties.xml</literal> specifies the JBossTS transaction manager default properties.
+ </entry>
+ </row>
+ <row>
+ <entry>
<literal>jndi.properties</literal>
</entry>
<entry>
@@ -1877,6 +1991,14 @@
</row>
<row>
<entry>
+ <literal>java.policy</literal>
+ </entry>
+ <entry>
+ A placeholder java security policy file that simply grants all permissions.
+ </entry>
+ </row>
+ <row>
+ <entry>
<literal>jboss-log4j.xml</literal>
</entry>
<entry>
More information about the jboss-cvs-commits
mailing list