Embed Size (px)
Citation preview
IBM
Tivoli
Service
Level
Advisor
Administrator’s
Guide
Version
2.1
SC32-0835-03
���
IBM
Tivoli
Service
Level
Advisor
Administrator’s
Guide
Version
2.1
SC32-0835-03
���
Fourth
Edition
(September
2004)
This
edition
applies
to
Version
2.1
of
IBM
Tivoli
Service
Level
Advisor
(product
number
5724–C40)
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
2002,
2004.
All
rights
reserved.
US
Government
Users
Restricted
Rights
–
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Who
should
read
this
guide
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
IBM
Tivoli
Service
Level
Advisor
library
.
.
.
. vi
IBM
DB2
Universal
Database
Enterprise
Edition
library
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Tivoli
Data
Warehouse
library
.
.
.
.
.
.
. vii
Warehouse
Enablement
Packs
.
.
.
.
.
.
. vii
IBM
WebSphere
Application
Server
library
.
.
. vii
SLM
Administrative
Console
Information
.
.
. viii
Related
publications
.
.
.
.
.
.
.
.
.
. viii
Accessing
Publications
Online
.
.
.
.
.
.
.
. viii
Ordering
publications
.
.
.
.
.
.
.
.
.
. viii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. ix
Tivoli
technical
training
.
.
.
.
.
.
.
.
.
. ix
Contacting
IBM
Software
Support
.
.
.
.
.
.
. ix
Determine
the
business
impact
of
your
problem
. x
Describe
your
problem
and
gather
background
information
.
.
.
.
.
.
.
.
.
.
.
.
.
. x
Submit
your
problem
to
IBM
Software
Support
.
. x
Searching
knowledge
bases
.
.
.
.
.
.
.
. xi
Obtaining
fixes
.
.
.
.
.
.
.
.
.
.
.
. xi
Updating
support
information
.
.
.
.
.
.
. xii
Participating
in
newsgroups
.
.
.
.
.
.
.
.
. xii
Conventions
used
in
this
guide
.
.
.
.
.
.
. xiii
Typeface
conventions
.
.
.
.
.
.
.
.
.
. xiii
Operating
system-dependent
variables
and
paths
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xiv
Chapter
1.
Introduction
.
.
.
.
.
.
.
. 1
What
Can
I
Do
with
IBM
Tivoli
Service
Level
Advisor?
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2
How
IBM
Tivoli
Service
Level
Advisor
Works
.
.
. 3
Managing
Levels
of
Service
.
.
.
.
.
.
.
. 4
Event
Notification
.
.
.
.
.
.
.
.
.
.
. 4
Reporting
Evaluation
and
Analysis
Results
.
.
. 4
Understanding
Tivoli
Data
Warehouse
.
.
.
.
.
. 5
Moving
Data
Through
the
Data
Warehouse
.
.
. 5
Working
with
the
Warehouse
Administrator
.
.
. 9
Chapter
2.
Creating
and
Managing
Users
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 11
Managing
Users
of
the
SLM
Administrative
Console
11
Signing
on
with
WebSphere
Security
Enabled
.
. 11
Creating
Additional
Users
.
.
.
.
.
.
.
. 11
Associating
Predefined
Roles
with
Users
.
.
. 12
Associating
User
Names
with
IBM
Tivoli
Service
Level
Advisor
Roles
.
.
.
.
.
.
.
.
.
. 14
Managing
Users
of
the
SLM
Reports
Console
.
.
. 15
Properties
for
SLM
Report
Users
.
.
.
.
.
. 16
Refreshing
User
Credentials
.
.
.
.
.
.
.
.
. 18
Accessing
Log
Files
.
.
.
.
.
.
.
.
.
.
.
. 18
Chapter
3.
Customizing
the
SLM
Environment
.
.
.
.
.
.
.
.
.
.
.
. 21
Setting
Up
The
CLI
Command
Environment
.
.
. 21
Customizing
the
CLI
Service
with
the
cliutil
utility
21
Retrieving
the
CLI
Service
Port
Number
.
.
.
. 22
Setting
a
New
CLI
Service
Port
Number
.
.
.
. 22
Resetting
the
CLI
Service
Password
.
.
.
.
. 22
Changing
Database
Connection
Parameters
with
the
dsutil
Utility
.
.
.
.
.
.
.
.
.
.
.
.
.
. 22
Specifying
Valid
Parameters
.
.
.
.
.
.
.
. 23
Running
the
dsutil
Utility
on
a
Distributed
Installation
.
.
.
.
.
.
.
.
.
.
.
.
. 23
Customizing
Server
Communication
with
the
rcomutil
Utility
.
.
.
.
.
.
.
.
.
.
.
.
. 23
Reporting
Product
Version
Information
with
the
verutil
Utility
.
.
.
.
.
.
.
.
.
.
.
.
.
. 24
Chapter
4.
Miscellaneous
Administrative
Tasks
.
.
.
.
.
.
.
.
. 25
Configuring
DB2
Settings
.
.
.
.
.
.
.
.
.
. 25
Enabling
Data
Collection
for
Source
Applications
.
. 26
Configuring
and
Scheduling
ETLs
.
.
.
.
.
.
. 27
Configuring
Hourly
Evaluation
Frequency
.
.
.
. 28
Impact
on
Intermediate
Evaluations
.
.
.
.
. 29
Disabling
Hourly
Evaluation
Frequency
Selection
29
Performing
Re-Evaluations
of
Late
or
Missing
Data
29
Creating
SLM
Objects
Using
CLI
Commands
.
.
. 29
Configuring
and
Running
the
Optional
Source
ETL
for
IBM
Tivoli
Service
Level
Advisor
.
.
.
.
.
. 30
Supporting
Problem
and
Change
Management
Metrics
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Adjudicating
Violations
.
.
.
.
.
.
.
.
.
. 30
Enabling
and
Disabling
WebSphere
Security
.
.
. 30
Exporting
Evaluation
Data
to
a
Comma
Separated
Value
File
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 31
Running
the
Sample
Script
.
.
.
.
.
.
.
. 31
Exporting
Evaluation
Data
Manually
.
.
.
.
. 32
Chapter
5.
Backup
and
Restoration
Procedures
.
.
.
.
.
.
.
.
.
.
.
.
. 35
Backing
Up
Tivoli
Data
Warehouse
.
.
.
.
.
. 35
Automating
the
Backup
and
Restoration
Process
.
. 36
Backing
up
IBM
Tivoli
Service
Level
Advisor
.
.
. 36
1.
Discontinuing
Use
of
the
Registration
ETL
and
Process
ETL
.
.
.
.
.
.
.
.
.
.
.
.
. 37
2.
Backing
Up
SLM
Administrative
Console
Users
and
Associated
Roles
.
.
.
.
.
.
.
. 38
3.
Shutting
Down
IBM
Tivoli
Service
Level
Advisor
.
.
.
.
.
.
.
.
.
.
.
.
.
. 38
4.
Backing
Up
IBM
Tivoli
Service
Level
Advisor
Installation
Directories
.
.
.
.
.
.
.
.
.
. 38
5.
Backing
up
the
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor
.
.
.
.
.
. 39
©
Copyright
IBM
Corp.
2002,
2004
iii
6.
Backing
Up
the
IBM
Tivoli
Service
Level
Advisor
Databases
.
.
.
.
.
.
.
.
.
.
. 39
7.
Backing
Up
Customized
Report
JSPs
in
WebSphere
.
.
.
.
.
.
.
.
.
.
.
.
. 40
8.
Backing
Up
Tivoli
Data
Warehouse
.
.
.
.
. 41
9.
Restarting
IBM
Tivoli
Service
Level
Advisor
.
. 41
10.
Restarting
the
Registration
ETL
and
Process
ETL
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 41
Using
the
slmbackup
Script
.
.
.
.
.
.
.
.
. 41
Backup
Procedure
Quick
Reference
.
.
.
.
.
. 43
Restoring
IBM
Tivoli
Service
Level
Advisor
.
.
.
. 44
1.
Discontinuing
Use
of
the
Registration
ETL
and
Process
ETL
.
.
.
.
.
.
.
.
.
.
.
.
. 45
2.
Reinstalling
the
SLM
Server
.
.
.
.
.
.
. 45
3.
Shutting
Down
IBM
Tivoli
Service
Level
Advisor
.
.
.
.
.
.
.
.
.
.
.
.
.
. 45
4.
Restoring
the
IBM
Tivoli
Service
Level
Advisor
Installation
Directories
.
.
.
.
.
.
.
.
.
. 46
5.
Restoring
the
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor
.
.
.
.
.
. 47
6.
Reintegrating
Report
Servlets
into
WebSphere
47
7.
Restoring
The
IBM
Tivoli
Service
Level
Advisor
Databases
.
.
.
.
.
.
.
.
.
.
. 47
8.
Restoring
Tivoli
Data
Warehouse
.
.
.
.
. 49
9.
Reinstall
Language
Packs
for
SLM
Reports
and
SLM
Administration
Server
.
.
.
.
.
.
.
. 49
10.
Regenerating
the
IBM
WebSphere
Web
Server
Plug-in
Configuration
.
.
.
.
.
.
.
.
.
. 50
11.
Restarting
IBM
Tivoli
Service
Level
Advisor
50
12.
Restarting
Registration
ETL
and
Process
ETL
Processing
.
.
.
.
.
.
.
.
.
.
.
.
.
. 50
13.
Configuring
IBM
Tivoli
Service
Level
Advisor
50
14.
Running
the
Registration
ETL
and
Process
ETL
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 50
15.
Recreating
SLM
Reports
Users
Added
since
the
Last
Backup
.
.
.
.
.
.
.
.
.
.
.
. 51
16.
Restoring
Role
Information
Associated
with
SLM
Administrative
Console
Users
.
.
.
.
. 51
Using
the
slmrestore
and
slmrestorerestart
Commands
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
Restoration
Procedure
Quick
Reference
.
.
.
.
. 53
Appendix.
Notices
.
.
.
.
.
.
.
.
.
. 55
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 57
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 59
iv
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Preface
The
Administrator’s
Guide
for
IBM®
Tivoli®
Service
Level
Advisor
provides
information
on
tasks
that
you
are
responsible
for
as
an
SLM
Administrator.
In
general,
you
are
responsible
for
setting
up
users
and
roles,
performing
backups
and
restorations
of
the
SLM
solution,
and
other
tasks
needed
to
manage
the
IBM
Tivoli
Service
Level
Advisor
environment.
Who
should
read
this
guide
This
document
is
written
for
systems
administrators
and
Tivoli
Professional
Services
personnel
who
configure
and
manage
the
installed
IBM
Tivoli
Service
Level
Advisor
product
and
its
supporting
applications
in
the
enterprise
environment.
You
should
be
familiar
with
the
overall
flow
of
how
customers,
realms,
schedules,
offerings,
and
SLAs
are
created,
and
be
familiar
with
the
business
objectives
associated
with
the
IBM
service
level
management
solution.
You
should
also
be
familiar
with
the
following
areas
of
knowledge:
v
IBM
DB2®
Universal
Database™
Enterprise
Edition,
in
the
areas
of
installing
and
configuring
DB2
servers
and
clients,
creating
multiple
instances
of
DB2
Universal
Database,
cataloging
databases,
and
performing
backup
and
restoration
operations
to
protect
your
database
resources.
v
The
IBM
data
warehouse
strategy,
including
installation
and
configuration
of
Tivoli
Data
Warehouse.
v
Supported
Tivoli
applications
that
are
enabled
for
putting
data
into
the
Tivoli
Data
Warehouse
(see
the
Release
Notes
for
information
on
supported
Tivoli
applications).
v
Familiarity
with
installing
and
configuring
the
extract,
transform,
and
load
(ETL)
processes,
provided
in
warehouse
enablement
packs
that
are
associated
with
the
applications
that
put
data
into
Tivoli
Data
Warehouse.
v
IBM
WebSphere®
Application
Server,
in
the
areas
of
installing,
configuring,
and
starting
and
stopping
the
WebSphere
Application
Server
and
the
WebSphere
Administrative
Console.
v
The
z/OS®
environment,
if
you
plan
to
create
and
maintain
SLM
databases
on
a
z/OS
platform.
v
HTML
concepts
for
customizing
Java™
Server
Pages
(JSP
files)
to
generate
Web-based
reports.
As
an
SLM
Administrator
you
should
be
familiar
with
much
of
the
information
that
is
available
in
the
rest
of
the
IBM
Tivoli
Service
Level
Advisor
library,
for
reference
in
performing
your
duties
or
to
assist
other
users
who
might
come
to
you
for
help.
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Service
Level
Advisor
library
and
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online,
and
how
to
order
Tivoli
publications.
©
Copyright
IBM
Corp.
2002,
2004
v
IBM
Tivoli
Service
Level
Advisor
library
Product
information
for
using
IBM
Tivoli
Service
Level
Advisor
is
found
in
the
/tsladocs
directory
on
the
IBM
Tivoli
Service
Level
Advisor
Documentation
CD,
in
and
HTML
formats.
Inserting
the
Documentation
CD
into
a
machine
using
the
Windows®
operating
system
automatically
launches
the
Tivoli
Software
Information
Center,
from
which
you
can
access
any
of
the
available
documentation
in
softcopy
form.
The
following
documents
are
available
in
the
IBM
Tivoli
Service
Level
Advisor
library:
v
A
″Read
Me
First″
document
that
provides
a
starting
point
to
help
you
become
oriented
with
the
set
of
IBM
products
that
support
the
overall
SLM
solution,
and
some
quick
instructions
on
what
documentation
to
refer
to
as
you
begin
your
installation
of
IBM
Tivoli
Service
Level
Advisor
and
its
supporting
applications.
v
Release
Notes,
SC09-7777
This
document
provides
late-breaking
information,
such
as
problems
and
workarounds,
and
patch
availability.
v
Getting
Started,
SC32-0834
This
document
introduces
you
to
IBM
Tivoli
Service
Level
Advisor
and
provides
information
about
planning,
installing,
and
configuring
IBM
Tivoli
Service
Level
Advisor
to
run
in
your
Tivoli
enterprise
environment.
v
Managing
Service
Level
Agreements,
SC32-1247
This
document
provides
information
about
creating
and
managing
schedules,
offerings,
customers,
and
realms,
and
associating
these
elements
with
selected
resources
in
your
enterprise
environment
to
develop
service
level
agreements
(SLAs)
between
your
organization
and
customers
who
depend
on
your
enterprise
for
agreed
upon
levels
of
service.
This
document
is
designed
to
be
used
by
administrators,
service
offering
specialists,
and
service
level
agreement
specialists
who
are
responsible
for
creating
and
managing
SLAs.
v
SLM
Reports,
SC32-1248
This
document
provides
information
about
generating
and
viewing
Web-based
SLM
reports
for
IBM
Tivoli
Service
Level
Advisor,
based
on
the
evaluation
and
trend
analysis
results
of
the
data
that
is
extracted
from
the
Tivoli
Data
Warehouse
database.
Additional
information
is
provided
so
that
you
or
your
customer
can
integrate
SLM
reports
into
the
customer
Web
site,
including
examples
of
how
you
can
customize
various
display
features.
v
Administrator’s
Guide,
SC32-0835
This
document
provides
information
about
the
administrative
tasks
you
can
perform
using
IBM
Tivoli
Service
Level
Advisor
to
configure
your
SLM
environment,
and
perform
various
administrative
functions
that
support
IBM
Tivoli
Service
Level
Advisor,
such
as
backup
and
restoration
operations,
and
user
definition
and
authorization.
v
Command
Reference,
SC32-0833
This
document
provides
information
on
command
line
interface
(CLI)
commands
available
for
displaying
certain
conditions
and
states
inside
IBM
Tivoli
Service
Level
Advisor,
and
for
performing
various
configuration
tasks
using
the
scmd
command.
Additional
utilities
that
provide
other
specific
functions
are
also
described.
v
Messages,
SC32-1250
This
document
provides
information
on
messages
that
might
be
displayed
while
using
the
IBM
Tivoli
Service
Level
Advisor
product.
It
provides
additional
explanations
for
messages
and
instructions
on
what
to
do
to
recover
from
errors.
vi
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
v
Troubleshooting,
SC32-1249
This
document
provides
information
on
resolving
problems
that
you
might
encounter
during
installation
and
configuration,
as
well
as
resolving
administrative
problems
that
might
arise
during
typical
operation
of
the
product.
Information
about
message
and
trace
logging
is
also
provided.
v
Online
user
assistance
for
IBM
Tivoli
Service
Level
Advisor
The
online
user
assistance
provides
integrated
online
help
topics
for
all
IBM
Tivoli
Service
Level
Advisor
administrative
tasks
that
are
performed
using
the
SLM
Administrative
Console.
Online
user
assistance
is
displayed
in
the
Task
Assistant
portion
of
the
SLM
Administrative
Console.
Specific
information
about
performing
IBM
Tivoli
Service
Level
Advisor
tasks
is
documented
only
in
this
online
user
assistance.
When
new
products
are
installed
that
run
in
the
SLM
Administrative
Console,
corresponding
online
help
topics
are
also
installed
and
integrated
into
the
existing
information
base.
In
addition,
refer
to
the
following
IBM
Tivoli
Service
Level
Advisor
Web
site
for
support
information
and
software
updates
on
IBM
Tivoli
Service
Level
Advisor
and
supported
warehouse
packs
and
downloadable
interim
fix
software:
www.ibm.com/software/sysmgmt/products/support/IBMTivoliServiceLevelAdvisor.html
IBM
DB2
Universal
Database
Enterprise
Edition
library
The
publications
required
to
support
IBM
DB2
Universal
Database
Enterprise
Edition
are
available
on
the
IBM
DB2
Universal
Database
Enterprise
Edition
CD,
or
from
this
IBM
Web
site:
http://www.ibm.com/software/data/db2/udb
Tivoli
Data
Warehouse
library
IBM
Tivoli
Service
Level
Advisor
requires
Tivoli
Data
Warehouse
to
be
installed
in
your
enterprise,
to
serve
as
the
data
repository
for
Tivoli
performance
and
availability
monitoring
applications
that
provide
data
for
service
level
management.
See
the
following
documentation
on
the
Tivoli
Data
Warehouse
Documentation
CD
included
with
IBM
Tivoli
Service
Level
Advisor:
v
Installing
and
Configuring
Tivoli
Data
Warehouse
v
Enabling
an
Application
for
Tivoli
Data
Warehouse
v
Tivoli
Data
Warehouse
Release
Notes
Warehouse
Enablement
Packs
Warehouse
enablement
packs
(also
referred
to
as
warehouse
packs)
are
the
interfaces
that
load
and
transform
data
collected
by
source
applications
into
Tivoli
Data
Warehouse,
and
from
Tivoli
Data
Warehouse
to
other
target
applications
that
use
the
data
to
generate
reports
and
perform
analyses.
Refer
to
the
Release
Notes
for
IBM
Tivoli
Service
Level
Advisor
for
the
online
location
of
the
latest
warehouse
pack
information.
IBM
WebSphere
Application
Server
library
IBM
Tivoli
Service
Level
Advisor
uses
IBM
WebSphere
Application
Server
as
the
basis
for
the
SLM
Administration
Server
and
SLM
Reports
functions.
Getting
Started
provides
introductory
information
on
installing
IBM
WebSphere
Application
Server
and
integrating
it
with
IBM
Tivoli
Service
Level
Advisor.
See
the
official
documentation
provided
on
the
IBM
WebSphere
Application
Server
product
media
Preface
vii
included
with
IBM
Tivoli
Service
Level
Advisor
for
additional
information,
and
also
refer
to
the
latest
IBM
WebSphere
Application
Server
product
information
online
at
the
following
Web
site:
http://www.ibm.com/software/webservers/appserv/was/library
SLM
Administrative
Console
Information
IBM
Tivoli
Service
Level
Advisor
provides
the
SLM
Administrative
Console,
a
Web-based
Administration
Server
graphical
user
interface
(GUI)
that
runs
in
the
IBM
WebSphere
environment,
from
which
you
can
create
and
manage
schedules,
offerings,
customers,
realms,
and
SLAs.
Information
on
the
use
of
the
SLM
Administrative
Console
and
tasks
related
to
creating
and
managing
SLAs
are
described
in
detail
in
Managing
Service
Level
Agreements.
User
assistance
for
the
SLM
Administrative
Console
is
available
in
the
Task
Assistant
online
help
function.
Related
publications
The
following
documents
also
provide
useful
information:
The
Tivoli
Software
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Software
Glossary
is
available,
in
English
only,
at
the
following
Web
site:
http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm
Access
the
glossary
by
clicking
the
Glossary
link
on
the
left
pane
of
the
Tivoli
software
library
window.
Accessing
Publications
Online
In
addition
to
the
Documentation
CD
that
is
shipped
with
IBM
Tivoli
Service
Level
Advisor,
you
can
also
access
these
publications
online.
IBM
posts
publications
for
this
and
all
other
Tivoli
products,
as
they
become
available
and
whenever
they
are
updated,
to
the
Tivoli
software
information
center
Web
site.
Access
the
Tivoli
software
information
center
by
first
going
to
the
Tivoli
software
library
at
the
following
Web
address:
http://www.ibm.com/software/tivoli/library
Scroll
down
and
click
the
Product
manuals
link.
In
the
Tivoli
Technical
Product
Documents
Alphabetical
Listing
window,
click
the
IBM
Tivoli
Service
Level
Advisor
link
to
access
the
product
library
at
the
Tivoli
software
information
center.
Note:
If
you
documents
on
other
than
letter-sized
paper,
set
the
option
in
the
File
–>
window
that
allows
Adobe
Reader
to
letter-sized
pages
on
your
local
paper.
Ordering
publications
You
can
order
many
Tivoli
publications
online
at
the
following
Web
site:
www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi
You
can
also
order
by
telephone
by
calling
one
of
these
numbers:
v
In
the
United
States:
800-879-2755
v
In
Canada:
800-426-4968
In
other
countries,
see
the
following
Web
site
for
a
list
of
telephone
numbers:
viii
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
http://www.ibm.com/software/tivoli/order-lit/
Accessibility
Accessibility
features
help
users
with
a
physical
disability,
such
as
restricted
mobility
or
limited
vision,
to
use
software
products
successfully.
With
this
product,
you
can
use
assistive
technologies
to
hear
and
navigate
the
interface.You
can
also
use
the
keyboard
instead
of
the
mouse
to
operate
all
features
of
the
graphical
user
interface.
Tivoli
technical
training
For
Tivoli
technical
training
information,
refer
to
the
following
IBM
Tivoli
Education
Web
site:
www.ibm.com/software/tivoli/education
Contacting
IBM
Software
Support
IBM
Software
Support
provides
assistance
with
product
defects.
Before
contacting
IBM
Software
Support,
your
company
must
have
an
active
IBM
software
maintenance
contract,
and
you
must
be
authorized
to
submit
problems
to
IBM.
The
type
of
software
maintenance
contract
that
you
need
depends
on
the
type
of
product
you
have:
v
For
IBM
distributed
software
products
(including,
but
not
limited
to,
Tivoli,
Lotus®,
and
Rational®
products,
as
well
as
DB2
Universal
Database
and
WebSphere
products
that
run
on
Windows
or
UNIX®
operating
systems),
enroll
in
Passport
Advantage®
in
one
of
the
following
ways:
–
Online:
Go
to
the
following
Passport
Advantage
Web
page
and
click
How
to
Enroll:
www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home
–
By
phone:
For
the
phone
number
to
call
in
your
country,
go
to
the
following
IBM
Software
Support
Web
site
and
click
the
name
of
your
geographic
region:
techsupport.services.ibm.com/guides/contacts.html
v
For
IBM
eServer™
software
products
(including,
but
not
limited
to,
DB2
Universal
Database
and
WebSphere
products
that
run
in
zSeries®,
pSeries®,
and
iSeries™
environments),
you
can
purchase
a
software
maintenance
agreement
by
working
directly
with
an
IBM
sales
representative
or
an
IBM
Business
Partner.
For
more
information
about
support
for
eServer
software
products,
go
to
the
IBM
Technical
Support
Advantage
Web
page:
www.ibm.com/servers/eserver/techsupport.html
If
you
are
not
sure
what
type
of
software
maintenance
contract
you
need,
call
1-800-IBMSERV
(1-800-426-7378)
in
the
United
States
or,
from
other
countries,
go
to
the
contacts
page
of
the
following
IBM
Software
Support
Handbook
on
the
Web
and
click
the
name
of
your
geographic
region
for
phone
numbers
of
people
who
provide
support
for
your
location:
techsupport.services.ibm.com/guides/contacts.html
Follow
the
steps
in
this
topic
to
contact
IBM
Software
Support:
1.
Determine
the
business
impact
of
your
problem.
2.
Describe
your
problem
and
gather
background
information.
3.
Submit
your
problem
to
IBM
Software
Support.
Preface
ix
Determine
the
business
impact
of
your
problem
When
you
report
a
problem
to
IBM,
you
are
asked
to
supply
a
severity
level.
Therefore,
you
need
to
understand
and
assess
the
business
impact
of
the
problem
you
are
reporting.
Use
the
following
criteria
to
decide
on
an
appropriate
severity
level
for
your
problem:
Severity
1
Critical
business
impact:
You
are
unable
to
use
the
program,
resulting
in
a
critical
impact
on
operations.
This
condition
requires
an
immediate
solution.
Severity
2
Significant
business
impact:
The
program
is
usable
but
is
severely
limited.
Severity
3
Some
business
impact:
The
program
is
usable
with
less
significant
features
(not
critical
to
operations)
unavailable.
Severity
4
Minimal
business
impact:
The
problem
causes
little
impact
on
operations,
or
a
reasonable
circumvention
to
the
problem
has
been
implemented.
Describe
your
problem
and
gather
background
information
When
explaining
a
problem
to
IBM,
be
as
specific
as
possible.
Include
all
relevant
background
information
so
that
IBM
Software
Support
specialists
can
help
you
solve
the
problem
efficiently.
To
save
time,
know
the
answers
to
these
questions:
v
What
software
versions
were
you
running
when
the
problem
occurred?
v
Do
you
have
logs,
traces,
and
messages
that
are
related
to
the
problem
symptoms?
IBM
Software
Support
is
likely
to
ask
for
this
information.
v
Can
the
problem
be
recreated?
If
so,
what
steps
led
to
the
failure?
v
Have
any
changes
been
made
to
the
system?
(For
example,
hardware,
operating
system,
networking
software,
and
so
on.)
v
Are
you
currently
using
a
workaround
for
this
problem?
If
so,
please
be
prepared
to
explain
it
when
you
report
the
problem.
Submit
your
problem
to
IBM
Software
Support
You
can
submit
your
problem
in
one
of
two
ways:
v
Online:
Go
to
the
″Submit
and
track
problems″
page
on
the
IBM
Software
Support
site
(http://www.ibm.com/software/support/probsub.html).
Enter
your
information
into
the
appropriate
problem
submission
tool.
v
Do
you
have
logs,
traces,
and
messages
that
are
related
to
the
problem
symptoms?
IBM
Software
Support
is
likely
to
ask
for
this
information.
v
Can
the
problem
be
recreated?
If
so,
what
steps
led
to
the
failure?
v
Have
any
changes
been
made
to
the
system?
(For
example,
hardware,
operating
system,
networking
software,
and
so
on.)
v
Are
you
currently
using
a
workaround
for
this
problem?
If
so,
please
be
prepared
to
explain
it
when
you
report
the
problem.
If
the
problem
you
submit
is
for
a
software
defect
or
for
missing
or
inaccurate
documentation,
IBM
Software
Support
creates
an
Authorized
Program
Analysis
Report
(APAR).
The
APAR
describes
the
problem
in
detail.
Whenever
possible,
IBM
Software
Support
provides
a
workaround
for
you
to
implement
until
the
APAR
is
resolved
and
a
fix
is
delivered.
IBM
publishes
resolved
APARs
on
the
IBM
product
support
Web
pages
daily,
so
that
other
users
who
experience
the
same
problem
can
benefit
from
the
same
resolutions.
x
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
For
more
information
about
problem
resolution,
see
“Searching
knowledge
bases”
and
“Obtaining
fixes.”
Searching
knowledge
bases
If
you
have
a
problem
with
your
IBM
software,
you
want
it
resolved
quickly.
Begin
by
searching
the
available
knowledge
bases
to
determine
whether
the
resolution
to
your
problem
is
already
documented.
Search
the
information
center
on
your
local
system
or
network
IBM
provides
extensive
documentation
that
can
be
installed
on
your
local
machine
or
on
an
intranet
server.
You
can
use
the
search
function
of
this
information
center
to
query
conceptual
information,
instructions
for
completing
tasks,
reference
information,
and
support
documents.
Tip:
Update
your
information
center
with
the
latest
support
information.
Search
the
Internet
If
you
cannot
find
an
answer
to
your
question
in
the
information
center,
search
the
Internet
for
the
latest,
most
complete
information
that
might
help
you
resolve
your
problem.
To
search
multiple
Internet
resources
for
your
product,
expand
the
product
folder
in
the
navigation
frame
to
the
left
and
select
Support
on
the
Web.
From
this
topic,
you
can
search
a
variety
of
resources
including:
v
IBM
technotes
v
IBM
downloads
v
IBM
Redbooks®
v
IBM
DeveloperWorks
v
Forums
and
newsgroups
v
Obtaining
fixes
A
product
fix
might
be
available
to
resolve
your
problem.
You
can
determine
what
fixes
are
available
for
your
IBM
software
product
by
checking
the
product
support
Web
site:
1.
Go
to
the
IBM
Software
Support
Web
site
(http://www.ibm.com/software/support).
2.
Under
Products
A
-
Z,
select
your
product
name.
This
opens
a
product-specific
support
site.
3.
Under
Self
help,
follow
the
link
to
All
Updates,
where
you
find
a
list
of
fixes,
fix
packs,
and
other
service
updates
for
your
product.
For
tips
on
refining
your
search,
click
Search
tips.
4.
Click
the
name
of
a
fix
to
read
the
description
and
optionally
download
the
fix.
To
receive
weekly
notifications
about
fixes
and
other
news
about
IBM
products,
follow
these
steps:
1.
From
the
support
page
for
any
IBM
product,
click
My
support
in
the
upper-right
corner
of
the
page.
2.
If
you
have
already
registered,
skip
to
the
next
step.
If
you
have
not
registered,
click
register
in
the
upper-right
corner
of
the
support
page
to
establish
your
user
ID
and
password.
3.
Sign
in
to
My
support.
Preface
xi
4.
On
the
My
support
page,
click
Edit
profiles
in
the
left
navigation
pane,
and
scroll
to
Select
Preferences.
Select
a
product
family
and
select
the
appropriate
boxes
for
the
type
of
information
you
want.
5.
Click
Submit.
6.
For
notification
for
other
products,
repeat
Steps
4
and
5.
For
more
information
about
types
of
fixes,
see
the
Software
Support
Handbook
(http://techsupport.services.ibm.com/guides/handbook.html).
Updating
support
information
Information
centers
typically
include
one
or
more
support
information
plug-ins.
These
plug-ins
add
IBM
technotes
and
other
support
documents
to
the
information
center.
The
following
steps
describe
how
to
update
your
support
information
plug-ins:
1.
Go
to
the
IBM
Software
Support
Web
site
(www.ibm.com/software/support).
2.
Under
Products
A
-
Z,
select
your
product
name.
This
opens
a
product-specific
support
site.
3.
Under
Search
support
for
this
product,
type
the
keyword
phrase:
com.ibm.support.
Select
the
Download
check
box,
and
click
Submit.
4.
Check
the
search
results
for
updates
to
support
information
plug-ins.
All
support
information
plug-ins
follow
the
naming
convention,
″com.ibm.support.product.doc.″
If
an
update
is
available,
select
it
from
the
list
and
view
the
download
instructions.
5.
Save
the
attached
zip
file
to
a
temporary
location
on
your
hard
drive.
6.
Unzip
the
downloaded
file,
making
sure
that
you
retain
the
subfolders.
7.
From
the
location
where
you
unzipped
the
file,
copy
the
support
information
plug-in
folder
to
your
Eclipse
plug-ins
folder.
For
example,
if
your
IBM
software
product
is
installed
at
c:\IBM\WebSphere\,
copy
the
updated
plug-in
folder
(com.ibm.support.product.doc)
to
c:\IBM\WebSphere\eclipse\plugins.
8.
To
see
the
updated
support
information,
start
the
information
center
(or
shut
it
down
and
restart
it),
and
expand
the
Support
information
node
in
the
navigation
tree.
Participating
in
newsgroups
User
groups
provide
software
professionals
with
a
forum
for
communicating
ideas,
technical
expertise,
and
experiences
related
to
the
product.
They
are
located
on
the
Internet,
and
are
available
using
standard
news
reader
programs.
These
groups
are
primarily
intended
for
user-to-user
communication,
and
are
not
a
replacement
for
formal
support.
If
you
use
Mozilla
as
your
browser,
complete
the
following
instructions
to
access
a
newsgroup:
1.
Open
a
Mozilla
browser
window.
2.
From
the
Edit
menu,
click
Preferences.
The
Preferences
window
is
displayed.
3.
In
the
Category
view,
click
&
Newsgroups
to
display
the
&
Newsgroups
settings.
4.
Select
the
Use
Mozilla
as
the
default
application
check
box.
5.
Click
OK.
6.
Close
your
Mozilla
browser
and
then
open
it
again.
7.
Cut
and
paste
the
newsgroup
address
of
a
product
into
the
browser
Address
field,
and
press
Enter
to
open
the
newsgroup.
xii
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
If
you
use
Microsoft®
Internet
Explorer
as
your
browser,
complete
the
following
instructions
to
access
a
newsgroup:
1.
Open
an
Internet
Explorer
browser.
2.
From
the
Tools
menu,
click
Internet
Options.
3.
On
the
Internet
Options
window,
click
the
Programs
tab.
4.
In
the
Newsgroups
list,
click
the
Down
Arrow
and
then
click
Outlook
Express.
5.
Click
OK.
6.
Close
your
Internet
Explorer
browser
and
then
open
it
again.
7.
Cut
and
paste
the
newsgroup
address
of
a
product
into
the
browser
Address
field,
and
press
Enter
to
open
the
newsgroup.
You
can
find
information
on
Tivoli
Data
Warehouse
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.tivoli.enterprise-data-warehouse
You
can
find
information
on
IBM
Tivoli
Service
Level
Advisor
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.tivoli.service-level-advisor
You
can
find
information
on
DB2
Universal
Database
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.db2
You
can
find
information
on
IBM
WebSphere
Application
Server
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.websphere.application-server
Conventions
used
in
this
guide
This
guide
uses
several
conventions
for
special
terms
and
actions,
operating
system-dependent
commands
and
paths,
and
margin
graphics.
Typeface
conventions
This
guide
uses
the
following
typeface
conventions:
Bold
v
Lowercase
commands
and
mixed
case
commands
that
are
otherwise
difficult
to
distinguish
from
surrounding
text
v
Interface
controls
(check
boxes,
push
buttons,
radio
buttons,
spin
buttons,
fields,
folders,
icons,
list
boxes,
items
inside
list
boxes,
multicolumn
lists,
containers,
menu
choices,
menu
names,
tabs,
property
sheets),
labels
(such
as
Tip:,
and
Operating
system
considerations:)
v
Keywords
and
parameters
in
text
Italic
v
Citations
(titles
of
books,
diskettes,
and
CDs)
v
Words
defined
in
text
v
Emphasis
of
words
(words
as
words)
v
New
terms
in
text
(except
in
a
definition
list)
v
Variables
and
values
you
must
provide
Monospace
Preface
xiii
v
Examples
and
code
examples
v
File
names,
programming
keywords,
and
other
elements
that
are
difficult
to
distinguish
from
surrounding
text
v
Message
text
and
prompts
addressed
to
the
user
v
Text
that
the
user
must
type
v
Values
for
arguments
or
command
options
Operating
system-dependent
variables
and
paths
This
guide
uses
the
UNIX
convention
for
specifying
environment
variables
and
for
directory
notation.
When
using
the
Windows
command
line,
replace
$variable
with
%
variable%
for
environment
variables
and
replace
each
forward
slash
(/)
with
a
backslash
(
\)
in
directory
paths.
The
names
of
environment
variables
are
not
always
the
same
in
Windows
and
UNIX.
For
example,
%TEMP%
in
Windows
is
equivalent
to
$tmp
in
UNIX.
Note:
If
you
are
using
the
bash
shell
on
a
Windows
system,
you
can
use
the
UNIX
conventions.
xiv
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Chapter
1.
Introduction
This
document
provides
information
about
tasks
that
you
can
perform
in
the
role
of
SLM
Administrator.
Several
additional
user
roles
are
defined
for
other
users
to
perform
certain
operations
in
IBM
Tivoli
Service
Level
Advisor.
As
an
SLM
Administrator,
you
have
access
to
all
operations
and
tasks,
and
you
alone
have
the
authority
to
create
additional
users
and
associate
them
to
a
particular
role.
There
are
various
configuration
tasks
that
you
perform
to
manage
the
IBM
Tivoli
Service
Level
Advisor
environment,
and
other
maintenance
tasks
such
as
backup
and
restoration
of
the
overall
SLM
solution,
which
includes
IBM
Tivoli
Service
Level
Advisor,
and
its
prerequisite
applications
and
data.
You
should
be
familiar
with
the
operation
of
IBM
Tivoli
Service
Level
Advisor
together
with
Tivoli
Data
Warehouse,
and
have
an
understanding
of
the
ETL
processes
that
move
measurement
data
and
resource
information
between
source
applications,
Tivoli
Data
Warehouse,
and
IBM
Tivoli
Service
Level
Advisor.
As
an
SLM
Administrator,
you
can
also
create
and
manage
customers,
realms,
schedules,
offerings,
and
service
level
agreements
(SLAs),
and
you
can
perform
adjudication
tasks
to
exclude
a
violation
from
SLM
reports
or
reinstate
a
violation
that
was
previously
excluded.
In
addition
to
this
document,
you
should
read
and
be
familiar
with
the
other
documents
in
the
library,
in
particular
the
following:
v
Managing
Service
Level
Agreements,
which
details
the
process
flow
and
procedures
for
creating
and
managing
customers,
realms,
schedules,
offerings,
and
SLAs.
An
overview
of
the
SLM
Administrative
Console
is
given
as
well.
As
a
user
of
the
console
and
to
provide
assistance
and
direction
to
others
who
are
creating
and
managing
service
level
agreements,
you
should
be
very
familiar
with
all
of
the
tasks
described
in
this
document.
v
Command
Reference,
which
details
the
syntax
and
function
of
the
command
line
interface
(CLI)
commands
that
are
available
to
you
and
other
users,
for
obtaining
internal
status
information
on
your
SLM
environment,
as
well
as
performing
various
configuration
tasks
needed
for
your
enterprise.
Some
of
these
commands
are
described
in
this
Administrator’s
Guide.
v
SLM
Reports,
which
describe
the
various
reports
that
are
generated
from
the
evaluations
and
analyses
performed
by
IBM
Tivoli
Service
Level
Advisor.
As
an
SLM
Administrator,
you
need
to
create
and
manage
report
users
and
authorize
them
to
view
certain
reports
while
restricting
them
from
other
reports.
If
you
are
also
responsible
for
incorporating
SLM
report
JavaServer
Page
(JSP)
files
into
a
company
Web
site,
you
might
find
the
customization
information
in
this
document
helpful.
v
Troubleshooting,
which
includes
information
on
various
troubleshooting
topics
that
can
arise
during
installation
and
day
to
day
operation
of
IBM
Tivoli
Service
Level
Advisor.
Other
users
will
contact
you
for
assistance
if
they
have
problems,
and
this
can
prove
to
be
a
useful
resource
to
assist
you
in
resolving
these
problems.
©
Copyright
IBM
Corp.
2002,
2004
1
What
Can
I
Do
with
IBM
Tivoli
Service
Level
Advisor?
You
can
use
IBM
Tivoli
Service
Level
Advisor
to
create,
track,
and
manage
service
level
agreements
(SLAs)
between
your
enterprise
and
your
customers.
You
can
measure,
manage,
and
report
on
availability
and
performance
aspects
of
the
internal
infrastructure
of
your
enterprise.
With
IBM
Tivoli
Service
Level
Advisor,
you
can
more
quickly
and
efficiently
obtain
information
to
help
you
manage
network
and
application
services.
Use
the
information
from
IBM
Tivoli
Service
Level
Advisor
to
maintain
productivity
and
customer
satisfaction,
minimize
revenue
impact,
manage
costs,
and
improve
planning
by
assuring
offered
services.
You
might
already
have
various
performance
and
availability
monitoring
applications
distributed
in
your
enterprise.
These
applications
might
collect
measurement
data
and
summarize
it
into
report
form
or
provide
threshold
management,
central
event
management,
and
other
basic
monitoring
functions.
You
can
extend
these
applications
by
using
IBM
Tivoli
Service
Level
Advisor
to
do
the
following
tasks:
v
Define
offerings
that
can
be
offered
with
differentiated
service
levels
based
on
a
set
of
service
level
objectives.
v
Create
customer
profiles
and
associate
them
with
specific
service
level
agreements.
v
Set
up
a
schedule
for
the
collection,
evaluation,
and
analysis
of
the
data,
at
customized
intervals.
v
Analyze
the
data
to
detect
violations
of
SLAs
or
trends
toward
future
violations.
v
Send
notifications
when
violations
or
trends
are
detected,
so
that
support
personnel
can
take
preventive
action
and
maintain
agreed
upon
levels
of
performance
and
availability
across
your
enterprise.
v
Provide
regular
Web-based
reports
of
evaluation
results
that
might
indicate
a
need
for
corrective
action
or
to
verify
that
levels
of
service
are
being
maintained
You
also
can
administer
the
IBM
Tivoli
Service
Level
Advisor
environment
by
doing
the
following:
v
Create
and
maintain
users,
and
assign
specific
roles
to
them,
giving
them
access
to
certain
functions
of
IBM
Tivoli
Service
Level
Advisor
and
restricting
access
to
other
functions.
v
Configure
Web
reports
and
allow
customers
to
view
some
reports,
while
other
reports
might
be
restricted
for
use
by
your
Information
Technology
(IT)
organization.
v
Backup
and
restore
the
product
and
its
databases
to
protect
the
entire
IBM
Tivoli
Service
Level
Advisor
installation,
to
restore
the
IBM
Tivoli
Service
Level
Advisor
environment
to
a
known
state
in
case
of
system
or
network
problems.
v
Use
the
command
line
interface
(CLI)
commands
to
modify
certain
configuration
parameters,
examine
internal
states,
and
collect
information
that
can
help
IBM
Customer
Support
personnel
to
troubleshoot
problems.
v
Use
the
log
and
trace
functions
to
help
diagnose
problems
that
you
might
encounter,
track
status
of
order
processing,
and
provide
information
to
IBM
Customer
Support.
2
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
How
IBM
Tivoli
Service
Level
Advisor
Works
The
service
level
management
capabilities
of
IBM
Tivoli
Service
Level
Advisor
complement
the
performance
and
availability
measurement
functions
of
selected
Tivoli
products
that
are
designed
to
provide
metrics
to
a
common
data
repository.
For
example,
the
following
are
some
of
the
Tivoli
applications
that
provide
data
to
Tivoli
Data
Warehouse
for
use
by
IBM
Tivoli
Service
Level
Advisor:
v
IBM
Tivoli
Monitoring
for
Transaction
Performance
v
IBM
Tivoli
Business
Systems
Manager
v
Tivoli
Distributed
Monitoring
v
IBM
Tivoli
Enterprise
Console®
For
example,
IBM
Tivoli
Monitoring
for
Transaction
Performance
measures
the
response
time
of
a
Web
site,
breaking
a
service
into
associated
sub-applications
that
complete
an
e-business
service
transaction.
IBM
Tivoli
Service
Level
Advisor
relies
on
the
monitoring
and
measuring
functions
of
these
and
other
Tivoli
applications
and
other
vendor
software
to
gather
data
through
their
own
facilities.
Performance
and
availability
data
from
these
applications
is
kept
in
a
centralized
repository
using
Tivoli
Data
Warehouse.
See
“Understanding
Tivoli
Data
Warehouse”
on
page
5
to
learn
how
IBM
Tivoli
Service
Level
Advisor
operates
with
Tivoli
Data
Warehouse
and
what
responsibilities
that
you,
as
an
administrator,
have
in
helping
to
manage
the
data
used
by
IBM
Tivoli
Service
Level
Advisor.
The
general
flow
of
measurement
data
that
is
collected
from
source
applications
and
written
to
Tivoli
Data
Warehouse
and
then
onto
IBM
Tivoli
Service
Level
Advisor
is
illustrated
in
Figure
1.
Figure
1
shows
how
multiple
source
applications
collect
and
store
their
data
in
their
local
databases,
which
are
then
written
to
the
Tivoli
Data
Warehouse
database.
This
takes
place
on
a
specific
time
interval,
for
example,
once
per
day,
or
once
every
four
hours.
At
some
other
scheduled
time
interval,
data
of
interest
to
Figure
1.
IBM
Tivoli
Service
Level
Advisor
analyzes
performance
and
availability
data
from
multiple
source
applications
that
store
their
data
in
the
Tivoli
Data
Warehouse
database.
Chapter
1.
Introduction
3
IBM
Tivoli
Service
Level
Advisor
is
sent
to
its
local
databases,
shown
in
Figure
1
on
page
3
as
the
SLM
Database
and
SLM
Measurement
Data
Mart
(see
Getting
Started
for
more
information
on
these
databases).
IBM
Tivoli
Service
Level
Advisor
evaluates
this
data
for
violations
and
trends
toward
violations
of
SLAs,
generates
reports
of
SLA
results,
and
sends
notifications
of
violations
or
trends
to
appropriate
support
personnel
or
supporting
applications.
Managing
Levels
of
Service
The
information
collected
by
performance
and
availability
monitoring
applications
is
used
by
IBM
Tivoli
Service
Level
Advisor
to
manage
against
SLAs
associated
with
your
enterprise
customer,
which
might
be
an
individual,
a
department,
or
a
division
in
your
organization.
Analysis
of
the
data
collected,
identification
of
trends
in
service
levels,
and
generated
reports
can
be
associated
with
a
specific
enterprise
customer.
You
can
manage
your
SLAs
by
completing
the
following
steps:
1.
Create
an
offering,
defining
the
service
level
objectives
(SLOs)
to
be
measured,
and
the
associated
schedules
used
to
determine
peak
hours,
standard
hours,
off
hours,
and
other
schedule
states.
2.
Create
and
submit
an
SLA,
that
specifies
the
customer
interested
in
the
SLA,
and
associate
that
customer
with
an
available
offering.
Included
is
information
on
the
enterprise
resources
that
are
managed
in
the
SLA.
Submitting
the
SLA
means
that
the
SLOs
in
the
offering
are
now
agreed
upon
by
the
offering
provider
and
by
the
customer.
This
agreement
is
the
service
level
agreement
that
is
analyzed
and
validated.
Managing
Service
Level
Agreements
describes
the
complete
process
of
creating
schedules,
offerings,
customers,
realms,
and
SLAs,
and
provides
an
overview
of
the
process
for
creating
and
managing
your
SLAs.
Event
Notification
IBM
Tivoli
Service
Level
Advisor
automatically
creates
events
whenever
the
breach
values
for
the
specific
metrics
in
the
SLA
have
been
violated,
or
when
the
analysis
shows
a
trend
toward
a
violation.
IBM
Tivoli
Service
Level
Advisor
sends
an
SLA
notification
event
to
the
appropriate
and
responsible
resources,
using
SNMP,
Tivoli
Enterprise
Console®
events,
or
as
the
notification
mechanism.
Managing
Service
Level
Agreements
provides
more
information
on
the
evaluation
and
event
escalation
processes.
Reporting
Evaluation
and
Analysis
Results
Web-based
reports
show
results
of
the
analysis
in
graphical
form,
and
can
be
customized
by
the
enterprise.
These
reports
can
answer
the
following
questions:
v
What
level
of
service
is
being
achieved?
v
Are
the
agreements
being
met
or
violated?
v
Is
the
level
of
service
trending
toward
future
violations?
These
results
can
be
used
to
provide
executive
summaries,
aid
in
service
administration
and
planning,
help
manage
operations,
and
validate
service
levels
for
the
customer.
Web-based
reports
can
help
you
to
manage
costs,
justify
expenses,
improve
internal
customer
satisfaction,
and
provide
information
to
help
you
measure
the
business
impact
of
problems
with
your
IT
infrastructure
in
terms
of
revenue,
productivity,
and
contribution
to
the
success
of
your
business.
4
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
IBM
Tivoli
Service
Level
Advisor
can
deliver
a
report
on
any
monitored
service,
resource,
SLA,
or
customer,
and
display
it
in
your
Web
browser
for
you
to
view
or
print.
See
SLM
Reports
for
more
information
on
the
Web-based
reports
that
you
can
generate,
as
well
as
techniques
for
customizing
the
Web
pages
that
you
can
incorporate
into
a
company
Web
site.
Controlling
Access
to
SLA
Results
SLA
results
are
segregated
by
realms,
a
grouping
mechanism
to
group
customers
by
geography,
by
line
of
business,
or
other
segmentation.
SLAs
and
their
evaluation
and
trend
results
are
associated
with
a
particular
customer
and
realm,
and
customers
can
view
reports
only
in
realms
for
which
they
have
access.
You
define
realms
when
you
create
customers.
See
Chapter
2,
“Creating
and
Managing
Users,”
on
page
11
for
more
information.
Understanding
Tivoli
Data
Warehouse
A
data
warehouse
is
a
centralized
repository
where
data
from
many
different
applications
can
be
stored
together.
The
data
that
originates
from
these
source
applications
can
be
of
widely
varying
types
and
formats,
and
the
amount
of
raw,
or
unprocessed,
data
that
is
generated
can
be
very
large.
When
using
a
data
warehouse,
specialized
programs
look
at
the
entire
contents
of
databases,
then
categorize
the
information
contained
in
those
databases
according
to
broad
selection
criteria,
and
move
and
transform
the
data
into
other
databases
for
subsequent
use.
IBM
Tivoli
Service
Level
Advisor
accesses
resource
data
for
processing
service
level
agreements
from
the
Tivoli
Data
Warehouse
database.
Data
is
extracted
and
analyzed
to
determine
long-term
trends
or
associations
that
are
not
easily
recognized
using
specific
applications.
IBM
Tivoli
Service
Level
Advisor
evaluates
the
collected
measurement
data
to
detect
violations
of
SLAs
or
trends
toward
possible
violations.
Tivoli
Data
Warehouse
provides
a
specific
data
warehouse
implementation.
Performance
and
availability
data
for
resources
from
across
your
enterprise
can
be
collected
by
various
Tivoli
monitoring
applications,
such
as
IBM
Tivoli
Business
Systems
Manager,
IBM
Tivoli
Monitoring
for
Transaction
Performance,
IBM
Tivoli
Monitoring,
and
others.
This
data
is
summarized
and
stored
in
the
Tivoli
Data
Warehouse
database
to
enable
reporting
across
multiple
applications.
Tivoli
Data
Warehouse
provides
a
database
with
a
common
schema,
or
data
model,
where
performance
and
availability
data
can
be
collected
and
stored
for
long
periods
of
time,
and
later
accessed
by
applications
such
as
IBM
Tivoli
Service
Level
Advisor
for
evaluation,
historical
tracking,
and
business
impact
management.
Moving
Data
Through
the
Data
Warehouse
A
typical
data
warehouse
processing
environment
involves
source,
target,
and
intermediate
databases.
Providing
multiple
layers
or
databases
enables
their
associated
applications
to
run
independently
of
each
other,
putting
in
data
and
extracting
data
at
different
times
and
frequencies,
as
necessary.
Data
is
moved
from
source
to
intermediate
to
target
databases
by
extract,
transform,
and
load
(ETL)
steps.
These
multi-step,
automated
procedures
are
described
as
follows:
Chapter
1.
Introduction
5
Extract
A
subset
of
the
data
is
selected
from
the
source
database
according
to
the
schema,
or
data
model,
for
that
database.
Transform
The
data
is
modified,
or
transformed,
to
fit
the
schema
of
the
target
database,
or
to
summarize
or
change
it
(for
example,
generating
once-per-hour
data
from
once-per-minute
records).
Load
The
results
of
the
transform
are
placed
into
the
target
database
according
to
its
schema.
ETL
steps
are
very
flexible,
with
the
capability
to
link
together
databases
that
have
different
formats
or
to
link
databases
that
were
not
originally
designed
to
be
used
together.
Multiple
ETL
steps
can
be
run
on
one
or
more
source
databases,
extracting
different
information,
and
placing
the
transformation
of
that
data
into
one
or
more
target
databases.
With
a
central
data
warehouse
in
the
environment,
ETL
steps
that
gather
data
from
source
applications
and
place
the
data
into
the
data
warehouse
are
commonly
referred
to
as
source
ETLs,
and
the
ETL
steps
that
extract
data
from
the
data
warehouse
and
make
it
available
for
use
by
target
applications
are
referred
to
as
target
ETLs.
ETL
steps
can
be
run
several
times
during
the
day
if
needed,
but
it
is
common
for
such
intensive
data
transfer
and
manipulation
processing
to
be
done
during
hours
of
low
usage.
Source
ETLs
for
IBM
Tivoli
Service
Level
Advisor
In
the
IBM
Tivoli
Service
Level
Advisor
environment,
a
set
of
source
ETLs
for
each
source
application
are
used
to
extract
data
from
the
source
application
database
at
Figure
2.
Extract,
Transform
and
Load
(ETL)
steps
manage
warehouse
data
between
source
and
target
applications.
6
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
scheduled
intervals,
transform
the
data
into
a
generalized
format,
and
then
load
the
data
into
Tivoli
Data
Warehouse
for
later
use
by
IBM
Tivoli
Service
Level
Advisor,
as
well
as
for
long
term
storage.
For
example,
various
source
applications,
such
as
IBM
Tivoli
Monitoring,
collect
metric
data
locally
on
monitored
resources,
and
store
this
data
in
their
local
databases.
Multiple
source
ETL
steps
then
extract
data
from
these
various
source
application
databases,
transform
the
data,
and
then
load
the
results
into
the
central
data
warehouse
component
of
Tivoli
Data
Warehouse.
These
source
ETLs
are
installed
and
configured
for
use
between
the
source
applications
and
the
central
data
warehouse.
Refer
to
Installing
and
Configuring
Tivoli
Data
Warehouse
for
more
information
about
source
ETLs
and
the
warehouse
enablement
packs
in
which
they
are
provided.
Target
ETLs
for
IBM
Tivoli
Service
Level
Advisor
Between
the
central
data
warehouse
database
of
Tivoli
Data
Warehouse
and
the
local
databases
used
by
IBM
Tivoli
Service
Level
Advisor,
an
independently
scheduled
set
of
target
ETLs,
referred
to
as
the
Registration
ETL
and
the
Process
ETL,
operates
on
the
data
in
the
central
data
warehouse,
extracting,
transforming
and
loading
the
data
according
to
scheduled
intervals
that
you
establish
(in
coordination
with
the
administrator
for
Tivoli
Data
Warehouse).
This
data
includes
measurement
data
from
the
source
applications,
along
with
information
about
the
various
types
of
data
that
are
available
for
use
in
creating
and
managing
SLAs.
These
target
ETLs
are
included
with
the
IBM
Tivoli
Service
Level
Advisor
product,
and
are
installed
and
configured
in
the
Tivoli
Data
Warehouse
environment.
Refer
to
Getting
Started
for
more
information
on
installing
target
ETLs
and
configuring
them
for
use
with
IBM
Tivoli
Service
Level
Advisor.
The
Registration
ETL:
The
Registration
ETL
is
in
charge
of
moving
measurement
type
data
from
the
central
data
warehouse
to
the
SLM
Database.
The
Registration
ETL
is
also
responsible
for
moving
component
name
and
attribute
information
into
the
SLM
Database.
This
information
is
required
to
assign
resources
to
offering
components
when
creating
an
SLA.
The
possible
types
of
measurement
information
against
which
SLAs
can
be
written
is
not
predefined.
It
depends
on
what
type
of
information
is
available
in
the
Tivoli
Data
Warehouse
database,
collected
from
the
various
source
applications.
IBM
Tivoli
Service
Level
Advisor
depends
on
the
Registration
ETL
to
extract
the
various
types
of
measurement
data
that
exist
in
the
Tivoli
Data
Warehouse
database
and
make
that
data
available
for
selection
during
the
definition
of
offerings
and
SLAs.
Because
of
the
large
amount
of
information
stored
in
the
central
data
warehouse,
the
Registration
ETL
extracts
data
related
to
the
types
of
resources
that
can
be
managed
with
SLAs,
and
their
associated
measurement
types.
This
information
is
used
as
filtering
criteria
when
creating
offerings
and
SLAs.
See
Managing
Service
Level
Agreements
for
more
information
about
selecting
resource
and
measurement
types
using
these
filtering
criteria.
The
Registration
ETL
is
typically
run
when
it
is
first
installed,
to
populate
the
SLM
Database
with
available
measurements
types
before
you
can
use
IBM
Tivoli
Service
Level
Advisor
to
create
offerings
and
SLAs.
Then
it
is
run
on
a
regular
schedule
by
the
Tivoli
Data
Warehouse
administrator.
When
new
measurement
types
are
added
Chapter
1.
Introduction
7
to
the
Tivoli
Data
Warehouse,
either
from
new
source
applications
or
from
existing
source
applications,
the
Registration
ETL
should
be
run
to
capture
the
new
measurement
type
information
and
store
it
in
the
SLM
Database.
You
should
work
closely
with
your
warehouse
administrator
to
coordinate
the
scheduling
of
the
Registration
ETL
with
the
building
of
offerings
and
SLAs,
as
well
as
the
schedule
of
running
the
Process
ETL
to
make
sure
that
the
latest
information
is
available
to
IBM
Tivoli
Service
Level
Advisor.
Enabling
Data
Collection
for
Specific
Applications:
By
default,
the
Registration
ETL
does
not
collect
any
of
the
available
data
types
in
the
Tivoli
Data
Warehouse
until
they
have
been
enabled.
Only
data
from
enabled
source
applications
is
available
for
inclusion
in
offerings
and
SLAs.
If
there
are
certain
applications
for
which
you
want
to
collect
data,
you
must
enable
collection
of
data
from
these
source
applications
before
running
the
Registration
ETL.
See
Getting
Started
for
information
on
enabling
data
collection
before
running
the
Registration
ETL.
The
Process
ETL:
The
Process
ETL
is
responsible
for
moving
the
large
amounts
of
actual
measurement
data
from
Tivoli
Data
Warehouse
into
the
SLM
Measurement
Data
Mart.
This
data
is
then
evaluated
and
analyzed
by
IBM
Tivoli
Service
Level
Advisor
against
the
existing
SLAs.
The
warehouse
administrator
should
schedule
the
Process
ETL
to
run
after
all
of
the
source
ETLs
have
completed
their
processing,
writing
the
latest
measurement
data
into
the
Tivoli
Data
Warehouse
database.
The
warehouse
administrator
can
control
the
frequency
at
which
the
Process
ETL
is
run,
and
the
time
of
day
that
the
ETL
is
run,
typically
during
non-peak
hours
(to
get
the
earliest
notification
of
violations
or
trends,
the
Process
ETL
should
be
scheduled
to
run
shortly
after
midnight
on
any
given
day).
After
the
Process
ETL
moves
the
latest
measurement
data
from
the
warehouse
into
the
SLM
Measurement
Data
Mart,
SLA
evaluation
and
analysis
is
automatically
started
by
IBM
Tivoli
Service
Level
Advisor.
Schedule
the
frequency
of
the
Process
ETL
carefully:
When
setting
the
frequency
at
which
the
Process
ETL
runs,
the
warehouse
administrator
must
also
consider
the
processing
time
needed
for
IBM
Tivoli
Service
Level
Advisor
to
evaluate
and
analyze
the
data
for
existing
SLAs.
IBM
Tivoli
Service
Level
Advisor
needs
to
complete
its
processing
before
new
data
is
written
to
the
SLM
Measurement
Data
Mart.
Expiration
of
Measurement
Data:
The
SLM
Measurement
Data
Mart
contains
availability,
performance
and
utilization
data
which
is
evaluated
and
analyzed
by
IBM
Tivoli
Service
Level
Advisor.
To
prevent
this
database
from
growing
unreasonably
large,
data
in
the
SLM
Measurement
Data
Mart
is
removed
after
a
certain
amount
of
time
(that
you
can
configure).
The
default
expiration
time
is
63
days
(the
longest
possible
combination
of
two
consecutive
months
plus
one
day).
See
the
Command
Reference
for
information
on
configuring
the
expiration
time
for
data
in
the
SLM
Measurement
Data
Mart.
Note:
Data
resulting
from
SLA
evaluation
and
trend
analysis
is
stored
in
the
separate
SLM
Database,
and
does
not
expire.
Because
data
is
stored
for
long
periods
in
the
Tivoli
Data
Warehouse
database,
any
measurement
data
that
expires
from
the
SLM
Measurement
Data
Mart
can
be
recovered
from
the
Tivoli
Data
Warehouse
database
if
needed.
8
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Working
with
the
Warehouse
Administrator
The
data
warehouse
processes
are
controlled
by
a
warehouse
administrator,
who
manages
the
transfer
of
data.
The
warehouse
administrator
addresses
contention
issues
for
the
Tivoli
Data
Warehouse
database,
and
oversees
the
data
warehouse
process
to
ensure
that
ETL
steps
are
completed
in
their
assigned
time
slots.
As
the
administrator
for
IBM
Tivoli
Service
Level
Advisor,
you
must
work
closely
with
the
warehouse
administrator
to
coordinate
the
scheduling
of
the
following
activities:
v
Running
the
source
ETLs
to
collect
data
from
the
source
applications
and
writing
the
data
to
the
Tivoli
Data
Warehouse
database.
v
Running
the
Registration
ETL
on
a
regular
schedule,
after
the
source
ETLs
have
completed
writing
data
to
the
central
data
warehouse.
Be
sure
to
run
this
ETL
when
new
source
applications
or
new
data
types
become
available
in
the
Tivoli
Data
Warehouse
database.
v
Running
the
Process
ETL
for
IBM
Tivoli
Service
Level
Advisor.
The
Process
ETL
must
be
scheduled
to
run
after
all
source
ETL
processing
has
completed,
to
ensure
that
the
latest
measurement
data
is
available
for
SLA
metric
evaluation
and
trend
analysis.
Configuring
for
hourly
evaluations:
If
you
have
source
applications
that
are
writing
data
to
Tivoli
Data
Warehouse
more
than
once
per
day,
you
should
verify
that
the
source
and
target
ETLs
are
scheduled
appropriately
to
run
more
than
once
per
day
as
well.
You
can
also
enable
additional
evaluation
frequency
settings
to
evaluate
results
more
than
once
per
day,
for
example,
hourly,
or
every
four
hours.
See
“Configuring
Hourly
Evaluation
Frequency”
on
page
28
for
more
information.
v
Running
the
runstats
command
on
the
central
data
warehouse
and
SLM
Measurement
Data
Mart
database
tables
to
optimize
data
collection
performance.
See
the
Troubleshooting
document
for
more
information
on
optimizing
performance
on
data
collection.
Chapter
1.
Introduction
9
10
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Chapter
2.
Creating
and
Managing
Users
As
an
SLM
Administrator
for
IBM
Tivoli
Service
Level
Advisor,
you
can
create
and
manage
users
and
assign
specific
roles
to
these
users,
depending
on
their
responsibilities
in
managing
the
levels
of
service
in
your
enterprise
environment.
There
are
two
types
of
users
that
you
need
to
manage:
v
Users
of
the
SLM
Administrative
Console
that
are
associated
with
certain
predefined
roles
that
are
authorized
for
various
tasks
in
the
portfolio
v
Users
of
the
SLM
Reports
Console
that
are
authorized
to
access
certain
SLM
Reports
and
views
of
evaluation
results
Managing
Users
of
the
SLM
Administrative
Console
IBM
Tivoli
Service
Level
Advisor
uses
the
concept
of
role-based
access
control
to
manage
system
security
in
the
WebSphere
environment.
After
starting
the
WebSphere
Administration
Server
that
supports
the
SLM
Administration
Server
(see
Getting
Started
for
the
procedures
for
starting
and
stopping
WebSphere
Application
Server),
start
the
SLM
Administrative
Console
by
opening
a
supported
Web
browser
and
typing
the
following
Web
address:
http://<fully_qualified_machine_name>:<port>/SLMAdmin
In
the
above
Web
address,
<fully_qualified_machine_name>
is
the
fully
qualified
name
of
the
machine
where
the
SLM
Administration
Server
is
located,
such
as
myMachine.raleigh.ibm.com,
and
<port>
is
a
valid
port
number
(you
can
usually
leave
the
port
number
unspecified
to
just
use
the
default
value
of
80).
For
example:
http://myMachine.raleigh.ibm.com/SLMAdmin
Signing
on
with
WebSphere
Security
Enabled
If
WebSphere
security
has
been
enabled
for
the
WebSphere
Application
Server
that
is
supporting
the
SLM
Administration
Server
component
of
IBM
Tivoli
Service
Level
Advisor,
you
must
sign
in
with
a
valid
user
name
and
password
to
gain
access
to
the
SLM
Administrative
Console.
If
WebSphere
security
is
not
enabled,
user
authorization
and
authentication
is
not
performed,
and
the
SLM
Administrative
Console
is
displayed
and
can
be
accessed
by
all
users.
Typically
WebSphere
security
is
enabled,
and
you
can
sign
on
to
the
SLM
Administrative
Console
using
the
user
name
and
password
created
during
installation.
There
are
various
options
available
to
you
to
enable
WebSphere
security.
Consult
your
WebSphere
documentation
for
more
information
about
enabling
WebSphere
security
for
your
enterprise
environment.
You
can
see
a
simple
example
of
enabling
WebSphere
security
using
a
local
operating
system
user
registry
in
Appendix
A
of
Getting
Started.
Creating
Additional
Users
You
can
create
additional
users
and
groups
to
access
the
SLM
Administrative
Console
by
adding
them
to
the
local
operating
system
user
registry
or
other
user
directory
service,
such
as
Lightweight
Directory
Access
Protocol
(LDAP),
and
then
associating
those
users
to
predefined
roles
that
are
authorized
for
various
tasks
in
the
SLM
Administrative
Console.
©
Copyright
IBM
Corp.
2002,
2004
11
For
example,
on
Windows
2000
systems,
you
can
access
the
local
operating
system
user
registry
and
create
a
new
user
by
completing
the
following
steps:
1.
You
must
be
signed
on
to
the
Windows
operating
system
with
a
user
that
has
Administrator
privileges.
2.
Click
Start
–>
Settings
–>
Control
Panel.
3.
On
the
Control
Panel,
click
Administrative
Tools.
4.
Click
Computer
Management.
5.
Under
System
Tools,
expand
Local
Users
and
Groups.
6.
Right-click
the
Users
folderand
select
New
User.
7.
Define
the
desired
user
name,
enter
a
description,
and
specify
a
password,
then
click
Create
to
create
the
new
user
in
the
local
Windows
operating
system
user
registry.
Note:
Consult
your
operating
system
documentation
for
procedures
to
define
new
users
to
your
local
operating
system
user
registry
or
other
user
directory
service.
You
might
prefer
to
create
a
Group
instead
of
an
individual
user,
and
associate
roles
with
that
group.
Then,
as
you
create
new
users,
you
can
add
them
to
the
existing
group
and
give
all
users
in
that
group
the
same
role
authority.
Associating
Predefined
Roles
with
Users
After
you
bring
up
the
SLM
Administrative
Console
in
your
Web
browser,
the
portfolio
section
of
the
console
displays
the
set
of
tasks
that
have
been
enabled
for
the
role
to
which
your
user
name
has
been
assigned.
In
addition
to
the
general
Welcome
and
Preferences
links,
the
portfolio
tasks
are
grouped
into
two
main
sections:
v
Administer
Offerings
This
group
of
tasks
includes
creating,
managing,
and
customizing
business
and
auxiliary
schedules,
and
creating
and
managing
offerings.
v
Administer
SLAs
This
group
of
tasks
includes
creating
and
managing
customers,
realms,
and
SLAs,
along
with
some
additional
specialized
tasks
to
manage
violations
and
replace
resources
or
offerings
within
established
SLAs.
Depending
on
the
role
to
which
your
user
has
been
assigned,
you
might
see
some
or
all
of
these
tasks
in
your
portfolio.
During
installation
of
IBM
Tivoli
Service
Level
Advisor,
the
following
predefined
user
roles
are
created
for
use
with
the
SLM
Administrative
Console:
SLM
Administrator
Grants
the
user
access
to
all
tasks
related
to
creating
and
managing
schedules,
offerings,
customers,
realms,
and
SLAs,
and
managing
violations
for
display
in
SLM
reports.
The
SLM
Administrator
has
the
authority
to
perform
all
tasks
that
the
other
roles
can
perform.
For
this
role
both
the
Administer
Offerings
and
Administer
SLAs
task
groups
are
displayed
in
the
portfolio.
In
addition
to
the
above
functions
granted
to
the
SLM
Administrator
role,
users
who
act
as
SLM
Administrators
are
typically
expected
to
perform
additional
administrative
tasks
that
are
not
governed
by
this
specific
role
assignment,
such
as
creating
users
and
managing
role
assignments
for
other
users,
backup
and
restoration
of
product
code
and
measurement
12
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
data,
and
configuring
logging
and
tracing
functions.
These
tasks
are
performed
outside
of
the
SLM
Administrative
Console,
and
are
not
subject
to
being
associated
to
the
SLM
Administrator
role.
Offering
Specialist
This
role
is
authorized
to
create
and
manage
offerings
and
their
associated
business
and
auxiliary
schedules,
and
publish
them
so
they
can
be
available
for
inclusion
in
service
level
agreements.
This
user
role
does
not
have
all
the
authority
of
the
SLM
Administrator,
and
cannot
create
or
manage
customers,
realms,
or
SLAs.
For
this
role
only
the
Administer
Offerings
task
group
is
displayed
in
the
portfolio.
SLA
Specialist
This
role
is
authorized
to
create
and
manage
customers
and
realms,
and
then
associate
them
with
published
offerings,
resulting
in
the
creation
of
a
service
level
agreement
(SLA).
This
user
role
does
not
have
the
authority
of
the
SLM
Administrator,
and
cannot
create
or
manage
schedules
or
offerings.
For
this
role
only
the
Administer
SLAs
task
group
is
displayed
in
the
portfolio.
SLA
Adjudicator
This
role
is
authorized
to
exclude
violations
from
SLM
reports,
or
reinstate
excluded
violations
to
be
included
in
SLM
reports,
using
the
Manage
Violations
task
in
the
portfolio.
This
user
can
also
perform
the
tasks
of
the
SLA
Specialist.
For
this
role
only
the
Administer
SLAs
task
group
is
displayed
in
the
portfolio.
These
user
roles
are
created
for
use
with
the
SLMAdmin
application
in
the
WebSphere
environment.
You
can
view
these
roles
and
the
users
or
groups
that
have
been
associated
with
them
in
the
WebSphere
Administrative
Console
by
completing
the
following
steps:
1.
Verify
that
the
WebSphere
Administration
Server
that
supports
the
SLM
Administration
Server
is
started
(see
Getting
Started
for
more
information
on
starting
WebSphere
Application
Server).
2.
Start
the
WebSphere
Administrative
Console.
If
WebSphere
security
is
enabled,
you
might
need
to
sign
on
to
the
WebSphere
Administrative
Console
using
an
authorized
user
name
and
password.
3.
In
the
left
pane
of
the
WebSphere
Administrative
Console,
expand
Applications.
4.
Click
Enterprise
Applications.
5.
From
the
table
that
is
displayed,
click
SLMAdmin.
6.
Click
the
Configuration
tab
if
it
is
not
already
selected.
7.
Scroll
down
to
the
Additional
Properties
table
and
click
Map
security
roles
to
users/groups.
A
table
is
displayed
showing
the
roles
that
have
been
created
for
the
SLMAdmin
application
(the
SLM
Administration
Server
feature
of
IBM
Tivoli
Service
Level
Advisor),
along
with
any
users
or
groups
that
have
been
mapped
to
these
roles.
Initially
you
might
only
see
the
single
default
user
that
was
created
during
installation,
mapped
to
the
SLM
Administrator
role.
Table
1
on
page
14
shows
which
tasks
and
task
groups
in
the
portfolio
are
associated
with
each
role:
Chapter
2.
Creating
and
Managing
Users
13
Table
1.
Defined
roles
restrict
access
to
specific
task
groups
Role
Tasks
assigned
to
this
role
Task
group
in
portfolio
Offering
Specialist
v
Manage
Schedules
v
Create
Schedule
v
Manage
Offerings
v
Create
Offering
Administer
Offerings
SLA
Specialist
v
Manage
Realms
v
Create
Realm
v
Manage
Customers
v
Create
Customer
v
Manage
SLAs
v
Create
SLA
v
Manage
Violations
v
Replace
Resource
v
Replace
Offering
Administer
SLAs
SLM
Administrator
All
Offering
Specialist
tasks
and
SLA
Specialist
tasks,
plus
Customize
Schedules
Administer
Offerings
Administer
SLAs
SLA
Adjudicator
All
SLA
Specialist
tasks
listed
above
Administer
SLAs
Within
each
role,
some
specific
capabilities
and
restrictions
further
differentiate
the
tasks
that
each
role
is
authorized
to
perform.
For
example,
an
SLA
Specialist
does
not
have
the
authority
to
manage
or
create
schedules
and
offerings,
but
within
an
SLA,
the
SLA
Specialist
can
view
the
associated
offerings
and
schedules
that
have
been
included
in
the
SLA.
Similarly,
an
SLA
Specialist
can
select
the
Manage
Violations
task
from
the
portfolio
to
display
a
list
of
current
violations
and
view
their
details,
as
can
an
SLA
Adjudicator,
but
only
the
SLA
Adjudicator
can
actually
exclude
or
reinstate
a
violation.
See
the
additional
information
about
user
roles
detailed
in
the
online
user
help
information
in
the
Task
Assistant.
Associating
User
Names
with
IBM
Tivoli
Service
Level
Advisor
Roles
You
can
associate
system
users
with
IBM
Tivoli
Service
Level
Advisor
roles
(for
use
with
the
SLM
Administrative
Console)
by
completing
the
following
steps:
1.
User
names
that
you
want
to
associate
with
IBM
Tivoli
Service
Level
Advisor
roles
must
already
exist
in
the
local
operating
system
user
repository
or
other
user
directory
service
if
appropriate.
See
“Creating
Additional
Users”
on
page
11
for
an
example
of
creating
new
user
names
in
the
Windows
user
repository.
2.
Follow
the
procedure
in
“Associating
Predefined
Roles
with
Users”
on
page
12
to
display
the
available
roles
for
the
SLMAdmin
application
in
the
WebSphere
Administrative
Console.
3.
Click
the
check
box
next
to
a
role
(such
as
SLM
Administrator)
and
then
click
Lookup
Users
to
search
for
individual
users,
or
click
Lookup
Groups
to
search
for
groups
of
users.
4.
Click
Search
to
initiate
the
search
for
users
or
groups.
5.
Use
the
double
list
chooser
to
move
users
back
and
forth
between
the
Available
column
and
the
Selected
column.
6.
Click
OK
when
you
have
finished
assigning
users
and
groups
to
this
role.
14
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
7.
Assign
other
users
to
other
roles
using
the
same
procedure
and
click
OK
when
you
have
finished.
8.
You
are
returned
to
the
Configuration
tab.
Scroll
to
the
bottom
and
click
OK
again.
9.
Click
Save
in
the
tool
bar
at
the
top
of
the
console
to
save
the
changes
to
your
local
configuration.
10.
Under
Save
to
Master
Configuration,
click
Save
to
apply
the
changes
to
the
master
configuration.
11.
In
the
left
pane
of
the
console,
click
Enterprise
Applications
again.
12.
If
the
SLMAdmin
application
is
already
started
in
the
table,
select
it
and
stop
it,
then
click
Start
to
restart
it.
The
next
time
you
sign
on
to
the
SLM
Administrative
Console,
you
can
use
one
of
these
user
names
and
the
portfolio
is
displayed
with
the
appropriate
tasks
for
your
assigned
role.
Associating
Users
and
Groups
to
Roles
using
wasutil
You
can
also
use
the
wasutil
utility
to
associate
users
and
groups
to
specific
roles
for
access
to
functions
in
the
SLM
Administrative
Console.
See
the
Command
Reference
for
more
information
on
this
utility.
Managing
Users
of
the
SLM
Reports
Console
You
can
authorize
existing
users
to
view
certain
levels
of
detail
in
SLM
reports
by
using
the
scmd
report
addUser
and
scmd
report
changeUser
CLI
commands.
These
commands
are
fully
described
in
the
Command
Reference.
Create
new
users
and
authorize
them
to
access
SLM
Reports
by
completing
the
following
steps:
1.
User
names
that
you
want
to
authorize
to
access
SLM
reports
must
first
be
created
in
the
local
operating
system
user
registry
or
other
user
directory
service.
See
“Creating
Additional
Users”
on
page
11
for
information
on
creating
new
user
names
and
passwords.
2.
Use
the
scmd
report
addUser
CLI
command
to
identify
the
new
user
to
SLM
Reports
and
define
the
level
of
detail
that
the
user
sees
after
signing
on.
The
user
name
is
also
assigned
an
authorization
level
that
determines
what
SLA
data
can
be
viewed
on
each
Web
page.
You
can
also
sign
on
to
the
SLM
Reports
Console
using
the
user
name
that
was
specified
when
the
IBM
Tivoli
Service
Level
Advisor
product
was
first
installed.
See
Getting
Started
for
more
information
about
the
user
name
that
is
created
during
installation
and
authorized
to
view
SLM
Reports.
You
can
define
additional
users
with
one
of
several
levels
of
access
to
SLM
reports.
Refer
to
the
following
commands
in
the
Command
Reference
for
more
information
on
managing
report
users:
v
scmd
report
addUser
v
scmd
report
changeUser
v
scmd
report
deleteUser
v
scmd
report
listUser
Chapter
2.
Creating
and
Managing
Users
15
Properties
for
SLM
Report
Users
User
authentication
involves
the
association
of
a
user
name
and
password
with
a
particular
level
of
authorization.
SLM
Reports
uses
the
following
properties
for
user
authentication:
time
zone,
customer,
realm,
user
type,
view,
and
int.
These
properties
are
specified
when
a
report
user
is
being
created.
The
properties
are
defined
as
follows:
Time
zone
All
time
information
for
each
report
is
presented
to
you
in
the
time
zone
that
you
specify.
If
no
time
zone
is
selected,
then
the
time
zone
of
the
Report
Server
is
the
default
selection.
This
option
is
typically
used
when
an
SLA
has
been
configured
for
a
particular
user
type
that
is
located
in
a
different
time
zone
than
the
SLM
Server.
Customer
A
user
can
be
associated
with
a
particular
customer
(for
example,
company
name
ABC
Inc.)
and
only
be
allowed
to
view
report
data
for
that
particular
customer.
Realm
This
is
the
grouping
of
customers
that
is
defined
by
a
SLA
Specialist
during
the
SLA
creation
process
(see
Managing
Service
Level
Agreements
for
information
about
realms).
A
user
can
be
associated
with
a
particular
realm
(for
example,
a
geographic
region,
such
as
Eastern
United
States),
and
only
be
allowed
to
view
report
data
from
that
particular
realm.
User
Type
The
type
of
user
that
determines
the
level
of
details
that
are
displayed
when
a
user
logs
on
to
view
the
reporting
system.
You
can
configure
each
user
to
display
a
particular
high
level
summary
report.
Valid
user
types
for
this
setting
are
executive,
customer,
or
operations,
as
shown
in
Table
2.
Table
2.
Valid
values
for
User
Type
parameter
User
Type
User
Explanation
1
Operations
This
user
type
can
view
detailed
reports
from
a
day
to
day
operations
personnel
perspective.
This
is
the
default
type
if
the
user
type
is
not
specified.
2
Executive
This
user
type
can
view
high
level
executive
summary
reports.
3
Customer
This
user
type
can
view
moderately
detailed
reports
from
a
customer
point
of
view.
View
This
view
property
provides
three
levels
of
authorization,
represented
as
numbers
1,
2,
or
3,
defined
as
follows:
1
(Unrestricted)
You
can
view
any
available
data
for
all
valid
customers
and
realms.
This
is
the
default
value.
The
unrestricted
view
is
represented
by
the
value
1.
Valid
combinations
of
customer,
realm,
and
view
for
unrestricted
users
as
shown
in
Table
3:
Table
3.
Valid
combinations
of
view,
customer,
and
realm
for
unrestricted
user
authentication.
View
Customer
Realm
Description
1
Unrestricted
view
across
all
available
customers
and
realms
16
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
You
cannot
specify
a
customer
or
realm
when
a
view
is
unrestricted.
Leaving
the
view
parameter
blank
reverts
to
the
unrestricted
view.
2
(Restricted)
You
are
authorized
to
view
limited
data
that
is
associated
with
a
particular
customer
name,
a
particular
realm,
or
both.
The
value
2
represents
the
restricted
view.
Valid
combinations
of
customer,
realm,
and
view
for
restricted
users
as
shown
in
Table
4:
Table
4.
Valid
combinations
of
view,
customer,
and
realm
for
restricted
user
authentication.
View
Customer
Realm
Description
2
<customer_name>
<realm_name>
Restricted
view
of
the
specified
customer
and
realm
only.
2
<customer_name>
Restricted
view
of
the
specified
customer
across
all
realms.
2
<realm_name>
Restricted
view
of
the
specified
realm
across
all
customers
in
that
realm.
You
must
specify
a
customer
or
realm
or
both,
for
a
restricted
view.
3
(External)
This
is
an
extension
of
the
Restricted
value,
indicating
that
the
user
is
authorized
to
view
limited
data
that
might
be
restricted
to
a
particular
customer
or
realm,
but
with
the
additional
restriction
that
only
allows
data
which
has
not
been
marked
for
internal
use
only.
The
Offering
Specialist
sets
this
indication
during
creation
of
the
offering.
See
Managing
Service
Level
Agreements
for
information
on
making
metric
information
available
externally.
The
value
3
represents
the
external
view.
Valid
combinations
of
customer,
realm,
and
view
for
external
users
as
shown
in
Table
5:
Table
5.
Valid
combinations
of
view,
customer,
and
realm
for
external
user
authentication.
View
Customer
Realm
Description
3
<customer_name>
<realm_name>
You
can
view
all
external
data
that
is
only
associated
with
the
specified
customer
and
realm.
3
<customer_name>
You
can
view
all
external
data
that
is
associated
with
the
specified
customer
across
all
realms.
3
<realm_name>
You
can
view
all
external
data
that
is
associated
with
the
specified
realm
across
all
customers
in
that
realm.
3
You
can
view
all
external
data
that
is
associated
with
all
customers
and
realms.
Int
Specifies
whether
or
not
intermediate
evaluation
results
are
to
be
displayed
in
SLM
reports
for
this
user.
The
default
value
is
true.
If
this
option
is
set
to
true,
then
for
this
user
when
SLM
reports
are
displayed,
intermediate
evaluations
results
are
included,
and
identified
by
a
special
icon
in
high
Chapter
2.
Creating
and
Managing
Users
17
level
reports.
In
lower
level
reports,
this
option
controls
whether
the
Intermediate
SLO
Results
table
in
the
report
is
expanded
or
collapsed
by
default.
Click
the
arrow
next
to
the
table
title
in
the
report
to
expand
or
collapse
the
table.
Refreshing
User
Credentials
Typically
you
create
a
user
or
group
and
associate
it
to
a
particular
role,
such
as
Offering
Specialist.
After
restarting
the
SLMAdmin
or
SLMReport
application
in
WebSphere,
individual
user
names
can
be
added
to
or
removed
from
the
group,
without
restarting
the
application.
However,
if
a
new
user
is
added
to
an
existing
group,
you
might
need
to
wait
approximately
10
to
15
minutes
for
the
user
credentials
to
be
refreshed
in
WebSphere
before
you
can
attempt
to
sign
on
(you
can
also
stop
and
restart
WebSphere
Application
Server
to
refresh
user
credentials
immediately).
This
wait
time
is
in
effect
only
if
you
previously
attempted
to
sign
on
before
being
added
to
the
group.
Note
that
if
you
attempt
to
sign
on
before
the
user
credentials
are
refreshed,
the
sign
on
fails
and
the
wait
time
is
restarted.
Accessing
Log
Files
Log
files
are
stored
in
the
Tivoli
Common
Directory,
a
common
repository
for
all
Tivoli
applications
to
store
log
and
trace
message
files.
The
location
of
this
directory
is
set
when
the
first
Tivoli
application
is
installed
on
the
machine.
If
IBM
Tivoli
Service
Level
Advisor
is
the
first
application
to
be
installed
on
the
machine,
it
creates
the
Tivoli
Common
Directory
in
the
default
path
<Program_Files>\ibm\tivoi\common,
or
in
another
location
specified
by
the
user
at
install
time.
The
<Program_Files>
parameter
can
be
found
on
your
system
by
examining
the
registry:
1.
Start
regedt32
(select
Start
–>
Run,
then
enter
regedt32).
2.
Expand
the
tree
under
HKEY_LOCAL_MACHINE
and
navigate
to
SOFTWARE\Microsoft\Windows\CurrentVersion.
3.
Find
the
ProgramFilesDir
parameter.
The
value
of
this
parameter
should
be
similar
to:
C:\Program
Files
You
can
find
where
the
Tivoli
Common
Directory
has
been
created
by
looking
in
the
following
file:
v
For
Windows
systems:
<Program_Files>\ibm\tivoli\common\cfg\log.properties
v
For
UNIX
systems:
/etc/ibm/tivoli/common/cfg/log.properties
The
log
files
stored
in
the
Tivoli
Common
Directory
are
accessible
to
users
defined
as
follows:
v
On
Windows
systems,
your
Windows
NT®
user
name
must
either
have
Administrator
access
or
belong
to
the
tivoli
user
group.
You
can
add
new
users
to
the
tivoli
group
by
completing
the
following
steps:
1.
Navigate
to
the
Tivoli
Common
Directory
(the
default
is
<Program_Files>\ibm\tivoli\common)
and
right-click
on
the
folder,
then
click
Properties,
then
Security,
and
add
the
tivoli
group
to
the
authorized
access
list.
18
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
2.
If
the
Tivoli
Common
Directory
is
not
located
in
the
default
location,
the
log.properties
file
is
still
initially
created
in
<Program_Files>\ibm\tivoli\common\cfg.
You
need
to
also
add
the
tivoli
group
to
this
file,
by
navigating
to
the
file,
right-clicking
on
the
file
icon,
then
clicking
Properties,
then
Security,
and
add
the
tivoli
group
to
the
authorized
access
list.
3.
Click
Start
–>
Settings
–>
Control
Panel
–>
Users
and
Passwords.
4.
Select
the
Advanced
tab
and
then
click
the
Advanced
button
under
Advanced
User
Management.
5.
Open
the
groups
folder
and
display
the
users
who
are
already
members
of
group
tivoli,
then
add
users.v
On
UNIX
operating
systems,
the
specific
procedure
might
vary
depending
on
the
system
platform.
Consult
your
local
UNIX
operating
system
administrator
and
documentation
for
assistance
in
adding
a
new
user
to
the
tivoli
group
for
access
to
these
files.
Chapter
2.
Creating
and
Managing
Users
19
20
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Chapter
3.
Customizing
the
SLM
Environment
Several
utilities
and
CLI
commands
are
available
to
customize
the
SLM
environment.
The
available
utilities
and
commands
are
described
in
detail
in
the
Command
Reference.
The
following
utilities
are
discussed
in
this
chapter:
v
cliutil,
for
customizing
the
CLI
Service
v
dsutil,
for
changing
database
connection
parameters
v
rcomutil,
for
customizing
server
communication
v
verutil,
for
displaying
a
product
version
report
or
for
checking
the
version
of
the
product
The
following
CLI
commands
are
also
discussed
in
this
chapter:
v
scmd
etl
getApps,
for
listing
applications
recognized
by
IBM
Tivoli
Service
Level
Advisor
v
scmd
etl
enable,
for
enabling
applications
for
data
collection
v
scmd
etl
disable,
for
disabling
applications
from
data
collection
v
scmd
etl
addApplicationData,
for
adding
applications
to
the
SLM
environment
v
scmd
sdc
registerWarehouseData,
for
registering
applications
with
IBM
Tivoli
Service
Level
Advisor
for
data
collection
v
scmd
mem
showHourlyFrequencyIntervals,
a
command
to
enable
or
disable
hourly
evaluation
frequency
selections
The
following
sections
give
a
brief
overview
of
these
utilities
and
commands.
Setting
Up
The
CLI
Command
Environment
Before
running
any
CLI
commands
and
utilities,
you
must
complete
the
following
steps
to
set
up
the
CLI
command
environment:
1.
Open
a
command
prompt
window.
2.
Navigate
to
<TSLA_Dir>,
the
directory
where
IBM
Tivoli
Service
Level
Advisor
was
installed
(for
example,
C:\TSLA).
3.
Initialize
the
CLI
command
environment
by
issuing
the
following
command:
slmenv
On
UNIX
systems,
this
command
must
be
sourced,
for
example:
.
./slmenv
4.
You
should
receive
the
following
response:
set
SLMCLI_PORT=9990
You
can
now
issue
CLI
commands
and
utilities.
Customizing
the
CLI
Service
with
the
cliutil
utility
The
cliutil
utility
is
used
for
setting
the
port
on
which
the
CLI
service
listens,
retrieving
the
port
number
on
which
the
CLI
service
is
currently
listening,
and
resetting
the
CLI
service
password.
This
utility
can
be
used
when
the
CLI
service
port
needs
to
be
changed
due
to
port
sharing
conflicts,
or
simply
retrieved
for
©
Copyright
IBM
Corp.
2002,
2004
21
configuration
information.
cliutil
can
also
be
used
if
the
CLI
service
password
is
forgotten.
You
can
run
the
cliutil
resetpassword
command,
and
the
CLI
service
password
is
reset
to
the
string:
password.
The
cliutil
utility
can
only
be
run
on
the
machine
where
the
SLM
Server
is
located.
Retrieving
the
CLI
Service
Port
Number
To
use
the
cliutil
utility
for
retrieving
the
CLI
service
port
number,
enter
the
command:
cliutil
getport
This
returns
the
current
port
number,
<port_number>,
on
which
the
CLI
service
is
listening
(for
example,
9990),
as
follows:
DYKAL9187I
Current
port
for
CLI
Service:
<port_number>
Referencing
DYK:
Throughout
this
document
are
various
references
to
DYK,
which
is
the
three
character
code
assigned
to
IBM
Tivoli
Service
Level
Advisor.
Messages
related
to
this
product
are
prefaced
with
this
code,
and
references
to
IBM
Tivoli
Service
Level
Advisor
databases
and
other
objects
might
also
include
this
character
prefix.
Setting
a
New
CLI
Service
Port
Number
To
use
the
cliutil
utility
for
setting
a
new
CLI
service
port
number,
type
the
following
command,
where
<port_number>
is
the
port
on
which
the
server
listens:
cliutil
setport
<port_number>
Before
changing
this
number,
make
sure
the
port
number
is
valid
and
not
in
use
by
another
application.
Resetting
the
CLI
Service
Password
To
use
the
cliutil
utility
for
resetting
the
CLI
service
password,
enter
the
following
command:
cliutil
resetpassword
This
command
resets
the
CLI
service
password
to
password.
Changing
Database
Connection
Parameters
with
the
dsutil
Utility
The
dsutil
utility
is
used
for
configuring
the
following
database
parameters,
explained
in
detail
in
the
Command
Reference:
v
User
ID
v
Password
v
Database
URL
v
Database
JDBC
driver
v
Minimum
open
connections
v
Maximum
open
connections
Use
this
utility
when
one
of
these
database
parameters
needs
to
be
changed
for
connections
to
the
SLM
Database
(dyk_cat)
or
the
SLM
Measurement
Data
Mart
(dyk_dm)
databases.
For
example,
expired
passwords
might
be
changed.
To
use
the
dsutil
utility
to
change
datasource
configuration
parameters,
enter
a
valid
datasource
name
followed
by
any
number
of
configuration
parameters
(user
22
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
ID,
password,
URL,
driver,
minconnections,
maxconnections)
and
a
corresponding
value
for
those
parameters
in
the
format:
<ds_parameter>=<ds_value>.
For
example:
dsutil
dmt
userid=db2user
password=db2pwd
This
command
changes
the
user
ID
and
password
datasource
configuration
parameters.
The
values
entered
must
be
valid
values
for
the
database
being
accessed.
If
any
values
are
not
valid,
the
datasource
creation
returns
errors
during
SLM
Server
restart,
and
the
datasource
creation
fails.
Specifying
Valid
Parameters
The
minconnections
parameter
must
be
greater
than
0
and
less
than
or
equal
to
the
value
of
maxconnections.
If
minconnections
is
set
improperly,
the
program
returns
an
error
and
the
parameter
is
not
set.
Similarly,
the
value
of
the
maxconnections
parameter
must
be
greater
than
the
value
of
minconnections.
If
maxconnections
is
set
improperly,
the
program
returns
an
error
and
the
parameter
is
not
set.
The
maxconnections
parameter
indicates
the
maximum
allowable
database
connections
to
hold
open
for
the
application.
This
configuration
parameter
is
linked
to
the
DB2
Universal
Database
database
level
configuration
parameter
maxappls
(default
value:
200
for
dyk_cat,
200
for
dyk_dm).
The
maxappls
database
configuration
parameter
refers
to
the
maximum
number
of
concurrent
applications
that
can
be
connected
to
a
database.
Therefore,
if
you
attempt
to
increase
the
value
of
maxconnections
using
the
dsutil
utility
(the
maxconnections
default
is
25),
you
might
need
to
also
increase
the
value
of
the
maxappls
parameter.
For
the
drivers
parameter,
only
the
DB2
Universal
Database
Application
Driver
is
supported.
This
string
should
be
set
to
COM.ibm.db2.jdbc.app.DB2Driver
at
all
times.
The
dsutil
utility
only
works
when
given
a
valid
data
source
as
its
first
argument.
Valid
data
sources
are
dmt
for
the
SLM
Measurement
Data
Mart
(dyk_dm)
and
sdc
for
the
SLM
Database
(dyk_cat).
After
these
database
parameters
are
altered,
you
must
restart
the
SLM
Server,
the
SLM
Reports
or
SLM
Administration
Server
options
with
WebSphere
for
the
configuration
changes
to
take
effect.
See
the
DB2
Universal
Database
documentation
for
more
information
on
database
configuration
parameters.
Running
the
dsutil
Utility
on
a
Distributed
Installation
If
your
SLM
installation
is
distributed
among
several
machines,
you
must
run
the
dsutil
utility
on
each
separate
machine.
Customizing
Server
Communication
with
the
rcomutil
Utility
Remote
communication
occurs
between
the
SLM
Administration
Server
and
the
SLM
Server
on
port
9980
by
default.
Remote
communication
also
occurs
between
the
SLM
Reports
and
SLM
Server
components.
If
this
port
is
not
acceptable
then
it
must
be
changed
on
both
ends
of
the
communication
path
for
successful
operation.
You
should
use
the
rcomutil
utility
to
alter
the
values
for
remote
communication
in
the
SLM
Administration
Server
and
SLM
Reports,
and
use
the
scmd
rcc
CLI
command
bundle
to
make
the
corresponding
change
to
the
port
on
the
SLM
Chapter
3.
Customizing
the
SLM
Environment
23
Server.
Both
commands
require
the
new
port
number,
but
the
rcomutil
utility
also
requires
the
host
name
of
the
SLM
Server.
To
change
the
communication
port
on
the
SLM
Server
machine,
complete
the
following
steps:
1.
Set
up
the
environment
by
running
the
slmenv
command.
2.
Run
the
following
CLI
command,
where
<somePort>
is
an
available
port
number:
scmd
rcc
setPort
<somePort>
3.
Restart
the
SLM
Server.
To
change
the
communication
port
on
the
SLM
Administrative
Console
machine,
where
the
SLM
Administration
Server
is
installed,
complete
the
following
steps:
1.
Set
up
the
environment
by
running
the
slmenv
command.
2.
Run
the
following
command,
where
<SLM
Server
host
name>
is
the
host
name
of
the
SLM
Server
machine,
and
<Port>
is
the
same
port
specified
above
when
setting
the
port
on
the
SLM
Server:
rcomutil
<SLM
Server
host
name>
<Port>
3.
Restart
the
WebSphere
Application
Server
that
is
supporting
the
SLM
Administration
Server.
If
the
SLM
Reports
component
is
installed
on
a
different
machine
from
the
SLM
Administration
Server,
on
the
SLM
Reports
machine,
complete
the
following
steps:
1.
Set
up
the
environment
by
running
the
slmenv
command.
2.
Run
the
following
command,
where
<SLM
Server
host
name>
is
the
host
name
of
the
SLM
Server
machine,
and
<Port>
is
the
same
port
specified
above
when
setting
the
port
on
the
SLM
Server:
rcomutil
<SLM
Server
host
name>
<Port>
3.
Restart
the
WebSphere
Application
Server
that
is
supporting
the
SLM
Reports
component.
Reporting
Product
Version
Information
with
the
verutil
Utility
The
verutil
utility
produces
a
report
showing
the
product
version
and
the
versions
of
all
JAR
files
used
by
the
product.
You
can
use
it
to
check
the
version
of
a
particular
file,
and
check
for
JAR
files
that
are
not
consistent
with
the
current
release
or
fix
pack
level.
This
utility
is
usually
only
needed
when
you
are
providing
diagnostic
information
to
IBM
Customer
Support.
See
the
Command
Reference
for
syntax
and
usage
examples
for
these
and
other
utilities
available
to
you
with
IBM
Tivoli
Service
Level
Advisor.
24
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Chapter
4.
Miscellaneous
Administrative
Tasks
This
chapter
includes
various
miscellaneous
administrative
tasks
that
you
might
perform.
Most
of
these
tasks
use
CLI
commands
that
are
fully
described
in
the
Command
Reference,
and
are
not
repeated
here.
Other
tasks
refer
to
procedures
already
described
in
detail
in
other
documents,
such
as
Getting
Started
or
Managing
Service
Level
Agreements.
Configuring
DB2
Settings
Typically
you
should
be
able
to
use
the
default
configuration
settings
for
DB2
Universal
Database
in
your
environment,
but
you
might
need
to
modify
some
DB2
configuration
settings
if
you
are
running
IBM
Tivoli
Service
Level
Advisor
in
one
of
the
following
situations:
v
You
are
running
on
UNIX
systems
with
remote
databases.
v
You
are
running
on
Windows
systems
with
large
databases.
v
You
are
running
a
distributed
deployment
with
IBM
Tivoli
Service
Level
Advisor
located
on
one
machine
and
databases
located
on
a
separate
machine,
and
both
systems
do
not
have
the
same
version
of
DB2
Universal
Database
installed
(for
example,
the
IBM
Tivoli
Service
Level
Advisor
machine
is
running
DB2
UDB
version
7,
while
the
database
server
machine
is
running
DB2
UDB
8).
In
these
environments,
you
might
receive
a
message
stating
that
the
transaction
has
been
rolled
back
due
to
a
deadlock
or
timeout
situation.
To
avoid
this
problem,
you
might
need
to
modify
the
configuration
of
some
DB2
settings.
Before
making
any
changes
to
your
DB2
settings:
Be
sure
to
consult
with
your
database
administrator.
These
settings
might
adversely
affect
the
overall
performance
of
the
product
in
your
environment.
Also,
there
might
already
be
higher
settings
in
your
existing
configuration
than
those
provided
here,
and
the
higher
settings
should
be
adequate
to
avoid
this
problem.
After
modifying
your
configuration
settings,
you
need
to
restart
DB2
Universal
Database
for
the
changes
to
take
effect.
The
following
DB2
commands
modify
certain
settings
for
the
Database
Manager,
the
SLM
Database
(DYK_CAT)
and
the
SLM
Measurement
Data
Mart
(DYK_DM).
These
commands
must
be
issued
from
a
DB2
command
prompt
on
the
database
server
machine
where
these
databases
are
located.
v
Issue
the
following
commands
to
modify
configuration
settings
for
the
Database
Manager:
update
dbm
cfg
using
mon_heap_sz
80;
update
dbm
cfg
using
java_heap_sz
2048;
update
dbm
cfg
using
sheapthres
30000;
v
Issue
the
following
commands
to
modify
configuration
settings
for
the
SLM
Database
(DYK_CAT):
connect
to
dyk_cat
user
<username>
using
<password>
update
db
cfg
for
DYK_CAT
using
logbufsz
500;
update
db
cfg
for
DYK_CAT
using
avg_appls
5;
update
db
cfg
for
DYK_CAT
using
dbheap
6000;
update
db
cfg
for
DYK_CAT
using
sortheap
10000;
©
Copyright
IBM
Corp.
2002,
2004
25
update
db
cfg
for
DYK_CAT
using
maxappls
250;
update
db
cfg
for
DYK_CAT
using
stmtheap
4096;
update
db
cfg
for
DYK_CAT
using
num_iocleaners
4;
update
db
cfg
for
DYK_CAT
using
num_ioservers
5;
update
db
cfg
for
DYK_CAT
using
dft_prefetch_sz
32;
update
db
cfg
for
DYK_CAT
using
app_ctl_heap_sz
1024;
update
db
cfg
for
DYK_CAT
using
applheapsz
4096;
update
db
cfg
for
DYK_CAT
using
logsecond
125;
ALTER
BUFFERPOOL
IBMDEFAULTBP
SIZE
10000;
ALTER
BUFFERPOOL
SDBUFF2
SIZE
2500;
v
Issue
the
following
commands
to
modify
configuration
settings
for
the
SLM
Measurement
Data
Mart
(DYK_DM):
connect
to
dyk_dm
user
<username>
using
<password>
update
db
cfg
for
DYK_DM
using
logbufsz
4000;
update
db
cfg
for
DYK_DM
using
dbheap
6000;
update
db
cfg
for
DYK_DM
using
logfilsiz
8000;
update
db
cfg
for
DYK_DM
using
logprimary
10;
update
db
cfg
for
DYK_DM
using
logsecond
118;
update
db
cfg
for
DYK_DM
using
maxappls
250;
update
db
cfg
for
DYK_DM
using
num_iocleaners
4;
update
db
cfg
for
DYK_DM
using
num_ioservers
5;
update
db
cfg
for
DYK_DM
using
dft_prefetch_sz
32;
ALTER
BUFFERPOOL
IBMDEFAULTBP
SIZE
20000;
ALTER
BUFFERPOOL
DM_BUFF2
SIZE
5000;
v
If
your
environment
includes
a
DB2
client
on
a
UNIX
system
that
is
communicating
with
the
DB2
server,
issue
the
following
command
on
the
DB2
client
machine:
update
dbm
cfg
using
drda_heap_sz
512;
After
modifying
your
DB2
configuration
settings,
you
must
restart
DB2
Universal
Database
for
the
changes
to
take
effect.
Enabling
Data
Collection
for
Source
Applications
By
default,
the
Registration
ETL
does
not
collect
data
from
the
Tivoli
Data
Warehouse
database
until
one
or
more
source
applications
have
been
added
to
the
SLM
environment
and
enabled
for
data
collection.
Only
data
types
from
source
applications
that
are
part
of
the
SLM
environment
and
that
are
enabled
are
recognized
by
IBM
Tivoli
Service
Level
Advisor
during
offering
and
order
creation.
The
procedures
for
enabling
data
collection
for
source
applications
includes
the
following
tasks:
v
Displaying
source
applications
that
have
been
added
to
the
SLM
environment,
using
the
scmd
etl
getApps
CLI
command
v
Enabling
existing
source
applications
for
data
collection,
using
the
scmd
etl
enable
CLI
command
v
Enabling
support
for
transaction
success
rate
derived
metrics,
by
running
a
special
script
26
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
v
Adding
new
source
applications
to
the
SLM
environment,
using
the
scmd
etl
addApplicationData
CLI
command
v
Finding
the
measurement
source
code
for
an
application
v
Disabling
source
applications
to
prevent
data
collection,
using
the
scmd
etl
disable
CLI
command.
v
Registering
measurement
type
data
using
the
scmd
sdc
registerWarehouseData
CLI
command
Refer
to
Chapter
5
of
Getting
Started
for
more
information
on
these
procedures,
and
refer
to
the
Command
Reference
for
additional
details
on
these
and
other
CLI
commands.
Configuring
and
Scheduling
ETLs
As
an
SLM
Administrator
you
should
have
an
understanding
of
your
general
SLM
environment,
including
the
following
information:
v
Knowing
which
source
applications
are
collecting
monitoring
data
in
your
enterprise
environment,
and
the
types
of
metric
data
being
collected,
and
the
frequency
of
data
collection
(which
has
a
direct
impact
on
how
often
this
data
is
evaluated
in
IBM
Tivoli
Service
Level
Advisor).
v
Understanding
the
ETL
processes
for
each
source
application
that
extract
the
measurement
data
from
the
source
application
local
storage,
transform
that
data
into
a
usable
format,
and
then
load
the
resulting
data
into
the
central
data
warehouse
of
Tivoli
Data
Warehouse.
You
should
be
aware
of
when
all
source
ETLs
are
scheduled
to
run,
to
ensure
that
all
measurement
data
is
written
into
the
central
data
warehouse
before
IBM
Tivoli
Service
Level
Advisor
extracts
it
for
evaluation.
v
Understanding
the
Tivoli
Data
Warehouse
configuration,
which
could
include
one
to
four
separate
central
data
warehouse
databases,
each
collecting
measurement
data
from
different
source
applications,
on
both
distributed
and
OS/390®
systems.
v
Understanding
the
function
of
the
target
ETLs
provided
with
IBM
Tivoli
Service
Level
Advisor,
that
extract
resource
type
information
and
measurement
data
for
evaluation
and
trend
analysis.
You
should
be
aware
of
the
critical
requirement
that
these
target
ETLs
must
be
scheduled
to
run
after
all
of
the
source
application
data
has
been
successfully
written
into
the
central
data
warehouse,
and
that
the
frequency
of
running
these
target
ETLs
coincides
with
the
frequency
with
which
measurement
data
is
written
into
Tivoli
Data
Warehouse.
Chapter
5
of
Getting
Started
describes
how
to
schedule,
configure,
and
run
the
target
ETLs
provided
with
IBM
Tivoli
Service
Level
Advisor,
including
the
Registration
ETL,
the
Process
ETL,
and
the
Purge
ETL.
You
should
also
consult
the
Warehouse
Enablement
Pack
documentation
for
each
of
your
source
applications
to
understand
how
each
source
application
ETL
operates,
and
refer
to
the
documentation
for
Tivoli
Data
Warehouse
for
central
data
warehouse
configuration
and
warehouse
enablement
pack
installation
information.
If
your
organization
has
a
warehouse
administrator,
check
to
see
how
source
and
target
ETLs
are
being
scheduled,
and
be
sure
to
coordinate
the
configuration
of
evaluations
and
trend
analysis
for
your
offerings
and
SLAs
in
IBM
Tivoli
Service
Level
Advisor
to
operate
correctly
in
this
overall
SLM
environment.
Chapter
4.
Miscellaneous
Administrative
Tasks
27
Configuring
Hourly
Evaluation
Frequency
During
the
offering
creation
process,
when
you
include
metrics
as
part
of
the
offering,
you
also
specify
the
frequency
at
which
evaluations
are
performed
to
determine
if
violations
or
trends
toward
violations
are
occurring
against
the
specified
service
level
objective.
The
frequency
of
evaluations
depends
on
how
often
data
is
written
to
Tivoli
Data
Warehouse
by
the
source
application
ETLs.
Most
ETLs
are
designed
to
write
data
as
often
as
once
per
day.
Even
if
a
source
application
is
collecting
data
multiple
times
per
day,
it
might
be
configured
to
summarize
the
data
points
for
the
day
into
a
single
datapoint
that
is
written
to
Tivoli
Data
Warehouse.
For
these
typical
ETLs,
the
typical
evaluation
frequencies
of
Daily,
Weekly,
and
Monthly
are
appropriate
to
select
for
your
offering.
However,
some
ETLs
might
actually
write
data
more
than
once
per
day
to
Tivoli
Data
Warehouse.
For
example,
you
might
have
a
polling
function
that
checks
availability
of
a
resource,
with
this
data
being
written
to
Tivoli
Data
Warehouse
every
hour
or
every
4
hours.
In
this
case,
you
might
want
to
specify
evaluations
to
occur
on
an
hourly
basis
(or
every
4
hours).
Of
course,
your
Registration
and
Process
target
ETLs
(the
ETLs
that
move
data
from
Tivoli
Data
Warehouse
to
the
SLM
databases
for
use
by
IBM
Tivoli
Service
Level
Advisor)
must
also
be
scheduled
to
run
at
this
frequency
as
well,
to
collect
the
data
for
each
hourly
evaluation.
In
addition
to
the
typical
evaluation
frequencies
of
Daily,
Weekly,
and
Monthly
that
you
can
select
during
offering
creation,
you
can
enable
the
following
hourly
evaluation
frequencies
that
you
can
select
to
include
with
your
metric
definition:
v
Hourly
v
Every
2
hours
v
Every
3
hours
v
Every
4
hours
v
Every
6
hours
v
Every
8
hours
v
Every
12
hours
You
can
enable
these
additional
evaluation
frequencies
by
using
the
scmd
mem
showHourlyFrequencyIntervals
command.
After
initializing
the
CLI
command
environment,
enable
hourly
evaluations
by
issuing
the
following
command:
scmd
mem
showHourlyFrequencyIntervals
enable
The
next
time
you
enter
the
offering
creation
process
and
include
metrics,
the
selection
list
for
Evaluation
Frequency
includes
these
additional
hourly
evaluation
frequencies.
Enable
hourly
evaluation
frequencies
only
for
hourly
data:
You
should
only
enable
these
evaluation
frequencies
if
you
have
source
applications
enabled
for
IBM
Tivoli
Service
Level
Advisor
that
write
data
to
Tivoli
Data
Warehouse
more
than
once
per
day.
You
should
check
the
Data
Warehouse
Center
to
verify
how
often
the
associated
source
and
target
ETLs
are
scheduled
to
run.
You
might
also
need
to
consult
with
your
database
administrator
or
other
personnel
in
your
organization
who
are
familiar
with
how
the
source
application
works,
and
refer
to
the
source
application
documentation
for
additional
information.
28
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Impact
on
Intermediate
Evaluations
If
you
select
one
of
these
hourly
evaluation
frequencies
for
your
metric,
you
cannot
also
perform
intermediate
evaluations.
Under
the
Advanced
Metric
Settings
portion
of
the
offering
creation
process
is
an
option
to
enable
intermediate
evaluations.
This
check
box
is
disabled
when
you
select
one
of
these
hourly
evaluation
frequencies.
Disabling
Hourly
Evaluation
Frequency
Selection
To
disable
these
additional
hourly
evaluation
frequency
selections,
issue
the
following
command:
scmd
mem
showHourlyFrequencyIntervals
disable
The
next
time
you
enter
the
offering
creation
process,
the
selection
list
for
Evaluation
Frequency
contains
only
the
original
Daily,
Weekly,
and
Monthly
evaluation
frequency
selections.
Previously
defined
offerings:
This
change
applies
only
to
the
creation
of
new
offerings.
If
you
have
previously
defined
offerings
that
include
these
hourly
evaluation
frequency
settings,
they
are
unaffected
by
this
disable
operation,
and
continue
to
evaluate
on
the
selected
hourly
frequency
interval.
Performing
Re-Evaluations
of
Late
or
Missing
Data
If
for
some
reason
your
source
or
target
ETLs
were
not
configured
and
scheduled
correctly,
or
if
the
source
ETLs
experienced
other
problems
that
prevented
them
from
writing
their
measurement
data
into
Tivoli
Data
Warehouse
when
expected,
you
might
have
missing
data
conditions
in
the
database,
or
late
data
arriving
after
the
intended
evaluation
period.
Use
the
scmd
mem
reEval
CLI
command
to
perform
a
reevaluation
of
the
data
after
the
Registration
and
Process
ETLs
have
retrieved
the
late
or
previously
missing
data
from
the
central
data
warehouse.
This
command
and
procedure
is
fully
described
in
the
Command
Reference.
Creating
SLM
Objects
Using
CLI
Commands
Usually
you
or
your
Offering
Specialists
and
SLA
Specialists
use
the
SLM
Administrative
Console
to
create
schedules,
offerings,
customers,
realms,
and
SLAs
(also
referred
to
in
this
documentation
as
SLM
objects).
However,
you
might
find
proceeding
through
the
wizard
steps
in
the
console
inconvenient
if
you
are
creating
many
similar
SLM
objects,
such
as
schedules
or
offerings,
with
only
minor
changes
between
them.
It
is
more
efficient
to
create
a
template
object
and
then
use
it
repeatedly
to
make
only
the
changes
that
you
want
for
each
new
object
that
you
are
creating.
This
technique
of
creating
many
SLM
objects
from
a
template
object
is
available
using
CLI
commands.
See
the
Appendices
in
Managing
Service
Level
Agreements
for
more
information,
and
refer
to
the
Command
Reference
for
the
CLI
commands
in
the
scmd
som
bundle.
Chapter
4.
Miscellaneous
Administrative
Tasks
29
Configuring
and
Running
the
Optional
Source
ETL
for
IBM
Tivoli
Service
Level
Advisor
In
addition
to
the
target
ETLs
provided
with
IBM
Tivoli
Service
Level
Advisor
that
are
used
to
extract
measurement
data
from
Tivoli
Data
Warehouse
for
evaluation,
IBM
Tivoli
Service
Level
Advisor
also
provides
an
optional
source
ETL
that
you
can
use
to
write
certain
IBM
Tivoli
Service
Level
Advisor
data
back
into
the
central
data
warehouse
of
Tivoli
Data
Warehouse
for
possible
use
by
other
applications.
This
source
ETL
is
contained
in
a
separate
warehouse
enablement
pack
that
is
provided
with
IBM
Tivoli
Service
Level
Advisor,
and
is
fully
described
in
Chapter
5
of
Getting
Started.
See
also
the
IBM
Tivoli
Service
Level
Advisor,
Version
2.1
Warehouse
Enablement
Pack,
Version
210.1.2.0
Implementation
Guide
for
additional
information
on
this
warehouse
pack.
Supporting
Problem
and
Change
Management
Metrics
For
certain
source
applications
that
support
problem
and
change
management
metrics,
the
measurement
data
that
is
stored
in
the
SLM
Database
might
need
to
be
kept
for
longer
periods
of
time
than
other
types
of
measurement
data.
Typically
an
expiration
time
of
approximately
2
months
(63
days)
is
set
as
the
default
for
expiring
normal
data,
while
problem
and
change
management
data
is
set
to
expire
after
365
days.
Expired
data
is
then
purged
from
the
SLM
Database
using
the
scheduled
Purge
ETL
to
remove
this
older
data
and
prevent
the
SLM
Database
from
growing
too
large
over
time.
You
can
configure
the
expiration
time
periods
for
typical
and
longer
term
data
by
using
the
scmd
etl
setDataExpiration
CLI
command.
See
the
Command
Reference
for
details
on
this
and
other
CLI
commands,
and
refer
to
Getting
Started
for
more
information
on
the
Purge
ETL.
Adjudicating
Violations
As
an
SLM
Administrator
you
have
the
authority
to
adjudicate
violations
that
have
been
reported
and
stored
in
the
SLM
Database
as
a
result
of
evaluations.
Using
the
Manage
Violations
function
in
the
portfolio
of
the
SLM
Administrative
Console,
you
can
select
specific
violations
and
exclude
them
from
reports,
or
reinstate
violations
that
have
been
previously
excluded.
This
function
is
typically
performed
after
consultation
with
your
customer,
to
resolve
problems
that
might
arise
with
violations
that
have
been
reported
but
are
later
determined
to
be
not
valid
for
reporting
purposes.
See
Managing
Service
Level
Agreements
for
more
information
on
adjudicating
violations.
Enabling
and
Disabling
WebSphere
Security
When
IBM
WebSphere
Application
Server
is
installed
as
a
prerequisite
to
installing
IBM
Tivoli
Service
Level
Advisor,
WebSphere
security
is
usually
enabled,
to
provide
authentication
functions
for
users
signing
on
to
the
SLM
Administrative
Console
and
SLM
Reports.
If
WebSphere
security
has
not
been
enabled,
or
if
you
need
to
disable
WebSphere
security,
consult
the
WebSphere
documentation
for
more
information.
30
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Exporting
Evaluation
Data
to
a
Comma
Separated
Value
File
You
might
want
to
export
the
report
data
from
the
SLM
Database
to
a
comma
separated
value
(CSV)
file
for
use
with
other
applications
in
analyzing
IBM
Tivoli
Service
Level
Advisor
data.
The
IBM
Tivoli
Service
Level
Advisor
product
provides
a
script
you
can
run
to
export
the
various
tables
of
interest
into
a
CSV
file,
or
you
can
export
tables
manually
using
either
of
the
following
procedures.
Sample
script:
The
script
provided
for
your
use
is
a
sample
script
that
you
might
need
to
modify
for
your
own
use.
Running
the
Sample
Script
The
script
is
called
exp_evaluation,
and
is
located
on
the
IBM
Tivoli
Service
Level
Advisor
product
CD,
in
the
\database\scripts\<OS>
directory,
where
<OS>
is
the
operating
system
platform
for
your
machine.
The
sample
export
scripts
assume
that
the
SLM
Database
is
created
with
the
name
dyk_cat.
If
you
create
the
SLM
Database
under
a
different
name,
you
can
export
the
tables
manually,
or
modify
the
sample
script
to
reference
your
SLM
Database
name.
To
run
the
exp_evaluation
script
to
automatically
export
your
evaluation
data
into
CSV
files,
complete
the
following
steps:
1.
Start
up
a
DB2
command
prompt
environment:
v
For
Windows
systems,
click
Start
–>
Run,
and
type
db2cmd.
v
For
UNIX
systems,
source
the
db2profile
by
running
the
following
command,
where
<DB2_instance_dir>
is
the
DB2
Universal
Database
instance
directory:
.
/<DB2_instance_dir>/sqllib/db2profile
2.
Insert
the
IBM
Tivoli
Service
Level
Advisor
product
CD.
If
you
are
running
on
UNIX
systems,
mount
the
CD.
3.
Navigate
to
the
appropriate
\<OS>
directory
for
your
operating
system.
v
For
Windows
systems,
run
the
following
command:
exp_evaluation
<db2_userid>
<db2_passwd>
<dir_name>
In
this
command,
<db2_userid>
is
the
user
ID
of
the
instance
owner
where
the
SLM
Database
resides,
<db2_passwd>
is
the
password
for
the
instance
owner,
and
<dir_name>
is
the
fully
qualified
name
of
the
directory
where
the
table
data
is
exported.
v
For
UNIX
systems,
run
the
following
command
(you
are
prompted
for
the
user
ID,
password,
and
target
file
name):
.
exp_evaluation.sh
Keep
in
mind
the
following:
–
You
must
be
the
owner
of
the
target
directory
where
the
export
files
are
being
created,
or
you
receive
the
following
error:
SQL3001C
An
I/O
error
(reason
=
"sqlofopn
-14847")
occurred
while
opening
the
output
file.
–
If
the
target
directory
that
you
specify
does
not
already
exist,
the
script
prompts
you
to
create
the
directory.
If
you
do
not
create
the
directory,
the
script
exits
and
no
tables
are
exported.
You
can
verify
that
the
sample
script
ran
properly
by
checking
that
the
directory
to
which
the
tables
were
exported
contains
24
text
files
from
the
export
operations.
The
file
names
correspond
with
the
names
of
the
tables
that
are
exported.
This
Chapter
4.
Miscellaneous
Administrative
Tasks
31
sample
script
does
not
support
the
SLM
Database
that
is
defined
on
a
DB2
Universal
Database
for
OS/390
and
z/OS
system
because
it
uses
the
delimited
ASCII
(DEL)
data
type
format.
Exporting
Evaluation
Data
Manually
If
you
do
not
use
the
sample
script
provided,
manually
export
evaluation
data
by
completing
the
following
steps:
1.
Open
a
DB2
command
prompt:
v
For
Windows,
select
Start
–>
Run,
and
enter
db2cmd
v
For
UNIX,
source
the
db2profile
by
running
the
following
command,
where
<DB2_instance_dir>
is
the
DB2
Universal
Database
instance
directory:
.
/<DB2_instance_dir>/sqllib/db2profile
2.
Connect
to
the
SLM
Database
by
issuing
the
following
command:
db2
connect
to
dyk_cat
user
<db2user>
using
<db2password>
In
this
command
the
db2user
is
the
DB2
Universal
Database
user
ID
and
db2password
is
the
associated
password
for
that
user
ID.
3.
Run
the
following
command,
where
<file_name>
is
the
fully
qualified
name
of
the
file
to
which
you
are
exporting
the
data,
and
<table_name>
is
the
name
of
the
table
to
export:
v
For
Windows
systems:
db2
export
to
<file_name>
of
del
select
*
from
<table_name>
v
For
UNIX
systems:
db2
export
to
<file_name>
of
del
select
\*
from
<table_name>
4.
When
you
complete
exporting
all
tables,
disconnect
from
the
SLM
Database
by
issuing
the
following
command:
db2
disconnect
current
Export
the
following
table
names:
v
agreement_viol
v
consumer
v
customer_realm
v
cust_order
v
metric_def
v
metric
v
monitoring_result
v
offering_order
v
offrg_elmt
v
order_prop
v
order_elmt
v
quarter_date
v
realm
v
resultview
v
schedule
v
schedule_hierachy
v
schedule_period
v
schedule_state
32
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
v
spec_def
v
svc_offrg
v
trend
v
trendview
v
user_info
v
violationview
Exporting
tables:
Each
time
the
DB2
Universal
Database
export
command
runs,
the
file
that
the
table
is
exported
to
is
overwritten
and
all
previous
data
in
that
file
is
lost.
You
might
receive
a
DB2
Universal
Database
warning
message
SQL3100W
for
certain
table
exports.
This
warning
indicates
that
a
character
column
with
a
length
greater
than
254
is
being
exported.
You
can
ignore
this
message.
For
example,
to
export
the
offering_order
table
to
a
CSV
file
on
Windows
systems,
issue
a
command
similar
to
the
following
example:
db2
export
to
C:\CSVFiles\OfferingOrder.csv
of
del
select
*
from
offering_order
Repeat
the
DB2
Universal
Database
export
command
for
each
table
that
you
want
to
export.
Using
Integrated
Exchange
Format
to
Export
Evaluation
Data
Manually
to
a
DB2
Universal
Database
for
z/OS
and
OS/390
You
can
manually
export
evaluation
data
for
DB2
Universal
Database
for
z/OS
and
OS/390
by
using
the
Integrated
Exchange
Format
(IXF).
You
can
export
to
an
IXF-formatted
file
and
then
import
into
a
temporary
(sample)
database
on
a
distributed
system
that
you
can
use
to
create
a
CSV
file.
To
export
to
an
IXF-formatted
file
and
create
a
CSV
file,
complete
the
following
steps:
1.
Create
a
sample
database
on
a
distributed
system:
db2
create
database
mydata
using
codeset
UTF-8
territory
en
2.
Connect
to
the
SLM
Database
on
OS/390
or
z/OS:
db2
connect
to
dykcat
user
user1
using
db2test
3.
Export
the
data
in
IXF
format
from
the
dykcat
database
on
OS/390
or
z/OS:
db2
export
to
agreement_viol.ixf
of
ixf
select
*
from
agreement_viol
Repeat
this
step
for
each
table,
for
example,
agreement_viol,
using
different
table
and
file
names
each
time
you
run
the
utility.
4.
Disconnect
from
dykcat
on
OS/390
or
z/OS:
db2
disconnect
dykcat
5.
End
the
back-end
process
for
the
command
line
processor
because
you
are
switching
from
connecting
to
a
OS/390
or
z/OS
location
to
a
distributed
database:
db2
terminate
6.
Connect
to
a
sample
database
on
distributed
system:
db2
connect
to
mydata
user
db2admin
using
db2test
7.
Import
data
into
a
distributed
database:
db2
import
from
agreement_viol.ixf
of
ixf
create
into
agreement_viol
Repeat
this
step
for
each
file
you
created
in
Step
3.
8.
Follow
the
procedures
for
exporting
to
a
CSV
file
from
the
preceding
″Exporting
Evaluation
Data
Manually″
section.
9.
Disconnect
from
the
database:
Chapter
4.
Miscellaneous
Administrative
Tasks
33
db2
disconnect
mydata
34
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Chapter
5.
Backup
and
Restoration
Procedures
Backup
and
restoration
procedures
are
available
to
help
you
preserve
and
maintain
your
IBM
Tivoli
Service
Level
Advisor
solution.
These
procedures
manage
all
of
the
data
and
operational
files
necessary
to
restore
IBM
Tivoli
Service
Level
Advisor
to
a
usable
state.
You
might
already
be
following
established
procedures
for
backup
and
restoration
of
your
enterprise
environment,
or
you
might
already
be
using
a
comprehensive
storage
management
solution
that
satisfies
the
needs
of
your
environment.
If
so,
then
this
chapter
might
simply
serve
as
a
guideline
to
help
you
ensure
that
information
vital
to
IBM
Tivoli
Service
Level
Advisor
is
backed
up
and
restored
as
needed.
If
you
do
not
already
have
an
established
backup
and
restoration
procedure,
then
the
procedure
described
in
this
chapter
should
be
adequate
for
your
needs.
Before
implementing
any
backup
and
restoration
procedure,
consult
with
your
local
system
administrators
to
determine
the
best
course
of
action.
Backups
should
be
performed
on
a
regular
basis
as
part
of
regular
system
maintenance
activities.
Using
the
IBM
Tivoli
Service
Level
Advisor
backup
procedure
enables
you
to
capture
the
entire
IBM
Tivoli
Service
Level
Advisor
solution
in
a
valid
state
usable
by
the
accompanying
restoration
procedure.
Not
following
the
IBM
Tivoli
Service
Level
Advisor
defined
procedures
for
backup
and
restoration
might
result
in
a
partially
configured
system
upon
restoration.
Refer
to
the
following
sections
for
the
procedures
on
backing
up
and
restoring
IBM
Tivoli
Service
Level
Advisor:
v
“Backing
up
IBM
Tivoli
Service
Level
Advisor”
on
page
36
v
“Restoring
IBM
Tivoli
Service
Level
Advisor”
on
page
44
Do
not
run
the
Registration
ETL:
The
Registration
ETL
should
not
be
run
while
performing
a
backup
or
restoration.
The
Registration
ETL
attempts
to
modify
the
SLM
Database,
changing
the
database
image
that
is
taken
or
restored
from
the
actual
state
it
was
in
when
IBM
Tivoli
Service
Level
Advisor
was
last
running.
Backing
Up
Tivoli
Data
Warehouse
As
part
of
regular
system
maintenance
or
recovery
procedures,
Tivoli
Data
Warehouse
must
be
backed
up
and
restored
in
conjunction
with
IBM
Tivoli
Service
Level
Advisor.
Each
backup
of
Tivoli
Data
Warehouse
must
include
a
backup
of
the
IBM
Tivoli
Service
Level
Advisor
solution
to
ensure
that
data
between
the
two
remain
synchronized.
Similarly,
each
restoration
of
Tivoli
Data
Warehouse
must
include
a
restoration
of
the
IBM
Tivoli
Service
Level
Advisor
solution.
In
either
case,
IBM
Tivoli
Service
Level
Advisor
should
be
shut
down
before
beginning
a
backup
or
restoration
of
Tivoli
Data
Warehouse.
The
backup
and
restoration
procedures
for
Tivoli
Data
Warehouse
should
be
performed
as
defined
by
the
Tivoli
Data
Warehouse
documentation
during
the
appropriate
steps
marked
by
the
IBM
Tivoli
Service
Level
Advisor
backup
and
restoration
procedures.
See
the
Tivoli
Data
Warehouse
documentation
for
further
information
on
backing
up
and
restoring
Tivoli
Data
Warehouse.
©
Copyright
IBM
Corp.
2002,
2004
35
Automating
the
Backup
and
Restoration
Process
The
following
automated
script
files
have
been
generated
for
backup
and
restoration
purposes:
v
slmbackup,
which
performs
backup
operations
v
slmrestore,
which
performs
restoration
operations
v
slmrestorerestart,
which
restarts
IBM
Tivoli
Service
Level
Advisor
after
an
slmrestore
completes.
With
minimal
input,
slmbackup,
slmrestore,
and
slmrestorerestart
scripts
help
to
manage
the
backup
and
restoration
tasks
that
are
common
to
all
IBM
Tivoli
Service
Level
Advisor
configurations,
from
shutdown
to
startup.
Tasks
that
might
differ
depending
on
the
IBM
Tivoli
Service
Level
Advisor
configuration,
including
the
location
of
the
Tivoli
Data
Warehouse
Server,
are
left
as
separate
tasks
to
be
managed
by
the
system
administrator.
Customized
database
backup
and
restoration
procedures
that
follow
database
and
system
administration
standards
which
might
apply
to
your
enterprise
environment
need
to
be
developed
and
used
during
the
designated
place
in
the
backup
and
restoration
processes.
The
following
sections
explain
the
steps
of
the
IBM
Tivoli
Service
Level
Advisor
backup
and
restoration
processes.
Please
read
the
entire
process
to
understand
the
backup
and
restoration
needs
of
your
system
before
using
the
automated
scripts.
The
following
sections
describe
the
overall
backup
and
restoration
processes,
along
with
the
details
of
the
functions
that
are
performed
by
each
script
and
which
functions
remain
for
the
administrator
to
manage.
See
the
Command
Reference
for
further
information
on
using
command
line
methods
for
backup
and
restoration.
Backing
up
IBM
Tivoli
Service
Level
Advisor
The
overall
process
for
backing
up
IBM
Tivoli
Service
Level
Advisor
is
described
in
the
following
sections.
You
might
want
to
create
a
Backup
Worksheet
that
you
can
use
to
record
pertinent
information
during
the
backup
process.
Be
sure
to
include
the
date
that
the
backup
was
performed,
for
future
reference
for
restoration
purposes
if
needed.
The
following
steps
describe
the
overall
backup
process,
which
you
can
either
complete
manually
or
by
using
the
slmbackup
script.
After
reading
the
following
sections
to
become
familiar
with
the
backup
process,
see
“Using
the
slmbackup
Script”
on
page
41
for
information
about
using
this
automated
script
to
perform
the
actual
backup
operations.
The
backup
procedure
involves
performing
the
following
tasks:
1.
Discontinue
use
of
the
Registration
ETL
and
the
Process
ETL.
2.
Backup
any
information
about
SLMAdmin
users
and
associated
roles.
Roles
are
not
automatically
preserved
by
the
backup
procedure.
3.
Shut
down
IBM
Tivoli
Service
Level
Advisor.
4.
Back
up
IBM
Tivoli
Service
Level
Advisor
installation
directories
for
the
three
main
install
options
of
IBM
Tivoli
Service
Level
Advisor,
recording
the
following
information:
v
SLM
Server
–
Machine
name
36
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
–
Time
stamp
–
Directory
of
the
backup
–
Installation
directory
–
Tivoli
Common
Directory
locationv
SLM
Administrations
Server
–
Time
stamp
–
Directory
of
the
backup
–
Tivoli
Common
Directory
locationv
SLM
Reports
–
Timestamp
–
Directory
of
the
backup
–
Tivoli
Common
Directory
location
5.
Backup
the
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor,
recording
the
following
information:
v
Location
of
the
Tivoli
Common
Directory
v
Location
of
the
backup
6.
Back
up
the
SLM
Database
and
SLM
Measurement
Data
Mart,
recording
the
following
information:
v
Timestamp
v
Directory
of
the
backup
7.
Backup
any
customized
report
JavaServer
Pages
(JSPs)
that
might
be
used
in
WebSphere.
8.
Back
up
Tivoli
Data
Warehouse,
following
the
backup
procedures
described
in
the
documentation
for
that
product.
9.
Restart
IBM
Tivoli
Service
Level
Advisor.
10.
Restart
Registration
ETL
and
Process
ETL
processing.
As
you
proceed
through
the
backup
procedure,
complete
the
worksheet
to
save
the
appropriate
information
so
that
you
can
successfully
restore
the
backed
up
state
at
a
later
time.
In
addition
to
the
information
listed
on
the
worksheet,
configuration
information
such
as
the
CLI
password,
CLI
Port,
and
any
configuration
value
that
might
have
changed
should
also
be
stored
so
that
you
can
restore
those
values.
The
following
sections
provide
further
details
on
each
of
these
steps
in
the
backup
process.
1.
Discontinuing
Use
of
the
Registration
ETL
and
Process
ETL
To
ensure
that
compatible
backup
images
of
the
SLM
Server
configuration,
the
SLM
Administration
Server,
the
SLM
Reports,
and
the
SLM
Database
are
maintained,
the
Registration
ETL
and
Process
ETL
must
not
be
scheduled
to
run
at
any
time
during
the
backup
procedure.
If
either
of
these
ETLs
is
run
during
backup,
data
in
the
SLM
Database
is
modified,
and
the
backup
procedure
does
not
capture
an
accurate
state
of
the
IBM
Tivoli
Service
Level
Advisor
solution.
If
either
ETL
is
active,
do
not
begin
the
backup
procedure
until
it
completes.
You
might
need
to
consult
with
your
warehouse
administrator
to
discontinue
a
scheduled
run
of
the
ETL.
Chapter
5.
Backup
and
Restoration
Procedures
37
2.
Backing
Up
SLM
Administrative
Console
Users
and
Associated
Roles
You
should
manually
document
information
about
roles
associated
with
each
SLM
Administrative
Console
user.
Information
on
user
roles
is
not
automatically
saved
during
the
backup
process.
3.
Shutting
Down
IBM
Tivoli
Service
Level
Advisor
To
ensure
data
integrity
during
the
backup
process,
the
three
installation
options
of
IBM
Tivoli
Service
Level
Advisor
must
be
shut
down,
regardless
of
their
location,
in
the
following
order:
1.
IBM
WebSphere
Application
Server
(including
the
SLM
Administration
Server
and
SLM
Reports
components)
2.
SLM
Server
This
guarantees
that
no
additional
information
can
be
created
or
written,
and
that
the
backup
procedure
is
able
to
capture
the
exact
state
of
the
IBM
Tivoli
Service
Level
Advisor
solution
at
the
time
it
was
shut
down.
Do
not
proceed
further
until
all
three
components
of
IBM
Tivoli
Service
Level
Advisor
have
been
shut
down,
or
the
backup
of
the
SLM
databases
is
not
able
to
complete
successfully.
DB2
Server:
The
DB2
Server
does
not
need
to
be
shut
down.
For
more
information
on
shutting
down
IBM
WebSphere
Application
Server
and
the
SLM
Server,
see
Getting
Started.
4.
Backing
Up
IBM
Tivoli
Service
Level
Advisor
Installation
Directories
The
SLM
Server,
SLM
Administration
Server,
and
SLM
Reports
might
all
reside
on
the
same
machine,
or
on
up
to
three
separate
machines.
If
they
are
installed
on
the
same
machine,
they
share
a
common
installation
directory
containing
the
necessary
files
and
configuration
for
each.
Installed
on
separate
machines,
each
machine
contains
an
installation
directory
with
files
and
configuration
information
for
the
applicable
IBM
Tivoli
Service
Level
Advisor
component
that
needs
to
be
backed
up.
If
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
a
backup
image
of
each
installation
directory
must
be
taken
as
part
of
the
backup
procedure.
Note
the
time
stamp
for
each
backup
image,
and
be
sure
to
keep
them
together
as
part
of
the
same
backup
level.
These
images
represent
a
complete
IBM
Tivoli
Service
Level
Advisor
installation
level.
The
exact
same
images,
restored
to
the
same
machine
names,
must
be
used
as
part
of
the
restoration
process.
Restoring
with
images
taken
from
different
backup
procedures
is
not
supported
and
results
in
IBM
Tivoli
Service
Level
Advisor
in
an
unpredictable
and
possibly
unusable
state
after
restoration.
The
installation
directories
on
each
machine
can
be
backed
up
according
to
the
backup
or
system
administration
standards
that
might
already
be
established
for
your
enterprise
environment.
If
no
standard
backup
procedure
exists
for
your
enterprise,
the
slmbackup
command
may
be
used.
See
“Using
the
slmbackup
Script”
on
page
41
for
the
instructions
and
results
of
using
the
slmbackup
command.
It
is
important
to
obtain
a
backup
image
of
all
IBM
Tivoli
Service
Level
Advisor
pieces
while
they
are
all
shut
down.
38
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Be
sure
to
record
the
appropriate
information
in
your
Backup
Worksheet.
5.
Backing
up
the
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor
Each
component
of
IBM
Tivoli
Service
Level
Advisor
is
associated
with
log
and
first
failure
data
capture
information
located
in
the
Tivoli
Common
Directory
(see
the
Messages
document
for
more
information
on
message
and
trace
logging).
Similar
to
the
installation
directory,
if
components
are
installed
on
the
same
machine,
the
Tivoli
Common
Directory
is
shared
between
them.
Otherwise,
each
machine
where
at
least
one
component
of
IBM
Tivoli
Service
Level
Advisor
is
installed
contains
this
directory.
The
Tivoli
Common
Directory,
which
contains
log
and
first
failure
data
capture
information,
can
be
backed
up
as
needed.
Information
contained
in
this
directory
includes
historical
audit,
message,
and
trace
log
files
that
are
not
considered
critical
for
product
operation,
but
are
useful
in
reviewing
past
product
failures
and
operations.
If
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
a
backup
image
of
each
Tivoli
Common
Directory
\DYK
subdirectory
can
be
taken
as
part
of
the
backup
procedure.
The
\DYK
directory
contains
only
the
files
related
to
IBM
Tivoli
Service
Level
Advisor.
Other
product
directories
might
also
exist
at
the
same
level
as
the
\DYK
directory,
but
they
do
not
directly
pertain
to
IBM
Tivoli
Service
Level
Advisor.
You
should
note
the
time
stamp
for
each
backup
image,
and
keep
all
images
together
as
part
of
the
same
backup
level.
These
images
represent
a
complete
IBM
Tivoli
Service
Level
Advisor
installation
level.
Although
the
data
in
the
Tivoli
Common
Directory
is
not
critical,
the
exact
same
Tivoli
Common
Directory
images,
restored
to
the
same
machine
names,
should
be
used
as
part
of
the
restoration
process.
Restoring
with
images
taken
from
different
backup
procedures
is
not
supported
and
results
in
IBM
Tivoli
Service
Level
Advisor
in
an
unpredictable
and
possibly
unusable
state
after
restoration.
The
Tivoli
Common
Directory
on
each
machine
can
be
backed
up
according
to
the
backup
or
system
administration
standards
that
might
already
be
established
for
your
enterprise
environment.
If
no
standard
backup
procedure
exists
for
your
enterprise,
use
the
slmbackup
command.
Doing
so
backs
up
the
IBM
Tivoli
Service
Level
Advisor
installation
and
Tivoli
Common
Directory
in
a
single
backup
image
in
a
single
backup
location
intended
for
use
by
the
slmrestore
command
for
restoration
purposes.
See
“Using
the
slmbackup
Script”
on
page
41
for
the
instructions
and
results
of
using
the
slmbackup
command.
It
is
important
to
obtain
a
backup
image
of
all
IBM
Tivoli
Service
Level
Advisor
components
while
they
are
all
shut
down,
such
that
no
log
or
first
failure
data
is
being
written
during
the
backup
operation.
Be
sure
to
record
the
appropriate
information
in
your
Backup
Worksheet.
6.
Backing
Up
the
IBM
Tivoli
Service
Level
Advisor
Databases
Data
in
the
SLM
Database
and
SLM
Measurement
Data
Mart
should
be
backed
up
while
IBM
Tivoli
Service
Level
Advisor
is
shut
down
to
maintain
compatibility
with
the
configuration
information
in
installation
directories
and
configuration
and
log
information
related
to
the
SLM
Administration
Server.
Regardless
of
whether
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
you
only
need
to
backup
these
databases
from
the
DB2
server
where
these
databases
are
physically
located.
Chapter
5.
Backup
and
Restoration
Procedures
39
On
distributed
operating
systems
(that
is,
not
z/OS
or
OS/390
systems),
these
databases
can
be
backed
up
by
running
the
following
command
on
the
DB2
server
machine:
Note:
For
Windows
systems,
first
run
the
db2cmd
command
to
initialize
the
DB2
Universal
Database
environment.
db2
backup
database
<db_name>
user
<user_name>
using
<password>
to
<directory>
In
the
above
command,
the
following
parameters
are
defined:
db_name
is
the
name
of
the
database
chosen
during
the
installation
of
IBM
Tivoli
Service
Level
Advisor
(for
example,
the
default
name
is
dyk_cat
for
the
SLM
Database
and
dyk_dm
for
the
SLM
Measurement
Data
Mart)
user_name
is
a
valid
DB2
Universal
Database
administrative
user
name
password
is
the
valid
DB2
Universal
Database
password
for
user_name
directory
is
the
location
in
which
to
place
the
DB2
Universal
Database
backup
image
Write-enable
the
backup
directory:
If
this
backup
directory
is
on
a
UNIX
machine,
verify
that
it
is
write-enabled.
If
necessary,
issue
the
following
command
to
enable
the
directory
for
writing
the
backup
information:
chmod
777
<directory>
For
example,
using
the
default
SLM
Database
name
of
dyk_cat,
the
db2
backup
command
could
be
issued
as:
db2
backup
database
dyk_cat
user
db2user
using
db2password
to
C:\DB\backup
Associate
backups:
Be
sure
to
associate
the
backup
of
the
SLM
Database
and
SLM
Measurement
Data
Mart
with
the
backup
of
the
IBM
Tivoli
Service
Level
Advisor
installation
directories,
and
that
you
record
the
time
stamps
for
each
of
these
backups
to
use
together
in
a
future
restoration.
Restoring
the
databases
from
a
DB2
Universal
Database
image
and
the
IBM
Tivoli
Service
Level
Advisor
installation
directory
image
that
were
not
taken
as
part
of
the
same
backup
procedure
is
not
supported
and
results
in
restoration
to
an
incorrect
and
possibly
non-functioning
IBM
Tivoli
Service
Level
Advisor
state.
Be
sure
to
record
the
appropriate
information
in
your
Backup
Worksheet.
While
this
backup
procedure
might
be
sufficient
for
typical
distributed
operating
systems,
you
should
consult
your
database
administrator
to
determine
the
best
backup
strategy
for
these
databases,
in
particular
when
the
database
is
located
in
z/OS
or
OS/390
environments.
See
Troubleshooting
for
further
information
on
resolving
problems
during
database
backup.
7.
Backing
Up
Customized
Report
JSPs
in
WebSphere
If
any
customization
of
the
IBM
Tivoli
Service
Level
Advisor
SLM
Report
JavaServer
Pages
was
performed
since
installing
the
IBM
Tivoli
Service
Level
Advisor
SLM
Administration
Server
or
SLM
Reports
option,
these
files
(in
WebSphere)
must
be
backed
up
manually.
If
the
customized
report
JavaServer
Pages
are
not
backed
up,
any
modifications
contained
in
the
SLM
Reports
application
for
the
WebSphere
node
where
the
JavaServer
Pages
were
installed
are
40
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
lost
during
the
restoration
process.
This
occurs
when
the
SLM
Reports
option
is
uninstalled
from
IBM
WebSphere
Application
Server
and
the
original
SLM
report
JavaServer
Pages
are
reintegrated.
If
no
modifications
were
made
to
the
SLM
Report
JavaServer
Pages,
no
additional
work
needs
to
be
performed.
See
SLM
Reports
for
information
on
customizing
the
SLM
Report
JavaServer
Pages.
8.
Backing
Up
Tivoli
Data
Warehouse
To
ensure
continuity
with
the
information
and
data
backed
up
for
IBM
Tivoli
Service
Level
Advisor,
you
should
also
make
a
complete
backup
of
Tivoli
Data
Warehouse.
Refer
to
the
documentation
accompanying
Tivoli
Data
Warehouse
for
more
information.
Be
sure
to
record
any
appropriate
information
in
your
Backup
Worksheet.
9.
Restarting
IBM
Tivoli
Service
Level
Advisor
When
backup
of
the
IBM
Tivoli
Service
Level
Advisor
installation
directories,
and
the
SLM
Database
have
completed,
you
can
restart
IBM
Tivoli
Service
Level
Advisor.
Restarting
before
all
backups
have
completed
might
result
in
a
backup
image
that
does
not
correctly
reflect
the
state
of
IBM
Tivoli
Service
Level
Advisor
at
the
time
it
was
shut
down.
Restart
IBM
Tivoli
Service
Level
Advisor
by
starting
each
component
of
IBM
Tivoli
Service
Level
Advisor
from
the
machine
on
which
it
resides,
in
the
following
order:
1.
SLM
Server
2.
WebSphere
Application
Server
(including
the
SLM
Administration
Server
and
SLM
Reports)
You
might
be
familiar
with
using
the
slm_service_start
script
to
start
up
the
SLM
Server.
However,
in
this
step
it
is
preferable
to
use
the
slmbackup
-start
command,
which
starts
up
not
only
the
SLM
Server
(using
slm_service_start),
but
also
IBM
WebSphere
Application
Server.
See
Getting
Started
for
information
on
starting
IBM
Tivoli
Service
Level
Advisor.
10.
Restarting
the
Registration
ETL
and
Process
ETL
The
Registration
ETL
and
Process
ETL
should
be
rescheduled
to
resume
running
as
before.
Consult
your
warehouse
administrator
to
complete
this
task.
Using
the
slmbackup
Script
Use
the
slmbackup
script
after
the
Registration
ETL
and
Process
ETL
complete
their
processing
or
are
removed
from
the
schedule
(see
step
1
on
page
36
of
the
backup
process).
Issuing
the
following
command
automates
the
shutdown
of
the
three
main
components
of
IBM
Tivoli
Service
Level
Advisor
(SLM
Server,
SLM
Administration
Server,
and
SLM
Reports)
and
backs
up
their
installation
directory
and
the
Tivoli
Common
Directory:
slmbackup
<directory>
This
script
must
be
run
on
each
machine
where
one
or
more
of
the
three
main
IBM
Tivoli
Service
Level
Advisor
components
is
installed.
The
commands
should
be
issued
simultaneously
on
all
machines
to
synchronize
their
shutdown
if
IBM
Tivoli
Chapter
5.
Backup
and
Restoration
Procedures
41
Service
Level
Advisor
installation
options
are
installed
on
multiple
machines.
The
slmbackup
script
processing
pauses
for
a
confirmation
from
you
that
the
command
was
issued
on
all
necessary
machines.
To
skip
the
confirmation
step
and
immediately
backup
the
local
IBM
Tivoli
Service
Level
Advisor
installation
directories,
issue
the
following
command:
slmbackup
<directory>
-auto
To
obtain
a
valid
backup
image,
all
IBM
Tivoli
Service
Level
Advisor
components
must
be
shut
down
before
proceeding
to
the
backup
of
the
SLM
Database.
The
slmbackup
script
uses
the
directory
specified
as
the
base
directory
to
place
the
backup
image.
All
slmbackup
images
are
placed
in
a
a
file
located
at:
<directory>\DYK\<timestamp>\<timestamp>.zip,
where
<directory>
is
the
directory
specified
by
the
user
and
<timestamp>
is
the
time
the
command
was
issued
as
determined
by
the
slmbackup
command.
These
exact
values,
<directory>
and
<timestamp>,
are
used
to
restore
this
IBM
Tivoli
Service
Level
Advisor
installation
image.
If
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
you
must
save
the
corresponding
time
stamps
from
each
backup
image
for
use
in
the
restoration
process.
Write-enable
the
backup
directory:
If
this
backup
directory
is
on
a
UNIX
system,
verify
that
it
is
write-enabled.
If
necessary,
issue
the
following
command
to
enable
the
directory
for
writing
the
backup
information:
chmod
777
<directory>
When
all
slmbackup
commands
complete,
the
SLM
Database
and
Tivoli
Data
Warehouse
must
be
backed
up.
The
SLM
Database
should
be
backed
up
according
to
procedures
defined
by
your
enterprise
database
administrator.
See
“8.
Backing
Up
Tivoli
Data
Warehouse”
on
page
41
for
instructions
on
backing
up
Tivoli
Data
Warehouse.
After
backup
steps
1
through
8
(see“Backing
up
IBM
Tivoli
Service
Level
Advisor”
on
page
36)
have
completed,
issue
the
following
command
to
restart
IBM
Tivoli
Service
Level
Advisor:
slmbackup
-start
If
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
this
command
must
be
issued
on
each
machine
where
one
or
more
IBM
Tivoli
Service
Level
Advisor
install
options
(SLM
Server,
SLM
Administration
Server,
and
SLM
Reports)
are
installed.
42
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Backup
Procedure
Quick
Reference
Table
6
provides
a
quick
reference
of
the
overall
backup
procedure,
specifying
steps
that
you
can
either
perform
manually
or
by
using
the
slmbackup
script.
Table
6.
Backup
procedure
quick
reference
Backup
Step
What
to
do
1.
Discontinue
use
of
the
Registration
ETL
and
Process
ETL.
2.
Backup
SLM
Administrative
Console
users
and
associated
roles.
3.
Shut
down
IBM
Tivoli
Service
Level
Advisor.
4.
Back
up
IBM
Tivoli
Service
Level
Advisor
installation
directories.
5.
Backup
the
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor.
Consult
your
warehouse
administrator
to
remove
or
suspend
the
Registration
ETL
and
Process
ETL
from
running
according
to
their
normal
schedules.
Do
either
of
the
following
on
each
machine
that
contains
an
installation
of
the
SLM
Server,
SLM
Administration
Server,
or
SLM
Reports:
v
Use
the
slmbackup
<directory>
command
v
Manually
shut
down
and
backup
IBM
Tivoli
Service
Level
Advisor
installation
directories
and
the
Tivoli
Common
Directory
according
to
procedures
defined
by
your
enterprise
environment.
Record
appropriate
information
on
your
Backup
Worksheet
for
future
reference.
6.
Backup
the
SLM
Database
and
SLM
Measurement
Data
Mart.
Consult
your
database
administrator
for
procedures
to
backup
your
DB2
Universal
Database
databases
for
your
enterprise
environment.
Record
appropriate
information
on
your
Backup
Worksheet
for
future
reference.
7.
Backup
any
customized
SLM
report
JSPs
in
WebSphere.
Manually
backup
these
files
to
a
safe
location
for
later
manual
restoration
in
the
restoration
process.
8.
Backup
Tivoli
Data
Warehouse.
Consult
the
Tivoli
Data
Warehouse
documentation
for
information
on
backing
up
Tivoli
Data
Warehouse.
9.
Restart
IBM
Tivoli
Service
Level
Advisor.
Do
either
of
the
following
on
each
machine
that
contains
an
installation
of
the
SLM
Server,
SLM
Administration
Server,
or
SLM
Reports:
v
Use
the
slmbackup
-start
command
v
Manually
start
IBM
Tivoli
Service
Level
Advisor.
See
Getting
Started
for
information
on
starting
IBM
Tivoli
Service
Level
Advisor.
10.
Restart
Registration
ETL
and
Process
ETL.
Consult
your
warehouse
administrator
to
resume
normal
scheduling
of
these
ETLs.
Chapter
5.
Backup
and
Restoration
Procedures
43
Restoring
IBM
Tivoli
Service
Level
Advisor
Restoring
IBM
Tivoli
Service
Level
Advisor
is
only
supported
when
the
target
restoration
environment
is
identical
to
that
of
the
backup.
All
host
names,
directory
locations
of
IBM
Tivoli
Service
Level
Advisor
components
and
associated
prerequisites,
and
configurations
of
associated
prerequisites
must
be
identical.
For
example,
changing
the
location
of
IBM
WebSphere
Application
Server
on
a
target
machine
is
not
supported.
The
IBM
WebSphere
configuration
must
also
be
identical,
including
the
named
application
servers
used
for
the
SLM
Administration
Server
and
SLM
Reports
components,
and
the
type
of
node
in
use
when
the
backup
is
taken.
For
example,
if
the
SLM
Administration
Server
is
backed
up
on
a
machine
containing
an
unfederated
WebSphere
Base,
then
it
must
still
be
unfederated
when
the
restoration
is
attempted.
If
the
node
was
federated
into
an
IBM
WebSphere
Application
Server
Network
Deployment
configuration
after
the
backup,
then
restoring
into
this
server
is
not
supported.
The
following
steps
describe
the
overall
restoration
process
for
IBM
Tivoli
Service
Level
Advisor,
which
you
can
either
perform
manually,
or
by
using
the
slmrestore
and
slmrestorerestart
script.
After
reading
the
following
sections
to
become
familiar
with
the
restoration
process,
see
“Using
the
slmrestore
and
slmrestorerestart
Commands”
on
page
51
for
information
about
using
these
automated
scripts
to
perform
the
actual
restoration
operations.
The
procedure
includes
the
following
tasks:
1.
Discontinue
use
of
the
Registration
ETL
and
Process
ETL.
2.
Optionally
reinstall
the
SLM
Server.
3.
Shut
down
IBM
Tivoli
Service
Level
Advisor.
4.
Restore
IBM
Tivoli
Service
Level
Advisor
installation
directories.
5.
Restore
the
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor.
6.
Optionally,
reintegrate
any
customized
report
servlets
into
IBM
WebSphere
Application
Server.
7.
Restore
the
SLM
Database
and
SLM
Measurement
Data
Mart.
8.
Restore
Tivoli
Data
Warehouse.
9.
Reinstall
language
packs
on
the
SLM
Reports
Server
and
SLM
Administration
Server.
10.
Regenerate
the
IBM
WebSphere
web
server
plugin
configuration.
11.
Restart
IBM
Tivoli
Service
Level
Advisor.
12.
Restart
Registration
ETL
and
Process
ETL
processing.
13.
Optionally,
perform
IBM
Tivoli
Service
Level
Advisor
configuration.
14.
Run
the
Registration
ETL
and
Process
ETL.
15.
Manually
add
any
user
names
authorized
to
access
SLM
Reports
since
the
time
of
the
last
backup.
16.
Manually
restore
role
information
associated
with
SLM
Administrative
Console
users
that
was
saved
as
part
of
the
latest
backup
procedure.
When
performing
a
restoration
to
a
prior
version
of
IBM
Tivoli
Service
Level
Advisor,
the
restoration
procedures
and
scripts
for
the
appropriate
version
of
IBM
Tivoli
Service
Level
Advisor
should
be
used.
For
example,
if
version
2.1
of
IBM
Tivoli
Service
Level
Advisor
is
installed
on
the
system
and
a
situation
arises
which
44
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
makes
it
necessary
to
restore
to
version
1.2,
the
version
1.2
restoration
procedures
outlined
in
this
document
and
scripts
contained
on
the
version
1.2
product
CD
should
be
used.
1.
Discontinuing
Use
of
the
Registration
ETL
and
Process
ETL
To
preserve
the
state
of
the
SLM
Database
that
is
restored
in
this
procedure,
the
Registration
ETL
and
Process
ETL
should
not
be
run
until
recovery
is
complete.
If
the
Registration
ETL
or
Process
ETL
is
active,
do
not
begin
the
restoration
procedure
until
it
is
complete.
You
might
need
to
consult
your
warehouse
administrator
to
discontinue
a
scheduled
run
of
these
ETLs.
2.
Reinstalling
the
SLM
Server
In
situations
where
the
machine
running
the
SLM
Server
is
lost
or
damaged,
the
SLM
Server
must
be
reinstalled.
Reinstallation
restores
operating
system
information
necessary
to
run
the
SLM
server.
To
remain
compatible
with
the
SLM
configuration,
reinstallation
must
be
performed
on
a
machine
with
the
same
host
name
and
disk
partition
characteristics.
If
the
SLM
Server
was
originally
installed
on
machineName.mydomain.com,
it
must
be
reinstalled
to
a
machine
with
that
exact
host
name.
Similarly,
if
the
SLM
Server
was
initially
installed
to
C:/SLM,
it
must
be
reinstalled
to
a
directory
with
the
same
name.
If
the
machine
on
which
SLM
Reports
or
the
SLM
Administration
Server
is
installed
is
damaged
or
otherwise
unusable,
those
options
do
not
need
to
be
reinstalled.
Only
the
SLM
Server
option
should
be
selected
for
reinstallation.
Complete
this
step
by
reinstalling
the
SLM
Server.
A
reinstallation
follows
the
same
procedure
as
an
initial
installation.
See
Getting
Started
for
details
on
installing
the
SLM
Server.
During
the
installation
process,
you
are
prompted
for
the
following
information:
v
Directory
name:
Specify
the
location
to
which
the
SLM
Server
was
initially
installed.
v
Select
one
or
more
SLM
servers
you
want
to
install
on
this
machine:
Select
the
SLM
Server
only.
Ignore
the
remaining
installation
windows.
Continue
to
click
Next
to
complete
the
installation.
Refer
to
your
Backup
Worksheet
for
the
correct
installation
directory
and
machine
name
for
the
backup
image
that
is
being
restored.
Do
not
modify
configurations:
Do
not
attempt
to
modify
any
configurations
during
the
installation.
All
configuration
data,
with
the
exception
of
the
two
items
above,
is
restored
when
the
installation
directories
are
restored.
3.
Shutting
Down
IBM
Tivoli
Service
Level
Advisor
To
successfully
restore
IBM
Tivoli
Service
Level
Advisor
to
a
valid
state,
the
correct
backup
images
must
be
restored
properly
while
IBM
Tivoli
Service
Level
Advisor
is
shut
down.
This
ensures
that
no
data
is
written,
processed,
or
modified
during
the
restoration
procedure,
and
ensures
that
all
components
of
IBM
Tivoli
Service
Level
Advisor
are
restarted
at
a
known
state.
The
three
main
components
of
IBM
Tivoli
Service
Level
Advisor
must
be
shut
down,
regardless
of
their
location,
in
the
following
order:
1.
IBM
WebSphere
Application
Server
(for
both
SLM
Administration
Server
and
SLM
Reports)
Chapter
5.
Backup
and
Restoration
Procedures
45
2.
SLM
Server
Do
not
proceed
further
until
all
three
components
of
IBM
Tivoli
Service
Level
Advisor
have
been
shut
down.
If
you
are
restoring
on
Windows
systems:
Be
sure
to
close
the
Services
control
panel
if
it
is
active.
If
you
attempt
a
restoration
procedure
while
this
window
is
active,
the
IBM
Tivoli
Service
Level
Advisor
service
is
removed
from
the
Services
control
panel
and
is
not
restored.
See
Getting
Started
for
information
on
shutting
down
IBM
Tivoli
Service
Level
Advisor.
4.
Restoring
the
IBM
Tivoli
Service
Level
Advisor
Installation
Directories
The
SLM
Server,
SLM
Administration
Server,
and
SLM
Reports
might
have
all
been
originally
installed
to
and
backed
up
from
a
single
machine,
or
up
to
three
separate
machines.
If
installed
on
the
same
machine,
they
share
a
common
installation
directory
containing
the
necessary
files
and
configuration
information
for
each.
Installed
on
separate
machines,
each
machine
contains
an
installation
directory
with
files
and
configuration
information
for
the
applicable
IBM
Tivoli
Service
Level
Advisor
component
to
be
restored.
If
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
it
must
be
restored
from
the
backup
images
of
each
installation
directory
taken
as
part
of
a
single
backup
procedure.
The
time
stamps
for
the
backup
image
taken
on
each
machine
should
have
been
saved
in
conjunction
with
each
other
as
part
of
the
backup
procedure.
Restoring
with
images
taken
from
different
backup
procedures
is
not
supported
and
results
in
an
incorrect
and
possibly
non-functioning
IBM
Tivoli
Service
Level
Advisor
state
upon
restoration.
Consult
your
Backup
Worksheet
for
the
correct
directory
and
time
stamp
of
each
image
associated
with
this
level
of
backup.
Renaming
the
installation
directory:
If
the
SLM
Server
was
not
reinstalled
in
step
2,
then
the
existing
IBM
Tivoli
Service
Level
Advisor
installation
directory
should
be
temporarily
renamed
before
restoring
the
IBM
Tivoli
Service
Level
Advisor
installation.
The
SLM
Server
(and
SLM
Reports
or
SLM
Administration
Server,
if
installed
with
the
SLM
Server)
must
be
shut
down
before
renaming
the
installation
directory.
After
successfully
completing
the
restoration
procedure,
you
can
delete
the
renamed
installation
directory.
The
renaming
procedure
is
a
critical
function
to
perform
a
clean
restoration
of
IBM
Tivoli
Service
Level
Advisor.
This
only
needs
to
be
performed
on
the
machine
where
the
SLM
Server
has
been
installed.
See
Getting
Started
for
instructions
on
shutting
down
the
components
of
IBM
Tivoli
Service
Level
Advisor.
The
installation
directories
on
each
machine
might
be
restored
according
to
the
restoration
or
system
administration
standards
that
might
already
be
established
for
your
enterprise
environment.
If
no
standard
restoration
procedure
exists
for
your
enterprise,
use
the
slmrestore
command
to
restore
the
installation
directories
and
delete
the
existing
installation
directory.
See
“Using
the
slmrestore
and
slmrestorerestart
Commands”
on
page
51
for
the
instructions
and
results
of
using
the
slmrestore
and
slmrestorerestart
commands.
It
is
important
to
restore
the
backup
images
of
all
IBM
Tivoli
Service
Level
Advisor
components
while
they
are
all
shut
down.
46
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
5.
Restoring
the
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor
Each
component
of
IBM
Tivoli
Service
Level
Advisor
is
associated
with
log
and
first
failure
data
capture
information
located
in
the
Tivoli
Common
Directory.
Similar
to
the
installation
directory,
if
components
are
installed
on
the
same
machine,
the
Tivoli
Common
Directory
is
shared
between
them.
Otherwise,
each
machine
where
IBM
Tivoli
Service
Level
Advisor
is
installed
contains
this
directory.
If
the
IBM
Tivoli
Service
Level
Advisor
\DYK
subdirectory
of
the
Tivoli
Common
Directory
was
backed
up
as
part
of
the
IBM
Tivoli
Service
Level
Advisor
backup
procedure,
that
image
should
be
restored
for
each
machine
containing
a
component
of
IBM
Tivoli
Service
Level
Advisor
from
which
it
was
taken.
Although
the
Tivoli
Common
Directory
does
not
contain
information
critical
for
operation
of
IBM
Tivoli
Service
Level
Advisor,
if
a
backup
image
exists
it
should
be
restored
appropriately.
The
\DYK
directory
containing
log
and
first
failure
data
should
be
restored
directly
to
the
Tivoli
Common
Directory.
The
restored
image
should
contain
the
time
stamp
matching
the
backup
image
for
the
installation
directory
from
step
4.
The
time
stamp
and
location
of
the
Tivoli
Common
Directory
should
have
been
recorded
as
part
of
the
backup
procedure
worksheet.
The
Tivoli
Common
Directory
on
each
machine
might
be
restored
according
to
the
restoration
or
system
administration
standards
that
might
already
be
established
for
your
enterprise
environment.
If
no
standard
restoration
procedure
exists
for
your
enterprise,
use
the
slmrestore
command.
See
“Using
the
slmrestore
and
slmrestorerestart
Scripts”
on
page
92
for
the
instructions
and
results
of
using
the
slmrestore
and
slmrestorerestart
commands.
It
is
important
to
restore
the
backup
images
of
the
IBM
Tivoli
Service
Level
Advisor
Tivoli
Common
Directory
for
all
components
while
they
are
all
shut
down.
Failure
to
do
so
might
result
in
the
inability
to
restore
the
log
files.
6.
Reintegrating
Report
Servlets
into
WebSphere
After
the
SLM
Reports
and
SLM
Administration
Server
components
of
IBM
Tivoli
Service
Level
Advisor
are
successfully
restored
to
the
WebSphere
environment,
you
might
also
need
to
reintegrate
any
customized
report
servlets
back
into
the
WebSphere
environment
as
well,
using
the
same
procedure
that
was
used
to
originally
install
these
changed
report
servlets
into
WebSphere.
If
you
have
changed
JSP
files
or
implemented
a
patch
that
has
changed
JSP
files,
there
might
be
files
in
a
temporary
WebSphere
directory
that
need
to
be
removed
manually.
Check
the
following
locations
for
temporary
JSP
files
that
should
be
removed:
<WebSphere_Dir>/temp/<node>/Default_Server/SLM_Report_Application_Server
/SLMReport.war
See
SLM
Reports
for
further
information
on
customizing
the
SLM
report
JSP
files.
7.
Restoring
The
IBM
Tivoli
Service
Level
Advisor
Databases
Data
in
the
SLM
Database
and
SLM
Measurement
Data
Mart
should
be
restored
while
all
three
install
options
of
IBM
Tivoli
Service
Level
Advisor
(SLM
Server,
SLM
Administration
Server,
and
SLM
Reports)
are
shut
down,
to
maintain
compatibility
with
the
configuration
information
in
installation
directories,
as
well
as
configuration
and
log
information
related
to
the
SLM
Administration
Server.
Regardless
of
whether
or
not
IBM
Tivoli
Service
Level
Advisor
is
installed
on
Chapter
5.
Backup
and
Restoration
Procedures
47
multiple
machines,
you
only
need
to
restore
these
databases
to
the
machine
containing
the
DB2
server
where
the
databases
were
originally
created.
If
the
database
has
been
dropped
for
any
reason,
you
must
create
the
database
again
before
attempting
to
restore
its
contents.
Refer
to
Getting
Started
for
information
about
creating
the
databases
if
needed.
On
distributed
operating
systems
(that
is,
not
z/OS
or
OS/390
systems),
the
databases
can
be
restored
by
running
the
following
command
on
the
DB2
server
machine.
For
Windows
systems,
first
run
the
db2cmd
command
to
initialize
the
DB2
Universal
Database
environment
db2
restore
database
<db_name>
user
<user_name>
using
<password>
from
<directory>
taken
at
<db2_timestamp>
In
this
command,
the
following
parameters
are
defined:
db_name
is
the
name
of
the
database
specified
during
the
installation
of
IBM
Tivoli
Service
Level
Advisor
(for
example,
the
default
name
for
the
SLM
Database
is
dyk_cat,
and
the
default
name
for
the
SLM
Measurement
Data
Mart
is
dyk_dm).
user_name
is
a
valid
DB2
Universal
Database
administrative
user
name.
password
is
the
valid
DB2
Universal
Database
password
for
user_name.
directory
is
the
location
in
which
the
DB2
Universal
Database
backup
image
is
located.
db2_timestamp
specifies
the
time
at
which
the
DB2
Universal
Database
backup
was
performed.
The
backup
worksheet
should
be
consulted
for
the
correct
time
stamp
associated
with
the
IBM
Tivoli
Service
Level
Advisor
backup
directories
that
were
restored.
A
list
of
backup
directory
locations
and
time
stamps
can
be
determined
by
issuing
the
following
DB2
Universal
Database
command:
db2
list
history
backup
all
for
<db_name>
The
output
appears
similar
to
the
following:
List
History
File
for
dyk_cat
Number
of
matching
file
entries
=
5
Op
Obj
Timestamp+Sequence
Type
Dev
Earliest
Log
Current
Log
Backup
ID
--
---
------------------
----
---
------------
------------
--------------
B
D
20020110172527001
F
D
S0000000.LOG
S0000000.LOG
---------------------------------------------------------------------------
Contains
2
tablespace(s):
00001
SYSCATSPACE
00002
USERSPACE1
---------------------------------------------------------------------------
Comment:
DB2
BACKUP
DYK_CAT
OFFLINE
Start
Time:
20020110172527
48
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
End
Time:
20020110172548
---------------------------------------------------------------------------
00001
Location:
C:\DB\backup\DYK_CAT.0\DB2\NODE0000\CATN0000\20020110
Applicable
backup
information
is
marked
by
the
Comment
field
containing
the
text,
DB2
Backup
<db_name>,
where,
in
this
case,
<db_name>
is
dyk_cat.
After
this
Comment
field
is
identified,
the
time
stamp
listed
in
the
Start
Time
field
can
be
used
as
input
to
the
DB2
Universal
Database
restore
command.
Below
this
field,
the
Location
field
contains
the
applicable
directory
location
of
the
backup
image.
For
the
directory,
only
the
portion
of
the
directory
name
preceding
the
database
name
must
be
specified.
See
the
highlighted
text
in
the
previous
example
for
the
appropriate
directory
name.
With
this
information,
using
the
default
SLM
Database
name
of
dyk_cat,
issue
the
db2
restore
command
similar
to
the
following
example:
db2
restore
dyk_cat
user
<db2user>
using
<db2password>
from
C:\DB\backup
taken
at
20020110172527
While
this
procedure
should
be
sufficient
for
restoring
the
SLM
Database
and
SLM
Measurement
Data
Mart
on
distributed
operating
systems,
the
databases
should
be
restored
according
to
standards
established
by
your
database
administrator
for
your
enterprise
environment.
Note
that
this
procedure
does
not
apply
to
databases
restored
to
z/OS
and
OS/390
operating
systems.
You
must
consult
with
your
database
administrator
for
the
proper
procedure
to
restore
these
databases
to
your
enterprise
environment.
The
databases
should
be
restored
at
this
time
to
return
IBM
Tivoli
Service
Level
Advisor
to
a
valid
state.
The
DB2
Universal
Database
image
that
is
restored
must
correspond
to
the
IBM
Tivoli
Service
Level
Advisor
installation
directory
backup
images
taken
during
the
same
backup
procedure.
The
DB2
Universal
Database
time
stamp
and
time
stamps
for
each
of
the
IBM
Tivoli
Service
Level
Advisor
installation
directory
images
taken
during
the
backup
procedure
should
have
been
correlated
and
saved.
Restoring
the
databases
from
a
DB2
Universal
Database
image
and
IBM
Tivoli
Service
Level
Advisor
installation
directory
images
that
were
not
taken
as
part
of
the
same
backup
procedure
is
not
supported
and
results
in
restoration
to
an
incorrect
and
possibly
unusable
state.
Consult
your
Backup
Worksheet
for
the
correct
directory
and
time
stamp
for
restoring
the
DB2
Universal
Database
backup
image.
See
Troubleshooting
for
further
information
on
resolving
problems
during
database
restoration.
8.
Restoring
Tivoli
Data
Warehouse
A
complete
restoration
of
Tivoli
Data
Warehouse
is
necessary
in
order
to
obtain
a
fully
synchronized
restoration.
Run
the
procedure
for
restoring
Tivoli
Data
Warehouse
according
to
the
documentation
provided
with
Tivoli
Data
Warehouse.
Consult
the
Backup
Worksheet
for
the
correct
information
to
identify
and
restore
Tivoli
Data
Warehouse.
9.
Reinstall
Language
Packs
for
SLM
Reports
and
SLM
Administration
Server
If
you
installed
any
language
packs,
they
must
be
reinstalled
now.
See
Getting
Started
for
information
on
installing
language
packs.
Chapter
5.
Backup
and
Restoration
Procedures
49
10.
Regenerating
the
IBM
WebSphere
Web
Server
Plug-in
Configuration
If
you
reinstalled
IBM
WebSphere
Application
Server
as
part
of
the
restoration
process,
you
might
need
to
regenerate
the
Web
server
plug-in
configuration.
See
Getting
Started,
along
with
your
WebSphere
documentation,
for
information
on
regenerating
the
Web
server
plug-in
configuration.
11.
Restarting
IBM
Tivoli
Service
Level
Advisor
Once
the
restoration
of
the
IBM
Tivoli
Service
Level
Advisor
installation
directories,
the
SLM
Administrative
Console,
the
SLM
Reports,
and
the
SLM
Database
is
complete,
restart
IBM
Tivoli
Service
Level
Advisor.
Restarting
the
solution
before
all
restorations
have
completed
might
result
in
an
image
that
does
not
correctly
reflect
the
backed
up
state.
Complete
this
step
by
starting
each
of
the
IBM
Tivoli
Service
Level
Advisor
components
from
the
machine
on
which
they
reside:
1.
SLM
Server
2.
WebSphere
Application
Server
(for
the
SLM
Administration
Server
and
SLM
Reports)
You
might
be
familiar
with
using
the
slm_service_start
script
to
start
up
the
SLM
Server.
However,
in
this
step
it
is
preferable
to
use
the
slmrestorerestart
command,
which
starts
up
the
entire
SLM
Solution,
not
just
the
SLM
Server.
See
Getting
Started
for
further
information
on
starting
IBM
Tivoli
Service
Level
Advisor.
12.
Restarting
Registration
ETL
and
Process
ETL
Processing
The
Registration
ETL
and
Process
ETL
should
be
rescheduled
to
resume
running
as
before.
Consult
your
warehouse
administrator
to
complete
this
task.
13.
Configuring
IBM
Tivoli
Service
Level
Advisor
After
restoring
IBM
Tivoli
Service
Level
Advisor,
all
configuration
data
reflects
that
which
was
active
at
the
time
the
systems
were
backed
up.
You
can
perform
the
following
additional
configuration
steps:
v
Change
the
Command
Line
Interface
(CLI)
Service
port
and
password.
v
Change
the
server
communication
port.
v
Modify
data
source
information.
Consult
your
Backup
Worksheet
for
any
configuration
information
that
might
have
been
backed
up
along
with
this
backup
level.
See
the
Command
Reference
for
additional
CLI
commands
that
might
be
useful
in
configuring
IBM
Tivoli
Service
Level
Advisor.
14.
Running
the
Registration
ETL
and
Process
ETL
After
IBM
Tivoli
Service
Level
Advisor
is
restored,
the
Registration
ETL
and
Process
ETL
should
be
run
to
update
the
SLM
Database
and
SLM
Measurement
Data
Mart
with
any
new
data
from
the
Tivoli
Data
Warehouse
database.
If
the
restoration
of
IBM
Tivoli
Service
Level
Advisor
was
completed
as
part
of
a
Tivoli
Data
Warehouse
restoration,
these
ETLs
might
already
be
run
as
part
of
that
50
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
process.
There
is
no
need
to
run
the
ETLs
twice.
Consult
your
warehouse
administrator
to
coordinate
running
the
Registration
ETL
and
Process
ETL
and
scheduling
them
for
normal
operation.
15.
Recreating
SLM
Reports
Users
Added
since
the
Last
Backup
Be
sure
to
recreate
user
names
that
were
authorized
to
access
SLM
Reports
since
the
last
backup
procedure.
Use
the
scmd
report
addUser
command
to
redefine
the
user
name
and
associated
access
parameters.
See
the
Command
Reference
for
more
information
on
the
scmd
report
addUser
CLI
command.
16.
Restoring
Role
Information
Associated
with
SLM
Administrative
Console
Users
Role
information
that
is
associated
with
users
authorized
to
access
the
SLM
Administrative
Console
is
not
preserved
during
the
backup
and
restoration
processes,
and
must
be
manually
restored.
See
Chapter
2,
“Creating
and
Managing
Users,”
on
page
11
for
information
about
associating
roles
with
user
names.
Using
the
slmrestore
and
slmrestorerestart
Commands
Use
of
the
slmrestore
command
begins
at
step
2
in
the
IBM
Tivoli
Service
Level
Advisor
restoration
process
(see
“2.
Reinstalling
the
SLM
Server”
on
page
45)
after
the
Registration
ETL
and
Process
ETL
are
complete
or
are
not
scheduled
to
run.
When
using
the
slmrestore
command,
it
is
not
necessary
to
delete
the
existing
IBM
Tivoli
Service
Level
Advisor
installation.
The
slmrestore
command
automates
this
task.
Before
running
these
commands
on
Windows
systems:
Be
sure
that
the
Services
control
panel
window
is
closed
before
running
either
slmrestore
or
slmrestorerestart.
If
this
window
is
left
open
during
a
restoration,
the
IBM
Tivoli
Service
Level
Advisor
service
is
removed
from
the
list
of
services
and
is
not
restored.
Begin
the
automated
restoration
of
the
IBM
Tivoli
Service
Level
Advisor
installation
directories
by
opening
a
Command
Prompt
window,
navigating
to
the
root
directory
of
the
IBM
Tivoli
Service
Level
Advisor
product
CD,
and
issuing
the
following
command:
slmrestore
<directory>
<timestamp>
Notes:
1.
Do
not
issue
the
slmenv
command
in
this
command
prompt
window.
2.
On
UNIX
systems
you
must
be
the
root
user
to
run
the
restoration
procedure.
The
installation
and
Tivoli
Common
Directory
are
located
together
in
a
single
backup
image
taken
as
part
of
the
slmbackup
command.
The
directory
<directory>
specified
should
be
the
same
directory
that
was
specified
in
the
slmbackup
script
that
created
the
backup
image
denoted
by
the
time
stamp
<timestamp>.
The
directory
should
be
the
base
directory
in
which
the
DYK\<timestamp>\<timestamp>.zip
file
is
located.
The
time
stamp
is
the
time
stamp
that
was
created
by
the
slmbackup
script.
Issuing
the
following
command
returns
the
list
of
all
time
stamps
found
in
the
directory:
Chapter
5.
Backup
and
Restoration
Procedures
51
slmrestore
<directory>
Issuing
slmrestore
<directory>
<timestamp>
automates
the
shutdown
of
the
three
IBM
Tivoli
Service
Level
Advisor
install
options
(SLM
Server,
SLM
Administration
Server,
and
SLM
Reports).
Run
this
script
on
each
machine
where
one
of
the
IBM
Tivoli
Service
Level
Advisor
install
options
is
installed.
The
scripts
should
be
run
simultaneously
on
all
machines
to
synchronize
their
shutdown
if
installed
on
multiple
machines.
The
slmrestore
script
pauses
and
prompt
you
to
confirm
that
the
command
has
been
issued
on
all
necessary
machines
and
that
all
three
IBM
Tivoli
Service
Level
Advisor
installation
options
have
shut
down.
To
omit
the
confirmation
step
and
immediately
restore
the
local
IBM
Tivoli
Service
Level
Advisor
installation
directories,
issue
the
following
command:
slmrestore
<directory>
-auto
Note:
The
SLM
Server,
SLM
Administration
Server,
and
SLM
Reports
must
all
be
shut
down
before
proceeding
to
restore
the
SLM
Database.
After
you
confirm
that
the
IBM
Tivoli
Service
Level
Advisor
install
options
are
shut
down,
or
if
you
issued
the
command
using
the
-auto
flag,
the
installation
directories
are
restored
from
the
DYK\<timestamp>\<timestamp>.zip
file
located
in
the
specified
directory
based
on
the
specified
time
stamp.
If
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
be
sure
to
specify
the
correct
time
stamp
for
each
machine
that
was
backed
up
at
this
level.
After
the
installation
directories
and
the
Tivoli
Common
Directory
have
been
restored,
the
slmrestore
script
reintegrates
the
SLM
Administration
Server
and
the
SLM
Report
servlets
into
IBM
WebSphere
Application
Server,
if
it
is
installed
on
the
local
machine.
After
all
runs
of
the
slmrestore
script
complete,
the
SLM
Database,
SLM
Measurement
Data
Mart,
and
Tivoli
Data
Warehouse
must
be
restored.
The
databases
should
be
restored
according
to
procedures
defined
by
the
enterprise
database
administrator.
See
“8.
Restoring
Tivoli
Data
Warehouse”
on
page
49
for
instructions
on
restoring
Tivoli
Data
Warehouse.
Upon
completion
of
these
steps,
any
language
packs
that
were
installed
should
be
reinstalled.
After
steps
1
through
9
of
the
restoration
process
are
complete,
issue
the
following
CLI
command
to
restart
the
IBM
Tivoli
Service
Level
Advisor
install
options:
slmrestorerestart
If
IBM
Tivoli
Service
Level
Advisor
is
installed
on
multiple
machines,
this
command
must
be
issued
on
each
machine
where
IBM
Tivoli
Service
Level
Advisor
is
installed.
The
remaining
steps
(12
through
14)
must
be
performed
manually.
See
“12.
Restarting
Registration
ETL
and
Process
ETL
Processing”
on
page
50
to
continue
with
these
final
steps
in
the
restoration
process.
52
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Restoration
Procedure
Quick
Reference
Table
7
provides
a
quick
reference
of
the
overall
restoration
procedure,
specifying
steps
that
you
can
either
perform
manually
or
by
using
the
slmrestore
script.
Table
7.
Restoration
procedure
quick
reference
Restoration
Step
What
to
do
1.
Discontinue
use
of
the
Registration
ETL
and
Process
ETL.
Consult
your
warehouse
administrator
to
remove
or
suspend
the
Registration
ETL
and
Process
ETL
from
running
according
to
their
usual
schedule.
2.
Optionally
reinstall
the
SLM
Server.
Use
the
IBM
Tivoli
Service
Level
Advisor
installation
CD
to
reinstall
the
SLM
Server.
See
Getting
Started
for
information
on
installing
the
SLM
Server.
3.
Shut
down
IBM
Tivoli
Service
Level
Advisor.
4.
Restore
IBM
Tivoli
Service
Level
Advisor
installation
directories.
5.
Restore
Tivoli
Common
Directory
for
IBM
Tivoli
Service
Level
Advisor.
6.
Reintegrate
the
report
servlets
into
WebSphere.
Do
either
of
the
following
on
each
machine
that
contains
an
installation
of
the
SLM
Server,
SLM
Administration
Server,
or
SLM
Reports:
v
Use
the
slmrestore
<directory>
<timestamp>
command,
using
the
directory
and
time
stamp
information
from
your
Backup
Worksheet.
Restore
any
customized
report
JSP
Files
that
were
backed
up
after
restoring
the
uncustomized
report
servlets.
v
Manually
shut
down
IBM
Tivoli
Service
Level
Advisor.
If
the
SLM
Server
was
not
installed
as
part
of
step
2,
delete
the
IBM
Tivoli
Service
Level
Advisor
installation
directory
before
proceeding.
v
Restore
the
installation
directories
and
Tivoli
Common
Directory
according
to
procedures
defined
by
your
enterprise
environment
and
using
the
directory
and
time
stamp
information
from
your
Backup
Worksheet.
v
After
restoring
SLM
Administration
Server
and
SLM
Reports
into
WebSphere,
restore
any
customized
report
servlets
that
have
been
backed
up
after
restoring
the
uncustomized
report
servlets.
7.
Restore
the
SLM
Database
and
SLM
Measurement
Data
Mart.
Consult
your
database
administrator
for
procedures
to
restore
your
DB2
Universal
Database
databases
for
your
enterprise
environment,
using
the
directory
and
time
stamp
information
from
your
Backup
Worksheet.
8.
Restore
the
Tivoli
Data
Warehouse.
Consult
the
Tivoli
Data
Warehouse
documentation
for
information
on
backing
up
Tivoli
Data
Warehouse.
Use
the
backup
information
recorded
on
the
Backup
Worksheet.
9.
Optionally
reinstall
language
packs
to
SLM
Reports
and
SLM
Administration
Server.
Consult
Getting
Started
for
instructions
on
reinstalling
language
packs.
Chapter
5.
Backup
and
Restoration
Procedures
53
Table
7.
Restoration
procedure
quick
reference
(continued)
Restoration
Step
What
to
do
10.
Regenerate
the
WebSphere
Web
server
plugin
configuration.
Consult
Getting
Started
and
WebSphere
documentation
for
more
information.
11.
Restart
IBM
Tivoli
Service
Level
Advisor.
Do
either
of
the
following
on
each
machine
that
contains
an
installation
of
the
SLM
Server,
SLM
Administration
Server,
or
SLM
Reports:
v
Use
the
slmrestorerestart
command
v
Manually
start
IBM
Tivoli
Service
Level
Advisor.
See
Getting
Started
for
information
on
starting
IBM
Tivoli
Service
Level
Advisor.
12.
Restart
Registration
ETL
and
Process
ETL
processing.
Consult
your
warehouse
administrator
to
resume
usual
scheduling
of
these
ETLs.
13.
Optionally
configure
IBM
Tivoli
Service
Level
Advisor.
Refer
to
your
Backup
Worksheet
for
additional
configuration
information
that
you
might
have
saved
that
can
now
be
restored
manually.
See
the
Command
Reference
for
information
on
CLI
commands
to
use
for
modifying
your
configuration.
14.
Run
the
Registration
ETL
and
Process
ETL.
Consult
your
warehouse
administrator
to
run
the
ETLs
to
repopulate
the
SLM
Database
and
SLM
Measurement
Data
Mart.
15.
Recreate
users
that
were
authorized
to
access
SLM
reports
since
the
time
of
the
last
backup.
16.
Manually
restore
role
information
for
users
that
are
authorized
to
access
the
SLM
Administrative
Console.
See
the
scmd
report
addUser
command
in
the
Command
Reference
for
information
about
creating
users
to
access
SLM
reports.
See
Chapter
2,
“Creating
and
Managing
Users,”
on
page
11
for
information
about
associating
users
and
roles
for
accessing
the
SLM
Administrative
Console.
54
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Appendix.
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
give
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,
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
allow
disclaimer
of
express
or
implied
warranties
in
certain
transactions,
therefore,
this
statement
might
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.
©
Copyright
IBM
Corp.
2002,
2004
55
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
(I)
the
mutual
use
of
the
information
which
has
been
exchanged,
should
contact:
IBM
Corporation
2Z4A/101
11400
Burnet
Road
Austin,
TX
78758
U.S.A.
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.
Any
performance
data
contained
herein
was
determined
in
a
controlled
environment.
Therefore,
the
results
obtained
in
other
operating
environments
may
vary
significantly.
Some
measurements
may
have
been
made
on
development-level
systems
and
there
is
no
guarantee
that
these
measurements
will
be
the
same
on
generally
available
systems.
Furthermore,
some
measurement
may
have
been
estimated
through
extrapolation.
Actual
results
may
vary.
Users
of
this
document
should
verify
the
applicable
data
for
their
specific
environment.
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.
COPYRIGHT
LICENSE:
This
information
contains
sample
application
programs
in
source
language,
which
illustrate
programming
techniques
on
various
operating
platforms.
You
may
copy,
modify,
and
distribute
these
sample
programs
in
any
form
without
payment
to
IBM,
for
the
purposes
of
developing,
using,
marketing
or
distributing
application
programs
conforming
to
the
application
programming
interface
for
the
operating
platform
for
which
the
sample
programs
are
written.
These
examples
have
not
been
thoroughly
tested
under
all
conditions.
IBM,
therefore,
cannot
guarantee
or
imply
reliability,
serviceability,
or
function
of
these
programs.
56
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Trademarks
IBM,
the
IBM
logo,
DB2,
Lotus,
Rational,
Tivoli,
the
Tivoli
logo,
WebSphere,
DB2
Universal
Database,
eServer,
iSeries,
OS/390,
Passport
Advantage,
pSeries,
Redbooks,
Tivoli
Enterprise
Console,
and
z/OS
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States,
other
countries,
or
both.
Microsoft,
Windows,
Windows
NT,
and
the
Windows
logo
are
registered
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
or
registered
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States,
other
countries,
or
both.
Other
company,
product,
or
service
names
may
be
trademarks
or
service
marks
of
others.
Appendix.
Notices
57
58
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
Index
Special
characters%Program
Files%
18
Aaccess
restricting
2
to
SLA
results,
controlling
5
addUser
15
adjudication
13,
30
analysis
2
applicationsource
5
applicationssource
3
authenticating
users
16
Bbackup
2,
8,
35
automating
36
discontinue
Registration
ETL
37
IBM
Tivoli
Service
Level
Advisor
36
install
directories
38
quick
reference
43
report
servlets,
customized
40
restarting
IBM
Tivoli
Service
Level
Advisor
41
restarting
Registration
ETL
41
shutdown
IBM
Tivoli
Service
Level
Advisor
38
SLM
Database
39
synchronizing,
warehouse
and
SLM
35
Tivoli
Common
Directory
39
Tivoli
Data
Warehouse
35,
41
benefits
of
using
SLM
4
breach
value
4
Ccentral
data
warehouse
6
changeUser
15
CLI
2
creating
SLM
objects
29
setting
up
command
environment
21
CLI
service,
customizing
21
CLI
service,
password
reset
21
CLI
Service,resetting
password
22
cliutil
21
cliutil
getport
22
cliutil
resetpassword
22
cliutil
setport
22
comma
separated
value
(CSV)
31
command
line
interface
2
configurationmodifying
2
configuredata
expiration
time
8
configure
(continued)IBM
Tivoli
Service
Level
Advisor,
after
restore
50
CSV
file,
exporting
data
to
31
customer
4,
16
profile
2
Ddata
expiring
8
exporting
to
CSV
files
31
flow
of
3
missing,
late
29
moving
into
SLM
Measurement
Data
Mart
8
moving
through
warehouse
5
data
collectionenabling
26
data
martSLM
Measurement
8
data
model
5
data
warehouse
5
databaseconnection
parameters,
changing
22
parameters,
specifying
23
SLM
3
warehouse
3
DB2
v
deleteUser
15
dsutil
21,
22
dyk
22
Ee-mail
4
enabledata
collection
8
escalation
2
etl
v
configuring,
scheduling
27
source,
configuring
and
running
30
ETL
5,
8
coordinating
schedule
9
process
7
purge
30
registration
7
restarting
Registration
ETL
after
backup
41
scheduling
7
scheduling
frequency
of
runs
8
source
6
target
6
evaluationdata,
exporting
manually
32
frequency,
configuring
28
hourly
frequency,
disabling
29
intermediate
29
re-evaluating
late
or
missing
data
29
evaluation
results
4
eventnotification
2,
4
expiration
of
data
8
exporting
evaluation
data
32
exporting
to
CSV
files
31
extract,
transform,
load
5
Ffilter
offerings
and
SLAs
7
Ggetport
22
Hhourly
evaluations
28
HTML
v
IIBM
customer
support
2
IBM
DB2
v
IBM
WebSphere
v
JJava
Server
Pages
v
JSP
files
v
Llanguage
pack,
reinstall
after
restore
49
level
of
servicemaintaining
2
managing
4
levels
of
service
2
listUser
15
loadextract,
transform,
and
(ETL)
5
log
2
log
files,
accessing
18
Mmeasurement
data,
expiring
8
measurement
typenew,
running
Registration
ETL
7
metric
4
problem
and
change
management
30
Nnotification
2
©
Copyright
IBM
Corp.
2002,
2004
59
Ooffering
2,
4,
7
filter
criteria
7
Offering
Specialist
13
order
4
OS/390
v
Ppassword,
CLI
service
21
password,
resetting
for
CLI
Service
22
performanceoptimizing,
runstats
9
plug-in,
Web
server,
regenerating
50
portCLI
service,
retrieving
22
CLI
service,
setting
21
CLI
Service,
setting
22
portal
page
16
portfolio
roles
12
problem
and
change
management
metric
30
process
ETL
7
Process
ETL
8
product
version
information,
verutil
24
Purge
ETL
30
Rrcomutil
21,
23
re-evaluation
29
realm
5,
16
Registration
ETL
7
discontinue
during
backup
37
discontinuing
for
restore
45
enabling
source
applications
for
8
restart
after
backup
41
restarting
after
restore
50
running
when
first
installed
7
remote
communication,
configuring
23
reportaccessing
15
users,
managing
15
report
servlets,
customized,
backing
up
40
reports
4
configuring
2
web-based
2
resetpassword
22
restore
2,
8,
35,
44
configuring
IBM
Tivoli
Service
Level
Advisor
50
customized
report
servlets
47
databases
47
install
directories
46
language
pack
reinstall
49
quick
procedure
53
Registration
ETL,
discontinuing
45
restart
IBM
Tivoli
Service
Level
Advisor
50
restart
Registration
ETL
50
running
ETLs
after
50
shutdown
IBM
Tivoli
Service
Level
Advisor
45
SLM
reports,
reintegrating
47
SLM
Server,
reinstall
45
restore
(continued)slmrestore,
specifying
timestamp
51
slmrestore,
using
51
slmrestorerestart,using
51
synchronizing,
warehouse
and
SLM
35
Tivoli
Common
Directory
47
Tivoli
Data
Warehouse
49
retrieving
CLI
port
number
22
roleassociating
users
14
Offering
Specialist
13
SLA
Adjudicator
13
SLA
Specialist
13
SLM
Administrator
12
role-based
access
11
rolesassigning
2
roles,
portfolio
12
roles,
predefined
12
runstats
9
Sschedule
coordinating
ETL
source
and
target
9
ETL
7
ETL,
coordinating
source
and
target
8
Registration
ETL
7
setting
up
2
state
4
schema
5
scmdetl
addApplicationData
21,
26
etl
disable
21,
26
etl
enable
21,
26
etl
getApps
21,
26
etl
registerWarehouseData
21
etl
setDataExpiration
30
mem
reEval
29
mem
showHourlyFrequencyIntervals
21,
28,
29
report
addUser
15
report
changeUser
15
report
deleteUser
15
report
listUser
15
sdc
registerWarehouseData
26
security,
enabling
WebSphere
30
server
communication,
remote
23
service
level
agreement
1,
2
service
level
objective
2
service
transaction
3
setport
22
SLA
1,
2,
7
filter
criteria
7
SLA
Adjudicator
13
SLA
resultsaccess
control
5
SLA
Specialist
13
SLM
Administrator
12
SLM
Database
3
backing
up
39
moving
data
to
7
new
measurement
data
7
restoring
47
SLM
environment,
customizing
21
SLM
Measurement
Data
Mart
3
restoring
47
SLM
Measurment
Dat
aMartexpiring
data
8
SLM
Measurment
Data
Mart
8
SLM
objects,
creating
29
SLM
reportsaccessing
15
reintegrating
during
restore
47
SLM
Serverreinstall
during
restore
45
slm_service_start
41
slmbackup
39,
41
slmbackup
script
36
slmenv
21
slmrestore
39,
44
slmrestore
script
36
slmrestorerestart
44
slmrestorerestart
script
36
SLO
2
SNMP
4
source
application
5
enabling
for
data
collection
8,
26
source
ETL
6
Ttarget
ETL
6
TEC
4
time
zone
16
timestamp,
specifying
for
restore
51
Tivoli
Common
Directory
18
backing
up
39
restoring
47
Tivoli
Data
Warehouse
v
Tivoli
Distributed
Monitoring
7
Tivoli
Enterprise
Data
Warehouse
3
Tivoli
Web
Service
Manager
7
trace
2
transformextract,
and
load
(ETL)
5
trend
4
analyze
2
evaluating
3
Uuser
associating
with
role
14
authenticating
16
authorizing
for
reports
15
created
during
install
15
credentials,
refreshing
18
user
roles
12
user
type
15,
16
user,
associating
with
roles
11
userscreating
2
managing
11
users,
managing
for
reports
15
Vverutil
21,
24
view
16
60
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
violation
4
adjudicating
13,
30
analyze
2
evaluating
3
excluding
13
reinstating
13
Wwarehouse
central
repository
3
warehouse
administrator
7,
8,
9
warehouse
pack
v
WebSphere
v
security
11
security,
enabling
30
Web
server
plug-in,
regenerating
50
Index
61
62
IBM
Tivoli
Service
Level
Advisor:
Administrator’s
Guide
����
Printed
in
USA
SC32-0835-03
