ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaha_5.4.0.1/jdbcreqs.htm

110 lines
7.7 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="JDBC requirements" />
<meta name="abstract" content="Before you write and deploy your JDBC applications, you may need to include specific jar files in your classpath." />
<meta name="description" content="Before you write and deploy your JDBC applications, you may need to include specific jar files in your classpath." />
<meta name="DC.Relation" scheme="URI" content="jdbcgets.htm" />
<meta name="DC.Relation" scheme="URI" content="jdbctydr.htm" />
<meta name="DC.Relation" scheme="URI" content="jdbctutr.htm" />
<meta name="DC.Relation" scheme="URI" content="dasrjndi.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="jdbcreqs" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>JDBC requirements</title>
</head>
<body id="jdbcreqs"><a name="jdbcreqs"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">JDBC requirements</h1>
<div><p>Before you write and deploy your JDBC applications, you may need
to include specific jar files in your classpath.</p>
<div class="section"><h4 class="sectiontitle">Core JDBC</h4><p>For core Java™ Database Connectivity (JDBC) access
to the local database, there are no requirements. All support is built in,
preinstalled, and configured.</p>
</div>
<div class="section"><h4 class="sectiontitle">JDBC 2.0 optional package</h4><p>If you need to use the
classes of the JDBC 2.0 optional package, you must include the jdbc2_0-stdext.jar
file in your classpath. This Java ARchive (JAR) file contains all the
standard interfaces that you need to write your application to use the JDBC
2.0 optional package. To add the JAR file to your extensions classpath, create
a symbolic link from the UserData extensions directory to the location of
the JAR file. You only need to perform this once; the JAR file in the JDBC
2.0 optional package is always available to your applications at runtime.
Use the following command to add the optional package to the extensions classpath:</p>
<pre> ADDLNK OBJ('/QIBM/ProdData/OS400/Java400/ext/jdbc2_0-stdext.jar')
NEWLNK('/QIBM/UserData/Java400/ext/jdbc2_0-stdext.jar')</pre>
<p><strong>Note:</strong> This
requirement is only for J2SDK 1.3. Since J2SDK 1.4 is the first release with
JDBC 3.0 support, all of JDBC (that is, the core JDBC and the optional package)
moves into the base J2SDK runtime JAR file that your program always finds.</p>
</div>
<div class="section"><h4 class="sectiontitle">Java Transaction API</h4><p>If you need to use the Java Transaction
API (JTA) in your application, you must include the jta-spec1_0_1.jar file
in your classpath. This JAR file contains all the standard interfaces that
you need to write your application to use JTA. To add the JAR file to your
extensions classpath, create a symbolic link from the UserData extensions
directory to the location of the JAR file. This is a one-time operation and
once completed, the JTA JAR file is always available to your application at
runtime. Use the following command to add JTA to the extensions classpath:</p>
<pre> ADDLNK OBJ('/QIBM/ProdData/OS400/Java400/ext/jta-spec1_0_1.jar')
NEWLNK('/QIBM/UserData/Java400/ext/jta-spec1_0_1.jar')</pre>
</div>
<div class="section"><h4 class="sectiontitle">JDBC compliance</h4><p>The native JDBC driver is compliant
with all relevant JDBC specifications. The compliance level of the JDBC driver
is not dependent on the <span class="keyword">i5/OS™</span> release,
but on the JDK release you use. The native JDBC driver's compliance level
for the various JDKs is listed as follows:</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th align="left" valign="top" width="19.897959183673468%" id="d0e61">J2SDK release</th>
<th align="left" valign="top" width="80.10204081632652%" id="d0e63">JDBC driver's compliance level</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="19.897959183673468%" headers="d0e61 ">JDK 1.1</td>
<td valign="top" width="80.10204081632652%" headers="d0e63 ">This JDK is compliant with JDBC 1.0.</td>
</tr>
<tr><td valign="top" width="19.897959183673468%" headers="d0e61 ">JDK 1.2</td>
<td valign="top" width="80.10204081632652%" headers="d0e63 ">This JDK is compliant with JDBC 2.0 and supports JDBC 2.1 optional
package.</td>
</tr>
<tr><td valign="top" width="19.897959183673468%" headers="d0e61 ">JDK 1.3</td>
<td valign="top" width="80.10204081632652%" headers="d0e63 ">This JDK is compliant with JDBC 2.0 and supports JDBC 2.1 optional
package (there were no JDBC-related changes for JDK 1.3).</td>
</tr>
<tr><td valign="top" width="19.897959183673468%" headers="d0e61 "><img src="./delta.gif" alt="Start of change" />JDK 1.4 and subsequent versions<img src="./deltaend.gif" alt="End of change" /></td>
<td valign="top" width="80.10204081632652%" headers="d0e63 "><img src="./delta.gif" alt="Start of change" />These JDK versions are compliant with JDBC 3.0, but the JDBC optional
package no longer exists (support for it is now part of the core JDK).<img src="./deltaend.gif" alt="End of change" /></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="jdbcgets.htm" title="The Java Database Connectivity (JDBC) driver shipped with the Developer Kit for Java is called the Developer Kit for Java JDBC driver. This driver is also commonly known as the native JDBC driver.">Get started with JDBC</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="jdbctydr.htm" title="This topic defines the Java Database Connectivity (JDBC) driver types. Driver types are used to categorize the technology used to connect to the database. A JDBC driver vendor uses these types to describe how their product operates. Some JDBC driver types are better suited for some applications than others.">Types of JDBC drivers</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="jdbctutr.htm" title="The following is a tutorial on writing a Java Database Connectivity (JDBC) program and having it run on the an iSeries server with the native JDBC driver. It is designed to show you the basic steps required for your program to run JDBC.">JDBC tutorial</a></div>
<div><a href="dasrjndi.htm" title="DataSources work hand-in-hand with the Java Naming and Directory Interface (JNDI). JNDI is a Java abstraction layer for directory services just as Java Database Connectivity (JDBC) is an abstraction layer for databases.">Use JNDI for the examples</a></div>
</div>
</div>
</body>
</html>