This template helps find out the up/down status of applications running in Interix subsystem. A batch file uses PsExec to run the appdump command on the Interix machine and redirect the output to a text file. This text file is then parsed by the script present within the components to verify the up/down status of applications.
- Download PsExec utility from Microsoft’s website,
- Copy the extracted PsExec utility to the SAM server, preferably to a directory in PATH.
- Save the appdump batch file to the SAM server, say C:\temp , and rename the “.bat.txt” extension to “.bat”.
- Edit the batch file and change the path to PsExec accordingly. Also put in the IP address of the machine running Interix, the username and password used to log into the Interix machine.
- Replace “C:\path\to\exe” with the actual path where the “appdump.exe” is present on the Interix machine.
- Save the batch file after making these changes.
- In Task Scheduler, using Advanced Settings, schedule to run the batch file every 5 minutes or every 10 minutes as needed.
- Import the attached template into SAM.
- You would have to edit the components to change the batch file output path if it is different from “C:\temp”.
File Age Monitor: Returns the number of minutes elapsed since the file modification date. If this is more than 10 (as specified in Task Scheduler) this would imply that the batch file has not run successfully and thus the output of the appdump command is not recent.
The other individual components monitor the up/down status of the applications by detecting the presence of the application names in the appdump command output. The script is written in Perl. To monitor more applications, you would have to clone the component in Component Library and modify the application name present within quotes in the following line of the script,
my $app = 'CAS';