41 lines
2.4 KiB
HTML
41 lines
2.4 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head>
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
|
|
|
<title>Connection management architecture</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h5><a name="dataarch"></a>Connection management architecture</h5>
|
|
|
|
<p>The connection management architecture for both relational and procedural access to enterprise information systems is based on the J2EE Connector Architecture (JCA) specification. The connection manager, which pools and manages connections within an application server, is capable of managing connections obtained through both resource adapters that are defined by the JCA specification, and DataSources that are defined by the JDBC 2.0 Extensions Specification.</p>
|
|
|
|
<p>To make DataSource connections manageable by this connection manager that works only with resource adapters, WebSphere Application Server - Express provides its own resource adapter. From the connection manager point of view, JDBC DataSources and JCA connection factories look the same. Users of DataSources do not experience any programmatic or behavioral differences in their applications because of the underlying JCA architecture. JDBC users still configure and use DataSources according to the JDBC programming model.</p>
|
|
|
|
|
|
<blockquote>
|
|
<p><strong><a href="datapool.htm">Connection pooling</a></strong>
|
|
<br>See this topic for information about database connection pools.</p>
|
|
|
|
<p><strong><a href="datalife.htm">Connection life cycle</a></strong>
|
|
<br>This topic describes the life cycle of a database connection.</p>
|
|
|
|
<p><strong><a href="datashre.htm">Unshareable and shareable connections</a></strong>
|
|
<br>Database connections can be shared by more than one component of an application. See this topic for considerations about whether to share database connections or not.</p>
|
|
|
|
<p><strong><a href="datahand.htm">Connection handles</a></strong>
|
|
<br>This topic compares the characteristics of shared and unshared database connection references.</p>
|
|
|
|
<p><strong><a href="datacntr.htm">Connections and transactions</a></strong>
|
|
<br>See this topic for information about how connections behave in various transaction scopes.</p>
|
|
</blockquote>
|
|
|
|
</body>
|
|
</html>
|
|
|