Administer data access applications

 

+

Search Tips   |   Advanced Search

 

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.

 

Procedure

  1. If your application contains Web modules or EJB modules that require access to a backend, configure resources according to your type of EIS:

    When you specify the JNDI name for resources...

    • 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 WebSphere Application Server, 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, we can alter the container-managed authentication alias using the administrative console. Click...

    Applications | Enterprise Applications | appname

    ...and select the link to the appropriate mapping page.

    For example, if you want to alter the alias of an EJB module resource, you might click...

    1.x CMP bean data sources

    ...or...

    2.x CMP bean data sources

    For a Web module resource, click...

    Resource References

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

  3. If your application contains a client module that requires data access, configure data access for application clients.

    In this single configuration process, we 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.

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

    To activate the trace using the administrative console, enable trace at server startup . Specify WAS.database as the trace group and select...

    com.ibm.ws.db2.logwriter

    ...as the trace string.

  7. Gather connection pool statistics by activating the JDBC connection pool counters or the J2C connection pool counters .

    Alternatively, use PMI method calls to gather connection statistics.

  8. Tune the resources to manage connection volume.

 

See also


Installing a Resource Adapter Archive (RAR) file
Configuring J2EE Connector connection factories in the administrative console
J2EE connector security
Mapping resource references to references
Configuring a JDBC provider and data source
Configuring data access for application clients using the assembly tool and ACRCT
Map resource references to resources
Performing platform-specific tasks for JDBC access
Pretesting pooled connections to ensure validity
Passing client information to a database
Configuring Cloudscape V5.1.60.x

Configuring Derby V10.0
Database performance tuning
Data access tuning parameters
Manage resources through JCA lifecycle management operations
Data access problems
JDBC trace configuration

Related concepts
Resource adapters
JDBC providers
Data sources
Connection pooling

Related tasks
Accessing data using J2EE Connector Architecture connectors

Related reference
Data source minimum required settings, by vendor
DB2 tuning parameters