[jboss-cvs] JBossAS SVN: r95815 - projects/docs/enterprise/5.0/Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Oct 30 01:25:36 EDT 2009
Author: laubai
Date: 2009-10-30 01:25:36 -0400 (Fri, 30 Oct 2009)
New Revision: 95815
Modified:
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
Log:
Applied all changes in JBPAPP-2960.
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml 2009-10-30 05:21:36 UTC (rev 95814)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml 2009-10-30 05:25:36 UTC (rev 95815)
@@ -28,7 +28,7 @@
</title>
<para>
- JBoss Enterprise Application Platform 5 fully supports the entire Java 6 Enterprise Edition specification. JEnterprise Application Platform 4.3 implemented EJB3 functionality by way of an EJB MBean container running as a plugin in the JBoss Enterprise Application Platform. This had certain implications for application development.
+ JBoss Enterprise Application Platform 5 fully supports the entire Java 5 Enterprise Edition specification. JBoss Enterprise Application Platform 4.3 implemented EJB3 functionality by way of an EJB MBean container running as a plugin in the JBoss Enterprise Application Platform. This had certain implications for application development.
</para>
<para>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml 2009-10-30 05:21:36 UTC (rev 95814)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml 2009-10-30 05:25:36 UTC (rev 95815)
@@ -7,7 +7,7 @@
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="The_JBoss_Server_A_Quick_Tour.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="EJB3_Caveats.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!--<xi:include href="EJB3_Caveats.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
<xi:include href="Using_Other_Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- <xi:include href="Appendix2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml 2009-10-30 05:21:36 UTC (rev 95814)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Preface.xml 2009-10-30 05:25:36 UTC (rev 95815)
@@ -4,7 +4,7 @@
<preface id="Book-Preface">
<title>Introduction</title>
<para>
- JBoss Enterprise Application Platform is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. It's easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
+ JBoss Enterprise Application Platform is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. Its easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
</para>
<para>
Because it is Java-based, JBoss Enterprise Application Platform is cross-platform, easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
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-10-30 05:21:36 UTC (rev 95814)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2009-10-30 05:25:36 UTC (rev 95815)
@@ -2,7 +2,7 @@
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations">
-<title>Server Configurations</title>
+<title>Server Profiles</title>
<para>
Fundamentally, the JBoss architecture consists of the microcontainer, bootstrap beans loaded into the micrcontainer, a collection of deployers for loading various deployment types, and various mcbean(<filename>-jboss-beans.xml</filename>) and legacy mbean(<filename>jboss-service.xml</filename>) deployments.
This makes it easy to assemble different configurations and gives you the flexibility to tailor them to meet your requirements.
@@ -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>, <literal>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.
+ <literal>all</literal>, <literal>default</literal>, <literal>minimal</literal>, <literal>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> profile is the one used if you don’t specify another one when starting up the server.
</para>
<para>
<variablelist>
@@ -31,7 +31,7 @@
<term>default</term>
<listitem>
<para>
- is a base Java EE 5 server profile containing a default set of services. It has the most frequently used services required to deploy a Java EE application. It does not include the JAXR service, the IIOP service, or any of the clustering services.
+ is a base Java EE 5 server profile containing a default set of services. It has the most frequently used services required to deploy a Java EE application. It does not include the JAXR service, the IIOP service, or any of the clustering services. This is the configuration used by the server when it is started, if no other configuration is specified.
</para>
</listitem>
</varlistentry>
@@ -39,7 +39,7 @@
<term>production</term>
<listitem>
<para>
- is based on the <literal>all</literal> profile, tuned for production; with log verbosity reduced, deployment scanning every 60 seconds, and memory usage tuned to accomodate production deployment requirements, among other things. This is the configuration that will be used by the server when it is started, if no other configuration is specified.
+ is based on the <literal>all</literal> profile, tuned for production; with log verbosity reduced, deployment scanning every 60 seconds, and memory usage tuned to accomodate production deployment requirements, among other things.
</para>
</listitem>
</varlistentry>
@@ -72,53 +72,73 @@
<para>
If you want to know which services are configured in each of these instances, the primary differences will be in the <filename class="directory"><JBoss_Home>/server/<instance-name>/deployers/</filename> directory and also the services deployments in the <filename class="directory"><JBoss_Home>/server/<instance-name>/deploy</filename> directory. For example, the default profile deployers and deploy directory contents are:
<programlisting>
-[usr at localhost <JBoss_Home>]$<literal>ls server/default/deployers </literal>
-alias-deployers-jboss-beans.xml jboss-aop-jboss5.deployer
-bsh.deployer jboss-jca.deployer
-clustering-deployer-jboss-beans.xml jbossweb.deployer
-dependency-deployers-jboss-beans.xml jbossws.deployer
-directory-deployer-jboss-beans.xml j sr77-deployers-jboss-beans.xml
-ear-deployer-jboss-beans.xml metadata-deployer-jboss-beans.xml
-ejb-deployer-jboss-beans.xml seam.deployer
-ejb3.deployer security-deployer-jboss-beans.xml
-hibernate-deployer-jboss-beans.xml
-[usr at localhost <JBoss_Home>]$<literal>ls server/default/deploy </literal>
-ROOT.war jsr88-service.xml
-cache-invalidation-service.xml legacy-invokers-service.xml
-ejb2-container-jboss-beans.xml mail-ra.rar
-ejb2-timer-service.xml mail-service.xml
-ejb3-connectors-jboss-beans.xml management
-ejb3-container-jboss-beans.xml messaging
-ejb3-interceptors-aop.xml monitoring-service.xml
-ejb3-timer-service.xml profileservice-jboss-beans.xml
-hdscanner-jboss-beans.xml properties-service.xml
-hsqldb-ds.xml quartz-ra.rar
-http-invoker.sar remoting-jboss-beans.xml
-jboss-local-jdbc.rar schedule-manager-service.xml
-jboss-xa-jdbc.rar scheduler-service.xml
-jbossweb.sar security
-jbossws.sar sqlexception-service.xml
-jca-jboss-beans.xml transaction-jboss-beans.xml
-jms-ra.rar transaction-service.xml
-jmx-console.war uuid-key-generator.sar
-jmx-invoker-service.xml vfs-jboss-beans.xml
-jmx-remoting.sar
+[usr at localhost <JBoss_Home>]$ <literal>ls server/default/deployers</literal>
+alias-deployers-jboss-beans.xml jboss-jca.deployer
+bsh.deployer jboss-threads.deployer
+clustering-deployer-jboss-beans.xml jbossweb.deployer
+dependency-deployers-jboss-beans.xml jbossws.deployer
+directory-deployer-jboss-beans.xml jsr77-deployers-jboss-beans.xml
+ear-deployer-jboss-beans.xml logbridge-jboss-beans.xml
+ejb3.deployer messaging-definitions-jboss-beans.xml
+ejb-deployer-jboss-beans.xml metadata-deployer-jboss-beans.xml
+hibernate-deployer-jboss-beans.xml seam.deployer
+jboss-aop-jboss5.deployer security-deployer-jboss-beans.xml
+jboss-ejb3-endpoint-deployer.jar xnio.deployer
+jboss-ejb3-metrics-deployer.jar
+[usr at localhost <JBoss_Home>]$ ls <literal>server/default/deploy</literal>
+admin-console.war legacy-invokers-service.xml
+cache-invalidation-service.xml mail-ra.rar
+ejb2-container-jboss-beans.xml mail-service.xml
+ejb2-timer-service.xml management
+ejb3-connectors-jboss-beans.xml messaging
+ejb3-container-jboss-beans.xml monitoring-service.xml
+ejb3-interceptors-aop.xml profileservice-jboss-beans.xml
+ejb3-timerservice-jboss-beans.xml properties-service.xml
+hdscanner-jboss-beans.xml quartz-ra.rar
+hsqldb-ds.xml remoting-jboss-beans.xml
+http-invoker.sar ROOT.war
+jboss-local-jdbc.rar schedule-manager-service.xml
+jbossweb.sar scheduler-service.xml
+jbossws.sar security
+jboss-xa-jdbc.rar sqlexception-service.xml
+jca-jboss-beans.xml transaction-jboss-beans.xml
+jms-ra.rar transaction-service.xml
+jmx-console.war uuid-key-generator.sar
+jmx-invoker-service.xml vfs-jboss-beans.xml
+jsr88-service.xml xnio-provider.jar
+
</programlisting>
while the web profile deployers and deploy directory contents are:
<programlisting>
-[usr at localhost <JBoss_Home>]$<literal>ls server/web/deployers </literal>
-alias-deployers-jboss-beans.xml jbossweb.deployer
-ejb3.deployer metadata-deployer-jboss-beans.xml
-jboss-aop-jboss5.deployer security-deployer-jboss-beans.xml
-jboss-jca.deployer
-[usr at localhost <JBoss_Home>]$<literal>ls server/web/deployers </literal>
-ROOT.war jbossweb.sar
-ejb3-container-jboss-beans.xml jca-jboss-beans.xml
-hdscanner-jboss-beans.xml jmx-console.war
-hsqldb-ds.xml jmx-invoker-service.xml
-http-invoker.sar security
-jboss-local-jdbc.rar transaction-jboss-beans.xml
-jboss-xa-jdbc.rar
+[usr at localhost <JBoss_Home>]$ <literal>ls server/web/deployers</literal>
+alias-deployers-jboss-beans.xml jboss-jca.deployer
+bsh.deployer jboss-threads.deployer
+clustering-deployer-jboss-beans.xml jbossweb.deployer
+dependency-deployers-jboss-beans.xml jbossws.deployer
+directory-deployer-jboss-beans.xml jsr77-deployers-jboss-beans.xml
+ear-deployer-jboss-beans.xml logbridge-jboss-beans.xml
+ejb3.deployer messaging-definitions-jboss-beans.xml
+ejb-deployer-jboss-beans.xml metadata-deployer-jboss-beans.xml
+hibernate-deployer-jboss-beans.xml seam.deployer
+jboss-aop-jboss5.deployer security-deployer-jboss-beans.xml
+jboss-ejb3-endpoint-deployer.jar xnio.deployer
+jboss-ejb3-metrics-deployer.jar
+[usr at localhost <JBoss_Home>]$ <literal>ls server/web/deploy</literal>
+admin-console.war jca-jboss-beans.xml
+cluster jmx-console.war
+ejb2-container-jboss-beans.xml jmx-invoker-service.xml
+ejb2-timer-service.xml legacy-invokers-service.xml
+ejb3-connectors-jboss-beans.xml mail-ra.rar
+ejb3-container-jboss-beans.xml mail-service.xml
+ejb3-interceptors-aop.xml profileservice-jboss-beans.xml
+ejb3-timerservice-jboss-beans.xml remoting-jboss-beans.xml
+hdscanner-jboss-beans.xml ROOT.war
+hsqldb-ds.xml security
+jboss-local-jdbc.rar transaction-jboss-beans.xml
+jbossweb.sar transaction-service.xml
+jbossws.sar vfs-jboss-beans.xml
+jboss-xa-jdbc.rar xnio-provider.jar
+
</programlisting>
</para>
<formalpara>
@@ -192,7 +212,7 @@
This directory is meant to contains all the configurations and JAR files which are common for all the server configuration sets. The <filename>lib</filename> sub-directory within this <filename>common</filename> directory, contains all the JAR files which are common to the server configuration sets. The intention of having these JAR files in this one place, instead of the <filename>lib</filename> folder of each of the server configuration sets, is to reduce the size of the server. It also helps in maintainance; the lower the number of files to maintain, the better it is.
</entry>
<entry>
- Like some of the other JBoss server configuration paths, this <filename>common</filename> and the <filename>common/lib</filename> directories are available as the system properties <filename>jboss.common.base.url</filename> (This holds the URL to <filename>JBOSS_DIST/common</filename> directory) and <filename>jboss.common.lib.url</filename> (This holds the URL to <filename>JBOSS_DIST/common/lib</filename> directory).
+ Like some of the other JBoss server configuration paths, this <filename>common</filename> and the <filename>common/lib</filename> directories are available as the system properties <filename>jboss.common.base.url</filename> (This holds the URL to <filename>JBOSS_DIST/jboss-as/common</filename> directory) and <filename>jboss.common.lib.url</filename> (This holds the URL to <filename>JBOSS_DIST/jboss-as/common/lib</filename> directory).
</entry>
</row>
<row>
@@ -220,7 +240,7 @@
server
</entry>
<entry>
- Contains the JBoss server configuration sets. Each of the subdirectories in here is a different server configuration. JBoss ships with minimal, default, production, standard, web and all configuration sets. The subdirectories and key configuration files contained in the <literal>default</literal> configuration set are discussed in more detail in subsequent sections.
+ Contains the JBoss server profile sets. Each of the subdirectories in here is a different server profile. JBoss ships with <literal>minimal</literal>, <literal>default</literal>, <literal>production</literal>, <literal>standard</literal>, <literal>web</literal> and <literal>all</literal> profile sets. The subdirectories and key configuration files contained in the <literal>default</literal> profile set are discussed in more detail in subsequent sections.
</entry>
<entry>
</entry>
@@ -231,18 +251,18 @@
</para>
<important>
<para>
- Do not remove any configuration or JRA files from the <filename>common</filename> directory location. You may add your own JAR files in the <filename>common/lib</filename> directory <emphasis>if</emphasis> those JAR files are meant to be used by all the server configuration sets. If you want the JAR files to be available for all the applications deployed in a single server configuration set (for example, the <literal>production</literal> configuration), then the best location to place these JARs is the <filename>JBOSS_DIST/server/<server-configuration-set>/lib</filename> directory.
+ Do not remove any configuration or JRA files from the <filename>common</filename> directory location. You may add your own JAR files in the <filename>common/lib</filename> directory <emphasis>if</emphasis> those JAR files are meant to be used by all the server profile sets. If you want the JAR files to be available for all the applications deployed in a single server profile set (for example, the <literal>production</literal> profile), then the best location to place these JARs is the <filename>JBOSS_DIST/server/<server-profile>/lib</filename> directory.
</para>
</important>
</section>
-<section id="Server_Configuration_Directory_Structure">
- <title>Server Configuration Directory Structure</title>
+<section id="Server_Profile_Directory_Structure">
+ <title>Server Profile Directory Structure</title>
<para>
- The directory server configuration you’re using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server configuration directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
+ The directory server profile you are using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server profile. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server profile directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
</para>
<para>
- <table id="Server_Configuration_Directory_Structure_table">
- <title>Server Configuration Directory Structure</title>
+ <table id="Server_Profile_Directory_Structure_table">
+ <title>Server Profile Directory Structure</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="1*"/>
<colspec colname="c2" colnum="2" colwidth="4*"/>
@@ -262,7 +282,7 @@
<filename class="directory">conf</filename>
</entry>
<entry>
- The <filename class="directory">conf</filename> directory contains the <filename>jboss-service.xml</filename>, <filename>bootstrap.xml</filename> bootstrap descriptor file for a given server configuration. The <filename>bootstrap.xml</filename> inturn points to various other configuration files which comprise of the server bootstrap. This defines the core microcontainer beans that are fixed for the lifetime of the server.
+ The <filename class="directory">conf</filename> directory contains the <filename>jboss-service.xml</filename>, <filename>bootstrap.xml</filename> bootstrap descriptor file for a given server profile. The <filename>bootstrap.xml</filename> inturn points to various other configuration files which comprise of the server bootstrap. This defines the core microcontainer beans that are fixed for the lifetime of the server.
</entry>
</row>
<row>
@@ -278,7 +298,7 @@
<filename class="directory">deploy</filename>
</entry>
<entry>
- The <filename class="directory">deploy</filename> directory contains the hot-deployable services (those which can be added to or removed from the running server). It also contains applications for the current server configuration. You deploy your application code by placing application packages (JAR, WAR and EAR files) in the <filename class="directory">deploy</filename> directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically. This may be overridden through the <property>applicationURIs</property> property of the <classname>BootstrapProfileFactory</classname> bean configuration in the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/bootstrap/profile.xml</filename> file.
+ The <filename class="directory">deploy</filename> directory contains the hot-deployable services (those which can be added to or removed from the running server). It also contains applications for the current server profile. You deploy your application code by placing application packages (JAR, WAR and EAR files) in the <filename class="directory">deploy</filename> directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically. This may be overridden through the <property>applicationURIs</property> property of the <classname>BootstrapProfileFactory</classname> bean configuration in the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/bootstrap/profile.xml</filename> file.
</entry>
</row>
<row>
@@ -294,7 +314,7 @@
<filename class="directory">lib</filename>
</entry>
<entry>
- This directory contains JAR files (Java libraries that should not be hot deployed) needed by this server configuration. You can add required library files here for JDBC drivers etc. All JARs in this directory are loaded into the shared classpath at startup. Note that this directory only contains those jars unique to the server configuration. Jars common across the server configurations are now located in <filename class="directory"><JBoss_Home>/common/lib</filename>.
+ This directory contains JAR files (Java libraries that should not be hot deployed) needed by this server profile. You can add required library files here for JDBC drivers etc. All JARs in this directory are loaded into the shared classpath at startup. Note that this directory only contains those jars unique to the server profile. Jars common across the server profiles are now located in <filename class="directory"><JBoss_Home>/common/lib</filename>.
</entry>
</row>
<row>
@@ -327,166 +347,275 @@
</para>
<important>
<para>
- The configuration file used for configuring the default set of ports for the server is available in the <filename>bindingservice.beans/META-INF</filename> subfolder of the <filename>conf</filename> folder. The name of the file is <filename>bindings-jboss-beans.xml</filename>. See the port confiuration section for more details on how to use this file.
+ The configuration file used for configuring the default set of ports for the server is available in the <filename>bindingservice.beans/META-INF</filename> subfolder of the <filename>conf</filename> folder. The name of the file is <filename>bindings-jboss-beans.xml</filename>. See the port configuration section for more details on how to use this file.
</para>
</important>
</section>
<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:
-<screen>[user at localhost <JBoss_Home>]$ tree
-|-- bin
+ The <literal>default</literal> server profile 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>/jboss-as</literal> server profile files:
+<screen>|-- bin
|-- client
|-- common
-| |-- lib
-| | |-- antlr.jar
-| | |-- ... many more jars
+| `-- lib
+| |-- antlr.jar
+| `-- ... many more jars.
|-- docs
-| |-- dtd
-| |-- examples
-| | |-- binding-manager
-| | | `-- sample-bindings.xml
-| | |-- jca
-| | |-- jms
-| | |-- jmx
-| | |-- netboot
-| | | `-- netboot.war
-| | `-- varia
-| | |-- deployment-service
-| | |-- derby-plugin.jar
-| | |-- entity-resolver-manager
-| | | `-- xmlresolver-service.xml
-| | `-- jboss-bindings.xml
-| `-- schema
+| |-- dtd
+| |-- examples
+| | |-- jca
+| | |-- jms
+| | |-- jmx
+| | |-- jmx-remoting
+| | |-- transactions
+| | `-- varia
+| | |-- deployment-service
+| | | |-- build.xml
+| | | |-- deployment-service.sar
+| | | |-- readme.txt
+| | | |-- schema
+| | | | `-- jboss-template-config.xsd
+| | | `-- templates
+| |-- licenses
+| `-- schema
|-- lib
-| |-- commons-codec.jar
-| |-- commons-httpclient.jar
-| |-- commons-logging.jar
-| |-- concurrent.jar
-| |-- endorsed
-| | |-- serializer.jar
-| | |-- xalan.jar
-| | `-- xercesImpl.jar
-| |-- getopt.jar
-| |-- jboss-common.jar
-| |-- jboss-jmx.jar
-| |-- jboss-system.jar
-| |-- jboss-xml-binding.jar
-| `-- log4j-boot.jar
+| |-- concurrent.jar
+| |-- dom4j.jar
+| |-- endorsed
+| | |-- activation.jar
+| | |-- ... more jars.
+| |-- getopt.jar
+| |-- javassist.jar
+| `-- ... many more jars
`-- server
-|-- all
-| |-- conf
-| | |-- bootstrap/
-| | | |-- aop.xml
-| | | |-- bindings.xml
-| | | |-- aop.xml
-| | | |-- classloader.xml
-| | | |-- deployers.xml
-| | | |-- jmx.xml
-| | | |-- profile-repository.xml
-| | | |-- profile.xml
-| | | |-- vfs.xml
-| | |-- bootstrap.xml
-| | |-- bootstrap-norepo.xml
-| | |-- jacorb.properties
-| | |-- java.policy
-| | |-- jax-ws-catalog.xml
-| | |-- jboss-log4j.xml
-| | |-- jboss-service.xml
-| | |-- jbossjta-properties.xml
-| | |-- jndi.properties
-| | |-- login-config.xml
-| | |-- props
-| | | |-- jbossws-roles.properties
-| | | |-- jbossws-users.properties
-| | | |-- jmx-console-roles.properties
-| | | `-- jmx-console-users.properties
-| | |-- standardjboss.xml
-| | |-- standardjbosscmp-jdbc.xml
-| | `-- xmdesc
-| |-- deploy
-| |-- deploy-hasingleton
-| | `-- jms
-| |-- deployers
-| `-- lib
-|-- default
-| |-- conf
-| | |-- bootstrap/
-| | | |-- aop.xml
-| | | |-- bindings.xml
-| | | |-- aop.xml
-| | | |-- classloader.xml
-| | | |-- deployers.xml
-| | | |-- jmx.xml
-| | | |-- profile-repository.xml
-| | | |-- profile.xml
-| | | |-- vfs.xml
-| | |-- bootstrap.xml
-| | |-- bootstrap-norepo.xml
-| | |-- jacorb.properties
-| | |-- java.policy
-| | |-- jax-ws-catalog.xml
-| | |-- jboss-log4j.xml
-| | |-- jboss-service.xml
-| | |-- jbossjta-properties.xml
-| | |-- jndi.properties
-| | |-- login-config.xml
-| | |-- props
-| | | |-- jbossws-roles.properties
-| | | |-- jbossws-users.properties
-| | | |-- jmx-console-roles.properties
-| | | `-- jmx-console-users.properties
-| | |-- standardjboss.xml
-| | |-- standardjbosscmp-jdbc.xml
-| | `-- xmdesc
-| | |-- AttributePersistenceService-xmbean.xml
-| | |-- ClientUserTransaction-xmbean.xml
-| | |-- JNDIView-xmbean.xml
-| | |-- Log4jService-xmbean.xml
-| | |-- NamingBean-xmbean.xml
-| | |-- NamingService-xmbean.xml
-| | |-- TransactionManagerService-xmbean.xml
-| | |-- org.jboss.deployment.JARDeployer-xmbean.xml
-| | |-- org.jboss.deployment.MainDeployer-xmbean.xml
-| | `-- org.jboss.deployment.SARDeployer-xmbean.xml
-| |-- data
-| | |-- hypersonic
-| | |-- jboss.identity
-| | |-- tx-object-store
-| | `-- xmbean-attrs
-| |-- deploy
-| |-- lib
-| |-- log
-| | |-- boot.log
-| | |-- server.log
-| | `-- server.log.2008-08-09
-| |-- tmp
-| `-- work
-| `-- jboss.web
-| `-- localhost
-`-- minimal
-|-- conf
-| |-- bootstrap/
-| |-- bootstrap/aop.xml
-| |-- bootstrap/classloader.xml
-| |-- bootstrap/deployers.xml
-| |-- bootstrap/jmx.xml
-| |-- bootstrap/profile.xml
-| |-- bootstrap.xml
-| |-- jboss-log4j.xml
-| |-- jboss-service.xml
-| |-- jndi.properties
-| `-- xmdesc
-| |-- NamingBean-xmbean.xml
-| `-- NamingService-xmbean.xml
-|-- deploy/
-|-- deploy/hdscanner-jboss-beans.xml
-|-- deployers/
-`-- lib
-|-- jboss-minimal.jar
-|-- jnpserver.jar
-`-- log4j.jar</screen>
+ |-- all
+ | |-- conf
+ | | |-- bindingservice.beans
+ | | |-- bootstrap
+ | | | |-- aop.xml
+ | | | |-- classloader.xml
+ | | | |-- deployers.xml
+ | | | |-- jmx.xml
+ | | | |-- logging.xml
+ | | | |-- profile.xml
+ | | | `-- vfs.xml
+ | | |-- bootstrap.xml
+ | | |-- jacorb.properties
+ | | |-- java.policy
+ | | |-- jax-ws-catalog.xml
+ | | |-- jboss-log4j.xml
+ | | |-- jboss-service.xml
+ | | |-- jbossts-properties.xml
+ | | |-- jndi.properties
+ | | |-- login-config.xml
+ | | |-- props
+ | | | |-- jbossws-roles.properties
+ | | | |-- jbossws-users.properties
+ | | | |-- jmx-console-roles.properties
+ | | | |-- jmx-console-users.properties
+ | | | |-- messaging-roles.properties
+ | | | `-- messaging-users.properties
+ | | |-- standardjboss.xml
+ | | |-- standardjbosscmp-jdbc.xml
+ | | `-- xmdesc
+ | |-- deploy
+ | |-- deploy-hasingleton
+ | |-- deployers
+ | `-- lib
+ |-- default
+ | |-- conf
+ | | |-- bindingservice.beans
+ | | |-- bootstrap
+ | | | |-- aop.xml
+ | | | |-- classloader.xml
+ | | | |-- deployers.xml
+ | | | |-- jmx.xml
+ | | | |-- logging.xml
+ | | | |-- profile.xml
+ | | | `-- vfs.xml
+ | | |-- bootstrap.xml
+ | | |-- java.policy
+ | | |-- jax-ws-catalog.xml
+ | | |-- jboss-log4j.xml
+ | | |-- jboss-service.xml
+ | | |-- jbossts-properties.xml
+ | | |-- jndi.properties
+ | | |-- login-config.xml
+ | | |-- props
+ | | | |-- jbossws-roles.properties
+ | | | |-- jbossws-users.properties
+ | | | |-- jmx-console-roles.properties
+ | | | |-- jmx-console-users.properties
+ | | | |-- messaging-roles.properties
+ | | | `-- messaging-users.properties
+ | | |-- standardjboss.xml
+ | | |-- standardjbosscmp-jdbc.xml
+ | | `-- xmdesc
+ | | |-- AttributePersistenceService-xmbean.xml
+ | | |-- ClientUserTransaction-xmbean.xml
+ | | |-- JNDIView-xmbean.xml
+ | | |-- Log4jService-xmbean.xml
+ | | |-- NamingBean-xmbean.xml
+ | | |-- NamingProviderURLWriter-xmbean.xml
+ | | `-- NamingService-xmbean.xml
+ | |-- deploy
+ | |-- deployers
+ | `-- lib
+ |-- minimal
+ | |-- conf
+ | | |-- bindingservice.beans
+ | | | `-- META-INF
+ | | | `-- bindings-jboss-beans.xml
+ | | |-- bootstrap
+ | | | |-- aop.xml
+ | | | |-- classloader.xml
+ | | | |-- deployers.xml
+ | | | |-- jmx.xml
+ | | | `-- profile.xml
+ | | |-- bootstrap.xml
+ | | |-- jboss-log4j.xml
+ | | |-- jboss-service.xml
+ | | |-- jndi.properties
+ | | `-- xmdesc
+ | | |-- Log4jService-xmbean.xml
+ | | |-- NamingBean-xmbean.xml
+ | | |-- NamingProviderURLWriter-xmbean.xml
+ | | `-- NamingService-xmbean.xml
+ | |-- deploy
+ | |-- deployers
+ | `-- lib
+ |-- production
+ | |-- conf
+ | | |-- bindingservice.beans
+ | | | |-- META-INF
+ | | | | `-- bindings-jboss-beans.xml
+ | | | `-- jboss-bindingservice.jar
+ | | |-- bootstrap
+ | | | |-- aop.xml
+ | | | |-- classloader.xml
+ | | | |-- deployers.xml
+ | | | |-- jmx.xml
+ | | | |-- logging.xml
+ | | | |-- profile.xml
+ | | | `-- vfs.xml
+ | | |-- bootstrap.xml
+ | | |-- jacorb.properties
+ | | |-- java.policy
+ | | |-- jax-ws-catalog.xml
+ | | |-- jboss-log4j.xml
+ | | |-- jboss-service.xml
+ | | |-- jbossts-properties.xml
+ | | |-- jndi.properties
+ | | |-- login-config.xml
+ | | |-- props
+ | | | |-- jbossws-roles.properties
+ | | | |-- jbossws-users.properties
+ | | | |-- jmx-console-roles.properties
+ | | | |-- jmx-console-users.properties
+ | | | |-- messaging-roles.properties
+ | | | `-- messaging-users.properties
+ | | |-- standardjboss.xml
+ | | |-- standardjbosscmp-jdbc.xml
+ | | `-- xmdesc
+ | | |-- AttributePersistenceService-xmbean.xml
+ | | |-- ClientUserTransaction-xmbean.xml
+ | | |-- JNDIView-xmbean.xml
+ | | |-- Log4jService-xmbean.xml
+ | | |-- NamingBean-xmbean.xml
+ | | |-- NamingProviderURLWriter-xmbean.xml
+ | | `-- NamingService-xmbean.xml
+ | |-- deploy
+ | |-- deploy-hasingleton
+ | |-- deployers
+ | |-- farm
+ | `-- lib
+ |-- standard
+ | |-- conf
+ | | |-- bindingservice.beans
+ | | | |-- META-INF
+ | | | | `-- bindings-jboss-beans.xml
+ | | | `-- jboss-bindingservice.jar
+ | | |-- bootstrap
+ | | | |-- aop.xml
+ | | | |-- classloader.xml
+ | | | |-- deployers.xml
+ | | | |-- jmx.xml
+ | | | |-- logging.xml
+ | | | |-- profile.xml
+ | | | `-- vfs.xml
+ | | |-- bootstrap.xml
+ | | |-- jacorb.properties
+ | | |-- java.policy
+ | | |-- jax-ws-catalog.xml
+ | | |-- jboss-log4j.xml
+ | | |-- jboss-service.xml
+ | | |-- jbossts-properties.xml
+ | | |-- jndi.properties
+ | | |-- login-config.xml
+ | | |-- props
+ | | | |-- jbossws-roles.properties
+ | | | |-- jbossws-users.properties
+ | | | |-- jmx-console-roles.properties
+ | | | |-- jmx-console-users.properties
+ | | | |-- messaging-roles.properties
+ | | | `-- messaging-users.properties
+ | | |-- standardjboss.xml
+ | | |-- standardjbosscmp-jdbc.xml
+ | | `-- xmdesc
+ | | |-- AttributePersistenceService-xmbean.xml
+ | | |-- ClientUserTransaction-xmbean.xml
+ | | |-- JNDIView-xmbean.xml
+ | | |-- Log4jService-xmbean.xml
+ | | |-- NamingBean-xmbean.xml
+ | | |-- NamingProviderURLWriter-xmbean.xml
+ | | `-- NamingService-xmbean.xml
+ | |-- deploy
+ | |-- deployers
+ | `-- lib
+ `-- web
+ |-- conf
+ | |-- bindingservice.beans
+ | | |-- META-INF
+ | | | `-- bindings-jboss-beans.xml
+ | | `-- jboss-bindingservice.jar
+ | |-- bootstrap
+ | | |-- aop.xml
+ | | |-- classloader.xml
+ | | |-- deployers.xml
+ | | |-- jmx.xml
+ | | |-- logging.xml
+ | | |-- profile.xml
+ | | `-- vfs.xml
+ | |-- bootstrap.xml
+ | |-- java.policy
+ | |-- jax-ws-catalog.xml
+ | |-- jboss-log4j.xml
+ | |-- jboss-service.xml
+ | |-- jbossts-properties.xml
+ | |-- jndi.properties
+ | |-- login-config.xml
+ | |-- props
+ | | |-- jbossws-roles.properties
+ | | |-- jbossws-users.properties
+ | | |-- jmx-console-roles.properties
+ | | |-- jmx-console-users.properties
+ | | |-- messaging-roles.properties
+ | | `-- messaging-users.properties
+ | |-- standardjboss.xml
+ | |-- standardjbosscmp-jdbc.xml
+ | `-- xmdesc
+ | |-- AttributePersistenceService-xmbean.xml
+ | |-- ClientUserTransaction-xmbean.xml
+ | |-- JNDIView-xmbean.xml
+ | |-- Log4jService-xmbean.xml
+ | |-- NamingBean-xmbean.xml
+ | |-- NamingProviderURLWriter-xmbean.xml
+ | `-- NamingService-xmbean.xml
+ |-- deploy
+ |-- deployers
+ `-- lib
+</screen>
</para>
<section id="The_default_Server_Configuration_File_Set-Contents_of_conf_directory">
@@ -1221,11 +1350,11 @@
<section id="The_all_Server_Configuration_File_Set">
<title>The <literal>all</literal> Server Profile File Set</title>
<para>
- 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.
+ 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>deploy/</literal> directory as shown below.
</para>
<para>
<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>
+ <title>Additional Services in <literal>deploy</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*"/>
@@ -1258,7 +1387,7 @@
</row>
<row>
<entry>
- cluster/farm-deployment-jboss-beans.xml
+ <literal>cluster/farm-deployment-jboss-beans.xml</literal>
</entry>
<entry>
This provides the farm service, which allows for cluster-wide deployment and undeployment of services.
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2009-10-30 05:21:36 UTC (rev 95814)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2009-10-30 05:25:36 UTC (rev 95815)
@@ -11,7 +11,7 @@
There is no <literal>Server Started</literal> message shown at the console when the server is started using the <literal>production</literal> profile. This message can be found in the <filename>server.log</filename> file located in the <filename>JBOSS_DIST/jboss-as/server/production/log</filename> subdirectory.
</para>
<important><title>Remote connection to the JBoss Enterprise Application Platform server</title>
- <para>the JBoss JBoss Enterprise Application Platform now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <command>-b</command> option. To bind to all available interfaces and re-enable the legacy behaviour use <command>./run.sh -b 0.0.0.0</command> on Linux and <command>run.bat -b 0.0.0.0</command>. In any case, be aware you still need to secure your server properly.
+ <para>the JBoss JBoss Enterprise Application Platform now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <command>-b</command> option. To bind to all available interfaces and re-enable the legacy behaviour use <command>./run.sh -b 0.0.0.0</command> on Linux or <command>run.bat -b 0.0.0.0</command> on Windows. In any case, be aware you still need to secure your server properly.
</para>
<para>
Using <command>-b</command> as part of the JBoss Server's command line is equivalent to setting these individual properties: <property>-Djboss.bind.address</property>, <property>-Djava.rmi.server.hostname</property>, <property>-Djgroups.bind_addr</property> and <property>-Dbind.address</property>. Passing <property>-Djboss.bind.address</property> to the Java process as part of the <varname>JAVA_OPTS</varname> variable in the run scripts will not work as it is a JBoss property not a JVM property.
@@ -54,7 +54,7 @@
<section id="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration">
<title>Start the Server With Alternate Configuration</title>
<para>
- Using <literal>run.sh</literal> without any arguments starts the server using the <literal>production</literal> server configuration file set. To start with an alternate configuration file set, pass the name of the server configuration file set (same as the name of the server configuration directory under <literal>JBOSS_DIST/jboss-as/server</literal>) that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>minimal</literal> configuration file set you should specify:
+ Using <literal>run.sh</literal> without any arguments starts the server using the <literal>default</literal> server profile file set. To start with an alternate profile file set, pass the name of the server configuration file set (same as the name of the server configuration directory under <literal>JBOSS_DIST/jboss-as/server</literal>) that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>minimal</literal> profile file set you should specify:
</para>
<programlisting>[bin]$ ./run.sh -c minimal
...
@@ -121,7 +121,7 @@
-H, --halt=<code> Force the VM to halt with a status code
</programlisting>
<para>
- Using the shutdown command requires a server configuration that contains the <literal>jmx-invoker-service.xml</literal> service. Hence you cannot use the shutdown command with the <literal>minimal</literal> configuration.
+ Using the shutdown command requires a server configuration that contains the <literal>jmx-invoker-service.xml</literal> service. Hence you cannot use the shutdown command with the <literal>minimal</literal> profile.
</para>
</section>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2009-10-30 05:21:36 UTC (rev 95814)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2009-10-30 05:25:36 UTC (rev 95815)
@@ -31,14 +31,18 @@
<section id="Server_Structure">
<title>Server Structure</title>
- <para>
+ <para>
+ For a thorough explanation of the structure of the application server, see Migration chapter of the Installation Guide that accompanies this release of JBoss Enterprise Application Platform.
+ </para>
+
+ <!--<para>
Now that you’ve downloaded JBoss and have run the server for the first time, the next thing you will want to know is how the installation is laid out and what goes where. At first glance there seems to be a lot of stuff in there, and it’s not obvious what you need to look at and what you can safely ignore for the time being. To remedy that, we’ll explore the server directory structure, locations of the key configuration files, log files, deployment and so on. It’s worth familiarizing yourself with the layout at this stage as it will help you understand the JBoss service architecture so that you’ll be able to find your way around when it comes to deploying your own applications.
- </para>
+ </para>-->
</section>
<!-- Embedded sections -->
- <xi:include href="Server_Configurations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!--<xi:include href="Server_Configurations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
<xi:include href="Start_Stop_Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- end embedded sections -->
@@ -88,7 +92,7 @@
Hot-deployable services are those which can be added to or removed from the running server. These are placed in the <literal>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</literal> directory. Let’s have a look at a practical example of hot-deployment of services in JBoss.
</para>
<para>
- Start JBoss if it isn’t already running and take a look at the <filename>server/production/deploy</filename> directory. Remove the <filename>mail-service.xml</filename> file and watch the output from the server:
+ Start JBoss if it isn’t already running and take a look at the <filename>server/default/deploy</filename> directory. Remove the <filename>mail-service.xml</filename> file and watch the output from the server:
<programlisting>
13:10:05,235 INFO [MailService] Mail service 'java:/Mail' removed from JNDI
</programlisting>
@@ -103,13 +107,13 @@
<section id="The_JBoss_Server___A_Quick_Tour-Hot-deployment_of_services_in_JBoss-Hot-deployment_configurations">
<title>Hot-deployment configurations</title>
<para>
- Hot deployment of services in the server is controlled by the HDScanner MC bean configured in <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy/hdscanner-jboss-beans.xml</filename> file. For the <literal>production</literal> server configuration the <property>scanPeriod</property> is set to 60 seconds:
+ Hot deployment of services in the server is controlled by the HDScanner MC bean configured in <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy/hdscanner-jboss-beans.xml</filename> file. For the <literal>default</literal> server configuration the <property>scanPeriod</property> is set to 5 seconds:
</para>
<programlisting>
<bean name="HDScanner" class="org.jboss.system.server.profileservice.hotdeploy.HDScanner">
<property name="deployer"><inject bean="ProfileServiceDeployer"/></property>
<property name="profileService"><inject bean="ProfileService"/></property>
- <property name="scanPeriod">60000</property>
+ <property name="scanPeriod">5000</property>
<property name="scanThreadName">HDScanner</property>
</bean>
</programlisting>
@@ -210,7 +214,7 @@
</section>
<section id="The_JBoss_Server___A_Quick_Tour-Bootstrap_Configuration">
<title>Bootstrap Configuration</title>
- <para>The microcontainer bootstrap configuration is described by the <filename>conf/bootstrap.xml</filename> and the <filename>conf/bootstrap/*.xml</filename> it references. Its expected that the number of bootstrap beans will be reduced in the future. Its not expected that you would need to edit the bootstrap configuration files for a typical installation.</para>
+ <para>The microcontainer bootstrap configuration is described by the <filename>conf/bootstrap.xml</filename> and the <filename>conf/bootstrap/*.xml</filename> it references. It is expected that the number of bootstrap beans will be reduced in the future. It is not expected that you would need to edit the bootstrap configuration files for a typical installation.</para>
</section>
<section id="Basic_Configuration_Issues-Core_Services">
<title>Legacy Core Services</title>
@@ -430,7 +434,7 @@
In a typical configuration, the <literal>ports-default</literal> set uses the standard ports (for example, JNDI on port 1099), with <literal>ports-01</literal> increasing each port value by 100 (for example, JNDI on 1199), <literal>ports-02</literal> by 200 and so on.
</para>
<para>
- SBM is configured through the <filename>$JBOSS_DIST/jboss-as/server/bindingservice.beans/META-INF/bindings-jboss-beans.xml</filename> file. The configuration of the <classname>ServiceBindingManager</classname> involves three primary elements :
+ SBM is configured through the <filename>$JBOSS_DIST/jboss-as/server/<instance-name>/conf/bindingservice.beans/ META-INF/bindings-jboss-beans.xml</filename> file. The configuration of the <classname>ServiceBindingManager</classname> involves three primary elements :
</para>
<itemizedlist>
<listitem>
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2009-10-30 05:21:36 UTC (rev 95814)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2009-10-30 05:25:36 UTC (rev 95815)
@@ -139,7 +139,7 @@
Oracle is one of the main players in the commercial database field and most readers will probably have come across it at some point. You can download it freely for non-commercial purposes from <ulink url="http://www.oracle.com/technology/products/database/xe/index.html"/>
</para>
<para>
- In this section, we'll connect the server to Oracle Database 10g Express Edition using the latest JDBC driver (11g) available at <ulink url="http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html"/>
+ In this section, we'll connect the server to Oracle Database 11g Express Edition using the latest JDBC driver (11g) available at <ulink url="http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html"/>
</para>
@@ -147,7 +147,7 @@
<section id="Setting_up_an_XADataSource_with_Oracle_9i-Installing_the_JDBC_Driver_and_Deploying_the_DataSource">
<title>Installing the JDBC Driver and Deploying the DataSource</title>
<para>
- To make the JDBC driver classes available to the JBoss Enterprise Application Platform, copy the archive <filename>ojdbc5.jar</filename> to the lib directory in the default server configuration (assuming that is the server configuration you’re running).
+ To make the JDBC driver classes available to the JBoss Enterprise Application Platform, copy the archive <filename>ojdbc6.jar</filename> to the lib directory in the default server configuration (assuming that is the server configuration you’re running).
</para>
<para>
Then create a text file in the <filename>deploy</filename> directory called <filename>oracle-ds.xml</filename> with the following datasource descriptor :
@@ -220,12 +220,12 @@
<section><title>Configuring a datasource for Microsoft SQL Server 200x</title>
- <para>In this section, we'll connect the server to MS SQL Server 2000 using the latest JDBC driver (v1.2) available at <ulink url="http://msdn2.microsoft.com/en-us/data/aa937724.aspx"/>.
+ <para>In this section, we'll connect the server to MS SQL Server 2005 using the latest JDBC driver (v2.0) available at <ulink url="http://msdn2.microsoft.com/en-us/data/aa937724.aspx"/>.
</para>
<section><title>Installing the JDBC Driver and Deploying the DataSource</title>
<para>
- To make the JDBC driver classes available to the JBoss Enterprise Application Platform, copy the archive <filename>sqljdbc.jar</filename> from the <filename>sqljdbc_1.2</filename> distribution to the <filename>lib</filename> directory in the default server configuration (assuming that is the server configuration you’re running).
+ To make the JDBC driver classes available to the JBoss Enterprise Application Platform, copy the archive <filename>sqljdbc.jar</filename> from the <filename>sqljdbc_2.0</filename> distribution to the <filename>lib</filename> directory in the default server configuration (assuming that is the server configuration you’re running).
</para>
<para>
Then create a text file in the <literal>deploy</literal> directory called <literal>mssql-ds.xml</literal> with the following datasource descriptor :
More information about the jboss-cvs-commits
mailing list