html5-img
1 / 34

IBM T ivoli Monitoring v6.1 ITM 6.1 Integration ITM 5.1.2

IBM T ivoli Monitoring v6.1 ITM 6.1 Integration ITM 5.1.2. IBM Software Group Services for Tivoli. Agenda. Introduction Why integrate ITM 5.x with ITM 6.1? Architectural Overview Installation and Deployment Agent basics Adding support for Custom RM Workspace Views for RM health and data

van
Télécharger la présentation

IBM T ivoli Monitoring v6.1 ITM 6.1 Integration ITM 5.1.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IBM Tivoli Monitoring v6.1ITM 6.1 Integration ITM 5.1.2 IBM Software Group Services for Tivoli

  2. Agenda • Introduction • Why integrate ITM 5.x with ITM 6.1? • Architectural Overview • Installation and Deployment • Agent basics • Adding support for Custom RM • Workspace Views for RM health and data • Integration of RM collected metric data with TDW 2.1

  3. Terminology Comparison: ITM v5.1 –vs- ITM v6.1

  4. Why integrate ITM 5.x with ITM 6.1 (TEPS)? • New 6.1 Portal GUI capabilities allow a more complete and user-friendly interface for the performance and availability data • Integration of multiple GUIs (ITM 5, OMEGAMON/ITM6, Omegamon Z, TEC and TDW Data) • Reduced number of end-user clients to be installed and run in parallel • Quick links sometimes available • Meaningful views and workspaces for recent and long-term historical data • Trending with the Data Warehouse • Forensic data for problem reconstruction • Simplified schema for easier manipulation and extraction of data

  5. Why integrate ITM 5.x with ITM 6.1 (TDW)? • TDW 2.1 also stores instance data which improves enormously the problem diagnosis capabilities inside the portal • Some customers are accessing the local ITM engine DB directly for that reason • Easy and granular pruning and aggregation mechanism can be leveraged • Metric data from custom resource models can be included into the warehouse much more easily • Who has written a custom ETL for TDW 1.x? Congratulation! • Free of Charge for ITM 5 customers

  6. Agenda • Introduction • Why integrate ITM 5.x with ITM 6.1? • Architectural Overview • Installation and Deployment • Agent basics • Adding support for Custom RM • Workspace Views for RM health and data • Integration of RM collected metric data with TDW 2.1

  7. Introduction • ITM v6.1 architecture is based on the OMEGAMON platform • ITM v6.1 is not based on the Tivoli Infrastructure (Framework) • Existing environments are integrated through various interfaces included in ITM v6.1: • OMEGAMON • IBM Tivoli Monitoring v5.1 • Tivoli Enterprise Console • Tivoli Business System Manager

  8. Components: Top Down • Tivoli Enterprise Portal Server (TEPS) • Tivoli Enterprise Portal client (TEP) • Installable client or Internet Explorer v6 browser • User interface management • RDBMS to support configuration data (TEPS DB) • TEC & Browser integration for enhanced capabilities • Tivoli Data Warehouse (TDW) • Actually a schema installed to a supported database (DB2, MS SQL, Oracle) • Warehouse Proxy Agent • Handles aggregation and loading of data into the TDW • Summarization & Pruning Agent • Processes data in the TDW for summarizing & pruning. • Tivoli Enterprise Monitoring Server (TEMS) • Situations • Heartbeat with Agents • Data collection and loading to the Warehouse Proxy • Agents • Various Agent for monitoring requirements (OS, WAS, DB2, etc.) • Integration Agent (for ITM v5.1 engine) • Optional components (not shown) • Failover TEMS • Remote TEMS: For load balancing number of Agents

  9. Architecture: ITM v5.1 Integration with ITM v6.1

  10. Integration Agent (IA) - What it is and what’s not? • Has two primary roles to perform towards ITM 6.1: • Displays RM health status and indications (like wdmlseng) • Displays real-time RM metrics and logs data for historical usage • Is focused on data collection – for example start and stop of resource models via the agent or TEPS is not possible • It does NOT take events of the ITM engine into account • Behaves like any other ITM 6.1 agent • Heartbeating • Collect data for real time visualization (TEPS requests for RM health/indications and RM views) • Record the data for warehousing (stored locally or on the TEMS) – if enabled • Official Name:IBM Tivoli Monitoring 5.x Endpoint Agent Sometimes also called ITM 5.x endpoint agent

  11. XML stream Local pipe Send monitoring data FP6 ITM 5.x Endpoint Agent ITM v5 Engine Architecture - ITM v5 Integration with ITM v6.1

  12. Integration agent – How does it work? • Communicates directly with the ITM 5.x engine over a local pipe - no gateway usage • Includes a set of predefined metadata files that define the attribute groups that result from the real time logging • All PAC RM metrics • Additional health status • For custom RMs the metadata files have to be created and deployed manually with help of a tool • IA gets automatically started by the ITM engine during a cycle when: • Data is logged (enabled in Tmw2kProfile) and • At the end of a visit tree cycle

  13. Agenda • Introduction • Why integrate ITM 5.x with ITM 6.1? • Architectural Overview • Installation and Deployment • Agent basics • Adding support for Custom RM • Workspace Views for RM health and data • Integration of RM collected metric data with TDW 2.1

  14. Product Prerequisites & Installation • ITM 5.x Endpoint • ITM 5.1.2 Fixpack 6 • ITM 5.1.1 Component Services Fixpack 2 / ITM 5.1.3 Component Services • Supported endpoint platforms • AIX 5.1 and higher, Solaris 2.8 and higher, (32/64bit) • HP/UX 11.11 and higher (32/64bit) • On Intel: SLES 8 and higher, Red Hat 2.1 and higher (32bit only) • On Z: SLES 8 and higher, Red Hat 3 and higher (32/64bit) • Windows XP, 2000 and 2003 (32bit only) • Installation of “TEMA for ITM v5.1“ via winstall or Tivoli Desktop • To be installed on all Gateways serving ITM v5.x Endpoints • ITM 6.1 prerequisites: “TEMA for ITM v5.1“ has to be chosen for seeding during ITM 6.1 installation

  15. Agent distribution and base configuration • Done via command witm61agt • Distributes the necessary files to endpoints • Binary code (can be omitted for re-configuration) • Metadata files for the known resource models (atr and xml files) • Specifies TEMS server address and port the IA should talk to • Server log files are located under %DBDIR%\KTM\logs or rather $DBDIR/KTM/logs • File names will look liketrace_witm61agt____<no>__p<pid>.log • Numbered <no> consecutively and with the <pid> of command

  16. Controlling ITM 5.x data seeding behavior • Can be configured with command wdmepconfig • Example: wdmepconfig -e my_ep -D DataSeeding=ITM6 • Valid values for the “DataSeeding” key are: • ITM5 - support ITM 5.x for WebHealthConsole and TDW 1.x • ITM6 - supports ITM 6.1 Tivoli Enterprise Portal only – no data to local Itm 5.x DB • BOTH - combine both • ITM engine has to be restarted to take affect! • “BOTH” allows smooth transition from TDW 1.x to 2.1, so that customers can compare and verify the collected metrics in both environments • WHC and TDW 1.x might become redundant and can be switched off • But keep in mind if and why local RM db data or RIM db data might still be needed • TSLA 2.1.1 leverages TDW 2.1 in addition to TDW 1.x

  17. Sample step-by-step approach • Install ITM 6.1 including the seeding of the integration agent • Install ITM 5.x prerequisites in TME environment • Install integration agent in TME environment • Deploy integration agents to endpoints • Define and configure the data collection behavior (ITM5, ITM6, both) • Start using TEP in parallel for real-time analysis as well as short and long-term reporting • If satisfying, stop ITM 5.x data collection and rollup for WHC and TDW 1.x by • Switching off the Tmw2kProfile settings “TDW logging” BUT “Enable data logging” has to remain switched on • Changing the DataSeeding for the ITM engine to “ITM6” only • Turning off the wdmcollect upload

  18. Stopping and deleting integration agent • ITM 5.x environment • Configure DataSeeding = ITM5 • Recycle ITM engine • Remove integration agent files from the agent via • witm61agt –r • ITM 6.1 environment • Remove managed systems for this agent from the “managed system workspace” • Managed Systems are getting status offline • <host>:KTM • <host>:AMW • <host>:TM • Context menu of the agents does NOT include “remove” option

  19. Agent files location AVA code for the agent • Integration Agent binaries • $LCF_BINDIR/../TME/KTM/ktmcma$(EXE_EXTENSION) • Integration Agent libraries • UNIX: $LCFROOT/lib/$INTERP • Windows: $LCFROOT/bin/$INTERP/mrt • Logfiles: • $LCF_DATDIR/LCFNEW/KTM/logs • Metadata and environment files • $LCF_DATDIR/LCFNEW/KTM/ATTRLIB • $LCF_DATDIR/LCFNEW/KTM/metadata • $LCF_DATDIR/LCFNEW/KTM/KTMENV Caution: if ITM5 engine gets removed and redeployed, the integration agent has to be redeployed as well

  20. Custom Resource Model Integration • For unknown RMs sample description files will be created on the endpoint under %LCF_DATDIR%/LCFNEW/KTM/metadata • <Category>_<RMname>_<Context>_<Resource>.xml.sample • Describes the data in xml format • “ktm-seedgen.jar” creates the metadata files from the sample files. • Catalog and attribute files for TEMS, TEPS and Integration agent • SQL script files for the TEPS database • TEMS and TEPS have to be • Re-seeded with the new metadata files • Recycled to take effect

  21. Custom Resource Model Integration • TME command witm61metadatais used to manage metadata files • Add or remove metadata files and attribute files to/from the dependency sets and distributes them to the gateways which have the Integration Agent installed. • List the current metadata dependency sets • Caution: remove only files from the dependency not from the EP • TME command“witm61agt” has to be used to re-distribute the new dependencies to the endpoints • After recycling the ITM v5.1 engine the new category will be shown on the TEPS

  22. Agenda • Introduction • Why integrate ITM 5.x with ITM 6.1? • Architectural Overview • Installation and Deployment • Agent basics • Adding support for Custom RM • Workspace Views for RM health and data • Integration of RM collected metric data with TDW 2.1

  23. Workspace views • Views are installed as seed information like for any other OS agent • To be chosen during ITM 6.1 installation • Resource Model Health Workspace • Displays status and health of RMs • Display details for a RM including historical trend and indication instances • Display “real-time“ RM metrics • Resource Model Workspaces • For some RM categories there are `pretty´ RM views predefined • DB/2, Oracle, Windows, Unix - Linux, Solaris and WebSphere AS • Plain table format for others which can be adjusted accordingly • Agent Message Workspace • Display errors reported by the integration agent Linked together for easy drill-down

  24. RM Health Workspace - Resource Model Overview Resource Model Overview - shows the health trend of the resource models Clicking on the link, it takes you to the metrics (event data) for that indication instance.

  25. RM Health Workspace - Resource Model Details Resource Model Details - shows the health trend of the resource model and any indication that is active (if health < 100). Clicking on the link, it takes you to the metrics (event data) for that indication instance.

  26. RM Health Workspace - Indication Metrics Indication Metrics - shows the resource model details, the indication instance that was selected and the metrics for that indication instance.

  27. RM WorkSpace– Unix Network Traffic

  28. RM Workspace – Unix Process

  29. Situations for ITM 5.x agents You can define situations on the ITM 5.x attribute groups as for other ITM6 agents!

  30. Agenda • Introduction • Why integrate ITM 5.x with ITM 6.1? • Architectural Overview • Installation and Deployment • Agent basics • Adding support for Custom RM • Workspace Views for RM health and data • Integration of RM collected metric data with TDW 2.1

  31. Historical data collection • Possible for any attribute group of a PAC (ITM RM category) • Example: Product=PAC-Windows Attribute group=AMW_TMW_LogicalDisk_PercentSpace • Collection Interval: 5,15,30 or 60 minutes • This might be slower than the RM collection interval, so graphs will have to set the “sample time” as the axis attribute in order to display each “real” recording time. • Collection location: “local” or “TEMS” • Instance data is collected by default • Summarization interval: hourly, daily, weekly, monthly, quarterly or yearly • Pruning settings for each summarization interval and for instance data • Warehouse upload interval: 1 hour, daily or off

  32. Historical ITM 5.x Data (TMW_Processor)

  33. Notice • There is no ITM 6.1 TEP authentication bridge to authenticate TME user and adhere to the defined TME authorization views • To limit access the TEP logical navigation trees (scopes) for an user have to be defined via the standard TEPS means • no modify rights should be assigned since it disregards theses scopes! • Currently the integration agent only supports the IP.PIPE protocol, SNA and SSL are not yet available • For environments with IP.SPIPE defined, add the IP.PIPE protocol for the TEMS server and the Warehouse proxy to assure the connection for integration agents at least • The integration agent cannot be deployed and controlled (start/stop) by means of the ITM 6.1 infrastructure • This is completely handled by TME and ITM 5.x mechanisms • Currently the RM status not equal to “running” are not shown in the workspaces • Planned to be included in the ITM 5.1 FP 6. • ITM6 Data collection interval might happen in shorter cycles than the ITM5 data collection interval • Graph styles have to be changed to display “Sample Time” instead of “Recording Time”

  34. End of Unit.

More Related