[jboss-cvs] JBossAS SVN: r92326 - projects/docs/enterprise/5.0/Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Aug 13 21:55:18 EDT 2009
Author: irooskov at redhat.com
Date: 2009-08-13 21:55:18 -0400 (Thu, 13 Aug 2009)
New Revision: 92326
Modified:
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
Log:
updated guide with changes
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2009-08-14 01:39:05 UTC (rev 92325)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2009-08-14 01:55:18 UTC (rev 92326)
@@ -15,7 +15,7 @@
</para>
<para>
The JBoss Enterprise Application Platform ships with six different server profiles. Within the <literal><JBoss_Home>/server</literal> directory, you will find six subdirectories:
- <literal>all</literal>, <literal>default</literal>, <literal>minimal</literal>, <literla>production</literal>, <literal>standard</literal> and <literal>web</literal> - one for each server profile. Each of these profiles 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.
+ <literal>all</literal>, <literal>default</literal>, <literal>minimal</literal>, <literla>production</literal>, <literal>standard</literal> and <literal>web</literal> - one for each server profile. Each of these profiles provide a different set of services. The <literal>production</literal> profile is the one used if you don’t specify another one when starting up the server.
</para>
<para>
<variablelist>
@@ -121,12 +121,21 @@
jboss-xa-jdbc.rar
</programlisting>
</para>
+<formalpara>
+ <title>Adding Your Own Profile</title>
+ <para>
+ You can add your own profiles too. The best way to do this is to copy an existing one that is closest to your needs and modify the contents. For example, if you weren’t interested in using messaging, you could copy the production directory, renaming it as myconfig, remove the messaging subdirectory from the deploy folder and then start JBoss with the new profile using the command:
+<programlisting>
+run -c myconfig
+</programlisting>
+ </para>
+</formalpara>
<note>
<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 <emphasis role="bold">production</emphasis> configuration is the one used if you don’t specify another one when starting up the server.
</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"/>.
+ To start the server using an alternate profile refer to <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/>.
</para>
</note>
<section id="Server_Configuration_Directory_Structure">
@@ -212,10 +221,10 @@
</table>
</para>
</section>
-<section id="The_default_Server_Configuration_File_Set">
- <title>The "default" Server Configuration File Set</title>
+<section id="The_default_Server_Profile_File_Set">
+ <title>The <literal>default</literal> Server Profile 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:
+ 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
@@ -371,13 +380,13 @@
</para>
<section id="The_default_Server_Configuration_File_Set-Contents_of_conf_directory">
- <title>Contents of "conf" directory</title>
+ <title>Contents of <literal>conf</literal> 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>
+ <title>Contents of <literal>conf</literal> directory</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="4*"/>
<colspec colname="c2" colnum="2" colwidth="4*"/>
@@ -394,6 +403,14 @@
<tbody>
<row>
<entry>
+ <literal>bindingservice.beans/*</literal>
+ </entry>
+ <entry>
+ This directory contains the configurations for various ports used by the server. See section [TODO: Point to the section which explains about port configurations] for details about port configurations.
+ </entry>
+ </row>
+ <row>
+ <entry>
<literal>bootstrap.xml</literal>
</entry>
<entry>
@@ -416,30 +433,30 @@
<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>
+ <!-- <row>
<entry>
<literal>jbossjta-properties.xml</literal>
</entry>
<entry>
<literal>jbossjta-properties.xml</literal> specifies the JBossTS transaction manager default properties.
</entry>
- </row>
- <row>
+ </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>
+ </row> -->
+ <!-- <row>
<entry>
<literal>java.policy</literal>
</entry>
<entry>
A placeholder java security policy file that simply grants all permissions.
</entry>
- </row>
+ </row> -->
<row>
<entry>
<literal>jboss-log4j.xml</literal>
@@ -450,6 +467,14 @@
</row>
<row>
<entry>
+ <literal>jbossts-properties.xml</literal>
+ </entry>
+ <entry>
+ This file provides the default configuration for the transaction manager.
+ </entry>
+ </row>
+ <row>
+ <entry>
<literal>login-config.xml</literal>
</entry>
<entry>
@@ -495,13 +520,13 @@
</section>
<section id="The_default_Server_Configuration_File_Set-Contents_of_deployers_directory">
- <title>Contents of "deployers" directory</title>
+ <title>Contents of <literal>deployers</literal> 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>
+ <title>Contents of <literal>deployers</literal> directory</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="4*"/>
<colspec colname="c2" colnum="2" colwidth="4*"/>
@@ -662,7 +687,7 @@
</section>
<section id="The_default_Server_Configuration_File_Set-Contents_of_deploy_directory">
- <title>Contents of "deploy" directory</title>
+ <title>Contents of <literal>deploy</literal> directory</title>
<para>
The files in the <literal>deploy</literal> directory are explained in the following table.
</para>
@@ -741,13 +766,20 @@
<literal>ejb3-interceptors-aop.xml</literal> defines
the EJB3 container aspects. </entry>
</row>
- <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>ejb3-timerservice-jboss-beans.xml</literal>
+ </entry>
+ <entry>
+ <literal>ejb3-timerservice-jboss-beans.xml</literal> configures the EJB3 TimerService </entry>
</row>
<row>
<entry>
@@ -764,12 +796,12 @@
service configuration file. It sets up the embedded
database and related connection factories. </entry>
</row>
- <row>
+ <!-- <row>
<entry><literal>http-invoker.sar</literal></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> -->
<row>
<entry><literal>jboss-local-jdbc.rar</literal></entry>
<entry>is a JCA resource adaptor that implements the JCA
@@ -782,14 +814,14 @@
<entry><literal>jboss-xa-jdbc.rar</literal></entry>
<entry>JCA resource adaptors for XA DataSources</entry>
</row>
- <row>
+ <!-- <row>
<entry>
<literal>jbossweb.sar</literal>
</entry>
<entry>an mbean service supporting TomcatDeployer with
web application deployment service
management.</entry>
- </row>
+ </row> -->
<row>
<entry><literal>jbossws.sar</literal></entry>
<entry>provides JEE web services support. </entry>
@@ -813,36 +845,29 @@
<literal>jms-ra.rar</literal> JBoss JMS Resource
Adapter </entry>
</row>
- <row>
+ <!-- <row>
<entry>
<literal>messaging/connection-factories-service.xml</literal>
</entry>
<entry>configures the DLQ, ExpiryQueue JMS connection
factory</entry>
- </row>
+ </row> -->
<row>
<entry>
<literal>messaging/destinations-service.xml</literal>
</entry>
- <entry>The message persistence store service</entry>
+ <entry>configures the default Dead Letter queue and the Expiry queue.</entry>
</row>
- <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>
+ </row> -->
+ <!-- <row>
<entry>
<literal>messaging/legacy-service.xml</literal>
</entry>
@@ -850,15 +875,15 @@
<literal>legacy-service.xml</literal> configures the
JMSProviderLoader and JmsXA inflow resource adaptor
connection factory binding. </entry>
- </row>
- <row>
+ </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> -->
<row>
<entry>
<literal>messaging/messaging-service.xml</literal>
@@ -867,24 +892,21 @@
file configures the core JBoss Messaging service.
</entry>
</row>
- <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> -->
<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> This is the <literal>jmx-console</literal> application which provides a simple web interface for managing the MBean server. By default, the jmx-console is available at http://localhost:8080/jmx-console</entry>
+ </row>
+ <!-- <row>
<entry>
<literal>jmx-invoker-service.xml</literal>
</entry>
@@ -894,8 +916,8 @@
JMX <literal>MBeanServer</literal> interface methods
as an RMI interface to enable remote access to the
JMX core functionality. </entry>
- </row>
- <row>
+ </row> -->
+ <!-- <row>
<entry>
<literal>jmx-remoting.sar</literal>
</entry>
@@ -903,7 +925,7 @@
<literal>jmx-remoting.sar</literal> is a
javax.management.remote implementation providing
access to the JMX server. </entry>
- </row>
+ </row> -->
<row>
<entry>
<literal>legacy-invokers-service.xml</literal>
@@ -937,7 +959,7 @@
an MBean service descriptor that provides JavaMail
sessions for use inside the JBoss server. </entry>
</row>
- <row>
+ <!-- <row>
<entry>
<literal>monitoring-service.xml</literal>
</entry>
@@ -945,14 +967,14 @@
file configures alert monitors like the console
listener and email listener used by JMX
notifications. </entry>
- </row>
+ </row> -->
<row>
<entry>
<literal>profileservice-jboss-beans.xml</literal>
</entry>
<entry>
<literal>profileservice-jboss-beans.xml</literal>
- description </entry>
+ configures the ProfileService, which is a generalization of the server configuration. </entry>
</row>
<row>
<entry>
@@ -985,15 +1007,15 @@
files are MBean service descriptors that provide a
scheduling type of service. </entry>
</row>
- <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>
+ </row> -->
+ <!-- <row>
<entry>
<literal>security/security-policies-jboss-beans.xml</literal>
</entry>
@@ -1001,7 +1023,7 @@
<literal>security-policies-jboss-beans.xml</literal>
security authorization related beans for ejb and web
authorization. </entry>
- </row>
+ </row> -->
<row>
<entry>
<literal>sqlexception-service.xml</literal>
@@ -1019,7 +1041,7 @@
<literal>transaction-jboss-beans.xml</literal> JTA
transaction manager related beans. </entry>
</row>
- <row>
+ <!-- <row>
<entry>
<literal>transaction-service.xml</literal>
</entry>
@@ -1027,7 +1049,7 @@
<literal>transaction-service.xml</literal>
ClientUserTransaction proxy service configuration.
</entry>
- </row>
+ </row> -->
<row>
<entry>
<literal>uuid-key-generator.sar</literal>
@@ -1044,13 +1066,13 @@
</section>
<section id="The_all_Server_Configuration_File_Set">
- <title>The "all" Server Configuration File Set</title>
+ <title>The <literal>all</literal> Server Profile 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.
+ The <literal>all</literal> server profile 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>
+ <table id="The_all_Server_Configuration_File_Set-Additional_Services_in_conf_directory_for_all_profile">
+ <title>Additional Services in <literal>conf</literal> directory for <literal>all</literal> profile</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="4*"/>
<colspec colname="c2" colnum="2" colwidth="4*"/>
@@ -1065,25 +1087,32 @@
</row>
</thead>
<tbody>
- <row>
+ <!-- <row>
<entry>
<literal>cluster-service.xml</literal>
</entry>
<entry>
This service configures clustering communication for most clustered services in JBoss.
</entry>
- </row>
+ </row> -->
<row>
<entry>
- <literal>deploy-hasingleton-service.xml</literal>
+ <literal>cluster/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>
+ cluster/farm-deployment-jboss-beans.xml
+ </entry>
+ <entry>
+ This provides the farm service, which allows for cluster-wide deployment and undeployment of services.
+ </entry>
+ </row>
+ <row>
+ <entry>
<literal>httpha-invoker.sar</literal>
</entry>
<entry>
@@ -1179,11 +1208,11 @@
</table>
</para>
<para>
- Finally, in the EJB3 "all" configuration there are two additional services.
+ Finally, in the EJB3 <literal>all</literal> profile 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>
+ <table id="EJB3_Services_-Additional_Services_in_EJB3_all_Profile">
+ <title>Additional Services in EJB3 <literal>all</literal> Profile</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="4*"/>
<colspec colname="c2" colnum="2" colwidth="4*"/>
More information about the jboss-cvs-commits
mailing list