You can edit EPMA_CreateAndStartAppResource.bat to specify values for these variables, which are listed at the top of the script:
ACTION_SCRIPT–Full path and file name for the EPMA_ActionScript.bat file provided with your Performance Management Architect installation
This batch file is the action script that Oracle Clusterware uses to manage the application resource (for example, Performance Management Architect Server).
FAILOVER_DELAY–Number of seconds to wait before starting the failover process after a failure is detected
FAILURE_THRESHOLD–Number of failures detected within a specified failure interval for a resource before Oracle Clusterware marks the resource as unavailable and stops monitoring it
If a resource fails the specified number of times, then Oracle Clusterware stops the resource. If the value is 0, then failure tracking is disabled. The maximum value is 20.
FAILURE_INTERVAL–Interval, in seconds, during which Oracle Clusterware applies the FAILURE_THRESHOLD attribute
If the value is 0, failure tracking is disabled.
START_TIMEOUT–Number of seconds that Oracle Clusterware waits for the application resource to start before declaring a failed start
STOP_TIMEOUT–Number of seconds that Oracle Clusterware waits for the application resource to stop before declaring a failed stop
CHECK_INTERVAL–Number of seconds between repeated checks
Shortening intervals for more-frequent checks increases resource consumption if you use the script agent. To reduce resource consumption, use an application-specific agent.
RESTART_ATTEMPTS–Number of times Oracle Clusterware attempts to restart a resource on the resource's current server before attempting to relocate it
For example, if the value is 1, Oracle Clusterware attempts to relocate the resource after a second failure. A value of 0 indicates that there is no attempt to restart, but Oracle Clusterware always attempts to fail the resource over to another server.
CRS_HOME–Full path to the BIN folder for your Oracle Clusterware installation