Tuning connection pools
Using connection pools helps to both alleviate connection
management overhead and decrease development tasks for data access.
Each time an application attempts to access a backend store (such
as a database), it requires resources to create, maintain, and release
a connection to that datastore. To mitigate the strain this process
can place on overall application resources, the application server
enables administrators to establish a pool of backend connections
that applications can share on an application server. Connection pooling
spreads the connection overhead across several user requests, thereby
conserving application resources for future requests.
Throttling inbound message flow for JCA 1.5 message-driven beans
This topic describes how to throttle message delivery for
message-driven beans (MDB) which are deployed as message endpoints
for Java Platform, Enterprise Edition (Java EE) Connector Architecture (JCA) Version
1.5 inbound resource adapters.
Database performance tuning
Database performance tuning can dramatically affect the
throughput of your application. For example, if your application requires
high concurrency (multiple, simultaneous interactions with backend
data), an improperly tuned database can result in a bottleneck. Database
access threads accumulate in a backlog when the database is not configured
to accept a sufficient number of incoming requests.
DB2 Universal Database performance tips
You can easily adjust your system QSQSRVR prestart job
settings to optimize the process of acquiring connections from DB2 Universal Database™ for IBM® i.
Directory conventions
References in product information to app_server_root, profile_root,
and other directories imply specific default directory locations.
Become familiar with the conventions in use for WebSphere® Application
Server.
Last updated: April 18, 2014 05:01 AM CDT http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=container_data_tuning File name: container_data_tuning.html