It all starts with what you name your situations. If you do not have unique names you could potentially cause greater problems for yourself and your environment. Problem description: When creating the name of a situation the ITM6.3 FP02 manual says: ‘The situation name can contain any UTF-8 characters and can be up to 256 bytes long. The number of characters allowed varies depending on the characters used, because some UTF-8 characters require more than one byte.’ (Page 259) Please note when creating... [More]

Tags:  duplicate monitoring aishasaini 6.23 saini ibm tep 6.3 mangaged create situations itm editor user name csimonitoringacademy 6.22 6.1 aisha missing tivoli situation

If you have ever needed to move an agent from one Hub TEMS environment to another, you'll know that reconfiguring the agent to connect to a different TEMS is the easy part. Before that agent will begin to monitor the resources it was previously monitoring, all the Situations, Groups, Overrides, Calendars, EIF slot customisations, Managed System Lists, (MSLs), Long Names and distributions must be replicated on the new Hub. If the agent has subnodes, the monitoring objects associated with its subnodes must be moved, too. This is a complex and... [More]

Tags:  export migrate tivoli agents how2 import itm situations monitoring groups msl how migrating

IBM Tivoli Composite Application Manager for Transactions ~ How to do stuff ~ By Kevin Baldwin - How to..... Correctly interpret playback status and availability information seen in Robotic Response Time workspaces The information in this blog answers the following questions: Why is Last Run Status showing Complete when the monitored web server isn't available? Why is the application showing 100% availability when the monitored web server isn't available? The quick answer to these questions is: Playback Status just reports the status of... [More]

Tags:  availability vp workspace verification transactions failure how2 kt6 apm itcamft playback robotic smartcloud itcam t6 status rrt situations

The following link provides a best practices document that groups a set of suggestions useful to reduce the impacts in terms of performances on the IBM Tivoli Monitoring infrastructure caused by the monitoring situations.   Link to the document: Situations Best Practices    

Tags:  performances best situations practicesm

A poorly written situation can have large impact on CPU usage of IBM Tivoli Monitoring 6.2.x OS Agents main processes (kuxagent, klzagent and kntcma.exe). Using wildcard characters (*) and MISSING function in situations is one of the most common source of high impact on CPU usage related to situations evaluation.   There are two main suggestions to follow while rewriting situations in order to reduce ITM OS Agents CPU usage: situation with this simple pattern 'LIKE "*/process"' can be re-written as 'SCAN "/process"' put the... [More]

Tags:  cpu agent os usage situations situation agents performance

The IBM Tivoli Monitoring Validation Tool for Autonomous Agent Situations is a new tool that will allow you to validate the situations for autonomous mode agents.    Here is the link on ISM library:    https://www-304.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10TM9Y 

Tags:  autonomous itm situations

Think a situation should be firing and it isn't?  You can always do a quick and dirty check to see what is happening at the HUB by using the kdstsns tool to query the TEMS database.  This is an internal tool and it is an easy way to "dump" information from the TEMS tables. It is located under the following directories: Windows - $CANDLEHOME\cms UNIX -  $CANDLEHOME/Mplatform>/ms/bin You must set SQLLIB to the location where the SQL you want to run resides.         example:  WINDOWS:  set SQLLIB=c:\IBM\ITM\cms\sqllib UNIX:     export... [More]

Tags:  situations itm monitoring tems