TNSQM v4.1.2 AIX SystemAdminstrationGuidev1.3

Netcool Service Quality Manager
Version 4.1.2
IBM
AIX System Administration Guide
SC23-9845-00
Note: Before using this information and the product it supports, read the information in Notices on page 105.
This edition applies to version 4, release 1, modification 2 of IBM Tivoli Netcool Service Quality Manager (Product Number 5724-V48) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2007, 2009. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE
Table of contents
1 About this documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required skills and knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guide conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Service Quality Manager online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing publications online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 2 3 4 4
2 Preinstallation checks and Service Quality Manager hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Checking customer documentation versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Service Quality Manager hardware and software requirements . . . . . . . . . . . . . . . . . . . . 5 System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Server installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Server hardware and software requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Software products (server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Client hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 File systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Service Quality Manager file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Customer Experience Manager file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3 Database administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User access and roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and stopping a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting database listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking database listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping database listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking database tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ARCHIVELOG mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ARCHIVELOG mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating ARCHIVELOG settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling ARCHIVELOG mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling ARCHIVELOG mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hourly aggregation of KQI historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daily aggregation of KQI historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weekly aggregation of KQI historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monthly aggregation of KQI historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analyzing Service Quality Manager schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 19 19 20 20 20 20 20 20 21 21 21 22 22 23 23 24 24 24 24 24 25 25
Updated: 2009-06-23
SAG Page iii
Partition maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Partition maintenance command line tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Limiting the scope of the partition maintenance command line interface tool . . . . . . . 26 Partition maintenance command line interface tasks . . . . . . . . . . . . . . . . . . . . . . . . . 27 List parameters option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Show parameters option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Update parameters option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 List partitions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Add partitions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Delete partitions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Pin partitions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Unpin partitions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 List pinned partitions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 List sessions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Update sessions option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 List spaces option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Show logs option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Show errors option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Show status option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4 Service Quality Manager user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Introduction to user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Default users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Adding a new user to Service Quality Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Default password rules for Service Quality Manager users . . . . . . . . . . . . . . . . . . . . . 38 Modifying a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Deleting a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configuring usage notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Configuring the user management application time out. . . . . . . . . . . . . . . . . . . . . . . . . . 41 Starting and stopping Service Quality Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Tivoli Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Starting Tivoli Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Checking Tivoli Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Stopping Tivoli Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 WebSphere Message Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Starting WebSphere Message Broker instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Checking WebSphere Message Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Stopping WebSphere Message Broker instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Service Quality Manager web portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Starting the Service Quality Manager web portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Checking Service Quality Manager web portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Stopping Service Quality Manager web portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Service Quality Manager process monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Starting Service Quality Manager process monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Checking Service Quality Manager process monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Stopping Service Quality Manager process monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Service Quality Manager process manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Starting the Service Quality Manager process manager . . . . . . . . . . . . . . . . . . . . . . . 46
SAG Page iv
Checking Service Quality Manager process manager . . . . . . . . . . . . . . . . . . . . . . . . Stopping the Service Quality Manager process manager . . . . . . . . . . . . . . . . . . . . . SOCKS proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting SOCKS proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking SOCKS proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping SOCKS proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Quality Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Service Quality Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping Service Quality Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the status of Service Quality Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop and start parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Quality Manager cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the crontab file (saserver) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the crontab file (root) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of cron scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping and starting cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locking and unlocking user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing passwords as Service Quality Manager administrator . . . . . . . . . . . . . . . . Changing passwords as a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Password policy configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the password policy in the Service Quality Manager server . . . . . . . . . . . . Changing the global password policy in the Tivoli Directory server . . . . . . . . . . . . . . SSL configuration and certificate management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating an SSL configuration for Service Quality Manager . . . . . . . . . . . . . . . . . Certificate management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Quality Manager site certification authority (The default method) . . . . . . . . . Configuring Tomcat server SSL keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Service Quality Manager client keystore . . . . . . . . . . . . . . . . . . . . . . Configuring the Tivoli Directory Server SSL database . . . . . . . . . . . . . . . . . . . . . . . . Configuring the certification authority certificate in the client web browser . . . . . . . . Backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup and restore (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup requirements and schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring from backup (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tape carriage control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rewinding a tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving through a tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the recovery catalog database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the recovery catalog schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the recovery catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering a database with the recovery catalog . . . . . . . . . . . . . . . . . . . . . . . . . . .
46 47 47 47 47 47 47 48 48 48 48 53 53 53 54 54 55 55 57 57 57 60 60 61 63 63 63 67 67 67 68 69 69 70 71 73 73 73 73 74 74 74 75 75 76 76 77 77 78
Updated: 2009-06-23
SAG Page v
Database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Restoring a database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Restoring when control files are not lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Restoring when control files are lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Errors during recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 9 System logging and tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 System logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Service Quality Manager application logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Adapter logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Oracle logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Operating system logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 FTP logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Installation logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 TOMCAT logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 IBM WebSphere Application Server logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 IBM Tivoli Directory Server logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Service Quality Manager log levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Logging tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Checking logging or debug levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Listing logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Changing logging or debug Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Changing logging levels on process loggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Service Quality Manager alarm tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Listing active alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Exporting active alarms in CSV, XML or HTML formats . . . . . . . . . . . . . . . . . . . . . . . 90 Listing registered alarm logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Exporting from an alarm log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Exporting from an alarm log to CSV, XML or HTML formats . . . . . . . . . . . . . . . . . . . . 91 Exports and files written to the system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Service Quality Manager process manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Preference management feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Service Quality Manager summarization tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Using the summaryadm script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Use case: Command line interface summarization backfill scenario . . . . . . . . . . . . . . 95
10 Integration with IBM Tivoli Netcool OMNIbus and IBM Tivoli Webtop . . . . . . . . . . . . . . 97 Preparing for integration with Tivoli Netcool OMNIbus . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 TRAPD rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Integrating Service Quality Manager with Tivoli Netcool OMNIbus . . . . . . . . . . . . . . . . . 98 Appendix A: Storage configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Additional reading material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Appendix B: Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Appendix C: Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
SAG Page vi

About this documentation
1
1.1
The IBM Tivoli Netcool Service Quality Manager AIX System Administration Guide provides an overview of the Service Quality Manager system and procedures for completing various administration tasks.
Audience
This guide is intended for engineers who have responsibility for the administration of IBM Tivoli Netcool Service Quality Manager v4.1.2.
1.2
Required skills and knowledge

IT (Information Technology) principles IBM AIX 5L Oracle 10g Graphical user interfaces Microsoft Windows operating systems UNIX operating systems
This guide assumes you are familiar with:
Note: Service Quality Manager administrators must not, without prior consultation and agreement from IBM, make any changes to the database schema or database instance configuration. Changes to the database schema or instance configuration may result in corruption of data and failure of the Service Quality Manager system. This applies to all releases of Service Quality Manager using all versions of interfaces.
Updated: 2009-06-23
SAG Page 1

1.3
Guide conventions
Table 1: General guide conventions
Description
This guide uses the typographical conventions shown in the table below:
Format Examples
ALL UPPERCASE Link Bold SMALL CAPS
GPS NULL MYWEBSERVER See www.ibm.com Note: The busy hour determiner is... The STORED SQL dialog box... ...click VIEW... In the main GUI window, select the FILE menu, point to NEW, and then select TRAFFIC TEMPLATE. A busy hour is... A web server must be installed... See the User Guide
./wminstall $ cd /cdrom/cdrom0 /xml/dict addmsc.sh core.spec Type OK to continue. [root] # pkginfo | grep -i perl system Perl5 On-Line Manual Pages system Perl 5.005_03 (POD Documentation) system Perl 5.005_03 # cd <oracle_setup>
Acronyms, device names, logical operators, registry keys, and some data structures. For links within a document or to the Internet. Heading text for Notes, Tips, and Warnings. Any text that appears on the GUI.
Italic
New terms, emphasis, and book titles. Code text, command line text, paths, scripts, and file names. Text written in the body of a paragraph that the user is expected to enter. For contrast in a code example to show lines the user is expected to enter.
Monospace
Monospace Bold
<Monospace italics>
Used in code examples: commandline variables that you replace with a real name or value. These are always marked with arrow brackets. Used in code examples: indicates options.
[square bracket]
log-archiver.sh
[-i][-w][-t]
SAG Page 2

1.4
User publications
The user publications below are provided with the Service Quality Manager software as Adobe PDFs (Portable Document Format). Online help is provided in HTML (Hypertext Markup Language) format.
Table 2:
Document
Service Quality Manager user documentation

Description
Release Notes
Provides information on the Service Quality Manager release contents, platform requirements, installation and upgrade procedures, and known issues. Describes SLA (Service Level Agreements) provisioning (parties, SLAs, and SLA templates applications) and Service Quality manager provisioning (services resources, KQI (Key Quality Indicator) models and service models applications) in Service Quality Manager. Describes monitoring (SLA monitor, KQI analyzer, alarm monitor, audit manager and SLA webview applications) in Service Quality Manager. Describes how to use and monitor the Customer Experience Manager feature in Service Quality Manager. Provides information for provisioning the Customer Experience Manager system. Describes how to install the Service Quality Manager server system on Solaris. Describes how to install the Service Quality Manager client. Describes how to install the Service Quality Manager server system on AIX. Provides an overview of the Solaris Service Quality Manager administrative tasks including instructions on how to complete the tasks: Starting and stopping Service Quality Manager. Running batch processes such as archiving trace files and log files. Backing up and restoring the system.
Configuration Guide
Monitoring Guide
Customer Experience Manager Monitoring Guide Customer Experience Manager Provisioning Guide Solaris Server Installation Guide Client Installation Guide AIX Server Installation Guide Solaris System Administration Guide
AIX System Administration Guide
Provides an overview of the AIX Service Quality Manager administrative tasks including instructions on how to complete the tasks: Starting and stopping Service Quality Manager. Running batch processes such as archiving trace files and log files. Backing up and restoring the system.
Updated: 2009-06-23
SAG Page 3

Table 2: Service Quality Manager user documentation (Continued)

Document Description
Upgrade Guide Business Objects Installation and Configuration Guide Service Quality Manager Core Online Help Customer Experience Manager Online Help SLA Webview Online Help
Details how to upgrade from one Service Quality Manager version to another. Provides information on the steps required to install and configure the BusinessObjects server and client for use with Service Quality Manager. Provides information and procedures for using Service Quality Manager client applications. Describes how to use and monitor the Customer Experience Manager feature in Service Quality Manager. Describes how to use and monitor the SLA Webview feature in Service Quality Manager.
1.4.1
Viewing the Service Quality Manager online help
You can view Service Quality Manager online help by clicking the ONLINE HELP tab on the Service Quality Manager client. This tab is accessible from all Service Quality Manager applications on the Service Quality Manager client. You can also access links for contextsensitive help.
1.4.2
Accessing publications online
You can view the Tivoli Network Management documentation on the Web by accessing the Tivoli Software Information Center at: http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/ index.jsp. To view the books of the Service Quality Manager library, click NETCOOL SERVICE QUALITY MANAGEMENT PRODUCTS.
SAG Page 4
IBM TIVOLI NETCOOL SERVICE QUALITY MANAGER AIX SYSTEM ADMINISTRATION GUIDE
Preinstallation checks and Service Quality Manager hardware and software requirements
2
2.1
Checking customer documentation versions
To view the latest versions of Tivoli Netcool Service Quality Manager customer documentation, please check the Tivoli Information Center by completing the following: 1. Access the Tivoli Information Center at: http://publib.boulder.ibm.com/infocenter/tivihelp/ v8r1/index.jsp. 2. To view the books of the Service Quality Manager library, click NETCOOL SERVICE QUALITY MANAGEMENT PRODUCTS.
2.2 Service Quality Manager hardware and software requirements

Ensure your environment can support the following requirements where applicable when installing Service Quality Manager or Customer Experience Manager: Multiple paths exist between the server and the SAN (Storage Area Network). Each card should be connected to each controller. Multipathing is enabled. Multipathing status is optimal. The logical block region-size is configured to be the size of the card cache. There is optimal stripe width on the SAN. Optimal cache size on the SAN. Optimal cache settings on the SAN. Note: Refer to Storage configuration on page 85 for additional reading material on storage configuration.
Updated: 2009-06-23
SAG Page 5
2.2.1
System overview
Network operators can use IBM Tivoli Netcool Service Quality Manager to manage the service quality delivered to their customers. Service Quality Manager must be installed on a highperformance and scalable AIX platform.
2.2.2
Additional information
To cater for different systems and scenarios, all possible installation options are detailed in this guide. Depending on your computer specification and configuration, some or all of the installation options can be displayed.
2.2.3
Server installation overview
Preparation Before installing the software, the following information is required for each server on which you are installing Service Quality Manager: Server IP address Server host name IP Address of the default router Netmask Domain Required software AIX 5L installation media Service Quality Manager 4.1.2 software installation and documentation Oracle 10g for AIX 5L Oracle 10g for Windows DVD BusinessObjects v6.5.1 (optional) BusinessObjects XI (optional)
2.2.4
Server hardware and software requirement
Note: All the procedures in this guide apply to the consolidated server unless stated otherwise. Minimum Service Quality Manager server hardware requirements The minimum hardware requirements for a Service Quality Manager server are: Four POWER 5, 5+ or higher processors 8 GB core memory Four 72 GB hard disks
SAG Page 6
Optical Drive - DVD ROM/R/RW The minimum hardware requirements for a BusinessObjects server are: 3 GHz Pentium III or equivalent processor 3 GB RAM 4 GB of available disk space Minimum Customer Experience Manager hardware requirements Note: The following table details an example Customer Experience Manager hardware specification, it details one possible configuration, all configurations will require these equivalent Customer Experience Manager hardware requirements.
Updated: 2009-06-23
SAG Page 7
Table 3:
Customer Experience Manager minimal hardware requirements

Type Quantity Notes
System element
IBM Power 550 Express Server
The basic specification for this machine contains two processors, detailed below. Eight core, 64 bit processor There are a variety of 4 GB options available for IBM P-series servers. Has either 2 GB or 4 GB cache, can take up to 16 fibre-channel disks of up to 300 GB each. Supports RAID 0, 1, 5 and 1+0., has two redundant controllers. There are a variety of options available for IBM P-series servers. Four of these disks should be dedicated to Oracle temporary tablespace, the remainder are for the operating system, logs and application files.
IBM POWER6 processor CPU HBA card Fibre-channel card
1 2
IBM DS4700
External storage 1
1 or 10 Gigabit Ethernet cards Internal SAS disks
Network cards
Internal storage 8
Main memory
RAM
64 GB
Service Quality Manager components The Service Quality Manager architecture is typically made up of five components, each with specific functions as follows: Application component - Consists of the Service Quality Manager software that is used to run Service Quality Manager core processes. Gateway component - Consists of Service Quality Manager software that mediates data from customer data sources and forwards it to the adapters. Database component - Consists of an Oracle database that Service Quality Manager uses to store data. Client component - Consists of Service Quality Manager client software installed on a client PC. Where applicable, the optional BusinessObjects client software is also installed on the client PC.
SAG Page 8
BusinessObjects reporting component (optional) - Consists of BusinessObjects server and client software that is used as a reporting tool for Service Quality Manager. Service Quality Manager installation structure Service Quality Manager components can be installed on a single server or distributed over several machines. A single Service Quality Manager server can house the application, gateway and database components (an all inclusive server) or these three components can be split over two or three servers. Note: The user must have access to all servers documented in the preceeding information to
install Service Quality Manager.
See the sample configuration in Appendix C: Service Quality Manager networking requirements.
2.2.5
Software products (server)
Note: The software products listed in the following table below must be installed on each server before installing Service Quality Manager. To install the Service Quality Manager system on a server with a UNIX operating system, the software products listed in the table below are required.
Table 4:
Product Version

Medium
AIX 5L unzip Must be pre installed.
5.3, OS level 5300-06 or later 5.51-1 or higher
Download this software from: http://www-03.ibm.com/systems/p/os/aix/index.html AIX Toolbox for Linux CD, or: Download this software from: http://www-03.ibm.com/systems/p/os/aix/linux/toolbox/ download.html
xlC RunTime Environment Must be pre installed.
9.0.0.2 or higher
xlC CD, or: Download this software from: http://www-1.ibm.com/support/docview.wss?rs=2239&context=SSJT9L&dc=D400&q1=xlc.rte.aix50&uid=swg24017 393&loc=en_US&cs=utf-8&lang=en The PTF contains two AIX version specific packages, choose the aix 50 package.
Updated: 2009-06-23
SAG Page 9
Table 4:
Product Version

Medium
Base Application Development math library Must be pre installed. Base Application Development profiling support Must be pre installed. Runtime for SMBFS Must be pre installed.
5.3.0.60 or higher AIX 5.3 installation media. This is the bos.adt.libm
package from the bos.adt fileset on CD 1. Insert and mount this CD. Use smitty install to install the fileset.
5.3.0.60 or higher AIX 5.3 installation media. This is the bos.adt.prof
package from the bos.adt fileset on CD 1. Insert and mount this CD. Use smitty install to install the fileset.
5.3.0.61 or higher AIX 5.3 installation media. This is the
and bos.cifs_fs.smit packages from the bos.cifs fileset on CD 1. Insert and mount this CD. Use smitty install to install the fileset.
bos.cifs_fs.rte
Base U.S. English language fileset Must be pre installed. Oracle Database Enterprise Edition
5.3.0.0 or higher
AIX 5.3 installation media. This is the

bos.loc.iso.en_US package from the bos.loc.iso
fileset on CD 1. Insert and mount this CD. Use smitty install to install the fileset.
10g, patch level: 10.2.0.4. Download this software from: http://www.oracle.com/technology/software/products/database/index.html Choose Oracle Database 10g Release 2 (10.2.0.1.0) for AIX5L. Download patches from: https://metalink.oracle.com/metalink/plsql/ f?p=200:101:6597563905604234225 This will bring the Oracle version to 10.2.0.4. (requires login ID/password)
IBM WebSphere Application Server
6.1.0.23
The WebSphere package is bundled with the Service Quality Manager product, it is one of the downloadable images or one of the CDs. See the entry for Service Quality Manager software installation and documentation at the end of this table.
Tivoli Directory Server
6.1
Download this software from: http://w3-103.ibm.com/software/xl/portal Login with username and password. Search for the product you want to install under the correct category, for example in this instance - Tivoli Directory Server. The download needed is IBM Tivoli Directory Server 6.1 Client-Server with entitlement, GSKit 7.0.3.30 (tar file) for AIX, Multilingual (C12UVML).
SAG Page 10
Table 4:
Product Version

Medium
DB2
9, Service Pack 2 Download this software from: http://w3-103.ibm.com/software/xl/portal Login with username and password. Search for the product you want to install under the correct category, for example in this instance - DB2. The download needed is IBM Tivoli Directory Server 6.1, DB2 v 9.1 Fix Pack 02 (tar file) for AIX, Multilingual (C12UXML).
Service Quality Man- 4.1.2 ager software installation and documentation
IBM Tivoli Netcool CD/DVD, or: Customers: Download the software from the IBM Passport
Advantage Web site: http://www.ibm.com/ software/howtobuy/passportadvantage/
Internal IBM team: Download the software from Xtreme Leverage http://w3103.ibm.com/software/xl/portal Search for TNSQMc (Tivoli Netcool Service Quality Management Center) 4.2.2 as Tivoli Netcool Service Quality Manager v4.1.2 is released as part of this center..
Note: Use the lslpp -l <fileset> command to check for the filesets for the products in Table 4. <fileset> denotes the various component packages for the products listed in Table 4. For additional information on these packages consult your system administrator.
2.2.6
Client hardware and software requirements
Minimum client hardware requirements The minimum hardware requirements for a client PC with a Windows operating system are: 1.5 Ghz Pentium III processor equivalent. 512 MB RAM. 300 MB RAM for the Service Quality Manager client. 3 GB of disk space must be available for the Service Quality Manager client software and optional software components. 500 MB of available disk space for the Service Quality Manager client software. 2.5 GB of available disk space for the optional BusinessObjects and Oracle software. The minimum peripheral requirements for the Service Quality Manager client and the optional BusinessObjects client are: One high-resolution 15-inch SVGA color monitor.
Updated: 2009-06-23
SAG Page 11
One 104-key, Windows-compatible keyboard. One two-button, Windows-compatible mouse. At least one 10 Base-T (10/100 Base-T recommended) network interface card. One accelerated SVGA (Super Video Graphics Adapter) card with at least 2 MB RAM. Client software requirements Adobe Flash Player v10.0.22 or higher is required. Note: It is your responsibility to ensure that the correct operating system is installed on the client PC before the Service Quality Manager client software can be installed. Software products (client) To install the Service Quality Manager system on a client PC, the software products listed in the table below are required.
Table 5:
Product
Software products (client PC)

Medium
Version
Windows operating system
Windows 2000 SP4, Windows XP and Windows 2003 10.2.0.4
CD-ROM (The customer must supply this software.)
Oracle database client (optional)
Download this software from:

http://www.oracle.com/technology/software/products/ database/index.html
Software products (optional BusinessObjects server) To install the optional BusinessObjects server software on a server with a Windows operating system, the software products listed in the table below are required.
Table 6:
Product
Software products (optional BusinessObjects server)

Version Medium
Windows operating system Oracle Database client
Windows 2003 or XP 10.2.0.4
CD-ROM (The customer must supply this
software)
http://www.oracle.com/technology/software/ products/database/index.html BusinessObjects server (optional) 6.5.1 BusinessObjects server XI 3 CD-ROMs or http://www.businessobjects.com 5 CD-ROMs or http://www.businessobjects.com
SAG Page 12
Software products (optional BusinessObjects client) To install the optional BusinessObjects client software on a client PC, the software products listed in the table below are required.
Table 7:
Product
Software products (BusinessObjects client)

Version Medium
Windows operating system Oracle database client
Windows XP or Windows 2003 10.2.0.4
CD-ROM (supplied by Cus-
tomer)

http://www.oracle.com/technology/software/products/ database/index.html
BusinessObjects client BusinessObjects client
6.5.1 XI
3 CD-ROMs or http:// www.businessobjects.com 4 CD-ROMs or http:// www.businessobjects.com
Note: BusinessObjects client Software version 6.5.1 is not supported on Windows 2000.
2.3
2.3.1
File systems
Service Quality Manager file systems
The following file systems are required for the installation of Service Quality Manager. Specific third-party software is installed in each file system. Symbolic links can be used so that the file systems in the following table are displayed. Note: An example file system is shown in the table below. The system is a IBM pSeries p52A with four 72GB disks. The size column records the size of the partition created during installation. If a Technical Architecture Specification is provided for the deployment refer to this specification for file system sizing information otherwise use the defaults set out in the table below.
Note: A volume group is a separate group of disks under AIX LVM (Logical Volume Manager).
Updated: 2009-06-23
SAG Page 13
Warning: You are required to create all the file systems as described in the table below because the Service Quality Manager installation scripts and software will not not function correctly without them.
SAG Page 14
Table 8:
File system Minimum size Software
File systems
Disk location Server type
/ swap /usr /var /opt /tmp /home /appl
2 GB 8 GB 3 GB 1 GB 2 GB 1 GB 2 GB 30 GB
Operating system Operating system Operating system Operating system IBM TDS and DB2 Operating system User home accounts Oracle, WAS and Service Quality Manager Service Quality Manager cached data Download data 1
rootvg rootvg rootvg rootvg rootvg rootvg AIX LVM volume group 1 AIX LVM volume group 1 AIX LVM volume group 1
All servers All servers All servers All servers application server All servers All servers All servers
/data/cache
8 GB
Application, gateway and consolidated servers Application, gateway and consolidated servers Application, gateway and consolidated servers Application, gateway and consolidated servers Application, gateway and consolidated servers Database server Database server
/data/ download1
8 GB
AIX LVM volume group 1
/data/ download2
8 GB
Download data 2
/data/ trace_archiv e1 /data/ trace_log1
8 GB
Trace archive location
8 GB
Trace log location
/oralogs1 /oralogs2
10 GB 10 GB
Oracle redo log location 1 Oracle redo log location 2
AIX LVM volume group 2 AIX LVM volume group 2
Updated: 2009-06-23
SAG Page 15
File system
Minimum size
Software
Disk location
Server type
/oradump /oratemp /oradata01 /oradata02 /oradata03 /oradata04
4 GB 20 GB 34 GB 34 GB 34 GB 34 GB
Oracle dump location Oracle temporary tablespace Oracle storage location 1 Oracle storage location 2 Oracle storage location 3 Oracle storage location 4
AIX LVM volume group 1 AIX LVM volume group 1 AIX LVM volume group 1 AIX LVM volume group 1 AIX LVM volume group 1 AIX LVM volume group 1
Database server Database server Database server Database server Database server Database server
2.3.2
Customer Experience Manager file systems
The following file systems are required for the installation of Customer Experience Manager. Specific third-party software is installed in each file system. Symbolic links can be used so that the file systems in the following table are displayed. Note: An example file system is shown in the table below.
Note: A volume group is a separate group of disks under AIX LVM.
Warning: You are required to create all the file systems as described in the table below because the Service Quality Manager installation scripts and software will not not function correctly without them.
SAG Page 16
Table 9:
File system Minimum size Software
File systems
Disk location Server type
/ swap /usr /var /opt
2 GB 8 GB 3 GB 1 GB 2 GB
Operating system Operating system Operating system Operating system IBM Tivoli Directory Server and DB2 Operating system User home accounts Oracle, WebSphere Application Server and Service Quality Manager Service Quality Manager cached data Download data 1
rootvg rootvg rootvg rootvg rootvg
All servers All servers All servers All servers Application server All servers All servers All servers
/tmp /home /appl
1 GB 2 GB 30 GB
rootvg AIX LVM volume group 1 AIX LVM volume group 1
/data/cache
8 GB
Application, gateway and consolidated servers Application, gateway and consolidated servers Application, gateway and consolidated servers Application, gateway and consolidated servers Application, gateway and consolidated servers Database server
/data/ download1
8 GB
/data/ download2
8 GB
Download data 2
/data/ trace_archiv e1 /data/ trace_log1
8 GB
Trace archive location
8 GB
Trace log location
/oralogs1
40 GB
Oracle redo log location 1
Updated: 2009-06-23
SAG Page 17
File system
Minimum size
Software
Disk location
Server type
/oralogs2 /oradump /oratemp /oradata01
40 GB 300 GB 200 GB 300 GB
Oracle redo log location 2 Oracle backup location Oracle temporary tablespace Oracle storage location 1 Oracle storage location 2 Oracle storage location 3 Oracle storage location 4
AIX LVM volume group 2 AIX LVM volume group 1 AIX LVM volume group 1 External storage (Hardware RAID array) External storage (Hardware RAID array) External storage (Hardware RAID array) External storage (Hardware RAID array)
Database server Database server Database server Database server
/oradata02
300 GB
Database server
/oradata03
300 GB
Database server
/oradata04
300 GB
Database server
SAG Page 18

Database administration
3
3.1
Depending on the type of configuration deployed, several databases are created by Oracle during the installation of the Service Quality Manager product. This chapter describes these databases and details the common tasks required to administer each database.
Databases
sadb repos
There are currently two main databases used by Service Quality Manager:
sadb database The Service Quality Manager database, sadb, is made up of both an Online Transaction Processing (OLAP) system and a data warehouse/mart system. The OLAP side provides support for high data insertion rates and the Data Warehouse provides high performance reporting and retrieval capabilities. repos database The repos database is used by BusinessObjects for reporting on historical data.
3.2
User access and roles
Only certain users are allowed to access the Service Quality Manager databases. Table 10 details which users can access the various databases and their associated roles.
Table 10:
Database
sadb sadb
Access to databases and roles

Privileges
User
saowner saserver
Role
sa_server_role and sa_usermgt_role
System Privileges (DBA, RESOURCES) INSERT,UPDATE,DELETE,SELECT, CREATE SESSION, CREATE USER, ALTER USER, DROP USER
Updated: 2009-06-23
SAG Page 19

Table 10:
Database
sadb
Access to databases and roles (Continued)

Role Privileges
User
sadefault
sa_readonly_role
SELECT on all Service Quality Manager tables except admin tables (AUTOPART, ADM_LOG), CREATE SESSION, CREATE SYNONYM INSERT,UPDATE,DELETE,SELECT, CREATE SESSION, CREATE SYNONYM System Privileges (DBA, RESOURCES)
sadb
ops$saserver sa_server_role and
sa_usermgt_role repos
repuser
3.3
Starting and stopping a database
To start and stop individual databases, complete the sections below:
3.3.1
Starting database listener

To start the database listener, execute the command below as user oracle:
$ lsnrctl start
3.3.2
Checking database listener

To check the listener is started for a database, execute the command below as user oracle:
$ lsnrctl status
3.3.3
Stopping database listener

To stop the database listener, execute the command below as user oracle:
$ lsnrctl stop
3.3.4
Starting a database
To start up a database, execute the commands below as user oracle:
$ export ORACLE_SID=<Oracle SID> $ sqlplus /nolog $ connect / as sysdba SQL> startup SQL> exit
where <Oracle SID> is the default database name to connect to.
3.3.5
Stopping a database
To shut down a database, execute the commands below as user oracle:
$ export ORACLE_SID=<Oracle SID> $ sqlplus /nolog
SAG Page 20

$ connect / as sysdba SQL> shutdown SQL> exit
where <Oracle SID> is the default database name to connect to.
3.3.6
Checking database tables
To check the database tables or the content of the tables in each database, complete the following steps: 1. Log in as OS user saserver and execute the commands:
$ sqlplus "saserver/<saserverpasswd>@<MYDB>" <MYDB>
is the name of the database
<saserverpasswd> is the password for the saserver user. 2. To view the tables within the database associated with the logged in user, execute the following commands:
SQL> select table_name from user_tables;
3. To describe the structure of a table, execute the following command:

SQL> desc SA_KQI_SIMPLEMODEL;
4. To get the total number of rows in a table, execute the following command:
SQL> select count(*) from SA_KQI_SIMPLEMODEL;
5. To view the contents of a table, execute the following command:

SQL> select * from SA_KQI_SIMPLEMODEL;
3.4
ARCHIVELOG mode
Based on Oracle best practices, enable the ARCHIVELOG mode for databases to maintain recoverability at a high level and to archive the redo logs so that they are not overwritten. By default, both databases in the Service Quality Manager application run in the NOARCHIVELOG mode. Implement and test the archivelog file maintenance procedure according to backup technologies and policies at your site. Then switch both databases to ARCHIVELOG mode with regular database and archivelog files backups. This section describes how to check if the database is in ARCHIVELOG mode and how to enable and disable ARCHIVELOG mode.
3.4.1
Checking ARCHIVELOG mode
To check ARCHIVELOG mode status, complete the following steps: 1. Log in as user oracle and execute the following commands:
Updated: 2009-06-23
SAG Page 21

$ export ORACLE_SID=<MYDB>
where <MYDB> is the name of the database

$ sqlplus /nolog SQL> connect / as sysdba
2. To check the ARCHIVELOG mode status, execute the following SQL command:
SQL> archive log list;
If the database is in ARCHIVELOG mode, the output below is returned:

Database log mode Automatic archival Archive Mode Enabled
If the database is not in ARCHIVELOG mode, the output below is returned:

Database log mode Automatic archival No Archive Mode Disabled
3.4.2
Updating ARCHIVELOG settings
Update the log destination directory to ensure it has sufficient space to store the archive log files. The recommended location is /oradump/<MYDB>. Ensure the log destination directory exists prior to setting it. Ensure the oracle user has full permission to access this log destination directory. Caution!: The location of archived redo log files should not share the same device/LUN with online redo log files that by default are located in /oralogs[1,2] mount points. Update the target archive location by completing the following steps: 1. Log in as user oracle and execute the following commands:

2. To change the archive log destination, execute the following SQL command:
SQL> alter system set log_archive_dest='/oradump/<MYDB>' scope=both;
3.4.3
Enabling ARCHIVELOG mode

To enable ARCHIVELOG mode, complete the following steps:
1. Log in as user oracle and execute the following commands:


SAG Page 22

2. To enable ARCHIVELOG mode status, execute the following SQL commands:

SQL> shutdown immediate SQL> startup mount SQL> alter database archivelog; SQL> alter database open;
3. To check the ARCHIVELOG mode , execute the following SQL command:

SQL> archive log list; Database log mode Automatic archival Archive destination Oldest online log sequence Current log sequence Archive Mode enabled /oradump/<MYDB> 7 9
The database is now in ARCHIVELOG mode.
3.4.4
Disabling ARCHIVELOG mode

To disable ARCHIVELOG mode status, complete the following steps:
1. Log in as user oracle and execute the following commands: $ export ORACLE_SID=<MYDB> where <MYDB> is the name of the database
2. To disable ARCHIVELOG mode status, execute the following SQL commands:

SQL> shutdown immediate SQL> startup mount SQL> alter database noarchivelog; SQL> alter database open;
3. To check the ARCHIVELOG mode status, execute the following SQL command:
SQL> archive log list; Database log mode Automatic archival Archive destination Oldest online log sequence Current log sequence No Archive Mode Disabled /oradump/<MYDB> 7 9
The database is now in NOARCHIVELOG mode.
3.5
Database jobs
These sections detail the jobs that are set up in Oracle to control the movement and maintenance of data in the database.
Updated: 2009-06-23
SAG Page 23

To see a list of scheduled Oracle jobs and associated statistics such as last occurrence, next occurrence, and execution time etcetera, execute the following commands as user saserver. To see a list of scheduled Oracle jobs and associated statistics, complete the following step: Execute the commands below as OS user saserver.
$ sqlplus "saserver/<saserverpasswd>@<MYDB>" <MYDB>
is the name of the database is the password for the saserver user.
<saserverpasswd>
SQL > set serveroutput on SQL > execute utl_task_pkg.print_info;
3.5.1
Hourly aggregation of KQI historical data
This Oracle job is executed every hour to aggregate data in the SA_HST_KQIVALUE table into the SA_HST_KQIVHOURAGG table.
KQI_ADMIN_PKG.HST_KQIV_HOURLYSUMMARY;
3.5.2
Daily aggregation of KQI historical data
This Oracle job is executed once a day to aggregate data in the SA_HST_KQIVHOURAGG table into the SA_HST_KQIVDAYAGG table.
KQI_ADMIN_PKG.HST_KQIV_DAILYSUMMARY;
3.5.3
Weekly aggregation of KQI historical data
This Oracle job is executed once a week to aggregate data in the SA_HST_KQIVHOURAGG table into the SA_HST_KQIVWEEKAGG table.
KQI_ADMIN_PKG.HST_KQIV_WEEKLYSUMMARY;
3.5.4
Monthly aggregation of KQI historical data
This Oracle job is executed once a month to aggregate data in the SA_HST_KQIVHOURAGG table into the SA_HST_KQIVMONTHAGG table.
KQI_ADMIN_PKG.HST_KQIV_MONTHLYSUMMARY;
3.5.5
Analyzing Service Quality Manager schema
The Oracle procedure below is executed once a day to analyze the Service Quality Manager schema that is defined as stale, that is, over 10% activity on a table.
PROC_ANALYZE_STALE('SASERVER');
SAG Page 24

3.5.6
Data maintenance
The Oracle jobs below are used to maintain data in the database by adding and removing table partitions and deleting data over set cut-off points. The table, PART_TABLES, contains a list of the tables that are managed. The PART_TABLES.DATA_RETENTION column contains the number of periods for which data is kept. PART_MAINT.MAINTAINMINLY; - maintains quarter-an-hour partitions. PART_MAINT.MAINTAINDAILY; - maintain daily partitions. PART_MAINT.MAINTAINWEEKLY; - maintain weekly partitions. PART_MAINT.MAINTAINMONTHLY; - maintain monthly partitions. DATA_ADMIN_PKG.DELETE_ROWS;
3.6
Depending on the type of configuration deployed, several Oracle databases are created by the application installer during the installation of the Service Quality Manager product. This section describes these databases and details the common tasks required to administer each database. sadb database The Service Quality Manager database, sadb, is made up of both an Online Transaction Processing (OLTP) system and a data warehouse or data mart system. The OLTP side provides support for high rate data loading and the Data Warehouse provides high performance reporting and retrieval capabilities.
3.6.1
Partition maintenance
Partition maintenance is a system maintenance job that is responsible for the creation, deletion and optimization of date range partitioned tables. It enables a seamless process of creating, deleting and analyzing partitions without impacting the performance of the system. The partition maintenance job deals with the adding of partitions to ensure that sufficient partitions exist in the future, and the purging of old data from the system. The addition and deletion of data is based on configurable data retention settings within the partition maintenance process. As well as creating and deleting data, the partition maintenance process helps to optimize database performance by analyzing tables and gathering partition level statistics.
Updated: 2009-06-23
SAG Page 25

Partitions are created based on the parameters defined in the partition maintenance table, PART_TABLES. Table 11 describes the different database parameters in PART_TABLES. Table 11: Database parameters in PART_TABLES
Parameter Description
TABLESPACE_NAME The tablespace where the partitions are stored. PERIOD DATA RETENTION PAST RETENTION The partitioning periodfor example, D(aily), W(eekly) or M(onthly). The number of partitions that will be kept in the past. The minimum number of partitions that are automatically created in the past.
FUTURE RETENTION The minimum number of partitions that are automatically created in the future. NEED_MOVE NEED_EXPORT NEED_PURGE Specific to Index Organized Tables and is not implemented in Service Quality Manager. Not implemented in Service Quality Manager. Controls the dropping (or purging) of partitions when they are outside of the data retention period. Set to Y by default. If set to N, partitions will not be dropped. Controls the analyzing of partitions during partition maintenance. Set to Y by default. Defines the days of week when the table is analyzed. Position is the day of a week starting from Monday. 0 - do not analyze, 1 - analyze table. Format - xxxxxxx, for example, 1010101 - translates to analyzing the table every second day.
NEED_ANALYZE ANALYZE_MASK
3.6.2
Partition maintenance command line tool
Partition maintenance provides a command-line tool, part_admin, that allows you to manually run partition maintenance tasks and update partition maintenance settings, including retention settings. The part_admin script can be found in the location below and can be executed from any directory as user saserver:
$WMCROOT/bin/part_admin
3.6.3 Limiting the scope of the partition maintenance command line interface tool
The scope of the partition maintenance CLI can be limited by the parameters below:
[-type] [-subtype] [-tabtype] [-sdate] [-edate] [-filter] [-param] [-value]
SAG Page 26

Table 12:
Parameter
type subtype tabtype filter sdate edate param value
Parameters
Description
The type of table. A valid type is TABLE. Subtype associated with a specific type. Subtypes are associated with the main types. Examples include "traffic", "sumdaily". Table Type. Examples include "traffic", "sumdaily". Filter the output by table name. Examples include "SA_HST_KQIVALUE, %_AGG". Start Time, sdate format: yyyymmddhh24. End Time, edate format: yyyymmddhh24. Parameter for updating PM parameters. Examples include data_retention, tablespace_name. Value for update PM parameters and settings.
3.6.4
Partition maintenance command line interface tasks
Table 13 describes a list of tasks that can be completed using the part_admin script. Table 13: Completing tasks using the part_admin script
Parameter
listtypes
Description
The scope of the partition maintenance tasks can be limited by type. The listtypes option can be used to list the available types and subtypes on the system. A valid type is TABLE. Subtypes are associated with the main types. Examples include "TRAFFIC", "SUMDAILY", "SUMWEEKLY", "SUMMONTHLY", "<ADAPTER NAME>".
add delete pin
Add partitions. Scope can be limited using [-type]

[-subtype] [-tabtype] [-filter] [-sdate] [-edate].
Delete partitions. Scope can be limited using [-type] [-subtype] [-tabtype] [-filter] [-sdate] [-edate].
Pin partitions into the database to allow them to be maintained outside of the defined data retention periods. Scope can be limited using [-type] [-subtype] [-tabtype] [-filter]
[-sdate] [-edate].
unpin
Unpin partitions from the database to allow them to be dropped from the system when they are outside of the defined data retention periods. Scope can be limited using [-type] [-subtype] [-tabtype] [-filter] [-sdate] [-edate].
Display all configurable partition maintenance parameters.
showparams
Updated: 2009-06-23
SAG Page 27

Table 13:
Parameter
listparams updateparams
Completing tasks using the part_admin script
Description
Display all parameters settings. Scope can be limited using[-type]

[-subtype] [-tabtype].
Update specific partition maintenance settings. Scope can be limited using [-type] [-subtype] [-tabtype] [-filter] [-param] [-value]. List the partitions per table. Scope can be limited using [-type]
[-subtype] [-tabtype] [-filter] [-sdate] [-edate].
listpart listpinned
List the pinned partitions per table. Scope can be limited using
[-type] [-subtype] [-tabtype] [-filter] [-sdate] [-edate].
listsessions updatesessions listspace logs errors status help
Display the number of configurable parallel PM sessions. Update the number of configurable parallel PM sessions. Scope can be limited using [-value]. Display the current space settings per tablespace. Display the PM logs per job id. Scope can be limited using [-id]. Display the PM error logs per job id. Display the status of the active PM job. Help.
3.6.5
List parameters option
The list parameters option allows you to view the current parameters setting, limited by type/ subtype/table type or table name (filter). The syntax of the list parameters option is as follows:
part_admin listparams [-type] [-subtype] [-tabtype]
Example
part_admin listparams type table
Refer to Table 11 for a list of the different configurable database parameters.
3.6.6
Show parameters option
The show parameters option allows you to see all the configurable partition maintenance parameters. These parameters include data_retention, tablespace_name, and so on, and are configurable by table or group of tables through the partition maintenance CLI. The syntax of the show parameters option is as follows:
part_admin showparams
SAG Page 28

3.6.7
Update parameters option
The update parameters option allows you to update the current parameter setting. You can update the retention periods, the partitioning period, tablespace, and so on. The impact of these changes on the system should be considered before implementation on a production system. The updates to the parameters setting can be limited by type/subtype/table type or table name. The syntax of the update partitions option is as follows:
part_admin updateparams [-type] [-subtype] [-tabtype] [-param] [-value]
The example below shows how to update data_retention to 90 days for all traffic tables:
part_admin -updateparams type TABLE subtype traffic param data_retention -value 90
The example below shows how to update data_retention to 93 days for the SA_HST_KQIVALUE traffic table:
part_admin -updateparams -type TABLE data_retention -value 93 -filter "SA_HST_KQIVALUE" -param
3.6.8
List partitions option
Partitions can be listed by table_name to allow the user to see what partitions currently exist on the system. The list can be limited by type/subtype/table type/table name or time period. The syntax of the list partitions option is as follows:
part_admin -listpart [type] [subtype] [tabtype] [-filter] [sdate] [edate]
The example below shows the list limited by type TABLE and subtype traffic.
part_admin -listpart -type TABLE -subtype traffic
3.6.9
Add partitions option
The add partitions option allows you to add a partition to an individual table or a group of tables. Additional partitions are generally created to allow backloading of data into a table or if specific data is to be added to a particular table. Adding partitions outside of the retention period will also pin them into the database. The syntax of the add partitions option is as follows:
part_admin -add [type] [subtype] [tabtype] [-filter] -sdate -edate
The example below shows how to add partitions to all traffic tables from 01 January 2008 to 10 January 2008:
part_admin -add type TABLE subtype traffic -sdate 2008010100 -edate 2008011000
The example below will add partitions to the table SA_HST_KQIVALUE from 01 January 2008 to 10 January 2008:
Updated: 2009-06-23
SAG Page 29

part_admin -add filter SA_HST_KQIVALUE -sdate 2008010100 -edate 2008011000
3.6.10
Delete partitions option
Caution! Deleting partitions is not usually required on a regular basis. Scheduled partition maintenance jobs usually control this task. If you need to delete partitions using this procedure, ensure that you are deleting the correct partitions to prevent the loss of a large amount of important data. The delete partitions option allows you to drop a partition from an individual table or a group of tables. The syntax of the delete partitions option is as follows:
part_admin -delete [type] [subtype] [tabtype] [-filter] -sdate -edate
The example below shows how to delete partitions from all daily summary tables from 01 January 2008 to 10 January 2008:
part_admin -delete type TABLE subtype SUMDAILY -sdate 2008010100 -edate 2008011000
The example below shows how to delete partitions from all tables with a name like "%_AGG" from 01 January 2008 to 10 January 2008:
part_admin -delete filter %_AGG -sdate 2008010100 -edate 2008011000
The example below shows how to delete partitions from the SA_HST_KQIVALUE table from 01 January 2008 to 10 January 2008:
part_admin -delete -filter "SA_HST_KQIVALUE" -sdate 2008010100 -edate 2008011000
3.6.11
Pin partitions option
The pin partitions option allows you to pin partitions into the database so that they can be maintained outside the defined data retention periods. The syntax of the pin partitions option is as follows:
part_admin -pin [type] [subtype] [tabtype] [-filter] -sdate -edate
The example below shows how to pin partitions from all ATKTEST adapter tables from 01 January 2008 to 10 January 2008:
part_admin -pin type TABLE subtype atktest -sdate 2008010100 -edate 2008011000
3.6.12
Unpin partitions option
The unpin partitions option allows you to unpin partitions from a database so that they can be dropped when they are outside the defined data retention periods.
SAG Page 30

The syntax of the unpin partitions option is as follows:

part_admin -unpin [type] [subtype] [tabtype] [-filter] -sdate -edate
The example below shows how to unpin partitions from all ATKTEST adapter tables from 01 January 2008 to 10 January 2008:
part_admin -unpin type TABLE subtype atktest -sdate 2008010100 -edate 2008011000
3.6.13
List pinned partitions option
The list pinned partitions option allows you to list pinned partitions by table_name so you can see what partitions are currently pinned on the system. The list can be limited by type/subtype/ table type or table name. The syntax of the list pinned partitions option is as follows:
part_admin -listpinned [type] [subtype] [tabtype] [-filter]
3.6.14
List sessions option
The list sessions option allows you to view the current number of configurable parallel PM sessions. The syntax of the lists sessions option is as follows:
part_admin listsessions
3.6.15
Update sessions option
The update sessions option allows you to update the number of configurable parallel PM sessions. The number of parallel PM sessions is the number of parallel, subordinate sessions which can be run to create partitions. The number of sessions is dependent on the number of CPUs on a system. The impact of changing this setting should be considered before implementation on a production system. The syntax of the update sessions option is as follows:
part_admin updatesessions -value <session value>
3.6.16
List spaces option
The listspace option allows you to view the current space settings per tablespace. The syntax of the listspace option is as follows:
part_admin listspace
3.6.17
Show logs option
The logs option allows you to view the partition maintenance logs.
Updated: 2009-06-23
SAG Page 31

The syntax of the logs option is as follows:

part_admin logs [-id xxx/latest]
The -logs option provides a summary of all partition maintenance logs by logid along with a start time, end time and total duration. The -logs id xxx option provides detailed logs of all tasks that ran for a particular log. The -logs id latest option provides detailed logs of all tasks that ran for the latest logs.
3.6.18
Show errors option
The errors option allows you to view the partition maintenance error logs. These logs show all errors that have occurred in partition maintenance in the last 30 days, ordered by time. The syntax of the errors option is as follows:
part_admin errors
3.6.19
Show status option
The status option allows you to view the current status of the active partition maintenance job. The syntax of the status option is as follows:
part_admin status
SAG Page 32

Service Quality Manager user management
4
4.1

Introduction to user management
This chapter provides an overview of user management in Service Quality Manager. It describes how to: Create users. Assign user roles. Create passwords. Delete users. Configure usage notices. Configure application time-outs. The user management topics below are described: Default users on page 33. Adding a new user to Service Quality Manager on page 34. Default password rules for Service Quality Manager users on page 38. Modifying a user on page 38. Deleting a user on page 38. Configuring usage notices on page 40. Configuring the user management application time out on page 41.
4.2
Default users
Table 14:
User
root saserver
When Service Quality Manager is installed, the users detailed in Table 14 are created by default.
User details
Function Home directory
/ /export/home/saserver
UNIX administrator Service Quality Manager administrator
Updated: 2009-06-23
SAG Page 33

Table 14:
User
oracle
User details
Function
Home directory
/export/home/oracle
Oracle administrator
4.3
Adding a new user to Service Quality Manager
To add a new user, first install the Service Quality Manager Client and discover the Service Quality Manager Server. Follow the instructions in the Service Quality Manager Client Installation Guide to install the client and discover the server and then continue with the following steps. To add a new user to Service Quality Manager: 1. Select START=>ALL PROGRAMS=>IBM TIVOLI NETCOOL=>SERVICE QUALITY MANAGER=>APPLICATION DISCOVERER=>USERS AND PASSWORDS. OR In the APPLICATION DISCOVERER window, double-click USERS AND PASSWORDS. The USER MANAGEMENT login screen is displayed in your web browser. If configured, a USAGE NOTICE may be displayed on the login screen as shown in Figure 1. To configure a USAGE NOTICE for your users, refer to Configuring usage notices on page 40.
Figure 1: User management login screen with usage notice
Note: To prevent security warnings being displayed by the web browser when using the USER MANAGEMENT application, the Certification Authority that is used to sign the applications certificates must be known to the web browser. If the Certification Authority is not known to the web browser, a security alert is displayed. To stop the security alert being dis-
SAG Page 34

played, download and install the certificate using the link to the Certification Authorities Certificate displayed at the bottom of the USER MANAGEMENT login screen. 2. To create a new Service Quality Manager user, log in as the user management administrator useradm. 3. Contact the administrator to obtain the useradm password. 4. Enter the USERNAME useradm and the ADMINISTRATOR PASSWORD and click the ADMIN option. 5. Click LOGIN. The USER MANAGEMENT WELCOME screen is displayed as shown in Figure 2. Note: The USER MANAGEMENT application is configured so that an inactive session is terminated after a fixed period of time. If a session times out, users are forced to log into the USER MANAGEMENT application again. You can configure the default 30-minute time-out period. Refer to Configuring the user management application time out on page 41.
Figure 2: User management welcome screen (administrator)
6. Click the CREATE NEW USER link at the top of the screen. The USER MANAGEMENT NEW USER screen is displayed as shown in Figure 3. 7. In the NEW USER screen, enter the required detailsFIRST NAME, LAST NAME, USER ID and EMAIL.
Updated: 2009-06-23
SAG Page 35

Figure 3:
User management - entering user details
8. Select the appropriate check boxes to assign various roles to the user. Each of the roles is described in Table 15. At a minimum, select the ACCESS TO SERVICE QUALITY MANAGER role for each new user.
Table 15: New user roles
Role Gives the user access to
SLA Template Management
The SLA TEMPLATE application on the SLA PROVISIONING shortcut bar.
Customer ExperiThe Customer Experience Manager Cellular application from a web browser. ence Manager Analysis Customer Experience Manager SLO Monitor Customer Experience Manager SLO Manager BusinessObjects Report Management SLA Provisioning KQI Analyzing Party Management Customer Experience Manager Service Level Objective (SLO) Monitor application from a web browser. Customer Experience Manager SLO Management application from a web browser. BusinessObjects reports. The user can open BusinessObjects reports. The SLA PROVISIONING application on the SLA PROVISIONING shortcut bar. The KQI ANALYZER application on the MONITORING shortcut bar. The PARTIES application on the SLA PROVISIONING shortcut bar.
SAG Page 36

Table 15:
Role Gives the user access to
New user roles
Service Quality Administrator Functions. This role gives the user the rights to create, delete and Manager User Man- update other users passwords in the system. This role should only be given to agement administrators. Access to Service Quality Management SLA Monitoring Alarm Monitoring Service Quality Management Audit Service Quality Manager Modelling Service Modelling SLA Web Monitor Gives the user rights to access Service Quality Manager. This role is not required to access Customer Experience Manager or SLA Web Monitor applications, it does not need to be given to users who will only use these applications. This role should be given to users accessing all other applications. The SLA MONITOR application on the MONITORING shortcut bar. The ALARM MONITOR application on the MONITORING shortcut bar. The AUDIT MANAGER on the AUDITING shortcut bar. The SERVICES RESOURCES and KQI MODELS applications on the SQM PROVISIONING shortcut bar. The SERVICE MODELLING application on the SQM PROVISIONING shortcut bar. The SLA WEB VIEWS application from a web browser.
Note: For security reasons, restrict the number of users assigned to the SERVICE QUALITY MANAGER USER MANAGEMENT role. Ensure that only users who are allowed to create users are assigned to this role. 9. Enter and confirm a password for the new user. This password must comply with the password rules in Default password rules for Service Quality Manager users on page 38. 10. Click the CREATE USER button as shown in Figure 4. The newly created user can now log into the Service Quality Manager Client.
Figure 4: User management - create user
Updated: 2009-06-23
SAG Page 37

4.3.1
Default password rules for Service Quality Manager users
Note: To configure your own specific password policy rules, refer to Password policy configuration on page 63. By default, a password must comply with the password rules below: It must be at least eight characters in length. It must contain at least three of the character categories below: Uppercase letter Lowercase letter Digit Symbol It cannot contain three or more consecutive instances of the same character, for example: aaa123AB is not acceptable. 111a1aAB is not acceptable. a1a1a1AB is acceptable. It cannot contain three or more consecutive ascending or descending characters, for example: abc123AB is not acceptable. cba321AB is not acceptable. ace246AB is acceptable. It cannot contain the USER ID or the USER ID in reverse format. For example, if the USER ID is fjones, the password cannot contain any of these:
fjones senojf
The last three passwords cannot be re-used.
4.3.2
Modifying a user
Refer to Security on page 57 for procedures for modifying user details.
4.3.3
Deleting a user
To remove a user from Service Quality Manager: 1. Open the USER MANAGEMENT WELCOME screen using Step 1 to Step 5 from Adding a new user to Service Quality Manager. 2. Click the MANAGE USERS link at the top of the screen. The USER SUMMARY screen is displayed as shown in Figure 5.
SAG Page 38

Figure 5:
User management user summary screen
3. Double-click the
icon beside the required users NAME.

Figure 6: User management modify user screen
The Modify User screen is displayed as shown in Figure 6.
4. Click the DELETE button. A confirmation message is displayed. 5. Click OK to continue and return to the USER SUMMARY screen.
Updated: 2009-06-23
SAG Page 39

The successful deletion of the selected user is now displayed on the USER SUMMARY screen.
4.4
Configuring usage notices
Note: In a distributed environment this section needs to be completed on the server containing the Application component of the Service Quality Manager application. This section describes how to configure the usage notices for the Service Quality Manager Client and Service Quality Manager User Management. To configure the usage notice, complete the following steps as user saserver on the Service Quality Manager Server: 1. Edit the file:
$WMCROOT/conf/auth/usermgmt.properties
2. Add the text you want displayed in the USAGE NOTICE to the com.comnitel.security.auth.usage.notice property. For example:
com.comnitel.security.auth.usage.notice=You are about to..........\n\
To insert line breaks in the notice, insert \n at the end of a line of text. Any text added after \n will be moved to a new line. 3. Save and exit the usermgmt.properties file. 4. To verify the usage notice for the Service Quality Manager Client, double-click SERVICE QUALITY MANAGER CLIENT on the APPLICATION DISCOVERER window. The text you entered is displayed in the notice as shown in the example in Figure 7.
Figure 7: Example of a client usage notice
5. To verify the usage notice in the USER MANAGEMENT login screen, execute the following commands as user saserver:
$ sap stop coreweb $ sap start coreweb
SAG Page 40

6. Relaunch the USER MANAGEMENT login screen by selecting USERS AND PASSWORDS on the APPLICATION DISCOVERER Window. The text you entered is now displayed in the usage notice as in the example in Figure 8.
Figure 8: Example usage notice on user management login screen
Note: If you do not configure the com.comnitel.security.auth.usage.notice property, a usage notice will not be displayed when users log into the SERVICE QUALITY MANAGER CLIENT or open the USER MANAGEMENT login screen.
4.5
Configuring the user management application time out
Note: In a distributed environment this section needs to be completed on the server containing the Application component of the Service Quality Manager application. The USER MANAGEMENT application is configured so that an inactive session is dropped after a fixed time period. Users are then forced to log into the USER MANAGEMENT application again. Note: The default value for the USER MANAGEMENT application time-out is 30 minutes. To change the time-out to a different value, complete the steps below. To configure the timeout value, complete the following steps as user saserver: 1. Edit the following file:
$WMCROOT/tomcat/webapps/usermgmt/WEB-INF/web.xml
2. Edit the section below of the web.xml file to configure the time-out. In the example, the time-out is configured with the default value of 30 minutes.
Updated: 2009-06-23
SAG Page 41

<session-config> <session-timeout> 30 </session-timeout> </session-config>
3. Enter the number of minutes for the new time-out period. 4. Save and exit the web.xml file. 5. Execute the following commands as user saserver:
$ sap stop coreweb $ sap start coreweb
The changes will be applied the next time a user logs into the USER MANAGEMENT application.
SAG Page 42

Starting and stopping Service Quality Manager
5
5.1

Overview
Several applications must be running before the Service Quality Manager application can be started correctly: Oracle Database: sadb Tivoli Directory Server WebSphere Message Broker Service Quality Manager Web Portal Service Quality Manager Process Monitor Service Quality Manager Process Manager Socks Proxy (optional) When all these applications are running, Service Quality Manager can be started. All of the processes are automatically started upon startup.
5.2
Oracle database
Refer to Database administration on page 19 for details on how to stop and start the Oracle database.
5.3
5.3.1
Tivoli Directory Server

Starting Tivoli Directory Server
To start Tivoli Directory Server, complete the following steps: 1. Log in as user idsinst. 2. Execute the command:
$ /opt/IBM/ldap/V6.1/sbin/idsdiradm -I idsinst $ /opt/IBM/ldap/V6.1/sbin/idsslapd -I idsinst
Updated: 2009-06-23
SAG Page 43

5.3.2
Checking Tivoli Directory Server
To check if the Tivoli Directory Server has started, complete the following steps: 1. Log in as user idsinst: 2. Execute the commands:
$ ps -ef | grep ibmslapd
There must be one slapd process running.

$ ps -ef | grep ibmdiradm
There must be one diradm process running.
5.3.3
Stopping Tivoli Directory Server
To stop the Tivoli Directory Server, complete the following steps: 1. Log in as user idsinst. 2. Execute the command:
$ /opt/IBM/ldap/V6.1/sbin/idsdiradm -I idsinst -k $ /opt/IBM/ldap/V6.1/sbin/idsslapd -I idsinst -k $ db2stop
5.4
5.4.1
WebSphere Message Broker

Starting WebSphere Message Broker instance
Execute this command as user saserver:
$ /etc/rc.d/init.d/wmbsa start
Start the WebSphere Message Broker instance by completing the following step:
5.4.2
Checking WebSphere Message Broker
To check if the WebSphere Message Broker has started successfully,complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ ps -ef | grep wmb
One wmb process is running.
5.4.3
Stopping WebSphere Message Broker instance
Stop the WebSphere Message Broker Instance by completing the following steps: 1. Log in as user saserver. 2. Execute this command as user saserver:
SAG Page 44

$ /etc/rc.d/init.d/wmbsa stop
5.5
Service Quality Manager web portal
The Service Quality Manager Web Portal process supports access to the Web Portal functionality.
5.5.1
Starting the Service Quality Manager web portal
1. Log in as user saserver. 2. Execute the command:

$ /etc/rc.d/init.d/wpsa start
5.5.2
Checking Service Quality Manager web portal
To check if the Service Quality Manager Web Portal has started successfully, complete the following steps: 1. Log in as saserver. 2. Execute the command:
$ ps -ef | grep isc
There must be one WebSphere process running.
5.5.3
Stopping Service Quality Manager web portal
To stop the Service Quality Manager Web Portal, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ /etc/rc.d/init.d/wpsa stop
5.6
Service Quality Manager process monitor
The Service Quality Manager process monitor manages the restart function of the application. Note: The Service Quality Manager process monitor must be started on each Service Quality Manager server.
5.6.1
Starting Service Quality Manager process monitor
To start the Service Quality Manager process monitor, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
Updated: 2009-06-23
SAG Page 45

$ /etc/rc.d/init.d/sapmonsa start
5.6.2
Checking Service Quality Manager process monitor
To check if the Service Quality Manager process monitor has started successfully, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ ps -ef | grep sapmon
There must be one sapmon process running.
5.6.3
Stopping Service Quality Manager process monitor
To stop the Service Quality Manager process monitor, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ /etc/rc.d/init.d/sapmonsa stop
5.7
Service Quality Manager process manager
The Service Quality Manager process manager registers all of the Service Quality Manager processes. Note: In a distributed environment the Service Quality Manager process manager is started only on the server containing the application component of the Service Quality Manager application.
5.7.1
Starting the Service Quality Manager process manager
To start the Service Quality Manager process manager, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ /etc/rc.d/init.d/sapmgrsa start
5.7.2
Checking Service Quality Manager process manager
To check if the Service Quality Manager process manager has started successfully, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ ps -ef | grep sapmgr
There must be one sapmgr process running.
SAG Page 46

5.7.3
Stopping the Service Quality Manager process manager
To stop the Service Quality Manager process manager, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ /etc/rc.d/init.d/sapmgrsa stop
This command does not stop Service Quality Manager processes.
5.8
SOCKS proxy
Note: In a distributed environment the SOCKS proxy is only started on the Service Quality Manager application server.
5.8.1
Starting SOCKS proxy
To start the SOCKS proxy, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ /etc/rc.d/init.d/sockssa start
5.8.2
Checking SOCKS proxy
To check if the Service Quality Manager SOCKS proxy has started successfully, complete the following steps: 1. Login as user saserver. 2. Execute the command:
$ ps -ef | grep sockd
There must be at least seven SOCK processes running.
5.8.3
Stopping SOCKS proxy
To stop the SOCKS proxy, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ /etc/rc.d/init.d/sockssa stop
5.9
Service Quality Manager
Service Quality Manager is started and stopped using the sap command.
Updated: 2009-06-23
SAG Page 47

5.9.1
Starting Service Quality Manager
To start Service Quality Manager, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ sap start
5.9.2
Stopping Service Quality Manager
To stop Service Quality Manager, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ sap stop
5.9.3
Checking the status of Service Quality Manager
To check the status of Service Quality Manager, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ sap disp
3. To see additional information, execute the command:

$ sap disp -l
5.9.4
Stop and start parameters

$ sap start <process>: starts the specified process or process group. $ sap stop <process>: stops the specified process or process group.
The sap command also enables you to stop and/or start individual processes:
Table 16 describes the individual processes and their groups.

Table 16:
Process
coreweb
Processes and process groups
Group
Process description
client
Core Web The Core Web process manages the web server on port 8092/ 8094 which provides the Web Start service for installing and running the client, and the user management interface.
SAG Page 48

Table 16:
Process
drldom
Processes and process groups (Continued)

Process description
Group
client
Drilldown object manager Supports DrillDown functionality and provides the historical service for SLA MONITOR. Each time the combiner produces a KQI, data is selected based on the network start and end times for the KQI which usually rules out any data older than the network start time (unless no current data is available, when the combiner may choose to select older data). Since the algorithm for selection of data is complex, it is possible to browse the actual data selected to understand how a particular value was obtained for a KQI. This is known as drilldown. Once the combiner has selected the constituent data, it stores enough information (drilldown relationships) about that data in the database to facilitate later browsing via the Monitoring UI and the KQI ANALYZER.
prefom
client
Preferences object manager Stores the user preferences, SLA MONITOR preferences and SLA MONITOR "discovered" SLAs.
ceb
client
Client event broker The Client Event Broker provides an intermediate communication layer between one or more SLA server processes and the GUI clients. The communication takes place via JMS (JavaTM Messaging Service). Each GUI client registers with the Client Event Broker and indicates via a filter SLAs for which it is responsible. The Client Event Broker caches this information and uses it to forward SLA violations to the correct clients.
rmom
domain
Resource object manager Provides the ability to define and maintain a repository of resources, resource types, and resource groups via a graphical user interface. In addition, aliases can be associated with these resources so that resource naming can be harmonized and consistent naming standards can be maintained.
kmom
domain
KQI model object manager Manages the KQI models in the system (simple and combined). Operations provided by this server include create, retrieve, update and delete.
partyom
domain
Party object manager Manages the party entities in the system. Operations provided by this server include create, retrieve, update and delete.
Updated: 2009-06-23
SAG Page 49

Table 16:
Process
slatom

Process description
Group
domain
SLA template object manager Manages the SLA template entities in the system. Operations provided by this server include create, retrieve, update and delete.
slaom
domain
SLA object manager The SLA Object Manager evaluates KQIs against clauses to determine whether an SLA warning or violation has occurred. It then generates notifications of SLA violations, warnings and clears as they occur and stores them in the SLA violation data store for reporting purposes and forwards these notifications to the OSS Adapter and Client Event Broker. This server also manages the SLA entities in the system. Operations provided by this server include create, retrieve, update and delete.
auditom
domain
Audit object manager This server is used to record all the operations (create, update and delete) performed on the managed entities of the system that is, KQI models, service resources, SLA templates, SLAs, and service models.
reportom
domain
Report object manager The report object manager facilitates the generation of reports based on data stored in the repos database. This server is responsible for performing report associations between entities and report namesfor example, a KQI model is associated with a list of reports. This list is managed by this server.
serviceom svcreportom
domain domain
Manages the service models in the system. Operations supported by the server include create, retrieve, update and delete. Used by the lightweight UI for report association with SLA WEB VIEW. This server is responsible for associating a context or roles with a set of reports. Currently, used by SLA WEB VIEW and CUSTOMER EXPERIENCE MANAGER. KPI (Key Performance Indicator) object Manager. Provides the ability to define and query the repository of key performance indicator models. The operations supported by this server include: Create, update, delete and retrieve.
kpiom
domain
uiservice
client
This server provides a UI or client with a set of services associated with SLA. This server contains an internal memory representation of SLAs that are monitored by SLA WEB VIEW. Currently, this server is only used by SLA WEB VIEW. Alarm object manager The Alarm server is responsible for managing the alarms in the system. Operations supported by the server include create, clear, acknowledge, retrieve, update and delete.
alarmom
monitoring
SAG Page 50

Table 16:
Process
combiner

Process description
Group
monitoring
KQI combiner The KQI combiner combines simple KQIs and combined KQIs into combined KQIs.
oss
monitoring
OSS (Operation Support System) adapter The OSS Adapter interfaces with other OSS systems by: Subscribing to SLA violations published by the SLA Server processes. Issuing X.733-compatible SLA violation events (alarms) to other OSS systems. The ADDITIONAL INFORMATION field is populated with information about the KQI indicating the violation, where the KQI represents a mean figure, the spread of values seen (maximum/minimum).
crmproxy slom customerom slouiservice
cem cem cem cem
Service used to integrate with CRM (Customer Resource Manager) systems in the scope of Customer Experience Manager. Used to manage Customer Experience Manager service level objectives. Used to manage the Customer Experience Manager customer identifiers and Customer Experience Manager customer groups. This server is used in the scope of the Customer Experience Manager SLO monitoring application. It defines a set of services used by the SLO monitor user interface only. These servers are used by the Customer Experience Manager analysis user interfaces to display the content of the analysis performed by the user. dsengineom1and dsengineom2 are used by the Customer Experience Manager Analysis user interface embedded in the Integrated Solutions Console, while dsengineom3 is used by the Customer Experience Manager analysis reporting functionality. Used to assess Customer Experience Manager service level objectives. The output from sap disp may show other managed processesfor example, the installed adapters. See the appropriate adapter documentation for details.
dsengineom1 dsengineom2 dsengineom3
cem
sloengineom1 adapter*
cem adapters
Note*: Depending on the deployed system, different adapters will be associated with the Service Quality Manager process manager. To see which adapters are on the system, execute the following command as user saserver:
$ sap disp adapters
Example:
$ sap disp adapters
Updated: 2009-06-23
SAG Page 51

NAME cdrmonitoradapter1 cdradapter1
STATE STARTED STARTED
SINCE Apr 16, 2007 Apr 16, 2007
SAG Page 52

Maintenance
6
6.1
Maintenance
Overview
Service Quality Manager provides the following application maintenace utilities below to enable maintenance and debugging of the application: Service Quality Manager cron jobs Service Quality Manager logging Service Quality Manager trace files Service Quality Manager debug levels Cron jobs are installed on each server: database, application and gateway. The sections below detail all cronjobs installed on the entire system. Note: If maintenance of the operating system log files is the responsibility of the customer, the customer must ensure maintenance of the /var/adm/wtmp file. This file can grow rapidly on the gateway server if adapter sessions are being logged.
6.2
Service Quality Manager cron jobs
Service Quality Manager uses a UNIX utility, called cron, to execute a schedule of commands in a crontab. All cronjobs are stored in each user's cron file that is located in the /var/spool/ cron/crontabs directory.
Updated: 2009-06-23
SAG Page 53

Maintenance
6.2.1
Viewing the crontab file (saserver)
To view the crontab file, complete the following steps: 1. Log in as user saserver. 2. Execute the command:
$ crontab -l OUTPUT:
Note: This is a sample cron file.

0 1 * * * /appl/sa/admin/common/cron/cron_script -r -d 31 /data/ trace_archive1 \*.log.\* 0 1 * * * /appl/sa/admin/common/cron/cron_script -r -d 31 /data/ trace_archive1 \*.err.\* 0 1 * * * /appl/sa/admin/common/cron/cron_script -r -d 31 /data/ trace_archive1 \*.out.\* 0 1 * * * /appl/sa/admin/common/cron/cron_script -a -d 0 /appl/sa/logs/ \*.log.\* /data/trace_archive1 0 1 * * * /appl/sa/admin/common/cron/cron_script -a -d 0 /appl/sa/logs/ \*.err.\* /data/trace_archive1 0 1 * * * /appl/sa/admin/common/cron/cron_script -a -d 0 /appl/sa/logs/ \*.out.\* /data/trace_archive1 0 3 * * * /appl/sa/admin/common/cron/cron_script -r -d 2 /appl/sa/tomcat/ logs \*.\*.log
6.2.2
Viewing the crontab file (root)
To view the crontab file, complete the following steps: 1. Log in as user root. 2. Execute the command
$ crontab -l OUTPUT:
Note: This is a sample cron file.

0 23 * * * /appl/sa/admin/oracle/cron/roll_listener_log 0 23 * * * /appl/sa/admin/common/cron/cron_script -r -d 2 CROND_LOG log.\* 0 23 * * * /appl/sa/admin/common/cron/cron_script -r -d 2 CROND_OLOG olog.\* 0 23 * * * /appl/sa/admin/common/cron/roll_wtmp_log 0 23 * * * /appl/sa/admin/common/cron/cron_script -r -d 2 WTMP_LOG wtmp\*.\* 0 23 * * * /appl/sa/admin/common/cron/roll_cron_log
SAG Page 54

Maintenance
0 22 * * * /appl/sa/admin/common/cron/cron_script -r -d 2 /tmp crout\* 0 23 * * * /appl/sa/admin/common/cron/cron_script -r -d 2 /appl/oracle/ product/10.2.0/db_1/network/log listener.log.\* 0 23 * * * /appl/sa/admin/common/cron/cron_script -r -d 5 /oradump arch_\* 0 23 * * * /appl/sa/admin/common/cron/cron_script -r -d 2 /appl/ldap/ idsslapd-idsinst/logs '\*.log'
6.2.3
List of cron scripts

cron_script - Clears out the Service Quality Manager system of old audit, trace archives and log files on a nightly basis. roll_cron_log -Timestamps and rolls over the cron file in /var/cron. Another cron is used to clean up the rolled over cron logs. roll_wtmpx_log - Timestamps and rolls over the wtmp file in /var/adm. Another cron is used to clean up the rolled over wtmp logs. roll_listener_log - Rolls the Oracle 10g listener logfile.
6.2.4
Stopping and starting cron jobs
To stop and start cron jobs, complete the following steps: 1. Log in as user root. 2. Find the cron jobs PID. 3. Execute the command:
kill <PID>
where <PID> is the cron job process id. The system will restart it automatically.
Updated: 2009-06-23
SAG Page 55

Maintenance
SAG Page 56

Security
7
7.1
Security
Overview
This chapter provides an overview of the security features of Service Quality Manager. It also describes how to change the password policies in configuration files and within the Tivoli Directory Server for all of the Service Quality Manager users. The Service Quality Manager application is preconfigured with a default global security policy. Depending on your company security policy, it may be necessary to change the default level of security that is provided by the Tivoli Directory Server. This chapter includes the topics: Locking and unlocking user accounts on page 57. Changing passwords as Service Quality Manager administrator on page 60. Changing passwords as a user on page 61. Password policy configuration on page 63. SSL configuration and certificate management on page 67.
7.2
Locking and unlocking user accounts
Sometimes it may be necessary to lock and unlock user accounts. An account can become locked for the reasons below: If the password has expired after the specified period of time. The user has locked themselves out of their account after inputting the password incorrectly more than the specified number of times. To lock or unlock a user account, complete the following steps: 1. Open the APPLICATION DISCOVERER window from the START Menu by selecting: START=>ALL PROGRAMS=>IBM TIVOLI NETCOOL=>SERVICE QUALITY MANAGER=>APPLICATION DISCOVERER. 2. In the APPLICATION DISCOVERER window, double-click USERS AND PASSWORDS. The USER MANAGEMENT login screen is displayed in your web browser.
Updated: 2009-06-23
SAG Page 57

Security
3. Select the ADMIN role option and log in with your administrator USERNAME and PASSWORD. The USER MANAGEMENT WELCOME screen is displayed as shown in Figure 9.
Figure 9: User management welcome screen (administrator)
4. Click the MANAGE USERS link at the top of the screen. The USER SUMMARY screen is displayed as shown in Figure 10.
Figure 10: User management user summary screen
5. Double-click the
The MODIFY USER screen is displayed as shown in Figure 11.
SAG Page 58

Security
Figure 11:
User management modify user screen
6. In the MODIFY USER screen, check the USER LOCKED check box to lock the account. OR Clear the checkbox to unlock the account as shown in Figure 12. Note: Ensure the LOGIN RETRY COUNT value is reset to 0 after an account is unlocked.
Figure 12: User locked/unlocked
7. Click UPDATE to update the account. 8. Click LOGOUT when complete.
Updated: 2009-06-23
SAG Page 59

Security
7.3
Changing passwords
The Service Quality Manager administrator. The user.
Changing a users password can be performed by:
7.3.1
Changing passwords as Service Quality Manager administrator
This procedure describes how you can log in and change a users password: 1. Open the USER MANAGEMENT WELCOME screen using Step 1 to Step 3 from Locking and unlocking user accounts. 2. Click the MANAGE USERS link at the top of the screen. The USER SUMMARY screen as shown in Figure 13 is displayed.
Figure 13: User management user summary screen
3. Double-click the
The MODIFY USER screen as shown in Figure 14 is displayed.
SAG Page 60

Security
Figure 14:
User management modify user screen
4. Enter the new password in both the PASSWORD and CONFIRM PASSWORD fields and click UPDATE. The user password is changed. 5. Click LOGOUT when complete.
7.3.2
Changing passwords as a user
This procedure describes how you can log in and change your own user password: 1. Open the APPLICATION DISCOVERER window from the START Menu by selecting: START=>ALL PROGRAMS=>IBM TIVOLI NETCOOL=>SERVICE QUALITY MANAGER=>APPLICATION DISCOVERER. 2. In the APPLICATION DISCOVERER window, double-click USERS AND PASSWORDS. The USER MANAGEMENT login screen is displayed in your web browser. 3. Select the USER role and log in with your USERNAME and PASSWORD. The USER MANAGEMENT WELCOME screen is displayed as shown in Figure 15.
Updated: 2009-06-23
SAG Page 61

Security
Figure 15:
User management welcome screen (user)
4. Click the MY RECORD link at the top of the screen. The MODIFY RECORD screen is displayed as shown in Figure 16.
Figure 16: User management modify record screen
5. In the MODIFY RECORD screen, enter the new password in both the PASSWORD and CONFIRM PASSWORD fields and click UPDATE. Your user password is changed.
SAG Page 62

Security
7.4
Password policy configuration
When creating a new Service Quality Manager user in User Management, you must enter and confirm a password for the new user. The new password must comply with the password policy rules below: Password policy rules in the Service Quality Manager Server. Global password policy rules in Tivoli Directory Server.
7.4.1 server
Changing the password policy in the Service Quality Manager
Note: In a distributed environment this section needs to be completed on the server containing the Application component of the Service Quality Manager Application. The password must comply with the password rules configured in the policy.properties file. A set of default password rules are provided, refer to Default password rules for Service Quality Manager users on page 38. You can modify the existing default password policy rules. Modifying an existing password rule To modify an existing password rule, complete the following steps as user saserver: 1. Open the file:
$WMCROOT/conf/auth/policy.properties
2. To modify a password rule: To modify the rule, change the parameters. For example, to modify the password rule below to increase the maximum consecutive ascending or descending characters from 2 to 4, replace 2 with 4 in the property:
com.comnitel.password.max.consecutive.chars=2
3. Save and exit the policy.properties file. 4. For the new password policy to take effect, you must restart the coreweb process.
7.4.2
Changing the global password policy in the Tivoli Directory server
Additional password security can be provided by configuring the global password policy in the Tivoli Directory Server. Below is a sample of the functionality that is supported: Enable, disable, or change the password expiration period Enable or disable account lockout Prohibit the use of previous passwords Note: The guidelines below are provided for information only; you must ensure that you fully understand the configuration of Tivoli Directory Server before attempting to modify global password policy attributes. For full information on password policy attributes, see documentaUpdated: 2009-06-23
SAG Page 63

Security
tion at http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/ com.ibm.IBMDS.doc/admin_gd17.htm. Enabling or changing the password expiration period - example: set 90 day password expiration It is possible to enable a Service Quality Manager password expiration policy. Note: For full information on password policy attributes, see documentation at http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/ com.ibm.IBMDS.doc/admin_gd17.htm.
This section details how to set a 90-day expiration policy within Service Quality Manager. All Service Quality Manager user passwords expire 90 days after they are initially created. To enable a 90 day expiration policy, complete the following steps as user saserver: 1. Create a cust_policy.ldif file under $WMCROOT/admin/tds/schema. Add only the entries that you want to change to the file you create. Omitted attributes will remain at their default values or the values that were set during the Service Quality Manager installation. This is an example of the cust_policy.ldif file:
dn: cn=user policy,cn=ibmpolicies changetype: modify replace: pwdMaxAge pwdMaxAge: 7776000
This file contains an attribute that can be used to enable password expiration. The attribute is: pwdMaxAge: 7776000 The pwdMaxAge value of 7776000 represents the number of seconds after which user passwords expire. For example, you can set all Service Quality Manager user passwords to expire 7776000 seconds (90 days) after they are initially created. Note: Ensure no spaces exist at the end of the lines being added or modified.
SAG Page 64

Security
2. Execute the command:

$WMCROOT/admin/tds/install/scripts/change_policy -wmcr <wmcroot> -p <ds_password>
where <wmcroot> is the location where Service Quality Manager is installed and <ds_password> is the Directory Server password. Enabling account lockout You can lock Service Quality Manager users out of their accounts after a specified number of unsuccessful login attempts. You can unlock a user account as described in Locking and unlocking user accounts on page 57. Note: For full information on password policy attributes, see the documentation at http://
publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/ com.ibm.IBMDS.doc/admin_gd17.htm.
To enable an account lockout policy, complete the following steps as user saserver: 1. Create a cust_policy.ldif file under $WMCROOT/admin/tds/schema. Add only the entries that you want to change to the file you create. Omitted attributes will remain at their default values or the values that were set during the Service Quality Manager installation. This is an example of the cust_policy.ldif file:
dn: cn=user policy,cn=ibmpolicies changetype: modify replace: pwdLockout pwdLockout: True dn: cn=user policy,cn=ibmpolicies changetype: modify replace: pwdMaxFailure pwdMaxFailure: 5
This example contains two attributes that can be used to enable account lockout. The 2 attributes show how to enable account lockout and how to set the maximum number of unsuccessful login attempts to 5. pwdLockout: true - Enables account lockout pwdMaxFailure:5 - Sets the maximum number of unsuccessful login attempts to 5.
Updated: 2009-06-23
SAG Page 65

Security
Note: Ensure no spaces exist at the end of the lines being added or modified. 2. Execute this command as user saserver:
where <wmcroot> is the location where Service Quality Manager is installed and <ds_password> is the Directory Server password. Prohibiting the reuse of past passwords You can change the number of past Service Quality Manager passwords that cannot be re-used. By default this password policy rule is configured so that the past three password cannot be reused. Note: For full information on password policy attributes, see documentation at http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/ com.ibm.IBMDS.doc/admin_gd17.htm.
To modify the value of the pwdInHistory attribute, complete the following steps as user
saserver:
1. Edit the file: $WMCROOT/admin/tds/schema/cust_policy.ldif You should only add the entries that you wish to change to the file you create. Omitted attributes will remain at their default values or the values that were set during the Service Quality Manager installation. 2. Change the value of the pwdInHistory attribute.
pwdInHistory: 3
The current value of 3 indicates that the past three passwords cannot be reused, to modify this value, set the pwdInHistory attribute to another value. Note: Ensure no spaces exist at the end of the lines being added or modified. 3. Save and exit the file. 4. Execute this command as user saserver:
where <wmcroot> is the location where Service Quality Manager is installed and <ds_password> is the Directory Server password.
SAG Page 66

Security
Tivoli Directory Server DB2 instance password expiration - changing Tivoli Directory Server DB2 instance password If the idsinst user account becomes unavailable, for example, because of the password expiring ora changed password, the Tivoli Directory Server will no longer be able to authenticate accessDB2 and the LDAP Server will not be able to operate. To resolve this, please refer to the Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21297067 for information on updating the TDS password for the DB2 instance.
7.5
SSL configuration and certificate management
Note: All the procedures in the sections below can be completed as user saserver.
7.5.1
Generating an SSL configuration for Service Quality Manager

The Secured Socket Layer (SSL) configuration script, config_ssl provides an automated procedure which generates SSL configuration for Service Quality Manager based on a generated local Certification Authority (CA). This script is executed as part of the Service Quality Manager Server Installation. It generates the files: cadb: The Service Quality Manager Certification Authority database. ca.cer: The Service Quality Manager Certification Authority certificate. tomcat.kst: The Tomcat Server keystore. The keystore is an encrypted container file which contains the Tomcat signed certificate. webstart.kst: The Certification Authority keystore. The keystore is an encrypted container file which contains the Certification Authority signed certificate. web.cer: The signed Tomcat certificate. web.csr: The Tomcat Certificate Signing Request. ds.cer: The signed Tivoli Directory Server certificate. ds.csr: The Tivoli Directory Server Certificate Signing Request. pwfile: Keystore password file.
7.5.2
Certificate management
Certificate Management provides the functionality of creating and installing certificates which are used in SSL communication. The Service Quality Manager system supports certificate management using one of the methods: The default Service Quality Manager Site Certification Authority. A well-known external Certification Authority. An unknown external Certification Authority. For any of the methods listed above the basic common steps are:
Updated: 2009-06-23
SAG Page 67

Security
Generating Certificate Signing Requests. Obtaining signed certificates from the Certification Authority. Installing signed certificates where required by Service Quality Manager. To enable SSL for the Service Quality Manager system, these procedures must be completed: Configuring the Tomcat (coreweb) SSL keystore. Refer to Configuring Tomcat server SSL keystore on page 69. Configuring the Service Quality Manager Client keystore. Refer to Configuring the Service Quality Manager client keystore on page 69. Configuring the Tivoli Directory Server SSL database. Refer to Configuring the Tivoli Directory Server SSL database on page 70. After installing Service Quality Manager, SSL is configured using certificates signed by the default Service Quality Manager Certification Authority. Note: Depending on your specific business requirements, you may wish to replace these default certificates with certificates signed by an external Certification Authority. In this case, no automated procedure is provided.
7.5.3 Service Quality Manager site certification authority (The default method)
In Service Quality Manager the default method of certification management is the Service Quality Manager site Certificate Authority. This method includes the creation of a local Certification Authority which is used to sign certificates. The process of creating the local Certification Authority, generating the signed certificates and installing the signed certificates is automated by the config_ssl script which is located in:
$WMCROOT/admin/tds/bin/
The script is executed as part of the Service Quality Manager Server installation and it generates the files listed in Generating an SSL configuration for Service Quality Manager on page 67. Note: If you choose to replace the default SSL installation with one using an external Certification Authority, you must complete these steps: remove the contents of $WMCROOT/cert directory and follow the steps in Configuring Tomcat server SSL keystore on page 69 to the end of Configuring the certification authority certificate in the client web browser on page 71 using your chosen Certification Authority. If the Certification Authority is unknown, that is, a Certification Authority that is not installed by default in web browsers, then the Certification Authority certificate must be copied to file: $WMCROOT/cert/ca.cer.
SAG Page 68

Security
7.5.4
Configuring Tomcat server SSL keystore
To configure the Tomcat Server SSL keystore, the following steps are required: 1. Create a Tomcat keystore which contains a single self-signed certificate. 2. A Certificate Signing Request is generated from the Tomcat keystore. 3. The Certificate Signing Request is submitted to the Certification Authority. 4. The Certification Authority issues a signed certificate. 5. The signed certificate (web.cer) is imported into the Tomcat keystore. 6. The Certification Authority certificate (ca.cer) is imported into the Tomcat keystore. 7. The secure socket is configured. 8. The Tomcat Server is restarted. Configuring Tomcat server SSL keystore using a locally generated Service Quality Manager certification authority Step 1 to Step 8 above are completed by the default installation locally using a generated Certification Authority. Configuring Tomcat server SSL keystore using an external certification authority The Tomcat Server can be configured for SSL using an external Certification Authority. If the Tomcat Server is going to be configured using an external Certification Authority, the preceeding Step 1 through Step 8 will need to be completed manually as there is no automated procedure provided. By default, Service Quality Manager requires: The keystore $WMCROOT/cert/tomcat.kst exists. The keystore password is the default as is used in the standard installation. Note: If the keystore name, location, password or secure port are changed the configuration file $WMCROOT/tomcat/conf/server.xml must be updated to bring it in line with these changes. The configuration of a Tomcat server to use SSL is documented at the URL:http:// tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html
7.5.5
Configuring the Service Quality Manager client keystore
The Service Quality Manager desktop application requires Certification Authority certificates to communicate with the Service Quality Manager Tomcat Server using SSL. The Certification Authority certificates are downloaded as a Client keystore file to the Client when the APPLICATION DISCOVERER is started.
Updated: 2009-06-23
SAG Page 69

Security
To configure the Service Quality Manager Client keystore: 1. Create the keystore file. 2. Import the Certification Authority certificate. 3. Copy the keystore file to the path and name of the file as configured in the web.xml file of the keystore servlet. The default location is $WMCROOT/cert/webstart.kst. Configuring Service Quality Manager client keystore using a locally generated Service Quality Manager certification authority The steps in Configuring the Service Quality Manager client keystore above are executed when the Service Quality Manager Server is installed by the config_ssl script. Configuring Service Quality Manager client keystore using an external certification authority The Service Quality Manager Client keystore can be configured using an external Certification Authority. If the Client keystore is configured using an external Certification Authority the steps in Configuring the Service Quality Manager client keystore above will need to be completed manually as there is no automated procedure provided. Note: The steps above are not required for a well-known Certification Authority.
7.5.6
Configuring the Tivoli Directory Server SSL database
To enable SSL in the Tivoli Directory Server, the following steps are performed: 1. A keystore for the Tivoli Directory Server is created in $WMCROOT/cert, unless it already exists. The files created or operated on are: dsdb.crl dsdb.kdb dsdb.rdb 2. A Certificate Signing Request is generated from the Tivoli Directory Server keystore. 3. The Certificate Signing Request is submitted to the Certification Authority. 4. The Certification Authority issues a signed certificate. 5. The signed certificate (server-cert) is imported into the Tivoli Directory Server keystore. 6. The Certification Authority certificate (ca-cert) is imported into the Tivoli Directory Server keystore. 7. The Tivoli Directory Server is configured to enable SSL. 8. The Tivoli Directory Server is configured to enable the keystore.
SAG Page 70

Security
9. The Tivoli Directory Server is configured to listen on the secure port specified in the Service Quality Manager configuration property comnitel.env.LDAPS_PORT in $WMCROOT/ conf/environment/default.properties. 10. The Tivoli Directory Server is restarted. Configuring the Tivoli Directory Server SSL database using a locally generated certification authority Step 1 to Step 9 above are completed as a function of the config_ssl script, which automates the configuration of SSL for Service Quality Manager. Step 1 to Step 6 are performed when you run the config_ssl script with the d option. Step 7 to Step 9 are performed when you run the config_ssl script with the "ds" option. Configuring the Tivoli Directory Server SSL database using an external certification authority If the Tivoli Directory Server SSL database is configured using an external Certification Authority the steps in Configuring the Tivoli Directory Server SSL database on page 70 above will need to be completed manually as there is no automated procedure provided. See the Tivoli Directory Server v6.1 Information Center at: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp for information on installing certificates and activating SSL in Tivoli Directory Server. Note: Use the Search scope link to restrict searches to Directory Server topics.
7.5.7 Configuring the certification authority certificate in the client web browser
If the default Service Quality Manager Certification Authority is used, SSL certificates will be signed by a Certification Authority unknown to the users web browser. In this case the user will receive a security warning from the web browser when accessing the User Management application. Removing the security warning To prevent the security warning being displayed in the web browser, complete the following steps: 1. In the APPLICATION DISCOVERER window, double-click USERS AND PASSWORDS. 2. In the USER MANAGEMENT login screen, click on the link to download the Certification Authority certificate. 3. Open the certificate. 4. Install the certificate.
Updated: 2009-06-23
SAG Page 71

Security
Note: If a known Certification Authority is used to configure SSL you are not required to install the certificate as it is installed in the web browser.
Note: The security warnings are not part of the Service Quality Manager product. They are functionality of the web browser.
SAG Page 72

Backup and restore
8
8.1
Backup and restore

Overview
A Service Quality Manager system, like all UNIX servers, should be backed up regularly. Provision should also be made for a restore of the backup in the event of data loss. This chapter outlines the backup and restore considerations for a Service Quality Manager UNIX server system.
8.2
8.2.1
Backup and restore (UNIX)

Backup requirements and schedule
To perform backups, you need a mass-storage device and media; for example, magnetic tape. Suitable tape media should be loaded to the device before performing a backup. Note: The tape system being used must have a capacity that exceeds the total allocated disk space for the file systems being backed up. These set of file systems should be backed up:
/ /opt /usr /var /appl /data/cache /data/download1 /data/download2 /data/trace_archive1 /data/trace_log1 /home /export/home
Updated: 2009-06-23
SAG Page 73

Backup and restore
Note: Some of the above entries may not necessarily exist as separate file systems. The backup operation should perform full or incremental backups of the Service Quality Manager file system as required. It is recommended that a full backup be run once per week at a suitable time, and incremental backups be run nightly. Optionally, file system-level backups may be made of the Oracle database file systems, provided that the Oracle database instances are first shut down. Note that this will incur downtime of the Service Quality Manager system. For example, the Oracle database file systems on a typical Service Quality Manager system are:
/oradata01 /oradata02 /oradata03 /oradata04 /oralogs1 /oralogs2 /oradump /oratemp
8.3
Restoring from backup (UNIX)
Identify the media that holds the data you wish to recover. If you are recovering data from a full backup, it will reside on a single or set of tapes. Incremental backups write to the same tape, or set of tapes, so some time may need to be spent moving through a set of tapes until you find the backup set that contains the required files.
8.3.1
Tape carriage control
Media may have to be loaded by hand, or by a mechanism specific to the tape device being used.
8.3.2
Rewinding a tape
You should rewind the tape before searching, so it can be scanned sequentially. To rewind a tape, enter the following command as user root:
# mt -f <tape device> rewind
where <tape device> denotes the tape device, for example: /dev/rmt/0
SAG Page 74

Backup and restore
8.3.3
Moving through a tape
Moving forward To move forward through a tape, enter this command as user root:
# mt -f <tape device> fsf <number of files to fast forward>
where <tape device> denotes the tape device, for example: /dev/rmt/0 Moving backwards To move backwards through a tape, enter this command as user root:
# mt -f <tape device> bsf <number of files to rewind>
where <tape device> denotes the tape device, for example: /dev/rmt/0 Checking the current position To check the current position of the tape, enter this command as user root:
# mt -f <tape device> status
where <tape device> denotes the tape device, for example: /dev/rmt/0
8.4
Oracle backup and restore
This section outlines a backup and restore of the Oracle databases. Service Quality Manager can use the Oracle Recovery Manager (RMAN) utility to perform the procedures. These databases should be included in the backup: Service Quality Manager core database (sadb) Business Objects repository database (repos) The Service Quality Manager databases are started in Hot Archive mode, that is, a database can be backed up while it is online. It does not require the databases to be shut down before performing the backup. The RMAN utility contains a recovery catalog that is a repository of information. RMAN uses the information in the recovery catalog to determine how to execute requested backup and restore actions. The recovery catalog contains information about: Datafile and archivelog backup sets and backup pieces. Datafile copies. Archived redo logs and their copies. Tablespaces and datafiles on the target database. Stored scripts, which are named, user-created sequences of RMAN and SQL commands. Oracle recommends use of RMAN with a recovery catalog, especially if there are twenty or more datafiles. However, it is not required to maintain a recovery catalog to use RMAN.
Updated: 2009-06-23
SAG Page 75

Backup and restore
Because most information in the recovery catalog is also available in the target database's control file, RMAN supports an operational mode where it uses the target database control file instead of a recovery catalog. This mode is appropriate for small databases where installation and administration of another database for the sole purpose of maintaining the recovery catalog would be a lot of work. If a recovery catalog is not used, these features are not supported: Tablespace point-in-time recovery. Stored scripts. Restore and recovery when the control file is lost or damaged. The RMAN recovery catalog must be installed and configured before Oracle backups can commence.
8.4.1
Recovery catalog
The recovery catalog is contained in an Oracle database. The recovery catalog may be stored on the Database Server, but the customer may choose to locate it elsewhere. For example, on a machine that is already providing an Oracle service. Should the customer choose to locate the recovery catalog elsewhere, it is strongly advised that it should not be located on Service Quality Manager Servers.
8.4.2
Creating the recovery catalog database
The directory $WMCROOT/admin/oracle/install/scripts should contain a description of the tablespaces to be used by createDataBase to prepare the RMAN database. On the Service Quality Manager Database Server, execute the following commands as user
root: # cd <target directory>/admin/oracle/install/scripts # ./database_install -wmcr /appl/sa Please, Enter the required Database Type (sadb/repos): ---->repos Please, Enter your Database SID (8 character maximum): ---->RMAN Please, Enter the sys user password: ---->Sysdb01 Please, Enter the system user password: ---->Sysdb01 . . . Please, Enter the repuser user password: ---->repuser01 Creating repos database user .
SAG Page 76

Backup and restore
. .
On the Service Quality Manager Database Server, execute the following commands as user oracle:
$ export ORACLE_SID=RMAN $ sqlplus /nolog SQL> connect / as sysdba SQL> CREATE TABLESPACE rman_tbs logging 2 3 datafile '/oradata01/RMAN/rman_tbs01.dbf' size 4096M reuse autoextend off;
SQL> exit
8.4.3
Creating the recovery catalog schema
$ export ORACLE_SID=RMAN $ sqlplus /nolog SQL> connect / as sysdba SQL> CREATE USER rman IDENTIFIED BY rman 2 3 4 TEMPORARY TABLESPACE TEMP DEFAULT TABLESPACE rman_tbs QUOTA UNLIMITED ON rman_tbs;
SQL> GRANT recovery_catalog_owner TO rman; SQL> GRANT connect, resource TO rman; SQL> exit
8.4.4
Creating the recovery catalog
$ rman catalog rman/rman@RMAN RMAN> create catalog tablespace RMAN_TBS; RMAN> exit
The creation of the recovery catalog can take several minutes to complete.
Updated: 2009-06-23
SAG Page 77

Backup and restore
8.4.5
Registering a database with the recovery catalog
You must register target databases on the database server, execute the following commands as user oracle: Note: <Oracle SID> below and in subsequent sections refers to the SID of the Oracle database being backed up, such as sadb or repos.
$ export ORACLE_SID=<Oracle SID> $ rman target / RCVCAT rman/rman@RMAN RMAN> register database; database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN> exit
8.5
Database backup
If the customer chooses to locate the recovery catalog elsewhere, backing up the RMAN recovery catalog will become a task for the customer. By default, however, the recovery catalog is stored on the Database Server, in which case it is convenient to backup the RMAN recovery catalog to the /oradump directory on the Database Server. To back up a database, on the Database Server, execute the following commands as user oracle: If the database to be backed up is using a PFILE (an Oracle mutually exclusive parameter file), edit the file $ORACLE_HOME/dbs/init<Oracle SID>.ora and ensure that log_archive_start=TRUE is set. Execute the following commands as user oracle:
$ export ORACLE_SID=<Oracle_SID> $ mkdir /oradump/$ORACLE_SID $ sqlplus /NOLOG SQL> connect / as sysdba SQL> shutdown immediate;
Note: If the /oradump/<Oracle SID> directory already exists, ensure that it is owned by oracle:dba. If the database to be backed up is using a PFILE, use the following SQL command:
SQL> startup mount PFILE="/appl/oracle/product/10.2.0/db_1/dbs/init<Oracle SID>.ora" ;
SAG Page 78

Backup and restore
If the database to be backed up is not using a PFILE, use the following SQL command: SQL> startup mount
SQL> alter database archivelog; SQL> alter database open; SQL> alter system switch logfile; SQL> exit $ rman target / RCVCAT rman/rman@RMAN RMAN> run { 2 allocate channel ch1 type disk format '/oradump/<Oracle SID>/%U'; 3 backup as compressed backupset database; 4 } .. .. .. RMAN> exit
The Oracle backup files within the /oradump file system should now be backed up using appropriate file system backup software for your operating system. See Backup requirements and schedule on page 73.
8.6
Restoring a database
As a general rule, it should only be necessary to restore a database if a media failure has occurred. In the event of media failure, the precise steps taken depend on the extent of the media failure. For example, if a single .DBF file is affected there will be no need to restore control files. However, restoring control files would be required if a catastrophic disk failure destroyed all of the database files. For the remainder of this chapter, it is assumed that the most recent backup files are still in the / oradump directory or have been restored from backup media to the /oradump directory. To restore the database, either the database must be closed or the data files must be offline. If the target database is mounted, then its control file is updated with any applicable data file copy and archived log records to describe the restored files.
Updated: 2009-06-23
SAG Page 79

Backup and restore
8.6.1
Restoring when control files are not lost
To restore the database, complete the following steps: If the target database is open, shut it down and then mount it as user oracle:
$ export ORACLE_SID=<Oracle_SID> $ sqlplus /NOLOG SQL> connect / as sysdba SQL> shutdown immediate; SQL> startup mount; SQL> exit
Start RMAN and connect to the target database and the recovery catalog database. For example, as user oracle enter:
$ rman target / catalog rman/rman@RMAN RMAN> run { 2 allocate channel ch1 type disk format '/oradump/<Oracle SID>/%U'; 3 restore database; 4 recover database; 5 alter database open; 6 release channel ch1; 7 } .. .. .. RMAN> exit
RMAN automatically uses the backup data and archived redo files to bring the data files up to date. The database is restarted by the above procedure.
SAG Page 80

Backup and restore
8.6.2
Restoring when control files are lost
Without control files the database cannot be mounted. As user oracle execute the following commands:
$ export ORACLE_SID=<Oracle_SID> $ rman catalog rman/rman@RMAN RMAN> connect target RMAN-06193: connected to target database (not started) RMAN> startup nomount RMAN-06196: Oracle instance started
The database control files must be restored:

RMAN> run { 2 allocate channel ch1 type disk format '/oradump/<Oracle_SID>/%U'; 3 restore controlfile; 4 startup mount; 5 release channel ch1; 6 } .. .. ..
The remaining steps in this case are similar to the case where the control files are available:
RMAN> run { 2 allocate channel ch1 type disk format '/oradump/<Oracle SID>/%U'; 3 restore database; 4 recover database; 5 alter database open resetlogs; 6 release channel ch1; 7 } .. .. .. RMAN> exit
Updated: 2009-06-23
SAG Page 81

Backup and restore
8.6.3
Errors during recovery
Occasionally, on completion of the recovery procedure you may see an error message similar to this:
RMAN-00571: ===================================================================== RMAN-00569: ============= ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ===================================================================== RMAN-03002: failure during compilation of command RMAN-03013: command type: recover RMAN-03006: non-retryable error occurred during execution of command: recover(4) RMAN-07004: unhandled exception during command execution on channel default RMAN-20000: abnormal termination of job step RMAN-06054: media recovery requesting unknown log: thread 1 scn 28146
If this error is seen, resume the backup from just before the point of error. To do this, note the SCN number at the end of the last line, and enter the following commands giving <PRIOR-SCN> a value of one less than the SCN from the error output. In the above example, this would be 28145.
RMAN> run { 2 set until SCN <PRIOR-SCN>; 2 allocate channel ch1 type disk format '/oradump/<Oracle SID>/%U'; 4 restore database; 5 recover database; 6 alter database open; 7 release channel ch1; 8 } .. .. .. RMAN> exit
Note: To move the target database to a new host, rename the datafiles as needed, using set newname. To create a test database using backups of the target database, use the duplicate command.
SAG Page 82

System logging and tools
9
9.1
9.1.1

System logging
Service Quality Manager application logging
The Service Quality Manager application writes log files to a specified location. The location is determined by whatever the SALOGDIR value is set to in the $WMCROOT/conf/environment/ default.properties file. Each process has its own directory where the log files are stored. This directory holds files with the extensions: server.log, .err, and .out . An explanation of each file type is as follows: <process_name>-server.log - This file contains the trace output for the named process. The level of tracing can be set in the default.properties file, $WMCROOT/ conf/logging/default.properties using the comnitel.log.level attribute. The value can range from FATAL (lowest) to debug4 (highest). <process_name>-<PID>.err -This file contains a detailed description of Service Quality Manager process errors. <process_name>-<PID>.out - This file contains the screen output from the Service Quality Manager process startup. For example: Service Quality Manager log files for the prefom would be kept in the example location:
/data/trace_log1/prefom/prefom-server.log
Updated: 2009-06-23
SAG Page 83

9.1.2
Adapter logging
Adapter logs are logged in the same way as the Service Quality Manager process logging. If a distributed environment is deployed then the adapter logs are created in the local logging directory of the Adapter Server.
9.1.3
Oracle logging
$ORACLE_BASE/admin/<MYDB>/bdump $ORACLE_BASE/admin/<MYDB>/cdump $ORACLE_BASE/admin/<MYDB>/udump $ORACLE_HOME/network/trace
Oracle logs are located in these locations:
<MYDB>
is the name of the Service Quality Manager database for example, sadb or repos. contains details specific to background process trace/ contains core dump information. contains user dump and trace files for the database.
$ORACLE_BASE/admin/<MYDB>/bdump
dump files and alert log file.

$ORACLE_BASE/admin/<MYDB>/cdump $ORACLE_BASE/admin/<MYDB>/udump $ORACLE_HOME/network/trace
details Oracle transactions that occur within Oracle.
For more details on the Oracle logs please refer to the Oracle 10g documentation.
9.1.4
Operating system logging

To view the AIX system log, execute the following command as user root:
# errpt -a
Note: The errpt -AD command can also be used above to provide more concise output.
9.1.5
FTP logging
The file below is a database of access logs for common operations on a UNIX operating system. This can be used to confirm user actions that could affect Service Quality Manager operations. The file is located in:
/var/adm/wtmp
This is a binary file and cannot be read directly. Instead, use tools such as who, last, and login, which can access and parse the file's contents.
SAG Page 84

9.1.6
Installation logging
Service Quality Manager installation logging is located in this directory:

$WMCROOT/admin/logs
The directory contains all logging for the installation of Service Quality Manager components including third party products.
9.1.7
TOMCAT logging
Tomcat logging is located in this directory:

$WMCROOT/tomcat/logs
Tomcat logging shows logging related to the basic operation of tomcat such as requests to Server and general web Server housekeeping. It also includes exceptions and tracing generated by servlets and JSPs hosted by Server.
9.1.8
IBM WebSphere Application Server logging
WebSphere Application Server logging is located in this directory:

<WAS_INSTALLATION_ROOT>/profiles/<PROFILE>/logs <WAS_INSTALLATION_ROOT> is the location where WebSphere Application Server for example this is usually the /appl/IBM/WebSphere/AppServer directory.
is installed,
<PROFILE> refers to the WebSphere Application Server instance profile, of which there are two on AIX, one for the Integrated Systems Console called isc, and one for the WebSphere Message Broker, called wmb.
These logs are not automatically managed by default. Over time they will grow in size which could cause problems with disk usage. Review the topics on Java virtual machine log management in the WebSphere Application Server Version 6.1 Information Center at: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp Note: Use the SEARCH SCOPE link to restrict searches to WEBSPHERE APPLICATION SERVER (DISTRIBUTED PLATFORMS AND WINDOWS) topics, then search for JAVA VIRTUAL MACHINE LOG SETTINGS.
9.1.9
IBM Tivoli Directory Server logging
Tivoli Directory Server logging is located in these directories:

<Base directory>/ldap/idsslapd-<INSTANCE>/logs /home/<INSTANCE>/sqllib/db2dump /home/<INSTANCE>/sqllib/log
Updated: 2009-06-23
SAG Page 85

<INSTANCE>
is the name of the Tivoli Directory Server instance created for use with Service Quality Manager. is the directory where the LDAP instance is stored.
<Base directory>
9.2
Service Quality Manager log levels
The Service Quality Manager application allows for log levels to be applied to the Service Quality Manager application. Table 17 details the log levels supported by the Service Quality Manager application.
Table 17:
Level Description
Log levels
FATAL ERROR WARN INFO DEBUG1 DEBUG2 DEBUG3 DEBUG4
FATAL is the lowest level of debug. This level designates severe error events
that can lead the application to abort.

The ERROR level designates error events that might still allow the application to continue running. The WARN level designates potentially harmful situations. The INFO level designates informational messages that highlight the progress of the application at coarse-grained level. Basic debugging is enabled. INFO, WARN, ERROR and FATAL are enabled. Low intermediate debugging is enabled. DEBUG1, INFO, WARN, ERROR and FATAL are enabled. High intermediate debugging is enabled. DEBUG2, DEBUG1, INFO, WARN, ERROR and FATAL are enabled. Advanced debugging is enabled. DEBUG3, DEBUG2, DEBUG1, INFO, WARN, ERROR and FATAL are enabled.
SAG Page 86

To apply a log level globally, complete the following steps: 1. As user saserver modify the $WMCROOT/conf/logging/default.properties file. 2. Set the comnitel.log.level attribute to the required level. 3. To allow for the change to take effect, the Service Quality Manager framework must be stopped and restartedthat is, stop all processes and then start them again. To stop all processes, as saserver run the following commands:
sap stop domain sap stop monitoring sap stop client sap stop cem sap stop adapters
Warning: A global log level setting affects all Service Quality Manager processes. If the log level is set to above info level, it may adversely affect system performance. The logging level should not be changed unless advised to do so by IBM.
9.3
Logging tool
The Service Quality Manager application logging tool allows the log or debug level on each process to be changed at run-time. This may be required if more debug from a process is required. Refer to Table 17 for a list of debug levels. This is the logging tool syntax:
$ logging disp [<processname>] $ logging list $ logging set <processname> [<logger>] <level>
9.3.1
Checking logging or debug levels

logging disp prefom Process( prefom ) Logger ( @.processmgmt, DEBUG4 ) Logger ( @.provision.core.agent.AgentErrorResolver, DEBUG4 ) Logger ( @.db.persist, DEBUG4 ) .. Logger ( @.slm.party, DEBUG4 )
To check the logging level of a process, complete the following step:
The above output shows the process is at DEBUG4 level.

Updated: 2009-06-23
SAG Page 87

Note: The process must be started to allow for the log or debug level to be changed.
9.3.2
Listing logging
logging list Process( rmom ) Process( kmom ) Process( reportom ) Process( drldom ) Process( combiner ) Process( auditom ) Process( slareport ) Process( atkcdradapter1 ) Process( atkcdrmonitoradapter1 ) Process( prefom ) Process( slatom ) Process( partyom ) Process( alarmom ) Process( slaom ) Process( ceb ) Process( oss ) Process( cem ) Process( adapters )
To list logging manageable processes, complete the following step:
9.3.3
Changing logging or debug Levels

logging set prefom INFO Process( prefom ) Logger ( @.processmgmt, INFO ) Logger ( @.provision.core.agent.AgentErrorResolver, INFO ) Logger ( @.db.persist, INFO ) .. Logger ( @.slm.party, INFO )
To change the logging level of a process, complete the following step:
This changes the logging level to INFO.
SAG Page 88

9.3.4
Changing logging levels on process loggers
The logging level of a specific logger within a process can be changed. To find out the loggers relating to a specific process, complete the following steps: Execute this command as user saserver:
logging disp prefom Process( prefom ) Logger ( @.processmgmt, DEBUG4 ) Logger ( @.provision.core.agent.AgentErrorResolver, DEBUG4 ) Logger ( @.db.persist, DEBUG4 ) .. Logger ( @.slm.party, DEBUG4 )
The output above shows just some of the loggers relating to the prefom process. The loggers are: @.processmgmt, @.provision.core.agent.AgentErrorResolver, @.db.persist, @.slm.party. To change the logging level of a specific logger within a process, complete the following step: Execute this command as user saserver:
logging set prefom @.db.persist WARN Process( prefom ) Logger ( @.processmgmt, INFO ) Logger ( @.provision.core.agent.AgentErrorResolver, INFO ) Logger ( @.db.persist, WARN ) .. Logger ( @.slm.party, INFO )
This changes only the logging level on the db.persist logger within the prefom process to WARN.
9.4
Service Quality Manager alarm tool
The alarm_cli tool which is part of the Service Quality Manager product enables alarms to be listed and exported. It is stored in the $WMCROOT/bin directory. This is the syntax of the alarm_cli tool:
alarm_cli active [ -h ] [ -t <csv|xml|html> ] [output_file] alarm_cli log log_names alarm_cli log log_export [ -h ] [ -t <csv|xml|html> ] <log_name> [<output_file>]
Updated: 2009-06-23
SAG Page 89

9.4.1
Listing active alarms
To list all active alarms, complete the following steps: 1. Execute this command as user saserver:
$ alarm_cli active
2. To export all active alarms execute this command as user saserver:

$ alarm_cli active <output_file> <output_file>
is the name of the file to export to.
9.4.2
Exporting active alarms in CSV, XML or HTML formats

CSV XML HTML
Alarms can be exported in three different formats:
The example below shows how to export all active alarms in CSV format. To export all active alarms in CSV format, complete the following step: Execute this command as user saserver:
$ alarm_cli active -t csv <output_file> <output_file>
is the name of the file to export to.
9.4.3
Listing registered alarm logs

$ alarm_cli log log_names
To list the names of registered alarm logs, complete the following step:
9.4.4
Exporting from an alarm log

$ alarm_cli log log_export <log_name> <log_name>
To export entries from an alarm log, complete the following step:
is the name of the file where the alarms are being exported from.
SAG Page 90

9.4.5
Exporting from an alarm log to CSV, XML or HTML formats

CSV XML HTML
Alarms can be exported from an alarm log into three different formats:
The example below shows how to export from an alarm log into CSV format. Execute this command as user saserver:
$ alarm_cli log log_export -t csv <log_name> <output_file> <log_name>
is the name of the file where the alarms are being exported from. is the name of the file to output to.
<output_file>
9.5
9.5.1
Exports and files written to the system.

Service Quality Manager process manager
Writes to a pid file at $WMCROOT/var/pid/<processname>.pid. The file contains the process id for the named process.
9.5.2
Preference management feature
Writes to preference files at $WMCROOT/var/prefs. These binary files are used by Client applications to store user preferences.
9.6
Service Quality Manager summarization tool

Update - which is used to update the metadata of the summarization server without stopping the server. Computation - which is used to re-compute some summarized definition or manually backfill the summary tables. Metric generation - which is used to assess the compression rates of the summary tables over time. Re-synchronization - which is used to validate the summary tables in the case where adapters were backfilled. This script uses the summarization metadata of the summary tables. The Customer Experience Manager summarization metadata for a given Service Quality Manager service solution is located on the application server in the directory:
$WMCROOT/conf/service/cem/adapters/ <service_solution>_<datasource>_loader/summary <service_solution>
The summaryadm script provides access to a set of summarization functionalities, they are:
is the service solution name.

Updated: 2009-06-23
SAG Page 91

<datasource>
is the data source for the above.
Note: This directory is only created if one Customer Experience Manager service solution is deployed.
Note: The Customer Experience Manager summarization metadata files associated with the summary tables are suffixed with _sum.xml inside these directories. These metadata files define the summary definitions via XML. Each summary definition is associated with at least: A summary table name - the table name where the summary data resides. A source table name - the source table name used for summarization. Note: Summary tables may have a summary table as a source in order to speed up the summarization process. A data source type - the data source type associated with a service solution.
9.6.1
Using the summaryadm script
Execute the summaryadm script as user saserver as follows:

$ summaryadm <subcommand>
The list and a description of the supported sub-commands are detailed in Table 18.
SAG Page 92

Table 18:
Sub Commands
-update
summaryadm sub commands, description and usage
Description and usage
Update the summaryom configuration metadata. All the summary definitions will be automatically reloaded and the summarization tasks will be automatically scheduled. This is used for administration purposes only when an update is made to the summary definitions. Usage: summaryadm update Compute a summary definition for a day. This could be used to re-synchronize a summary table with its associated source table. Additionally, summaryom may be configured in order to avoid the automatic summarization. This command can then be used with a cron job in order to schedule the summarization of a given table at a given time during the day preferably, during off-peak hours. Usage: summaryadm compute <summary> <date>
<summary> This is mandatory. The summary definition to compute.
-compute
Note: The list of supported summary definitions could be accessed via the metricserver sub-command detailed below.
<date> This is mandatory. The date to be summarized. The format is dd-MM-
yyyy.
-computeall
Compute all the summary definitions for a day. This could be used to re-synchronize all the summary tables with their associated source tables for a given day. This command can then be used with a cron job in order to schedule the summarization of all the tables at a given time. Usage: summaryadm computeall <date>
yyyy.
-computeallds
Computes all the summary definitions for a day for a given datasource type. This can be used to resynchronize all summary tables with their associated source tables for a given day and a given datasource type. This command can then be used with a cron job in order to schedule the summarization of all the tables at a given time for a given datasource type. Usage: summaryadm computeallds <date> <dstype>
yyyy.
<dstype> This is mandatory, The datasource type for the summarization. -metricserver
Displays the summaryom metadata on the standard output. This could be used to display: The list of summary definitions. The last summarized day for the summary definitions. The next summarization tasks schedule. Usage: summaryadm -metricserver
Updated: 2009-06-23
SAG Page 93

Sub Commands
-metric
Compute a summarization definition metric for a day. A summarization metric consists of indicating the number of rows in the source table, the number of rows in the summary table, the row compression rate for a given day and the execution time associated with the computation of the metric. Usage: summaryadm metric <summary> <date>
<summary> This is mandatory. The summary definition.
Note: The list of supported summary definitions can be accessed using the
metricserver sub-command. <date> This is mandatory. The date to be summarized. The format is dd-MM-
yyyy.
-metricall
Computes all the summary definition metrics for a day. A summarization metric consists of indicating the number of rows in the source table, the number of rows in the summary table, the row compression rate for a given day and the execution time associated with the computation of the metric. Usage: summaryadm -metricall <date>
yyyy.
-metricallrepeat
Computes all the summary definition metrics for a set of days. A summarization metric consists of indicating the number of rows in the source table, the number of rows in the summary table, the row compression rate for a given day and the execution time associated with the computation of the metric. This command specifies the start date as an argument and a number of repeats that indicates how many days after the start date the metrics should be generated for. Usage: summaryadm -metricallrepeat
<startdate> <nbdays> <startdate>This is mandatory. The date that acts as a reference point in time. The format is dd-MM-yyyy. <nbdays> This is mandatory. It indicates how many days after the start date the metrics should be generated for.
-listnotsummarized
List the non summarized summary definitions for a given data-source type. This could be used to identify the days that have not been summarized for a given data-source type. Note: Each summary table is associated with one data source type. An internal table in the database is used to identify the list of non summarized summary definitions. Usage: summaryadm -listnotsummarized <dstype>
<dstype> This is mandatory. The data source type.
Note: The list of supported data source types could be accessed using the metricserver sub-command.
SAG Page 94

Sub Commands
-listnotsummarizedall
List the non summarized summary definitions. This could be used to identify the days that have not been summarized yet by the summaryom process. An internal table in the database is used to identify the list of non summarized summary definitions. Usage: summaryadm -listnotsummarizedall Displays the checksum metrics associated with a given data source type for a set of days. The current date is used as a reference point. A checksum metric is displayed for each summary table associated with the data source type given as an argument. The checksum only reports on the root tables. The checksum consists of indicating the number of adapter batches associated with the summary computation for a given summary definition and a given day. Usage: summaryadm -checksum <dstype> <nbdays>
<dstype> This is mandatory. The data source type to analyze.
-checksum
Note: The list of supported data source types can be accessed using the metricserver sub command. <nbdays> This is mandatory. The date. The format is dd-MM-yyyy. -checksumresync
This could be used to re-compute the checksums associated with the summary definitions and when an inconsistency is detected the summary definitions will be automatically re-computed. This command is used for a given data source type and a number of days, the current date is used as a reference point. The list of re-synchronized summary definitions will be displayed on the standard output. Usage: summaryadm -checksumresync <dstype> <nbdays>
<dstype> This is Mandatory. The data source type.
Note: The list of supported data source types can be accessed using the metricserver sub-command.
<nbdays> This is mandatory. The number of days in the past from the current
date that needs to be analyzed and re-synchronized if inconsistencies are detected.
9.6.2 Use case: Command line interface summarization backfill scenario

When a Customer Experience Manager service solution is upgraded in order to support summarization, the summaryadm command may be used to backfill the summary tables of the Customer Experience Manager service solution when the new version of the Customer Experience Manager service solution is deployed. 1. As user saserver, stop the summaryom process by executing the command:
$ sap stop summaryom
At this point, the summaryom server will need to work in CLI (Command-line Interface) mode only in order to backfill the non-summarized days, one by one.
Updated: 2009-06-23
SAG Page 95

2. Edit $WMCROOT/conf/service/cem/summary/summary.properties, be sure that you set these properties to:

cem.summary.auto.summarization=false cem.summary.auto.resync=false cem.summary.cli.reload.metadata=false
3. As user saserver, re-start the summaryom process by executing :

$ sap start summaryom
The summaryom is now ready to receive any request from the Command Line Interface in order to execute summarization. All requests will need to be executed chronologically i.e. start from the oldest summary requests to the most recent ones. If none of the summary definitions were computed previously, it is advised to use the computeall command. If any other Customer Experience Manager service solution is already summarized on the system, the compute command should be used.
Note: When the compute command is used, special attention should be given in order to execute the summary definitions in the proper order. Summary definitions may be based on other summary definitions. The commands should be invoked from the root summary tables to the next level in a recursive way. For example: A summary table T1 is based on a adapter fact table F1. A summary table T2 is based on the summary table T1. A summary table T3 is based on the summary table T2.Summarizing data for the tables above for a given set of days results in these to be invoked for example, if the -computeall cannot be used i.e. another Customer Experience Manager service solution is deployed and already summarized on the system: $ summaryadm
compute T1 24-05-2009 $ summaryadm compute T2 24-05-2009 $ summaryadm compute T3 24-05-2009 $ summaryadm compute T1 25-05-2009 $ summaryadm compute T2 25-05-2009 $ summaryadm compute T3 25-05-2009
4. When the backfill activity is terminated, the summaryom needs to be re-configured in automatic summarization mode:
cem.summary.auto.summarization=true cem.summary.auto.resync=true
Note: If the backfill activity spans over two days to complete, the summaryom process will be able to automatically re-synchronize all the summary tables that were not summarized during the backfill activity. During the re-synchronization phase, the summaryom will remain at the init state.
SAG Page 96

Integration with IBM Tivoli Netcool OMNIbus and IBM Tivoli Webtop
10
This chapter describes how to integrate Tivoli Netcool Service Quality Manager with Tivoli Netcool OMNIbus and Tivoli Netcool Webtop. Note: Procedures in this chapter should be completed by network administrators or operations specialists who are responsible for installing Tivoli Netcool Service Quality Manager product suite on an enterprise network. The sections below include this information: Preparation steps that need to be completed before integrating Tivoli Netcool Service Quality Manager with Tivoli Netcool OMNIbus and Webtop, refer to Preparing for integration with Tivoli Netcool OMNIbus on page 97. Integration of Tivoli Netcool Service Quality Manager with Tivoli Netcool OMNIbus. Refer to Integrating Service Quality Manager with Tivoli Netcool OMNIbus on page 98.
10.1
Preparing for integration with Tivoli Netcool OMNIbus
This section lists the pr-requisites and software requirements that need to be fulfilled before the integration procedures: Integrating Service Quality Manager with Tivoli Netcool OMNIbus on page 98 can be completed. It also provides information about rules and the ObjectServer.
10.1.1
Prerequisite
SNMP protocol (TRAPs) is allowed (Fire Wall policy) between the Tivoli Netcool Service Quality Manager hosts and the SNMP TRAPD probe.
10.1.2
Software requirements
Netcool/OMNIbus v7.x, including Multi-Thread Trapd probe Netcool Knowledge Library (NcKL) v1.3 or v1.4
Updated: 2009-06-23
SAG Page 97

10.1.3
TRAPD rules
This list identifies TRAPD rules: Tivoli Netcool Service Quality Manager provides an event feed only through MultiThreaded SNMP Trapd probe. Tivoli Netcool Service Quality Manager provides rule files for Enterprise TRAPs issued by Tivoli Netcool Service Quality Manager.
10.2 Integrating Service Quality Manager with Tivoli Netcool OMNIbus

This section details the procedures that need to be completed to integrate Tivoli Netcool Service Quality Manager with Tivoli Netcool/Webtop application. Tivoli Netcool/Webtop allows you to view Netcool events in real time using your web browser. It works in conjunction with the Netcool/OMNIbus application to retrieve real time event data which allows you remotely monitor and manage your Netcool implementation. The Tivoli Netcool/Webtop customizable dashboards display real time performance information and event data. Integrating Tivoli Netcool Service Quality Manager with Tivoli Netcool/Webtop combines the Tivoli Netcool Service Quality Manager ability to generate SNMP traps when threshold violations are detected with the Webtop application functionality. Complete the following steps to integrate Tivoli Netcool Service Quality Manager with Tivoli Netcool OMNIbus. Note: Integrating Tivoli Netcool Service Quality Manager specific rules files may differ depending on a customer's deployment of Netcool. 1. Install these files into ${NC_RULES_HOME}/include-snmptrap directory on the OMNIbus platform:
ibm-TNSQM-MIB.include.snmptrap.rules ibm-TNSQM-MIB.adv.include.snmptrap.rules ibm-TNSQM-MIB.sev.snmptrap.lookup ibm-TNSQM-MIB.include.snmptrap.lookup ibm-TNSQM-MIB.user.include.snmptrap.rules
These files can be found in $WMCROOT/admin/omnibus/include-snmptrap on the Tivoli Netcool Service Quality Manager platform. 2. Update $NC_RULES_HOME/snmptrap.rules on the OMNIbus platform as follows: Add this Tivoli Netcool Service Quality Manager line to the lookup table Includes section:
SAG Page 98

######################################################################## ####### # Enter lookup table Includes below with the following syntax: # # include "<$NCHOME>/etc/rules/include-snmptrap/ <lookuptable>.include.snmptrap # .lookup" ######################################################################## ####### include "$NC_RULES_HOME/include-snmptrap/ibm-TNSQMMIB.include.snmptrap.lookup"
Add these Tivoli Netcool Service Quality Manager lines to the Severity lookup tables section:
######################################################################## ####### # Enter "Severity" lookup tables below with the following syntax: # # include "<$NCHOME>/etc/rules/include-snmptrap/ <lookuptable>.include.snmptrap # .lookup" ######################################################################## ####### table ibm-TNSQM-MIB_sev = "$NC_RULES_HOME/include-snmptrap/ibm-TNSQMMIB.sev.snmptrap.lookup" default = {"Unknown","Unknown","Unknown"}
Add this Tivoli Netcool Service Quality Manager line to the rules file Includes section:
################################################################### # Enter rules file Includes below with the following syntax: # # include "<$NCHOME>/etc/rules/include-snmptrap/<rulesfile>.include # .rules" ################################################################### include "$NC_RULES_HOME/include-snmptrap/ibm-TNSQMMIB.include.snmptrap.rules"
3. Update the {NC_RULES_HOME}/include-snmptrap/PreClass.snmptrap.lookup file by adding these Tivoli Netcool Service Quality Manager lines:
SNMPTRAP-ibm-TNSQM-MIB-metricaAlarmTrap_cleared SNMPTRAP-ibm-TNSQM-MIB-metricaAlarmTrap_critical SNMPTRAP-ibm-TNSQM-MIB-metricaAlarmTrap_major SNMPTRAP-ibm-TNSQM-MIB-metricaAlarmTrap_minor 4 0 0 0 0
Updated: 2009-06-23
SNMPTRAP-ibm-TNSQM-MIB-metricaAlarmTrap_indeterminate
SAG Page 99

SNMPTRAP-ibm-TNSQM-MIB-metricaAlarmTrap_warning SNMPTRAP-ibm-TNSQM-MIB-metricaAlarmTrap_unknown
0 0
Note: The exact deployment/integration logistics are different for each customer. Any changes to the Netcool framework must be completed by a knowledgeable member of staff aware of the particular customer Netcool deployment specifics.
SAG Page 100

Storage configuration
Appendix A: Storage configuration

Additional reading material
Multi-path Input/Output on AIX 5L documentation: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/ com.ibm.aix.baseadmn/doc/baseadmndita/devmpio.htm Multi-path Input/Output for AIX 5L whitepaper: http://www-03.ibm.com/systems/p/os/aix/whitepapers/multi_path.html Note: The Multi-path input/output on AIX 5L documentation URLs above are for reference purposes only. DS4000 Best Practises and Performance Tuning Guide: http://www.redbooks.ibm.com/abstracts/sg246363.html
Updated: 2009-06-23
SAG Page 101

Storage configuration
SAG Page 102
TIVOLI NETCOOL SERVICE QUALITY MANAGER AIX SYSTEM ADMINISTRATION GUIDE
Appendix B: Glossary
Table 19:
Acronym
Definition of product acronyms

Description
BO CA CD CD-ROM CLI CPU CRM CSV DBA DVD GB GUI FTP HBA HTML IT JMS JSP KQI KPI KSH LDAP LUN LVM
BusinessObjects Certification Authority Compact Disk Compact Disk - Read Only Memory Command Line Interface Central Processing Unit Custom Resource Manager Comma Separated Value Database Administrator Digital Versatile Disk Gigabytes Graphical User Interface File Transfer Protocol Host Bus Adapter HyperText Markup Language Information Technology Java Messaging Service Java Server Pages Key Quality Indicator Key Product Indicator Korn Shell Lightweight Directory Access Protocol Logical Unit Number Logical Volume Manager
Updated: 2009-06-23
SAG Page 103
TIVOLI NETCOOL SERVICE QUALITY MANAGER AIX SYSTEM ADMINISTRATION GUIDE
Table 19:
Acronym
Definition of product acronyms

Description
OLAP OS OSS PC PCI PM RAID RAM RMAN ROM SAN SAPMGR SAPMON SID SLA SLO SNMP SQL SSL SVGA TDS URL WAS XML
Online Transaction Processing Operating System Operations Support System Personal Computer Peripheral Component Interconnect Partition Maintenance Redundant Array of Inexpensive Disks Random Access Memory Oracle Recovery Manager Read Only Memory Storage Area Network Service Quality Manager Process Manager Service Quality Manager Process Monitor System Identifier Service Level Agreement Service Level Objective Simple Network Management Protocol Structured Query Language Secured Socket Layer Super Video Graphics Adapter Tivoli Directory Server Uniform Resource Locator IBM WebSphere Application Server eXtensive Markup Language
SAG Page 104
Appendix C: Notices
This 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. Consult your 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 IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility 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 grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome Minato-ku Tokyo 106-0032 Japan. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS 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
Updated: 2009-06-23
SAG Page 105
allow disclaimer of 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 made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials 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 without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 5300 Cork Airport Business Park Kinsale Road Cork Ireland. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as 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 business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
SAG Page 106
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Other company, product or service names may be trademarks or service marks of others.
Updated: 2009-06-23
SAG Page 107
SAG Page 108
SAG Page 109
IBM
Printed in the Republic of Ireland.

TNSQM v4.1.2 AIX SystemAdminstrationGuidev1.3

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TNSQM v4.1.2 AIX SystemAdminstrationGuidev1.3

Uploaded by

Copyright:

Available Formats

Netcool Service Quality Manager

AIX System Administration Guide

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

SAG Page iii

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

About this documentation

Required skills and knowledge

This guide assumes you are familiar with:

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

ALL UPPERCASE Link Bold SMALL CAPS

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

Service Quality Manager user documentation

AIX System Administration Guide

TIVOLI NETCOOL SERVICE QUALITY MANAGER SYSTEM ADMINISTRATION GUIDE

Table 2: Service Quality Manager user documentation (Continued)

Viewing the Service Quality Manager online help

Accessing publications online

2.2 Service Quality Manager hardware and software requirements

Server installation overview

Server hardware and software requirement

Customer Experience Manager minimal hardware requirements

IBM Power 550 Express Server

IBM POWER6 processor CPU HBA card Fibre-channel card

1 or 10 Gigabit Ethernet cards Internal SAS disks

install Service Quality Manager.

Software products (server)

Software products (server)

AIX 5L unzip Must be pre installed.

5.3, OS level 5300-06 or later 5.51-1 or higher

xlC RunTime Environment Must be pre installed.

Software products (server)

5.3.0.60 or higher AIX 5.3 installation media. This is the bos.adt.libm

AIX 5.3 installation media. This is the

IBM WebSphere Application Server

Tivoli Directory Server

Software products (server)

Service Quality Man- 4.1.2 ager software installation and documentation

Advantage Web site: http://www.ibm.com/ software/howtobuy/passportadvantage/

Client hardware and software requirements

Software products (client PC)

Windows operating system

Windows 2000 SP4, Windows XP and Windows 2003 10.2.0.4

CD-ROM (The customer must supply this software.)

Oracle database client (optional)

Download this software from:

Software products (optional BusinessObjects server)

Windows operating system Oracle Database client

Windows 2003 or XP 10.2.0.4

CD-ROM (The customer must supply this

Download this software from:

Software products (BusinessObjects client)

Windows operating system Oracle database client

Windows XP or Windows 2003 10.2.0.4

CD-ROM (supplied by Cus-

Download this software from:

BusinessObjects client BusinessObjects client

3 CD-ROMs or http:// www.businessobjects.com 4 CD-ROMs or http:// www.businessobjects.com

/ swap /usr /var /opt /tmp /home /appl

AIX LVM volume group 1

AIX LVM volume group 1