1.6 Material covered in this book

< Day Day Up >

In the remainder of this redbook, we focus upon the applicable high availability concepts for IBM Tivoli Workload Scheduler, and two detailed implementations of high availability for IBM Tivoli Workload Scheduler, one using IBM HACMP and the other using Microsoft Cluster Service.

In particular, we show you:

Key architectural design issues and concepts to consider when designing highly available clusters for IBM Tivoli Workload Scheduler and IBM Tivoli Management Framework; refer to Chapter 2, "High level design and architecture" on page 31.
How to implement an AIX HACMP and Microsoft Cluster Service cluster; refer to Chapter 3, "High availability cluster implementation" on page 63.
How to implement a highly available installation of IBM Tivoli Workload Scheduler, and a highly available IBM Tivoli Workload Scheduler with IBM Tivoli Management Framework, on AIX HACMP and Microsoft Cluster Service; refer to Chapter 4, "IBM Tivoli Workload Scheduler implementation in a cluster" on page 183.
How to implement a highly available installation of IBM Tivoli Management Framework on AIX HACMP and Microsoft Cluster Service; refer to Chapter 5, "Implement IBM Tivoli Management Framework in a cluster" on page 411.

The chapters are generally organized around the products we cover in this redbook: AIX HACMP, Microsoft Cluster Service, IBM Tivoli Workload Scheduler, and IBM Tivoli Management Framework. The nature of high availability design and implementation requires that some products and the high availability tool be considered simultaneously, especially during the planning stage. This tends to lead to a haphazard sequence when applied along any thematic organization, except a straight cookbook recipe approach.

We believe the best results are obtained when we present enough of the theory and practice of implementing highly available IBM Tivoli Workload Scheduler and IBM Tivoli Management Framework installations so that you can apply the illustrated principles to your own requirements. This rules out a cookbook recipe approach in the presentation, but readers who want a "recipe" will still find value in this redbook.

If you are particularly interested in following a specific configuration we show in this redbook from beginning to end, the following chapter road map gives the order that you should read the material.

If you are not familiar with high availability in general, and AIX HACMP or Microsoft Cluster Service in particular, we strongly recommend that you use the introductory road map shown in Figure 1-13.

Figure 1-13: Introductory high availability road map

If you want an installation of IBM Tivoli Workload Scheduler in a highly available configuration by itself, without IBM Tivoli Management Framework, the road map shown in Figure 1-14 on page 29 gives the sequence of chapters to read. This would be appropriate, for example, for implementing a highly available Fault Tolerant Agent.

Figure 1-14: Road map for implementing highly available IBM Tivoli Workload Scheduler (no IBM Tivoli Management Framework, no Job Scheduling Console access through cluster nodes)

If you want to implement an installation of IBM Tivoli Workload Scheduler with IBM Tivoli Management Framework, use the road map shown in Figure 1-15.

Figure 1-15: Road map for implementing IBM Tivoli Workload Scheduler in a highly available configuration, with IBM Tivoli Management Framework

If you want to implement an installation of IBM Tivoli Management Framework in a highly available configuration by itself, without IBM Tivoli Workload Scheduler, the road map shown in Figure 1-16 on page 30 should be used. This would be appropriate, for example, for implementing a stand-alone IBM Tivoli Management Framework server as a prelude to installing and configuring other IBM Tivoli products.

Figure 1-16: Road map for implementing IBM Tivoli Management Framework by itself

High availability design is a very broad subject. In this redbook, we provide representative scenarios meant to demonstrate to you the issues that must be considered during implementation. Many ancillary issues are briefly mentioned but not explored in depth here. For further information, we encourage you to read the material presented in "Related publications" on page 607.

< Day Day Up >