26.1 The Cookbook for Setting Up Packages in a Serviceguard Cluster
26.2 Setting Up and Testing a Serviceguard Package-less Cluster
26.3 Understanding How a Serviceguard Package Works
26.4 Establishing Whether You Can Utilize a Serviceguard Toolkit
26.5 Understanding the Workings of Any In-house Applications
26.6 Creating Package Monitoring Scripts, If Necessary
26.7Distributing the Application Monitoring Scripts to All Relevant Nodes in the Cluster
26.8 Creating and Updating an ASCII Application Configuration File (cmmakepkg “p)
26.9 Creating and Updating an ASCII Package Control Script (cmmakepkg “s)
26.10 Manually Distributing to All Relevant Nodes the ASCII Package Control Script
26.11 Checking the ASCII Package Control File (cmcheckconf)
26.12 Distributing the Updated Binary Cluster Configuration File (cmapplyconf)
26.13Ensuring That Any Data Files and Programs That Are to Be Shared Are Loaded onto Shared Disk Drives
26.14Starting the Package
26.15Ensuring That Package Switching Is Enabled
26.16Testing Package Failover Functionality
In this chapter, we look at the task of configuring our applications to be monitored and managed by Serviceguard. We look at configuring an in-house application whereby we need to write our own monitoring scripts that Serviceguard can use to ascertain whether our application is still functioning as we expect. We also look at some of the various Serviceguard Toolkits, which makes integrating common applications such as RDBMS applications, Web servers, and NFS into a Serviceguard cluster much easier. As with setting up a package-less cluster, we need to perform rigorous testing to ensure that our application behaves as expected when a failure occurs.
