Configuring application monitoring by using the Veritas High Availability Configuration wizard

Before you configure an application for monitoring, you must configure a cluster. Refer to the VCS Installation Guide for the steps to configure a cluster.

To configure a generic application for monitoring by using the Veritas High Availability Configuration Wizard:

  1. Launch the Veritas High Availability Configuration Wizard.
  2. Review the information on the Welcome panel and click Next.
  3. On the Application Selection panel, select Generic Application and click Next.
  4. On the Application Inputs panel, enter a name for the component and click Add Component.

    The component you added appears in the Component box.

  5. Specify the following details to configure the component for monitoring:
    • Start program: The complete path of the start program script.

    • Stop program: The complete path of the stop program script.

    • Force-stop program: The complete path of the program script to forcefully stop the application.

    • At least one or more of the following:

      • Monitor program: The complete path of the monitor program script.

      • Application-related processes to monitor: Names of the application processes that must be monitored.

      • Application-generated PID files: Path names of the process ID (PID) files of your application.

    • Enable intelligent monitoring for this application: Select or clear this option to enable or disable intelligent monitoring for the application component. This option is selected by default. Veritas recommends that you enable intelligent monitoring of the application component.

      For more information about intelligent monitoring, refer to the Application agent section in the VCS Bundled Agents Reference Guide.

    • User: The user name. This user name is used to run all the agent scripts. Ensure that you specify a valid user with adequate privileges on the physical machine, virtual machine, logical domain, or LPAR where you configure the application. Else, application monitoring may fail.

    To remove a component from the Component box, use the Remove icon.

  6. To specify more application components for monitoring, repeat steps 4 and 5. Else, click Next.
  7. On the Storage Selection panel, select the appropriate mount points for the application instances that require storage, and click Next.


    The Storage Selection panel does not appear if shared storage is not mounted on the physical machine, virtual machine, logical domain, or LPAR.

  8. The Define Start-Stop Order panel appears only when you have added more than one component for monitoring.

    On the Define Start-Stop Order panel, to define the dependency between the components, select an application component from the Parent Component box and then select the components that it depends on from the Depends on box. When starting the application, the components are brought online in the defined order.

    Click Next.

  9. If you have launched the wizard through VOM, go to step 12.

    On the Configuration Inputs panel, use the Edit icon to specify the user name and password of the systems for the VCS cluster operations.

  10. On the Configuration Inputs panel, move the required systems to the Application failover targets list. Use the up and down arrow keys to define the priority order of the failover systems.
    • Cluster systems lists the systems included in the cluster configuration.

    • Application failover targets lists the systems to which the application can fail over.

  11. Skip this step if you do not want to add more systems to your cluster.

    To add a system to the cluster, on the Configuration Inputs panel, click Add System. In the Add System dialog box, specify the following details of the system that you want to add to the VCS cluster and click OK:

    System Name or IP address

    Specify the name or IP address of the system that you want to add to the VCS cluster.

    User name

    Specify the user account for the system.

    Typically, this is the root user.


    Specify the password for the user account mentioned.

    Use the specified user account on all systems

    Select to use the specified user account on all those cluster systems that have the same user name and password.

    The wizard validates the details, and the system then appears in the Cluster Systems list.

    To remove a system from the cluster or from the Application failover targets list, use the Remove icon.

  12. Skip this step if you do not want to specify a virtual IP address for the application component.

    On the Virtual Network Details panel, select the IP network (IPV4 or IPv6). The IPv4 protocol is selected by default.

    Select the appropriate component and specify the following details for each failover system:

    Virtual IP address

    Specify a unique virtual IP address.

    You can specify only one virtual IP address for each component.

    Subnet Mask (for IPv4)

    Specify the subnet mask details.

    Prefix (for IPv6)

    Select the prefix details.

    Network Adapter

    Select the network adapter that will host the virtual IP.

    If you want to add another virtual IP address, click Add virtual IP address.

    Click Next.

  13. This step is only applicable if you are configuring application monitoring on a virtual machine (VMware environment).

    If you selected mount points for your application in step 7, the Storage HA Inputs panel appears.

    On the Storage HA Inputs panel, specify all the ESX/ESXi hosts to which virtual machines can fail over. Each ESX/ESXi host must be able to access the required shared datastores that contain visible disks.

    To specify the ESX/ESXi hosts, click Add ESX/ESXi Host and in the Add ESX/ESXi Host dialog box, specify the following details and click OK:

    ESX/ESXi hostname or IP address

    Specify the target ESX/ESXi hostname or IP address.

    The virtual machines can fail over to this ESX/ESXi host during vMotion. All the additional ESX/ESXi hosts should have access to the datastore on which the disks used by the application reside.

    User name

    Specify a user account for the ESX/ESXi host. The user account must have administrator privileges on the specified ESX/ESXi host.


    Specify the password for the user account provided in the User name text box.

    The wizard validates the user account and the storage details on the specified ESX/ESXi hosts.

    If you want to remove an ESX/ESXi host, use the Remove icon.

    Click Next.

  14. On the Summary panel, review the configuration details information and click Next to proceed with the configuration.

    If you want to rename the service group, click the Rename link and edit the service group name in the Rename service group name dialog box.

  15. On the Implementation panel, the wizard performs the following tasks and displays the status of each task:
    • Configures the application for monitoring

    • In a VMware environment, creates cluster communication links

    After all the tasks are complete, click Next.

    If a configuration task fails, click Diagnostic information to check the details of the failure. Rectify the cause of the failure and run the wizard again to configure application monitoring.

  16. Click Next and then click Finish to complete the wizard workflow.

    This completes the application monitoring configuration.


    If the application is not running and if you want to start the application, click Start to start the configured components on the system.