Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Data access resources

Administer data access applications

These administrative tasks consist primarily of configuring the objects, or resources, through which applications connect with a backend, and tuning those resources to handle the volume of connection requests.


  1. If the application contains web modules or EJB modules that require access to a backend, configure resources according to your type of enterprise information system (EIS):

    • For a relational database, follow the steps outlined in the topic, Configuring a JDBC provider and data source. If you are using a DB2 database, the topic, Configuring an application to use pureQuery is another option. IBM Optim PureQuery Runtime provides an alternative to JDBC as a way to access the DB2 database.

    • For a non-relational database, or another type of EIS such as the Customer Information Control System (CICS), configure a resource adapter and connection factories. The topic, Accessing data using Java EE Connector Architecture connectors, provides information on setting up these objects.

    When you specify the JNDI name for resources, adhere to the following requirements:

    • Do not assign duplicate JNDI names across different resource types (such as data sources versus J2C connection factories or JMS connection factories).
    • Do not assign duplicate JNDI names for multiple resources of the same type in the same scope.

  2. Configure an authentication alias for the new web module resource or EJB module resource only if the application code, rather than WAS, authenticates connections with the backend. This security configuration is called component-managed authorization, and is indicated in the application deployment descriptor as res-auth = Application.

    Container-managed authorization, which is designated as res-auth = Container, indicates that Application Server performs signon for backend connections. The container-managed authentication alias must be specified on the application resource reference. This task can be done during application assembly or deployment, along with mapping the resource reference to a data source or connection factory resource. After application deployment, however, you can alter the container-managed authentication alias . Click Applications > Websphere enterprise applications > application_name , and select the link to the appropriate mapping page. For example, to alter the alias of an EJB module resource, you might click Map data sources for all 2.x CMP beans. For a web module resource, click Resource References.

    Read the J2EE connector security topic for detailed reference on resource authentication.

  3. If the application contains a client module that requires data access, see the topic, Configuring data access for application clients. In this single configuration process, you can define authentication data for either component-managed or container-managed signon.

  4. Specify connection pool settings.
  5. Test a connection to the new data source. See the article, Test connection service, for information on the available methods for testing connections. This article also addresses important data source settings that can affect the accuracy of your test connection results.

  6. Set the JDBC trace service. The JDBC trace log information augments the JVM log data for data source failures.

    To activate the trace , read the topic, Enabling trace at server startup.. Specify WAS.database as the trace group and select as the trace string.

  7. Gather connection pool statistics by activating the JDBC connection pool counters or the J2C connection pool counters. Alternatively, you can use Performance Monitoring Infrastructure (PMI) method calls to gather connection statistics; see the topic, Connection and connection pool statistics.

  8. Tune the resources to manage connection volume. See the topic, Data access tuning parameters.


Configure Java EE Connector connection factories in the administrative console
Install a resource adapter archive
Configure resource adapters
Update a stand-alone resource adapter archive
Java EE connector security
Map resource manager connection factory references to resource factories
Manage messages with message endpoints
Configure a JDBC provider and data source
Configure data access for application clients using the assembly tool and ACRCT
Resource references
Map-configuration alias
Select a J2C authentication alias
Considerations for isolated resource providers
Performing platform-specific tasks for JDBC access
Pass client information to a database
About Apache Derby
Verify Cloudscape automatic migration
Upgrade Cloudscape manually
Database performance tuning
Data access tuning parameters
Manage resources through JCA lifecycle management operations
Configure connection validation timeout
Relational resource adapters and JCA
JDBC providers
Data sources
Connection pooling
Access data using Java EE Connector Architecture connectors
Configure JDBC providers to use pureQuery to access DB2
Enable trace at server startup


Application scoped resources
Data source minimum required settings, by vendor
DB2 tuning parameters


Search Tips   |   Advanced Search