geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r917744 [18/31] - in /websites/production/geronimo/content: GMOxDOC20/ GMOxDOC20/geronimo-eclipse-plugin-installation-instructions.data/ cache/
Date Tue, 29 Jul 2014 00:52:21 GMT
Modified: websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-jdbc-migration.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-jdbc-migration.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-jdbc-migration.html Tue Jul 29 00:52:18 2014
@@ -95,42 +95,40 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><p><a shape="rect" name="JBosstoGeronimo-JDBCMigration-top"></a><br clear="none">
+          <div class="wiki-content maincontent"><p><span class="confluence-anchor-link" id="JBosstoGeronimo-JDBCMigration-top"></span><br clear="none">
 This article will help you migrate JDBC applications developed for JBoss v4 to Apache Geronimo. This article is part of a series of migration articles covering different types of applications migration.</p>
 
-<p>This article provides details on the JDBC implementation differences between these two application servers as well as a detailed step-by-step migration procedure for porting JDBC applications from JBoss v4 to Apache Geronimo.  To define a common starting point (the source environment), this article provides steps for deploying the <a shape="rect" href="jboss-to-geronimo-jdbc-migration.data/brokerage.zip?version=1&amp;modificationDate=1188982869000">Online Brokerage</a> sample application into the JBoss source environment. Then you will be guided through the application migration and deployment process in Apache Geronimo.</p>
+<p>This article provides details on the JDBC implementation differences between these two application servers as well as a detailed step-by-step migration procedure for porting JDBC applications from JBoss v4 to Apache Geronimo.  To define a common starting point (the source environment), this article provides steps for deploying the <a shape="rect" href="jboss-to-geronimo-jdbc-migration.data/brokerage.zip?version=1&amp;modificationDate=1188982869000&amp;api=v2">Online Brokerage</a> sample application into the JBoss source environment. Then you will be guided through the application migration and deployment process in Apache Geronimo.</p>
 
 <p>This article is organized in the following sections:</p>
 <ul><li><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-implementation">JDBC implementation analysis</a></li><li><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-sampleApp">Sample application</a></li><li><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-JBoss">The JBoss environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-Geronimo">The Geronimo environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-migration">Step-by-step migration</a></li><li><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-summary">Summary</a></li></ul>
 
 
-<h1><a shape="rect" name="JBosstoGeronimo-JDBCMigration-JDBCimplementationanalysis"></a>JDBC implementation analysis <a shape="rect" name="JBosstoGeronimo-JDBCMigration-implementation"></a></h1>
+<h1 id="JBosstoGeronimo-JDBCMigration-JDBCimplementationanalysisimplementation">JDBC implementation analysis <span class="confluence-anchor-link" id="JBosstoGeronimo-JDBCMigration-implementation"></span></h1>
 
 <p>JDBC implementation may vary from one vendor to another. The purpose of this section is to provide a JDBC specific feature-to-feature comparison between JBoss and Apache Geronimo so you can clearly identify the differences and plan accordingly before migration.</p>
 
 <p>Given that JBoss and Geronimo both use J2CA connectors for accessing JDBC resources, there will be an overlap of some J2CA features when comparing the platform specific JDBC features.</p>
 
-<p><b>Note:</b> Since Geronimo is still in its infancy some of the features provided by JBoss may not yet be implemented in Geronimo.</p>
-<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Feature </th><th colspan="1" rowspan="1" class="confluenceTh"> Apache Geronimo </th><th colspan="1" rowspan="1" class="confluenceTh"> JBoss v4 </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> JDBC access </td><td colspan="1" rowspan="1" class="confluenceTd"> Geronimo does not have any direct integration with JDBC but supports access through the generic J2CA framework. The TranQL project has J2CA adapters for various databases. </td><td colspan="1" rowspan="1" class="confluenceTd"> JDBC access in JBoss is through JDBC connectors based on the JCA specification. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> JCA implementation </td><td colspan="1" rowspan="1" class="confluenceTd"> Geronimo supports the JCA 1.5 specification and is backward compatible to the JCA 1.0 specification. </td><td colspan="1" rowspan="1" class="confluenceTd"> JBoss AS 4.0 implements the JC
 A (Java Connector Architecture) 1.5 specification instead of the JCA 1.0 in JBoss AS 3.2. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Data sources supported </td><td colspan="1" rowspan="1" class="confluenceTd"> TranQL has generic wrappers for data source, ConnectionPoolDatasource, and XADataSource. </td><td colspan="1" rowspan="1" class="confluenceTd"> Supports 5 types of data sources:
-<ul class="alternate" type="square"><li>no-tx-datasource</li><li>local-tx-datasource</li><li>xa-datasource</li><li>ha-local-tx-datasource</li><li>ha-xa-datasource</li></ul>
-</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Data source failover </td><td colspan="1" rowspan="1" class="confluenceTd"> TranQL has specialized drivers for certain databases (including Apache Derby, Oracle and soon DB2) that provide a tighter integration with the advanced features of the driver. <br clear="none" class="atl-forced-newline">
- It is at this level that features such as load-balancing and failover would be provided. You can also use a C-JDBC wrapper for providing database clustering and failover. </td><td colspan="1" rowspan="1" class="confluenceTd"> JBoss has data source failover capabilities implemented through two data sources. <br clear="none" class="atl-forced-newline">
+<p><strong>Note:</strong> Since Geronimo is still in its infancy some of the features provided by JBoss may not yet be implemented in Geronimo.</p>
+<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Feature </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Apache Geronimo </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> JBoss v4 </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> JDBC access </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Geronimo does not have any direct integration with JDBC but supports access through the generic J2CA framework. The TranQL project has J2CA adapters for various databases. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JDBC access in JBoss is through JDBC connectors based on the JCA specification. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> JCA implementation </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Geronimo supports the JCA 1.5 specification and is backward compatible to the JCA 1.0 specification. </p></td>
 <td colspan="1" rowspan="1" class="confluenceTd"><p> JBoss AS 4.0 implements the JCA (Java Connector Architecture) 1.5 specification instead of the JCA 1.0 in JBoss AS 3.2. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Data sources supported </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> TranQL has generic wrappers for data source, ConnectionPoolDatasource, and XADataSource. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Supports 5 types of data sources:</p>
+<ul class="alternate"><li>no-tx-datasource</li><li>local-tx-datasource</li><li>xa-datasource</li><li>ha-local-tx-datasource</li><li>ha-xa-datasource</li></ul>
+</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Data source failover </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> TranQL has specialized drivers for certain databases (including Apache Derby, Oracle and soon DB2) that provide a tighter integration with the advanced features of the driver. <br clear="none" class="atl-forced-newline">
+ It is at this level that features such as load-balancing and failover would be provided. You can also use a C-JDBC wrapper for providing database clustering and failover. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JBoss has data source failover capabilities implemented through two data sources. <br clear="none" class="atl-forced-newline">
  1)	ha-local-tx-datasource - for local transactions. <br clear="none" class="atl-forced-newline">
- 2)	ha-xa-datasource - for distributed transactions </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> XA support </td><td colspan="1" rowspan="1" class="confluenceTd"> Supports XA transactions, Local Transactions, and No transaction. </td><td colspan="1" rowspan="1" class="confluenceTd"> Supports XA transactions, Local Transactions, and No transaction. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Connection Manager Configurability </td><td colspan="1" rowspan="1" class="confluenceTd"> The J2CA framework is interceptor based which allows different parts of the connection framework to be plugged in. <br clear="none" class="atl-forced-newline">
- Although you cannot plug in a custom connection manager now, this capability can be added fairly easily. </td><td colspan="1" rowspan="1" class="confluenceTd"> You can plug in your own custom connection manager if required. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> JTA implementation </td><td colspan="1" rowspan="1" class="confluenceTd"> Transaction support is provided through JOTM and HOWL. </td><td colspan="1" rowspan="1" class="confluenceTd"> Full support for JTA through JBossJTA. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Connection pooling and management </td><td colspan="1" rowspan="1" class="confluenceTd"> Custom Geronimo Code and TranQL used for connection pooling and management. </td><td colspan="1" rowspan="1" class="confluenceTd"> JBossCX framework used for connection pooling and management. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Legacy driver support </td><td colspan="1" rowspan="1" class="confluenceTd"
 > Geronimo also provides this through the TranQL- connector JDBC to JCA wrapper in Geronimo. Supports JDBC 3.0 and 2.1. </td><td colspan="1" rowspan="1" class="confluenceTd"> JBoss provides connection to RDBMS that have not yet implemented JCA- JDBC drivers through JCA wrappers for JDBC drivers. </td></tr></tbody></table>
-</div>
+ 2)	ha-xa-datasource - for distributed transactions </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> XA support </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Supports XA transactions, Local Transactions, and No transaction. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Supports XA transactions, Local Transactions, and No transaction. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connection Manager Configurability </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The J2CA framework is interceptor based which allows different parts of the connection framework to be plugged in. <br clear="none" class="atl-forced-newline">
+ Although you cannot plug in a custom connection manager now, this capability can be added fairly easily. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> You can plug in your own custom connection manager if required. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> JTA implementation </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Transaction support is provided through JOTM and HOWL. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Full support for JTA through JBossJTA. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connection pooling and management </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Custom Geronimo Code and TranQL used for connection pooling and management. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JBossCX framework used for connection pooling and management. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Legacy driver suppo
 rt </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Geronimo also provides this through the TranQL- connector JDBC to JCA wrapper in Geronimo. Supports JDBC 3.0 and 2.1. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JBoss provides connection to RDBMS that have not yet implemented JCA- JDBC drivers through JCA wrappers for JDBC drivers. </p></td></tr></tbody></table></div>
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Sampleapplication"></a>Sample application <a shape="rect" name="JBosstoGeronimo-JDBCMigration-sampleApp"></a></h1>
+<h1 id="JBosstoGeronimo-JDBCMigration-SampleapplicationsampleApp">Sample application <span class="confluence-anchor-link" id="JBosstoGeronimo-JDBCMigration-sampleApp"></span></h1>
 
-<p>This article contains a sample application to demonstrate migrating an application from JBoss to Geronimo, called <a shape="rect" href="jboss-to-geronimo-jdbc-migration.data/brokerage.zip?version=1&amp;modificationDate=1188982869000">Online Brokerage</a>. It represents an online trading scenario in which users can buy and sell stocks. The application has the following five pages:</p>
+<p>This article contains a sample application to demonstrate migrating an application from JBoss to Geronimo, called <a shape="rect" href="jboss-to-geronimo-jdbc-migration.data/brokerage.zip?version=1&amp;modificationDate=1188982869000&amp;api=v2">Online Brokerage</a>. It represents an online trading scenario in which users can buy and sell stocks. The application has the following five pages:</p>
 <ul><li>Login Page</li><li>Registration Page</li><li>User Information Page</li><li>Available Stocks Page</li><li>User Portfolio Page</li></ul>
 
 
 <p>The following figure illustrates the application flow:<br clear="none">
-<span class="image-wrap" style=""><img src="jboss-to-geronimo-jdbc-migration.data/JSP_flow.jpg" style="border: 0px solid black"></span></p>
+<img class="confluence-embedded-image" src="https://cwiki.apache.org/confluence/download/attachments/65036/JSP_flow.jpg?version=1&amp;modificationDate=1188982908000&amp;api=v2" data-image-src="/confluence/download/attachments/65036/JSP_flow.jpg?version=1&amp;modificationDate=1188982908000&amp;api=v2"></p>
 
 <p>First, the user accesses the Login page. From the Login page the user enters the user name and password. If the user name or password is not valid the application throws an error message and rejects the user's login attempt. If the user name and password are correct, the user is taken to the Available Stocks page where he/she can view all the stocks that are present for sale at that time.</p>
 
@@ -148,7 +146,7 @@ This article will help you migrate JDBC 
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-ApplicationclassesandJSPpages"></a>Application classes and JSP pages</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-ApplicationclassesandJSPpages">Application classes and JSP pages</h2>
 
 <p>The Online Brokerage sample application consists of the following packages:</p>
 <ul><li>com.dev.trade.bo
@@ -177,36 +175,34 @@ This article will help you migrate JDBC 
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Toolsused"></a>Tools used</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Toolsused">Tools used</h2>
 
 <p>The tools used for developing and building the Online Brokerage application are:</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Eclipse"></a>Eclipse</h3>
+<h3 id="JBosstoGeronimo-JDBCMigration-Eclipse">Eclipse</h3>
 
 <p>The Eclipse IDE was used for development of the sample application. This is a very powerful and popular open source development tool. Integration plug-ins are available for both JBoss and Geronimo. Eclipse can be downloaded from the following URL:<br clear="none">
 <a shape="rect" class="external-link" href="http://www.eclipse.org" rel="nofollow">http://www.eclipse.org</a></p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-JDBCMigration-ApacheAnt"></a>Apache Ant</h3>
+<h3 id="JBosstoGeronimo-JDBCMigration-ApacheAnt">Apache Ant</h3>
 
 <p>Ant is a pure Java build tool. It is used for building the war files and populating the database for the Online Brokerage application. Ant can be downloaded from the following URL:<br clear="none">
 <a shape="rect" class="external-link" href="http://ant.apache.org">http://ant.apache.org</a></p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Sampledatabase"></a>Sample database</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Sampledatabase">Sample database</h2>
 
-<p>The database used for demostrating this application is MySQL.  The sample database name is <b>tradedb</b> and it consists of the following three tables, STOCKS, USERS and TRADINGACCOUNT.  The fields for each of these tables are described below.</p>
-<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Table Name </th><th colspan="1" rowspan="1" class="confluenceTh"> Fields </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> STOCKS </td><td colspan="1" rowspan="1" class="confluenceTd"> ID (PRIMARY KEY) <br clear="none" class="atl-forced-newline">
+<p>The database used for demostrating this application is MySQL.  The sample database name is <strong>tradedb</strong> and it consists of the following three tables, STOCKS, USERS and TRADINGACCOUNT.  The fields for each of these tables are described below.</p>
+<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Table Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Fields </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> STOCKS </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> ID (PRIMARY KEY) <br clear="none" class="atl-forced-newline">
  NAME <br clear="none" class="atl-forced-newline">
- PRICE </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> USERS </td><td colspan="1" rowspan="1" class="confluenceTd"> USERID (PRIMARY KEY) <br clear="none" class="atl-forced-newline">
+ PRICE </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> USERS </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> USERID (PRIMARY KEY) <br clear="none" class="atl-forced-newline">
  NAME <br clear="none" class="atl-forced-newline">
  PASSWORD <br clear="none" class="atl-forced-newline">
  ADDRESS <br clear="none" class="atl-forced-newline">
- CASH </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> TRADINGACCOUNT </td><td colspan="1" rowspan="1" class="confluenceTd"> USERID <br clear="none" class="atl-forced-newline">
+ CASH </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> TRADINGACCOUNT </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> USERID <br clear="none" class="atl-forced-newline">
  STOCKID <br clear="none" class="atl-forced-newline">
- QUANTITY </td></tr></tbody></table>
-</div>
+ QUANTITY </p></td></tr></tbody></table></div>
 
 <p>The TRADINGACCOUNT table is used to store the stocks that are owned by each user. The USERS and STOCKS tables are used to store the user and stock details. Because this is just a sample application the amount of money that a user has is entered during user registration by the user itself.</p>
 
@@ -214,23 +210,23 @@ This article will help you migrate JDBC 
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-JDBCMigration-TheJBossenvironment"></a>The JBoss environment <a shape="rect" name="JBosstoGeronimo-JDBCMigration-JBoss"></a></h1>
+<h1 id="JBosstoGeronimo-JDBCMigration-TheJBossenvironmentJBoss">The JBoss environment <span class="confluence-anchor-link" id="JBosstoGeronimo-JDBCMigration-JBoss"></span></h1>
 
 <p>This section shows you how and where the sample JBoss reference environment was installed so you can map this scenario to your own implementation.</p>
 
 <p>Detailed instructions for installing, configuring, and managing JBoss are provided in the product documentation. Check the product Web site for the most updated documents.</p>
 
 <p>The following list highlights the general tasks you will need to complete to install and configure the initial environment as the starting point for deploying the sample application.</p>
-<ol><li>Download and install JBoss v4 as explained in the product documentation guides. From now on the installation directory will be referred as <b>&lt;jboss_home&gt;</b></li><li>Create a copy of the default JBoss v4 application server. Copy recursively <b>&lt;jboss_home&gt;\server\default</b> to <b>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;</b></li><li>Start the new server by running the <tt>run.sh -c &lt;your_server_name&gt;</tt> command from the <b>&lt;jboss_home&gt;\bin</b> directory.</li><li>Once the server is started, you can verify that it is running by opening a Web browser and pointing it to this URL: <a shape="rect" class="external-link" href="http://localhost:8080" rel="nofollow">http://localhost:8080</a>. You should see the JBoss Welcome window and be able to access the JBoss console.</li><li>Once the application server is up and running, the next step is to install and configure all the remaining prerequisite software required by the sample application. This s
 tep is described in the following section.</li></ol>
+<ol><li>Download and install JBoss v4 as explained in the product documentation guides. From now on the installation directory will be referred as <strong>&lt;jboss_home&gt;</strong></li><li>Create a copy of the default JBoss v4 application server. Copy recursively <strong>&lt;jboss_home&gt;\server\default</strong> to <strong>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;</strong></li><li>Start the new server by running the <code>run.sh -c &lt;your_server_name&gt;</code> command from the <strong>&lt;jboss_home&gt;\bin</strong> directory.</li><li>Once the server is started, you can verify that it is running by opening a Web browser and pointing it to this URL: <a shape="rect" class="external-link" href="http://localhost:8080" rel="nofollow">http://localhost:8080</a>. You should see the JBoss Welcome window and be able to access the JBoss console.</li><li>Once the application server is up and running, the next step is to install and configure all the remaining prerequisite softwar
 e required by the sample application. This step is described in the following section.</li></ol>
 
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Installandconfigureprerequisitesoftware"></a>Install and configure prerequisite software</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Installandconfigureprerequisitesoftware">Install and configure prerequisite software</h2>
 
 <p>In order to build and run the Online Brokerage application included in this article, you need to install and configure the build tool and the database that is used by the application.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Installthedatabase"></a>Install the database</h3>
+<h3 id="JBosstoGeronimo-JDBCMigration-Installthedatabase">Install the database</h3>
 
 <p>As mentioned earlier in the article, this application is using the MySQL database that can be downloaded from the following URL:<br clear="none">
 <a shape="rect" class="external-link" href="http://www.mysql.com" rel="nofollow">http://www.mysql.com</a><br clear="none">
@@ -238,13 +234,13 @@ The Installation and configuration of My
 
 <p><a shape="rect" class="external-link" href="http://dev.mysql.com/doc/mysql/en" rel="nofollow">http://dev.mysql.com/doc/mysql/en</a></p>
 
-<p><b>Note:</b> During the instance configuration I modified the security settings and specified "password" as the password for the root user. This user ID and password will later be used for accessing the database from the sample application.</p>
+<p><strong>Note:</strong> During the instance configuration I modified the security settings and specified "password" as the password for the root user. This user ID and password will later be used for accessing the database from the sample application.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Createsampledatabase"></a>Create sample database</h3>
+<h3 id="JBosstoGeronimo-JDBCMigration-Createsampledatabase">Create sample database</h3>
 
 <p>Once the MySQL instance is configured you need to create the sample database that will be used by the Online Brokerage application. From a command line, type the following command to start the MySQL monitor:</p>
 
-<p><tt><b>mysql -u root -ppassword</b></tt></p>
+<p><code><strong>mysql -u root -ppassword</strong></code></p>
 
 <p>Note that there is no blank between the flag -p and the password.</p>
 
@@ -260,11 +256,11 @@ mysql&gt;
 </div></div>
 <p>From the MySQL command interface create the tradedb sample database by typing the following command:</p>
 
-<p><tt><b>mysql&gt; create database tradedb;</b></tt></p>
+<p><code><strong>mysql&gt; create database tradedb;</strong></code></p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-JDBCMigration-ConfigureAnt"></a>Configure Ant</h3>
+<h3 id="JBosstoGeronimo-JDBCMigration-ConfigureAnt">Configure Ant</h3>
 
-<p>As mentioned before, Apache Ant is used to build the binaries for the Online Brokerage application. If you do not have Ant installed this is a good time for doing it and make sure that <b>&lt;ant_home&gt;\bin</b> directory is added to the system's path variable.</p>
+<p>As mentioned before, Apache Ant is used to build the binaries for the Online Brokerage application. If you do not have Ant installed this is a good time for doing it and make sure that <strong>&lt;ant_home&gt;\bin</strong> directory is added to the system's path variable.</p>
 
 <p>Apache Ant can be downloaded from the following URL:</p>
 
@@ -272,23 +268,23 @@ mysql&gt;
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Configureresources"></a>Configure resources</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Configureresources">Configure resources</h2>
 
 <p>In order to successfully build and deploy the Online Brokerage application and database, you will first need to configure some resources. This section describes how to configure a MySQL data source in JBoss.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Datasource"></a>Data source</h3>
+<h3 id="JBosstoGeronimo-JDBCMigration-Datasource">Data source</h3>
 
 <p>The Online Brokerage application is a Web application that uses a data source to connect to the MySQL database. To use JBoss with MySQL you need to copy the MySQL driver into the JBoss server classpath. The driver, which is provided by the database vendor, is called Connector/J 3.0 and can be downloaded from the following URL:<br clear="none">
 <a shape="rect" class="external-link" href="http://dev.mysql.com/downloads/connector/j/3.1.html" rel="nofollow">http://dev.mysql.com/downloads/connector/j/3.1.html</a></p>
 
-<p>After downloading and extracting the driver, copy the <b>mysql-connector-java-3.1.14.jar</b> file to the <b>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\lib</b> directory.</p>
+<p>After downloading and extracting the driver, copy the <strong>mysql-connector-java-3.1.14.jar</strong> file to the <strong>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\lib</strong> directory.</p>
 
 <p>The data source configuration in JBoss is done through an XML configuration file. The JBoss installation contains sample configuration files for many popular databases including MySQL.</p>
 
-<p>The sample data source configuration file for MySQL is <b>mysql-ds.xml</b> and it is located in the <b>&lt;jboss_home&gt;\docs\examples\jca</b> directory:</p>
+<p>The sample data source configuration file for MySQL is <strong>mysql-ds.xml</strong> and it is located in the <strong>&lt;jboss_home&gt;\docs\examples\jca</strong> directory:</p>
 
-<p>Copy the mysql-ds.xml file to the deploy directory of your JBoss server (<tt>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\deploy</tt>) and edit it as shown in the following example:</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Update the mysql-ds.xml file</b></div><div class="codeContent panelContent">
+<p>Copy the mysql-ds.xml file to the deploy directory of your JBoss server (<code>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\deploy</code>) and edit it as shown in the following example:</p>
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Update the mysql-ds.xml file</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;jndi-name&gt;jdbc/TradeDB&lt;/jndi-name&gt;
 &lt;connection-url&gt;jdbc:mysql://localhost:3306/tradedb&lt;/connection-url&gt;
@@ -300,17 +296,17 @@ org.jboss.resource.adapter.jdbc.vendor.M
 &lt;/exception-sorter-class-name&gt;
 ]]></script>
 </div></div>
-<p>Delete all the other tags inside the <b>&lt;local-tx-datasource&gt;</b> tag and save the file. JBoss will automatically deploy the data source.</p>
+<p>Delete all the other tags inside the <strong>&lt;local-tx-datasource&gt;</strong> tag and save the file. JBoss will automatically deploy the data source.</p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Buildthesampleapplication"></a>Build the sample application</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Buildthesampleapplication">Build the sample application</h2>
 
 <p>The Online Brokerage application included with this article provides an Ant script that you will use in order to build the application and populate the database. Download the Online Brokerage application from the following link:</p>
 
-<p><a shape="rect" href="jboss-to-geronimo-jdbc-migration.data/brokerage.zip?version=1&amp;modificationDate=1188982869000">Online Brokerage</a></p>
+<p><a shape="rect" href="jboss-to-geronimo-jdbc-migration.data/brokerage.zip?version=1&amp;modificationDate=1188982869000&amp;api=v2">Online Brokerage</a></p>
 
-<p>After extracting the zip file, a brokerage directory is created. In that directory open the <b>build.properties</b> file and edit the properties to match your environment as shown in the following example:</p>
+<p>After extracting the zip file, a brokerage directory is created. In that directory open the <strong>build.properties</strong> file and edit the properties to match your environment as shown in the following example:</p>
 <div class="preformatted panel" style="border-style: solid;border-width: 1px;"><div class="preformattedHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Update the build.properties file</b></div><div class="preformattedContent panelContent">
 <pre># Replace server.name with either jboss or geronimo depending on which server to deploy.
 server.name=jboss
@@ -334,11 +330,17 @@ sql.file=sql/db.sql
 driver.classpath=&lt;jboss_home&gt;/server/&lt;your_server_name&gt;/lib/mysql-connector-java-3.1.14-bin.jar
 </pre>
 </div></div>
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">When specifying the driver.classpath in the build.properties file, make sure to use just the forward slash "/" , otherwise the build will not find the jar file.</td></tr></table></div>
-<p>From a command prompt or shell go to the brokerage directory and run <b>ant</b>. This will build the war file and place it directly in the brokerage directory. The war created by the ant build contains a JBoss specific deployment descriptor, the <b>jboss-web.xml</b> file in the WEB-INF directory of the WAR is shown in the following example.</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>JBoss deployment descriptor</b></div><div class="codeContent panelContent">
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>When specifying the driver.classpath in the build.properties file, make sure to use just the forward slash "/" , otherwise the build will not find the jar file.</p>
+                    </div>
+    </div>
+
+<p>From a command prompt or shell go to the brokerage directory and run <strong>ant</strong>. This will build the war file and place it directly in the brokerage directory. The war created by the ant build contains a JBoss specific deployment descriptor, the <strong>jboss-web.xml</strong> file in the WEB-INF directory of the WAR is shown in the following example.</p>
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>JBoss deployment descriptor</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;jboss-web&gt;
   &lt;context-root&gt;/brokerage&lt;/context-root&gt;
   &lt;resource-ref&gt;
@@ -353,69 +355,90 @@ driver.classpath=&lt;jboss_home&gt;/serv
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Deploythesampleapplication"></a>Deploy the sample application</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Deploythesampleapplication">Deploy the sample application</h2>
 
-<p>To deploy the Online Brokerage application in JBoss, copy the <b>brokerage.war</b> file you just built with Ant to the following directory:</p>
+<p>To deploy the Online Brokerage application in JBoss, copy the <strong>brokerage.war</strong> file you just built with Ant to the following directory:</p>
 
-<p><tt>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\deploy</tt></p>
+<p><code>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\deploy</code></p>
 
 <p>If JBoss is already started, it will automatically deploy and start the application;  otherwise, the application will be deployed and started at the next startup.</p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Testthesampleapplication"></a>Test the sample application</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Testthesampleapplication">Test the sample application</h2>
 
 <p>To test the application, open a Web browser and access the following URL:</p>
 
 <p><a shape="rect" class="external-link" href="http://localhost:8080/brokerage" rel="nofollow">http://localhost:8080/brokerage</a></p>
 
-<p>This brings up the login screen of the Online Brokerage application.  Enter <b>j2ee</b> as the user name and <b>password</b> as the password and click on login. This takes you to the available stocks page illustrated in the following figure. The application is now configured and running.</p>
+<p>This brings up the login screen of the Online Brokerage application.  Enter <strong>j2ee</strong> as the user name and <strong>password</strong> as the password and click on login. This takes you to the available stocks page illustrated in the following figure. The application is now configured and running.</p>
 
-<p><span class="image-wrap" style=""><img src="jboss-to-geronimo-jdbc-migration.data/availableStocks.jpg" style="border: 0px solid black"></span></p>
-<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Pro Tip</b><br clear="none">If you want to use another root password for the database, replace the occurrences of 'password' with the required password. This has to be changed in the following three places:
+<p><img class="confluence-embedded-image" src="https://cwiki.apache.org/confluence/download/attachments/65036/availableStocks.jpg?version=1&amp;modificationDate=1188982908000&amp;api=v2" data-image-src="/confluence/download/attachments/65036/availableStocks.jpg?version=1&amp;modificationDate=1188982908000&amp;api=v2"></p>
+    <div class="aui-message success shadowed information-macro">
+                    <p class="title">Pro Tip</p>
+                            <span class="aui-icon icon-success">Icon</span>
+                <div class="message-content">
+                            <p>If you want to use another root password for the database, replace the occurrences of 'password' with the required password. This has to be changed in the following three places:</p>
 <ol><li>MySQL instance configuration.</li><li>Data source configuration file.</li><li>build.properties file used by the Ant build script.</li></ol>
-</td></tr></table></div>
+
+                    </div>
+    </div>
+
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-JDBCMigration-TheGeronimoenvironment"></a>The Geronimo environment <a shape="rect" name="JBosstoGeronimo-JDBCMigration-Geronimo"></a></h1>
+<h1 id="JBosstoGeronimo-JDBCMigration-TheGeronimoenvironmentGeronimo">The Geronimo environment <span class="confluence-anchor-link" id="JBosstoGeronimo-JDBCMigration-Geronimo"></span></h1>
 
 <p>Download and install Geronimo from the following URL:</p>
 
 <p><a shape="rect" class="external-link" href="http://geronimo.apache.org/downloads.html">http://geronimo.apache.org/downloads.html</a></p>
 
-<p>The release notes available there provide clear instructions on system requirements and how to install and start Geronimo.  Throughout the rest of this article we will refer to the Geronimo installation directory as <b>&lt;geronimo_home&gt;</b>.</p>
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>TCP/IP ports conflict</b><br clear="none">If you are planning to run JBoss and Geronimo on the same machine consider to change the default service ports on, at least, one of these servers.</td></tr></table></div>
+<p>The release notes available there provide clear instructions on system requirements and how to install and start Geronimo.  Throughout the rest of this article we will refer to the Geronimo installation directory as <strong>&lt;geronimo_home&gt;</strong>.</p>
+    <div class="aui-message problem shadowed information-macro">
+                    <p class="title">TCP/IP ports conflict</p>
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            <p>If you are planning to run JBoss and Geronimo on the same machine consider to change the default service ports on, at least, one of these servers.</p>
+                    </div>
+    </div>
+
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Configureresources"></a>Configure resources</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Configureresources.1">Configure resources</h2>
 
-<p>In Geronimo the JDBC resources are implemented using J2EE connectors. Therefore, you need to write a Geronimo specific deployment plan for deploying a JDBC datasource. Additionally, while doing the deployment you need to provide the deployer with the <b>tranql-connector-ra-1.3.rar</b> file. This RAR file contains the connection pool management logic for Geronimo.</p>
+<p>In Geronimo the JDBC resources are implemented using J2EE connectors. Therefore, you need to write a Geronimo specific deployment plan for deploying a JDBC datasource. Additionally, while doing the deployment you need to provide the deployer with the <strong>tranql-connector-ra-1.3.rar</strong> file. This RAR file contains the connection pool management logic for Geronimo.</p>
 
 <p>For running the Online Brokerage application in Geronimo, you will be using the same MySQL database that was used with JBoss. So the only task you need to do in order to prepare the Geronimo environment is to configure the data source.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Configurethedatasource"></a>Configure the data source</h3>
+<h3 id="JBosstoGeronimo-JDBCMigration-Configurethedatasource">Configure the data source</h3>
 
 <p>The first thing you need to do is to copy the MySQL database driver into the Geronimo repository so that you can refer to it in the data source deployment plan.</p>
 
-<p>The Geronimo repository is located at &lt;geronimo_home&gt;/repository. Inside this directory, create a directory called <b>mysql/mysql-connector-java/3.1.14-bin</b> and copy the <b>mysql-connector-java-3.1.14-bin.jar</b> file into it. Now, you need to create the data source deployment plan.</p>
-<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Different types of data sources</b><br clear="none">There are three types of data sources that Geronimo supports:
+<p>The Geronimo repository is located at &lt;geronimo_home&gt;/repository. Inside this directory, create a directory called <strong>mysql/mysql-connector-java/3.1.14-bin</strong> and copy the <strong>mysql-connector-java-3.1.14-bin.jar</strong> file into it. Now, you need to create the data source deployment plan.</p>
+    <div class="aui-message hint shadowed information-macro">
+                    <p class="title">Different types of data sources</p>
+                            <span class="aui-icon icon-hint">Icon</span>
+                <div class="message-content">
+                            <p>There are three types of data sources that Geronimo supports:</p>
 <ul><li>Global data source - Visible to all the applications on a Geronimo Instance.</li><li>Application scoped data source - Visible to a single application within which it is defined.</li><li>Module scoped data source - Visible to a single module within which it is defined.</li></ul>
 
 
 <p>For this migration exercise you will be using a Global data source. For instructions on configuring and using the other two types of data sources see the the following developerWorks article:</p>
 
-<p><a shape="rect" class="external-link" href="http://www.ibm.com/developerworks/opensource/library/os-ag-jdbc/" rel="nofollow">http://www.ibm.com/developerworks/opensource/library/os-ag-jdbc/</a></p></td></tr></table></div>
+<p><a shape="rect" class="external-link" href="http://www.ibm.com/developerworks/opensource/library/os-ag-jdbc/" rel="nofollow">http://www.ibm.com/developerworks/opensource/library/os-ag-jdbc/</a></p>
+                    </div>
+    </div>
+
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h4><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Createthedatasourcedeploymentplan"></a>Create the data source deployment plan</h4>
+<h4 id="JBosstoGeronimo-JDBCMigration-Createthedatasourcedeploymentplan">Create the data source deployment plan</h4>
 
-<p>First, create an xml file called <b>mysql-geronimo-plan.xml</b>. Copy the plan shown in the following example and paste it in the xml file.</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Data source deployment plan</b></div><div class="codeContent panelContent">
+<p>First, create an xml file called <strong>mysql-geronimo-plan.xml</strong>. Copy the plan shown in the following example and paste it in the xml file.</p>
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Data source deployment plan</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;connector xmlns=&quot;http://geronimo.apache.org/xml/ns/j2ee/connector-1.2&quot;&gt;
 
-  &lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1"&gt;
+  &lt;dep:environment xmlns:dep=&quot;http://geronimo.apache.org/xml/ns/deployment-1.1&quot;&gt;
     &lt;dep:moduleId&gt;
 	  &lt;dep:groupId&gt;user&lt;/dep:groupId&gt;
 	  &lt;dep:artifactId&gt;jdbcdatasource&lt;/dep:artifactId&gt;
@@ -439,22 +462,22 @@ driver.classpath=&lt;jboss_home&gt;/serv
       &lt;/connectionfactory-interface&gt;
       &lt;connectiondefinition-instance&gt;
         &lt;name&gt;TradeDS&lt;/name&gt;
-        &lt;config-property-setting name="UserName"&gt;
+        &lt;config-property-setting name=&quot;UserName&quot;&gt;
           root
         &lt;/config-property-setting&gt;
-        &lt;config-property-setting name="Password"&gt;
+        &lt;config-property-setting name=&quot;Password&quot;&gt;
           password
         &lt;/config-property-setting&gt;
-        &lt;config-property-setting name="Driver"&gt;
+        &lt;config-property-setting name=&quot;Driver&quot;&gt;
           com.mysql.jdbc.Driver
         &lt;/config-property-setting&gt;
-        &lt;config-property-setting name="ConnectionURL"&gt;
+        &lt;config-property-setting name=&quot;ConnectionURL&quot;&gt;
           jdbc:mysql://localhost:3306/tradedb
         &lt;/config-property-setting&gt;
-        &lt;config-property-setting name="CommitBeforeAutocommit"&gt;
+        &lt;config-property-setting name=&quot;CommitBeforeAutocommit&quot;&gt;
            false
         &lt;/config-property-setting&gt;
-        &lt;config-property-setting name="ExceptionSorterClass"&gt;
+        &lt;config-property-setting name=&quot;ExceptionSorterClass&quot;&gt;
            org.tranql.connector.NoExceptionsAreFatalSorter
         &lt;/config-property-setting&gt;
         &lt;connectionmanager&gt;
@@ -487,9 +510,7 @@ driver.classpath=&lt;jboss_home&gt;/serv
 
 
 <p>The following table shows the configuration properties that are specified by the config-property-setting element.</p>
-<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Configuration Property </th><th colspan="1" rowspan="1" class="confluenceTh"> Meaning </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Driver </td><td colspan="1" rowspan="1" class="confluenceTd"> Fully qualified class name of the JDBC driver. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> ConnectionURL </td><td colspan="1" rowspan="1" class="confluenceTd"> The JDBC connection URL. This can contain parameters when supported by the driver. For example, for MySQL to use named pipes instead of TCP/IP you can attach <tt>?socketFactory=com.mysql.jdbc.NamedPipeSocketFactory</tt> to the JDBC connection URL. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> UserName </td><td colspan="1" rowspan="1" class="confluenceTd"> The user name needed to connect to the database. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Password </td><td colspa
 n="1" rowspan="1" class="confluenceTd"> The password needed to connect to the database. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> CommitBeforeAutocommit </td><td colspan="1" rowspan="1" class="confluenceTd"> In case the JDBC driver does not commit the pending data changes when <tt>setAutoCommit</tt> (true) is called. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> ExceptionSorterClass </td><td colspan="1" rowspan="1" class="confluenceTd"> To provide information to the pool whether the Exceptions that occur are fatal or not. </td></tr></tbody></table>
-</div>
+<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Configuration Property </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Meaning </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Driver </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Fully qualified class name of the JDBC driver. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ConnectionURL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JDBC connection URL. This can contain parameters when supported by the driver. For example, for MySQL to use named pipes instead of TCP/IP you can attach <code>?socketFactory=com.mysql.jdbc.NamedPipeSocketFactory</code> to the JDBC connection URL. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> UserName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The user name needed to connect to the database. </p></td
 ></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The password needed to connect to the database. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> CommitBeforeAutocommit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> In case the JDBC driver does not commit the pending data changes when <code>setAutoCommit</code> (true) is called. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ExceptionSorterClass </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To provide information to the pool whether the Exceptions that occur are fatal or not. </p></td></tr></tbody></table></div>
 
 <p>After creating the MySQL deployment plan we need to deploy the connection pool datasource by running the deployer tool.</p>
 
@@ -497,33 +518,33 @@ driver.classpath=&lt;jboss_home&gt;/serv
 
 <p>From a command line change directory to &lt;geronimo_home&gt;/bin and run the following command:</p>
 
-<p><tt>./deployer.cmd --user system --password manager deploy &lt;brokerage_home&gt;\plan\mysql-geronimo-plan.xml &lt;geronimo_home&gt;\repository\org\tranql\tranql-connector-ra\1.3</tt>tranql-connector-ra-1.3.rar</p>
+<p><code>./deployer.cmd --user system --password manager deploy &lt;brokerage_home&gt;\plan\mysql-geronimo-plan.xml &lt;geronimo_home&gt;\repository\org\tranql\tranql-connector-ra\1.3</code>tranql-connector-ra-1.3.rar</p>
 
 <p>where brokerage_home is the path of the brokerage directory.This will deploy the data source.<br clear="none">
 Now you are ready to proceed with the migration.</p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Stepbystepmigration"></a>Step-by-step migration <a shape="rect" name="JBosstoGeronimo-JDBCMigration-migration"></a></h1>
+<h1 id="JBosstoGeronimo-JDBCMigration-Step-by-stepmigrationmigration">Step-by-step migration <span class="confluence-anchor-link" id="JBosstoGeronimo-JDBCMigration-migration"></span></h1>
 
 <p>Geronimo does not support accessing external resources(JDBC datasources) by setting JNDI properties at runtime as shown in the following example:</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 Context ctx = null;
 Hashtable env = new Hashtable();
-env.put(Context.INITIAL_CONTEXT_FACTORY, "Geronimo specific factory");
-env.put(Context.PROVIDER_URL, "provider URL for geronimo");
+env.put(Context.INITIAL_CONTEXT_FACTORY, &quot;Geronimo specific factory&quot;);
+env.put(Context.PROVIDER_URL, &quot;provider URL for geronimo&quot;);
      ctx = new InitialContext(env)
 ]]></script>
 </div></div>
 <p>This is because reference resolution is done at deploy time and is based on the JSR-77 object names of the target component. In order to migrate the Online Brokerage application to Geronimo, you first need to replace the jboss-web.xml file with a geronimo-web.xml file which is the Geronimo-specific descriptor file.</p>
 
 <p>The geronimo-web.xml file is located in the &lt;brokerage_home&gt;\web\descriptors\geronimo directory and looks like the following example.</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>geronimo-web.xml</b></div><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>geronimo-web.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
-&lt;web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1" xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1"&gt;
-    &lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;ISO-8859-1&quot;?&gt;
+&lt;web-app xmlns=&quot;http://geronimo.apache.org/xml/ns/j2ee/web-1.1&quot; xmlns:naming=&quot;http://geronimo.apache.org/xml/ns/naming-1.1&quot;&gt;
+    &lt;dep:environment xmlns:dep=&quot;http://geronimo.apache.org/xml/ns/deployment-1.1&quot;&gt;
 	    &lt;dep:moduleId&gt;
 		    &lt;dep:groupId&gt;BrokerageApp&lt;/dep:groupId&gt;
 			&lt;dep:artifactId&gt;MySqlDS&lt;/dep:artifactId&gt;
@@ -558,24 +579,24 @@ env.put(Context.PROVIDER_URL, "provider 
 
 <p>These are the only changes required to run this application on Geronimo.</p>
 
-<p>In order to build the .war file for Geronimo, you can modify the build.properties file that is provided with the sample application to remove the jboss-web.xml and include the geronimo-web.xml. This is done by changing the <b>server.name</b> property to geronimo.  Also you need to specify the property <b>geronimo.home</b> in the build script.</p>
+<p>In order to build the .war file for Geronimo, you can modify the build.properties file that is provided with the sample application to remove the jboss-web.xml and include the geronimo-web.xml. This is done by changing the <strong>server.name</strong> property to geronimo.  Also you need to specify the property <strong>geronimo.home</strong> in the build script.</p>
 
 <p>The two values that you need to modify are:</p>
 
-<p><tt>server.name=geronimo</tt><br clear="none">
-<tt>geronimo.home=&lt;geronimo_home&gt;</tt></p>
+<p><code>server.name=geronimo</code><br clear="none">
+<code>geronimo.home=&lt;geronimo_home&gt;</code></p>
 
-<p>The build.properties is used by the build script to pick up the J2EE specs for Geronimo. If your <b>jboss.home</b> property is still valid, it is not required to set this property. If this property is not set and the jboss.home is also not valid then you will get compilation errors. You also need to set the <b>driver.classpath</b> to point to the new driver jar. Now from the command prompt go to the brokerage directory and run ant. This builds the war file and places it directly in the brokerage directory.</p>
+<p>The build.properties is used by the build script to pick up the J2EE specs for Geronimo. If your <strong>jboss.home</strong> property is still valid, it is not required to set this property. If this property is not set and the jboss.home is also not valid then you will get compilation errors. You also need to set the <strong>driver.classpath</strong> to point to the new driver jar. Now from the command prompt go to the brokerage directory and run ant. This builds the war file and places it directly in the brokerage directory.</p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Deploythemigratedsampleapplication"></a>Deploy the migrated sample application</h2>
+<h2 id="JBosstoGeronimo-JDBCMigration-Deploythemigratedsampleapplication">Deploy the migrated sample application</h2>
 
 <p>To deploy the migrated Online Brokerage application, make sure the Geronimo server is up and running.</p>
 
 <p>From a command line, change directory to &lt;geronimo_home&gt; and type the following command:</p>
 
-<p><tt>./deployer --user system --password manager deploy &lt;brokerage_home&gt;/brokerage.war</tt></p>
+<p><code>./deployer --user system --password manager deploy &lt;brokerage_home&gt;/brokerage.war</code></p>
 
 <p>Once the application is deployed, open a Web browser and access the following URL:</p>
 
@@ -585,7 +606,7 @@ env.put(Context.PROVIDER_URL, "provider 
 
 <p><a shape="rect" href="#JBosstoGeronimo-JDBCMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-JDBCMigration-Summary"></a>Summary <a shape="rect" name="JBosstoGeronimo-JDBCMigration-summary"></a></h1>
+<h1 id="JBosstoGeronimo-JDBCMigration-Summarysummary">Summary <span class="confluence-anchor-link" id="JBosstoGeronimo-JDBCMigration-summary"></span></h1>
 
 <p>This article has shown you how to migrate a sample application, from JBoss to the Apache Geronimo application server. You followed step-by-step instructions to build the application, deploy and run it, and then migrate it to the Geronimo environment.</p>
 



Mime
View raw message