[jboss-cvs] JBossAS SVN: r66721 - projects/docs/trunk/Server_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Nov 5 00:00:19 EST 2007
Author: skittoli at redhat.com
Date: 2007-11-05 00:00:19 -0500 (Mon, 05 Nov 2007)
New Revision: 66721
Modified:
projects/docs/trunk/Server_Configuration_Guide/en-US/Additional_Services.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Alternative_DBs.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Example_Installation.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Info.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Connectors.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Deploy.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/EJBs.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Messaging.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Naming.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Security.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/The_CMP_Engine.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/The_JMX_Microkernel.xml
projects/docs/trunk/Server_Configuration_Guide/en-US/Transactions.xml
Log:
minor changes to scg xml
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Additional_Services.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Additional_Services.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Additional_Services.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -758,12 +758,12 @@
</mbean>
</programlisting>
<para>
- As an example of a slightly more interesting listener, we'll look at the ScriptingListener. This listener listens for particular events and then executes a specified script when events are received. The script can be writen in any bean shell scripting language. The ScriptingListener accepts has the following parameters.
+ As an example of a slightly more interesting listener, we'll look at the ScriptingListener. This listener listens for particular events and then executes a specified script when events are received. The script can be writen in any different scripting languages. The ScriptingListener accepts the following parameters.
</para>
<itemizedlist>
<listitem>
<para>
- <emphasis role="bold">ScriptLanguage</emphasis>: This is the language the script is written in. This should be <literal>beanshell</literal>, unless you have loaded libraries for another beanshell compatible language.
+ <emphasis role="bold">ScriptLanguage</emphasis>: This is the language the script is written in. This should be <literal>beanshell</literal>, unless you have loaded libraries for another scripting language, like groovy for example.
</para>
</listitem>
<listitem>
@@ -838,7 +838,7 @@
The following example shows a service that depends on the Tomcat connectors. In fact, this is a very common pattern for services that want to hit a servlet inside tomcat. The service that depends on the Barrier in the example, is a simple memory monitor that creates a background thread and monitors the memory usage, emitting notifications when thresholds get crossed, but it could be anything. We have used this because it prints out to the console starting and stopping messages, so we know when the service gets activated/deactivated.
</para>
<programlisting><!--<?xml version="1.0" encoding="UTF-8"?>
-<!$Id: Additional_Services.xml,v 1.5 2007/06/27 08:34:43 skittoli Exp $ >-->
+ <!$Id: Additional_Services.xml,v 1.5 <date> <time> user Exp $ >-->
<server>
<!--
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Alternative_DBs.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Alternative_DBs.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Alternative_DBs.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -2,7 +2,7 @@
<title>Use Alternative Databases with JBoss AS</title>
<section>
<title>How to Use Alternative Databases</title>
- <para>JBoss utilizes the Hypersonic database as its default database. While this is good for development and prototyping, you or your company will probably require another database to be used for production. This chapter covers configuring JBoss AS to use alternative databases. We cover the procedures for all officially supported databases on the JBoss Enterprise Application Platform 4.2. They include: MySQL 5.0, PostgreSQL 8.1, Oracle 9i and 10g R2, DB2 7.2 and 8, Sybase ASE 12.5, as well as MS SQL 2005.
+ <para>JBoss utilizes the Hypersonic database as its default database. While this is good for development and prototyping, you or your company will probably require another database to be used for production. This chapter covers configuring JBoss AS to use alternative databases. We cover the procedures for all officially supported databases on the JBoss Application Server. They include: MySQL 5.0, PostgreSQL 8.1, Oracle 9i and 10g R2, DB2 7.2 and 8, Sybase ASE 12.5, as well as MS SQL 2005.
</para>
<para>Please note that in this chapter, we explain how to use alternative databases to support all services in JBoss AS. This includes all the system level services such as EJB and JMS. For individual applications (e.g., WAR or EAR) deployed in JBoss AS, you can still use any backend database by setting up the appropriate data source connection as described in <xref linkend="Connectors_on_JBoss-Configuring_JDBC_DataSources"/>.</para>
@@ -14,21 +14,17 @@
<section>
<title>Install JDBC Drivers</title>
- <para>For the JBoss Application Server and our applications to use the external database, we also need to install the database's JDBC driver. The JDBC driver is a JAR file, which you'll need to copy into your JBoss AS's <literal>jboss-as/server/production/lib</literal> directory. Replace <literal>production</literal> with the server configuration you are using if needed. This file is loaded when JBoss starts up. So if you have the JBoss AS running, you'll need to shut down and restart. The availability of JDBC drivers for different databases are as follows.</para>
+ <para>For the JBoss Application Server and our applications to use the external database, we also need to install the database's JDBC driver. The JDBC driver is a JAR file, which you'll need to copy into your JBoss AS's <literal>jboss-as/server/production/lib</literal> directory. Replace <literal>production</literal> with the server configuration you are using if needed. This file is loaded when JBoss starts up. So if you have the JBoss AS running, you'll need to shut down and restart. The availability of JDBC drivers for different databases are as follows.
+ </para>
+
<itemizedlist>
- <listitem><para>MySQL JDBC drivers can be obtained from <ulink url="http://dev.mysql.com/downloads/connector/j/5.0.html">http://dev.mysql.com/downloads/connector/j/5.0.html</ulink>. The download contains documentation, etc. for the JDBC connector, but you really only need the <literal>mysql-connector-java-5.0.4-bin.jar</literal> file to get MySQL to work with and be used by JBoss AS.</para></listitem>
-
- <listitem><para>PostgreSQL JDBC drivers can be obtained from: <ulink url="http://jdbc.postgresql.org/">http://jdbc.postgresql.org/</ulink>. For 8.2.3 version, we need the JDBC3 driver <literal>8.2-504 JDBC 3</literal>. The download is just the JDBC driver <literal>postgresql-8.2-504.jdbc3.jar</literal> file.</para></listitem>
-
- <listitem><para>Oracle thin JDBC drivers can be obtained from: <ulink url="http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html">http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html</ulink> for your Oracle DB versions.</para></listitem>
-
- <listitem><para>IBM DB2 JDBC drivers can be downloaded from the IBM web site <ulink url="http://www-306.ibm.com/software/data/db2/java/">http://www-306.ibm.com/software/data/db2/java/</ulink>.
+ <listitem><para>IBM DB2 JDBC drivers can be downloaded from the IBM web site <ulink url="http://www-306.ibm.com/software/data/db2/java/">http://www-306.ibm.com/software/data/db2/java/</ulink>.
</para></listitem>
<listitem><para>Sybase JDBC drivers can be downloaded from the Sybase jConnect product page <ulink url="http://www.sybase.com/products/allproductsa-z/softwaredeveloperkit/jconnect">http://www.sybase.com/products/allproductsa-z/softwaredeveloperkit/jconnect</ulink></para></listitem>
-<listitem><para>MS SQL Server JDBC drivers can be downloaded from the MSDN web site <ulink url="http://msdn.microsoft.com/data/jdbc/">http://msdn.microsoft.com/data/jdbc/</ulink>.</para></listitem>
+<listitem><para>MS SQL Server JDBC drivers can be downloaded from the MSDN web site <ulink url="http://msdn.microsoft.com/data/jdbc/">http://msdn.microsoft.com/data/jdbc/</ulink>.</para></listitem>
</itemizedlist>
<section><title>Special notes on Sybase</title>
@@ -41,27 +37,22 @@
Refer the sybase manuals for more options.
</para>
<formalpara><title>Enable JAVA services</title>
- <para>
- To use any java service like JMS, CMP, timers etc. configured with Sybase, java should be enabled on Sybase Adaptive Server.
-
- To do this use:
+ <para>
+ To use any java service like JMS, CMP, timers etc. configured with Sybase, java should be enabled on Sybase Adaptive Server. To do this use:
<screen><command>sp_configure "enable java",1</command></screen>
- Refer the sybase manuals for more information.
+ Refer to the sybase manuals for more information.
</para>
</formalpara>
<para>
If java is not enabled you might see this exception being thrown when you try to use any of the above services.
<screen>com.sybase.jdbc2.jdbc.SybSQLException: Cannot run this command because Java services are not enabled. A user with System Administrator (SA) role must reconfigure the system to enable Java</screen>
</para>
+
+
<formalpara><title>CMP Configuration</title>
<para>
- To use Container Managed Persistence for user defined Java objects with Sybase Adaptive Server Enterprise the java classes
- should be installed in the database.
- The system table 'sysxtypes' contains one row for each extended, Java-SQL datatype.This table is only used for
- Adaptive Servers enabled for Java.
-
- Install java classes using the installjava program.
+ To use Container Managed Persistence for user defined Java objects with Sybase Adaptive Server Enterprise the java classes should be installed in the database. The system table 'sysxtypes' contains one row for each extended, Java-SQL datatype. This table is only used for Adaptive Servers enabled for Java. Install java classes using the installjava program.
<screen><command>installjava -f <jar-file-name> -S<sybase-server> -U<super-user> -P<super-pass> -D<db-name></command></screen>
@@ -176,7 +167,7 @@
<section>
<title>Support Foreign Keys in CMP Services</title>
- <para>Next, we need to go change the <literal>jboss-as/server/production/conf/standardjbosscmp-jdbc.xml</literal> file so that the <literal>fk-constraint</literal> property is <literal>true</literal>. That is needed for all external databases we support on the JBoss Enterprise Application Platform. This file configures the database connection settings for the EJB2 CMP beans deployed in the JBoss AS.</para>
+ <para>Next, we need to go change the <literal>jboss-as/server/production/conf/standardjbosscmp-jdbc.xml</literal> file so that the <literal>fk-constraint</literal> property is <literal>true</literal>. That is needed for all external databases we support on the JBoss Application Server. This file configures the database connection settings for the EJB2 CMP beans deployed in the JBoss AS.</para>
<programlisting>
<![CDATA[
@@ -189,7 +180,7 @@
<section>
<title>Specify Database Dialect for Java Persistence API</title>
- <para>The Java Persistence API (JPA) entity manager can save EJB3 entity beans to any backend database. Hibernate provides the JPA implementation in JBoss AS. In order for Hibernate to work correctly with alternative databases, we recommend you configure the database dialect in the <varname>jboss-as/server/production/deploy/ejb3.deployer/META-INF/persistence.properties</varname> file. You need to un-comment the <varname>hibernate.dialect</varname> property and change its value to the following based on the database you setup.</para>
+ <para>The Java Persistence API (JPA) entity manager can save EJB3 entity beans to any backend database. Hibernate provides the JPA implementation in JBoss AS. Hibernate has a dialect auto-detection mechanism that works for most databases including the dialects for databases referenced in this appendix which are listed below. If a specific dialect is needed for alternative databases, you can configure the database dialect in the <varname>jboss-as/server/production/deploy/ejb3.deployer/META-INF/persistence.properties</varname> file. You need to un-comment the <varname>hibernate.dialect</varname> property and change its value to the following based on the database you setup. For a complete list of dialects, refer to the Hibernate Reference Guide, Chapter 3, Section 4.1 SQL Dialects.</para>
<itemizedlist>
<listitem><para>Oracle 9i: org.hibernate.dialect.Oracle9iDialect</para></listitem>
@@ -226,6 +217,19 @@
<section>
<title>The Easy Way</title>
+ <para>
+ The easy way is just to change the JNDI name for the external database to <literal>DefaultDS</literal>. Most JBoss services are hard-wired to use the <literal>DefaultDS</literal> by default. So, by changing the datasource name, we do not need to change the configuration for each service individually.
+ </para>
+ <para>
+ To change the JNDI name, just open the <literal>*-ds.xml</literal> file for your external database, and change the value of the <literal>jndi-name</literal> property to <literal>DefaultDS</literal>. For instance, in <literal>mysql-ds.xml</literal>, you'd change MySqlDS to DefaultDS and so on. You will need to remove the <literal>jboss-as/server/production/deploy/hsqldb-ds.xml</literal> file after you are done to avoid duplicated <literal>DefaultDS</literal> definition.
+ </para>
+ <para>
+ In the <literal>jms/*-jdbc2-service.xml</literal> file, you should also change the datasource name in the <literal>depends</literal> tag for the <literal>PersistenceManagers</literal> MBean to <literal>DefaultDS</literal>. For instance, for <literal>mysql-jdbc2-service.xml</literal> file, we change the <literal>MySqlDS</literal> to <literal>DefaultDS</literal>.
+
+ </para>
+
+
+
<para>The easy way is just to change the JNDI name for the external database to <literal>DefaultDS</literal>. Most JBoss services are hard-wired to use the <literal>DefaultDS</literal> by default. So, by changing the datasource name, we do not need to change the configuration for each service individually.</para>
<para>To change the JNDI name, just open the <literal>*-ds.xml</literal> file for your external database, and change the value of the <literal>jndi-name</literal> property to <literal>DefaultDS</literal>. For instance, in <literal>mysql-ds.xml</literal>, you'd change <literal>MySqlDS</literal> to <literal>DefaultDS</literal> and so on. You will need to remove the <literal>jboss-as/server/production/deploy/hsqldb-ds.xml</literal> file after you are done to avoid duplicated <literal>DefaultDS</literal> definition.</para>
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Example_Installation.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Example_Installation.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Example_Installation.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -5,7 +5,7 @@
<appendix id="Book_Example_Installation">
<title>Book Example Installation</title>
<para>
- The book comes with the source code for the examples discussed in the book. You can download the examples zip file from <ulink url="http://www.redhat.com/docs/manuals/jboss">http://www.redhat.com/docs/manuals/jboss</ulink>. Unzipping the example code archive creates a JBoss <literal>jboss4guide</literal> directory that contains an <literal>examples</literal> subdirectory. This is the <literal>examples</literal> directory referred to by the book.
+ The book comes with the source code for the examples discussed in the book. You can download the examples zip file from <ulink url="http://www.redhat.com/docs/manuals/jboss">http://www.redhat.com/docs/manuals/jboss</ulink>. Unzipping the example code archive creates a JBoss <literal>jboss<version>guide</literal> directory that contains an <literal>examples</literal> subdirectory. This is the <literal>examples</literal> directory referred to by the book.
</para>
<para>
The only customization needed before the examples may be used is to set the location of the JBoss server distribution. This may be done by editing the <literal>examples/build.xml</literal> file and changing the <literal>jboss.dist</literal> property value. This is shown in bold below:
@@ -15,25 +15,25 @@
<property file="ant.properties"/>
<!-- Override with your JBoss server bundle dist location -->
- <property name="jboss.dist" value="<emphasis role="bold">/tmp/jboss-4.2</emphasis>"/>
+ <property name="jboss.dist" value="<emphasis role="bold">/tmp/jboss-<version></emphasis>"/>
<property name="jboss.deploy.conf" value="default"/>
...
</programlisting>
<para>
or by creating an <literal>.ant.properties</literal> file in the examples directory that contains a definition for the <literal>jboss.dist</literal> property. For example:
</para>
-<programlisting>jboss.dist=/usr/local/jboss/jboss-4.2</programlisting>
+ <programlisting>jboss.dist=/usr/local/jboss/jboss-<version></programlisting>
<para>
Part of the verification process validates that the version you are running the examples against matches what the book examples were tested against. If you have a problem running the examples first look for the output of the validate target such as the following:
</para>
<programlisting>validate:
[java] ImplementationTitle: JBoss [Zion]
[java] ImplementationVendor: JBoss Inc.
- [java] ImplementationVersion: 4.2.0 (build: CVSTag=JBoss_4_2_0 date=200704070944)
+ [java] ImplementationVersion: <version> (build: CVSTag=JBoss_<version> date=200704070944)
[java] SpecificationTitle: JBoss
[java] SpecificationVendor: JBoss (http://www.jboss.org/)
- [java] SpecificationVersion: 4.2.0
- [java] JBoss version is: 4.2.0
+ [java] SpecificationVersion: <version>
+ [java] JBoss version is: <version>
</programlisting>
</appendix>
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Info.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Book_Info.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -28,10 +28,10 @@
</inlinemediaobject>
</publishername>
</publisher-->
- <copyright>
+ <!--<copyright>
<year>&YEAR;</year>
<holder>&FORMAL-RHI;</holder>
- </copyright>
+ </copyright>-->
<!--xi:include href="Common_Content/Boilerplate.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /-->
<xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Connectors.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Connectors.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Connectors.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -457,7 +457,7 @@
</para>
<programlisting>[examples]$ ant -Dchap=chap7 -Dex=1 run-example</programlisting>
<para>
- You'll see some output from the bean in the system console, but much more detailed logging output can be found in the <literal>server/production/log/server.log</literal> file. Don't worry if you see exceptions. They are just stack traces to highlight the call path into parts of the adaptor. To help understand the interaction between the adaptor and the JBoss JCA layer, we'll summarize the events seen in the log using a sequence diagram. <xref linkend="A_Sample_Skeleton_JCA_Resource_Adaptor-A_sequence_diagram_illustrating_the_key_interactions_between_the_JBossCX_framework_and_the_example_resource_adaptor_that_result_when_the_EchoBean_accesses_the_resource_adaptor_connection_factory." /> is a sequence diagram that summarizes the events that occur when the <literal>EchoBean</literal> accesses the resource adaptor connection factory from JNDI and creates a connection.
+ You'll see some output from the bean in the system console, but much more detailed logging output can be found in the <literal>server/default/log/server.log</literal> file. Don't worry if you see exceptions. They are just stack traces to highlight the call path into parts of the adaptor. To help understand the interaction between the adaptor and the JBoss JCA layer, we'll summarize the events seen in the log using a sequence diagram. <xref linkend="A_Sample_Skeleton_JCA_Resource_Adaptor-A_sequence_diagram_illustrating_the_key_interactions_between_the_JBossCX_framework_and_the_example_resource_adaptor_that_result_when_the_EchoBean_accesses_the_resource_adaptor_connection_factory." /> is a sequence diagram that summarizes the events that occur when the <literal>EchoBean</literal> accesses the resource adaptor connection factory from JNDI and creates a connection.
</para>
<figure id="A_Sample_Skeleton_JCA_Resource_Adaptor-A_sequence_diagram_illustrating_the_key_interactions_between_the_JBossCX_framework_and_the_example_resource_adaptor_that_result_when_the_EchoBean_accesses_the_resource_adaptor_connection_factory.">
<title>A sequence diagram illustrating the key interactions between the JBossCX framework and the example resource adaptor that result when the EchoBean accesses the resource adaptor connection factory.</title>
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Deploy.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Deploy.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Deploy.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -5,7 +5,7 @@
<chapter id="Deployment">
<title>Deployment</title>
- <para>Deploying applications on JBoss AS is very easy. You just need to copy the application into the jboss-as/server/production/deploy directory. You can replace default with different server profiles such as all or minimal or production. We will cover those later in this chapter. JBoss AS constantly scans the deploy directory to pick up new applications or any changes to existing applications. So, you can "hot deploy" application on the fly while JBoss AS is still running.</para>
+ <para>Deploying applications on JBoss AS is very easy. You just need to copy the application into the JBOSS_HOME/server/default/deploy directory. You can replace default with different server profiles such as all or minimal. We will cover those later in this chapter. JBoss AS constantly scans the deploy directory to pick up new applications or any changes to existing applications. So, you can "hot deploy" application on the fly while JBoss AS is still running.</para>
<section>
<title>Deployable Application Types</title>
@@ -38,88 +38,18 @@
<section>
<title>Standard Server Configurations</title>
- <para>The JBoss Enterprise Platform ships with four server configurations. You can choose which configuration to start by passing the -c parameter to the server startup script. For instance, command run.sh -c all would start the server in the all configuration. Each configuration is contained in a directory named jboss-as/server/[config name]/. You can look into each server configuration's directory to see the default services, applications, and libraries supported in the configuration.</para>
+ <para>The JBoss Application Server ships with three server configurations. You can choose which configuration to start by passing the -c parameter to the server startup script. For instance, command run.sh -c all would start the server in the all configuration. Each configuration is contained in a directory named <literal> JBOSS_HOME/server/[config name]/</literal>. You can look into each server configuration's directory to see the default services, applications, and libraries supported in the configuration.</para>
<itemizedlist>
- <listitem><para>The minimal configuration starts the core server container without any of the enterprise services. It is a good starting point if you want to build a customized version of JBoss AS that only contains the servers you need.</para></listitem>
+ <listitem><para>The minimal configuration starts the core server container without any of the enterprise services. It is a good starting point if you want to build a customized version of JBoss AS that only contains the services you need.</para></listitem>
<listitem><para>The default configuration is the mostly common used configuration for application developers. It supports the standard J2EE 1.4 and most of the Java EE 5.0 programming APIs (e.g., JSF and EJB3).</para></listitem>
<listitem><para>The all configuration is the default configuration with clustering support and other enterprise extensions.</para></listitem>
- <listitem><para>The production configuration is based on the all configuration but with key parameters pre-tuned for production deployment.</para></listitem>
+
</itemizedlist>
- <para>The detailed services and APIs supported in each of those configurations will be discussed throughout this book. In this section, we focus on the optimization we did for the production configuration.</para>
+ <para>The detailed services and APIs supported in each of those configurations will be discussed throughout this book.</para>
- <section>
- <title>The production Configuration</title>
-
- <para>To start the server in the production configuration, you can use the following command under Linux / Unix:</para>
-
- <programlisting>
-cd /path/to/jboss-as
-RUN_CONF=server/production/run.conf bin/run.sh -c production
- </programlisting>
-
- <para>Or, you can simply copy the jboss-as/server/production/run.conf file to jboss-as/bin directory and start the server with run.sh -c production command. Below is a list of optimizations we specifically did for the production configuration:</para>
-
- <itemizedlist>
- <listitem><para>In the jboss-as/server/production/run.conf file, we expanded the memory size of the server to 1.7 GB. We added the -server tag to JVM startup command on all platforms except for Darwin (Mac OS X). If the JVM is BEA jRockit, the -Xgc:gencon parameter is also added.</para></listitem>
- <listitem><para>We configured the key generation algorithm to use the database to generate HiLo keys in order to generate the correct keys in a cluster environment (see deploy/uuid-key-generator.sar/META-INF/jboss-service.xml).</para></listitem>
- <listitem><para>We removed the test JMS queues from deploy-hasingleton/jms/jbossmq-destinations-service.xml. Those queues are setup primarily for ease of application development. Production applications should configure their own JMS queues.</para></listitem>
- <listitem><para>We set the ScanPeriod parameter to 60000 in conf/jboss-minimal.xml and conf/jboss-service.xml, so that JBoss AS does not spend too much time constantly scanning the deploy directory for new or updated deployments.</para></listitem>
- <listitem><para>We removed the connection monitoring in deploy/jbossjca-service.xml. The connection monitoring feature helps catch unclosed connections that would otherwise cause leaks in the connection pools in development. However, it is a global point of contention that should be turned off (false) in production.</para></listitem>
- <listitem><para>Logging is a big contention point in many production applications. In the production configuration, we removed the console logging and increased the logging level to WARN and ERROR for most packages. Please see details in conf/jboss-log4j.xml.</para></listitem>
- </itemizedlist>
-
- </section>
-
- <section>
- <title>Further Tuning from the production Configuration</title>
-
- <para>In addition to the standard optimization in the production configuration, there are a couple of simple techniques you can use to improve the performance and stability of your server.</para>
-
- <para>The production configuration increases the JVM heap memory size to 1.7 GB. You should probably change it to fit your own server. For instance, if have a 64 bit server with several GBs of RAM, you can probably increase this value as long as you also use a 64 bit JVM. If your server has less than 2 GB RAM, you should decrease that value accordingly. In the production/run.conf file, the -Xmx and -Xms parameters specify the maximum and minimum heap sizes respectively. It is recommended that you set the -Xmx and -Xms to the same value to avoid dynamic re-sizing of the heap, which is a source of instability in many JVMs. You could also consider turing on parallel GC options if you are using the Sun JVM on a multi-core machine. The following is an example setup you might use a reference. Please see the Sun JVM documentation for more details on this startup parameters.</para>
-
- <programlisting>
-JAVA_OPTS="-Xms1740m -Xmx1740m -XX:PermSize=256m -XX:MaxPermSize=512
- -XX:+UseConcMarkSweepGC -XX:+CMSPermGenSweepingEnabled
- -XX:+CMSClassUnloadingEnabled"
- </programlisting>
-
- <para>In the embedded Tomcat module, you can turn off the development mode so that the server does not constantly monitor the changes in JSP files. To do that, edit the deploy/jboss-web.deployer/conf/web.xml file and add the development attribute to the JspServlet.</para>
-
- <programlisting>
-<![CDATA[
- <servlet>
- <servlet-name>jsp</servlet-name>
- <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
- ... ...
- <init-param>
- <param-name>development</param-name>
- <param-value>false</param-value>
- </init-param>
- ... ...
-]]>
- </programlisting>
-
- <para>In Tomcat, you could adjust the size of the thread pool. If you have multi-core CPUs or more than one CPUs on your server, it might be beneficial to increase the thread pool beyond the default 250. On the other hand, if you have a slow server, decreasing the thread pool will decrease the overhead on the server. The thread pool size can be adjusted via the deploy/jboss-web.deployer/server.xml file.</para>
-
- <programlisting>
-<![CDATA[
- ... ...
- <Connector port="8080" address="${jboss.bind.address}"
- maxThreads="250" maxHttpHeaderSize="8192"
- emptySessionPath="true" protocol="HTTP/1.1"
- enableLookups="false" redirectPort="8443" acceptCount="100"
- connectionTimeout="20000" disableUploadTimeout="true" />
- ... ...
-]]>
- </programlisting>
-
- <para>In addition, JBoss AS needs to use a relational database to store runtime data. In a production environment, you should use a production quality database to replace the embedded HSQL database. Please see <xref linkend="alternative_DBs"/> for more information on how to setup alternative databases for the JBoss AS.</para>
-
- </section>
-
- </section>
+</section>
</chapter>
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/EJBs.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/EJBs.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/EJBs.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -90,7 +90,7 @@
The configuration of the client side interceptors is done using the <literal>jboss.xml</literal><literal>client-interceptors</literal> element. When the <literal>ClientContainer</literal> invoke method is called it creates an untyped <literal>Invocation</literal> (<literal>org.jboss.invocation.Invocation</literal>) to encapsulate request. This is then passed through the interceptor chain. The last interceptor in the chain will be the transport handler that knows how to send the request to the server and obtain the reply, taking care of the transport specific details.
</para>
<para>
- As an example of the client interceptor configuration usage, consider the default stateless session bean configuration found in the <literal>server/production/standardjboss.xml</literal> descriptor. <xref linkend="The_EJB_Client_Side_View-The_client_interceptors_from_the_Standard_Stateless_SessionBean_configuration." /> shows the <literal>stateless-rmi-invoker</literal> client interceptors configuration referenced by the Standard Stateless SessionBean.
+ As an example of the client interceptor configuration usage, consider the default stateless session bean configuration found in the <literal>server/default/standardjboss.xml</literal> descriptor. <xref linkend="The_EJB_Client_Side_View-The_client_interceptors_from_the_Standard_Stateless_SessionBean_configuration." /> shows the <literal>stateless-rmi-invoker</literal> client interceptors configuration referenced by the Standard Stateless SessionBean.
</para>
<example id="The_EJB_Client_Side_View-The_client_interceptors_from_the_Standard_Stateless_SessionBean_configuration."><title>The client-interceptors from the Standard Stateless SessionBean configuration.</title>
<programlisting><invoker-proxy-binding>
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Messaging.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Messaging.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Messaging.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -9,15 +9,17 @@
The JMS API stands for Java Message Service Application Programming Interface, and it is used by applications to send asynchronous <emphasis>business-quality</emphasis> messages to other applications. In the messaging world, messages are not sent directly to other applications. Instead, messages are sent to destinations, known as queues or topics. Applications sending messages do not need to worry if the receiving applications are up and running, and conversely, receiving applications do not need to worry about the sending application's status. Both senders, and receivers only interact with the destinations.
</para>
<para>
- The JMS API is the standardized interface to a JMS provider, sometimes called a Message Oriented Middleware (MOM) system. JBoss comes with a JMS 1.1 compliant JMS provider called JBoss Messaging or JBossMQ. When you use the JMS API with JBoss, you are using the JBoss Messaging engine transparently. JBoss Messaging fully implements the JMS specification; therefore, the best JBoss Messaging user guide is the JMS specification. For more information about the JMS API please visit the JMS Tutorial or JMS Downloads & Specifications.
+ The JMS API is the standardized interface to a JMS provider, sometimes called a Message Oriented Middleware (MOM) system. JBoss comes with a JMS 1.1 compliant JMS provider called JBossMQ or JBossMQ. When you use the JMS API with JBoss, you are using the JBossMQ engine transparently. JBossMQ fully implements the JMS specification; therefore, the best JBossMQ user guide is the JMS specification. For more information about the JMS API please visit the JMS Tutorial or JMS Downloads & Specifications.
</para>
<para>
- This chapter focuses on the JBoss specific aspects of using JMS and message driven beans as well as the JBoss Messaging configuration and MBeans.
+ There is also the option of replacing JbossMQ with the newer and more performant JBoss Messaging provider. This is a standalone project/product that needs to be downloaded separately.
+
+ This chapter focuses on the JBoss specific aspects of using JMS and message driven beans as well as the JBossMQ configuration and MBeans.
</para>
<section id="Messaging_on_JBoss-JMS_Examples">
<title>JMS Examples</title>
<para>
- In this section we discuss the basics needed to use the JBoss JMS implementation. JMS leaves the details of accessing JMS connection factories and destinations as provider specific details. What you need to know to use the JBoss Messaging layer is:
+ In this section we discuss the basics needed to use the JBoss JMS implementation. JMS leaves the details of accessing JMS connection factories and destinations as provider specific details. What you need to know to use the JBossMQ layer is:
</para>
<itemizedlist>
<listitem>
@@ -899,7 +901,7 @@
<programlisting>[examples]$ ant -Dchap=chap6 -Dex=2 run-example
...
run-example2:
- [copy] Copying 1 file to /tmp/jboss-4.2.0/server/production/deploy
+ [copy] Copying 1 file to /tmp/jboss-4.2.0/server/default/deploy
[echo] Waiting 5 seconds for deploy...
[java] Begin SendRecvClient, now=1102900541558
[java] Begin sendRecvAsync
@@ -929,7 +931,7 @@
The corresponding JBoss server console output is:
</para>
<programlisting>19:15:40,232 INFO [EjbModule] Deploying TextMDB
- 19:15:41,498 INFO [EJBDeployer] Deployed: file:/private/tmp/jboss-4.2.0/server/production/deplo
+ 19:15:41,498 INFO [EJBDeployer] Deployed: file:/private/tmp/jboss-4.2.2.GA/server/default/deplo
y/chap6-ex2.jar
19:15:45,606 INFO [TextMDB] TextMDB.ctor, this=10775981
19:15:45,620 INFO [TextMDB] TextMDB.ctor, this=1792333
@@ -1007,7 +1009,7 @@
</section>
<section id="Messaging_on_JBoss-JBoss_Messaging_Overview">
- <title>JBoss Messaging Overview</title>
+ <title>JBossMQ Overview</title>
<para>
JBossMQ is composed of several services working together to provide JMS API level services to client applications. The services that make up the JBossMQ JMS implementation are introduced in this section.
</para>
@@ -1109,7 +1111,7 @@
</section>
<section id="Messaging_on_JBoss-JBoss_Messaging_Configuration_and_MBeans">
- <title>JBoss Messaging Configuration and MBeans</title>
+ <title>JBossMQ Configuration and MBeans</title>
<para>
This section defines the MBean services that correspond to the components introduced in the previous section along with their MBean attributes. The configuration and service files that make up the JBossMQ system include:
</para>
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Naming.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Naming.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Naming.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -431,8 +431,6 @@
| +- WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet.class
| +- WEB-INF/classes/org/jboss/invocation/http/servlet/NamingFactoryServlet.class
| +- WEB-INF/classes/org/jboss/invocation/http/servlet/ReadOnlyAccessFilter.class
-| +- WEB-INF/classes/roles.properties
-| +- WEB-INF/classes/users.properties
| +- WEB-INF/web.xml
| +- META-INF/MANIFEST.MF
+- META-INF/MANIFEST.MF
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Security.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Security.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Security.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -813,7 +813,7 @@
</para>
<programlisting>[examples]$ ant -Dchap=chap8 -Dex=1 run-example
run-example1:
-[copy] Copying 1 file to /tmp/jboss-4.2.0/server/production/deploy
+[copy] Copying 1 file to /tmp/jboss-<version>/server/default/deploy
[echo] Waiting for 5 seconds for deploy...
[java] [INFO,ExClient] Looking up EchoBean
[java] [INFO,ExClient] Created Echo
@@ -2366,7 +2366,7 @@
<programlisting>[examples]$ ant -Dchap=chap8 -Dex=2 run-example
...
run-example2:
- [copy] Copying 1 file to /tmp/jboss-4.2.0/server/production/deploy
+ [copy] Copying 1 file to /tmp/jboss-<version>/server/default/deploy
[echo] Waiting for 5 seconds for deploy...
[java] [INFO,ExClient] Login with username=jduke, password=theduke
[java] [INFO,ExClient] Looking up EchoBean2
@@ -2375,10 +2375,10 @@
</programlisting>
<programlisting>19:06:13,266 INFO [EjbModule] Deploying EchoBean2
19:06:13,482 INFO [JndiStore] Start, bound security/store
-19:06:13,486 INFO [SecurityConfig] Using JAAS AuthConfig: jar:file:/private/tmp/jboss-4.2.0/
-server/production/tmp/deploy/tmp23012chap8-ex2.jar-contents/chap8-ex2.sar!/META-INF/login-config
+19:06:13,486 INFO [SecurityConfig] Using JAAS AuthConfig: jar:file:/private/tmp/jboss-<version>/
+server/default/tmp/deploy/tmp23012chap8-ex2.jar-contents/chap8-ex2.sar!/META-INF/login-config
.xml
-19:06:13,654 INFO [EJBDeployer] Deployed: file:/private/tmp/jboss-4.2.0/server/production/deplo
+19:06:13,654 INFO [EJBDeployer] Deployed: file:/private/tmp/jboss-<version>/server/default/deplo
y/chap8-ex2.jar
</programlisting>
<para>
@@ -2793,7 +2793,7 @@
validate:
fail_if_not_valid:
init:
- [echo] Using jboss.dist=/home/samson/EnterprisePlatform-4.2.0.BETA/jboss-as
+ [echo] Using jboss.dist=/home/samson/EnterprisePlatform-<version>.BETA/jboss-as
compile:
build-chap:
build-all:
@@ -2893,7 +2893,7 @@
<programlisting>[examples]$ ant -Dchap=chap8 -Dex=3 run-example
...
run-example3:
-[copy] Copying 1 file to /tmp/jboss-4.2.0/server/production/deploy
+[copy] Copying 1 file to /tmp/jboss-<version>/server/default/deploy
[echo] Waiting for 5 seconds for deploy...
[java] Logging in using the 'srp' configuration
[java] Created Echo
@@ -3167,7 +3167,7 @@
<programlisting>[examples]$ ant -Dchap=chap8 -Dex=4b run-example
...
run-example4b:
- [copy] Copying 1 file to /tmp/jboss-4.2.0/server/production/deploy
+ [copy] Copying 1 file to /tmp/jboss-<version>/server/default/deploy
[echo] Waiting for 15 seconds for deploy...
...
[java] Exception in thread "main" java.rmi.ConnectIOException: error during JRMP connect
@@ -3182,7 +3182,7 @@
<programlisting>[examples]$ ant -Dchap=chap8 -Dex=4 run-example
...
run-example4:
- [copy] Copying 1 file to /tmp/jboss-4.2.0/server/production/deploy
+ [copy] Copying 1 file to /tmp/jboss-<version>/server/default/deploy
[echo] Waiting for 5 seconds for deploy...
...
[java] Created Echo
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/The_CMP_Engine.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/The_CMP_Engine.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/The_CMP_Engine.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -21,11 +21,11 @@
</mediaobject>
</figure>
<para>
- The source code for the crime portal is available in the <literal>src/main/org/jboss/cmp2</literal> directory of the example code. To build the example code, run Ant as shown below
+ The source code for the crime portal is available in the <literal>src/main/org/jboss/cmp2</literal> directory of the example code. To build the example code, run Ant as shown below. This command builds and deploys the application to the JBoss server. Be sure the JBoss server dist locations are correctly defined or overridden using a local ant.properties file.
</para>
<programlisting format="linespecific">[examples]$ ant -Dchap=cmp2 config</programlisting>
<para>
- This command builds and deploys the application to the JBoss server. When you start yours JBoss server, or if it is already running, you should see the following deployment messages:
+ When you start your JBoss server, or if it is already running, you should see the following deployment messages:
</para>
<programlisting>15:46:36,704 INFO [OrganizationBean$Proxy] Creating organization Yakuza, Japanese Gangsters
15:46:36,790 INFO [OrganizationBean$Proxy] Creating organization Mafia, Italian Bad Guys
@@ -99,7 +99,7 @@
M GANGSTER t0_GangsterEJB WHERE t0_GangsterEJB.id=?
</programlisting>
<para>
- These tests exercise various finders, selectors and object to table mapping issues. We will refer to the tests throughout the chapter.
+ These tests exercise various finders, selects and object to table mapping issues. We will refer to the tests throughout the chapter.
</para>
<para>
The other main target runs a set of tests to demonstrate the optimized loading configurations presented in <xref linkend="The_CMP_Engine-Optimized_Loading" />. Now that the logging is setup correctly, the read-ahead tests will display useful information about the queries performed. Note that you do not have to restart the JBoss server for it to recognize the changes to the log4j.xml file, but it may take a minute or so. The following shows the actual execution of the readahead client:
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/The_JMX_Microkernel.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/The_JMX_Microkernel.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/The_JMX_Microkernel.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -1018,11 +1018,11 @@
Two useful operations you will find here are <literal>getPackageClassLoaders(String)</literal> and <literal>displayClassInfo(String)</literal>. The <literal>getPackageClassLoaders</literal> operation returns a set of class loaders that have been indexed to contain classes or resources for the given package name. The package name must have a trailing period. If you type in the package name <literal>org.jboss.ejb.</literal>, the following information is displayed:
</para>
<programlisting>[org.jboss.mx.loading.UnifiedClassLoader3 at e26ae7{
- url=file:/private/tmp/jboss-4.2.0/server/production/tmp/deploy/tmp11895jboss-service.xml,
+ url=file:/private/tmp/jboss-<version>/server/default/tmp/deploy/tmp11895jboss-service.xml,
addedOrder=2}]
</programlisting>
<para>
- This is the string representation of the set. It shows one <literal>UnifiedClassLoader3</literal> instance with a primary URL pointing to the <literal>jboss-service.xml</literal> descriptor. This is the second class loader added to the repository (shown by <literal>addedOrder=2</literal>). It is the class loader that owns all of the JARs in the <literal>lib</literal> directory of the server configuration (e.g., <literal>server/production/lib</literal>).
+ This is the string representation of the set. It shows one <literal>UnifiedClassLoader3</literal> instance with a primary URL pointing to the <literal>jboss-service.xml</literal> descriptor. This is the second class loader added to the repository (shown by <literal>addedOrder=2</literal>). It is the class loader that owns all of the JARs in the <literal>lib</literal> directory of the server configuration (e.g., <literal>server/default/lib</literal>).
</para>
<para>
The view the information for a given class, use the <literal>displayClassInfo</literal> operation, passing in the fully qualified name of the class to view. For example, if we use <literal>org.jboss.jmx.adaptor.html.HtmlAdaptorServlet</literal> which is from the package we just looked at, the following description is displayed:
@@ -1084,13 +1084,9 @@
All URLs referenced via the <literal>jboss.boot.library.list</literal> system property. These are path specifications relative to the <literal>libraryURL</literal> defined by the <literal>jboss.lib.url</literal> property. If there is no <literal>jboss.lib.url</literal> property specified, it defaults to <literal>jboss.home.url + /lib/</literal>. If there is no <literal>jboss.boot.library</literal> property specified, it defaults to <literal>jaxp.jar</literal>, <literal>log4j-boot.jar</literal>, <literal>jboss-common.jar</literal>, and <literal>jboss-system.jar</literal>.
</para>
</listitem>
+
<listitem>
<para>
- The JAXP JAR which is either <literal>crimson.jar</literal> or <literal>xerces.jar</literal> depending on the <literal>-j</literal> option to the <literal>Main</literal> entry point. The default is <literal>crimson.jar</literal>.
- </para>
- </listitem>
- <listitem>
- <para>
The JBoss JMX jar and GNU regex jar, <literal>jboss-jmx.jar</literal> and <literal>gnu-regexp.jar</literal>.
</para>
</listitem>
@@ -1184,7 +1180,7 @@
XMBeans are the JBoss JMX implementation version of the JMX model MBean. XMBeans have the richness of the dynamic MBean metadata without the tedious programming required by a direct implementation of the <literal>DynamicMBean</literal> interface. The JBoss model MBean implementation allows one to specify the management interface of a component through a XML descriptor, hence the X in XMBean. In addition to providing a simple mechanism for describing the metadata required for a dynamic MBean, XMBeans also allow for the specification of attribute persistence, caching behavior, and even advanced customizations like the MBean implementation interceptors. The high level elements of the <literal>jboss_xmbean_1_2.dtd</literal> for the XMBean descriptor is given in <xref linkend="JBoss_XMBeans-The_JBoss_1.0_XMBean_DTD_Overview_jboss_xmbean_1_2.dtd" />.
</para>
<figure id="JBoss_XMBeans-The_JBoss_1.0_XMBean_DTD_Overview_jboss_xmbean_1_2.dtd">
- <title>The JBoss 1.0 XMBean DTD Overview (jboss_xmbean_1_2.dtd)</title>
+ <title>The JBoss 1.2 XMBean DTD Overview (jboss_xmbean_1_2.dtd)</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="images/xmbean_1_2.jpg" />
@@ -1646,7 +1642,7 @@
<section id="Inspecting_the_Server___the_JMX_Console_Web_Application-Securing_the_JMX_Console">
<title>Securing the JMX Console</title>
<para>
- Since the JMX console web application is just a standard servlet, it may be secured using standard J2EE role based security. The <literal>jmx-console.war</literal> that is deployed as an unpacked WAR that includes template settings for quickly enabling simple username and password based access restrictions. If you look at the <literal>jmx-console.war</literal> in the <literal>server/production/deploy</literal> directory you will find the <literal>web.xml</literal> and <literal>jboss-web.xml</literal> descriptors in the <literal>WEB-INF</literal> directory. The <literal>jmx-console-roles.properties</literal> and <literal>jmx-console-users.properties</literal> files are located in the <literal>server/production/conf/props</literal> directory.
+ Since the JMX console web application is just a standard servlet, it may be secured using standard J2EE role based security. The <literal>jmx-console.war</literal> that is deployed as an unpacked WAR that includes template settings for quickly enabling simple username and password based access restrictions. If you look at the <literal>jmx-console.war</literal> in the <literal>server/default/deploy</literal> directory you will find the <literal>web.xml</literal> and <literal>jboss-web.xml</literal> descriptors in the <literal>WEB-INF</literal> directory. The <literal>jmx-console-roles.properties</literal> and <literal>jmx-console-users.properties</literal> files are located in the <literal>/conf/props</literal> directory.
</para>
<para>
By uncommenting the security sections of the <literal>web.xml</literal> and <literal>jboss-web.xml</literal> descriptors as shown in <xref linkend="Securing_the_JMX_Console-The_jmx_console.war_web.xml_descriptors_with_the_security_elements_uncommented." />, you enable HTTP basic authentication that restricts access to the JMX Console application to the user <literal>admin</literal> with password <literal>admin</literal>. The username and password are determined by the <literal>admin=admin </literal>line in the <literal>jmx-console-users.properties</literal> file.
@@ -2200,7 +2196,7 @@
</listitem>
<listitem>
<para>
- Initialize the unified class loader repository to contain all JARs in the optional patch directory as well as the server configuration file conf directory, for example, <literal>server/production/conf</literal>. For each JAR and directory an <literal>org.jboss.mx.loading.UnifiedClassLoader</literal> is created and registered with the unified repository. One of these <literal>UnifiedClassLoader</literal> is then set as the thread context class loader. This effectively makes all <literal>UnifiedClassLoader</literal>s available through the thread context class loader.
+ Initialize the unified class loader repository to contain all JARs in the optional patch directory as well as the server configuration file conf directory, for example, <literal>server/default/conf</literal>. For each JAR and directory an <literal>org.jboss.mx.loading.UnifiedClassLoader</literal> is created and registered with the unified repository. One of these <literal>UnifiedClassLoader</literal> is then set as the thread context class loader. This effectively makes all <literal>UnifiedClassLoader</literal>s available through the thread context class loader.
</para>
</listitem>
<listitem>
@@ -2540,7 +2536,7 @@
<itemizedlist>
<listitem>
<para>
- <emphasis role="bold">URLs</emphasis>: A comma separated list of URL strings for the locations that should be watched for changes. Strings that do not correspond to valid URLs are treated as file paths. Relative file paths are resolved against the server home URL, for example, <literal>JBOSS_DIST/server/production</literal> for the default config file set. If a URL represents a file then the file is deployed and watched for subsequent updates or removal. If a URL ends in <literal>/</literal> to represent a directory, then the contents of the directory are treated as a collection of deployables and scanned for content that are to be watched for updates or removal. The requirement that a URL end in a <literal>/</literal> to identify a directory follows the RFC2518 convention and allows discrimination between collections and directories that are simply unpacked archives.
+ <emphasis role="bold">URLs</emphasis>: A comma separated list of URL strings for the locations that should be watched for changes. Strings that do not correspond to valid URLs are treated as file paths. Relative file paths are resolved against the server home URL, for example, <literal>JBOSS_DIST/server/default</literal> for the default config file set. If a URL represents a file then the file is deployed and watched for subsequent updates or removal. If a URL ends in <literal>/</literal> to represent a directory, then the contents of the directory are treated as a collection of deployables and scanned for content that are to be watched for updates or removal. The requirement that a URL end in a <literal>/</literal> to identify a directory follows the RFC2518 convention and allows discrimination between collections and directories that are simply unpacked archives.
</para>
<para>
The default value for the URLs attribute is <literal>deploy/</literal> which means that any SARs, EARs, JARs, WARs, RARs, etc. dropped into the <literal>server/<name>/deploy</literal> directory will be automatically deployed and watched for updates.
@@ -2977,7 +2973,7 @@
<programlisting>[examples]$ ant -Dchap=chap2 -Dex=xmbean1 run-example
...
run-examplexmbean1:
- [copy] Copying 1 file to /tmp/jboss-4.2.0/server/production/deploy
+[copy] Copying 1 file to /tmp/jboss-<version>/server/production/deploy
[java] JNDIMap Class: org.jboss.mx.modelmbean.XMBean
[java] JNDIMap Operations:
[java] + void start()
@@ -3711,8 +3707,7 @@
<para>
On the server console there will be messages similar to the following:
</para>
-<programlisting>14:57:12,906 INFO [EARDeployer] Init J2EE application: file:/private/tmp/jboss-4.2.0/server/
- production/deploy/chap2-ex3.ear
+ <programlisting>14:57:12,906 INFO [EARDeployer] Init J2EE application: file:/private/tmp/jboss-<version>/server/default/deploy/chap2-ex3.ear
14:57:13,044 INFO [EjbMBeanAdaptor] Don't panic, just a stack trace
java.lang.Throwable: getMBeanInfo trace
at org.jboss.chap2.ex3.EjbMBeanAdaptor.getMBeanInfo(EjbMBeanAdaptor.java:153)
@@ -3792,9 +3787,9 @@
14:57:13,983 INFO [EchoBean] echo, info=echo info, arg=, arg=startService
14:57:13,986 INFO [EjbMBeanAdaptor] echo(startService) = startService
14:57:13,988 INFO [EjbMBeanAdaptor] End invoke, actionName=start
-14:57:13,991 INFO [EJBDeployer] Deployed: file:/private/tmp/jboss-4.2.0/server/production/tmp/d
+14:57:13,991 INFO [EJBDeployer] Deployed: file:/private/tmp/jboss-<version>/server/default/tmp/d
eploy/tmp1418chap2-ex3.ear-contents/chap2-ex3.jar
-14:57:14,075 INFO [EARDeployer] Started J2EE application: file:/private/tmp/jboss-4.2.0/serv
+14:57:14,075 INFO [EARDeployer] Started J2EE application: file:/private/tmp/jboss-<version>/serv
er/production/deploy/chap2-ex3.ear
</programlisting>
<para>
Modified: projects/docs/trunk/Server_Configuration_Guide/en-US/Transactions.xml
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/en-US/Transactions.xml 2007-11-04 22:15:55 UTC (rev 66720)
+++ projects/docs/trunk/Server_Configuration_Guide/en-US/Transactions.xml 2007-11-05 05:00:19 UTC (rev 66721)
@@ -6,8 +6,11 @@
<title>Transactions on JBoss</title>
<subtitle>The JTA Transaction Service</subtitle>
<para>
- This chapter discusses transaction management in JBoss and the JBossTX architecture. The JBossTX architecture allows for any Java Transaction API (JTA) transaction manager implementation to be used. JBossTX includes a fast in-VM implementation of a JTA compatible transaction manager that is used as the default transaction manager. We will first provide an overview of the key transaction concepts and notions in the JTA to provide sufficient background for the JBossTX architecture discussion. We will then discuss the interfaces that make up the JBossTX architecture and conclude with a discussion of the MBeans available for integration of alternate transaction managers.
+ This chapter discusses transaction management in JBoss and the JBossTX architecture. The JBossTX architecture allows for any Java Transaction API (JTA) transaction manager implementation to be used. JBossTX includes a fast in-VM implementation of a JTA compatible transaction manager which is now deprecated. JBoss Transactions (JBoss TS) is the new default transaction manager for JBoss. JBoss TS is founded on industry proven technology and 18 year history as a leader in distributed transactions. The JTA version of JBoss Transactions included with the server provides for fully recoverable transactions. For distributed transaction support the JTS version of JBoss Transactions will need to be used.
</para>
+ <para>
+ We will first provide an overview of the key transaction concepts and notions in the JTA to provide sufficient background for the JBossTX architecture discussion. We will then discuss the interfaces that make up the JBossTX architecture and conclude with a discussion of the MBeans available for integration of alternate transaction managers.
+ </para>
<section id="Transactions_on_JBoss-TransactionJTA_Overview">
<title>Transaction/JTA Overview</title>
<para>
More information about the jboss-cvs-commits
mailing list