The IBM Cognos TM1 Operations Console is an interface on top of TM1 Top. The main advantage is that you can manage different servers from a more user-friendly single console in your web browser.
If you don’t have the TM1 Operations Console installed yet, check this post: IBM Cognos TM1 Operations Console Installation.
TM1 Operations Console Setup
If you have the TM1 Operations Console installed, you can browse to the console via your web browser via “http://server:port/tm1operationsconsole” where “server” is you server name and “port” the server port, usually 9510 by default.
Before you can start using the TM1 Operations Console you need to set up an “Operations Group”. Within each “Operations Group” you can then add multiple TM1 servers and TM1 application servers. An “Operations Group” should be a logical grouping of servers, e.g. a sales group and a finance group or a development group and a production group.
The process of adding an “Operations Group” and servers is straightforward. Create an “Operations Group” and then add the servers and applications servers via right-click in the tree (Click the image for a larger view).
TM1 Operations Console Configuration
Once the servers are added you will see the default information pane with the Server Health Status, Monitors and Logging. For each server you have an additional pane, that can be shown next to each other.
Now you can do some configuration to manage the operation as you want it. The most important are the configuration parameters for a server. The following can be set:
- Log Period (sec): The time interval in seconds between updates being written to the log file.
- Log Append: If set to True new logs will be appended to the log file. If set to False the existing log file will be overwritten.
- Top Refresh Period (sec): The time interval in seconds before the data is refreshed.
- Top Tolerance Factor (sec): If set to 0, data is new, if set to 1 or more, this depicts the number of seconds data can be held before a new polling.
- Top Time Out (sec): Number of seconds the console will attempt to connect to the server before a time out.
- Memory Stats Refresh Period (min): The period in minutes the console waits before refreshing the data.
- Memory Stats Tolerance Factor (min): If set to 0, data is new, if set to 1 or more, this depicts the number of seconds data can be held before a new polling.
- Memory Stats Time Out (min): Number of minutes the console will attempt to connect to the server before a time out.
Next to the configuration parameters you can also set some filters to narrow down the logging and you can schedule the logs.
If you want to use the performance monitoring features you have to enable this first in TM1 Architect, “Start Performance Monitor”:
TM1 Operations Console Monitoring
Once you have done your setup you can basically do and monitor everything you know from TM1 Top and a bit more (I think), in short:
- Server: Number of threads, wait threads and status.
- Memory usage with a split for views, calculations, feeders and data
- Thread information
- Sandboxes, active and queued
- Web applications (needs config in the web/application server)
You can also export the log files. Again this looks familiar.
- In the TM1s.cfg file you can set the “MaskUserNameInServerTools” parameter. If this parameter is set to FALSE, user names are displayed in the TM1 Operations Console by default. If this parameter is set to TRUE, user names are masked out for non administrator users. Users with administrator privileges can always see the user names if they want.
- This was tested using the Chrome web browser. The operation is not super smooth and some improvements can be made to make life easier. This is not a deal breaker as managing multiple TM1 Top screens at the same time is hardly user-friendly either.
- You can kill processes and sandbox queues. You can basically kill what you can/could kill with TM1 Top.
- You can download and import the configuration settings via the import and download option. The data are stored in the tm1operationsconsole.xml file.
- Just as with TM1 Top, performing intensive logging will have a performance impact.
- You can choose between basic and enhanced monitoring. This can be configured in the OpsConfig.xml file.
All in all, if you haven’t already done so, installing and playing around a bit with the TM1 Operations Console is worth doing. It is an interface on top of TM1 Top to make things easier and more manageable and you can monitor things from within a single console. Now I need some sort of problem so I can actually use it for real …