WebSphere Application Server support for Oracle Real Application Clusters (RAC)

Resolving The Problem

WebSphere Application Server supports Oracle Real Application Cluster (RAC). This statement of support means that you are able to open problem records (PMRs) and get full support from IBM on any issues related to running RAC in WebSphere Application Server. However, the statement of support does not mean that WebSphere Application Server test suites were run against it.

Key points that you should consider when running Oracle RAC with the WebSphere Application Server:

• Re-balancing of pooled connections to all nodes after an Oracle Node comes up:
  There are two options available to re-balance connections in the WebSphere pool when an Oracle Node comes up:
1. By purging the WebSphere connection pool using MBeans (thus, forcing the pool to be repopulated with new connections from all Oracle nodes. For more details, see WebSphere connection pool can be purged using MBeans.
   
   
2. By configuring WebSphere connection pool Aged Timeout. Aged Timeout is the approximate interval (or age of a ManagedConnection), in seconds, before a ManagedConnection is discarded. The default value is 0, which will allow active ManagedConnections to remain in the pool indefinitely. For more details, see Connection pool settings.
   
   Note: Setting the Aged Timeout, or purging of connections, will not affect any ongoing transactions as the connection will not be discarded until they are no longer involved in a transaction.