+

Search Tips   |   Advanced Search

Data source settings

Use this page to edit the properties of a data source. You can access this console page in one of two ways:

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

 

Configuration tab

Test connection

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

Before you click Test connection, set your 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

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

Name

Specify 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

JNDI name

Specify 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

Container-managed persistence

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

Description

Specify a text description for the resource.

Data type String

Category

Specify a category string you 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 your selected JDBC driver implementation class to perform database-specific functions.

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

Component-managed Authentication Alias

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

Authentication Alias for XA Recovery

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

Use Component-managed Authentication Alias

Selecting this radio button specifies that the alias set for Component-managed Authentication is used at XA recovery time.

Data type Radio button

Specify:

Selecting this radio button enables you to choose an authentication alias from a drop-down list of configured aliases.

Data type Radio button

Container-managed Authentication Alias (deprecated)

Specify authentication data (a string path converted to userid and password) for container-managed sign-on to the resource.

Beginning with WAS V6.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.

Select an alias from the list. To define a new alias that is not displayed in the list:

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

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

  • Click New.

  • Define an alias.

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

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

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

  • Click Apply.

Data type Drop-down list

Mapping-Configuration Alias (deprecated)

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

Beginning with WAS V6.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 > Secure administration, applications, and infrastructure > Java Authentication and Authorization Service > Application logins and select an alias from the table.

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

Important data source properties

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 adapters
JDBC providers
Data sources

 

Related tasks


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

 

Related Reference


Administrative console preference settings

 

Reference topic