Ibm tivoli monitoring version 5.1.1 creating resource models and providers sg246900

889 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
889
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ibm tivoli monitoring version 5.1.1 creating resource models and providers sg246900

  1. 1. Front coverIBM Tivoli MonitoringVersion 5.1.1Creating Resource Models and ProvidersPractical step-by-step developmentexamplesCreating cross-platform Javaresource modelsProvider engineering andimplementation Tony Bhe Kiyonobu Inayama Craig Lister Massimiliano Parlione Michael Vesichibm.com/redbooks
  2. 2. International Technical Support OrganizationIBM Tivoli Monitoring Version 5.1.1Creating Resource Models and ProvidersAugust 2003 SG24-6900-00
  3. 3. Note: Before using this information and the product it supports, read the information in “Notices” on page xvii.First Edition (August 2003)This edition applies to Version 5, Release 1, Modification 1 of IBM Tivoli Monitoring.© Copyright International Business Machines Corporation 2003. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.
  4. 4. Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix The team that wrote this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Comments welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiPart 1. ITM fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. IBM Tivoli Monitoring architecture . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 High level architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Engine features and abilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Endpoint integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4.1 ITM data flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4.2 Directory structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.5 ITM Engine architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1.5.1 Engine input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.5.2 Engine output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.5.3 Engine components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Chapter 2. Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2.2 Using Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 2.2.1 The Workbench panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 2.2.2 Elements in Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.2.3 Looking at the PhysicalDiskModel . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.3 Creating Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 2.3.1 Creating Resource Models using the wizard. . . . . . . . . . . . . . . . . . . 46 2.3.2 Cloning existing Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . 60 2.3.3 Registering a Resource Model into ITM . . . . . . . . . . . . . . . . . . . . . . 61 2.4 Tools and extra information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 2.4.1 WorkBench command line interface . . . . . . . . . . . . . . . . . . . . . . . . . 62 2.4.2 Microsoft tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63© Copyright IBM Corp. 2003. All rights reserved. iii
  5. 5. 2.4.3 Saxsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 2.4.4 Rhino . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Chapter 3. Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 3.1 Resource Model overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 3.1.1 Logical components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 3.1.2 Physical components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 3.1.3 Types of Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.2 Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 3.2.1 Resource Models for each platform . . . . . . . . . . . . . . . . . . . . . . . . . 77 3.2.2 Windows Resource Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 3.2.3 UNIX Resource Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Chapter 4. Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 4.2 Industry technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 4.2.1 Web-Based Enterprise Management (WBEM) . . . . . . . . . . . . . . . . 113 4.2.2 The Common Information Model (CIM). . . . . . . . . . . . . . . . . . . . . . 113 4.2.3 Managed Object Format (MOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 4.2.4 CIM Provider layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 4.2.5 Windows Management Interface (WMI) . . . . . . . . . . . . . . . . . . . . . 115 4.2.6 Java Management Extensions (JMX) . . . . . . . . . . . . . . . . . . . . . . . 117 4.3 Tivoli implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 4.3.1 ITM Engine components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 4.3.2 Legacy support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 4.3.3 Touchpoint Service Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 4.3.4 CIM object definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 4.3.5 Tivoli ILT Provider Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 4.3.6 Tivoli Management Extensions for Java (TMX4J). . . . . . . . . . . . . . 133Part 2. Practical examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Chapter 5. Engineering a Java ILT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 5.1 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 5.2 Planning and design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 5.2.1 Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 5.2.2 CIM class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 5.2.3 ILT class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 5.2.4 Provider class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 5.2.5 Component reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 5.3 Implementing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 5.3.1 Managed Object Format (MOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 5.3.2 ILT Java class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 5.3.3 Provider Java class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156iv IBM Tivoli Monitoring: Creating Resource Models and Providers
  6. 6. 5.3.4 Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615.4 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 5.4.1 Testing and importing the MOF. . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 5.4.2 Java compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 5.4.3 Making the jar file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 5.4.4 Assembling the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . 173 5.4.5 Building the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745.5 ITSO_Sample template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 5.5.1 ITSO_Sample.mof. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 5.5.2 ITSO_SampleIlt.java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 5.5.3 ITSO_Sample.java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 5.5.4 Resource Model JavaScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Chapter 6. Creating an SNMP Resource Model for Windows . . . . . . . . . 2016.1 Designing the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 6.1.1 Design overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 6.1.2 What part of ITM will we use? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 6.1.3 Detailed design Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . 2046.2 Creating the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 6.2.1 Installing SNMP and WMI SNMP on the managed machine . . . . . 205 6.2.2 Creating the new SNMP Resource Model . . . . . . . . . . . . . . . . . . . 211 6.2.3 Packaging the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 6.2.4 Testing the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2236.3 ITSO_SNMP_Interface_Bps source code . . . . . . . . . . . . . . . . . . . . . . . . 225 6.3.1 ITSO_SNMP_Interface_Bps.vba . . . . . . . . . . . . . . . . . . . . . . . . . . 225Chapter 7. Creating an SNMP Resource Model for Java . . . . . . . . . . . . . 2317.1 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2327.2 Planning and design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 7.2.1 Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 7.2.2 CIM class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 7.2.3 ILT class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 7.2.4 Provider class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 7.2.5 Component reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2357.3 Implementing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 7.3.1 Managed object format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 7.3.2 ILT Java class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 7.3.3 Provider Java class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 7.3.4 Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2637.4 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 7.4.1 Testing and importing the MOF. . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 7.4.2 Java compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 7.4.3 Making the jar file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Contents v
  7. 7. 7.4.4 Assembling the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . 274 7.4.5 Building the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 7.5 ITSO_SnmpProbe source code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 7.5.1 ITSO_SnmpProbe.mof . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 7.5.2 ITSO_SnmpProbeILT.Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 7.5.3 ITSO_SnmpProbe.Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 7.5.4 SnmpInterface.Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 7.5.5 Resource Model JavaScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Chapter 8. Creating a log-file Resource Model. . . . . . . . . . . . . . . . . . . . . 305 8.1 Engine component utilization: Overview . . . . . . . . . . . . . . . . . . . . . . . . . 306 8.2 Creating the MOF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 8.3 Compiling the MOF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 8.4 Creating the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 8.5 Constructing the Resource Model: Events . . . . . . . . . . . . . . . . . . . . . . . 325 8.6 Constructing the Resource Model: Dependencies . . . . . . . . . . . . . . . . . 327 8.7 Constructing the Resource Model: Inserting code . . . . . . . . . . . . . . . . . 328 8.8 The flow of the code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Chapter 9. Creating a log-file Resource Model and ILT . . . . . . . . . . . . . . 333 9.1 Designing the ITSO_LogfileLite Resource Model and ILT . . . . . . . . . . . 334 9.1.1 Design overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 9.1.2 What part of ITM will we use? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 9.1.3 The detailed design of the ITSO_LogfileLite Resource Model . . . . 338 9.2 Creating the ITSO_LogfileLite Resource Model and ILT. . . . . . . . . . . . . 341 9.2.1 Setting up the development environment . . . . . . . . . . . . . . . . . . . . 341 9.2.2 Creating the MOF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 9.2.3 Creating the ITSO_LogfileLite ILT code . . . . . . . . . . . . . . . . . . . . . 345 9.2.4 Creating the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 9.2.5 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 9.2.6 Testing the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 9.3 ITSO_LogfileLite source code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 9.3.1 ITSO_LogfileLite.mof . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 9.3.2 ITSO_LogfileLite-wmi.mof . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 9.3.3 ITSO_LogfileLiteILT.java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 9.3.4 ITSO_LogfileLite.java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 9.3.5 ITSO_LogfileLite_RM.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Chapter 10. Creating a custom script Resource Model . . . . . . . . . . . . . . 411 10.1 Designing the ITSO_ProcessNum Resource Model . . . . . . . . . . . . . . . 412 10.1.1 Design overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 10.1.2 What part of ITM will we use? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 10.1.3 The detailed design of the ITSO_ProcessNum Resource Model . 413 10.2 Creating a custom script Resource Model . . . . . . . . . . . . . . . . . . . . . . 416vi IBM Tivoli Monitoring: Creating Resource Models and Providers
  8. 8. 10.2.1 Using the wizard to create a custom script Resource Model . . . . 416 10.2.2 Extending the functions of the Resource Model . . . . . . . . . . . . . . 421 10.2.3 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 10.2.4 Testing the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 10.3 ITSO_ProcessNum source code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 10.3.1 ITSO_ProcessNum.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 10.3.2 ITSO_ProcessNum.ksh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Chapter 11. File monitoring Resource Model example . . . . . . . . . . . . . . 447 11.1 Engine component utilization: Overview . . . . . . . . . . . . . . . . . . . . . . . . 448 11.2 Compiling DMXFile MOF into Workbench. . . . . . . . . . . . . . . . . . . . . . . 449 11.2.1 Extraction of MOF from DMXFile resource monitor . . . . . . . . . . . 449 11.2.2 Strip UNIX control characters from the MOF file . . . . . . . . . . . . . . 450 11.2.3 Extraction of dependencies from the DMXFile resource monitor . 450 11.2.4 Compiling the MOF file to the CIM repository . . . . . . . . . . . . . . . . 450 11.3 Constructing the Resource Model: Dynamic Model . . . . . . . . . . . . . . . 459 11.3.1 Constructing the Resource Model: Events . . . . . . . . . . . . . . . . . . 464 11.3.2 Constructing the Resource Model: Parameters . . . . . . . . . . . . . . 467 11.3.3 Constructing the Resource Model: Dependencies . . . . . . . . . . . . 469 11.3.4 Constructing the Resource Model: Inserting code . . . . . . . . . . . . 470 11.3.5 The flow of the code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476Part 3. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Appendix A. Testing a Java Resource Model . . . . . . . . . . . . . . . . . . . . . . 481 ITM Engine tracing and clean-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Debugging the Init function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483 Debugging the VisitTree function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 Simulating data Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Verifying the Resource Model logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Appendix B. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 System requirements for downloading the Web material . . . . . . . . . . . . . 496 How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 Contents vii
  9. 9. How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503viii IBM Tivoli Monitoring: Creating Resource Models and Providers
  10. 10. Figures 1-1 High level architecture view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1-2 ITM data flow diagram: all platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1-3 Windows LCFD directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1-4 Windows ITM directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1-5 UNIX directory structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1-6 Java ITM on UNIX directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . 14 1-7 ITM Engine components for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 16 1-8 ITM Engine components for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1-9 Engine sub-components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1-10 Graph of holes and occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2-1 Introduction of the Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2-2 Panes in the Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 2-3 TMW_PhsyicalDiskModel general settings . . . . . . . . . . . . . . . . . . . . . . 29 2-4 Example of descriptive name in a profile . . . . . . . . . . . . . . . . . . . . . . . . 30 2-5 PhysicalDiskModel general settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2-6 Opening the CIM browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2-7 PhysicalDisk resource class definitions . . . . . . . . . . . . . . . . . . . . . . . . . 33 2-8 Profile indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2-9 TMW_SlowPhysicalDrive event element settings . . . . . . . . . . . . . . . . . 36 2-10 PhysicalDiskModel thresholds in a profile . . . . . . . . . . . . . . . . . . . . . . . 38 2-11 PhysicalDiskModel HighPercentUsage threshold profile display . . . . . . 39 2-12 PhysicalDiskModel logging element profile display . . . . . . . . . . . . . . . . 40 2-13 PhysicalDiskModel percent disk usage element profile display . . . . . . . 41 2-14 Creating a Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 2-15 Selecting JavaScript or Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 2-16 Selecting the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 2-17 Selecting the data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 2-18 Connecting to namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 2-19 Selecting a CIM class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 2-20 Selecting properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 2-21 Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 2-22 Specifying the event trigger condition . . . . . . . . . . . . . . . . . . . . . . . . . . 55 2-23 Entering the trigger condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 2-24 Selecting the properties to log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 2-25 Cycle time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 2-26 Saving the source file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 2-27 Building the package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 2-28 Building the TEC BAROC file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60© Copyright IBM Corp. 2003. All rights reserved. ix
  11. 11. 2-29 Copying the package file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3-1 Logical components of the Resource Model . . . . . . . . . . . . . . . . . . . . . 69 3-2 Sampling of volatile metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 3-3 Physical components in the Resource Model . . . . . . . . . . . . . . . . . . . . 74 4-1 IT management methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 4-2 Management technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 4-3 JMX MBean server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 4-4 Management agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 4-5 ITM Engine Logical Components (Java) . . . . . . . . . . . . . . . . . . . . . . . 121 4-6 Common logical components for Windows and Java . . . . . . . . . . . . . 122 4-7 ITM Engine Logical Components (Windows) . . . . . . . . . . . . . . . . . . . . 124 4-8 Logical components for Windows COM support . . . . . . . . . . . . . . . . . 125 4-9 Logical components for Windows WMI native support . . . . . . . . . . . . 127 4-10 Logical components for Windows and Java custom scripts. . . . . . . . . 128 4-11 Logical components for Windows and Java DM Classic . . . . . . . . . . . 128 4-12 Logical components for Windows and Java ILTs. . . . . . . . . . . . . . . . . 132 5-1 Java ITM Engine logical components . . . . . . . . . . . . . . . . . . . . . . . . . 142 5-2 ITM Workbench: about selected class . . . . . . . . . . . . . . . . . . . . . . . . . 144 5-3 ITM Workbench: General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 5-4 ITM Workbench: Dynamic Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 5-5 ITM Workbench: parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 5-6 ITSO_Sample.tar: Resource Model Tar File . . . . . . . . . . . . . . . . . . . . 170 5-7 mofcomp output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 5-8 javac output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 5-9 javac output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 5-10 jar output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 5-11 ITM Workbench: Tree view pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 5-12 ITM Workbench: Build menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 5-13 ITM Workbench: Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 6-1 Design overview of ITSO_SNMP_Interface_Bps Resource Model . . . 202 6-2 ITM Engine logical components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 6-3 Installing Optional Networking Components . . . . . . . . . . . . . . . . . . . . 206 6-4 Installing the SNMP Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 6-5 Enabling SNMP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 6-6 Installing the WMI SNMP Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 6-7 Connect to namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 6-8 Browse for Namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 6-9 Browse for Namespace to localhost . . . . . . . . . . . . . . . . . . . . . . . . . . 213 6-10 Selecting a class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 6-11 Selecting properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 6-12 Collection test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6-13 Filter condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6-14 Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217x IBM Tivoli Monitoring: Creating Resource Models and Providers
  12. 12. 6-15 Entering the trigger condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2186-16 Using the Proc drop down selector . . . . . . . . . . . . . . . . . . . . . . . . . . . 2196-17 Resource Model Tar File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2226-18 Step to cursor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2236-19 Quick Watch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2236-20 Debugging the Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2247-1 Java: ITM logical components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2367-2 ITM Workbench: About selected class. . . . . . . . . . . . . . . . . . . . . . . . . 2387-3 ITM Workbench: General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2637-4 ITM Workbench: Dynamic Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2647-5 ITM Workbench: Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2657-6 ITSO_SnmpProbe.tar: Resource Model Tar File . . . . . . . . . . . . . . . . . 2707-7 mofcomp output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2717-8 SnmpInterface.java: javac output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2727-9 ITSO_SnmpProbe.java: javac output. . . . . . . . . . . . . . . . . . . . . . . . . . 2727-10 ITSO_SnmpProbeILT.java: javac output . . . . . . . . . . . . . . . . . . . . . . . 2737-11 jar output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2747-12 ITM Workbench: Tree view pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2757-13 ITM Workbench: Build menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2767-14 ITM Workbench: Save As dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2778-1 Resource Model sub-components for Windows . . . . . . . . . . . . . . . . . 3068-2 Resource Model sub-components for Java . . . . . . . . . . . . . . . . . . . . . 3078-3 Workbench new Resource Model window . . . . . . . . . . . . . . . . . . . . . . 3098-4 Select VBA or JavaScript language . . . . . . . . . . . . . . . . . . . . . . . . . . . 3098-5 Workspace selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3108-6 Select data source window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3118-7 Connect to namespace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3118-8 Username/password selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3128-9 Select a Class window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3128-10 MOF compiler action select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3138-11 MOF file path and namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3148-12 MOF compiler wizard update options window . . . . . . . . . . . . . . . . . . . 3158-13 MOF compile results window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3158-14 Resource Model Wizard: Select a Class window. . . . . . . . . . . . . . . . . 3168-15 Resource Model Wizard: Select Properties window . . . . . . . . . . . . . . 3178-16 Resource Model Wizard: Filtering window . . . . . . . . . . . . . . . . . . . . . . 3188-17 Resource Model Wizard: Specify the Event Triggering Conditions . . . 3198-18 Resource Model Wizard: Select the Properties to log window . . . . . . 3208-19 Resource Model cycle time data entry panel . . . . . . . . . . . . . . . . . . . . 3208-20 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 3218-21 Dynamic Model data entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3228-22 Dynamic Model data entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3238-23 Dynamic Model data entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Figures xi
  13. 13. 8-24 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 325 8-25 Event construction window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 8-26 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 327 8-27 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 328 9-1 Design overview of ITSO_LogfileLite Resource Model . . . . . . . . . . . . 335 9-2 Windows ITM Engine Logical Components . . . . . . . . . . . . . . . . . . . . . 337 9-3 UNIX ITM Engine Logical Components . . . . . . . . . . . . . . . . . . . . . . . . 337 9-4 Flowchart of ITSO_LogfileLite decision tree script. . . . . . . . . . . . . . . . 340 9-5 Setting the CLASSPATH environment variable . . . . . . . . . . . . . . . . . . 342 9-6 The relationship of the methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 9-7 Creating a new Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 9-8 Selecting data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 9-9 Connect to namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 9-10 Launching the MOF Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 9-11 Selecting a MOF file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 9-12 Completing the compile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 9-13 Selecting the class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 9-14 Trigger condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 9-15 Property of the ITSO_LogfileLite Resource Model . . . . . . . . . . . . . . . 364 9-16 Setting the alias name of the CIM class. . . . . . . . . . . . . . . . . . . . . . . . 365 9-17 Changing the event setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 9-18 Changing the threshold setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 9-19 Adding the ITSO_LogfileLite_Pattern parameter . . . . . . . . . . . . . . . . . 368 9-20 Adding the ITSO_LogfileLite_FileName parameter . . . . . . . . . . . . . . . 368 9-21 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 9-22 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 9-23 Category and Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 9-24 Parameter ITSO_LogfileLite_FileName . . . . . . . . . . . . . . . . . . . . . . . . 378 9-25 Parameter ITSO_LogfileLite_Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . 379 9-26 Event ITSO_LogfileLite_EventNum_too_high . . . . . . . . . . . . . . . . . . . 380 10-1 Design overview of ITSO_ProcessNum Resource Model . . . . . . . . . . 412 10-2 ITM Engine Logical Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 10-3 Flowchart of ITSO_ProcessNum Resource Model . . . . . . . . . . . . . . . 415 10-4 Creating a new ITM Workbench project. . . . . . . . . . . . . . . . . . . . . . . . 417 10-5 Selecting data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 10-6 Importing the custom script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 10-7 Trigger condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 10-8 Saving the Resource Model file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 10-9 ITM Workbench thermometer icon. . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 10-10 Changing properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 10-11 Opening the event setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 10-12 Changing the event setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 10-13 Changing the threshold setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427xii IBM Tivoli Monitoring: Creating Resource Models and Providers
  14. 14. 10-14 Adding the parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42810-15 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43310-16 Category and Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43510-17 Parameter of the ITSO_ProcessNum . . . . . . . . . . . . . . . . . . . . . . . . . 43610-18 Event I of the ITSO_ProcessNum . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43711-1 Resource Model sub-components for Windows . . . . . . . . . . . . . . . . . 44811-2 Resource Model sub-components for Java . . . . . . . . . . . . . . . . . . . . . 44911-3 Workbench new Resource Model window . . . . . . . . . . . . . . . . . . . . . . 45111-4 Select VBA or JavaScript language . . . . . . . . . . . . . . . . . . . . . . . . . . . 45111-5 Workspace selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45211-6 Select data source window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45311-7 Connect to namespace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45311-8 Browse For Namespace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45411-9 Username/password selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45411-10 Select a class window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45511-11 MOF compiler action select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45611-12 MOF file path and namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45711-13 MOF compiler wizard update options window . . . . . . . . . . . . . . . . . . . 45811-14 MOF compile successful results window . . . . . . . . . . . . . . . . . . . . . . . 45811-15 MOF compile error results window . . . . . . . . . . . . . . . . . . . . . . . . . . . 45911-16 Resource Model Wizard: Select a Class window. . . . . . . . . . . . . . . . . 46011-17 Resource Model wizard properties selection window . . . . . . . . . . . . . 46111-18 Resource Model wizard triggering conditions selection window . . . . . 46211-19 Resource Model wizard filtering selection window. . . . . . . . . . . . . . . . 46311-20 Resource Model cycle time data entry panel . . . . . . . . . . . . . . . . . . . . 46311-21 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 46411-22 Event construction window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46511-23 Event construction window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46611-24 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 46711-25 Parameter data entry window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46811-26 Parameter data entry window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46811-27 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 46911-28 IBM Tivoli Monitoring Workbench main window . . . . . . . . . . . . . . . . . 470A-1 The Quadcap Embeddable Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 489A-2 Opening the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Figures xiii
  15. 15. xiv IBM Tivoli Monitoring: Creating Resource Models and Providers
  16. 16. Tables 2-1 Supported Resource Model type per operating system . . . . . . . . . . . . . 47 3-1 Resource Model types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3-2 Windows Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 3-3 UNIX Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 3-4 OS/400 Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 3-5 Memory Resource Model dependencies . . . . . . . . . . . . . . . . . . . . . . . . 85 3-6 Network Interface Card Resource Model dependencies . . . . . . . . . . . . 87 3-7 Parametric event log Resource Model dependencies . . . . . . . . . . . . . . 90 3-8 Parametric Services Resource Model dependencies . . . . . . . . . . . . . . 90 3-9 Parametric TCP/IP Ports Resource Model dependencies . . . . . . . . . . . 91 3-10 Logical Disk Resource Model dependencies . . . . . . . . . . . . . . . . . . . . . 91 3-11 Physical Disk Resource Model dependencies . . . . . . . . . . . . . . . . . . . . 92 3-12 Printing Resource Model dependencies . . . . . . . . . . . . . . . . . . . . . . . . 93 3-13 Process Resource Model dependencies . . . . . . . . . . . . . . . . . . . . . . . . 94 3-14 Processor Resource Model dependencies . . . . . . . . . . . . . . . . . . . . . . 95 3-15 Services Resource Model dependencies. . . . . . . . . . . . . . . . . . . . . . . . 96 3-16 TCP/IP Resource Model dependencies . . . . . . . . . . . . . . . . . . . . . . . . . 97 3-17 Table of correlated indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 3-18 CPU Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 3-19 Memory Resource Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 3-20 File Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 3-21 Process Resource Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 3-22 Network Interface Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 3-23 File system Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 3-24 Security Resource Model and file monitoring: Part 1 . . . . . . . . . . . . . . 105 3-25 Security Resource Model and file monitoring: Part 2 . . . . . . . . . . . . . . 106 3-26 Network RPC/NFS Resource Model (Sun Solaris specific) . . . . . . . . . 107 5-1 ILT supported classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 5-2 CIM class properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 6-1 The indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 6-2 List of elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 7-1 CIM class properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 9-1 The parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 9-2 The indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 9-3 A list of elements of the ITSO_LogfileLite Resource Model. . . . . . . . . 338 9-4 Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 9-5 An example of the values of the properties . . . . . . . . . . . . . . . . . . . . . 344 9-6 Operations in the ITSO_LogfileLite ILT . . . . . . . . . . . . . . . . . . . . . . . . 346© Copyright IBM Corp. 2003. All rights reserved. xv
  17. 17. 9-7 Operations in the ITSO_LogfileLite Provider . . . . . . . . . . . . . . . . . . . . 353 9-8 The event of ITSO_LogfileLite_EventNum_too_high. . . . . . . . . . . . . . 366 9-9 The threshold definition for Thr_EventNum_gt . . . . . . . . . . . . . . . . . . 367 9-10 Dependency files for each platform . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 9-11 Summary of the useful trace and log files . . . . . . . . . . . . . . . . . . . . . . 382 10-1 The parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 10-2 The indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 10-3 A list of elements of the ITSO_ProcessNum Resource Model . . . . . . 414 10-4 The event of Ev_process_num_becomes_very_high . . . . . . . . . . . . . 425 10-5 The event of Ev_process_num_becomes_high . . . . . . . . . . . . . . . . . . 426 10-6 The event definition for Ev_process_num_becomes_low . . . . . . . . . . 426 10-7 The threshold definition for Ev_process_num_becomes_veryhigh . . . 427 10-8 The threshold definition for Ev_process_num_becomes_high . . . . . . 428 10-9 The threshold definition for Ev_process_num_becomes_low . . . . . . . 428 10-10 ITSO_ProcessNum Resource Model scenarios . . . . . . . . . . . . . . . . . 438 A-1 Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 A-2 RmProfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 A-3 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 A-4 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 A-5 Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 A-6 Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 A-7 MetricsData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 A-8 CategoriesData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493xvi IBM Tivoli Monitoring: Creating Resource Models and Providers
  18. 18. NoticesThis information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area.Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the usersresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to:IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.The following paragraph does not apply to the United Kingdom or any other country where such provisionsare inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof express or implied warranties in certain transactions, therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM maymake improvements and/or changes in the product(s) and/or the program(s) described in this publication atany time without notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirmthe accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe capabilities of non-IBM products should be addressed to the suppliers of those products.This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which thesample programs are written. These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment to IBM for the purposes ofdeveloping, using, marketing, or distributing application programs conforming to IBMs applicationprogramming interfaces.© Copyright IBM Corp. 2003. All rights reserved. xvii
  19. 19. TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both: AIX® Notes® Tivoli® ™ OS/400® Tivoli Enterprise™ ^™ Perform™ Tivoli Enterprise Console® eServer™ Redbooks™ TME® IBM® Redbooks (logo) ™ WebSphere® ibm.com® RMF™ NetView® S/390®The following terms are trademarks of other companies:Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, othercountries, or both.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.Java and all Java-based trademarks and logos are trademarks or registered trademarks of SunMicrosystems, Inc. in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET SecureElectronic Transaction LLC.Other company, product, and service names may be trademarks or service marks of others.xviii IBM Tivoli Monitoring: Creating Resource Models and Providers
  20. 20. Preface This IBM Redbook focuses on creating Resource Models (RMs) and Providers for the IBM® Tivoli® Monitoring Version 5.1.1 infrastructure. The ITM Workbench is used for developing, debugging, and packaging Resource Models for IBM Tivoli Monitoring. You will learn how to use the step-by-step wizards provided by the ITM Workbench to create RMs to monitor any number of your IT resources, including operating systems, databases, hardware resources, and applications. In addition, you will learn how to use the step-by-step instructions to bind groups of Resource Models into deployable PACs using the ITM Toolkit. Upon completion, you will be able to create, test, and deploy monitoring solutions, quickly and efficiently creating an autonomic environment.The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, Austin Center. Tony Bhe is an IT Specialist in the United States. He has eight years of experience in the IT industry with seven years of direct Tivoli Enterprise™ products experience while working for IBM. He holds a degree in Electrical Engineering from North Carolina State University in Raleigh, North Carolina. His areas of expertise include Tivoli Performance and Availability and Tivoli Configuration and Operations. He has spent the last three years working as a Tivoli Integration Test Lead, and one year prior to that as a Tivoli Services consultant for Tivoli Performance and Availability products. Kiyonobu Inayama is an IT Specialist working at IBM Japan. He has eight years of experience mainly in systems and network management, architecting solutions, and consulting for IBM customers. He also teaches IBM classes in Japan on the areas of systems and network management. His areas of expertise include Tivoli Performance and Availability Management: server monitoring, transaction performance, and network management. Kiyonobu holds a bachelors degree in Computer Science from Nagoya University, Japan. Craig Lister is a Tivoli Analyst with StGeorge Bank in Australia. He has twenty years of experience in the IT industry. His areas of expertise include ITM, DM, and TEC rule writing, and has a passion for Perl. Massimiliano Parlione is a Software Engineer in the IBM Tivoli Software lab in Rome, Italy. He has been with IBM Tivoli Software since April 2000. He worked© Copyright IBM Corp. 2003. All rights reserved. xix
  21. 21. in the teams that developed and designed Tivoli Java™ Management Extensions (TMX4J), Tivoli Web Component Manager (TWCM), and ported ITM Version 5.1.1 on OS400 and OS2. Currently, he is working on the ITM 5.2 OEM Java engine. Before joining IBM, Mr. Parlione worked as an independent consultant for the Italian Research Council (CNR) and as an employee of the “Regione Marche” regional government. He received his degree (“laurea”) in Computer Science from the University of LAquila, Italy, in July 1995 and a doctorate in Computer Science from the University "La Sapienza" of Rome in April 2000. He is co-author of the Introducing IBM Tivoli Monitoring for Web Infrastructure, SG24-6618 redbook. Michael Vesich is a member of the Tivoli Services organization in North America. He has over fourteen years experience in the information systems field with nine years in software development. Prior to joining IBM in 1998, Michael worked for Kvaerner Engineering, initially as an Automation Engineer developing real-time industrial process control systems and later becoming the I.T. Director for the Merrillville facility. Since joining IBM, he has focused on the Performance and Availability product set, with a more recent role as an ITM Subject Matter Expert. He has contributed to the Tivoli Certification program, Business Partner enablement, and was the initial developer of the Tivoli Knowledge Toolkit. Thanks to the following people for their contributions to this project: Joanne Luedtke, Edson Manoel, Stephen Hochstetler, Lupe Brown, Wade Wallace, and Chris Blatchley International Technical Support Organization, Austin Center Wade Allen Software Developer, IBM Software Group Kevin P. Ferguson Software Developer, IBM Software Group Steve Gutierrez Software Developer, IBM Software Group Jason Hooper Senior Software Engineer, IBM Software Group Bill Horne Software Developer, IBM Software Group Richard F. Reed Systems Integrator Consultant, IBM Software Groupxx IBM Tivoli Monitoring: Creating Resource Models and Providers
  22. 22. Theo Winkelmann Technical Evangelist, IBM Software GroupBecome a published author Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. Youll team with IBM technical professionals, Business Partners and/or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, youll develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.htmlComments welcome Your comments are important to us! We want our Redbooks™ to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an Internet note to: redbook@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. JN9B Building 003 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 Preface xxi
  23. 23. xxii IBM Tivoli Monitoring: Creating Resource Models and Providers
  24. 24. Part 1Part 1 ITM fundamentals In this part, we introduce the architecture and theory behind the IBM Tivoli Monitoring Version 5.1.1 product, and provide definitions of the intricate pieces of the product, including the different types of Providers. Specifically, we cover the following topics: IBM Tivoli Monitoring Architecture IBM Tivoli Monitoring Workbench Resource Models Providers© Copyright IBM Corp. 2003. All rights reserved. 1
  25. 25. 2 IBM Tivoli Monitoring: Creating Resource Models and Providers
  26. 26. 1 Chapter 1. IBM Tivoli Monitoring architecture This chapter provides an overview of the IBM Tivoli Monitoring Version 5.1.1 engine architecture, as well as references to the components that support the engine. Subsequent chapters will provide specific details on the components related to the creation of custom IBM Tivoli Monitoring Version 5.1.1 instrumentation.© Copyright IBM Corp. 2003. All rights reserved. 3
  27. 27. 1.1 Overview IBM Tivoli Monitoring Version 5.1.1 (ITM) is a Resource Model based monitoring infrastructure that provides Resource Models for best practice monitoring of common resources. ITM also provides System Administrators a means to extend its monitoring capabilities by providing the ability to create and import custom Resource Models and dynamically pluggable instrumentation. The focus of this redbook is on the methods used to extend the monitoring capabilities of the product through the use of IBM Tivoli Monitoring Workbench 5.1.1 (ITMWB), which is supplied with the product, and through the development of custom Java instrumentation. After the development of a custom Resource Model is complete, the package created by the ITMWB can be installed into your Tivoli Enterprise environment from the command line. Once installed into the Tivoli Enterprise environment, the new Resource Model can then be used in the same manner as the ITM provided Resource Models.1.2 High level architecture Figure 1-1 on page 5 gives a high level overview of the full data flow of IBM Tivoli Monitoring Version 5.1.1. You will note that the flow commences with either the distribution of a supplied Resource Model or the development of a custom Resource Model from ITMWB, and completes with the measured metrics being supplied to one or all of the following: IBM Tivoli Data Warehouse IBM Tivoli Web Health Console IBM Tivoli Event Console The cycle of instrumenting and reporting will repeat, with the above outputs, until the ITM Engine is stopped.4 IBM Tivoli Monitoring: Creating Resource Models and Providers
  28. 28. Trend Analy sis CuCu Trend Ana lysis s t s to om m ize ize/ De /D Dis Data Warehouse Data Warehouse Profile Profile D fa e is t r tri ib ulfau bu utRollup ts lt s te e Rollup y Web Health la Web Health TMR TMR TMR TMR D isp Display Console Console Ge tD ITM ITM ata ll Tivoli Event Console In s ta HeartBeat HeartBeat Get Data Endpoint Di Unix/Linux tall Resource In s st r Model ib Resource Design Distributeut Endpoint Endpoint Model e Endpoint Windows ITM Engine Uni x/Linux Create Windows Design , Create, Deb ug NT/2000 NT/2000 Debug ITM Engine ITM Engine ITM Engine Workbench WorkbenchFigure 1-1 High level architecture view1.3 Engine features and abilities ITM eliminates the need to transfer large amounts of diagnostic data back to a central location for evaluation. On each localized endpoint, it has the ability to: Perform root-cause analysis Isolate individual faults Initiate programmed corrective actions The ITM Engine is able to initiate the following functions on the endpoint: Event analysis Chapter 1. IBM Tivoli Monitoring architecture 5
  29. 29. Event correlation (Windows® only) Event aggregation Event management Data logging The engine’s ability to perform these functions locally is what frees the system administrators from the analysis of multiple data sources, including large log files, event logs, and performance metrics, to detect resource failures and bottlenecks. A further extension of the local engine’s capabilities is obtained when the data logging feature is used in conjunction with IBM Tivoli Data Warehouse. This enables system administrators to gain a trend analysis tool for any resource profile from which data logging is enabled. All instrumentation sources for ITM are provided to the engine through a Common Information Model (CIM) interface. In a Windows environment, this is provided by Microsoft®’s implementation of CIM, Windows Management Instrumentation (WMI). The UNIX® component of CIM is provided via IBM Tivoli’s own CIM implementation, which is called Touchpoint.1.4 Endpoint integration There are several aspects that make up the ITM integration with the Tivoli Endpoint. It helps to be able to identify these aspects in order to aid in problem diagnosis. First, understanding the flow of information through the endpoint to the ITM components will assist in determining which components may be at fault; is the problem high level (TMR or specifically MDist2), mid-level (the assigned Gateway), or low-level (the Endpoint or ITM Engine itself)? Second, the directory structures of the engine will define which files or paths should be investigated when a problem is believed to be on the endpoint directly.1.4.1 ITM data flow It is helpful to understand the flow of configuration information as it relates to the ITM components. Figure 1-2 on page 7 provides a high level view of the ITM Engine upon which later chapters will provide additional granularity.6 IBM Tivoli Monitoring: Creating Resource Models and Providers
  30. 30. Data Flow TME 1 LCF ITM Engine 2 3 Event Analyzer Handling ITM Engine 4 TMWService (Java Class) 5 Platform Specific CIM Implementations Reference s ITM Logical Diagrams: Touchpoint (Java) -or- WMI (Windows) Provider Layer Resources (OS & Applications)Figure 1-2 ITM data flow diagram: all platforms Chapter 1. IBM Tivoli Monitoring architecture 7
  31. 31. Figure 1-2 on page 7 contains five boxes numbered one through five. Each of these boxes represents a data flow and is defined in the subsequent numbered lists. Each list number represents the number in the box in Figure 1-2 on page 7. 1. Management Framework & Endpoint Management [M9] information (that is, Reference Model and Parameters) and Manageability [M12] information (that is, Dynamic Model) reach the endpoint through a conduit, currently the Tivoli Endpoint agent, LCFD. 2. ITM Engine The ITM Engine works as a façade between the LCFD and the ITM components. It receives Tmw2k profile distributions and configuration changes from the LCFD and configures the management function, the analyzer component, with the management information, Resource Model and parameters, and the Touchpoint with the manageability information, and Dynamic Model. 3. Dynamic Model The Dynamic Model is loaded in the Touchpoint. The manageability information presented in M12 MOF format will be loaded in the underlying CIMOM. 4. Analyzer The Analyzer component is actually a script engine, which means the configuration that it receives from the façade is presented in script form. In this script, the TMWService object is instantiated and initialized with information about the resource that it needs to collect metrics on. At run time, the code inside the script invokes the collect method of TMWService, which in turn accesses the Touchpoint to collect the resource metrics. 5. TMWService a. Java platform Driven by the script, TMWService Java class accesses the Touchpoint using the Touchpoint service layer (TSL) interface on Java to collect the resource metrics. b. Windows platform Driven by the script, the TMWService COM object accesses the WMI using the WMI APIs to collect the resource metrics. The metrics may be direct WMI Providers or ILT compliant Providers utilizing the Tivoli Touchpoint Java engine. The metric data collected is reported back to the Resource Model script where it is processed according to the best practices coded within the script. An event handling component is then used to allow the analyzer to communicate the result of the best practices appliance to other components.8 IBM Tivoli Monitoring: Creating Resource Models and Providers
  32. 32. CIM components and the Provider layer The Common Information Model (CIM) allows the ITM Engine to handle system resources in an industry standard object oriented fashion, while the Provider layer allows for dynamically pluggable instrumentation within the ITM Engine. The concepts and technologies behind the CIM implementation and the Provider layer are discussed at length in Chapter 4, “Providers” on page 109. Resources Resources refers to the physical resources that the Provider components provide instrumentation for. Instrumentation is handled through either operating system libraries or Application Programming Interfaces (APIs), such as Java or vendor supplied APIs. Such resources include, but are not limited to, the following: System hardware Operating system Applications1.4.2 Directory structures When troubleshooting, it is important to know where to find the files you need. This section will give some insight into where log files and other ITM components are located. Windows platform Figure 1-3 on page 10 corresponds to the Framework (LCFD) components of the endpoint. The primary log file, lcfd.log, can be found in the lcfdat1 directory. This log file can prove to be very useful while diagnosing many problems. Chapter 1. IBM Tivoli Monitoring architecture 9
  33. 33. Figure 1-3 Windows LCFD directory structure It is also important to note that the lcfbinw32-ix86JREDMAE directory is where Java is installed by default when you distribute a profile from the command line using the wdmdistrib command and the -J switch.10 IBM Tivoli Monitoring: Creating Resource Models and Providers
  34. 34. Another directory of interest is lcfbinw32-ix86tools. This is where all the tooltype programs (perl, bash, ntprocinfo, and so on) reside.Figure 1-4 corresponds to the ITM components of the endpoint. The main ITMlog file resides in the lcfdat1LCFNEWTmw2k directory and is namedTmw2k.log. It is in here that you will find most of your ITM debugging informationwhen you run into problems.Figure 1-4 Windows ITM directory structureAnother useful file is located in lcfdat1LCFNEWAMGlogs and is namedlogging.properties. This file is a Java config file that gives you the ability to initiatelogging for the various Java modules. This is easily done by looking for linessuch as islogging=False and changing them to islogging=true, and thenrestarting the ITM Engine.You will notice another directory under the preceding directory called log files.This directory relates to the log file adapter Resource Model discussed later inthis book. It is in this file that the offsets are stored when reading log files. If theengine is stopped and Java is also stopped, you can remove this file. When the Chapter 1. IBM Tivoli Monitoring architecture 11
  35. 35. engine restarts, the ITM log file adapter will start reading from the beginning of your log file. In the directory lcfdat1LCFNEWAMWlogs, you will find three other log files named ILTManagerForJava1.log, trace_ILTManagerForJava.log, and msg_ILTManagerForJava.log. These can be useful when debugging Java ILT issues. If you have enabled logging in your profile, then the directory lcfdat1LCFNEWTmw2kdb is where the log information is written on a Windows endpoint and stored in a Microsoft Access database. The lcfdat1LCFNEWTmw2kDec directory is particularly interesting. This directory is where your code, be it VBA or Java, is stored on the local endpoint. If you stop your ITM Engine by use of the wdmcmd -stop -e <endpointname> command, you are able to make changes to this script on the local endpoint. You will then be able to restart the ITM Engine and validate your changes. This can be a great time saver, as you do not have to go all the way out to the ITMWB and back through the distribution process. In the lcfdat1LCFNEWTmw2kMof directory, you will find your MOF files that you compiled from the ITMWB. There is also a directory within this tree named compiled. It houses the locally compiled MOF files. So if your MOF file is in the top directory but not in the compiled directory, then you know that you have a problem. Finally, the lcfdat1LCFNEWTmw2kUnixClassesWizGenRM directory is the storage area for any dependant jar files that you may have included in your Resource Model. Java platform on UNIX Figure 1-5 on page 13 corresponds to the Framework (LCFD) components of the endpoint. The main LCFD log file, lcfd.log, can be found in the lcfdat1 directory. This log file can prove to be very useful while diagnosing many problems. It is also important to note that lcfbinaix4-r1JREDMAE is where Java is installed by default when you distribute a profile from the command line using the wdmdistrib command and the -J switch.12 IBM Tivoli Monitoring: Creating Resource Models and Providers
  36. 36. Figure 1-5 UNIX directory structureIt is in the lcfdat1LCFNEWAMWlogs directory, in Figure 1-6 on page 14,where you will find the trace_dmxengine.log, msg_dmxengine.log,trace_dmxeu.log and trace_dmxntv.log log files. The file that will be most useful Chapter 1. IBM Tivoli Monitoring architecture 13
  37. 37. is trace_dmxengine.log. This file is the equivalent to the Windows endpoint Tmw2k.log. The best way to view the file, as it is XML formatted, is to open the file in a text editor and set word wrap on. Figure 1-6 Java ITM on UNIX directory structure14 IBM Tivoli Monitoring: Creating Resource Models and Providers
  38. 38. Another useful file is located in lcfdat1LCFNEWAMGlogs and is named logging.properties. This file is a Java config file, which give you the ability to instigate logging for the various Java modules. This is easily done by looking for lines like islogging=False and changing it to islogging=true, and then restarting the ITM Engine. If you have enabled logging in your profile, then the lcfdat1LCFNEWTmw2kUnixdataITMLoggerdblogger directory is where the log information is written on a UNIX endpoint. The logging information is stored in an Open Source Database by Quadcap Software. The lcfdat1LCFNEWTmw2kUnixDec directory is particularly interesting. It is here that your code, be it VBA or Java, is stored on the local endpoint. If you stop your ITM Engine by use of the wdmcmd -stop -e <endpointname> command, you are able to make changes to this script on the local endpoint. After restarting the ITM Engine, you can then validate your changes. This can be a great time saver, as you do not have to go all the way out to the ITMWB and back through the distribution process. Finally, the lcfdat1LCFNEWTmw2kUnixClassesWizGenRM directory is the storage area for any dependant jar files that you may have included in your Resource Model.1.5 ITM Engine architecture Figure 1-7 on page 16 highlights the logical components that comprise the Windows platform ITM Engine. Chapter 1. IBM Tivoli Monitoring architecture 15
  39. 39. Windows, ITM Engine Logical Components Analyzer Resource Resource Resource Resource Resource Resource Resource Model Model Model Model Model Model Model TMWService WMI APIs WMI (CIMOM) DM Classic Monitor Probes COM Objects ILT Manager for Java (WMI Provider DLL) Custom Scripts WMI Provider DLLs Java Virtual Machine (JVM) Launch (Class Loader) ILT ILT JMX ILT Provider MBean Providers JNI Server Binary Resource Resource Resource Resource Resource MBean1 Library Resources (OS & Applications) Figure 1-7 ITM Engine components for Windows Figure 1-8 on page 17 highlights the logical components that comprise the Java platform ITM Engine.16 IBM Tivoli Monitoring: Creating Resource Models and Providers
  40. 40. Java, ITM Engine Logical Components Analyzer Resource Resource Resource Resource Resource Model Model Model Model Model DM Classic Monitor Probes Service Object Launch (Class Loader) Custom Scripts Java Class Loader ILT ILT JMX ILT Provider MBean Providers JNI Server Native Resource Resource Resource MBean(s) Binaries Resources (OS & Applications) Figure 1-8 ITM Engine components for Java1.5.1 Engine input To get the engine to monitor your endpoint, you need to create a profile that contains at least one Resource Model and distribute it to the endpoint. A Resource Model is a way of monitoring certain properties of the endpoint to which the profile, which contains the Resource Model, is distributed. The data is derived through the Service Object API using WMI or CIM from the endpoint’s operating system. When the Resource Model is distributed to the endpoint, the following types of files are placed in the directories described in 1.4.2, “Directory structures” on page 9 and “Java platform on UNIX” on page 12: Managed Object Format (MOF) Visual Basic or JavaScript Chapter 1. IBM Tivoli Monitoring architecture 17
  41. 41. Dependent jar files A Resource Model may have the following elements defined depending on the desired functionality: Visual Basic or JavaScript, as contained in the VisitTree function Events Thresholds Parameters Logging Dependencies The script component Every Resource Model requires some programatic instructions on how to deal with the metric data supplied. It needs to compare these values against your thresholds and decide when it is appropriate to generate the alerting events. The public function VisitTree contains your monitoring algorithm, which will be called cyclically, as specified in your Resource Model. Events and thresholds Each Resource Model can include one or more events which will be checked against its corresponding threshold. Each period cycle, the monitored resource is checked against the specified numeric threshold. If the threshold is exceeded, then an event will be escalated. Events can have many causative indications or only one. If there are many indications, they must be aggregated before they trigger an event. If the indication does not exceed its particular threshold, it is called a hole. Holes are used to reset indications. In other words, if an indication exceeds its threshold for three cycles in a row without any holes, then an event would be generated. If, on the second cycle, the threshold was not exceeded, then the engine would restart the threshold breech count. This examples assumes that you have configured the indications and holes for the Resource Model to be 3 and 0, respectively. Parameters While thresholds must be numeric, parameters can be multiple numeric or alpha characters. You are able to customize your Resource Models by coding the parameters in ITM Workbench as defaults or they can be entered at profile definition time.18 IBM Tivoli Monitoring: Creating Resource Models and Providers

×