Administer data access applications

1. Configure resources according to the type of backend enterprise information system (EIS):

   • For a relational database, set a JDBC provider and data source.

     For a DB2 database pureQuery provides an alternative to JDBC.

   • For a non-relational database, or another type of EIS such as the CICS, configure a resource adapter and connection factories.

   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. Set an authentication alias for the resource only if 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 during application assembly or deployment, along with mapping the resource reference to a data source or connection factory resource.

   Applications | Websphere enterprise apps | application_name

   Select the link to the appropriate mapping page. For example, to alter the alias of an EJB module resource, we might click...

   Map data sources for all 2.x CMP beans

   For a Web module resource, click...

   Resource References

3. If the application contains a client module that requires data access, set data access for application clients.

4. Specify connection pool settings.
5. Test connection to data source.

6. Set the JDBC trace service.

   trace group	WAS.database
   trace string	com.ibm.ws.db2.logwriter

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

 

Related

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