on the VM or vPar guest. The number of times HP Serviceguard attempts to restart cmappmgr and the VM or vPar guest application is defined by the service_restart value, set for the cmappmgr service in the guest package. If the number of restart attempts exceeds the service_restart value, HP Serviceguard fails over the VM or vPar guest package to its configured VM or vPar Host failover node, as shown in Figure 4 (page 22).
Figure 4 Failover of a VM or vPar guest due to an application failure
To configure the VM or vPar guest application monitoring service:
1.Create and distribute client or server security keys.
2.Configure the cmappmgr.conf file on VM or vPar Hosts.
3.Install cmappserver depots on VM or vPar guests.
4.Configure the cmappserver.conf file on VM or vPar guests.
5.To start or monitor specific applications in the VM or vPar guests, modify the VM or vPar guest package.
6.Test application monitoring and VM or vPar guest failover operation.
When you install HP Serviceguard A.11.20, or later on the VM or vPar Host cluster nodes, it installs the cmappmgr or cmappserver software and creates the following files and directories:
•/etc/cmappmgr.conf(security configuration file)
•/usr/sbin/cmappmgr (cmappmgr daemon)
•/opt/hp/serviceguard/cmappserver (contains the cmappserver software depots for HPUX, Linux, and Windows guests)
To configure application monitoring:
1.Create and distribute client or server security keys.
The cmappmgr and cmappserver daemons communicate through a secure SSL connection using JSSE and JRE. The system administrator must generate SSL security keys and distribute them to the cluster VM or vPar Hosts and VM or vPar guests. The security keys are used for authentication during the initial cmappmgr or cmappserver connection. A keytool program shipped with JRE is used for key management.
SSL setup overview
A public and private key pair must be generated for
