Sample configuration for custom processes


Sample configuration for custom processes
Prev	Appendix B. Sample configurations	Next

This section describes steps to configure custom processes for high availability by using Symantec ApplicationHA.

Let us assume the following:

The sample custom application component, HttpServer, can be started, stopped, forcibly stopped, and monitored by using appropriate options of the following scripts, respectively: /usr/local/apache2/bin/httpd start, /usr/local/apache2/bin/httpd stop,/usr/local/apache2/bin/httpd stop, and /usr/local/apache2/bin/monitor_httpd. The monitor_httpdscript is written to comply with the MonitorProgram attribute of custom applications.
The sample custom application component, MyComponent1, can be started, stopped, forcibly stopped, and monitored by using the following scripts, respectively: startMyComponent1, stopMyComponent1, forcestopMyComponent1, and monitorMyComponent1. The monitorMyComponent1 script is written to comply with the MonitorProgram attribute of custom applications.

See Agent attributes.

To configure application monitoring for an init process

In the Symantec High Availability view of the Veritas Operations Manager Management Server console, click Configure Application Monitoring. This launches the Symantec ApplicationHA Configuration Wizard.
Review the information on the Welcome screen and then click Next.
The wizard lists all the supported applications for the system.
Select Custom Application, and then click Next.
The Program Selection screen appears.

To specify the httpd application details to monitor, click Add Component.

The Application Component Parameters dialog box appears.

Note:

init processes such as httpd, do not require special monitor scripts. ApplicationHA uses the status option of the init script for monitoring. However you can also use your own program scripts to monitor such processes.

Enter the following values in the respective fields and then click OK:

Program to start the application	`/usr/local/apache2/bin/httpd -f /usr/local/apache2/conf/httpd.conf -k start`
Program to stop the application	`/usr/local/apache2/bin/httpd -f /usr/local/apache2/conf/httpd.conf -k stop`
Program to monitor the application	`/usr/local/apache2/bin/monitor_httpd`

To specify the application components to monitor, click Add Component.
The Application Component Parameters dialog box appears.

Enter the following values in the respective fields:

Program to start the application	`/home/user1/myapplication/bin/startMyComponent1`
Program to stop the application	`/home/user1/myapplication/bin/stopMyComponent1`
Program to monitor the application	`/home/user1/myapplication/bin/monitorMyComponent1`
Program to forcibly stop the application	`/home/user1/myapplication/bin/forcestopMyComponent1`
User name to use when administering the application	username The default user name is 'root'

Click OK.
The specified component appears on the Program Selection screen.
If you want to specify more application components for monitoring, repeat step 4 to step 8.
If you want to define the relationship between httpd and MyApplication components, click Next. The Define Start Stop Order screen appears. The screen lists the previously selected components.
To bring the httpd program online first and then the MyApplication program, in the Parent Component list, click on startMyComponent1_Program.
In the Component list, click to check httpd_Program and then click Configure.
The wizard performs the application monitoring configuration tasks. The ApplicationHA Configuration screen displays the status of each task. After all the tasks are complete, click Next.
Click Finish to complete the wizard. This completes the application monitoring configuration.