Data source (WAS Version 4) settings (deprecated)
Create a Version 4.0 style data source. This data source uses the WebSphere Application Server 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(WAS V4) > data_source.
- Resources > JDBC > JDBC providers > JDBC_provider > Data sources(WAS V4) > data_source.
Scope
Scope of the JDBC provider that encapsulates the driver implementation classes to support this data source. Only applications installed within this scope can use this data source.
Provider
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 we create, 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 (WAS V4) configuration page again, where we 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
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 we set this value, save it, and restart the server, we can see this string when running the memory dump name space tool.
Information Value Data type String
Description
Text description for the resource.
Information Value Data type String
Category
Category string 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:
JDBC providers Data sources Configure a data source Administrative console scope settings