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
The wizard lists all the supported applications for the system.
The Program Selection screen appears.
The Application Component Parameters dialog box appears.
The Application Component Parameters dialog box appears.
The specified component appears on the Program Selection screen.
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.
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.