Customer was running into problems with Policy Server TCP connections, and we needed to request more statistics from the Policy Server process that would be dumped into the logs in order to continue analysis.
A cron job is beneficial to run when the logs do not display enough detail related to performance, etc.
crontab -e Edit your crontab file, or create one if it doesn’t already exist.
crontab -l Display your crontab file.
crontab -r Remove your crontab file.
crontab -v Display the last time you edited your crontab file. (This option is only available on a few systems.)
Create a script such as the example below:
(where /space/home/r12sp3/CA/siteminder/bin/smpolicysrv is the root directory where the smpolicysrv binary file is located, and '-stats' is the command that will allow the statistics to be taken on the Policy Server process that is running and dumped into the smps.log)
Run the cron as the user that runs policy server process - example runs every 3 minutes
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /space/home/r12sp3/scripts/cronrun.sh
The asterisks in the above example stand for minutes, hours, days, months, and "day of week" respectively.