Users need to create a script for the following cases when: starting or stopping ISV applications and user application in line with the userApplication state transition, and switching the userApplication status in line with the stopping of the applications.
Set the created scripts as Cmdline resources, and then set those resources in the userApplication.
This chapter also describes the example of the scripts and notes when creating them.
The following three script types can be set to Cmdline:
Start script
is started when the status of userApplication is transited to Online or Standby.
is a script to start user applications.
Stop script
is started when the status of userApplication is transited to Offline.
is a script to stop user applications.
Check script
is used to monitor the status of resources (user applications) to be started or stopped with a Start or Stop script. It is executed in regular intervals after starting RMS. In addition, it is a script to report the status of user applications.
(*) If the processing time of the Check script (time from the start to the end of the Check script) is within about 0.25 seconds, it is started about every 10 seconds. If the processing time exceeds 0.25 seconds, it is started about every 20 seconds in maximum.
Besides, the Start script and Stop script are called as the Online script and Offline script respectively.
For the attributes that can be set to the Cmdline resources, see "Setting up Cmdline flags" in "6.7.1.1 Creating Cmdline Resources."
Note
When PRIMECLUSTER products are not specified, do not change ReturnCodes of the Cmdline resource.
