| |
Create a UCP Data Source
Use this page to create a UCP data source. A UCP data source is an object bound to the JNDI tree that provides database connectivity through a pool of UCP connections. Applications can look up a data source on the JNDI tree and then reserve a database connection from a data source.
Configuration Options
Name Description Name A unique name that identifies this data source in the WebLogic domain.
MBean Attribute (Does not apply to application modules) :
JDBCDataSourceBean.NameChanges take effect after you redeploy the module or restart the server.
JNDI Name The JNDI path to where this data source is bound. By default, the JNDI name is the name of the data source.
To specify multiple JNDI names for the data source, enter each JNDI name on a separate line.
Applications that look up the JNDI path will get a
javax.sql.DataSourceinstance that corresponds to this data source.MBean Attribute (Does not apply to application modules) :
JDBCDataSourceParamsBean.JNDINamesChanges take effect after you redeploy the module or restart the server.
Database Type Select the database management system of your database. The Administration Console tailors the list of known JDBC drivers to the DBMS you select and constructs connection properties in a format that the DBMS supports.
Database Driver Select that 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.
Database Name Enter the name of the database that you want to connect to.
Service Name Enter the service name of the database to which you want to connect.
Host Name Enter the name or IP address of your database server.
Port Enter the port number on which your database server listens for connection requests.
Database User Name Enter the database user name that you want to use to create database connections.
Driver Class Name The full package name of JDBC driver class used to create the physical database connections in the connection pool in the data source.
For example:
oracle.jdbc.OracleDriverThe driver must be the name of a class that implements the
java.sql.Driverinterface. Check the driver documentation to find the full pathname.Note that the driver class must be in the classpath of any server to which the data source is deployed.
MBean Attribute (Does not apply to application modules) :
JDBCDriverParamsBean.DriverNameChanges take effect after you redeploy the module or restart the server.
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.UrlChanges take effect after you redeploy the module or restart the server.
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.PropertiesChanges take effect after you redeploy the module or restart the server.
System Properties The list of driver properties whose values are derived at runtime from the named system property.
Servers Lists the servers in your configuration on which you can deploy the data source.
Clusters Lists clusters and comprising servers on which you can deploy the data source.
|