Orb Data

Orb Data's Blog Site

How do you monitor the Tivoli Workload Scheduler (TWS) server?

There are 3 ways that you can use to do this:

  1. Monitor the TWS Master and Backup Domain Manager with event-driven rules
  2. ITM integration
  3. Or lastly using the Orb Data TWS 8.X agent.

This blog briefly discusses each option.

Monitoring with event-driven workload automation rules. EDWA.

Some basic monitoring of the TWS server can be performed with event rules to monitor the message queues filling up, TWS file systems filling up and TWS processes not running. You can then set up an event rule with an action that starts up the process if it is down. The alert can be sent to Netcool via EIF.

Monitoring with the ITM integration

The ITM integration consists of the universal agent and a number of scripts. In my opinion this does not look that well in the TEP. For example each process monitored is displayed in its own workspace and I have found this painful to configure.

Monitoring with the Orb Data TWS 8.X agent

The last option is to use an ITM agent that I have developed that in my view offers a more complete solution.  This TWS 8.X agent monitors and collects data from the TWS MDM and BDM.


If you are interested and want to know more follow this link


, , , , ,

2 thoughts on “How do you monitor the Tivoli Workload Scheduler (TWS) server?
  • vamsi krishna B says:

    Hi Team,

    In our current environment we have to monitor TWS out of memory(OOM) by using ITM 6.2.3 version.Could you please suggest us the better way to monitor TWS oom

  • Simon Barnes says:

    You can’t use TWS built-in monitoring to monitor for WAS oom errors as TWS uses WAS to do the monitoring. So if you used WAS to monitor the WAS logfile and an oom condition occurred, you *MAY* not receive the alert if the oom caused WAS to fail or hang. Using a third-party monitoring tool for this is much more reliable and as you have ITM why not use that?

Leave a Reply

Your email address will not be published. Required fields are marked *