Welcome to the Application Performance Management Blog, where you can read the perspectives from APM experts. This Blog provides insights into the Application Performance Management solution, as well as technical details about specific IBM products.
This video is your one stop shop for learning how to set tracing on the Tivoli Enterprise Monitoring Server (TEMS).
This video will show you how to:-
- Set traces on the TEMS component
- How to increase the size and number of log files
- How to check that the trace which has been set is being used by the TEMS
Direct link to YouTube: http://ow.ly/G7i72
ITM 6.3 Fix Pack 4 has arrived! All the info you need to download now and get the benefits of the new fix pack! Happy downloading!!!
LIVE and direct Download links, APAR and packages all listed below!
All of the links in the below tables are live. They will take you directly to the download location of the package you require, or the IBM official technote for one of the APARs included in this fix pack (if you wish to know more about the APAR)
Here is a quick video tutorial on how to create a custom query to retrieve and display TEMS data, directly in a TEPS workspace (using your own custom SQL)!
Not everyone is a big fan of using command line and then having to plough through a text file, to look at a list of records from a database. This method allows quick and easy access to TEMS data, which is then displayed directly in your TEPS workspace.
Many users of ITM are broken... [More]
This "Nuggets of Knowledge" is a series of blogs that are all aimed at hints and tips to maximise the use and value you can get from the IBM Tivoli Monitoring (ITM) product suite. Below is a full list of my blogs for easy navigation and future reference.
All new blogs will also be added to this post, so feel free to bookmark it so you don't miss any new additions.
Please feel free to contact me, all my links are at the bottom of the page
I welcome sugestions... [More]
On the forth installment of the SPUFI series, we look at our third "use case". This blog will show you how to extract key information via the command line from your TEMS relating to which agents are assigned to which MSL (Managed system list). This is a very powerful way to obtain great information from your TEMS
If you missed part one on how to use the tool here is a quick link: -----> ... [More]
On the third installment of the SPUFI series, we look at our second "use case". This blog will show you how to extract key information via the
command line from your TEMS relating to which situations are started, stopped, deleted or in error in you ITM infrastructure. This is a very
powerful way to obtain great information from your TEMS outside the GUI.
If you missed part one on how to use the tool here is a quick link: --->... [More]
On the second installment of the SPUFI series, we look at our first "use case". This blog will show you how to extract key information via the command line from your TEMS relating to events/situations that have fired in your ITM infrastructure. This can be used to health check, sanity check and recheck all key areas of event management. This is a very powerful way to obtain great information from your TEMS
If you missed part one on how to use the tool here is a quick... [More]
The Warehouse Proxy agent provides a set of works spaces that are defined as “Manage Our Stuff With Our Stuff”(MOSWOS). IBM/Tivoli love acronyms and MOSWOS has been around a long time internally. But, it is a term that usually causes confusion for a user of ITM. This confusion extents further for the Warehouse Proxy agent in the sense that most users do not know that these MOSWOS workspaces exist. The Warehouse MOSWOS workspaces can be used to look for problems occurring in historical data collection. ... [More]
In my previous blog entry , I detailed how to configure historical collection so that the least amount of data is saved and the export of that data is the quickest. All for keeping the size of the short term history file below 1GB. However, when saving historical data at the TEMA the agent can become isolated from the Warehouse Proxy agent because of network issues. Or the database itself may be down not allowing exports. When this happens, the STH files start growing and can exceed the 1GB limit over time. At the TEMS, this can also... [More]
In my previous blog entry
we discovered that each short term history(STH) file must be kept
under 1GB in size for performance reasons at the TEMA (Tivoli
Enterprise Monitoring Agent) or TEMS (Tivoli Enterprise Monitoring
Server). As with any smartphone data plan it is always good to have
ways to try and not exceed this limit. And for STH files the same
applies. Here are ways to achieve this: Use
the largest collection interval possible. This reduces the number
of rows saved in the STH file. Filter
any unneeded data from the... [More]
You have just bought your
first smart phone. You then have to decide on how to use 'less data'
using your data plan(unless you are on an unlimited plan). You
google 'how to use less data' and see there are thousands of posts on
how to do this. In terms of Tivoli ITM warehousing, the same concept
applies, how to keep the short term history(STH) files at a
reasonable size. This requires for large data intensive agents to
think about the configuration of the historical collection interval,
warehousing upload interval, and retention... [More]
Robert Frost said in “The Road Not Taken” : “Two roads diverged in a wood, and I,I took the one less traveled by, And that has made all the difference” For historical collection of data within the Tivoli Framework, the user has to decide for each table collected if it should be saved at the TEMA (Tivoli Enterprise Monitoring Agent) or TEMS (Tivoli Enterprise Monitoring Server). The default location is the TEMA, but we have found that users like to move this to the TEMS so that all of their data is located on one machine.... [More]
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]