This section describes a sample procedure for using the Veritas High Availability Configuration wizard.
To configure monitoring for the following across two virtual machines - Machine1 and Machine2:
As part of the configuration process, the wizard configures a 2-node cluster between the machines Machine1 and Machine2 running on hosts - Host1 and Host2, respectively.
Let us assume that the generic application (MyApplication) can be started, stopped, monitored, and forcibly stopped by using the following scripts, respectively:
start_MyComponent
stop_MyComponent
monitor_MyComponent
The monitor_MyComponent
script is written to comply with the MonitorProgram attribute of generic applications. For more information, see the description of the Application agent attributes in the Cluster Server Bundled Agents Reference Guide.
forcestop_MyComponent
To configure application monitoring using the Veritas High Availability Configuration wizard
The component you added (cups_Program) appears in the Component box.
The component you added (MyComponent) appears in the Component box.
Start program |
|
Stop program |
|
Force-stop program |
|
Monitor program |
|
Application-related processes to monitor |
Not specified |
Application-generated PID files |
Not specified |
Enable intelligent monitoring for this application |
Selected by default to enable intelligent monitoring |
User |
username. This user name is used to run all the agent scripts. For example, root. |
To bring the CUPS process online first and then MyApplication, in the Parent Component list, select MyComponent and in the Depends on box, select cups_Program.
This completes the application monitoring configuration.
If the application status shows as not running, click Start to start the configured components on the system.