Oracle Clusterware calls an action script to stop or start an application resource (for example, Performance Management Architect Dimension Server) or to check the status of the application. You can run the action script from Oracle Clusterware or from the command line. The action script logs the date, time, action being performed (start, stop, clean, or check), and action result (success or failure).
You create the action script by editing EPMA_ActionScript.bat, in EPM_ORACLE_HOME/products/Foundation/BPMA/AppServer/DimensionServer/ServerEngine/Failover, to conform to your environment.
You can edit EPMA_ActionScript.bat to specify these variables, which are listed at the top of the script:
LOG_PATH–Full path to a local folder where the application resource action script logs information
Example: set LOG_PATH=C:/CRS_ACTION/EPMA
Assuming that you provide a path with a valid drive letter, the action script creates the path at runtime if the path does not exist.
LOGSCR–A concatenation of the LOG_PATH value and a valid file name for the environment
Example: set LOGSCR=%LOG_PATH%/ClusterActionEPMA.log
SECONDS_TO_WAIT_FOR_START–Number of seconds that the action script waits for the application resource to start before declaring a failed start and returning a 0 to the calling process (Oracle Clusterware)
Example: set SECONDS_TO_WAIT_FOR_START=180
SECONDS_TO_WAIT_FOR_STOP–Number of seconds that the action script waits for the application resource to stop before declaring a failed stop and returning a 0 to the calling process (Oracle Clusterware)
Example: set SECONDS_TO_WAIT_FOR_STOP=60
Note: | If your Performance Management Architect release is 11.1.2.1, the two sections labeled EPMA pre-11.1.2.1 section should be commented out. If your Performance Management Architect release is 11.1.2.0 or earlier, the section labeled EPMA 11.1.2.1 section should be commented out. |