[jboss-cvs] JBossAS SVN: r99640 - projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Jan 20 01:40:41 EST 2010
Author: gmeintjes
Date: 2010-01-20 01:40:41 -0500 (Wed, 20 Jan 2010)
New Revision: 99640
Modified:
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Preface.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
Log:
Updated to reflect Web rather than Application
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -4,11 +4,11 @@
<chapter id="EJB3_Caveats">
<title>
- EJB3 Caveats in JBoss Enterprise Application Platform 5.0
+ EJB3 Caveats in JBoss Enterprise Web Platform 5.0
</title>
<para>
- There are a number of implementation features that you should be aware of when developing applications for JBoss Enterprise Application Platform 5.0.
+ There are a number of implementation features that you should be aware of when developing applications for JBoss Enterprise Web Platform 5.0.
</para>
<!--<section>
@@ -28,7 +28,7 @@
</title>
<para>
- 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.
+ JBoss Enterprise Web Platform 5.0 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/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -3,7 +3,7 @@
<section id="The_JNDIView_Service">
<title>The JNDIView Service</title>
<para>
- The JNDIView Service is enabled by default in the JBoss Enterprise Application Platform. This service is listed in the <literal>jmx-console</literal> (<ulink url="http://localhost:8080/jmx-console">http://localhost:8080/jmx-console</ulink>). Navigate to the <filename>jboss:service=JNDIView</filename> Mbean and click on that link. On the MBean operations page, you will find the <methodname>list</methodname> method. Click on the <guibutton>Invoke</guibutton> button adjacent to this <methodname>list</methodname> method.
+ The JNDIView Service is enabled by default in the JBoss Enterprise Web Platform. This service is listed in the <literal>jmx-console</literal> (<ulink url="http://localhost:8080/jmx-console">http://localhost:8080/jmx-console</ulink>). Navigate to the <filename>jboss:service=JNDIView</filename> Mbean and click on that link. On the MBean operations page, you will find the <methodname>list</methodname> method. Click on the <guibutton>Invoke</guibutton> button adjacent to this <methodname>list</methodname> method.
</para>
<para>
The list operation will display the JNDI tree contents. The output will look something similar to this:
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Preface.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Preface.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -4,10 +4,10 @@
<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. 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.
+ JBoss Enterprise Web 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.
+ Because it is Java-based, JBoss Web 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.
</para>
<!-- <para>
Installing JBoss Enterprise Application Platform is simple and easy. You can have it installed and running in no time. This guide will teach you to install and get started with the JBoss Application Server.</para> -->
@@ -15,7 +15,7 @@
<section id="Book-We_Need_Feedback">
<title>Help Contribute</title>
<para>
- If you find a typographical error or if you have thought of a way to make this manual better, submit a report in JIRA: <ulink url="http://jira.jboss.com">http://jira.jboss.com</ulink> against the product <citetitle>JBoss Enterprise Application Platform</citetitle> and component <citetitle>Documentation</citetitle>.
+ If you find a typographical error or if you have thought of a way to make this manual better, submit a report in JIRA: <ulink url="http://jira.jboss.com">http://jira.jboss.com</ulink> against the product <citetitle>JBoss Enterprise Web Platform</citetitle> and component <citetitle>Documentation</citetitle>.
</para>
<para>
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -7,8 +7,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.2</revnumber>
- <date>Thu Oct 29 2009</date>
+ <revnumber>1.3</revnumber>
+ <date>Thu Jan 20 2010</date>
<author>
<firstname>Laura</firstname>
<surname>Bailey</surname>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -14,7 +14,7 @@
You don’t need a detailed understanding of the microcontainer to use JBoss, but it’s worth keeping a picture of this basic architecture in mind as it is central to the way JBoss works.
</para>
<para>
- The JBoss Enterprise Application Platform ships with six different server profiles. Within the <literal><JBoss_Home>/server</literal> directory, you will find six subdirectories:
+ The JBoss Enterprise Web Platform (JBoss EWP) 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>default</literal> profile is the one used if you don’t specify another one when starting up the server.
</para>
<para>
@@ -161,7 +161,7 @@
<section id="Server_Directory_Structure">
<title>Server Directory Structure</title>
<para>
- Installing JBoss Enterprise Application Platform creates a top level directory, which will be named <filename>jboss-eap-<version></filename> if you used the zip installation method, and will be named according to your specification if you used the GUI installer. Throughout this guide we refer to this top-level directory as the <filename>JBOSS_DIST</filename> directory.
+ Installing JBoss EWP creates a top level directory, which will be named <filename>jboss-ewp-<version></filename> if you used the zip installation method, and will be named according to your specification if you used the GUI installer. Throughout this guide we refer to this top-level directory as the <filename>JBOSS_DIST</filename> directory.
</para>
<para>
<table id="JBOSS_DIST_jboss-as_directory_structure">
@@ -201,7 +201,7 @@
Stores configuration files and JAR files that may be used by a Java client application (running outside JBoss) or an external web container. You can select archives as required or use <filename>jbossall-client.jar</filename>.
</entry>
<entry>
- Unlike the earlier 4.x versions of the JBoss Enterprise Application Platform, the <filename>jbossall-client.jar</filename> is now a <filename>MANIFEST</filename> only JAR file. So if the client application copies over the <filename>jbossall-client.jar</filename> to its classpath, then it also has to copy over all the other jar files listed in the <filename>META-INF/MANIFEST.MF</filename> file of <filename>jbossall-client.jar</filename>. Furthermore, all these JARs, including the <filename>jbossall-client.jar</filename>, must be placed in the same folder in the client classpath.
+ Unlike the earlier 4.x versions of the JBoss EWP, the <filename>jbossall-client.jar</filename> is now a <filename>MANIFEST</filename> only JAR file. So if the client application copies over the <filename>jbossall-client.jar</filename> to its classpath, then it also has to copy over all the other jar files listed in the <filename>META-INF/MANIFEST.MF</filename> file of <filename>jbossall-client.jar</filename>. Furthermore, all these JARs, including the <filename>jbossall-client.jar</filename>, must be placed in the same folder in the client classpath.
</entry>
</row>
<row>
@@ -282,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 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.
+ 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> in turn 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>
@@ -306,7 +306,7 @@
<filename class="directory">deployers</filename>
</entry>
<entry>
- In the Enterprise Application Platform 5, unlike earlier versions, the deployers (which are responsible for parsing and deploying deployments) are located separately in the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deployers</filename> folder. This folder contains various deployer JAR files and their configurations in <filename>*-jboss-beans.xml</filename> files.
+ In JBoss EWP 5.0, unlike earlier versions, the deployers (which are responsible for parsing and deploying deployments) are located separately in the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deployers</filename> folder. This folder contains various deployer JAR files and their configurations in <filename>*-jboss-beans.xml</filename> files.
</entry>
</row>
<row>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -10,8 +10,8 @@
<para>
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 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.
+<important><title>Remote connection to the JBoss Enterprise Web Platform server</title>
+ <para>The JBoss Enterprise Web Platform (EWP) 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.
@@ -37,13 +37,13 @@
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.client.
gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
- CLASSPATH: /home/user/jboss-as-version/jboss-as/bin/run.jar
+ CLASSPATH: /home/user/jboss-web-version/jboss-as/bin/run.jar
=========================================================================
</programlisting>
-<para>More options for the JBoss Enterprise Application Platform <literal>run</literal> script are discussed in <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/> below.</para>
+<para>More options for the JBoss Enterprise Web Platform <literal>run</literal> script are discussed in <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/>.</para>
<note>
<para>
There is no <emphasis>Server Started</emphasis> message shown at the console when the server is started using the <literal>production</literal> profile. This message may be observed in the <filename>server.log</filename> file located in the <filename class="directory">server/production/log</filename> subdirectory.
@@ -128,14 +128,14 @@
<section id="Starting_and_Stopping_the_Server-Running_as_a_Service_under_Microsoft_Windows">
<title> Running as a Service under Microsoft Windows </title>
<para>
- The JBoss Enterprise Application Platform 5 comes with the necessary files to configure the server to run as a service under windows. Distributed with JBoss Native, this enables the JBoss Enterprise Application Platform 5 to be run as a service on Windows operating system. To install the service navigate to <filename>JBOSS_DIST/jboss-as/bin</filename> and locate the <filename>service.bat</filename> file. Run the following command in a command prompt:
+ The JBoss Enterprise Web Platform 5 comes with the necessary files to configure the server to run as a service under windows. Distributed with JBoss Native, this enables the JBoss Enterprise Web Platform 5 to be run as a service on Windows operating system. To install the service navigate to <filename>JBOSS_DIST/jboss-as/bin</filename> and locate the <filename>service.bat</filename> file. Run the following command in a command prompt:
</para>
<programlisting>
./service.bat install
</programlisting>
<!-- JBoss Application Server in this instance should be left as is and not changed to the EAP name -->
<para>
- This commands installs the JBoss Enterprise Application Platform as a service. Under the Windows services list you will find this listed by the short name <filename>JBAS50SVC</filename> and the long name <filename>JBoss Application Server 5.1</filename>.
+ This commands installs the JBoss Enterprise Web Platform as a service. Under the Windows services list you will find this listed by the short name <filename>JBAS50SVC</filename> and the long name <filename>JBoss Application Server 5.1</filename>.
</para>
<para>
Once the service is installed successfully, you can control and configure the service from the <literal>Windows Services Manager</literal> application. You can configure it to start automatically when the system is booted. You can even manually start and stop the service from the <literal>Windows Services Manager</literal>.
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -32,7 +32,7 @@
<section id="Server_Structure">
<title>Server Structure</title>
<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.
+ 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 Web Platform.
</para>
<!--<para>
@@ -420,7 +420,7 @@
The non-core, hot-deployable services are added to the <filename class="directory">deploy</filename> directory. They can be either XML descriptor files, <filename>*-service.xml, *-jboss-beans.xml</filename>, MC <filename>.beans</filename> archive, or JBoss Service Archive (SAR) files. SARs contains an <filename>META-INF/jboss-service.xml</filename> descriptor and additional resources the service requires (for example, classes, library JAR files or other archives), all packaged up into a single archive. Similarly, a <filename>.beans</filename> archive contains a <filename>META-INF/jboss-beans.xml</filename> and additional resources.
</para>
<para>
- Detailed information on all these services can be found in the <emphasis>JBoss Enterprise Application Platform: Aministration and Configuration Guide</emphasis>, which also provides comprehensive information on server internals and the implementation of services such as JTA and the J2EE Connector Architecture (JCA).
+ Detailed information on all these services can be found in the <emphasis>JBoss Enterprise Web Platform: Aministration and Configuration Guide</emphasis>, which also provides comprehensive information on server internals and the implementation of services such as JTA and the J2EE Connector Architecture (JCA).
</para>
</section>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2010-01-20 06:28:36 UTC (rev 99639)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2010-01-20 06:40:41 UTC (rev 99640)
@@ -5,13 +5,13 @@
<chapter id="Using_other_Databases">
<title>Using other Databases</title>
<para>
- In the previous chapters, we’ve been using the JBoss Enterprise Application Platform server default datasource in our applications. This datasource is configured to use the embedded Hypersonic database instance shipped by default with the distribution. This datasource is bound to the JNDI name <literal>java:/DefaultDS</literal> and its descriptor is named <literal>hsqldb-ds.xml</literal> under the deploy directory
+ In the previous chapters, we’ve been using the JBoss Enterprise Web Platform server default datasource in our applications. This datasource is configured to use the embedded Hypersonic database instance shipped by default with the distribution. This datasource is bound to the JNDI name <literal>java:/DefaultDS</literal> and its descriptor is named <literal>hsqldb-ds.xml</literal> under the deploy directory
</para>
<para>
- Having a database included with JBoss Enterprise Application Platform is very convenient for running the server and examples out-of-the-box. However, this database is not a production quality database and as such should not be used with enterprise-class deployments. As a consequence of this JBoss Support does not provide any official support for Hypersonic.
+ Having a database included with JBoss Enterprise Web Platform is very convenient for running the server and examples out-of-the-box. However, this database is not a production quality database and as such should not be used with enterprise-class deployments. As a consequence of this JBoss Support does not provide any official support for Hypersonic.
</para>
<para>
- In this chapter we will explain in details how to configure and deploy a datasource to connect the JBoss Enterprise Application Platform to the most popular database servers available on the market today.
+ In this chapter we will explain in detail how to configure and deploy a datasource to connect the JBoss Enterprise Web Platform to some of the popular database servers currently available.
</para>
<section id="Using_other_Databases-DataSource_Configuration_Files">
@@ -91,7 +91,7 @@
<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>mysql-connector-java-5.1.8-bin.jar</filename> from the <literal>Connector/J</literal> distribution to the <literal>lib</literal> directory in the <literal>default</literal> server configuration (assuming that is the server configuration you’re running).
+ To make the JDBC driver classes available to the JBoss Enterprise Web Platform, copy the archive <filename>mysql-connector-java-5.1.8-bin.jar</filename> from the <literal>Connector/J</literal> distribution to the <literal>lib</literal> directory in the <literal>default</literal> server configuration (assuming that is the server configuration you’re running).
</para>
<para>
Then create a file in the deploy directory called <filename>mysql-ds.xml</filename> with the following datasource configuration. Note that the databse user name and password corresponds to the MySQL user that we created in the previous section:
@@ -190,7 +190,7 @@
<section id="Setting_up_an_XADataSource_with_Oracle_9i-Testing_the_Oracle_DataSource">
<title>Testing the Oracle DataSource</title>
<para>
- Before you can verify the datasource configuration, Oracle XE should be reconfigured to avoid port conflict with the JBoss Enterprise Application Platform as by default they both start a web server on port 8080.
+ Before you can verify the datasource configuration, Oracle XE should be reconfigured to avoid port conflict with the JBoss Enterprise Web Platform as by default they both start a web server on port 8080.
</para>
<para>Open up an Oracle SQLcommand line and execute the following commands:
</para>
@@ -225,7 +225,7 @@
<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_2.0</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 Web 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 :
@@ -261,7 +261,7 @@
</section>
-<section id="configuring_jbossmessaging_persistence_manager"><title>Configuring JBoss Messaging Persistence Manager</title>
+<!-- <section id="configuring_jbossmessaging_persistence_manager"><title>Configuring JBoss Messaging Persistence Manager</title>
<para>
The persistence manager of JBoss Messaging uses the default datasource to create tables to store messages, transaction data and other indexes. Configuration of "persistence" is grouped in <filename>xxx-persistence-service.xml</filename> files. JBoss Enterprise Application Platform ships with a default <filename>hsqldb-persistence-service.xml</filename> file, which configures the Messaging server to use the Hypersonic database instance that ships by default with the JBoss Enterprise Application Platform.
</para>
@@ -284,7 +284,7 @@
</para>
-</section>
+</section> -->
<section id="creating_a_jdbc_client"><title>Creating a JDBC client</title>
@@ -322,7 +322,7 @@
}]]> %> </programlisting>
Open up a web browser and hit the url: <ulink url="http://localhost:8080/jdbcclient/client.jsp"/>.
-A list of users and password should show up as a result of the JDBC query:
+A list of users and passwords should show up as a result of the JDBC query:
<screen>
dynsub | dynsub
guest | guest
More information about the jboss-cvs-commits
mailing list