Data source settings


To edit the properties of a data source.

We can access this admin console page in one of two ways:

Supported configurations: If the application uses an EJB 1.1 or a Java ™ Servlet 2.2 module, use the Data sources (WAS V4) > data_source console page.

Test connection

Activates the test connection service for validating application connections to the data source.

Before you click Test connection, set the data source properties and click Apply.

Scope

Scope of the JDBC provider that supports this data source. Only applications that are installed within this scope can use this data source.

Provider

JDBC provider that encapsulates the driver implementation classes to support this data source.

Name

Display name for the data source.

Valid characters for this name include letters and numbers, but NOT most of the special characters. For example we 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

JNDI name

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 used to access the various naming and directory services.

For example, we can use the name jdbc/markSection.

If we 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, we can see this string when you run the dump name space tool.

Data type String

Use this data source in container-managed persistence (CMP)

Specifies if this data source is used for container-managed persistence of enterprise beans.

This option triggers creation of a CMP connection factory, which corresponds to this data source, for the relational resource adapter.

Data type Boolean
Default True (enabled)

Description

Specifies a text description for the resource.

Data type String

Category

Category string we can use to classify or group the resource.

Data type String

Data store helper class name

Name of the DataStoreHelper implementation class that extends the capabilities of the selected JDBC driver implementation class to perform database-specific functions.

The appserver 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 the JDBC provider is DB2, then the default DataStoreHelper class is com.ibm.websphere.rsadapter.DB2DataStoreHelper. The admin console page we 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 the database configuration. Otherwise, the application might not work correctly. 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 for instructions on creating a custom DataStoreHelper class.

Data type Drop-down list or string (if user-defined DataStoreHelper is selected)

Component-managed authentication alias

This alias is used for database authentication at run time.

If the database is not secured, you do not need to set database authentication. This is not recommended for a production environment.

Avoid trouble: If we have a database that does not support user ID and password, like Cloudscape, 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 the database is secured, we need to set database authentication. You can configure authentication through:

  • The application

  • The admin console with Component-managed Authentication Alias. This is used when the application resource reference uses res-auth = Application.

If we do not set an alias through the component-managed authentication or otherwise, and the database requires the user ID and password to get a connection, then you will receive an exception during run time.

Data type Drop-down list

Authentication alias for XA recovery

This field is used to specify the authentication alias that should be used during XA recovery processing. If this alias name is changed after a server failure, the subsequent XA recovery processing will use the original setting that was in effect before the failure.

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).

If we have defined security domains in the appserver, we can click Browse... to select an authentication alias for the resource that we are configuring. Security domains allow us to isolate authentication aliases between servers. The tree view is useful in determining the security domain to which an alias belongs, and the tree view can help you determine the servers that will be able to access each authentication alias. The tree view is tailored for each resource, so domains and aliases are hidden when we cannot use them.

Data type Drop-down list

Container-managed authentication alias

Specifies authentication data, which is a JAAS - J2C authentication data entry, for container-managed signon to the resource.

Select an alias from the list.

To define a new alias not displayed in the list:

  1. Click Apply. Under Related Items, you now see a listing for J2EE Connector Architecture (J2C) authentication data entries.

  2. Click J2EE Connector Architecture (J2C) authentication data entries.

  3. Click New.

  4. Define an alias.

  5. Click OK. The console now displays an alias collection page. This page contains a table that lists all of the configured aliases. Before the table, this page also displays the name of the connection factory.

  6. Click the name of the J2C connection factory. You now see the configuration page for the connection factory.

  7. Select the new alias in the Container-managed authentication alias list.

  8. Click Apply.

If we have defined security domains in the appserver, we can click Browse... to select an authentication alias for the resource that we are configuring. Security domains allow us to isolate authentication aliases between servers. The tree view is useful in determining the security domain to which an alias belongs, and the tree view can help you determine the servers that will be able to access each authentication alias. The tree view is tailored for each resource, so domains and aliases are hidden when we cannot use them.

Data type Drop-down list

Mapping-configuration alias

Authentication alias for the Java Authentication and Authorization Service (JAAS) mapping configuration used by this connection factory.

Click Security > Global security . In the Authentication section, click Java Authentication and Authorization Service > Application logins, and select an alias from the table.

The DefaultPrincipalMapping JAAS configuration maps the authentication alias to the user ID and password. We can define and use other mapping configurations.

Data type Drop-down list

Common and required data source properties

These properties are specific to the data source that corresponds to the selected JDBC provider. They are either required by the data source, or are especially useful for the data source. We can find a complete list of the properties required for all supported JDBC providers in the information center.





Related concepts


Relational resource adapters and JCA
JDBC providers
Data sources

 

Related tasks

Set a data source
Set a JDBC provider
Monitor performance with Tivoli Performance Viewer (TPV)
Tuning the application serving environment

 

Related


Administrative console preference settings