Author Topic: Monitoring CMOD Windows Service using PowerShell or other Scripting?  (Read 1126 times)

bbeach

  • Newbie
  • *
  • Posts: 1
    • View Profile
I have a client with CMOD on Windows using a remote Clustered SQL Server.  For non-Prod environments, it is not unusual for the SQL server to be restarted without warning. Whenever this happens, the CMOD service stops working and requires a restart.  CMOD is unusual in that if the DB connection breaks the process shuts down, rather than managing it with an error at login time - until the DB is available again.  Has anyone devised a clever way to monitor for this occurrence and automatically restart using OOTB Windows capabilities, without requiring a purchased 3rd party monitoring tool that leverages SNMP alerts or something like that which would be overkill?

Thank you for any feedback.

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Monitoring CMOD Windows Service using PowerShell or other Scripting?
« Reply #1 on: September 10, 2020, 08:30:33 AM »
I've never used it on windows, but maybe the CMOD arslog logging exit could be used to detect a database error, then check on CMOD after a short delay and restart it?

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR