Before you start
This series from the IBM Continuous Computing team focuses on building a highly available solution platform for Java™ 2 Platform, Enterprise Edition (J2EE). Follow along as the team uses existing hardware and software from across IBM divisions to produce a complete solution that offers high availability. In the first phase of this series, we use existing products to establish the baseline of what is possible using current technologies. Next, we enhance the design of the system to take advantage of emerging technologies in the areas of automation, faster failure detection, and multisite failover.
This tutorial describes how to set up IBM DB2® Universal Database™ (UDB) for high availability using High Availability Disaster Recovery (HADR) software, Automatic Client Reroute, and IBM Tivoli® System Automation for Multiplatforms.
If you want to learn how to set up DB2 for high availability, take this tutorial. Basic knowledge of DB2 UDB and the Linux™ operating system will help you complete the tasks.
To set up the environment described in this tutorial, you'll need:
- A three-node cluster on IBM eServer™ xSeries® hardware
- Redundant network adapters (NICs)
- Sufficient logical disks (LUNs) to host all database data
- IBM Tivoli System Automation (TSA) for Multiplatforms Version 1.2
- DB2 UDB Enterprise Server Edition Version 8.2 or later
- Red Hat Enterprise Linux 3.0
- The first node hosts our primary database instance, the second node hosts our standby database instance, and the third node is used by TSA to provide quorum functionality. The third node does not need to be dedicated to this function and can be used to perform other functions or to support other applications. If a shared disk is available, it can be used to provide quorum functionality instead of the third node. (See the Resources section for information about this configuration.)

