IMS Server database high availability

IBM® Security Access Manager for Enterprise Single Sign-On interfaces with corporate directories without changing the directory schema. There is no additional load or high availability requirements for existing directory services.IBM Security Access Manager for Enterprise Single Sign-On leverages on the existing high-availability features of the database products that it works with – IBM DB2®, Microsoft SQL Server, and Oracle.

The most popular method for database high availability is using the database clustering feature together with a compatible third-party high availability solution such as Microsoft Cluster Server (MSCS). A typical clustered configuration involves an active-passive pair of database nodes with access to a shared disk storage. Newer versions of database products provide alternative high availability solutions that do not require a shared disk storage to maintain an active-passive configuration. For example, Microsoft SQL Server 2005 Database Mirroring feature and DB2 HADR feature.

DB2 HADR feature might not necessarily support automatic failover in its basic configuration. Additional software components such as SA-MP for DB2 and additional configuration at the database and WebSphere® Application Server are required to support automatic failover. For example, configuration of the JDBC connection string. You can create a WebSphere Application Server data source with the JNDI key of "jdbc/ims", and an associated J2C alias "imsauthdata" with the multi-node JDBC connection string during the initial IMS Server configuration.

IBM Security Access Manager for Enterprise Single Sign-On also support DB2 SQL replication feature. However, this feature is more appropriate for a distributed IMS Server setup.