1. technology and computing
2. software
3. databases

STOR03
How to integrate TSM 6.x Monitoring & Reporting into the real ITM world
Christian Michaelski
ACT IT-Consulting & Services AG
Agenda
 Overview TSM 6.x Monitoring & Reporting
 Deep Dive
 Integration of TSM 6.x Agent into IBM Tivoli Monitoring
COPYRIGHT ACT © 2010
OVERVIEW TSM 6.X
MONITORING & REPORTING
COPYRIGHT ACT © 2010
Enterprise Monitoring
 Enterprise monitoring is all about observing resources
that are crucial for your daily business operations.
 Use IBM Tivoli Monitoring to:
 View availability and performance data that provides
insight into the components, applications, and services in
your enterprise
 Be notified of incidents that require attention
 Diagnose problems
 Enterprise monitoring data can be available as:
 Incidents, displayed as situation events, which indicate
potential problems that require attention
 Real-time statistics about a particular resource or
application
 Historical statistics to provide insight into the long-term
behavior of components
COPYRIGHT ACT © 2010
ITM Positioning
 TSM 6.1 Monitoring & Reporting is a monitoring solution
based on IBM Tivoli Monitoring 6.2 FixPack 1.
 TSM 6.2 Monitoring & Reporting is a monitoring solution
based on IBM Tivoli Monitoring 6.2.1.
 IBM Tivoli Monitoring 6.2x is a systems monitoring solution.
 It allows you to monitor a variety of resources, including
distributed systems, mainframe systems, databases, and
applications.
 Many other IBM offerings have an option to interact
with IBM Tivoli Monitoring like Tivoli Storage Manager.
COPYRIGHT ACT © 2010
Architecture and Components
 ITM follows a client-server architecture.
 The Tivoli Monitoring infrastructure includes all
components needed in an enterprise monitoring
solution.
 Those components are called Tivoli Monitoring Services
(TMS). They include:




TEP (Tivoli Enterprise Portal)
TEPS (Tivoli Enterprise Portal Server)
TEMS (Tivoli Enterprise Monitoring Server)
TEMA (Tivoli Enterprise Monitoring Agent)
TEP
COPYRIGHT ACT © 2010
TEPS
Hub TEMS Remote TEMS
TEMA
Tivoli Enterprise Monitoring Agents
TEMA
 The data collectors, which gather data from one or
more systems that are critical for your business.
 Each collected parameter is called an attribute. These
are grouped in attribute groups to simplify managing
the large amount of data collected by some agents.
COPYRIGHT ACT © 2010
Tivoli Enterprise Monitoring Server
Hub TEMS Remote TEMS
 Each enterprise monitoring solution must contain one
Hub TEMS. It can include multiple remote Tivoli Enterprise
Monitoring Servers, which are used to scale large
installations.
 Stores the definitions for conditions, called situations,
that indicate a problem with a particular resource.
 Controls the security (user authentication) for your
monitoring solution.
 Can store historical data temporarily.
COPYRIGHT ACT © 2010
Tivoli Enterprise Portal Server
TEPS
 Functions as a repository for all user data, defining what
a user can access and how the data is displayed
 Connects to a hub TEMS and can be accessed by the
TEP clients
 Controls access to data and TEP functions by user ID
 Stores data in a Microsoft SQL Server or IBM DB2 UDB
COPYRIGHT ACT © 2010
TEP Client
TEP




Three TEP Client types:
TEP Desktop Client
TEP Browser Client
TEP WebStart Client
COPYRIGHT ACT © 2010
Tivoli Data Warehouse
TEP
TEPS
Hub TEMS Remote TEMS
Summarization &
Pruning Agent
Warehouse Proxy
Agent
Warehouse Database
Server
COPYRIGHT ACT © 2010
TEMA
Tivoli Data Warehouse Solution
 Tivoli Data Warehouse database
 Warehouse Proxy agent
 Summarization and Pruning agent
Source
Agent or
TEMS
Short-term
data
12
COPYRIGHT ACT © 2010
Warehouse
Proxy agent
Tivoli
Data
Warehouse
Summarization and
Pruning agent
Tivoli Data Warehouse Database
 Row-based relational database
 DB2 UDB
 Oracle
 Microsoft SQL Server
Tivoli
Data
Warehouse
 Detailed and summarized data within the same schema
 One warehouse database for multiple monitoring
environments
 Data served to the Tivoli Enterprise Portal (TEP) on
request
 Short-term and long-term data combined in single request
- Less than 24-hour-old data from TEMA or TEMS
- Greater than 24-hour-old data from Data Warehouse
13
COPYRIGHT ACT © 2010
Warehouse Proxy Agent
 Handles warehouse requests from all managed systems
in the monitoring environment
 Creates detailed data tables and indexes as required
 Multiple Warehouse Proxy agents supported
 Must be connected to the hub TEMS
 Product code: hd
 Various operating systems supported
 Windows and several UNIX and Linux options;
consult installation guide for details
Warehouse
Proxy
Warehouse
Proxy
14
COPYRIGHT ACT © 2010
Tivoli
Data
Warehouse
Summarization and Pruning Agent
 Manages the data in the Tivoli Data Warehouse
 Summarizes according to the configuration for an
attribute group
 Creates tables and indexes as required
Prunes old data by configuration
Must be connected to the hub TEMS and the TEPS
One agent for one warehouse
JDBC connection to warehouse database (regardless
of operating system)
 Various operating systems supported




 Windows and several UNIX and Linux options;
consult installation guide for details
Summarization and
Pruning Agent
15
COPYRIGHT ACT © 2010
Tivoli
Data
Warehouse
Tivoli Data Warehouse Database
Issues
 Dynamic table creation
 Tables, indexes, views
 Based on attribute groups and summarization levels
selected
 No user control
 No schema provided
 Database growth
 Can exceed database or disk capacity
 Planning spreadsheet
 Backup and recovery
 Normal database administrator procedures
 Logs required for recovery
16
COPYRIGHT ACT © 2010
Historical Data Collection Process





17
Short-term data collection and storage
Mapping attribute groups to table names
Warehousing
Summarization
Pruning
COPYRIGHT ACT © 2010
Tivoli Common Reporting
TEP
TEPS
Hub TEMS Remote TEMS
TEMA
Tivoli Common Reporting
Warehouse Database
Server
COPYRIGHT ACT © 2010
Report
Library
HTML
Reports
PDF
Reports
DEEP DIVE
COPYRIGHT ACT © 2010
Product Architecture
 Reporting consists of the following components
 ITM (IBM Tivoli monitoring)
- TEP (Tivoli Enterprise Portal)
- TDW (Tivoli Data Warehouse)
- TSM Reporting Agent
 TCR (Tivoli Common Reporting)
 ITM, along with the TSM reporting agent does the work
of collecting data from TSM server(s) and sending that
data to TDW for historical storage
 TEP is used to view near-live data from TSM
 TEP is used to configure historical data collection from
TSM
 TCR accesses the TDW historical data and reports it in
the TCR UI
COPYRIGHT ACT © 2010
Product Technonogy
 IBM Tivoli Monitoring is both native and Java based
technologies
 Tivoli Storage Manager Reporting Agent is JAVA based
 Tivoli Common Reporter is Web/ISC based
COPYRIGHT ACT © 2010
Agent on TSM Server
TSM
TSM Server
TSM Server
TSM
Activity Log
ITM Agent
Admin
API
TSM
Historical
Extraction
Derby
TSM/ITM
Agent
TSM
Operational
Database
ITM
ISC
Reports
COPYRIGHT ACT © 2010
TEP
Client /
Browser
TCR
Reporting
engine
ITM Server
TEPS / TEMS
WPA / S&P
Warehouse
DB/2
Agent on TSM Server
 TSM Monitoring and Reporting Agent installed on the
TSM server
 Sends the queried data from the TSM server to the ITM
server
 Install/Configurations steps
 Install TSM Monitoring and Reporting Agent on the TSM
server
 Install IBM Tivoli Monitoring (ITM) on a different system
 Create (instance) and configure the instance to query
data from the TSM server and send the data to the ITM
server
 TEP, TEMS, TDW and DB2 will be run/manage from the ITM
server
COPYRIGHT ACT © 2010
Agent on ITM Server
TSM Server
ITM Server
TSM Server
TSM Server
TSM
Activity Log
ISC
Reports
COPYRIGHT ACT © 2010
ITM Agent
Admin
API
TSM
Historical
Extraction
Derby
TSM/ITM
Agent
TSM
Operational
Database
TEP
Client /
Browser
TCR
Reporting
engine
ITM Server
TEPS / TEMS
WPA / S&P
Warehouse
DB/2
Agent on ITM Server
 TSM Monitoring and Reporting Agent installed on the
ITM server
 Pulls the queried data from the TSM server
 Install/Configurations steps
 Install ITM
- This will automatically install DB2, ITM and TSM Agent
 Create (instance) and configure the instance to query
data from the selected TSM server
COPYRIGHT ACT © 2010
Admin / Operator Console
 Admin Center (TCR Historical Reports)
 Can be installed on any system with network access and
a web browser
 User can changes the data source to point to the system
(ITM server) where the TDW (DB2) is installed
 Tivoli Enterprise Portal
 Client can be installed on every workstation
 To access ITM:
- TEP Client
- TEP Client Browser Mode
- TEP Client Java WebStart
COPYRIGHT ACT © 2010
Hints and tips
 Capacity issues:
 Large capacity TSM servers may encounter time-outs
during certain queries.
 ClientMissedFiles = contains the most possible data
 NodeActivity = depending on the number of nodes and
the number of operations done each day
 Equipment issues:
 The longer that historical data is collected, the more
storage space will be needed on the reporting server
 As with most products, the more memory and disk
capacity available, the better the reporting server will
work
COPYRIGHT ACT © 2010
Hints and tips
 Best Practices
 Install reporting on an independent server
 Install ONLY the TSM agent on a TSM server. Do not install
any other reporting components on an existing or new
TSM server installation.
 More than 10 TSM servers being monitored on a single ITM
server may cause performance and storage space issues
 Sizing, Scalability and performance tuning
 Performance and memory-out issues may occur on large
TSM servers monitored
COPYRIGHT ACT © 2010
ITM Connectivity implemented for TSM
Reporting
TEP Browser
Java WebStart
TEP Client
1920/tcp
15001/tcp
DB2 or MS SQL TEPS
Database
ODBC or native
connected
TEPS
S&P
1918/tcp
Internal TEMS
Database
Hub TEMS
WPA
1918/tcp
6014/tcp
DB2, MS SQL or
Oracle Warhouse
Database
ODBC or JDBC
connected
Reporting Server
Windows, Linux or AIX
(all on one)
Legend:
OS Agent
TSM Agent
TSM Server
29
COPYRIGHT ACT © 2010
IP.PIPE
WPA
TSM Java API
Other TCP
INTEGRATION OF TSM 6.X
AGENT INTO IBM TIVOLI
MONITORING
COPYRIGHT ACT © 2010
Versions
 The TSM Monitoring Agent 6.x can be integrated into an
IBM Monitoring 6.2 and above environment
 Integration in:
 IBM Tivoli Monitoring 6.2 FixPack 1 and above.
 IBM Tivoli Monitoring 6.21 and above.
 IBM Tivoli Monitoring 6.22 and above
 You need the Application Support Files for TSM 6.x
Monitoring Agent and the Agent Code.
COPYRIGHT ACT © 2010
TSM Reporting Install Images
 The TSM Monitoring agent is included in the download
package from Passport Advantage.
Description
Windows Installation Image for TSM Monitoring & Reporting
Linux 32 Bit Installation Image for TSM Monitoring & Reporting
Linux 64 Bit Installation Image for TSM Monitoring & Reporting
AIX 32/64 Bit Installation Image for TSM Monitoring & Reporting
(Monitoring Server)
AIX 32/64 Bit Installation Image for TSM Monitoring & Reporting
(Agent)
 These images contain the Monitoring, Reporting and
Console components for the monitoring solution.
 You have to extract the Agent from the given file sets if
you wish to use the Agent only in a given ITM
environment.
COPYRIGHT ACT © 2010
Extracting the TSM 6.1 Agent
 The following tree shows the main components from this
image:
+---COI
\ +---DeploymentSteps
|
+---DB2_9.1
|
+---eWAS
|
+---ISC
|
+---ITM_6.2
|
+---TSM_AdminCenter
\
+---TSM_Agent
 To use the TSM Agent for the ITM environment you have
to copy the code into a temporary directory:
 Change directory to
- .\COI\DeploymentSteps\TSM_Agent\FILES (Windows)
- ./COI/DeploymentSteps/TSM_Agent/FILES (AIX/Linux)
 Copy all files and directories from this path into a
temporary directory.
COPYRIGHT ACT © 2010
Adding Application Support
TEP
KSK
TEPS
KSK
Hub TEMS Remote TEMS
KSK
KSK
 Application Support must applied to:




Hub TEMS
Remote TEMS
TEPS
TEP Client
COPYRIGHT ACT © 2010
TEMA
Adding Application Support –
Unix/Linux
 Run install.sh on Unix/Linux Systems where TEMS or TEPS is
installed.
Product packages are available for this operating system and component support categories:
1)
2)
3)
4)
5)
6)
IBM Tivoli Monitoring components for this operating system
Tivoli Enterprise Portal Browser Client support
Tivoli Enterprise Portal Desktop Client support
Tivoli Enterprise Portal Server support
Tivoli Enterprise Monitoring Server support
Other operating systems
Type the number or type "q" to quit selection
[ number "1" or "IBM Tivoli Monitoring components for this operating system" is default ]:
 You must choose 5 on TEMS or 2,3,4 on TEPS. If you have
an all-in-one system you should choose 2,3,4,5.
 To seed the Application Support on TEMS run:
 Itmcmd support –t <TEMS> sk
 Itmcmd manage
COPYRIGHT ACT © 2010
Adding Application Support –
Windows
 Run setup.exe
COPYRIGHT ACT © 2010
Local Agent Installation
 Windows Installation
 Walk to the directory where the TSM Agent Code is stored.
 Change into the WINDOWS directory and run the
“setup.exe” command.
 During the installation you must choose the Agent and the
connection configuration to the ITM infrastructure Server
(TEMS).
 Configure the connections to the TSM Server you must
open the “Manage Tivoli Enterprise Monitoring Services”
console.
COPYRIGHT ACT © 2010
Local Agent Installation
COPYRIGHT ACT © 2010
Local Agent Installation
 Unix/Linux Installation
 Walk to the directory where the TSM Agent Code is stored.
 Run the “install.sh” script.
 Configure Agent with “Manage Tivoli Enterprise Monitoring
Services” or “/opt/IBM/ITM/bin/itmcmd config –A sk”.
./itmcmd config -A -o testtsm sk
Agent configuration started...
Enter instance name (default is: ): testtsm
Edit "Monitoring Agent for Tivoli Storage Manager" settings? [ 1=Yes, 2=No ]
(default is: 1):
Edit 'TSM Server Connection Information' settings? [ 1=Yes, 2=No ] (default is: 1):
Server Address (default is: ): testtsm
Port Number (default is: 1500):
TSM Administrator (default is: ): Admin
TSM Administrator Password (default is: ):
Type password:
Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1):
TEMS Host Name (Default is: tsmreport):
COPYRIGHT ACT © 2010
Prepare Remote Deployment
 To prepare your environment for a remote deployment
of the TSM Monitoring agent you must add the agent
bundle to your agent depot.
 At first you have to login to the HUB TEMS with the
command line interface using:
- /opt/IBM/ITM/bin/tacmd login -s <HUB hostname> -u
<username> -p <password> -t 1440
 To add the bundle run the following command:
- /opt/IBM/ITM/bin/tacmd addbundles -i
/mnt/TSM_Agent/FILES/unix/ -t sk
 Hint: You should add the bundle to all TEMS depots in
your environment.
 Now you will be able to deploy your agent remotely
over TEPS or CLI.
COPYRIGHT ACT © 2010
?
Kontakt:
Christian Michaelski
[email protected]
41
COPYRIGHT ACT © 2010