Data source (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 the 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

Scope	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. Cell The most general scope. Resources defined at the Cell scope are visible from all Nodes and servers, unless they are overridden. To view resources defined in the cell scope, do not specify a server or a node name in the scope selection form. Node The default scope for most resource types. Resources defined at the Node scope override any duplicates defined at the Cell scope and are visible to all servers on the same node, unless they are overridden at a server scope on that node. To view resources defined in a node scope, do not specify a server, but select a node name in the scope selection form. Server The most specific scope for defining resources. Resources defined at the Server scope override any duplicate resource definitions defined at the Cell scope or parent Node scope and are visible only to a specific server. To view resources defined in a server scope, specify a server name as well as a node name in the scope selection form. 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
Name	Specifies the display name for the resource. For example you can set this field to Test Data Source. 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 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 dumpNameSpace.sh. Data type String
Description	Specifies a text description for the resource. Data type String
Category	Specifies a category string that you can use to classify or group the resource. Data type String
Database Name	Name of the database that this data source accesses. For example, you can call the database SAMPLE. Data type String
Default User ID	Specifies the user name to use for connecting to the database. For example, you can use the ID db2admin. Data type String
Default Password	Specifies the password used for connecting to the database. For example, you can use the password db2admin. Data type String

 

---