[jboss-cvs] JBossAS SVN: r82247 - projects/docs/community/5/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Dec 12 12:15:59 EST 2008
Author: scott.stark at jboss.org
Date: 2008-12-12 12:15:59 -0500 (Fri, 12 Dec 2008)
New Revision: 82247
Modified:
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Book_Info.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml
Log:
JBAS-6820, update directory view and compatibility notes
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2008-12-12 14:30:21 UTC (rev 82246)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2008-12-12 17:15:59 UTC (rev 82247)
@@ -15,46 +15,139 @@
<para>
The directory structure of JBoss 5 resembles that of the 4.x series with some notable differences:
-<screen><![CDATA[-<JBOSS_HOME>/ - the path to your JBoss AS installation.
- + bin/ - contains start scripts and run.jar
- + client/ - client jars
- + docs/ - docs, schemas/dtds, examples
- + lib/ - core bootstrap jars, different with the introduction of
- the microcontainer and breakup of jboss-common.
- + server/ - contains the same server configuration directories.
- + default/ configuration
- + conf/ - contains server configuration files used when starting the server.
- changes in here are detected on restarting your server.
- # bootstrap-beans.xml - new mc kernel bootstrap configuration
- # jax-ws-catalog.xml - oasis catalog driven schema/dtd namespace configuration
- # jbossjta-properties.xml - new JBossTS properties
- # jboss-service.xml - legacy static mbeans for compatibility
- # jndi.properties - the same jndi props
- # log4j.xml - the same log4j config
- # login-config.xml - the same jaas login config
- # props/ - the same default jaas login properties files
- # standardjaws.xml - obsolete cmp config
- # standardjbosscmp-jdbc.xml - the same cmp2 config
- # standardjboss.xml - the same ejb2 config
- # xmdesc/ - legacy xmbean descriptors
- + data/ - contains hypersonic local database, transactions, xmbean configuration files.
- + deploy/ - this is where services and your java applications are deployed.
+<screen>
+<![CDATA[-<JBOSS_HOME>/ - the path to your JBoss AS installation.
+ |-- bin - contains start scripts and run.jar
+ |-- client - client jars
+ |-- common - static jars shared across server configuration
+ | |-- lib
+ | | |-- antlr.jar
+ | | |-- ... many more jars
+ |-- docs - docs, schemas/dtds, examples
+ | |-- 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 - core bootstrap jars.
+ | |-- concurrent.jar
+ | |-- dom4j.jar
+ | |-- getopt.jar
+ | |-- javassist.jar
+ | |-- ...
+ | |-- endorsed - added to the server JVM java.endorsed.dirs path
+ | | |-- serializer.jar
+ | | |-- xalan.jar
+ | | `-- xercesImpl.jar
+ `-- server - contains the same server configuration/profile directories.
+ |-- default
+ | |-- conf - contains server configuration files used when starting the server.
+ | | |-- bootstrap/
+ | | | |-- aop.xml - JBoss AOP integration and AspectManager beans
+ | | | |-- bindings.xml - Rewrite of the ServiceBindingManager as a POJO bean
+ | | | |-- classloader.xml - the root class loading beans for the peer class loading model
+ | | | |-- deployers.xml - Core deployers for -jboss-beans.xml and -service.xml
+ | | | |-- jmx.xml - JBoss JMX kernel initialization
+ | | | |-- profile-repository.xml - full featured repository based profile service referenced by bootstrap.xml
+ | | | |-- profile.xml - simple disk based profile service referenced by bootstrap-norepo.xml
+ | | | |-- vfs.xml - JBoss VFS caching beans
+ | | |-- bootstrap.xml - bootstrap deployment definition file
+ | | |-- bootstrap-norepo.xml - bootstrap deployment definition file for the non-repository profile service
+ | | |-- java.policy - stub for java security policy
+ | | |-- jax-ws-catalog.xml - oasis catalog driven schema/dtd namespace configuration
+ | | |-- jboss-log4j.xml - the server log4j configuration
+ | | |-- jboss-service.xml - legacy static mbeans, to be removed in future
+ | | |-- jbossjta-properties.xml - JBossTS properties
+ | | |-- jndi.properties - server default JNDI properties
+ | | |-- login-config.xml - security authentication domain definitions
+ | | |-- props -
+ | | | |-- jbossws-roles.properties
+ | | | |-- jbossws-users.properties
+ | | | |-- jmx-console-roles.properties
+ | | | `-- jmx-console-users.properties
+ | | |-- standardjboss.xml - legacy EJB2 container definitions
+ | | |-- standardjbosscmp-jdbc.xml - legacy CMP2 definitions
+ | | `-- xmdesc - JBoss XMBean descriptors
+ | | |-- 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 - location for services data
+ | | |-- hypersonic
+ | | |-- jboss.identity
+ | | |-- tx-object-store
+ | | `-- xmbean-attrs
+ | |-- deploy - this is where services and your java applications are deployed.
You can deploy an application on the JBoss application server by simply
copying the application's (WAR, EAR or JAR files) into this directory.
- + deployers/ - new vdf deployers
- # bsh-deployer - beanshell deployer
- # ejb3.deployer - ejb3 deployers
- # jboss-aop-jboss5.deployer - aspect deployer
- # jboss-jca.deployer - JCA deployers
- # jbossweb.deployer - war deployers
- # jbossws.deployer - web services deployers
- # ear-deployer-beans.xml - ear deployers
- # ejb-deployer-beans.xml - ejb2.x deployers
- # metadata-beans.xml - metadata handlers
- # security-deployer-beans.xml - security deployers
- # profileservice-beans.xml.bak - an example of the repository based profile service
- + lib/ - the JBoss AS static library files shared by the services and applications
- in the respective configuration.]]></screen>
+ | |-- deployers/ - new vdf deployers
+ | | |-- alias-deployers-jboss-beans.xml - Deployers that know how to handle The know
+how to handle deployment aliases.
+ | | |-- bsh-deployer - beanshell deployer
+ | | |-- clustering-deployer-jboss-beans.xml - add dependencies on needed clustering services
+to clustered EJB3, EJB2 beans and to distributable web applications.
+ | | |-- dependency-deployers-jboss-beans.xml - aliases.txt, jboss-dependency.xml
+ | | |-- directory-deployer-jboss-beans.xml
+ | | |-- ear-deployer-jboss-beans.xml - ear deployers
+ | | |-- ejb-deployer-jboss-beans.xml - ejb2.x deployers
+ | | |-- ejb3.deployer - ejb3 deployers
+ | | |-- hibernate-deployer-jboss-beans.xml - deployers for -hibernate.xml descriptors
+ | | |-- jboss-aop-jboss5.deployer - aspect deployer
+ | | |-- jboss-jca.deployer - JCA deployers
+ | | |-- jbossweb.deployer - war deployers
+ | | |-- jbossws.deployer - web services deployers
+ | | |-- jsr77-deployers-jboss-beans.xml - JSR77 mbean view creation deployers
+ | | |-- metadata-deployer-jboss-beans.xml - metadata handlers
+ | | |-- seam.deployer - seam integration deployer
+ | | |-- security-deployer-jboss-beans.xml - security deployers
+ | |-- lib - default server static jars, empty by default
+ | |-- log - default root for log files, controlled by jboss.server.log.dir
+ | | |-- boot.log
+ | | |-- server.log
+ | |-- tmp
+ | `-- work
+ | `-- jboss.web
+ | `-- localhost
+ `-- minimal - a
+ |-- conf
+ | |-- bootstrap/
+ | | | |-- aop.xml
+ | | | |-- classloader.xml
+ | | | |-- deployers.xml
+ | | | |-- jmx.xml
+ | | | |-- 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>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2008-12-12 14:30:21 UTC (rev 82246)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2008-12-12 17:15:59 UTC (rev 82247)
@@ -5,12 +5,12 @@
<bookinfo id="JBoss_Application_Server">
<title>Administration And Configuration Guide</title>
- <edition>2</edition>
+ <edition>5</edition>
<issuenum>2</issuenum>
<pubsnumber>2</pubsnumber>
<productname>JBoss Application Server</productname>
<productnumber>5</productnumber>
- <pubdate>Nov 2008</pubdate>
+ <pubdate>Dec 2008</pubdate>
<abstract>
<para>
This book is a guide to the administration and configuration of the JBoss Application Server 5.
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml 2008-12-12 14:30:21 UTC (rev 82246)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml 2008-12-12 17:15:59 UTC (rev 82247)
@@ -1,5 +1,5 @@
<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<chapter id="JBoss_AS5_Introduction">
@@ -240,85 +240,74 @@
</section>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
<section>
<title>JBoss Application Server 5 compatibility issues</title>
<para>
The following are current compatibility issues for JBoss AS5:
- <orderedlist>
- <listitem>
- <para>
- JBossAS 5 runs under Java 5 but there is an ongoing task to make it run safely under Java 6, too <ulink url="http://jira.jboss.org/jira/browse/JBAS-5031"/>. If using a Sun Java 6 runtime, you may want to set <command>-Dsun.lang.ClassLoader.allowArraySyntax=true</command>, as described in <ulink url="http://jira.jboss.org/jira/browse/JBAS-4491"/>.
- </para>
- </listitem>
- <listitem>
- <para>
- If using proprietary JBoss/EJB3 annotations, those have moved into the <literal>org.jboss.ejb3.annotation</literal> package, <ulink url="http://jira.jboss.org/jira/browse/EJBTHREE-1099"/>. Those are now included in a new artifact, <literal>jboss-ejb3-ext-api.jar</literal>
- </para>
- </listitem>
- <listitem>
- <para>
- Work on EJB3 Extended Persistence Context support is not completed, <ulink url="http://jira.jboss.org/jira/browse/EJBTHREE-1026"/>.
- </para>
- </listitem>
- <listitem>
- <para>
- Interoperating with previous JBoss EJB3 implementations may present problems due to serialVersionUIDs issues, <ulink url="http://jira.jboss.org/jira/browse/EJBTHREE-1118"/>.
- </para>
- </listitem>
- <listitem>
- <para>
- EJB 2.1 View requirements
- <itemizedlist>
- <listitem>
- <para>
- Home extending EJBLocalHome? or EJBHome must be defined
- </para>
- </listitem>
- <listitem>
- <para>
- Remote or Local interface must either be defined via @Local/@Remote or via return type of "create<METHOD>" methods of the Home
- </para>
- </listitem>
- <listitem>
- <para>
- EJB 2.1 Remote/Local interfaces must extend EJBObject/EJBLocalObject
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- @Local/@Remote may be used to define either EJB 3.0 View Business Interface, or EJB 2.1 View Remote/Local interface
- </para>
- </listitem>
- <listitem>
- <para>
- Use of JBoss Cache 2.x. JBC 2.x has a significantly different API from the 1.x releases used in JBoss AS 4.x and 3.2.x.
- </para>
- </listitem>
- </orderedlist>
-
- </para>
-</section>
+ </para>
+ <section id="Java6_Notes">
+ <title>Java 6 Notes</title>
+ <para>JBossAS 5.0.0.GA can be compiled with both Java5 and Java6. The Java5 compiled binary is our primary/recommended binary
+ distribution. It has undergone rigorous testing and can run under both a Java 5 and a Java 6 runtime. When running
+ under Java 6 you need to manually copy the following libraries from the JBOSS_HOME/client directory to the
+ JBOSS_HOME/lib/endorsed directory, so that the JAX-WS 2.0 apis supported by JBossWS are used:
+ <simplelist>
+ <member>jbossws-native-saaj.jar</member>
+ <member>jbossws-native-jaxrpc.jar</member>
+ <member>jbossws-native-jaxws.jar</member>
+ <member>jbossws-native-jaxws-ext.jar</member>
+ </simplelist>
+
+ The other option is to download the jdk6 distribution (jboss-5.0.0.GA-jdk6.zip) in which case no configuration
+ changes are required. If you still have problems using JBoss with a Sun Java 6 runtime, you may want to set
+ -Dsun.lang.ClassLoader.allowArraySyntax=true, as described in JBAS-4491. Other potential problems under a Java 6
+ runtime include:
+ <simplelist>
+ <member>ORB getting prematurely destroyed when using Sun JDK 6 (see Sun Bug ID: 6520484)</member>
+ <member>Unimplemented methods in Hibernate for JDK6 interfaces.</member>
+ <member>When JBossAS 5 is compiled with Java 6, support for the extended JDBC 4 API is included in the binary, however
+ this can only be used under a Java 6 runtime. In this case no manual configuration steps are necessary.</member>
+ </simplelist>
+ <note><para>It should be noted that the Java 6 compiled distribution of JBoss AS 5 is still in an experimental stage in terms of testing.</para></note>
+ </para>
+ </section>
+ <section id="Hibernate_Logging">
+ <title>Hibernate Logging</title>
+ <para>Hibernate-core is now using slf4j-api as a logging facade. To properly integrate that in JBossAS we have created an slf4j-to-jboss-logging adapter (slf4j-jboss-logging.jar) that creates a static binding between sl4j and jboss-logging-spi.</para>
+ </section>
+ <section>
+ <title>jbossall-client.jar </title>
+ <para>The client/jbossall-client.jar library that used to bundle the majority of jboss client libraries, is now referencing them instead through the Class-Path manifest entry. This allows swapping included libraries (e.g. jboss-javaee.jar) without having to re-package jbossall-client.jar. On the other hand, it requires that you have jbossall-client.jar together with the other client/*.jar libraries, so they can be found.</para>
+ </section>
+ <section id="EJB3_Compatibility_Notes">
+ <title>EJB3 Compatibility Notes</title>
+ <para>If using proprietary JBoss/EJB3 annotations, those have moved (since Beta4) into the org.jboss.ejb3.annotation package, EJBTHREE-1099. Those are now included in a new artifact, jboss-ejb3-ext-api.jar</para>
+ <para>Interoperating with previous JBoss EJB3 implementations may present problems due to serialVersionUIDs issues, EJBTHREE-1118.</para>
+ <para>Use of JBoss Cache 3.x. has a significantly different API from the 1.x releases used in JBoss AS 4.x and 3.2.x.</para>
+ <para>@EJB injections should now work from servlets, JBAS-5646.</para>
+ <para>EJB3 configuration is now controlled by deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml as described in <ulink url="http://www.jboss.org/community/docs/DOC-12407"></ulink></para>
+ </section>
+ <section>
+ <title>Other JBossAS </title>
+ <para>The ClassPathExtension MBean has been replaced with a VFS classloader definition, see JBAS-5446.</para>
+ <para>The old JMX-based ServiceBindingManager has been replaced by a POJO-based ServiceBindingManager, see <ulink url="http://www.jboss.org/community/docs/DOC-9038">AS5ServiceBindingManager Wiki</ulink>.</para>
+ <para>The Farm service from 4.x has been removed, and replaced with a HASingletonDeploymentScanner that integrates with the ProfileService.</para>
+ <para>JBoss 5 is stricter when it comes to verifying/deploying JavaEE artifacts. EJB3 deployments that run in AS 4.2 may fail in AS5. We have tried to keep the validation messages as accurate as possible in order to help you modify your deployment descriptors/annotations to be in-line with the JavaEE 5 requirements.</para>
+ <para>A new jboss.server.log.threshold system property can be used to control the log/server.log threshold. It defaults to DEBUG.</para>
+ <para>The default conf/jboss-log4j.xml configuration now includes the thread name for entries in log/server.log (JBAS-5274).</para>
+ <para>The transaction manager configuration has moved from conf/jboss-service.xml to deploy/transaction-service.xml.</para>
+ <para>All the security related configuration files are now grouped under the deploy/security directory (JBAS-5318). The security configuration changes are further described in <ulink url="http://www.jboss.org/community/docs/DOC-12199">SecurityInJBoss5</ulink> wiki.</para>
+ </section>
+ <section>
+ <title>Clustering</title>
+ <para>A new jboss.jgroups.udp.mcast_port property is to control easy configuration of multicast port. It defaults to ${jboss.jgroups.udp.mcast_port:45688}.</para>
+ <para>Clustering configurations are now in a deploy/clustering subdirectory</para>
+ <para>A separate cache is now used for Clustered SSO (JBAS-4676).</para>
+ <para>Per webapp configuration of useJK, snapshot mode and snapshot interval (JBAS-3460). Default for useJK is whether jvmRoute is set (JBAS-4961).</para>
+ <para>Total replication (rather than buddy replication) is the default setting for session replication (JBAS-5085).</para>
+ <para>Loopback is now set to true for all JGroups UDP stacks (JBAS-5323).</para>
+ </section>
+ </section>
</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml 2008-12-12 14:30:21 UTC (rev 82246)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/What_This_Book_Covers.xml 2008-12-12 17:15:59 UTC (rev 82247)
@@ -4,7 +4,7 @@
<preface id="What_this_Book_Covers"><title>What this Book Covers</title>
<para>
- The primary focus of this book is the presentation of the standard JBoss 4.2 architecture components from both the perspective of their configuration and architecture. As a user of a standard JBoss distribution you will be given an understanding of how to configure the standard components. Note that this book is not an introduction to J2EE or how to use J2EE in applications. It focuses on the internal details of the JBoss server architecture and how our implementation of a given J2EE container can be configured and extended.
+ The primary focus of this book is the presentation of the standard JBossAS 5.0 architecture components from both the perspective of their configuration and architecture. As a user of a standard JBoss distribution you will be given an understanding of how to configure the standard components. Note that this book is not an introduction to JavaEE or how to use JavaEE in applications. It focuses on the internal details of the JBoss server architecture and how our implementation of a given JavaEE container can be configured and extended.
</para>
<para>
As a JBoss developer, you will be given a good understanding of the architecture and integration of the standard components to enable you to extend or replace the standard components for your infrastructure needs. We also show you how to obtain the JBoss source code, along with how to build and debug the JBoss server.
More information about the jboss-cvs-commits
mailing list