Migrate Collaborative Lifecycle Management applications to a cluster, Part 1. A high availability approach
From the developerWorks archives
Date archived: December 16, 2016 | First published: March 19, 2013
This article helps administrators of the Rational solution for Collaborative Lifecycle Management (CLM) migrate their stand-alone setups to a highly available cluster environment. The authors explain the CLM configuration for the high-availability deployment that they used for this article. Then they provide steps and sample code for making backups of the CLM databases available quickly by using a standby server and the IBM DB2 High Availability Disaster Recovery (HADR) feature. That server takes over quickly when the databases are not available on the primary server for any reason.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.