There are 3 ways that you can use to do this:
- Monitor the TWS Master and Backup Domain Manager with event-driven rules
- ITM integration
- 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.
- It can be configured to monitor more than one instance of TWS installed on one server.
- It collects the audit logs that can be stored in the data warehouse for further analysis or just as an audit trail.
- If the MDM is running on a Windows platforms the Windows Event Log is monitored for Maestro events.
- It also monitors the processes, message queues and file systems filling up.
- The global and local options can be viewed, which can be useful for an operator or first line support.
- You can add TWS devices to the TWS Ping to monitor network access.
- One workspace shows the current ‘planman showinfo’, and the Summarized Job workspace shows the current statuses of all the jobs.
- The agent also includes default situations and take actions.
If you are interested and want to know more follow this link