ITM61_UA_Overview

1 IBM Tivoli Monitoring 6.1 Universal Agent Tivoli Universal Agent overview IBM Tivoli Monitoring 6.1 Universal AgentIBM Tivoli Monitoring 6.1 Universal AgentIBM Tivoli Monitoring 6.1 Universal AgentIBM Tivoli Monitoring 6.1 Universal Agent Tivoli Universal Agent OverviewTivoli Universal Agent OverviewTivoli Universal Agent OverviewTivoli Universal Agent Overview 2 22 Tivoli Universal Agent overview • Architectural overview • Universal Agent and ITM 6.1 • Universal Agent versus Standard Agents 33 Overview of the agent UA relies on a set of Data Providers to collect data from a variety of data sources. Attributes data are described in definition files known as Metafiles.� provide the data model of the “application” being monitored The overview of the agent, and I’m going to kind of cover this quickly. I’m assuming folks have an existing knowledge of the TIMS and TEPS. I’ll cover that just briefly, but this not being…. The agent is there, he runs an ES data providers. These are the programs that collect data from the sources. They collect it from databases or SNMP as we saw earlier from the files, from scripts, APIs, HTTP and socket. These are what you’ll end up writing applications for in order to collect that data. 3 4 44 Tivoli Universal Agent Overview Universal Agent and ITM 6.1 • Product code is “UM”. • When integrating data through the Universal Agent, all ITM functions are available: Data Visualization and Reporting: � Views and workspaces � Historical data collection � Customizable queries (attribute based) � Thresholds and data filtering � Reporting through Web services Monitoring and event management: � Event Situations � Reflex automation � Policy automation The overview of the product code, which you may or may not care about, but if you ever get into looking at the logs, is UM. The full product code is KUM. When you’re integrating through the universal agent, all the ITM functions are available. You have workspaces and views, historical data collection. You can customize queries, you can do thresholds and data filtering and you can do reporting through web services. You can also do monitoring of events through situations and you can write reflex automation and policy automation. These are all available to the agent. 5 55 Universal agent vs. standard agents • Standard Agents: � Monitors a specific application or operating system � Use a static set of attributes � Cannot be enhanced/extended by field personnel to “see“ more data • The Universal Agent: � Full-featured IRA (intelligent remote agent) with dynamic application capabilities. � Dynamically creates custom attributes and catalogs. � Adds to monitoring solutions to make them complete. � Supports eight different types of data providers (collectors). Value Added: Flexibility! Tivoli Universal Agent overview UA is a full-featured IRA with dynamic application capabilities. Monitoring requirements are determined at run-time rather than compile-time. Generates application ATR, CAT, and ODI files based on customer-defined metafile. •Files are dynamically uploaded to the TEMS and TEPS without requiring a recycle. Unlike traditional IRAs with static pre-defined attributes, UA lets you change the attributes you’re collecting. Stores all application data in subnodes. Now, you say ‘well, why do I need the other agents versus the universal agents, or what’s the difference?’ Standard agents monitor a specific application or operating system. It uses a static set of attributes. What I mean by that is, the developer who wrote that application or that agent decides what attributes are going to be collected and how they are going to be defined and you can’t enhance that with filed. You can’t edit the files that come with the UNIX agent, for example, save it and expect to see any change in the UNIX agent. However the universal agent has got dynamic capabilities. Now, obviously with dynamic comes good things and bad things. If you make a change that you didn’t like but the agent accepted, then you’re going to see the change up in the TEPS so you really need to test what you’re working with as you create these. It dynamically creates the attributes and catalog files. Like I said on the last slide, it loads those up to the TIMS and to the TEPS. It does not load it to the hub TIMS, that’s something you have to do manually or connect the agent to the hub TIMS and it will actually do it at that point. So it loads it up to the TIMS that it’s connected to. It adds monitoring solutions to make them complete. You could use the Oracle agent for example and lets say that there are some tables for example, that you want to monitor but the Oracle agent doesn’t provide capability. As long as you have Windows ODBC, you could then use the universal agent to enhance your solution and add to it. It does support eight different types of data providers or data collectors. And the value is flexibility. 66 Copyright and trademark information © Copyright IBM Corporation 2000 - 2007. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM web site pages may contain other proprietary notices and copyright information which should be observed. IBM trademarks http://www.ibm.com/legal/copytrade.shtml#ibm Fair use guidelines for use and reference of IBM trademarks http://www.ibm.com/legal/copytrade.shtml#fairuse General rules for proper reference to IBM product names http://www.ibm.com/legal/copytrade.shtml#general Special attributions http://www.ibm.com/legal/copytrade.shtml#section-special