BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
| WebLogic Server Doc Home | Console Online Help | Previous Topic | Next Topic | Contents | Index | View as PDF

JDBC Data Sources

The following procedures describe how to use the Administration Console to set the attributes for configuring and managing Data Sources. Read about Data Sources in Managing JDBC Connectivity.

Configure a JDBC Data Source

1. Click to expand the JDBC node.

2. Click the Data Sources node. The Data Sources table displays in the right pane showing all the data sources defined in your domain.

3. Click the Configure a New JDBC Data Source text link. A dialog displays in the right pane showing the tabs associated with configuring a new data source.

4. Enter values in the Name, JNDI Name, and Pool Name attribute fields.

5. Click Create to create a data source instance with the name you specified in the Name field. The new instance is added under the Data Sources node in the left pane.

For what's next in the configuration process, see the Configuration Procedures in Managing JDBC Connectivity.

Clone a JDBC Data Source

1. Click to expand the JDBC node.

2. Click the Data Sources node. The Data Sources table displays in the right pane showing all the data sources defined in your domain.

3. Click the Clone icon in the row of the data source you want to clone. A dialog displays in the right pane showing the tabs associated with cloning a data source.

4. Enter values in the Name, JNDI Name, and Pool Name attribute fields.

5. Click Create to create a data source instance with the name you specified in the Name field. The new instance is added under the Data Sources node in the left pane.

Monitor All Instances of a JDBC Data Source

1. Click to expand the JDBC node.

2. Click the Data Sources node in the left pane. The Data Sources table displays in the right pane showing all the data sources defined in the domain.

3. Click the Monitor All Instances icon in the row of the data source you want to monitor. A dialog displays in the right pane showing all instances of the data source deployed across the server domain.

Assign a JDBC Data Source

1. Click the instance node in the left pane under Data Sources for the source you want to assign. A dialog displays in the right pane showing the tabs associated with this instance.

2. Click the Targets tab.

3. Complete the following steps for the Servers, Groups, and Clusters tabs:

   1. Select one or more targets in the Available column that you want to assign to the data source.

   2. Click the mover control to move the targets you selected to the Chosen column.

   3. Click Apply to save your assignments.

Configuration

The following tables describe the attributes you use to configure and manage Data Sources. Read about Data Sources in Managing JDBC Connectivity.

General

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Name | This attribute reports the name of the data source. | The name can be up to 256 alphanumeric characters, but may not contain commas or spaces. | Null
JNDIName | This attribute sets the JNDI name associated with this data source. Sets the JNDI path to where this DataSource is bound. | String | Null
PoolName | Sets the name of the JDBC connection pool that is associated with this DataSource. DataSource will return a connection from the associated connection pool. | String | Null
Row Prefetch Enabled | Set to true to enable row prefetching between client and WebLogic Server for each ResultSet. When an external client does JDBC access through Weblogic Server, row prefetching improves performance by fetching multiple rows from the server to the client in one server access. The WebLogic Server will ignore this setting and not use row prefetching when the client and WebLogic Server are in the same JVM. | Boolean Selected = true Not Selected = false | Not selected (default) = false.
Row Prefetch Size | The number of rows that will be prefetched between the client and WebLogic Server for each ResultSet. The optimal value is very dependent on the particulars of the query. Generally, increasing this number will increase performance, until a particular value is reached. At that point further increases do not result in any significant performance increase. Very rarely will increased performance result from exceeding 100 rows. The default value should be reasonable for most situations. | Legal Minimum = 2 Legal Maximum = 65536 | Default = 48
Stream Chunk Size | The number of rows that will be prefetched between client and WebLogic Server for each ResultSet. The optimal value is very dependent on the particulars of the query. Generally, increasing this number will increase performance, until a particular value is reached. At that point further increases do not result in any significant performance increase. Very rarely will increased performance result from exceeding 100 rows. The default value should be reasonable for most situations. | Integer. Minimum = 1. Maximum = 65,536. | Default = 256.

Target

Servers

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Target Servers | This attribute allows the user to select the servers to be used as targets for this datasource. | List | Null

Clusters

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Target Clusters | This attribute allows the user to select the clusters to be used as targets for this datasource. | List | Null

Notes

Attribute | Description | Range of Values | Default Value
Notes | This attribute provides a space for user supplied information. | The value must be an alphanumeric string. | Null

Read about Data Sources in Managing JDBC Connectivity.

Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.