Use this page to create a Version 4.0 style data source. This data source uses the WebSphere Application Server Version 4.0 connection manager architecture. All of your EJB1.x modules must use this data source.
To view this administrative console page, click Resources > JDBC Providers > JDBC_provider > Data Sources (Version 4) > data_source.
Configuration tab
The level to which this resource definition is visible -- the cell, node, or server level.
Resources such as JDBC providers, namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates which are defined at more general scopes. Note that no matter what the scope of a defined resource, the resource's properties only apply at an individual server level. For example, if you define the scope of a data source at the cell level, all users in that cell can look up and use that data source, which is unique within that cell. However, resource property settings are local to each server in the cell. For example, if you define max connections to 10, then each server in that cell can have 10 connections.
When resources are created, they are always created into the current scope selected in the panel. To view resources in other scopes, specify a different node or server in the scope selection form.
Data type | String |
The display name for the resource.
For example, you can set this field to Test Data Source.
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 a text description for the resource.
Data type | String |
Specifies a category string that you can use to classify or group the resource.
Data type | String |
The name of the database that this data source accesses.
For example, you can call the database SAMPLE.
Data type | String |
The user name to use for connecting to the database.
For example, you can use the ID db2admin.
Data type | String |
The password used for connecting to the database.
For example, you can use the password db2admin.
Data type | String |
Related concepts
JDBC providers
Data sources
Related tasks
Configuring a data source using the administrative console