Technical data

16 Managing JDBC Connectivity
16-26 Administration Guide
Refer to the following table for more information on association and assignment in the
configuration process.
(You can assign more than one Data Source to a pool, but there is no practical purpose
for this.) You can assign these Data Source/pool combinations to more than one server
or cluster, but they must be assigned in combination. For example, you can’t assign a
DataSource to Managed Server A if its associated Connection Pool is assigned only to
Server B.
You can configure dynamic Connection Pools (after the server starts) using the
command-line interface. See “JDBC Configuration Tasks Using the Command-Line
Interface” on page 16-29. You can also configure dynamic Connection Pools
programatically using the API (see Creating a Dynamic Connection Pool in
Programming WebLogic JDBC).
Table 16-18 Association and Assignment Scenarios
Scenario
#
Associated. . . Assign . . . . Target
Description
1 Data Source A with
Connection Pool A
1. Data Source A to Managed
Server 1, and
2. Connection Pool A to
Managed Server 1.
Data Source and
Connection Pool
assigned to the
same target.
2 Data Source B with
Connection Pool B
1. Data Source B to Cluster X,
then
2. Connection Pool B to Cluster
X.
Data Source and
Connection
assigned to
related
server/cluster
targets.
3 Data Source C with
Connection Pool C
n Data Source A and
Connection Pool A to
Managed Server 1.
- AND -
n Data Source A to Cluster X;
then assign Connection Pool
A to Cluster X.
Data Source and
Connection Pool
assigned as a unit
to two different
targets.