[jboss-cvs] JBossAS SVN: r100845 - in projects/docs/enterprise/EWP_5.0: Getting_Started_Guide/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 10 20:08:57 EST 2010
Author: laubai
Date: 2010-02-10 20:08:56 -0500 (Wed, 10 Feb 2010)
New Revision: 100845
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml
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/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/Start_Stop_Server.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
Log:
Updated Getting Started Guide.
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -20,7 +20,7 @@
<para>
Please note that in this chapter, we explain how to use alternative databases to support all
services in JBoss Enterprise Web Platform. This includes all the system level services such
- as EJB and JMS. For individual applications (e.g., WAR or EAR) deployed in
+ as EJB<!-- and JMS-->. For individual applications (e.g., WAR or EAR) deployed in
JBoss Enterprise Web Platform, you can still use any backend database by setting up the
appropriate data source connection. </para>
@@ -62,7 +62,7 @@
</para>
<formalpara><title>Enable JAVA services</title>
<para>
- To use any Java service like JMS, CMP, timers etc. configured with Sybase, Java should be enabled on Sybase Adaptive Server. To do this use:
+ To use any Java service like <!--JMS, -->CMP, timers, etc. configured with Sybase, Java should be enabled on Sybase Adaptive Server. To do this use:
<screen><command>sp_configure "enable java",1</command></screen>
Refer to the sybase manuals for more information.
@@ -612,7 +612,7 @@
<term><literal><![CDATA[security-domain-and-application]]></literal></term>
<listitem>
<para>
- Uses the identified login module configured in <filename>conf/login-module.xml</filename> and other connection request information supplied by the application, for example JMS Queues and Topics.
+ Uses the identified login module configured in <filename>conf/login-module.xml</filename> and other connection request information supplied by the application<!--, for example JMS Queues and Topics-->.
</para>
</listitem>
</varlistentry>
@@ -715,12 +715,12 @@
</section>
</section>
- <section>
+ <!--<section>
<title>Change Database for the JMS Services</title>
<para>The JMS service in the JBoss Enterprise Web Platform uses relational databases to persist its messages. For improved performance, we should change the JMS service to take advantage of the external database. To do that, we need to replace the file <filename>$JBOSS_HOME/server/$PROFILE/deploy/messaging/$DATABASE-persistence-service.xml</filename> with the file <filename>$JBOSS_HOME/docs/examples/jms/$DATABASE-persistence-service.xml</filename> depending on your external database.
- <!--To do that, we need to replace the file <literal><JBoss_Home>/server/all/deploy/jms-singleton/hsqldb-jdbc2-service.xml</literal> with a file in <literal><JBoss_Home>/docs/examples/jms/</literal> depending on your external database. Notice that if you are using the <literal>default</literal> server profile, the file path is <literal><JBoss_Home>/server/default/deploy/jms/hsqldb-jdbc2-service.xml</literal>.--></para>
+ To do that, we need to replace the file <literal><JBoss_Home>/server/all/deploy/jms-singleton/hsqldb-jdbc2-service.xml</literal> with a file in <literal><JBoss_Home>/docs/examples/jms/</literal> depending on your external database. Notice that if you are using the <literal>default</literal> server profile, the file path is <literal><JBoss_Home>/server/default/deploy/jms/hsqldb-jdbc2-service.xml</literal>.</para>
<itemizedlist>
<listitem><para>MySQL: <filename>mysql-persistence-service.xml</filename></para></listitem>
@@ -731,12 +731,12 @@
<listitem><para>MS SQL Server: <filename>mssql-persistence-service.xml</filename></para></listitem>
</itemizedlist>
-<!-- <note>
+ <note>
<title>What about the hsqldb-jdbc-state-service.xml file?</title>
<para>Despite its name, the <literal>hsqldb-jdbc-state-service.xml</literal> file applies to all databases. So, there is no need to use a special <literal>jdbc-state-service.xml</literal> for each database.</para>
- </note>-->
+ </note>
- </section>
+ </section>-->
<section>
<title>Support Foreign Keys in CMP Services</title>
@@ -825,7 +825,7 @@
<section>
<title>Change Other JBoss Enterprise Web Platform Services to use the External Database</title>
- <para>Besides JMS, CMP, and JPA, we still need to hook up the rest of JBoss services with the external database. There are two ways to do it. One is easy but inflexible. The other is flexible but requires more steps. Now, let's discuss those two approaches respectively.</para>
+ <para>Other services may also need to be configured to interact with the external database. <!--Besides JMS, CMP, and JPA, we still need to hook up the rest of JBoss services with the external database.--> There are two ways to do it. One is easy but inflexible. The other is flexible but requires more steps. Now, let's discuss those two approaches respectively.</para>
<section>
<title>The Easy Way</title>
@@ -884,7 +884,7 @@
<listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml</filename>: This file configures the UUDI service.</para></listitem>
- <listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/messaging/messaging-jboss-beans.xml</filename> and <filename>$JBOSS_HOME/server/$PROFILE/deploy/messaging/persistence-service.xml</filename>: Those files configure the JMS persistence service as we discussed earlier.</para></listitem>
+<!-- <listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/messaging/messaging-jboss-beans.xml</filename> and <filename>$JBOSS_HOME/server/$PROFILE/deploy/messaging/persistence-service.xml</filename>: Those files configure the JMS persistence service as we discussed earlier.</para></listitem>-->
<!-- ${jboss.dist}/server/${server}/deploy/schedule-manager-service.xml -->
</itemizedlist>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -7,7 +7,7 @@
<subtitle>for JBoss Enterprise Web Platform 5.0</subtitle>
<edition>1</edition>
<issuenum>1</issuenum>
- <pubsnumber>1.5</pubsnumber>
+ <pubsnumber>1.6</pubsnumber>
<productname>JBoss Enterprise Web Platform</productname>
<productnumber>5.0</productnumber>
<!-- <pubdate>, 2009</pubdate> -->
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -84,7 +84,7 @@
<title>Client-side interceptor architecture</title>
<para>
Most remote services provided by the JBoss Enterprise Web Platform, including
- JNDI, <!--EJB,-->JMS, RMI and JBoss Remoting, require the client to obtain
+ JNDI and RMI,<!--EJB, JMS, JBoss Remoting--> require the client to obtain
(that is, to look up and download) a remote proxy object. The proxy object
is generated by the server and it implements the business interface of
the service. The client then makes local method calls against the proxy
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -283,10 +283,10 @@
to configure the lookup of resources is to bind the resources to the
environment naming context of the bean or webapp performing the lookup. The
binding can then be configured to use HA-JNDI instead of a local mapping.
- Following is an example of doing this for a JMS connection factory and
- queue (the most common use case for this kind of thing).</para>
+ <!--Following is an example of doing this for a JMS connection factory and
+ queue (the most common use case for this kind of thing).--></para>
- <para>Within the bean definition in the <!--<filename>ejb-jar.xml</filename> or in the-->
+<!-- <para>Within the bean definition in the <filename>ejb-jar.xml</filename> or in the
WAR's <filename>web.xml</filename>,
you will need to define two <literal>resource-ref</literal> mappings, one for the connection
factory and one for the destination.</para>
@@ -308,7 +308,7 @@
queue by looking up <literal>java:comp/env/jms/Queue</literal>.
</para>
<para>
-Within the JBoss-specific deployment descriptor (<!--jboss.xml for EJBs, -->
+Within the JBoss-specific deployment descriptor (jboss.xml for EJBs,
<filename>jboss-web.xml</filename>) these references need to be mapped to a URL
that makes use of HA-JNDI.
</para>
@@ -330,7 +330,7 @@
to use the value of the <varname>jboss.bind.address</varname> system property
when determining the URL. That system property is itself set to whatever value
you assign to the <code>-b</code> command line option when you start JBoss Enterprise Web Platform.
-</para>
+</para>-->
<important><title>Why do this programmatically and not just put this in a jndi.properties file?</title>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -45,7 +45,7 @@
<listitem>
<indexterm><primary>Service Archive</primary><secondary>*-service.xml deployment type</secondary></indexterm>
- <para>You can deploy <filename>*-service.xml</filename> files with MBean service definitions. If you have the appropriate JAR files available in the deploy or lib directories, the MBeans specified in the XML files will be started. This is the way you deploy many JBoss Enterprise Web Platform internal services that have not been updated to support POJO style deployment, such as the JMS queues.</para></listitem>
+ <para>You can deploy <filename>*-service.xml</filename> files with MBean service definitions. If you have the appropriate JAR files available in the deploy or lib directories, the MBeans specified in the XML files will be started. This is the way you deploy many JBoss Enterprise Web Platform internal services that have not been updated to support POJO style deployment<!--, such as the JMS queues.--></para></listitem>
<listitem><para>You can also deploy JAR files containing EJBs or other service objects directly in JBoss Enterprise Web Platform. The list of suffixes that are recognized as JAR files is specified in the <filename>conf/bootstrap/deployers.xml</filename> <literal>JARStructure</literal> bean constructor set.</para></listitem>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -311,7 +311,7 @@
</section>
- <section id="EJB3_Services-Message_Driven_Beans">
+ <!--<section id="EJB3_Services-Message_Driven_Beans">
<title>Message Driven Beans</title>
<para>Messaging driven beans are specialized EJB3 beans that receive service requests via JMS messages instead of proxy method calls from the "stub". So, a crucial configuration parameter for the message driven bean is to specify which JMS message queue its listens to. When there is an incoming message in the queue, the server invokes the beans's <literal>onMessage()</literal> method, and passes in the message itself for processing. The bean class specifies the JMS queue it listens to in the @MessageDriven annotation. The queue is registered under the local JNDI java:comp/env/ name space.</para>
@@ -353,6 +353,7 @@
e.printStackTrace ();
}
+
TextMessage msg = sess.createTextMessage(...);
sender = sess.createSender(queue);
@@ -362,7 +363,7 @@
<para>Please refer to the JMS specification or books to learn how to program in the JMS API.</para>
- </section>
+ </section>-->
<section id="EJB3_Services-Package_and_Deploy_EJB3_Services">
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Introduction.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -159,12 +159,12 @@
</listitem>
<listitem>
<para>
- Complex web applications with JSPs/Servlets, Seam, Enterprise Java Beans (EJB), Java Messaging (JMS), caching, etc.
+ Complex web applications with JSPs/Servlets, Seam, Enterprise Java Beans (EJB), <!--Java Messaging (JMS),--> caching, etc.
</para>
</listitem>
<listitem>
<para>
- Cross application middleware (JMS, Corba, JMX, etc.)
+ Cross application middleware (Corba, JMX, etc.)
</para>
</listitem>
</itemizedlist>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/JGroups.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -40,7 +40,7 @@
<para>
<orderedlist>
<listitem>
- <para>Transport protocols: UDP (IP Multicast), TCP, JMS </para>
+ <para>Transport protocols: UDP (IP Multicast), TCP</para>
</listitem>
<listitem>
<para>Fragmentation of large messages </para>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -8,7 +8,7 @@
<simpara>
<revhistory>
<revision>
- <revnumber>2.5</revnumber>
+ <revnumber>2.6</revnumber>
<date>Wed Feb 10 2010</date>
<author>
<firstname>Laura</firstname>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml 2010-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -5,7 +5,7 @@
<title>Getting Started Guide</title>
<subtitle>for Use with JBoss Enterprise Web Platform 5.0</subtitle>
<edition>1.0</edition>
- <pubsnumber>33.1</pubsnumber>
+ <pubsnumber>33.2</pubsnumber>
<productname>JBoss Enterprise Web Platform</productname>
<productnumber>5.0</productnumber>
<!-- <pubdate>, 2009</pubdate> --><isbn>N/A</isbn>
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-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/EJB3_Caveats.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -17,7 +17,7 @@
</title>
<para>
- The Release Notes for JBoss Enterprise Application Platform may contain updated information on new and modified features. The Release Notes also include links to issues in JIRA for issue details and information about workarounds.
+ The Release Notes for JBoss Enterprise Web Platform may contain updated information on new and modified features. The Release Notes also include links to issues in JIRA for issue details and information about workarounds.
</para>
</section>-->
@@ -28,11 +28,11 @@
</title>
<para>
- 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.
+ JBoss Enterprise Web Platform 5.0 fully supports the entire Java 5 Enterprise Edition specification. JBoss Enterprise Web Platform 4.3 implemented EJB3 functionality by way of an EJB MBean container running as a plugin in the JBoss Enterprise Web Platform. This had certain implications for application development.
</para>
<para>
- The EJB3 plugin injects references to an EntityManager and @EJB references from one EJB object to another. However this support is limited to the EJB3 MBean and the JAR files it manages. Any JAR files which are loaded from a WAR (such as Servlets, JSF backing beans, and so forth) do not undergo this processing. The Java 5 Enterprise Edition standard specifies that a Servlet can reference a Session Bean through an @EJB annotated reference, this was not implemented in Enterprise Application Platform 4.3.
+ The EJB3 plugin injects references to an EntityManager and @EJB references from one EJB object to another. However this support is limited to the EJB3 MBean and the JAR files it manages. Any JAR files which are loaded from a WAR (such as Servlets, JSF backing beans, and so forth) do not undergo this processing. The Java 5 Enterprise Edition standard specifies that a Servlet can reference a Session Bean through an @EJB annotated reference, this was not implemented in Enterprise Web Platform 4.3.
</para>
<!--
<para>
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-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Preface.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -10,12 +10,12 @@
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> -->
+ Installing JBoss Enterprise Web 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> -->
<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 Web 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="https://jira.jboss.com/jira/browse/JBPAPP">https://jira.jboss.com/jira/browse/JBPAPP</ulink> against the product version <citetitle>EWP 5.0.0</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-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -7,8 +7,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.6</revnumber>
- <date>Thu Jan 21 2010</date>
+ <revnumber>1.7</revnumber>
+ <date>Thu Feb 11 2010</date>
<author>
<firstname>Laura</firstname>
<surname>Bailey</surname>
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-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -18,7 +18,7 @@
</para>
</important>
<para>
- For more information including setting up multiple JBoss server instances on one machine and hosting multiple domains with JBoss, please refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_And_Configuration_Guide/index.html">Administration and Configuration Guide</ulink>.
+ For more information including setting up multiple JBoss server instances on one machine and hosting multiple domains with JBoss, please refer to the <citetitle>Administration and Configuration Guide</citetitle> for this distribution of JBoss Enterprise Web Platform.
</para>
<para>
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-02-11 01:07:38 UTC (rev 100844)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2010-02-11 01:08:56 UTC (rev 100845)
@@ -17,7 +17,7 @@
<section id="Using_other_Databases-DataSource_Configuration_Files">
<title>DataSource Configuration Files</title>
<para>
- Datasource configuration file names end with the suffix <filename>-ds.xml</filename> so that they will be recognized correctly by the JCA deployer. The <filename>docs/example/jca</filename> directory contains sample files for a wide selection of databases and it is a good idea to use one of these as a starting point. For a full description of the configuration format, the best place to look is the DTD file <filename>docs/dtd/jboss-ds_1_5.dtd</filename>. Additional documentation on the files and the JBoss JCA implementation can also be found in the JBoss Enterprise Application Platform Administration and Server Configuration Guide available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"/>.
+ Datasource configuration file names end with the suffix <filename>-ds.xml</filename> so that they will be recognized correctly by the JCA deployer. The <filename>docs/example/jca</filename> directory contains sample files for a wide selection of databases and it is a good idea to use one of these as a starting point. For a full description of the configuration format, the best place to look is the DTD file <filename>docs/dtd/jboss-ds_1_5.dtd</filename>. Additional documentation on the files and the JBoss JCA implementation can also be found in the JBoss Enterprise Web Platform <citetitle>Administration and Configuration Guide</citetitle> available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/"/>.
</para>
<para>
Local transaction datasources are configured using the <literal>local-tx-datasource</literal> element and XA-compliant ones using <literal>xa-tx-datasource</literal>. The example file <filename>generic-ds.xml</filename> shows how to use both types and also some of the other elements that are available for things like connection pool configuration. Examples of both local and XA configurations are available for Oracle, DB2 and Informix.
@@ -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>ojdbc6.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 Web 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 :
@@ -202,7 +202,7 @@
<para>
The web server started by Oracle XE to provide http-based administration tools is now running on port 8090.
- Start the JBoss Enterprise Application Platform server instance as you would normally do. You are now ready to use the test client to verify the proper installation of your datasource.
+ Start the JBoss Enterprise Web Platform server instance as you would normally do. You are now ready to use the test client to verify the proper installation of your datasource.
</para>
</section>
@@ -253,7 +253,7 @@
<!-- <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.
+ 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 Web 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 Web Platform.
</para>
<para>
You can view the <filename>hsqldb-persistence-service.xml</filename> file in configurations based on the <emphasis>all</emphasis> or <emphasis>default</emphasis> configurations:
More information about the jboss-cvs-commits
mailing list