Automated Smart Windows Server Bounce Script for PeopleSoft
Technologies used.
1) Cygwin
2) PHP
3) Bash Scripting
4) Sendmail As because, PHP can not use mailx to send emails.
5) NSSM Windows Service Manager.
Problem Statement
Why do we need a windows server bounce running peoplesoft NT Process scheduler domains?
Windows OS is part of PeopleSoft architecture and can not be ignored. But, there are some difficult times where windows server become a bit uncomfortable after running for a 3 months to 6 months.
Windows Servers running Peoplesoft NT Process scheduler domains
need to be bounced/recycled periodically to avoid any unforeseen
performance issues with the peoplesoft jobs and also to avoid high CPU and Memory usage issues.
The Script follows the below criteria before bouncing the windows servers automatically.
1) The windows server should be bounced, only when there are no peoplesoft jobs running on NT Process Scheduler domain.
2) If there are any peoplesoft jobs running on the NT Process Scheduler domain, then the bounce activity need to wait for a predefined time, till all the jobs are completed and then initiate the windows server bounce.
3) If the wait is too long for the running jobs to complete, then abort the windows server bounce activity and report the event to peoplesoft administrator.
3) Once after the windows server is bounced, the NT process scheduler domain service need to be started automatically. so that, it can start processing peoplesoft jobs again.
4) Finally, Send detailed server bounce activity report to peoplesoft administrator along with the time stamp from start to finish.
Production Windows Server running PeopleSoft NT Process Scheduler Domains.
a)abc.200.xx.15 Bounce this windows box @9:00 PM MST on every 2nd Saturday of the month (PSNT)
b)abc.200.yy.16 Bounce this windows box @9:00 PM MST on every 3rd Saturday of the month (PSNT2) (FSPRDPGP)
c)abc.200.zz.17 Bounce this windows box @9:00 PM MST on every 4th Saturday of the month (PSNT3)
No comments:
Post a Comment