[jboss-cvs] JBossAS SVN: r112172 - in projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US: images and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Aug 30 15:49:00 EDT 2011
Author: smcgowan at redhat.com
Date: 2011-08-30 15:48:59 -0400 (Tue, 30 Aug 2011)
New Revision: 112172
Added:
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/QuickTour.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/images/JMXView.png
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/images/microcontainer.png
Removed:
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
Modified:
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/About_the_Example_Applications.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix1.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix2.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/EJB3.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Getting_Started.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation_And_Getting_Started_Guide.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Preface.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml
projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Test_Your_Installation.xml
Log:
JBAS-8006 - prepare documentation for community site update
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/About_the_Example_Applications.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/About_the_Example_Applications.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/About_the_Example_Applications.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -5,7 +5,7 @@
<chapter id="About_the_Example_Applications">
<title>Sample Applications</title>
<para>
- The JBoss Application Server, ships with various sample applications under <literal>JBOSS_HOME/docs/examples</literal>.
+ The JBoss Application Server 6 ships with reference examples under <literal>JBOSS_HOME/docs/examples</literal>.
</para>
<para>
For further details, please refer to the accompanying <filename>readme.txt</filename> for the respective sample applications under the above directory.
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix1.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix1.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix1.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -4,11 +4,28 @@
<appendix id="appendix1">
<title>Book Revision History</title>
+<para>
<bibliolist>
<biblioentry>
<revhistory>
<revision>
+ <revnumber>6.1.0</revnumber>
+ <date>August 28 2011</date>
+ <author>
+ <firstname>Shelly</firstname>
+ <surname>McGowan</surname>
+
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Updated Content for 6.1.0.Final release </member>
+
+ </simplelist>
+ </revdescription>
+ </revision>
+
+ <revision>
<revnumber>6.0.0</revnumber>
<date>January 17 2010</date>
<author>
@@ -18,7 +35,7 @@
</author>
<revdescription>
<simplelist>
- <member>Updated Content for Final release </member>
+ <member>Updated Content for 6.0.0.Final release </member>
</simplelist>
</revdescription>
@@ -56,6 +73,7 @@
</biblioentry>
</bibliolist>
+</para>
</appendix>
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix2.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix2.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Appendix2.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -2,7 +2,7 @@
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<appendix id="appendix2">
- <title>Further Information Sources</title>
+ <title>Additional Information Sources</title>
<para>
Developers wanting to get familiar with software development and implementation in JBoss Application Server can read: <emphasis>JBoss in Action: Configuring the JBoss Application Server</emphasis>. (Manning, 2009. Javid Jamae, Peter Johnson).
</para>
@@ -10,7 +10,7 @@
For more JBoss documentation related to JBoss Application Server 6 and its' underlying technologies, refer to the manuals available online at <ulink url="http://www.jboss.org/jbossas/docs/6-x.html"/>.
</para>
<para>
- For the latest information on EJB 3.1 with thorough JBoss coverage see <ulink url="http:http://www.amazon.ca/Enterprise-JavaBeans-3-1-Andrew-Rubinger/dp/0596158025"><emphasis>Enterprise JavaBeans 3.1, 6th Edition</emphasis></ulink>. (O'Reilly, 2010. Andrew Rubinger, Bill Burke). The book examples show how Java EE integration testing is made easier using <ulink url="http://www.jboss.org/arquillian">Arquillian</ulink> and <ulink url="http://jboss.org/shrinkwrap">ShrinkWrap</ulink>, two breakthrough community projects simplifying Java EE integration testing.
+ For the latest information on EJB 3.1 with thorough JBoss coverage see <ulink url="http://www.amazon.com/Enterprise-JavaBeans-3-1-Andrew-Rubinger/dp/0596158025"><emphasis>Enterprise JavaBeans 3.1, 6th Edition</emphasis></ulink>. (O'Reilly, 2010. Andrew Rubinger, Bill Burke). The book examples show how Java EE integration testing is made easier using <ulink url="http://www.jboss.org/arquillian">Arquillian</ulink> and <ulink url="http://jboss.org/shrinkwrap">ShrinkWrap</ulink>, two breakthrough community projects simplifying Java EE integration testing.
</para>
<para>
To learn more about RESTEasy, see <ulink url="http://www.amazon.com/RESTful-Java-Jax-RS-Animal-Guide/dp/0596158041"><emphasis>RESTFul Java with Jax-RS</emphasis></ulink>. (O'Reilly, 2010. Bill Burke)
@@ -18,4 +18,5 @@
<para>
For complete coverage of the JBoss Seam framework, refer to <ulink url="http://www.amazon.com/Seam-Action-Dan-Allen/dp/1933988401"><emphasis>Seam in Action</emphasis></ulink>. (Manning, 2009. Dan Allen).
</para>
+ <para>More information on the <emphasis>JBoss Microcontainer</emphasis> project can be obtained from <ulink url="http://www.jboss.org/jbossmc/">http://www.jboss.org/jbossmc/"</ulink>.</para>
</appendix>
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/EJB3.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/EJB3.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -4,21 +4,11 @@
<chapter id="EJB3">
<title>
- EJB 3 in JBoss Application Server 6.0.0
+ EJB 3 in JBoss Application Server 6
</title>
<para>
- There are a number of implementation features that you should be aware of when developing applications for JBoss Application Server 6.0.0.
+ Referenced the JBoss EJB3 Documentation <emphasis>provide LINK HERE</emphasis>.
</para>
- <section>
- <title>
- Unimplemented features
- </title>
-
- <para>
- The Release Notes for JBoss Application Server contain information on EJB3 features that are not yet implemented, or partially implemented. The Release Notes include links to issues in JIRA for information on workarounds and further details.
- </para>
- </section>
-
</chapter>
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Getting_Started.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Getting_Started.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -6,7 +6,7 @@
<title>Getting Started</title>
<section id="Configuring your Java Environment"><title>Configuring your Java Environment</title>
<para>
- You must have a working installation of <emphasis>JDK 1.6</emphasis> before you install JBoss Application Server. You can install the 32-bit or 64-bit JVM depending on your requirements.
+ You must have a working installation of <emphasis>JDK 1.6</emphasis> before you install JBoss Application Server 6. You can install the 32-bit or 64-bit JVM depending on your requirements.
</para>
<para>Be sure to create an environment variable that points to the JDK installation directory and call it <literal>JAVA_HOME</literal>. Add <literal>$JAVA_HOME/bin</literal> to the system path to be able to run <literal>java</literal> from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. In this example /usr/java/jdk1.6.0 is the JDK installation directory.
<programlisting>
@@ -17,7 +17,7 @@
<para>
Make sure that the <literal>java</literal> executable is in your path and that you are using an appropriate version. To verify your Java environment, type <literal>java -version</literal> at the shell prompt and you should see something like this:
<programlisting>
- [root at hostname]$ java -version
+ [user at localhost]$ java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -6,17 +6,17 @@
<title>Installation</title>
<section id="Zip Distribution"><title>Installation with the Zip Distribution</title>
<para>
- In this form of installation, simply unzip the downloaded zip file to the directory of your choice. You can unzip JBoss Application Server 6 on any operating system that supports the zip format. Zip distributions of the latest milestone releases are available on <ulink url="http://www.jboss.org/jbossas/downloads/">JBoss AS Download</ulink> site. Refer to the Release Notes for additional information on the milestone release you select for download which includes new features and bug fixes included in the release.
+ In this form of installation, simply unzip the downloaded zip file to the directory of your choice. You can unzip JBoss Application Server 6 on any operating system that supports the zip format. Zip distributions of the latest milestone releases are available on <ulink url="http://www.jboss.org/jbossas/downloads/">JBoss Application Server Download</ulink> site. Refer to the Release Notes for additional information on the milestone release you select for download which includes new features and bug fixes included in the release.
</para>
</section>
<section id="Building Distribution from Source"><title>Building Distribution from Source</title>
- <para>Check out the latest version of the JBoss AS 6 sources from the anonymous <ulink url="http://anonsvn.jboss.org/repos/jbossas/trunk/">JBoss subversion repository</ulink>:</para>
+ <para>Alternatively, if you prefer you can check out the latest version of the sources from the anonymous <ulink url="http://anonsvn.jboss.org/repos/jbossas/trunk/">JBoss subversion repository</ulink>:</para>
<programlisting>
svn co http://anonsvn.jboss.org/repos/jbossas/trunk
</programlisting>
-<para> If you are already an authorized committer check out the sources providing your username and password from:</para>
+<para> If you are already an authorized committer check out the sources providing your username and password from:</para>y
<programlisting>
svn co https://svn.jboss.org/repos/jbossas/trunk --username your_username
</programlisting>
@@ -32,7 +32,7 @@
<listitem><ulink url="http://community.jboss.org/wiki/MavenRepository-FAQ">Maven Repository FAQ</ulink></listitem>
<listitem><ulink url="http://community.jboss.org/wiki/MavenSettingsExample-Developers">Maven Settings Example for Developers</ulink></listitem>
</itemizedlist>
-If you have additional questions, post your question on the <ulink url="http://community.jboss.org/en/jbossas/">JBoss AS community forum</ulink>.
+If you have additional questions, post your question on the <ulink url="http://community.jboss.org/en/build/">JBoss Community Build System</ulink> forum.
</para>
To build JBoss Application Server 6, simply execute:
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation_And_Getting_Started_Guide.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation_And_Getting_Started_Guide.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Installation_And_Getting_Started_Guide.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -2,8 +2,8 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.docbook.org/xml/4.4/docbookx.dtd"
[
-<!ENTITY versionNumber "5.0.0.GA">
-<!ENTITY copyrightYear "2008">
+<!ENTITY versionNumber "6.1.0.Final">
+<!ENTITY copyrightYear "2011">
<!ENTITY copyrightHolder "Red Hat Middleware, LLC.">
<!ELEMENT xi:include (xi:fallback?) >
<!ATTLIST xi:include
@@ -43,16 +43,13 @@
</bookinfo>
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <!-- <xi:include href="Whats_New.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
- <xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Whats_New.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Setting_JBOSS_HOME.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Start_Stop_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="The_JBoss_Server_A_Quick_Tour.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <!-- <xi:include href="EJB3.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
- <!-- <xi:include href="About_the_Example_Applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
- <!-- <xi:include href="Sample_JSF_EJB3_Application.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
- <!-- <xi:include href="Using_Seam.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+ <xi:include href="QuickTour.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Using_Other_Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Appendix1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Preface.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Preface.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -5,7 +5,7 @@
<title>Preface</title>
<section id="Introduction"><title>Introduction</title>
<para>
- JBoss Application Server 6 is the open source implementation of the Java EE 6 Enterprise Edition Platform. It comprises the set of technologies for enterprise developers looking for an easy-to-use, out-of-box, robust solution for running enterprise applications. Offering an extensible core architecture, JBoss Application Server 6 is the ideal choice for users new to enterprise development as well as senior architects looking for a customizable middleware platform.
+ JBoss Application Server 6 is the open source implementation of the Java Enterprise Edition 6 Platform. It comprises the set of technologies for enterprise developers looking for an easy-to-use, out-of-box, robust solution for running enterprise applications. Offering an extensible core architecture, JBoss Application Server 6 is the ideal choice for users new to enterprise development as well as senior architects looking for a customizable middleware platform.
</para>
<para>
Because it is Java-based, JBoss Application Server 6 runs on any operating system that supports Java. This guide will provide information to get you started using JBoss Application Server 6 in a few easy steps. It will also provide an overview of the distribution layout and other feature highlight. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.</para>
Copied: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/QuickTour.xml (from rev 112114, projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml)
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/QuickTour.xml (rev 0)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/QuickTour.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -0,0 +1,1424 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.docbook.org/xml/4.4/docbookx.dtd"
+[
+<!ELEMENT xi:include (xi:fallback?) >
+<!ATTLIST xi:include
+xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude"
+href CDATA #REQUIRED
+parse (xml|text) "xml"
+xpointer CDATA #IMPLIED
+encoding CDATA #IMPLIED
+accept CDATA #IMPLIED
+accept-charset CDATA #IMPLIED
+accept-language CDATA #IMPLIED >
+<!ELEMENT xi:fallback ANY >
+<!ATTLIST xi:fallback
+xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude" >
+<!ENTITY % local.preface.class "| xi:include" >
+<!ENTITY % local.part.class "| xi:include" >
+<!ENTITY % local.chapter.class "| xi:include" >
+<!ENTITY % local.divcomponent.mix "| xi:include" >
+<!ENTITY % local.para.char.mix "| xi:include" >
+<!ENTITY % local.info.class "| xi:include" >
+<!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED
+xmlns:xi CDATA #FIXED 'http://www.w3.org/2001/XInclude'" >
+
+]>
+
+<chapter id="QuickTour">
+ <title>JBoss Application Server 6 - A Quick Tour</title>
+ <para>
+ Now that you’ve downloaded JBoss and have run the server for the first time the next thing you will want to know is how the installation is laid out and what goes where. At first glance there seems to be a lot of stuff in there and it’s not obvious what you need to look at and what you can safely ignore for the time being. To remedy that, we’ll explore the server directory structure, locations of the key configuration files, log files, deployment and so on. It’s worth familiarizing yourself with the layout at this stage as it will help you understand the JBoss service architecture so that you’ll be able to find your way around when it comes to deploying your own applications.
+ </para>
+
+ <section id="Server Architecture">
+ <title>Server Architecture</title>
+<para>
+ Fundamentally, the JBoss Application Server 6 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 all the available services all the time; you can remove unwanted components (which can also reduce the server startup time considerably) or you can integrate additional services into JBoss by writing your own. However, neither is necessary to ensure running of standard Java EE 6 applications without any modifications.
+</para>
+
+<para>
+ This section introduces the various Microcontainer modules. A detailed understanding of the microcontainer is not necessary to use JBoss but we'll outline the basic architecture as it is central to the way JBoss application server works. The figure below gives an overview of the modules.
+</para>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/microcontainer.png"/>
+ </imageobject>
+ </mediaobject>
+
+<itemizedlist>
+ <listitem>
+ <para>
+ <literal>Tools</literal> represents a variety of tools to assist users with use and development with JBoss Microcontainer.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>Integr.</literal> represents the <literal>aop-mc-int</literal> module, which handles integration between the JBoss AOP and JBoss Microcontainer.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>Deployers</literal> load components from from various modules (such as POJOs, JMX, Spring, Java EE) into the Microcontainer at runtime.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>CL</literal> represents the <emphasis>Classloader</emphasis>, a new peer classloader module that handles the OSGi bundle module.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>VFS</literal> represents the <emphasis>Virtual File System</emphasis>. This is an abstract layer used to identify known file system issues within a single module.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>Kernel</literal> defines the core kernel SPI, including bootstrap, configuration, POJO deployments, dependency, events, bean metadata and bean registry. It contains the following modules:
+ </para>
+ <itemizedlist>
+ <listitem><para><literal>Dependency</literal></para></listitem>
+ <listitem><para><literal>Kernel</literal></para></listitem>
+ <listitem><para><literal>AOP-MC-int</literal></para></listitem>
+ <listitem><para><literal>Spring-int</literal></para></listitem>
+ <listitem><para><literal>Guice-int</literal></para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>Managed</literal> represents two modules: <literal>managed</literal> and <literal>metatype</literal>. These modules define the base objects that define the management view of a component.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>MDR</literal> is the generic <emphasis>Metadata Repository</emphasis>. It handles scoped metadata lookups.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>Reflect</literal> is the integration point for manipulating class information at runtime.
+ </para>
+ </listitem>
+</itemizedlist>
+
+
+ <para>To configure the Microcontainer bootstrap you can use the <filename>JBOSS_HOME/server/<server_configuration>/conf/bootstrap.xml</filename> and <filename>JBOSS_HOME/server/<server_configuration>/conf/bootstrap/*.xml</filename> files where <emphasis><server_configuration></emphasis> represents the name of the server profile in use. The <filename>bootstrap.xml</filename> simply references Microcontainer deployment descriptors that should be loaded in the indicated order. The current <emphasis>default</emphasis> profile <filename>bootstrap.xml</filename> references are:
+ </para>
+ <itemizedlist>
+ <listitem><para><filename>stdio.xml</filename> - beans to define the Input/OutputStreams required for handling stdio </para></listitem>
+ <listitem><para><filename>vfs.xml</filename> - JBoss VFS caching beans</para></listitem>
+ <listitem><para><filename>classloader.xml</filename> - the root class loading beans for the peer class loading model</para></listitem>
+ <listitem><para><filename>aop.xml</filename> - JBoss AOP integration and AspectManager beans</para></listitem>
+ <listitem><para><filename>jmx.xml</filename> - JBoss JMX kernel initialization</para></listitem>
+ <listitem><para><filename>deployers.xml</filename> - Core deployers for -<filename>jboss-beans.xml</filename> and -service.xml</para></listitem>
+ <listitem><para><filename>profile.xml</filename> - full featured repository based profile service referenced by <filename>bootstrap.xml</filename></para></listitem>
+ <listitem><para><filename>security.xml</filename> - security bootstrap configuration</para></listitem>
+
+ </itemizedlist>
+
+<para>The main beans are:
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>ProfileService</emphasis> : This bean loads the deployments associated with the named server profile, <emphasis>default</emphasis>, <emphasis>all</emphasis> or the name that is passed to the server using the <code>-c</code> option. It's an extension of always looking to the filesystem <filename>server/name/conf/jboss-service.xml</filename>, <filename>server/name/deployers</filename> and <filename>server/name/deploy</filename> to load deployments.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>AspectManager</emphasis> : the AOP aspects
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>MainDeployer</emphasis> : An update of the JMX based MainDeployer from earlier versions to one based on the Microcontainer and the Virtual File System<!--, and Virtual Deployment Framework (VDF)-->. Deployer aspects are registered with the MainDeployer as an ordered list via inject of the deployers property.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>ServiceClassLoaderDeployer</emphasis> : Manages the class loading aspect of deployment.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>JARDeployer</emphasis> : This bean is a structural deployment aspect which handles the legacy nested deployment behavior of adding non-deployable jars to the current deployment classpath.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>FileStructure</emphasis> : this bean is a structural deployment aspect which recognizes well know deployment file types specified by FileManager and suffix.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>AspectDeployer</emphasis> : handles AOP descriptor deployments.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>BeanDeployer</emphasis> : this bean translates <filename>*-jboss-beans.xml</filename> into <classname>KernelDeployment</classname> for the descriptor beans.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>KernelDeploymentDeployer</emphasis> : Translates a <classname>KernelDeployment</classname> into the constituent <classname>BeanMetaData</classname> instances for the kernel beans.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>BeanMetaDataDeployer</emphasis> : Creates the kernel beans from the deployment <classname>BeanMetaData</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>SARDeployer</emphasis> : this bean is a port of the legacy JMX <classname>SARDeployer</classname><!-- to the Virtual Development Framework-->. It handles the legacy <filename>*-service.xml</filename> style of mbean deployment descriptors and maps this into a <classname>ServiceDeployment</classname> POJO.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>ServiceDeploymentDeployer</emphasis> : Translates the <classname>ServiceDeployment</classname> POJO into the constituent <classname>ServiceMetaData</classname> that represent the various mbeans.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>ServiceDeployer</emphasis> : creates the mbean services from deployment <classname>ServiceMetaData</classname> instances.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>JMXKernel</emphasis> : Manages the instantiation of a JMX kernel and <classname>MBeanServer</classname> in the jboss domain. It is used by the <classname>SARDeployer</classname>. It will be used by other management deployment aspects in the future to expose kernel beans via JMX.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>HDScanner</emphasis> : A bean that queries the profile service for changes in deploy directory contents and redeploys updated content, undeploys removed content, and add new deployment content to the profile service.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+</para>
+<note>
+<para>
+The location to configure a scanPeriod for the HDScanner has changed in the JBoss Application Server 6 release. This setting is now located in JBOSS_HOME/server/$lt;server_configuration$gt;/conf/bootstrap/profile.xml:
+</para>
+<para>
+<programlisting>
+ <!-- The scan period in seconds -->
+ <bean name="ScanPeriod" class="org.jboss.profileservice.profile.metadata.plugin.ScanPeriod">
+ <property name="scanPeriod">5</property>
+ </bean>
+</programlisting>
+</para>
+<para>
+In previous releases this setting was located in:
+JBOSS_HOME/server/$lt;server_configuration$gt;/deploy/hdscanner-jboss-beans.xml
+</para>
+
+</note>
+</section>
+
+ <section id="Server_Structure">
+ <title>Server Structure</title>
+
+ <para>
+ The following example illustrates the distribution layout of <literal>jboss-6.1.0.Final</literal>:
+<screen>[user at localhost <JBoss_Home>]$ tree
+|-- copyright.txt
+|-- jar-versions.xml
+|-- LICENSE.txt
+|-- README.txt
+|-- bin
+| |-- native
+| | | --lib
+| | | --lib64
+|-- client
+|-- common
+| |-- lib
+| | |-- various jars common to all server configs
+|-- docs
+| |-- dtd
+| | |-- Java EE dtds
+| |-- examples
+| | |-- jca
+| | |-- jmx
+| | |-- netboot
+| | |-- transactions
+| | | |-- build.xml
+| | | |-- jbossts-tools.sar
+| | | |-- jbossxts.sar
+| | | |-- transaction-jboss-beans-for-jts.xml
+| | | |-- README.txt (how to enable JTS)
+| | |-- licenses
+| | | |-- associated licenses for the distribution
+| | |-- varia
+| | |-- deployment-service
+| | |-- derby-plugin.jar
+| | |-- threaddump.war
+| |-- schema
+| | |-- Java EE schemas
+|-- lib
+| |-- concurrent.jar
+| |-- dom4j.jar
+| |-- endorsed
+| | |-- activation.jar
+| | |-- jboss-jaxb-api_2.2_spec.jar
+| | |-- jbossws-cxf-factories.jar
+| | |-- jboss-annotations-api_1.1_spec.jar
+| | |-- jboss-jaxws-api_2.2_spec.jar
+| | |-- stax-api.jar
+| |-- getopt.jar
+| |-- javassist.jar
+| |-- javax.inject.jar
+| |-- jaxb-impl.jar
+| |-- jaxb-xjc.jar
+| |-- jboss-aop-*.jar
+| |-- jboss-bootstrap-*jar
+| |-- jboss-classloader.jar
+| |-- jboss-classloading-*.jar
+| |-- jboss-classpool.jar
+| |-- jboss-classpool-*.jar
+| |-- jboss-common-core.jar
+| |-- jboss-dependency.jar
+| |-- jboss-deployers-*.jar
+| |-- jboss-j2se.jar
+| |-- jboss-jmx-*.jar
+| |-- jboss-kernel.jar
+| |-- jboss-logging.jar
+| |-- jboss-logmanager.jar
+| |-- jboss-main.jar
+| |-- jboss-managed.jar
+| |-- jboss-mbeanserver.jar
+| |-- jboss-mbeans.jar
+| |-- jboss-mdr.jar
+| |-- jboss-metatype.jar
+| |-- jboss-profileservice-*.jar
+| |-- jboss-reflect.jar
+| |-- jboss-security-spi.jar
+| |-- jboss-stdio.jar
+| |-- jbosssx.jar
+| |-- jbosssx-server.jar
+| |-- jboss-system.jar
+| |-- jboss-system-jmx.jar
+| |-- jboss-vfs.jar
+| |-- jbossxb.jar
+| |-- scanning-impl.jar
+| |-- scanning-plugins.jar
+| |-- scanning-spi.jar
+| |-- trove.jar
+| |-- wstx-lgpl.jar
+| |-- xercesImpl.jar
+| |-- xml-resolver.jar
+|-- server
+|-- all
+|-- default
+|-- jbossweb-standalone
+|-- minimal
+|-- standard
+|</screen>
+
+</para>
+</section>
+
+ <!-- Embedded sections
+
+ <xi:include href="Server_Configurations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Start_Stop_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ end embedded sections -->
+ <section id="Server Configuration Directory Structure">
+ <title>Server Configuration Directory Structure</title>
+
+<para>
+ Located within the <literal><JBOSS_HOME>/server</literal> directory, you will find five subdirectories for each pre-configured server configurations:
+ <literal>minimal</literal>, <literal>default</literal>, <literal>standard</literal>, <literal>all</literal> and <literal>jbossweb-standalone</literal>. Each of these configurations provide a different set of services.
+</para>
+<para>
+ <variablelist>
+ <varlistentry>
+ <term>minimal</term>
+ <listitem>
+ <para>
+ has a minimal configuration—the bare minimum services required to start JBoss. It starts the logging service, a JNDI server and a URL deployment scanner to find new deployments. This is what you would use if you want to use JBoss to start your own services without any other Java EE 6 technologies. This is just the bare server. There is no web container, no EJB or JMS support.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>default</term>
+ <listitem>
+ <para>
+ is a base server profile containing a default set of services. It does not include the the IIOP service or any of the clustering services.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>all</term>
+ <listitem>
+ <para>
+ starts all the available services. This includes the RMI/IIOP and clustering services.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>standard</term>
+ <listitem>
+ <para>
+ is the Java EE 6 Web Profile certified configuration of services.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>jbossweb-standalone</term>
+ <listitem>
+ <para>
+ is a lightweight web container profile.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+</para>
+<para>
+ 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/<server_configuration>/deployers/</filename> directory and also the services deployments in the <filename class="directory"><JBOSS_HOME>/server/<server_configuration>/deploy</filename> directory.
+</para>
+<note>
+ <para>
+ The <emphasis role="bold">default</emphasis> configuration is started unless an alternate configuration is specified.
+ </para>
+ <para>
+ To start the server using an alternate configuration refer to <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/>.
+ </para>
+</note>
+
+ <para>
+ The directory server configuration you’re using is effectively the server root while JBoss Application Server 6 is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server configuration directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
+ </para>
+ <para>
+ <table id="Server_Configuration_Directory_Structure_table">
+ <title>Server Configuration Directory Structure</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="1*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ Directory
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <filename class="directory">conf</filename>
+ </entry>
+ <entry>
+ 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>
+ <entry>
+ <filename class="directory">data</filename>
+ </entry>
+ <entry>
+ The <filename class="directory">data</filename> directory is available for use by services that want to store content in the file system. It holds persistent data for services intended to survive a server restart. Serveral JBoss services, such as the embedded Hypersonic database instance, store data here.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <filename class="directory">deploy</filename>
+ </entry>
+ <entry>
+ The <filename class="directory">deploy</filename> directory contains the hot-deployable services (those which can be added to or removed from the running server). It also contains applications for the current server configuration. You deploy your application code by placing application packages (JAR, WAR and EAR files) in the <filename class="directory">deploy</filename> directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <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. 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>
+ <entry>
+ <filename class="directory">log</filename>
+ </entry>
+ <entry>
+ This is where the log files are written.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <filename class="directory">tmp</filename>
+ </entry>
+ <entry>
+ The <filename class="directory">tmp</filename> directory is used for temporary storage by JBoss services. The deployer, for example, expands application archives in this directory.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <filename class="directory">work</filename>
+ </entry>
+ <entry>
+ This directory is used by Tomcat for compilation of JSPs.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+</section>
+<section id="The_default_Server_Configuration_File_Set">
+ <title>The "default" Server Configuration File Set</title>
+
+ <section id="The_default_Server_Configuration_File_Set-Contents_of_conf_directory">
+ <title>Contents of "conf" directory</title>
+ <para>
+ The files in the <literal>conf</literal> directory are explained in the following table.
+ </para>
+ <para>
+ <table id="Contents_of_conf_directory-Contents_of_conf_directory">
+ <title>Contents of "conf" directory</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>bootstrap.xml</literal>
+ </entry>
+ <entry>
+ 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> 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>
+ The <literal>jndi.properties</literal> file specifies the JNDI <literal>InitialContext</literal> properties that are used within the JBoss server when an <literal>InitialContext</literal> is created using the no-arg constructor.
+ </entry>
+ </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>
+ This file configures the Apache log4j framework category priorities and appenders used by the JBoss server code.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>login-config.xml</literal>
+ </entry>
+ <entry>
+ This file contains sample server side authentication configurations that are applicable when using JAAS based security.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>props/*</literal>
+ </entry>
+ <entry>
+ The <literal>props</literal> directory contains the users and roles property files for the <literal>jmx-console</literal>.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>standardjboss.xml</literal>
+ </entry>
+ <entry>
+ This file provides the default container configurations.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>standardjbosscmp-jdbc.xml</literal>
+ </entry>
+ <entry>
+ This file provides a default configuration file for the JBoss CMP engine.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>xmdesc/*-mbean.xml</literal>
+ </entry>
+ <entry>
+ The <literal>xmdesc</literal> directory contains XMBean descriptors for several services configured in the <literal>jboss-service.xml</literal> file.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+
+ <section id="The_default_Server_Configuration_File_Set-Contents_of_deployers_directory">
+ <title>Contents of "deployers" directory</title>
+ <para>
+ The files in the <literal>deployers</literal> directory are explained in the following table.
+ </para>
+ <para>
+ <table id="Contents_of_deployers_directory_table1">
+ <title>Contents of "deployers" directory</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>alias-deployers-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Deployers that know how to handle The know how to handle <alias> in <deployment> as true controller context.
+ Meaning they will only get active/installed when their original is installed.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>bsh.deployer</literal>
+ </entry>
+ <entry>
+ This file configures the bean shell deployer, which deploys bean shell scripts as JBoss mbean services.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>clustering-deployer-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Clustering-related deployers which add dependencies on needed clustering services to clustered EJB3, EJB2 beans and to distributable web applications.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>dependency-deployers-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Deployers for aliases.txt, jboss-dependency.xml jboss-depedency.xml adds generic dependency on whatever. aliases.txt adds human-readable name for deployments, e.g. vfszip://home/blah/.../jboss-5.0.0.GA/server/default/deploy/some-long-name.ear aliased to ales-app.ear.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>directory-deployer-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Adds legacy behavior for directories, handling its children as possible deployments.
+ e.g. .sar's lib directory to treat its .jar files as deployments
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ear-deployer-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ JavaEE 5 enterprise application related deployers
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb-deployer-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Legacy JavaEE 1.4 ejb jar related deployers
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb3.deployer</literal>
+ </entry>
+ <entry>
+ This is a deployer that supports JavaEE 5 ejb3, JPA, and application client deployments, .
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>hibernate-deployer-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Deployers for Hibernate -hibernate.xml descriptors, which are similar to Hibernate's .cfg.xml files.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jboss-aop-jboss5.deployer</literal>
+ </entry>
+ <entry>
+ JBossAspectLibrary and base aspects. Why is this in deployers, dependencies?
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jboss-jca.deployer</literal>
+ </entry>
+ <entry>
+ <literal>jboss-jca.deployer</literal> description
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <literal>jbossweb.deployer</literal>
+ </entry>
+ <entry>
+ The JavaEE 5 servlet, JSF, JSP deployers.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jbossws.deployer</literal>
+ </entry>
+ <entry>
+ The JavaEE 5 webservices endpoint deployers.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jsr77-deployers-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Deployers for creating the JSR77 MBeans from the JavaEE components.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>metadata-deployer-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Deployers for processing the JavaEE metadata from xml, annotations.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>seam.deployer</literal>
+ </entry>
+ <entry>
+ Deployer providing integration support for JBoss Seam applications.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>security-deployer-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ Deployers for configuration the security layers of the JavaEE components.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+
+ <section id="The_default_Server_Configuration_File_Set-Contents_of_deploy_directory">
+ <title>Contents of "deploy" directory</title>
+ <para>
+ The files in the <literal>deploy</literal> directory are explained in the following table.
+ </para>
+ <para>
+ <table id="Contents_of_deploy_directory_table">
+ <title>Contents of "deploy" directory</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>ROOT.war</literal>
+ </entry>
+ <entry>
+ <literal>ROOT.war</literal> establishes the '/' root
+ web application. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>cache-invalidation-service.xml</literal>
+ </entry>
+ <entry> This is a service that allows for custom
+ invalidation of the EJB caches via JMS
+ notifications. It is disabled by default. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb2-container-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>ejb2-container-jboss-beans.xml</literal>
+ UserTransaction integration bean for the EJB2
+ containers. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb2-timer-service.xml</literal>
+ </entry>
+ <entry>
+ <literal>ejb2-timer-service.xml</literal> contains
+ the ejb timer service beans. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb3-connectors-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>ejb3-connectors-jboss-beans.xml</literal>
+ EJB3 remoting transport beans. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb3-container-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>ejb3-container-jboss-beans.xml</literal>
+ UserTransaction integration bean for the EJB3
+ containers. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb3-interceptors-aop.xml</literal>
+ </entry>
+ <entry>
+ <literal>ejb3-interceptors-aop.xml</literal> defines
+ the EJB3 container aspects. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb3-timer-service.xml</literal>
+ </entry>
+ <entry>
+ <literal>ejb3-timer-service.xml</literal> an
+ alternate quartz based timer service </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>hdscanner-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>hdscanner-jboss-beans.xml</literal> the
+ deploy directory hot deployment scanning bean
+ </entry>
+ </row>
+ <row>
+ <entry>hsqldb-ds.xml</entry>
+ <entry>configures the Hypersonic embedded database
+ service configuration file. It sets up the embedded
+ database and related connection factories. </entry>
+ </row>
+ <row>
+ <entry>http-invoker.sar</entry>
+ <entry>contains the detached invoker that supports RMI
+ over HTTP. It also contains the proxy bindings for
+ accessing JNDI over HTTP. </entry>
+ </row>
+ <row>
+ <entry>jboss-local-jdbc.rar</entry>
+ <entry>is a JCA resource adaptor that implements the JCA
+ <literal>ManagedConnectionFactory</literal>
+ interface for JDBC drivers that support the
+ <literal>DataSource</literal> interface but not
+ JCA. </entry>
+ </row>
+ <row>
+ <entry>jboss-xa-jdbc.rar</entry>
+ <entry>JCA resource adaptors for XA DataSources</entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jbossweb.sar</literal>
+ </entry>
+ <entry>an mbean service supporting TomcatDeployer with
+ web application deployment service
+ management.</entry>
+ </row>
+ <row>
+ <entry><literal>jbossws.sar</literal></entry>
+ <entry>provides JEE web services support. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jca-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>jca-jboss-beans.xml</literal> is the
+ application server implementation of the JCA
+ specification. It provides the connection management
+ facilities for integrating resource adaptors into
+ the JBoss server. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jms-ra.rar</literal>
+ </entry>
+ <entry>
+ <literal>jms-ra.rar</literal> JBoss JMS Resource
+ Adapter </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/connection-factories-service.xml</literal>
+ </entry>
+ <entry>configures the DLQ, ExpiryQueue JMS connection
+ factory</entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/destinations-service.xml</literal>
+ </entry>
+ <entry>The message persistence store service</entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/destinations-service.xml</literal>
+ </entry>
+ <entry>configures the DLQ, ExpiryQueue JMS destinations.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/jms-ds.xml</literal>
+ </entry>
+ <entry>
+ <literal>jms-ds.xml</literal> configures the
+ JMSProviderLoader and JmsXA inflow resource adaptor
+ connection factory binding. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/legacy-service.xml</literal>
+ </entry>
+ <entry>
+ <literal>legacy-service.xml</literal> configures the
+ JMSProviderLoader and JmsXA inflow resource adaptor
+ connection factory binding. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/messaging-jboss-beans.xml</literal>
+ </entry>
+ <entry> The <literal>messaging-jboss-beans.xml</literal>
+ file configures JMS security and management beans.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/messaging-service.xml</literal>
+ </entry>
+ <entry> The <literal>messaging-service.xml</literal>
+ file configures the core JBoss Messaging service.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>messaging/remoting-bisocket-service.xml</literal>
+ </entry>
+ <entry> The
+ <literal>remoting-bisocket-service.xml</literal>
+ configures the JMS remoting service layer. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jmx-console.war</literal>
+ </entry>
+ <entry> The <literal>jmx-console.war</literal> directory
+ provides the JMX Console. The JMX Console provides a
+ simple web interface for managing the MBean server.
+ </entry>
+</row>
+ <row>
+ <entry>
+ <literal>jmx-invoker-service.xml</literal>
+ </entry>
+ <entry>
+ <literal>jmx-invoker-service.xml</literal> is an
+ MBean service archive that exposes a subset of the
+ JMX <literal>MBeanServer</literal> interface methods
+ as an RMI interface to enable remote access to the
+ JMX core functionality. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jmx-remoting.sar</literal>
+ </entry>
+ <entry>
+ <literal>jmx-remoting.sar</literal> is a
+ javax.management.remote implementation providing
+ access to the JMX server. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>legacy-invokers-service.xml</literal>
+ </entry>
+ <entry>
+ <literal>legacy-invokers-service.xml</literal> the
+ legacy detached jmx invoker remoting services.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jsr-88-service.xml</literal>
+ </entry>
+ <entry>
+ <literal>jsr-88-service.xml</literal> provides the
+ JSR 88 remote deployment service. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>mail-ra.rar</literal>
+ </entry>
+ <entry>
+ <literal>mail-ra.rar</literal> is a resource adaptor
+ that provides a JavaMail connector. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>mail-service.xml</literal>
+ </entry>
+ <entry> The <literal>mail-service.xml</literal> file is
+ an MBean service descriptor that provides JavaMail
+ sessions for use inside the JBoss server. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>monitoring-service.xml</literal>
+ </entry>
+ <entry> The <literal>monitoring-service.xml</literal>
+ file configures alert monitors like the console
+ listener and email listener used by JMX
+ notifications. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>profileservice-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>profileservice-jboss-beans.xml</literal>
+ description </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>properties-service.xml</literal>
+ </entry>
+ <entry> The <literal>properties-service.xml</literal> file is an MBean service descriptor that allows for customization of the JavaBeans <literal>PropertyEditor</literal>s as well as the definition of system properties. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>quartz-ra.rar</literal>
+ </entry>
+ <entry>
+ <literal>quartz-ra.rar</literal> is a resource adaptor for inflow of Quartz events </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>remoting-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>remoting-jboss-beans.xml</literal>
+ contains the unified invokers based on JBoss
+ Remoting. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>scheduler-service.xml</literal>
+ </entry>
+ <entry> The <literal>scheduler-service.xml</literal> and
+ <literal>schedule-manager-service.xml</literal>
+ files are MBean service descriptors that provide a
+ scheduling type of service. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>security/security-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>security-jboss-beans.xml</literal> security
+ domain related beans. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>security/security-policies-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>security-policies-jboss-beans.xml</literal>
+ security authorization related beans for ejb and web
+ authorization. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>sqlexception-service.xml</literal>
+ </entry>
+ <entry> The <literal>sqlexception-service.xml</literal>
+ file is an MBean service descriptor for the handling
+ of vendor specific <literal>SQLException</literal>s.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>transaction-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>transaction-jboss-beans.xml</literal> JTA
+ transaction manager related beans. </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>transaction-service.xml</literal>
+ </entry>
+ <entry>
+ <literal>transaction-service.xml</literal>
+ ClientUserTransaction proxy service configuration.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>uuid-key-generator.sar</literal>
+ </entry>
+ <entry> The <literal>uuid-key-generator.sar</literal>
+ service provides a UUID-based key generation
+ facility. </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+
+</section>
+<section id="The_all_Server_Configuration_File_Set">
+ <title>The "all" Server Configuration File Set</title>
+ <para>
+ The "all" server configuration file set is located in the <filename class="directory"><JBoss_Home>/server/all</filename> directory. In addition to the services in the "default" set, the all configuration contains several other services in the <literal>conf/</literal> directory as shown below.
+ </para>
+ <para>
+ <table id="The_all_Server_Configuration_File_Set-Additional_Services_in_conf_directory_for_all_configuration">
+ <title>Additional Services in "conf" directory for "all" configuration</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>cluster-service.xml</literal>
+ </entry>
+ <entry>
+ This service configures clustering communication for most clustered services in JBoss.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>deploy-hasingleton-service.xml</literal>
+ </entry>
+ <entry>
+ This provides the HA singleton service, allowing JBoss to manage services that must be active on only one node of a cluster.
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <literal>httpha-invoker.sar</literal>
+ </entry>
+ <entry>
+ This service provides HTTP tunneling support for clustered environments.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>iiop-service.xml</literal>
+ </entry>
+ <entry>
+ This provides IIOP invocation support.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>juddi-service.sar</literal>
+ </entry>
+ <entry>
+ This service provides UDDI lookup services.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>snmp-adaptor.sar</literal>
+ </entry>
+ <entry>
+ This is a JMX to SNMP adaptor. It allows for the mapping of JMX notifications onto SNMP traps.
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+</section>
+<section id="EJB3_Services">
+ <title>EJB3 Services </title>
+ <para>
+ The following table explains the files providing ejb3 services.
+ </para>
+ <para>
+ <table id="EJB3_Services_-EJB3_Services">
+ <title>EJB3 Services</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>ejb3-interceptors-aop.xml</literal>
+ </entry>
+ <entry>
+ This service provides the AOP interceptor stack configurations for EJB3 bean types.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb3.deployer</literal>
+ </entry>
+ <entry>
+ This service deploys EJB3 applications into JBoss.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jboss-aop-jdk50.deployer</literal>
+ </entry>
+ <entry>
+ This is a Java 5 version of the AOP deployer. The AOP deployer configures the <literal>AspectManagerService</literal> and deploys JBoss AOP applications.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>jbossws.sar</literal>
+ </entry>
+ <entry>
+ This provides Java EE 5 web services support.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ <para>
+ Finally, in the EJB3 "all" configuration there are two additional services.
+ </para>
+ <para>
+ <table id="EJB3_Services_-Additional_Services_in_EJB3_all_Configuration">
+ <title>Additional Services in EJB3 "all" Configuration</title>
+ <tgroup cols="2">
+ <colspec colname="c1" colnum="1" colwidth="4*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ File
+ </entry>
+ <entry>
+ Description
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <literal>ejb3-clustered-sfsbcache-service.xml</literal>
+ </entry>
+ <entry>
+ This provides replication and failover for EJB3 stateful session beans.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>ejb3-entity-cache-service.xml</literal>
+ </entry>
+ <entry>
+ This provides a clustered cache for EJB3 entity beans.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+</section>
+
+ <section id="Hot Deployment of Services in JBoss Application Server 6">
+ <title>Hot-deployment of services in JBoss</title>
+ <para>
+ Hot-deployable services are those which can be added to or removed from the running server. These are placed in the <literal>JBOSS_DIST/jboss-as/server/<server_configuration>/deploy</literal> directory. Let’s have a look at a practical example of hot-deployment of services before we go on to look at server configuration issues in more detail.
+ </para>
+ </section>
+
+ <section id="Basic Configuration Topics">
+ <title>Basic Configuration Topics</title>
+ <para>
+ Now that we have examined the JBoss server, we will take a look at some of the main configuration files and what they are used for. All paths are relative to the server configuration directory (<filename class="directory">JBOSS_HOME/server/default</filename>, for example).
+ </para>
+ </section>
+ <section id="BootStrap Configuration">
+ <title>Bootstrap Configuration</title>
+ <para>The microcontainer bootstrap configuration is described by the <filename>conf/bootstrap.xml</filename> and the <filename>conf/bootstrap/*.xml</filename> it references. It's expected that the number of bootstrap beans will be reduced in the future. It's not expected that you would need to edit the bootstrap configuration files for a typical installation.</para>
+ </section>
+ <section id="Basic_Configuration_Issues-Core_Services">
+ <title>Legacy Core Services</title>
+ <para>
+ The legacy core services specified in the <filename>conf/jboss-service.xml</filename> file are started just after server starts up the microcontainer. If you have a look at this file in an editor you will see MBeans for various services including logging, security, JNDI, JNDIView etc. Try commenting out the entry for the <literal>JNDIView</literal> service.
+ </para>
+ <note>
+ <para>
+ Eventually this file will be dropped as the services are converted to microcontainer beans or mbeans that are deployed as deploy directory services.</para></note>
+ <para>
+ Note that because the mbeans definition had nested comments, we had to comment out the mbean in two sections, leaving the original comment as it was.
+ </para>
+<programlisting>
+<!-- Section 1 commented out
+<mbean code="org.jboss.naming.JNDIView"
+ name="jboss:service=JNDIView"
+ xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
+-->
+ <!-- The HANamingService service name -->
+<!-- Section two commented out
+ <attribute name="HANamingService">jboss:service=HAJNDI</attribute></mbean>
+-->
+
+</programlisting>
+ <para>
+ If you then restart JBoss, you will see that the <literal>JNDIView</literal> service no longer appears in the JMX Management Console (JMX Console) listing. In practice, you should rarely, if ever, need to modify this file, though there is nothing to stop you adding extra MBean entries in here if you want to. The alternative is to use a separate file in the <filename class="directory">deploy</filename> directory, which allows your service to be hot deployable.
+ </para>
+ </section>
+
+ <section id="Basic_Configuration_Issues-Logging_Service">
+ <title>Logging Service</title>
+ <para>
+ In JBoss <literal>log4j</literal> is used for logging. If you are not familiar with the <literal>log4j</literal> package and would like to use it in your applications, you can read more about it at the Jakarta web site (<ulink url="http://jakarta.apache.org/log4j/"></ulink>).
+ </para>
+ <para>
+ Logging is controlled from a central <filename>conf/jboss-log4j.xml</filename> file. This file defines a set of appenders specifying the log files, what categories of messages should go there, the message format and the level of filtering. By default, JBoss produces output to both the console and a log file (<filename>log/server.log</filename>).
+ </para>
+ <para>
+ There are 6 basic log levels used: <literal>TRACE</literal>, <literal>DEBUG</literal>, <literal>INFO</literal>, <literal>WARN</literal>, <literal>ERROR</literal> and <literal>FATAL</literal>. The logging threshold on the console is <literal>INFO</literal>, which means that you will see informational messages, warning messages and error messages on the console but not general debug messages. In contrast, there is no threshold set for the <filename>server.log</filename> file, so all generated logging messages will be logged there.
+ </para>
+ <para>
+ If things are going wrong and there doesn’t seem to be any useful information in the console, always check the <filename>server.log</filename> file to see if there are any debug messages which might help you to track down the problem. However, be aware that just because the logging threshold allows debug messages to be displayed, that doesn't mean that all of JBoss will produce detailed debug information for the log file. You will also have to boost the logging limits set for individual categories. Take the following category for example.
+ </para>
+<programlisting><!-- Limit JBoss categories to INFO -->
+<category name="org.jboss">
+ <priority value="<emphasis role="bold">INFO</emphasis>"/>
+</category>
+</programlisting>
+ <para>
+ This limits the level of logging to <literal>INFO</literal> for all JBoss classes, apart from those which have more specific overrides provided. If you were to change this to <literal>DEBUG</literal>, it would produce much more detailed logging output.
+ </para>
+ <para>
+ As another example, let’s say you wanted to set the output from the container-managed persistence engine to <literal>DEBUG</literal> level and to redirect it to a separate file, <filename>cmp.log</filename>, in order to analyze the generated SQL commands. You would add the following code to the <filename>conf/jboss-log4j.xml</filename> file:
+ </para>
+<programlisting><appender name="CMP" class="org.jboss.logging.appender.RollingFileAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="File" value="${jboss.server.home.dir}/log/cmp.log"/>
+ <param name="Append" value="false"/>
+ <param name="MaxFileSize" value="500KB"/>
+ <param name="MaxBackupIndex" value="1"/>
+
+ <layout class="org.apache.log4j.PatternLayout">
+ <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
+ </layout>
+</appender>
+
+<category name="org.jboss.ejb.plugins.cmp">
+ <priority value="DEBUG" />
+ <appender-ref ref="CMP"/>
+</category>
+</programlisting>
+ <para>
+ This creates a new file appender and specifies that it should be used by the logger (or category) for the package <literal>org.jboss.ejb.plugins.cmp</literal>.
+ </para>
+ <para>
+ The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to their filenames. Please note that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
+ </para>
+ </section>
+
+ <section id="Basic_Configuration_Issues-Security_Service">
+ <title>Security Service</title>
+ <para>
+ Refer to the <ulink url="http://docs.jboss.org/jbosssecurity/docs/6.0/security_guide/html/index.html">JBoss Application Server 6 Security Guide</ulink>.
+ </para>
+ </section>
+
+ <section id="Basic_Configuration_Issues-Additional_Services">
+ <title>Additional Services</title>
+ <para>
+ The non-core, hot-deployable services are added to the <filename class="directory">deploy</filename> directory. They can be either XML descriptor files, <filename>*-service.xml, *-jboss-beans.xml</filename>, MC <filename>.beans</filename> archive, or JBoss Service Archive (SAR) files. SARs contains an META-INF/jboss-service.xml descriptor and additional resources the service requires (e.g. classes, library JAR files or other archives), all packaged up into a single archive. Similarly, a <filename>.beans</filename> archive contains a META-INF/jboss-beans.xml and additional resources.
+ </para>
+ </section>
+
+</chapter>
+
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Server_Configurations.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -1,83 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.docbook.org/xml/4.4/docbookx.dtd">
-<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations">
-<title>Server Configurations</title>
-<para>
- 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 6 applications though.
-</para>
-<para>
- 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 five 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>jbossweb-standalone</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>
- <varlistentry>
- <term>minimal</term>
- <listitem>
- <para>
- has a minimal configuration—the bare minimum services required to start JBoss. It starts the logging service, a JNDI server and a URL deployment scanner to find new deployments. This is what you would use if you want to use JMX/JBoss to start your own services without any other Java EE 6 technologies. This is just the bare server. There is no web container, no EJB or JMS support.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>default</term>
- <listitem>
- <para>
- is a base server profile containing a default set of services. It does not include the the IIOP service or any of the clustering services.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>all</term>
- <listitem>
- <para>
- The all configuration starts all the available services. This includes the RMI/IIOP and clustering services, which are not loaded in the default configuration.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>standard</term>
- <listitem>
- <para>
- is the Java EE 6 Web Profile certified configuration of services.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>jbossweb-standalone</term>
- <listitem>
- <para>
- is a lightweight web container profile.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-</para>
-<para>
- 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.
-</para>
-<note>
+<chapter id="JBoss Application Server 6 - A Quick Tour">
+ <title>Server Configuration Directory Structure</title>
+ <section id="Server Configuration Directory Structure">
<para>
- The <emphasis role="bold">default</emphasis> configuration is the one used if you don’t specify another one when starting up the server.
+ The directory server configuration you’re using is effectively the server root while JBoss Application Server 6 is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server configuration directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
</para>
<para>
- To start the server using an alternate configuration refer to <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/>.
- </para>
-</note>
-<section id="Server_Configuration_Directory_Structure">
- <title>Server Configuration Directory Structure</title>
- <para>
- The directory server configuration you’re using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server configuration directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
- </para>
- <para>
<table id="Server_Configuration_Directory_Structure_table">
<title>Server Configuration Directory Structure</title>
<tgroup cols="2">
@@ -131,7 +61,7 @@
<filename class="directory">log</filename>
</entry>
<entry>
- This is where the log files are written. JBoss uses the Jakarta <literal>log4j</literal> package for logging and you can also use it directly in your own applications from within the server. This may be overridden through the <filename class="directory">conf/</filename><filename>jboss-log4j.xml</filename> configuration file.
+ This is where the log files are written.
</entry>
</row>
<row>
@@ -157,162 +87,7 @@
</section>
<section id="The_default_Server_Configuration_File_Set">
<title>The "default" Server Configuration File Set</title>
- <para>
- The "<literal>default</literal>" server configuration file set is located in the <literal><JBoss_Home>/server/default</literal> directory. The following example illustrates a truncated directory structure of the <literal>jboss-as-<release></literal> server configuration files:
-<screen>[user at localhost <JBoss_Home>]$ tree
-|-- bin
-|-- client
-|-- common
-| |-- lib
-| | |-- antlr.jar
-| | |-- ... many more jars
-|-- docs
-| |-- dtd
-| |-- examples
-| | |-- binding-manager
-| | | `-- sample-bindings.xml
-| | |-- jca
-| | |-- jms
-| | |-- jmx
-| | |-- netboot
-| | | `-- netboot.war
-| | `-- varia
-| | |-- deployment-service
-| | |-- derby-plugin.jar
-| | |-- entity-resolver-manager
-| | | `-- xmlresolver-service.xml
-| | `-- jboss-bindings.xml
-| `-- schema
-|-- lib
-| |-- commons-codec.jar
-| |-- commons-httpclient.jar
-| |-- commons-logging.jar
-| |-- concurrent.jar
-| |-- endorsed
-| | |-- serializer.jar
-| | |-- xalan.jar
-| | `-- xercesImpl.jar
-| |-- getopt.jar
-| |-- jboss-common.jar
-| |-- jboss-jmx.jar
-| |-- jboss-system.jar
-| |-- jboss-xml-binding.jar
-| `-- log4j-boot.jar
-`-- 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-service.xml
-| | |-- jbossjta-properties.xml
-| | |-- jndi.properties
-| | |-- login-config.xml
-| | |-- props
-| | | |-- jbossws-roles.properties
-| | | |-- jbossws-users.properties
-| | | |-- jmx-console-roles.properties
-| | | `-- jmx-console-users.properties
-| | |-- standardjboss.xml
-| | |-- standardjbosscmp-jdbc.xml
-| | `-- xmdesc
-| |-- deploy
-| |-- deploy-hasingleton
-| | `-- jms
-| |-- 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-service.xml
-| | |-- jbossjta-properties.xml
-| | |-- jndi.properties
-| | |-- login-config.xml
-| | |-- props
-| | | |-- jbossws-roles.properties
-| | | |-- jbossws-users.properties
-| | | |-- jmx-console-roles.properties
-| | | `-- jmx-console-users.properties
-| | |-- standardjboss.xml
-| | |-- standardjbosscmp-jdbc.xml
-| | `-- xmdesc
-| | |-- AttributePersistenceService-xmbean.xml
-| | |-- ClientUserTransaction-xmbean.xml
-| | |-- JNDIView-xmbean.xml
-| | |-- Log4jService-xmbean.xml
-| | |-- NamingBean-xmbean.xml
-| | |-- NamingService-xmbean.xml
-| | |-- TransactionManagerService-xmbean.xml
-| | |-- org.jboss.deployment.JARDeployer-xmbean.xml
-| | |-- org.jboss.deployment.MainDeployer-xmbean.xml
-| | `-- org.jboss.deployment.SARDeployer-xmbean.xml
-| |-- data
-| | |-- hypersonic
-| | |-- jboss.identity
-| | |-- tx-object-store
-| | `-- xmbean-attrs
-| |-- deploy
-| |-- lib
-| |-- log
-| | |-- boot.log
-| | |-- server.log
-| | `-- server.log.2008-08-09
-| |-- tmp
-| `-- work
-| `-- jboss.web
-| `-- 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/hdscanner-jboss-beans.xml
-|-- deployers/
-`-- lib
-|-- jboss-minimal.jar
-|-- jnpserver.jar
-`-- log4j.jar</screen>
-</para>
<section id="The_default_Server_Configuration_File_Set-Contents_of_conf_directory">
<title>Contents of "conf" directory</title>
<para>
@@ -1162,8 +937,6 @@
</table>
</para>
</section>
- <section>
- <title></title>
- </section>
</section>
+</chapter>
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Setting_JBOSS_HOME.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -8,7 +8,7 @@
<section id="setting_JBOSS_HOME_linux"><title>Setting the <command>JBOSS_HOME</command> variable in Linux.</title>
<para>
- Before you can run the JBoss Application Server, you need to ensure that you've configured the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file as follows. In this example the Application Server folder has beeen copied to the <filename>/usr/jboss/jboss-<release></filename> folder.
+ Before you can run the JBoss Application Server 6, you need to ensure that you've configured the JBOSS_HOME environment variable in your <filename>.bashrc</filename> file as follows. In this example the Application Server folder has been installed to the <filename>/usr/jboss</filename> folder.
The following is a <filename>.bashrc</filename> file used in this installation. Please ensure that your <filename>.bashrc</filename> file has a similar configuration.
<screen>[user at localhost ~]$ gedit .bashrc
@@ -24,10 +24,10 @@
export JAVA_HOME=/usr/jdk6
export PATH=$PATH:$JAVA_HOME/bin
-export ANT_HOME=/usr/ant/apache-ant-1.6.0
+export ANT_HOME=/usr/ant/apache-ant-1.7.1
export PATH=$PATH:$ANT_HOME/bin
-export JBOSS_HOME=/home/jboss-user/jboss-<release>
+export JBOSS_HOME=/home/jboss-user/jboss-6.1.0.Final;
export PATH=$PATH:$JBOSS_HOME/bin
</screen>
@@ -36,7 +36,7 @@
<screen>[user at localhost ~]$ source .bashrc
[user at localhost ~]$</screen>
- If no errors are displayed on your terminal, you are now ready to run your JBoss Application Server.
+ If no errors are displayed on your terminal, you are now ready to run your JBoss Application Server 6.
</para>
</section>
@@ -46,12 +46,12 @@
<itemizedlist>
<listitem>
<para>
- Create an environment variable called <literal>JBOSS_HOME</literal> that points to the JBoss Application Server installation directory, for example: <literal>C:\Program Files\JBoss\jboss-<release>\</literal>.
+ Create an environment variable called <literal>JBOSS_HOME</literal> that points to the JBoss Application Server 6 installation directory, for example: <literal>C:\Program Files\JBoss\jboss-6.1.0.Final\</literal>.
</para>
</listitem>
<listitem>
<para>
- In order to run JBoss Application Server from the command line, add the <literal>jboss-<release>\bin</literal> directory to your path, for example: <literal>C:\Program Files\JBoss\jboss-<release>\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
+ In order to run JBoss Application Server 6 from the command line, add the <literal>jboss-6.1.0.Final\bin</literal> directory to your path, for example: <literal>C:\Program Files\JBoss\jboss-6.1.0.Final\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
</para>
</listitem>
</itemizedlist>
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Start_Stop_Server.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -4,43 +4,54 @@
<title>Starting and Stopping the Server</title>
<section id="Starting_and_Stopping_the_Server-Start_the_Server">
<title>Start the Server</title>
- <para>
- Move to <filename class="directory">JBOSS_HOME/bin</filename> directory and execute the <literal>run.bat</literal> (for Windows) or <literal>run.sh</literal> (for Linux) script, as appropriate for your operating system.
+ <para>Move to <filename class="directory">JBOSS_HOME/bin</filename> directory and execute the <literal>run.bat</literal> (for Windows) or <literal>run.sh</literal> (for Linux) script, as appropriate for your operating system.
</para>
-<important><title>Remote connection to the JBoss AS server</title>
- <para>JBoss AS now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers properly. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <literal>-b</literal> option. To bind to all available interfaces and re-enable the legacy behaviour use <literal>-b 0.0.0.0</literal>. In any case, be aware you still need to secure your server properly.
+<important><title>Remote connection to the JBoss Application Server 6</title>
+ <para>JBoss Application Server 6 binds its services to localhost (127.0.0.1) by default instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons till proper configuration adjusts can be made to properly secure your server[s]. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <literal>-b</literal> option. To bind to all available interfaces and re-enable the legacy behaviour use <literal>-b 0.0.0.0</literal>.
</para>
</important>
<para>
- For more information including setting up multiple JBoss server instances on one machine and hosting multiple domains with JBoss, please refer to the <ulink url="http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta500/html-single/index.html">Administration and Configuration Guide</ulink>. Some examples on binding are shipped in <filename><JBOSS_HOME>/docs/examples/binding-manager/sample-bindings.xml</filename>.
+ On starting your server, your screen output should look like the following (accounting for installation directory differences) and should not contain error or exception messages:
</para>
-
<para>
- On starting your server, your screen output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
-</para>
-
-<programlisting>[user at mypc bin]$ ./run.sh
-=========================================================================
+<programlisting>[user at localhost bin]$ ./run.sh
+ =========================================================================
+ JBoss Bootstrap Environment
- JBoss Bootstrap Environment
+ JBOSS_HOME: /home/jboss-user/jboss-6.1.0.Final
- JBOSS_HOME: /home/user/jboss-as-version/jbossas
+ JAVA: /usr/jdk6/bin/java
- JAVA: java
+ JAVA_OPTS: -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
+ -Dprogram.name=run.sh -Djava.library.path=/home/jboss-user/jboss-6.1.0.Final/bin/native/lib64
- JAVA_OPTS: -Dprogram.name=run.sh -server -Xms256m -Xmx512m -Dsun.rmi.dgc.client.
-gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
+ CLASSPATH: /home/jboss-user/jboss-6.1.0.Final/bin/run.jar:/usr/jdk6/lib/tools.jar
+ =========================================================================
- CLASSPATH: /home/user/jboss-as-version/jbossas/bin/run.jar
+ 13:31:13,005 INFO [AbstractJBossASServerBase] Server Configuration:
-=========================================================================
+ JBOSS_HOME URL: file:/home/jboss-user/jboss-6.1.0.Final/
+ Bootstrap: $JBOSS_HOME/server/all/conf/bootstrap.xml
+ Common Base: $JBOSS_HOME/common/
+ Common Library: $JBOSS_HOME/common/lib/
+ Server Name: all
+ Server Base: $JBOSS_HOME/server/
+ Server Library: $JBOSS_HOME/server/all/lib/
+ Server Config: $JBOSS_HOME/server/all/conf/
+ Server Home: $JBOSS_HOME/server/all/
+ Server Data: $JBOSS_HOME/server/all/data
+ Server Log: $JBOSS_HOME/server/all/log/
+ Server Temp: $JBOSS_HOME/server/all/tmp
+ 13:31:13,031 INFO [AbstractServer] Starting: JBossAS [6.1.0.Final "Neo"]
+
</programlisting>
-
-<para>More options for the JBoss AS <literal>run</literal> script are discussed in <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/> below.</para>
+</para>
+<para>More options for the JBoss Application Server 6 <literal>run</literal> script are discussed in <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/> below.</para>
<note>
<para>
- Note that the <literal>default</literal> profile will be started when no option is specified.
+ The <literal>default</literal> profile is started when no option is specified.
</para>
</note>
</section>
@@ -48,14 +59,9 @@
<section id="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration">
<title>Start the Server With Alternate Configuration</title>
<para>
- Using <literal>run.sh</literal> without any arguments starts the server using the <literal>default</literal> server configuration file set. To start with an alternate configuration file set, pass the name of the server configuration file set [same as the name of the server configuration directory under <literal>JBOSS_HOME/jbossas/server</literal>] that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>all</literal> configuration file set you should specify:
+ To start with an alternate server configuration, whether it is provided in the JBoss Application Server 6 distribution or one you specifically created and customized, pass the name of the server configuration [same as the name of the server_configuration directory under <literal>JBOSS_HOME/jboss-6.1.0.Final/server</literal>] that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>all</literal> configuration file set you should specify:
</para>
-<programlisting>[bin]$ ./run.sh -c all
-...
-...
-...
-JBossAS [6.0.0.SNAPSHOT "Neo"] Started
-</programlisting>
+<programlisting>[bin]$ ./run.sh -c all</programlisting>
</section>
<section id="Starting_and_Stopping_the_Server-Using_run.sh">
@@ -116,8 +122,20 @@
<para>
Using the shutdown command requires a server configuration that contains the <literal>jmx-invoker-service.xml</literal> service. Hence you cannot use the shutdown command with the <literal>minimal</literal> configuration.
</para>
+
+<note>
+<para>
+A slight change to note as this behavior differs from previous JBoss Application Server releases.
+</para>
+
+<para>
+When running multiple JBoss Application Server instances using the Service Binding Manager specify the --host option for the remote host and the --port option to specify the port. You can open (on the remote server) the JBOSS_HOME/server/<italic>server_configuration</italic>/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and determine the correct port number to bind to. By default, the port number will be 1090 for "PortsDefaultBindings". For each other binding, add 100 respectively to the port number; e.g., Port 1190 for Ports01Bindings, Port 1290 for Ports02Bindings, Port 1390 for Ports03Bindings.
+<programlisting>
+% ./shutdown.sh --host=myremotemachine [ | myIP ] --port=1290 -S
+</programlisting>
+</para>
+</note>
</section>
-
<section id="Starting_and_Stopping_the_Server-Running_as_a_Service_under_Microsoft_Windows">
<title> Running as a Service under Microsoft Windows </title>
<para>
@@ -131,7 +149,7 @@
</para>
<screen>JBossInstall.bat <replaceable><depends></replaceable> [-auto | -manual]</screen>
<para>
- Where <replaceable><depends></replaceable> is the name of any service that the JBoss AS server depends on, such as the <literal>mysql</literal> database service.
+ Where <replaceable><depends></replaceable> is the name of any service that the JBoss Application Server 6 depends on such as the <literal>mysql</literal> database service.
</para>
<para>
Once the service is installed the server can be started by using the command <literal>net start JBoss</literal>, and stopped with the command <literal>net stop JBoss</literal>.
Modified: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Test_Your_Installation.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/Test_Your_Installation.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -4,31 +4,31 @@
<chapter id="Test_your_Installation">
<title>Test your Installation</title>
<para>
- After you have installed or built the JBoss Application Server, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. To test your installation, open the <filename>JBOSS_DIST/jboss-<release>/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Unix) script, as appropriate for your operating system.
+ After you have installed or built JBoss Application Server 6, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. To test your installation, open the <filename>JBOSS_HOME/jboss-6.1.0.Final/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Unix) script, as appropriate for your operating system.
</para>
<para>
Your output should look similar to the following (accounting for installation directory differences) and contain no error or exception messages:
</para>
- <screen>
- [samson at dhcp-1-150 bin]$ sh run.sh
+<para>
+ <programlisting>
+ [user at localhost bin]$ sh run.sh
=========================================================================
-
-
JBoss Bootstrap Environment
- JBOSS_HOME: /home/jboss-user/jboss-6.0.0.Final
+ JBOSS_HOME: /home/jboss-user/jboss-6.1.0.Final
JAVA: /usr/jdk6/bin/java
- JAVA_OPTS: -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 -Dprogram.name=run.sh -Djava.library.path=/home/jboss-user/jboss-6.0.0.Final/bin/native/lib64
+ JAVA_OPTS: -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
+ -Dprogram.name=run.sh -Djava.library.path=/home/jboss-user/jboss-6.1.0.Final/bin/native/lib64
- CLASSPATH: /home/jboss-user/jboss-6.0.0.Final/bin/run.jar:/usr/jdk6/lib/tools.jar
-
+ CLASSPATH: /home/jboss-user/jboss-6.1.0.Final/bin/run.jar:/usr/jdk6/lib/tools.jar
=========================================================================
19:55:07,131 INFO [AbstractJBossASServerBase] Server Configuration:
- JBOSS_HOME URL: file:/home/jboss-user/jboss-6.0.0.Final/
+ JBOSS_HOME URL: file:/home/jboss-user/jboss-6.1.0.Final/
Bootstrap: $JBOSS_HOME/server/default/conf/bootstrap.xml
Common Base: $JBOSS_HOME/common/
Common Library: $JBOSS_HOME/common/lib/
@@ -41,13 +41,14 @@
Server Log: $JBOSS_HOME/server/default/log/
Server Temp: $JBOSS_HOME/server/default/tmp/
- 19:55:07,133 INFO [AbstractServer] Starting: JBossAS [6.0.0.Final "Neo"]
+ 19:55:07,133 INFO [AbstractServer] Starting: JBossAS [6.1.0.Final "Neo"]
. . .output truncated
- 19:55:22,507 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.Final "Neo"] Started in 15s:370ms
+ 19:55:22,507 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.1.0.Final "Neo"] Started in 15s:370ms
- </screen>
+ </programlisting>
+</para>
<para>
Now open <literal>http://localhost:8080</literal> in your web browser. (Make sure you dont have anything else already on your machine using that port).<footnote><para>
Note that on some machines, the name localhost may not resolve properly and you may need to use the local loopback address 127.0.0.1 instead.</para></footnote> The contents of your page should look similar to the following: <xref linkend="Test_your_Installation-Test_your_Installation"/>.
@@ -63,6 +64,42 @@
</figure>
</para>
<para>
- You are now ready to use the JBoss Application Server. This landing page provides links to assist in managing your JBoss AS instance as well as many on-line resources.
+ You are now ready to use JBoss Application Server 6. This landing page provides links to assist in managing your JBoss Application Server 6 instance as well as many on-line resources.
</para>
+
+ <section id="Administration Console">
+ <title>Administration Console</title>
+ <para>
+ The Administration Console is easily accessible by pointing your browser at <ulink url="http://localhost:8080/admin-console"></ulink>. Additional management features have been added to the Administration Console provided in JBoss AS 6; specifically management of JMS Topics and Queues provided by the default message provider, HornetQ and the management of Infinispan cache managers and cache instances (seen in the 'all' config). Refer to the <ulink url="http://www.jboss.org/jbossas/docs/6-x/Core-Documentation/admin-console.html">JBoss AS Administration Console User Guide</ulink> for additional information.
+</para>
+</section>
+ <section id="The JMX Console">
+ <title>The JMX Console</title>
+ <para>
+ The JMX console remains available in AS 6 for convenience. When the JBoss Server is running, you can get a live view of the server by going to the JMX console application at <ulink url="http://localhost:8080/jmx-console"></ulink>. You should see something similar to <xref linkend="The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application" />.
+ </para>
+ <para>
+ The JMX Console is the JBoss Management Console which provides a raw view of the JMX MBeans which make up the server. They can provide a lot of information about the running server and allow you to modify its configuration, start and stop components and so on.
+ </para>
+ <para>
+h For example, find the <literal>service=JNDIView</literal> link and click on it. This particular MBean provides a service to allow you to view the structure of the JNDI namespaces within the server. Now find the operation called <literal>list</literal> near the bottom of the MBean view page and click the <literal>invoke</literal> button. The operation returns a view of the current names bound into the JNDI tree, which is very useful when you start deploying your own applications and want to know why you can’t resolve a particular EJB name.
+ </para>
+ <figure id="The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application">
+ <title>View of the JMX Management Console Web Application</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/JMXView.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ Look at some of the other MBeans and their listed operations; try changing some of the configuration attributes and see what happens. With a very few exceptions, none of the changes made through the console are persistent. The original configuration will be reloaded when you restart JBoss, so you can experiment freely without doing any permanent damage.
+ </para>
+ </section>
+ <section id="JBoss Web Services Console">
+ <title>JBoss Web Services Console</title>
+ <para>
+ The JBoss Web Services Console can be used to get runtime information about JBoss Web Services. This Console also provides convenient access to project-related information such as user documentation, community forums, and source code repositories. Simply point your brower at <ulink url="http://localhost:8080/jbossws"></ulink>
+</para>
+</section>
</chapter>
Deleted: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2011-08-30 19:03:19 UTC (rev 112171)
+++ projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2011-08-30 19:48:59 UTC (rev 112172)
@@ -1,277 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.docbook.org/xml/4.4/docbookx.dtd"
-[
-<!ELEMENT xi:include (xi:fallback?) >
-<!ATTLIST xi:include
-xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude"
-href CDATA #REQUIRED
-parse (xml|text) "xml"
-xpointer CDATA #IMPLIED
-encoding CDATA #IMPLIED
-accept CDATA #IMPLIED
-accept-charset CDATA #IMPLIED
-accept-language CDATA #IMPLIED >
-<!ELEMENT xi:fallback ANY >
-<!ATTLIST xi:fallback
-xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude" >
-<!ENTITY % local.preface.class "| xi:include" >
-<!ENTITY % local.part.class "| xi:include" >
-<!ENTITY % local.chapter.class "| xi:include" >
-<!ENTITY % local.divcomponent.mix "| xi:include" >
-<!ENTITY % local.para.char.mix "| xi:include" >
-<!ENTITY % local.info.class "| xi:include" >
-<!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED
-xmlns:xi CDATA #FIXED 'http://www.w3.org/2001/XInclude'" >
-
-]>
-
-<chapter id="The_JBoss_Server___A_Quick_Tour">
- <title>The JBoss Server - A Quick Tour</title>
-
-<section id="Server_Structure">
- <title>Server Structure</title>
- <para>
- Now that you’ve downloaded JBoss and have run the server for the first time, the next thing you will want to know is how the installation is laid out and what goes where. At first glance there seems to be a lot of stuff in there, and it’s not obvious what you need to look at and what you can safely ignore for the time being. To remedy that, we’ll explore the server directory structure, locations of the key configuration files, log files, deployment and so on. It’s worth familiarizing yourself with the layout at this stage as it will help you understand the JBoss service architecture so that you’ll be able to find your way around when it comes to deploying your own applications.
- </para>
-</section>
-
- <!-- Embedded sections -->
-
- <xi:include href="Server_Configurations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Start_Stop_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <!-- end embedded sections -->
-
- <section id="The_JBoss_Server___A_Quick_Tour-The_JMX_Console">
- <title>The JMX Console</title>
- <para>
- When the JBoss Server is running, you can get a live view of the server by going to the JMX console application at <ulink url="http://localhost:8080/jmx-console"></ulink>. You should see something similar to <xref linkend="The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application" />.
- </para>
- <para>
- The JMX Console is the JBoss Management Console which provides a raw view of the JMX MBeans which make up the server. They can provide a lot of information about the running server and allow you to modify its configuration, start and stop components and so on.
- </para>
- <para>
- For example, find the <literal>service=JNDIView</literal> link and click on it. This particular MBean provides a service to allow you to view the structure of the JNDI namespaces within the server. Now find the operation called <literal>list</literal> near the bottom of the MBean view page and click the <literal>invoke</literal> button. The operation returns a view of the current names bound into the JNDI tree, which is very useful when you start deploying your own applications and want to know why you can’t resolve a particular EJB name.
- </para>
- <figure id="The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application">
- <title>View of the JMX Management Console Web Application</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/jmx-console.png" />
- </imageobject>
- </mediaobject>
- </figure>
- <para>
- Look at some of the other MBeans and their listed operations; try changing some of the configuration attributes and see what happens. With a very few exceptions, none of the changes made through the console are persistent. The original configuration will be reloaded when you restart JBoss, so you can experiment freely without doing any permanent damage.
- </para>
- <note>
- <para>
- If you installed JBoss using the graphical installer, the JMX Console will prompt you for a username and password before you can access it. If you installed using other modes, you can still configure JMX Security manually. We will show you how to secure your console in <xref linkend="Basic_Configuration_Issues-Security_Service"/>.
- </para>
- </note>
- </section>
- <section id="The_JBoss_Server___A_Quick_Tour-Hot-deployment_of_services_in_JBoss">
- <title>Hot-deployment of services in JBoss</title>
- <para>
- Hot-deployable services are those which can be added to or removed from the running server. These are placed in the <literal>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</literal> directory. Let’s have a look at a practical example of hot-deployment of services in JBoss before we go on to look at server configuration issues in more detail.
- </para>
- <para>
- Start JBoss if it isn’t already running and take a look at the <literal>server/all/deploy</literal> directory. Remove the <literal>mail-service.xml</literal> file and watch the output from the server:
-<programlisting>13:10:05,235 INFO [MailService] Mail service 'java:/Mail' removed from JNDI</programlisting>
- </para>
- <para>
- Then replace the file and watch JBoss re-install the service: <programlisting>13:58:54,331 INFO [MailService] Mail Service bound to java:/Mail</programlisting>
- This is hot-deployment in action.
- </para>
- </section>
-
- <section id="The_JBoss_Server___A_Quick_Tour-Basic_Configuration_Issues">
- <title>Basic Configuration Issues</title>
- <para>
- Now that we have examined the JBoss server, we will take a look at some of the main configuration files and what they are used for. All paths are relative to the server configuration directory (<filename class="directory">server/default</filename>, for example).
- </para>
- <section id="The_JBoss_Server___A_Quick_Tour-Bootstrap_Configuration">
- <title>Bootstrap Configuration</title>
- <para>The microcontainer bootstrap configuration is described by the <filename>conf/bootstrap.xml</filename> and the <filename>conf/bootstrap/*.xml</filename> it references. It's expected that the number of bootstrap beans will be reduced in the future. It's not expected that you would need to edit the bootstrap configuration files for a typical installation.</para>
- </section>
- <section id="Basic_Configuration_Issues-Core_Services">
- <title>Legacy Core Services</title>
- <para>
- The legacy core services specified in the <filename>conf/jboss-service.xml</filename> file are started just after server starts up the microcontainer. If you have a look at this file in an editor you will see MBeans for various services including logging, security, JNDI, JNDIView etc. Try commenting out the entry for the <literal>JNDIView</literal> service.
- </para>
- <note>
- <para>
- Eventually this file will be dropped as the services are converted to microcontainer beans or mbeans that are deployed as deploy directory services.</para></note>
- <para>
- Note that because the mbeans definition had nested comments, we had to comment out the mbean in two sections, leaving the original comment as it was.
- </para>
-<programlisting>
-<!-- Section 1 commented out
-<mbean code="org.jboss.naming.JNDIView"
- name="jboss:service=JNDIView"
- xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
--->
- <!-- The HANamingService service name -->
-<!-- Section two commented out
- <attribute name="HANamingService">jboss:service=HAJNDI</attribute></mbean>
--->
-
-</programlisting>
- <para>
- If you then restart JBoss, you will see that the <literal>JNDIView</literal> service no longer appears in the JMX Management Console (JMX Console) listing. In practice, you should rarely, if ever, need to modify this file, though there is nothing to stop you adding extra MBean entries in here if you want to. The alternative is to use a separate file in the <filename class="directory">deploy</filename> directory, which allows your service to be hot deployable.
- </para>
- </section>
-
- <section id="Basic_Configuration_Issues-Logging_Service">
- <title>Logging Service</title>
- <para>
- In JBoss <literal>log4j</literal> is used for logging. If you are not familiar with the <literal>log4j</literal> package and would like to use it in your applications, you can read more about it at the Jakarta web site (<ulink url="http://jakarta.apache.org/log4j/"></ulink>).
- </para>
- <para>
- Logging is controlled from a central <filename>conf/jboss-log4j.xml</filename> file. This file defines a set of appenders specifying the log files, what categories of messages should go there, the message format and the level of filtering. By default, JBoss produces output to both the console and a log file (<filename>log/server.log</filename>).
- </para>
- <para>
- There are 6 basic log levels used: <literal>TRACE</literal>, <literal>DEBUG</literal>, <literal>INFO</literal>, <literal>WARN</literal>, <literal>ERROR</literal> and <literal>FATAL</literal>. The logging threshold on the console is <literal>INFO</literal>, which means that you will see informational messages, warning messages and error messages on the console but not general debug messages. In contrast, there is no threshold set for the <filename>server.log</filename> file, so all generated logging messages will be logged there.
- </para>
- <para>
- If things are going wrong and there doesn’t seem to be any useful information in the console, always check the <filename>server.log</filename> file to see if there are any debug messages which might help you to track down the problem. However, be aware that just because the logging threshold allows debug messages to be displayed, that doesn't mean that all of JBoss will produce detailed debug information for the log file. You will also have to boost the logging limits set for individual categories. Take the following category for example.
- </para>
-<programlisting><!-- Limit JBoss categories to INFO -->
-<category name="org.jboss">
- <priority value="<emphasis role="bold">INFO</emphasis>"/>
-</category>
-</programlisting>
- <para>
- This limits the level of logging to <literal>INFO</literal> for all JBoss classes, apart from those which have more specific overrides provided. If you were to change this to <literal>DEBUG</literal>, it would produce much more detailed logging output.
- </para>
- <para>
- As another example, let’s say you wanted to set the output from the container-managed persistence engine to <literal>DEBUG</literal> level and to redirect it to a separate file, <filename>cmp.log</filename>, in order to analyze the generated SQL commands. You would add the following code to the <filename>conf/jboss-log4j.xml</filename> file:
- </para>
-<programlisting><appender name="CMP" class="org.jboss.logging.appender.RollingFileAppender">
- <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
- <param name="File" value="${jboss.server.home.dir}/log/cmp.log"/>
- <param name="Append" value="false"/>
- <param name="MaxFileSize" value="500KB"/>
- <param name="MaxBackupIndex" value="1"/>
-
- <layout class="org.apache.log4j.PatternLayout">
- <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
- </layout>
-</appender>
-
-<category name="org.jboss.ejb.plugins.cmp">
- <priority value="DEBUG" />
- <appender-ref ref="CMP"/>
-</category>
-</programlisting>
- <para>
- This creates a new file appender and specifies that it should be used by the logger (or category) for the package <literal>org.jboss.ejb.plugins.cmp</literal>.
- </para>
- <para>
- The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to their filenames. Please note that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
- </para>
- </section>
-
- <section id="Basic_Configuration_Issues-Security_Service">
- <title>Security Service</title>
- <para>
- The security domain information is stored in the file <filename>conf/login-config.xml</filename> as a list of named security domains, each of which specifies a number of JAAS <footnote><para>
- The Java Authentication and Authorization Service. JBoss uses JAAS to provide pluggable authentication modules. You can use the ones that are provided or write your own if you have more specific requirements.
- </para>
- </footnote> login modules which are used for authentication purposes in that domain. When you want to use security in an application, you specify the name of the domain you want to use in the application’s JBoss-specific deployment descriptors, <filename>jboss.xml</filename> (used in defining jboss specific configurations for an application) and/or <filename>jboss-web.xml</filename> (used in defining jboss for a Web application. We'll quickly look at how to do this to secure the JMX Console application which ships with JBoss.
- </para>
- <para>
- Almost every aspect of the JBoss server can be controlled through the JMX Console, so it is important to make sure that, at the very least, the application is password protected. Otherwise, any remote user could completely control your server. To protect it, we will add a security domain to cover the application.
- <!--<footnote><para>
- If you installed JBoss using the Graphical Installer and set the JMX Security up, then you will not have to uncomment the sections, because they are already uncommented. Additionally, the admin password will be set up to whatever you had specified.
- </para>
- </footnote>-->
-
- This can be done in the <filename>jboss-web.xml</filename> file for the JMX Console, which can be found in <filename class="directory">deploy/jmx-console.war/WEB-INF/</filename> directory. Uncomment the <literal>security-domain</literal> in that file, as shown below.
- </para>
- <para>
-<programlisting><jboss-web>
- <security-domain>java:/jaas/jmx-console</security-domain>
-</jboss-web>
-</programlisting>
- </para>
- <para>
- This links the security domain to the web application, but it doesn't tell the web application what security policy to enforce, what URLs are we trying to protect, and who is allowed to access them. To configure this, go to the <filename>web.xml</filename> file in the same directory and uncomment the <literal>security-constraint</literal> that is already there. This security constraint will require a valid user name and password for a user in the <literal>JBossAdmin</literal> group.
- </para>
-<programlisting><!--
- A security constraint that restricts access to the HTML JMX console
- to users with the role JBossAdmin. Edit the roles to what you want and
- uncomment the WEB-INF/jboss-web.xml/security-domain element to enable
- secured access to the HTML JMX console.
--->
-<security-constraint>
- <web-resource-collection>
- <web-resource-name>HtmlAdaptor</web-resource-name>
- <description>
- An example security config that only allows users with the
- role JBossAdmin to access the HTML JMX console web application
- </description>
- <url-pattern>/*</url-pattern>
- <http-method>GET</http-method>
- <http-method>POST</http-method>
- </web-resource-collection>
- <auth-constraint>
- <role-name>JBossAdmin</role-name>
- </auth-constraint>
-</security-constraint>
-</programlisting>
- <para>
- That's great, but where do the user names and passwords come from? They come from the <literal>jmx-console</literal> security domain we linked the application to. We have provided the configuration for this in the <filename>conf/login-config.xml</filename>.
- </para>
- <para>
-<programlisting><application-policy name="jmx-console">
- <authentication>
- <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
- flag="required">
- <module-option name="usersProperties">
- props/jmx-console-users.properties
- </module-option>
- <module-option name="rolesProperties">
- props/jmx-console-roles.properties
- </module-option>
- </login-module>
- </authentication>
-</application-policy>
-</programlisting>
- </para>
- <para>
- This configuration uses a simple file based security policy. The configuration files are found in the <filename class="directory">conf/props</filename> directory of your server configuration. The usernames and passwords are stored in the <literal>conf/props/jmx-console-users.properties</literal> file and take the form "<literal>username=password</literal>". To assign a user to the <literal>JBossAdmin</literal> group add "<literal>username=JBossAdmin</literal>" to the <literal>jmx-console-roles.properties</literal> file (additional roles on that username can be added comma separated). The existing file creates an <literal>admin</literal> user with the password <literal>admin</literal>. For security, please either remove the user or change the password to a stronger one.
- </para>
- <para>
- JBoss will re-deploy the JMX Console whenever you update its <filename>web.xml</filename>. You can check the server console to verify that JBoss has seen your changes. If you have configured everything correctly and re-deployed the application, the next time you try to access the JMX Console, it will ask you for a name and password. <footnote><para>
- Since the username and password are session variables in the web browser you may need to restart your browser to use the login dialog window.
- </para>
- </footnote>
- </para>
- <para>
- The JMX Console isn't the only web based management interface to JBoss. There is also the Web Console. Although it's a Java applet, the corresponding web application can be secured in the same way as the JMX Console. The Web Console is in the file <filename>deploy/management/console-mgr.sar/web-console.war.</filename>. The only difference is that the Web Console is provided as a simple WAR file instead of using the exploded directory structure that the JMX Console did. The only real difference between the two is that editing the files inside the WAR file is a bit more cumbersome.
- </para>
- </section>
-
- <section id="Basic_Configuration_Issues-Additional_Services">
- <title>Additional Services</title>
- <para>
- The non-core, hot-deployable services are added to the <filename class="directory">deploy</filename> directory. They can be either XML descriptor files, <filename>*-service.xml, *-jboss-beans.xml</filename>, MC <filename>.beans</filename> archive, or JBoss Service Archive (SAR) files. SARs contains an META-INF/jboss-service.xml descriptor and additional resources the service requires (e.g. classes, library JAR files or other archives), all packaged up into a single archive. Similarly, a <filename>.beans</filename> archive contains a META-INF/jboss-beans.xml and additional resources.
- </para>
- <para>
- Detailed information on all these services can be found in the <emphasis>JBoss Application Server: Configuration Guide</emphasis>, which also provides comprehensive information on server internals and the implementation of services such as JTA and the J2EE Connector Architecture (JCA).
- </para>
- </section>
-
- </section>
-
- <!--<section id="The_JBoss_Server___A_Quick_Tour-The_Web_Container___Tomcat">
- <title>The Web Container - Tomcat</title>
- <para>
- JBoss Application Server comes with Tomcat as the default web container.
- </para>
- <para>
- </para>
- </section>-->
-</chapter>
-
Added: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/images/JMXView.png
===================================================================
(Binary files differ)
Property changes on: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/images/JMXView.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/images/microcontainer.png
===================================================================
(Binary files differ)
Property changes on: projects/docs/community/6/Installation_And_Getting_Started_Guide/en-US/images/microcontainer.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
More information about the jboss-cvs-commits
mailing list