[jboss-cvs] JBossAS SVN: r95810 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 29 22:26:23 EDT 2009
Author: laubai
Date: 2009-10-29 22:26:23 -0400 (Thu, 29 Oct 2009)
New Revision: 95810
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
Log:
several corrections and additions to datasource chapter.
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml 2009-10-30 02:01:35 UTC (rev 95809)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml 2009-10-30 02:26:23 UTC (rev 95810)
@@ -8,7 +8,7 @@
<title>How to Use Alternative Databases</title>
<para>
<indexterm><primary>Configuration</primary><secondary>databases</secondary></indexterm>
-JBoss utilizes the Hypersonic database as its default database. While this is good for development and prototyping, you or your company will probably require another database to be used for production. This chapter covers configuring JBoss Enterprise Application Platform to use alternative databases. We cover the procedures for all officially supported databases on the JBoss Enterprise Application Platform. They include: MySQL 5.0, PostgreSQL 8.1, Oracle 9i and 10g R2, DB2 7.2 and 8, Sybase ASE 12.5, as well as MS SQL 2005.
+JBoss utilizes the Hypersonic database as its default database. While this is good for development and prototyping, you or your company will probably require another database to be used for production. This chapter covers configuring JBoss Enterprise Application Platform to use alternative databases. We cover the procedures for all officially supported databases on the JBoss Enterprise Application Platform. They include: MySQL 5.0, MySQL 5.1, PostgreSQL 8.2.4, PostgreSQL 8.3.5, Oracle 10g, Oracle 11g R2, Oracle 11g R2 RAC, DB2 9.7, Sybase ASE 15.0, and MS SQL 2005 and 2008.
</para>
<para>Please note that in this chapter, we explain how to use alternative databases to support all services in JBoss Enterprise Application Platform. This includes all the system level services such as EJB and JMS. For individual applications (e.g., WAR or EAR) deployed in JBoss Enterprise Application Platform, you can still use any backend database by setting up the appropriate data source connection. </para>
@@ -633,21 +633,23 @@
<section>
<title>Change Database for the JMS Services</title>
- <para>The JMS service in the JBoss Enterprise Application 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 <literal>{jboss.dist}/server/${server}/deploy/messaging/${database}-persistence-service.xml</literal> with the file <literal>${jboss.dist}/docs/examples/jms/${database}-persistence-service.xml</literal> depending on your external database. Notice that if you are using the <literal>default</literal> server profile, the file path is <literal>{jboss.dist}/server/default/deploy/messaging/${database}-persistence-service.xml</literal>. <!--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>
+ <para>The JMS service in the JBoss Enterprise Application 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 <literal>{jboss.dist}/server/${server}/deploy/messaging/${database}-persistence-service.xml</literal> with the file <literal>${jboss.dist}/docs/examples/jms/${database}-persistence-service.xml</literal> 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>
<itemizedlist>
<listitem><para>MySQL: <literal>mysql-persistence-service.xml</literal></para></listitem>
- <listitem><para>PostgreSQL: <literal>postgres-persistence-service.xml</literal></para></listitem>
+ <listitem><para>PostgreSQL: <literal>postgresql-persistence-service.xml</literal></para></listitem>
<listitem><para>Oracle: <literal>oracle-persistence-service.xml</literal></para></listitem>
<listitem><para>DB2: <literal>db2-persistence-service.xml</literal></para></listitem>
<listitem><para>Sybase: <literal>sybase-persistence-service.xml</literal></para></listitem>
<listitem><para>MS SQL Server: <literal>mssql-persistence-service.xml</literal></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>
@@ -1201,8 +1203,61 @@
</datasources></programlisting>
</section>
+
+<section>
+ <title>Datasource sample for Oracle RAC</title>
+ <programlisting><![CDATA[
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DefaultDS</jndi-name>
+ <connection-url>jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP) (HOST=YOUR_HOST)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=YOUR_SERVICE_NAME)))</connection-url>
+ <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
+ <user-name>jboss</user-name>
+ <password>password</password>
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
+ <metadata>
+ <type-mapping>Oracle9i</type-mapping>
+ </metadata>
+ <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
+ </local-tx-datasource>
+</datasources>]]>
+ </programlisting>
+</section>
+
+<section>
+ <title>XA Datasource sample for Oracle RAC</title>
+ <programlisting><![CDATA[
+<datasources>
+ <xa-datasource>
+ <jndi-name>YourJndiName</jndi-name>
+ <track-connection-by-tx>true</track-connection-by-tx>
+ <isSameRM-override-value>false</isSameRM-override-value>
+ <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
+ <xa-datasource-property name="URL">jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=YOUR_HOST)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=YOUR_SERVICE_NAME)))</xa-datasource-property>
+ <xa-datasource-property name="User">your_user</xa-datasource-property>
+ <xa-datasource-property name="Password">your_password</xa-datasource-property>
+ <!-- Checks the Oracle error codes and messages for fatal errors -->
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
+ <!-- Oracles XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction and vice-versa -->
+ <no-tx-separate-pools/>
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Oracle9i</type-mapping>
+ </metadata>
+ </xa-datasource>
+</datasources>
+]]>
+ </programlisting>
+ <para>
+ You can also use the following URL structure, which supports load-balancing:
+ </para>
+ <programlisting>
+jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=ON)
+(ADDRESS=(PROTOCOL=TCP)(HOST=YOUR_NODE_1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)
+(HOST=YOUR_NODE_2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=YOUR_SERVICE_NAME)))
+ </programlisting>
+</section>
-
<section>
<title>Configuring a DataSource for remote usage</title>
<para>
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2009-10-30 02:01:35 UTC (rev 95809)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2009-10-30 02:26:23 UTC (rev 95810)
@@ -8,7 +8,7 @@
5.0</subtitle>
<edition>1</edition>
<issuenum>1</issuenum>
- <pubsnumber>3</pubsnumber>
+ <pubsnumber>4</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>5.0</productnumber>
<!-- <pubdate>, 2009</pubdate> -->
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml 2009-10-30 02:01:35 UTC (rev 95809)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml 2009-10-30 02:26:23 UTC (rev 95810)
@@ -5,6 +5,25 @@
<appendix id="appe-Publican-Revision_History">
<title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>1.2</revnumber>
+ <date>Wed Oct 28 2009</date>
+ <author>
+ <firstname>Laura</firstname>
+ <surname>Bailey</surname>
+ <email>lbailey at redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>JIRA corrections.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ </revhistory>
+ </simpara>
+
<simpara>
<revhistory>
<revision>
More information about the jboss-cvs-commits
mailing list