User: kunle
Date: 01/03/24 07:31:08
Modified: documentation mssql.htm
Log:
fixed a couple of broken links in the document and added install instructions for
i-net Opta
Revision Changes Path
1.4 +135 -116 newsite/documentation/mssql.htm
Index: mssql.htm
===================================================================
RCS file: /cvsroot/jboss/newsite/documentation/mssql.htm,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- mssql.htm 2001/03/24 01:23:11 1.3
+++ mssql.htm 2001/03/24 15:31:08 1.4
@@ -38,12 +38,12 @@
(ROI) and substantially reduced time to market (TTM) compared to other J2EE
application suites and RDBMS solutions on the Windows platform.</p>
</div>
- <h4>C'mon, show me already...</h4>
+ <h4><a name="INSTALL-MENU">C'mon, show me already...</a></h4>
<div class="para" align="left">
<p>Not so fast amigos. You need to obtain a copy of the JBoss distribution
from the <a href="http://www.jboss.org/">JBoss website</a>. General
information
about all JBoss products as well as instructions on how to get a copy of
- JBoss for yourself can be found in the <a
href="http://www.jboss.org/newsite/business/faq.html">JBoss
+ JBoss for yourself can be found in the <a href="../business/faq.html">JBoss
FAQ</a> or on the <a href="http://www.jboss.org/">JBoss website</a>. The
rest of this document covers the following tasks: </p>
<ol>
@@ -59,7 +59,7 @@
This is even more likely to be the case if you have the latest experimental
or developer version of JBoss. </p>
<p> If this is the case with you or, if you have any further comments or
suggestions
- about this document or JBoss then please join the <a
href="http://www.jboss.org/newsite/business/list.html">JBoss
+ about this document or JBoss then please join the <a
href="../business/list.html">JBoss
mailing list</a> . You will then be able to contribute to the production
of this document and the development of JBoss.</p>
<p> </p>
@@ -162,36 +162,37 @@
<p align="center"><font size="-1">* The Sun JBDC-ODBC Bridge driver is NOT
recommended for serious J2EE development or deployment</font></p>
<br>
- <p>For the remainder of this document, the Sun JDBC-ODBC bridge and the Merant
- DataDirect Connect JDBC 2.0 Client JDBC drivers will be used to illustrate
- the use of MS SQL Server with JBoss.</p>
+ <p>For the remainder of this document, the Sun JDBC-ODBC bridge, the Merant
+ DataDirect Connect JDBC 2.0 Client and the i-net OPTA 2000 JDBC drivers
+ will be used to illustrate the use of MS SQL Server with JBoss.</p>
</div>
- <h3>1.2 Installing the Sun JDBC-ODBC Bridge Driver</h3>
+ <h3>1.1 Installing the Sun JDBC-ODBC Bridge driver</h3>
<div class="para" align="left">
<p> The Sun ODBC-JDBC driver is installed automatically during the Java 2
SDK installation process. It is installed as package
<code>sun.jdbc.odbc</code>.
This package must be in the CLASSPATH for any application that uses the
JDBC-ODBC bridge. For this tutorial it will be assumed that the Sun JDBC-ODBC
- bridge is properly installed on your system. To use the Sun JDBC-ODBC bridge
- with JBoss and MS SQL Server you need to create an ODBC datasource that
- references your MS SQL Server database. For this tutorial we will assume
- the datasource has been created and named <code><b>jboss_odbc</b></code>.<br>
+ bridge is properly installed on your system.
+ <p>To use the Sun JDBC-ODBC bridge with JBoss and MS SQL Server you need to
+ create an ODBC datasource that references your MS SQL Server database. For
+ this tutorial it will be assumed that a datasource named
<code><b>jboss_odbc</b></code>
+ has been created that points to an MS SQL Server database.<br>
<br>
</div>
- <h3>1.1 Installing the Merant DataDirect Connect JDBC Driver</h3>
+ <h3>1.2 Installing the Merant DataDirect Connect JDBC driver</h3>
<div class="para" align="left">
<p>According to the blurb on Merant's site:</p>
- <p>
+
<blockquote>
- <p>"Connect JDBC are optimized and reliable Type 4 JDBC drivers for
+ "Connect JDBC are optimized and reliable Type 4 JDBC drivers for
accessing data from Java applets or applications. Connect JDBC supports
the latest Sun JDBC specification and the J2EE framework, providing highly
scalable data access from heterogeneous platforms, and offering greater
- flexibility for today's demanding corporate environment."</p>
+ flexibility for today's demanding corporate environment."
</blockquote>
- <p> Before the Merant DataDirect Connect JDBC drivers can be used with JBoss,
- the driver's .jar files must be accessible to JBoss. There are two ways
- to accomplish this, you should choose one of the following options:</p>
+ <p> The Merant DataDirect Connect JDBC driver's .jar files must be accessible
+ to JBoss. There are two ways to accomplish this, you should choose one of
+ the following options:</p>
<ol>
<li> Run Merant's installation program then add the <code>base.jar</code>,
<code>util.jar</code> and <code>sqlserver.jar</code> files to the
<code>CLASSPATH</code>.
@@ -201,37 +202,59 @@
<ol start="2">
<li> Copy the <code>base.jar</code>, <code>util.jar</code> and
<code>sqlserver.jar</code>
files from the <code>%MERANT_HOME%/lib</code> directory to the
<code>%JBOSS_HOME%/lib/ext</code>
- directory.</li>
+ directory. This is the recommended option.</li>
</ol>
</div>
+ <h3>1.3 Installing the i-net OPTRA 2000 JDBC driver</h3>
+ <div class="para" align="left">
+ <p>According to the blurb on Merant's site:</p>
+ <blockquote> "i-net software announces the availability of i-net OPTA�
+ 2000, version 2.0. This version features i-net PLEXA�, a pool manager that
+ comes with i-net OPTA� free of charge. The easy to use pool manager is a
+ means of seamlessly employing connection pooling with i-net
OPTA".</blockquote>
+ <p> The i-net OPTRA 2000 JDBC driver's .jar files must be accessible to JBoss.
+ There are two ways to accomplish this, you should choose one of the following
+ options:</p>
+ <ol>
+ <li>Add the <code>Optra2000.jar</code> file to your <code>CLASSPATH</code>
+ when running JBoss. Or you can just...</li>
+ </ol>
+ <ol start="2">
+ <li> Copy the <code>Optra2000.jar</code> file to the
<code>%JBOSS_HOME%/lib/ext</code>
+ directory. This is the recommended option.</li>
+ </ol>
+ <p>Back to <a href="#INSTALL-MENU">install menu</a></p>
+ </div>
<p> </p>
- <div class="para" align="left">
-<hr>
+ <div class="para" align="left">
+ <hr>
</div>
<h2><a name="#CONFIGURE-JBOSS">2. Configure JBoss to use JDBC driver</a></h2>
- <div class="para" align="left">
+ <div class="para" align="left">
<p>The instructions for configuring JBoss to use your JDBC driver is different
depending on the version of JBoss you have. </p>
<ul>
<li><a href="#CONFIGURE-JBOSS-2">Configure JBoss versions up to 2.0
FINAL</a></li>
</ul>
<ul>
- <li><a href="#CONFIGURE-JBOSS-2-PLUS">Configure JBoss versions later than 2.0
FINAL</a></li>
+ <li><a href="#CONFIGURE-JBOSS-2-PLUS">Configure JBoss versions later than
+ 2.0 FINAL</a></li>
</ul>
<p> </p>
</div>
<h3><a name="#CONFIGURE-JBOSS-2">2.1 Configure JBoss 2.0 FINAL</a></h3>
<h4>2.1.1 Add the JDBC driver to jboss.properties</h4>
<div class="para" align="left">
- <p>Now that we have installed a JDBC driver for MS SQL Server, we need to
- tell JBoss that we would like it to use this driver. To do this we will
- add an entry for the driver to the list of drivers that JBoss can use. This
- list is stored in the <code>jbdc.drivers</code> entry in the
<code>jboss.properties</code>
- file. The file can be found in
<code>%JBOSS_HOME%/conf/<config-name></code>.
- For a standard distribution of JBoss, <code><config-name></code> is
- <code>default</code> whilst for the JBoss-Jetty it is <code>jetty</code>.
- The <code>jbdc.drivers</code> entry should be a single, continuous string.</p>
-
+ <p>Now that you have installed a JDBC driver for MS SQL Server, you need to
+ tell JBoss that you would like it to use this driver. Do this by adding
+ an entry for the driver to the list of JDBC drivers that JBoss loads at
+ startup. This list is stored in the <code>jbdc.drivers</code> entry in the
+ <code>jboss.properties</code> file. The <code>jboss.properties</code> file
+ can be found in <code>%JBOSS_HOME%/conf/<font
color="green"><config-name></font></code>.
+ For a standard distribution of JBoss, <code><font
color="green"><config-name></font></code>
+ is <code>default</code> whilst for the JBoss-Jetty it is <code>jetty</code>.
+ The <code>jbdc.drivers</code> entry should be a single, continuous string
+ of JDBC driver names separated with a comma.</p>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td width="50%" height="32" bgcolor="lightgreen">
@@ -253,7 +276,7 @@
<td width="50%"
><code>jdbc.drivers=org.hsql.jdbcDriver,jdbc.idbDriver,<b>com.merant.datadirect.jdbc.sqlserver.SQLServerDriver</b></code></td>
</tr>
</table>
- <br>
+ <br>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td width="50%" height="32" bgcolor="lightblue">
@@ -266,14 +289,11 @@
</table>
<br>
<br>
- </div>
-
+ </div>
<h4>2.1.2 Ensure that JBoss loads the JDBC driver correctly</h4>
- <div class="para" align="left">
+ <div class="para" align="left">
<p>Start JBoss and ensure that the JDBC driver is found (the relevant output
would be similar to the output shown below). Stop JBoss afterwards.</p>
-
-
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td height="32" bgcolor="lightgreen">
@@ -314,21 +334,19 @@
</table>
<br>
<br>
- </div>
-
+ </div>
<h4>2.1.3 Declare a DB connection pool for your driver</h4>
-
<div class="para" align="left">
- <p>Now that we know the driver is correctly installed, we need to set up a
- connection pool that EJBs can connect to. We will add an MLET entry into
- the <code>jboss.conf</code> file as shown below. The file can be found in
- <code>%JBOSS_HOME%/conf/<config-name></code>.</p>
- <p>For this tutorial, we will create a connection pool named
<code><b>SQLServerPool</b></code>
+ <p>At this point, you know that the driver is correctly installed. You will
+ now set up a connection pool that your EJBeans can connect to. Add an MLET
+ entry into the <code>jboss.conf</code> file as shown below. The file can
+ be found in <code>%JBOSS_HOME%/conf/<config-name></code>.</p>
+ <p>For this tutorial, you will create a connection pool named
<code><b>SQLServerPool</b></code>
as specified in the first argument in the MLET entry. The second argument
in the MLET entry should be your driver's <code>XADataSource</code>
classname.
If your driver doesn't support <code>XADataSource</code> use
<code>org.jboss.minerva.xa.XADataSourceImpl</code>
instead.</p>
- <table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
+ <table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td bordercolor="#000000" height="32" bgcolor="lightgreen">
<h4 align="center">Sun JDBC-OBDC bridge</h4>
@@ -374,16 +392,16 @@
</table>
<br>
<br>
- </div>
-
+ </div>
<h4>2.1.4 Configure the DB connection pool</h4>
-
<div class="para" align="left">
- <p>Before we can use our connection pool, we need to tell it how to find our
- database server. We can also take this chance to specifiy other configuration
- parameters for the pool. To do this, we will add an MBEAN entry into the
- <code>jboss.jcml</code> file as shown below. The file can be found in
<code>%JBOSS_HOME%/conf/<config-name></code>.</p>
- <table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
+ <p>Before you can use your spanking new connection pool, you need to tell
+ it how to find your database server (you can also take this chance to
specifiy
+ other configuration parameters for the pool like
"<code>LoggingEnabled</code>").
+ Tell your pool how to connect to your database server by adding an MBEAN
+ entry into the <code>jboss.jcml</code> file as shown below. The file can
+ be found in <code>%JBOSS_HOME%/conf/<config-name></code>.</p>
+ <table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td bordercolor="#000000" height="32" bgcolor="lightgreen">
<h4 align="center">Sun JDBC-OBDC bridge</h4>
@@ -397,12 +415,13 @@
</mbean> </code> </td>
</tr>
<tr>
- <td bordercolor="#000000" height="32" align="center"><p><font size="-1">*
- If the ODBC DSN is already configured with a username and password,
- you do not to include <b>dbusername</b> and
<b>dbpassword</b>.</font></p></td>
+ <td bordercolor="#000000" height="32" align="center">
+ <p><font size="-1">* If the ODBC DSN is already configured with a
username
+ and password, you do not to include <b>dbusername</b> and
<b>dbpassword</b>.</font></p>
+ </td>
</tr>
</table>
- <br>
+ <br>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td height="32">
@@ -432,7 +451,7 @@
</td>
</tr>
</table>
- <br>
+ <br>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td height="32" bgcolor="lightblue">
@@ -463,40 +482,40 @@
</tr>
</table>
<br>
- <br>
- </div>
-
+ <br>
+ </div>
<h4>2.1.5 Check that JBoss creates the connection pool</h4>
- <div class="para" align="left">
+ <div class="para" align="left">
<p>Start JBoss and ensure that the JDBC driver is found (the relevant output
would be similar to the output shown below). Stop JBoss afterwards.</p>
- <div class="code" align="left">
- [SQLServerPool] Starting<br>
+ <div class="code" align="left"> [SQLServerPool] Starting<br>
[SQLServerPool] XA Connection pool SQLServerPool bound to
java:/SQLServerPool<br>
- [SQLServerPool] Started
- </div>
- <br>
+ [SQLServerPool] Started </div>
<br>
+ <p>Back to <a href="#INSTALL-MENU">install menu</a></p> <p> </p>
+ </div>
+ <div class="para" align="left">
+ <hr>
</div>
-
- <h3><a name="#CONFIGURE-JBOSS-2-PLUS">2.2 Configure JBoss versions later than 2.0
FINAL</a></h3>
+ <h3><a name="#CONFIGURE-JBOSS-2-PLUS">2.2 Configure JBoss versions later than
+ 2.0 FINAL</a></h3>
<div class="para" align="left">
<h4>2.2.1 Tell JBoss about your JDBC driver</h4>
- <p>Now that we have installed a JDBC driver for MS SQL Server, we need to
- tell JBoss that we would like it to use this driver. To do this we will
- add an entry for the driver to the list of drivers that JBoss can use. This
- list is stored in the <code>jboss.jcml</code> file. The file can be found
- in <code>%JBOSS_HOME%/conf/<config-name></code>. For a standard
distribution
- of JBoss, <code><config-name></code> is <code>default</code> whilst
- for the JBoss-Jetty it is <code>jetty</code>. The entry should be a single,
- continuous list of comma-separated JDBC driver names.</p>
+ <p>Now that you have installed a JDBC driver for MS SQL Server, you need to
+ tell JBoss that you would like it to use this driver. Add an entry for the
+ driver to the list of drivers that JBoss loads at startup. This list is
+ stored in the <code>jboss.jcml</code> file. The file can be found in
<code>%JBOSS_HOME%/conf/<font color="green"><config-name></font></code>.
+ For a standard distribution of JBoss, <code><font
color="green"><config-name></font></code>
+ is <code>default</code> whilst for the JBoss-Jetty it is <code>jetty</code>.
+ The entry should be a single, continuous list of comma-separated JDBC driver
+ names.</p>
<p>Open the file and look for the entry that begins with the following
<code>mbean</code>
tag:</p>
<p> <code><font color="blue"><mbean
code="org.jboss.jdbc.JdbcProvider"
name="DefaultDomain:service=JdbcProvider"></font></code></p>
- <p> The list of drivers is kept in a sub-tag of this entry named
<code>Drivers</code>.
- Add your JBDC driver to the list as shown below. When you've finished, keep
- the file open as we still need to use it for the next step too.</p>
+ <p> The list of drivers is kept in an <code><attribute></code> sub-tag
+ of this entry named <code>Drivers</code>. Add your JBDC driver to the list
+ as shown below. When you've finished, keep the file open in your editor.</p>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td width="50%" height="32" bgcolor="lightgreen">
@@ -549,11 +568,10 @@
</div>
<h4></h4>
<h4>2.2.2 Create a DB connection pool</h4>
-
<div class="para" align="left">
- <p>Now that we have added our driver to the list so that JBoss knows about
- it, we need to create a connection pool that our EJBs can connect to. For
- this tutorial, we will create a connection pool named
<code><b>SQLServerPool</b></code>.
+ <p>At this point, you have told JBoss about your driver. You will now set
+ up a connection pool that your EJBeans can connect to. For this tutorial,
+ you will create a connection pool named <code><b>SQLServerPool</b></code>.
To create the connection pool, locate the <code>mbean</code> entry that
begins with the following line in the <code>jboss.jcml</code> file (you
should have kept it open as advised in the last step):</p>
@@ -561,7 +579,8 @@
name="DefaultDomain:service=XADataSource,name=DefaultDS"></font></code><br>
</p>
<p> Add the <code>mbean</code> entry given below to the file just <i>below</i>
- the <code>mbean</code> you have just located.</p>
+ the <code>mbean</code> entry you have just located above. This should be
+ added after the closing <code></mbean></code> tag!!.</p>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td bordercolor="#000000" height="32" bgcolor="lightgreen">
@@ -576,16 +595,16 @@
<attribute
name="URL">jdbc:odbc:<b>jboss_odbc</b></attribute><br>
<attribute
name="JDBCUser"><b>dbusername</b></attribute><br>
<attribute
name="Password"><b>dbpassword</b></attribute><br>
- </mbean>
- </code> </td>
+ </mbean> </code> </td>
</tr>
<tr>
- <td bordercolor="#000000" height="32" align="center"><p><font size="-1">*
- If the ODBC DSN is already configured with a username and password,
- you do not to include <b>dbusername</b> and
<b>dbpassword</b>.</font></p></td>
+ <td bordercolor="#000000" height="32" align="center">
+ <p><font size="-1">* If the ODBC DSN is already configured with a
username
+ and password, you do not to include <b>dbusername</b> and
<b>dbpassword</b>.</font></p>
+ </td>
</tr>
</table>
- <br>
+ <br>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td height="32">
@@ -614,12 +633,11 @@
<attribute
name="IdleTimeoutEnabled">false</attribute><br>
<attribute
name="IdleTimeout">1800000</attribute><br>
<attribute
name="MaxIdleTimeoutPercent">1.0</attribute><br>
- </mbean>
- </code></p>
- </td>
+ </mbean> </code></p>
+ </td>
</tr>
</table>
- <br>
+ <br>
<table class="code" width="93%" border="0" cellspacing="2" cellpadding="1"
align="center">
<tr bgcolor="khaki">
<td height="32" bgcolor="lightblue">
@@ -654,32 +672,30 @@
</tr>
</table>
<br>
- </div>
-
+ </div>
<h4>2.2.3 Check that JBoss creates the connection pool</h4>
- <div class="para" align="left">
+ <div class="para" align="left">
<p>Start JBoss and ensure that the JDBC driver is found and the connection
pool is created. The relevant out put is shown below for successful JBDC
driver load.</p>
- <div class="code" align="left">
- <p>[Transaction manager] Initializing<br>
+ <div class="code" align="left">
+ <p>[Transaction manager] Initializing<br>
[Transaction manager] Loaded JDBC-driver:org.hsql.jdbcDriver<br>
[Transaction manager] Loaded
JDBC-driver:org.enhydra.instantdb.jdbc.idbDriver<br>
[Transaction manager] Loaded
JDBC-driver:com.merant.datadirect.jdbc.sqlserver.SQLServerDriver<br>
[Transaction manager] Initialized</p>
- </div>
- <p>And a litte later...the output for the connection pool. Stop JBoss
afterwards.
+ </div>
+ <p>And a litte later...the output for the connection pool. Stop JBoss
afterwards.
</p>
- <div class="code" align="left">
- [SQLServerPool] Starting<br>
+ <div class="code" align="left"> [SQLServerPool] Starting<br>
[SQLServerPool] XA Connection pool SQLServerPool bound to
java:/SQLServerPool<br>
- [SQLServerPool] Started
- </div>
+ [SQLServerPool] Started </div>
<br>
+ <p>Back to <a href="#INSTALL-MENU">install menu</a></p>
</div>
<p> </p>
- <div class="para" align="left">
-<hr>
+ <div class="para" align="left">
+ <hr>
</div>
<h2><a name="#TROUBLE-SHOOTING">3. Troubleshooting</a></h2>
<div class="para" align="left"> </div>
@@ -693,8 +709,8 @@
incorrect. In the example above it should have been
<code>sun.jdbc.odbc.JdbcOdbcDriver</code>.<br>
b) a JDBC driver has not been properly installed - it's class files or .jar
file(s) are not in the <code>CLASSPATH</code> <br>
- <br>
- </div>
+ <br>
+ </div>
<h3>3.2 JBoss hangs while starting connection pool</h3>
<div class="para" align="left"> When JBoss is started, the sequence of messages
that is shown on the console stops midway. The last message refers to a
connection
@@ -707,7 +723,7 @@
[DefaultDS] Started[SQLServerPool] Starting<br>
[SQLServerPool] XA Connection pool SQLServerPool bound to
java:/SQLServerPool<br>
<font color="white">[SQLServerPool] Started<br>
- [Container factory] Starting<br>
+ [Container factory] Starting<br>
[Container factory] Started<br>
[JBossMQ] Starting<br>
[JBossMQ] Server Version 0.8 Started<br>
@@ -722,18 +738,21 @@
the correct hostname, database, username, password etc for the connection
pool.<br>
</p>
+ <p>Back to <a href="#INSTALL-MENU">install menu</a></p>
<p> </p>
+ </div>
+ <div class="para" align="left">
<hr>
</div>
<br>
<div class="footer" align="left">
<p>This document was created by Anthony Oguntimehin and <a
href="mailto:[EMAIL PROTECTED]">Kunle
Odutola</a> on 20 February 2000. Please report any errors and omissions
- to <b> </b>the <a
href="http://www.jboss.org/newsite/business/list.html">JBoss
- mailing list</a> in the first instance. You may copy the report to <a
href="mailto:[EMAIL PROTECTED]">Kunle
+ to <b> </b>the <a href="../business/list.html">JBoss mailing list</a> in
+ the first instance. You may copy the report to <a
href="mailto:[EMAIL PROTECTED]">Kunle
Odutola</a> as well. <br>
<br>
- Revision: $Id: mssql.htm,v 1.3 2001/03/24 01:23:11 kunle Exp $</p>
+ Revision: $Id: mssql.htm,v 1.4 2001/03/24 15:31:08 kunle Exp $</p>
</div>
</div>
</body>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
