Use this page to edit the properties of a data source.
To view this administrative console page, click Resources > JDBC Providers > JDBC_provider > Data sources > data_source.
Version requirements: If your application uses an
Enterprise JavaBean (EJB) 1.1 or a Java Servlet 2.2 module, use the
Data sources (Version 4) > data_source console page.
Configuration tab
The scope of the JDBC provider that encapsulates the driver implementation classes to support this data source. Only applications that are installed within this scope can use this data source.
The display name for the data source.
Valid characters for this name include letters and numbers, but NOT most of the special characters. For example you can set this field to Test Data Source . But any name starting with a period (·) or containing special characters ( \ / , : ; " * ? < > | = + & % ' `) is not a valid name.
| Data type | String |
The Java Naming and Directory Interface (JNDI) name.
Distributed computing environments often employ naming and directory services to obtain shared components and resources. Naming and directory services associate names with locations, services, information, and resources.
Naming services provide name-to-object mappings. Directory services provide information on objects and the search tools required to locate those objects.
There are many naming and directory service implementations, and the interfaces to them vary. JNDI provides a common interface that is used to access the various naming and directory services.
For example, you can use the name jdbc/markSection.
If you leave this field blank a JNDI name is generated from the name of the data source. For example, a data source name of markSection generates a JNDI name of jdbc/markSection .
After you set this value, save it, and restart the server, you can see this string when you run the dump name space tool.
| Data type | String |
Specifies if this data source is used for container-managed persistence of enterprise beans.
If this field is checked, a CMP Connector Factory that corresponds to this data source is created for the relational resource adapter.
| Data type | Checkbox |
| Default | Enabled (The field is checked.) |
Specifies a text description for the resource.
| Data type | String |
Specifies a category string you can use to classify or group the resource.
| Data type | String |
The name of the DataStoreHelper implementation class that extends the capabilities of your selected JDBC driver implementation class to perform database-specific functions.
WebSphere Application Server provides a set of DataStoreHelper implementation classes for each of the JDBC provider drivers it supports. These implementation classes are in the package com.ibm.websphere.rsadapter. For example, if your JDBC provider is DB2, then your default DataStoreHelper class is com.ibm.websphere.rsadapter.DB2DataStoreHelper.
The administrative console page you are viewing, however, might make multiple
DataStoreHelper class names available to you in a drop-down list; be sure to select the one required by your database configuration. Otherwise, your application might not work correctly. If you want to use a DataStoreHelper other than those displayed in the drop-down list, select Specify a user-defined DataStoreHelper and type a fully qualified class name. Refer to the Information Center topic "Example: Developing your own DataStoreHelper class."
| Data type | Drop-down list or string (if user-defined DataStoreHelper is selected) |
This alias is used for database authentication at run time.
The Component-managed Authentication Alias is only used when the application resource reference is using res-auth = Application.
If your database (for example, Cloudscape) does not support user ID and password, then do not set the alias in the component-managed authentication alias or container-managed authentication alias fields. Otherwise, you see the warning message in the system log to indicate that the user and password are not valid properties. (This message is only a warning message; the data source is still created successfully.)
If you do not set an alias (component-managed or otherwise), and your database requires the user ID and password to get a connection, then you receive an exception during run time.
| Data type | Drop-down list |
This optional field is used to specify the authentication alias that should be used during XA recovery processing.
If the
resource adapter does not support XA transactions, then this field will not be displayed. The default value will come from the selected alias for application authentication (if specified).
| Data type | Radio button |
| Data type | Radio button |
Specifies authentication data (a string path converted to userid and password) for container-managed sign-on to the resource.
Note: Beginning with WebSphere Application Server Version 6.0, the container-managed authentication alias is superseded by the specification of a login configuration on the resource-reference mapping at deployment time, for components with res-auth=Container.
Choose from aliases defined under Security >JAAS Configuration > J2C Authentication Data. To define a new alias not already appearing in the pick list:
| Data type | Drop-down list |
The authentication alias for the Java Authentication and Authorization Service (JAAS) mapping configuration that is used by this connection factory.
Note: Beginning with WebSphere Application Server Version 6.0, the Mapping-Configuration Alias is superseded by the specification of a login configuration on the resource-reference mapping at deployment time, for components with res-auth=Container .
Click Security > JAAS Configuration > Application Logins Configuration and select an alias from the list.
The DefaultPrincipalMapping JAAS configuration maps the authentication alias to the userid and password. You may define and use other mapping configurations.
| Data type | Drop-down list |
These properties are specific to the data source that corresponds to your selected JDBC provider. They are either required by the data source, or are especially useful for the data source. You can find a complete list of the properties required for all supported JDBC providers in the topic "Vendor-specific data sources minimum required settings" in the Information Center.
Related concepts
Resource adapter
JDBC providers
Data sources
Related tasks
Configuring a data source using the administrative console
Configuring a JDBC provider using the administrative console
Monitoring performance with Tivoli Performance Viewer (TPV)