WebSphere Application Server tuning

Optimal WebSphere Application Server settings vary from implementation to implementation.
However, always address the following items for each WebSphere Application Server
instance:
Ensure that the Object Request Broker (ORB) thread pool is equal to the maximum
amount of concurrent RMI (direct calls to the WCC ServiceController stateless session
bean) WCC transactions expected for each WCC instance. ORB threads block WCC
service requests. Therefore, the maximum thread pool limit is your theoretical maximum
number of concurrent users.
Ensure that the Web container thread pool is equal or tuned to a high enough level to
accommodate Web service requests, if applicable for your application. In most cases, this
thread pool does not need to be adjusted because Web container threads are
non-blocking and can handle multiple WCC service requests concurrently.
Set the Enterprise JavaBeans™ (EJB™) cache size to 3500, which is the optimal setting
for WCC.
On the Java Database Connectivity (JDBC™) data source used for WCC (default Java
Naming and Directory Interface (JNDI) name is jdbc/DWLCustomer), set the Prepared
Statement cache size to 300, which can improve transaction response time by 5% to 15%.
Use the default logging level (or lower) that is set by WebSphere.