![]() ![]() ![]() ![]() |
Create a GridLink Data Source: Connection Properties
Use this page to create a JDBC GridLink data source. A JDBC GridLink data source is an object bound to the JNDI tree that provides database connectivity through a pool of JDBC connections. Applications can look up a data source on the JNDI tree and then reserve a database connection from a data source.
Buttons
Name Description Generate URL and Properties Select this button to enter the information required for WebLogic Server to create the fully qualified URL for your JDBC connections.
Test Database Connection Select this button to test this database connection.
Configuration Options
Name Description Data Source Name A unique name that identifies this data source in the WebLogic domain.
MBean Attribute (Does not apply to application modules) :
JDBCDataSourceBean.Name
Changes take effect after you redeploy the module or restart the server.
Type The type of data source: generic, GridLink, or multi data source.
Driver Class Name Select the driver that you want to use to create physical database connections. The data source pools the database connections for use and reuse by your applications.
* indicates that the driver is explicitly supported by Oracle WebLogic Server.
If your driver is not listed, select "other."
Configuration Options
Name Description Database URL The URL of the database to connect to. The format of the URL varies by JDBC driver.
The URL is passed to the JDBC driver to create the physical database connections.
MBean Attribute (Does not apply to application modules) :
JDBCDriverParamsBean.Url
Changes take effect after you redeploy the module or restart the server.
Password The password attribute passed to the JDBC driver when creating physical database connections.
The value is stored in an encrypted form in the descriptor file and when displayed in an administration console.
MBean Attribute (Does not apply to application modules) :
JDBCDriverParamsBean.Password
Changes take effect after you redeploy the module or restart the server.
Test Table Name or SQL Statement The name of the database table to use when testing physical database connections. This name is required when you specify a Test Frequency and enable Test Reserved Connections.
The default SQL code used to test a connection is
select count(*) from TestTableName
Most database servers optimize this SQL to avoid a table scan, but it is still a good idea to set the Test Table Name to the name of a table that is known to have few rows, or even no rows.
If the Test Table Name begins with
SQL
, then the rest of the string following that leading token will be taken as a literal SQL statement that will be used to test connections instead of the standard query. For example:SQL BEGIN; Null; END;
For an Oracle database, you can reduce the overhead of connection testing by setting Test Table Name to
SQL PINGDATABASE
which uses thepingDatabase()
method to test the Oracle connection. For any JDBC 4.0 database, it is possible to use "SQL ISVALID" to use theisValid()
method on the connection.MBean Attribute (Does not apply to application modules) :
JDBCConnectionPoolParamsBean.TestTableName
Properties The list of properties passed to the JDBC driver that are used to create physical database connections. For example: server=dbserver1. List each property=value pair on a separate line.
To enable driver-level features, add the driver property and its value to the Properties list. WebLogic Server sets driver-level properties in the Properties list on the driver's ConnectionPoolDataSource object.
- Note:
- For security reasons, when WebLogic Server is running in Production mode, you cannot specify database passwords in this properties list. Data source deployment will fail if a password is specified in the properties list. To override this security check, use the command line argument "weblogic.management.allowClearTextPasswords" when starting the server.
MBean Attribute (Does not apply to application modules) :
JDBCDriverParamsBean.Properties
Changes take effect after you redeploy the module or restart the server.
System Properties The list of system properties passed to the JDBC driver that are used to create physical database connections. For example: server=dbserver1. List each property=value pair on a separate line.
MBean Attribute (Does not apply to application modules) :
JDBCPropertyBean.SysPropValue
Changes take effect after you redeploy the module or restart the server.
Initial Capacity The number of physical connections to create when creating the connection pool in the data source. If unable to create this number of connections, creation of the data source will fail.
MBean Attribute (Does not apply to application modules) :
JDBCConnectionPoolParamsBean.InitialCapacity
Minimum value:
0
Maximum value:
2147483647
Maximum Capacity The maximum number of physical connections that this connection pool can contain.
MBean Attribute (Does not apply to application modules) :
JDBCConnectionPoolParamsBean.MaxCapacity
Minimum value:
1
Maximum value:
2147483647
Minimum Capacity The minimum number of physical connections that this connection pool can contain after it is initialized.
Default: InitialCapacity
Used only for connection pool shrinking calculations.
For compatibility,
InitialCapacity
is used ifMinCapacity
is not configured.Once a data source has gone through a suspend/resume, the larger value of either
MinCapacity
orInitialCapacity
is used.MBean Attribute (Does not apply to application modules) :
JDBCConnectionPoolParamsBean.MinCapacity
Minimum value:
0
Maximum value:
2147483647
Statement Cache Type The algorithm used for maintaining the prepared statements stored in the statement cache.
Options are:
LRU - when a new prepared or callable statement is used, the least recently used statement is replaced in the cache.
FIXED - the first fixed number of prepared and callable statements are cached.
MBean Attribute (Does not apply to application modules) :
JDBCConnectionPoolParamsBean.StatementCacheType
Changes take effect after you redeploy the module or restart the server.
Statement Cache Size The number of prepared and callable statements stored in the cache. (This may increase server performance.)
WebLogic Server can reuse statements in the cache without reloading the statements, which can increase server performance. Each connection in the connection pool has its own cache of statements.
Setting the size of the statement cache to 0 turns off statement caching.
MBean Attribute (Does not apply to application modules) :
JDBCConnectionPoolParamsBean.StatementCacheSize
Minimum value:
0
Maximum value:
1024
![]() |