Data source (WebSphere Application Server Version 4) settings

Use this page to create a Version 4.0 style data source. This data source uses the WAS Version 4.0 connection manager architecture. All EJB 1.x modules must use a Version 4.0 data source.

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

• Resources > JDBC > Data sources(WebSphere Application Server V4) > data_source.

• Resources > JDBC > JDBC providers > JDBC_provider > Data sources(WebSphere Application Server V4) > data_source.

Scope

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.

Provider

Specifies the JDBC provider that WAS uses for this data source.

The list shows all of the existing JDBC providers defined at the relevant scope. Select one from the list to use an existing JDBC provider as Provider.

Create new provider

Provides the option of configuring a new JDBC provider for the new data source.

Create New Provider is displayed only when creating, rather than edit, a data source.

If we click Create New Provider the Create a new JDBC provider wizard launches. Complete all of the wizard panels and click Finish. The administrative console now displays the Data sources (WebSphere Application Server V4) configuration page again, where you see the new JDBC provider name in the Provider field.

Name

Display name for the resource.

For example, we can set this field to Test Data Source.

Information	Value
Data type	String

JNDI name

Specifies the 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 about 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 setting this value, save it, and restart the server, we can see this string when you run the memory dump name space tool.

Information	Value
Data type	String

Description

Specifies a text description for the resource.

Information	Value
Data type	String

Category

Specifies a category string that we can use to classify or group the resource.

Information	Value
Data type	String

Database name

Name of the database of the data source to access.

For example, we can call the database SAMPLE.

Information	Value
Data type	String

Default user ID

User name to use for connecting to the database.

For example, we can use the ID db2admin.

Information	Value
Data type	String

Default password

Password used for connecting to the database.

For example, we can use the password db2admin.

Information	Value
Data type	String

Related concepts

JDBC providers

Data sources

Related tasks

Configure a data source using the administrative console

Administrative console scope settings