StartProgram 

The executable, created locally on each node, which starts the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. 

In some situations, the Online agent function of an Application resource does not start the StartProgram attribute's program as a background process. It instead executes the application in the foreground. If your application start program blocks the application, append an ampersand symbol to the value of the StartProgram attribute. 

For example, if the attribute for StartProgram is
/usr/sbin/vxnotify -g dg00 -m >> /var/log/vxnotify.log
(and vxnotify is blocking command) set it like:
/usr/sbin/vxnotify -g dg00 -m >> /var/log/vxnotify.log &  

Note   Do not use the opening and closing ({ }) brace symbols in this string.

Type and dimension: string-scalar 

Example: /usr/sbin/sample_app start 

Example: "/usr/sbin/sample_app start" 

StopProgram 

The executable, created locally on each node, which stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. 

Note   Do not use the opening and closing ({ }) brace symbols in this string.

Type and dimension: string-scalar 

Example: /usr/sbin/sample_app stop 

Example: "/usr/sbin/sample_app stop" 

At least one of the following attributes: 

• MonitorProcesses
• MonitorProgram
• PidFiles

See Optional attributes for HP-UX. 

CleanProgram 

The executable, created locally on each node, which forcibly stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them.  

Type and dimension: string-scalar 

Example: /usr/sbin/sample_app force stop 

Example: "/usr/sbin/sample_app force stop" 

MonitorProcesses 

A list of processes that you want monitored and cleaned. Each process name is the name of an executable. Qualify the executable name with its complete path if the path starts the executable. 

The process name must be the full command line argument that the ps -u user -o args | more command displays for the process. 

Type and dimension: string-vector 

Example: sample_app_process 

Example: "sample_app_process" 

MonitorProgram 

The executable, created locally on each node, which monitors the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. 

MonitorProgram can return the following VCSAgResState values: offline value is 100; online values range from 101 to 110 (depending on the confidence level); 110 equals confidence level of 100%. Any other value = unknown.  

Note   Do not use the opening and closing ({ }) brace symbols in this string.

Type and dimension: string-scalar 

Example: /usr/sbin/sample_app_monitor all 

Example: "/usr/sbin/sample_app_monitor all" 

PidFiles 

A list of PID (process ID) files that contain the PID of the processes that you want monitored and cleaned. These are application generated files. Each PID file contains one monitored PID. Specify the complete path of each PID file in the list.  

The process ID can change when the process restarts. If the application takes time to update the PID file, the agent's Monitor function may return an incorrect result. If incorrect results occur, increase the ToleranceLimit in the resource definition. 

Type and dimension: string-vector 

Example: /etc/sample/sample_app.pid 

Example: "/etc/sample/sample_app.pid" 

User 

The user ID for running StartProgram, StopProgram, MonitorProgram, and CleanProgram. The processes that are specified in the MonitorProcesses list must run in the context of the specified user. Monitor checks the processes to make sure they run in this context. 

Type and dimension: string-scalar 

Default: root