ibm tivoli service level advisor: slm...
TRANSCRIPT
IBM
Tivoli
Service
Level
Advisor
SLM
Reports
Version
2.1
SC32-1248-00
���
IBM
Tivoli
Service
Level
Advisor
SLM
Reports
Version
2.1
SC32-1248-00
���
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
.
.
.
. v
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
.
.
. vii
Related
publications
.
.
.
.
.
.
.
.
.
. vii
Accessing
Publications
Online
.
.
.
.
.
.
.
. viii
Ordering
publications
.
.
.
.
.
.
.
.
.
. viii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. viii
Tivoli
technical
training
.
.
.
.
.
.
.
.
.
. viii
Contacting
IBM
Software
Support
.
.
.
.
.
.
. ix
Determine
the
business
impact
of
your
problem
ix
Describe
your
problem
and
gather
background
information
.
.
.
.
.
.
.
.
.
.
.
.
.
. x
Submit
your
problem
to
IBM
Software
Support
.
. x
Searching
knowledge
bases
.
.
.
.
.
.
.
. x
Obtaining
fixes
.
.
.
.
.
.
.
.
.
.
.
. xi
Updating
support
information
.
.
.
.
.
.
. xi
Participating
in
newsgroups
.
.
.
.
.
.
.
.
. xii
Conventions
used
in
this
guide
.
.
.
.
.
.
. xiii
Typeface
conventions
.
.
.
.
.
.
.
.
.
. xiii
Operating
system-dependent
variables
and
paths
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xiii
Web-Based
SLM
Reports
.
.
.
.
.
.
. 1
Accessing
SLM
Reports
.
.
.
.
.
.
.
.
.
.
. 1
High
Level
Status
Reports
.
.
.
.
.
.
.
.
.
. 2
Configuring
High
Level
Status
Thresholds
.
.
. 4
High
Level
Reports
.
.
.
.
.
.
.
.
.
.
. 6
Viewing
Trend
and
Violation
Details
.
.
.
.
. 9
Additional
Reports
.
.
.
.
.
.
.
.
.
.
.
. 9
The
Ranking
Algorithm
.
.
.
.
.
.
.
.
. 14
Ranking
Categories
.
.
.
.
.
.
.
.
.
.
. 15
Selecting
a
Ranking
Category
.
.
.
.
.
.
. 16
Specifying
Additional
Filtering
Criteria
.
.
.
.
. 16
Selecting
Time
Periods
.
.
.
.
.
.
.
.
.
. 17
Specifying
a
Start
and
End
Date
.
.
.
.
.
. 18
Selecting
an
SLA
Type
.
.
.
.
.
.
.
.
.
. 18
Searching
for
Customers,
Realms,
Resources,
or
SLAs
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Additional
Report
Page
Features
.
.
.
.
.
.
. 19
Specifying
the
Report
Table
Row
Count
.
.
.
. 19
Additional
Web
Links
.
.
.
.
.
.
.
.
.
. 20
Navigational
Links
.
.
.
.
.
.
.
.
.
.
. 21
Displaying
Report
Details
.
.
.
.
.
.
.
.
. 21
Report
Details
for
the
Executive
User
Type
.
.
. 21
Report
Details
for
Operations
View
.
.
.
.
. 28
Report
Details
for
Customer
View
.
.
.
.
.
. 28
Displaying
Graphs
and
Graph
Data
.
.
.
.
.
. 28
Exporting
Evaluation
Data
to
a
Comma
Separated
Value
File
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Appendix
A.
Customizing
SLM
Reports
31
Controlling
Report
Web
Page
Formats
.
.
.
.
. 31
An
Overview
of
the
JavaServer
Page
Files
.
.
.
. 32
Embedding
Report
Servlets
.
.
.
.
.
.
.
.
. 35
Linking
Web
Pages
and
JSP
Files
.
.
.
.
.
. 37
Customizing
Results
Tables
.
.
.
.
.
.
.
. 37
Customizing
User
Authentication
.
.
.
.
.
.
. 38
Authenticating
Users
From
Data
in
the
SLM
Database
.
.
.
.
.
.
.
.
.
.
.
.
.
. 38
Authenticating
Users
Using
a
Java
Bean
.
.
.
. 39
Including
a
Company
Logo
.
.
.
.
.
.
.
.
. 41
Understanding
the
Links
Under
the
Banner
.
.
. 41
Report
Definitions
.
.
.
.
.
.
.
.
.
.
. 41
Tips
.
.
.
.
.
.
.
.
.
.
.
.
.
. 42
Printable
Version
.
.
.
.
.
.
.
.
.
.
. 42
Export
to
MS
Excel
.
.
.
.
.
.
.
.
.
.
. 42
Refreshing
the
Report
Table
Display
.
.
.
.
. 43
Logging
Off
From
the
Report
Display
.
.
.
. 43
Getting
Filter
Parameters
.
.
.
.
.
.
.
.
.
. 44
Including
Selection
Fields
and
Input
Fields
.
.
.
. 45
Including
the
Maximum
Rows
to
Display
Function
46
Customizing
Report
Column
Names
.
.
.
.
.
. 48
Customizing
Graphs
.
.
.
.
.
.
.
.
.
.
. 49
Resizing
Graphs
.
.
.
.
.
.
.
.
.
.
.
. 51
Replacing
the
Back
and
Next
Buttons
.
.
.
.
.
. 51
Creating
Reports
with
Third-Party
Reporting
Software
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
Adding
the
Configure
Status
Association
Link
.
.
. 52
Configuring
the
Configure
Status
Association
Page
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 52
Accessing
Reports
from
the
Report
Link
in
Escalated
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 53
Controlling
the
Number
of
Top
Violations
and
Trends
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 54
Pointing
to
Customized
Exploded
Chart
and
Chart
View
Data
JSP
Files
.
.
.
.
.
.
.
.
.
.
.
. 54
Changing
the
Character
Length
of
Filters
in
Exploded
Charts
.
.
.
.
.
.
.
.
.
.
.
. 55
Displaying
Long
Labels
in
Pie
and
Bar
Charts
.
. 55
Including
Navigational
Links
.
.
.
.
.
.
.
. 56
Adding
Charts
to
an
Overall
Details
Report
.
.
. 57
Changing
the
Excluded
Violation
Page
.
.
.
.
. 57
Changing
the
Full
Resource
Name
Page
.
.
.
.
. 57
Adding
a
Link
Name
.
.
.
.
.
.
.
.
.
.
. 58
Customizing
Web
Links
for
High
Level
Reports
.
. 58
Changing
the
Required
Web
Link
.
.
.
.
.
. 59
Changing
Optional
Web
Links
.
.
.
.
.
.
. 60
Modifying
the
View
Intermediate
SLO
Chart
Link
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 60
Appendix
B.
Notices
.
.
.
.
.
.
.
.
. 63
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 65
©
Copyright
IBM
Corp.
2002,
2004
iii
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 67
iv
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Preface
The
SLM
Reports
document
for
IBM®
Tivoli®
Service
Level
Advisor
provides
information
on
using
the
SLM
Reports
Console
to
generate
and
view
reports
in
IBM
Tivoli
Service
Level
Advisor.
These
reports
are
the
result
of
evaluations
and
trend
analyses
performed
on
measurement
data
that
has
been
extracted
from
the
Tivoli
Data
Warehouse
central
data
warehouse.
This
document
provides
additional
information
on
customizing
JavaServer
Page
(JSP)
files
for
display
in
a
Web
browser.
Who
should
read
this
guide
This
document
is
written
for
users
who
want
to
generate
and
view
reports
on
evaluation
results
and
trend
analyses
performed
by
IBM
Tivoli
Service
Level
Advisor.
Users
of
this
document
should
be
authorized
to
access
SLM
reports
using
the
SLM
Reports
console
from
a
supported
Web
browser.
Certain
users
might
want
to
customize
reports
for
use
by
external
customers
or
others
in
their
organization,
and
want
to
integrate
these
SLM
reports
into
their
existing
Web
pages.
You
should
be
familiar
with
the
following
applications:
v
Accessing
the
Internet
using
a
supported
Web
browser
(see
the
Release
Notes
for
information
on
supported
Web
browsers)
v
IBM
WebSphere®
Application
Server,
in
the
areas
of
starting
and
stopping
the
IBM
WebSphere
Application
Server
and
the
IBM
WebSphere
Administrative
Console
v
HTML
concepts
for
customizing
Java™
Server
Pages
(JSP
files)
to
generate
Web-based
reports
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.
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.
©
Copyright
IBM
Corp.
2002,
2004
v
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
restore
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.
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.
vi
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
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:
http://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
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:
Preface
vii
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:
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
viii
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
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
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
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.
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.
Preface
ix
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.
For
more
information
about
problem
resolution,
see
“Searching
knowledge
bases”
and
“Obtaining
fixes”
on
page
xi.
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.
x
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
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.
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).
Preface
xi
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.
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:
xii
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
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
IBM
DB2
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
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
Preface
xiii
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:
SLM
Reports
Web-Based
SLM
Reports
After
the
service
level
agreement
(SLA)
measurement
data
has
been
evaluated,
the
results,
trends,
and
violations
associated
with
an
SLA
are
stored
in
the
SLM
Database.
You
can
then
retrieve
this
data
from
the
SLM
Database
and
summarize
it
into
reports
that
you
can
view
using
a
supported
Web
browser.
After
you
sign
on
to
the
SLM
Reports
console,
a
colorful
high
level
summary
report
is
displayed
in
table
form,
showing
totals
of
trends
and
violations
across
the
reporting
period,
grouped
by
realms
and
customers.
You
can
click
a
cell
in
the
table
and
view
accompanying
color
charts
and
additional
tables
of
summary
information
about
trends
and
violations,
key
operations
information,
and
specific
details
about
particular
customers
and
SLAs.
You
can
obtain
more
detailed
information
by
selecting
available
Web
links
to
view
additional
reports
and
graphs
that
support
and
explain
the
summary
information.
Where
available,
this
detailed
information
includes
actual
measurement
data
on
individual
violations
and
trends.
You
can
display
the
various
reports
in
different
ways,
depending
on
your
user
type
authorization.
For
example,
information
can
be
displayed
as
a
list
of
SLAs
grouped
by
customer,
or
a
list
of
customers
that
are
grouped
by
realm.
In
addition,
information
can
be
displayed
across
various
time
periods,
for
example,
the
previous
full
week,
month,
quarter
or
year,
on
rolling
periods
of
seven
days,
four
weeks,
30
days,
or
365
days.
Displayed
information
can
also
be
restricted
to
specific
SLA
types
(Internal,
External,
or
Outsourced).
Customers,
realms,
SLAs,
offering
components,
resources,
and
SLA
types
are
ranked
according
to
an
algorithm
that
sorts
by
the
number
of
trends
and
violations,
and
displays
the
results
in
order
of
priority.
Accessing
SLM
Reports
To
access
SLM
Reports,
open
your
Web
browser
and
point
to
the
following
Web
site,
where
<report_server>
is
the
fully
qualified
name
of
the
machine
where
SLM
Reports
is
installed,
and
<port>
is
the
HTTP
port
number
used
by
WebSphere:
http://<report_server>:<port>/SLMReport
For
example:
http://abcuser1.chicago.ibm.com:80/SLMReport
Typically
the
default
port
number,
80,
is
used,
and
in
that
case
the
port
number
does
not
need
to
be
specified.
The
location
can
then
be
entered
similar
to
the
following
example:
http://abcuser1.chicago.ibm.com/SLMReport
Note:
You
must
have
your
Web
browser
configured
to
enable
session
cookies
to
successfully
sign
on
to
SLM
Reports.
To
verify
this,
do
the
following
steps:
v
For
Internet
Explorer,
select
Tools
–>
Internet
Options...,
then
select
the
Privacy
tab,
click
Advanced,
and
verify
that
cookies
are
not
blocked.
v
For
Mozilla,
select
Edit
–>
Preferences...,
then
expand
the
Privacy
&
Security
category
and
select
Cookies.
Verify
that
the
Disable
cookies
radio
button
is
not
selected.
©
Copyright
IBM
Corp.
2002,
2004
1
If
WebSphere
security
is
enabled,
a
sign
on
page
is
displayed,
as
shown
in
Figure
1.
Sign
on
to
the
SLM
Reports
console
using
an
authorized
user
name
and
password
created
by
your
SLM
Administrator
(for
information
on
creating
user
names
and
passwords,
see
the
Administrator’s
Guide).
Your
SLM
Administrator
can
restrict
your
authorization
to
view
only
certain
types
of
reports,
or
to
view
results
only
for
certain
customers,
realms,
or
SLA
types
(internal
or
external).
Signing
on
with
the
user
name
created
during
installation:
When
the
SLM
Reports
option
of
IBM
Tivoli
Service
Level
Advisor
is
first
installed,
a
user
name
is
created
for
default
access
to
the
SLM
Reports
console.
This
user
name
is
authorized
with
an
operations
view
of
reports,
and
is
assigned
a
view
type
of
unrestricted,
meaning
that
this
user
can
view
all
report
data
across
all
realms,
customers,
and
SLA
types.
If
WebSphere
security
has
not
been
enabled,
when
you
bring
up
the
SLM
Reports
console,
you
are
signed
on
with
this
default
user
name
and
authorization.
If
WebSphere
security
is
enabled,
you
can
sign
on
to
SLM
Reports
using
this
user
name
and
its
valid
password.
See
Getting
Started
for
more
information
on
the
creation
of
this
default
user
name
during
the
installation
process.
See
the
Administrator’s
Guide
for
information
on
the
operations
view
and
other
view
configuration
parameters.
After
you
successfully
sign
on
with
an
authorized
user
name
and
password
(or
if
WebSphere
security
has
not
been
enabled),
the
SLM
Reports
console
is
displayed,
showing
a
high
level
report
of
evaluation
results
for
which
you
are
authorized.
From
this
high
level
report,
you
can
obtain
more
details
about
violations
and
trends
of
interest.
High
Level
Status
Reports
The
first
report
that
you
see
is
the
high
level
status
report,
which
gives
you
an
overall
summary
of
the
SLA
status.
There
are
two
types
of
high
level
status
reports,
depending
on
the
view
authorization
for
your
user
name:
v
Customer
Status
by
Realms
v
SLA
Status
by
Customers
An
example
of
a
high
level
status
report
is
shown
in
Figure
2
on
page
3.
Figure
1.
The
SLM
Reports
sign
on
page
is
displayed
if
WebSphere
security
is
enabled.
2
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
The
high
level
status
report
summarizes
information
for
the
entire
time
period
of
interest
(for
example,
the
last
full
week,
month,
quarter,
or
year,
or
a
rolling
view
of
the
past
7
days,
4
weeks,
30
days,
or
365
days).
The
information
is
displayed
in
multiple
columns,
the
number
of
which
depends
on
the
time
period
you
selected
and
the
number
of
days
in
the
time
period.
For
example,
if
the
time
period
spans
10
days
or
less,
the
display
consists
of
10
columns,
with
each
column
in
the
display
representing
one
full
day
(24
hour
time
period)
of
data.
Table
1
describes
the
relationship
between
the
size
of
the
time
period
and
how
that
data
is
displayed
in
the
columns
of
the
high
level
status
report.
Table
1.
Understanding
the
amount
of
data
in
each
column
of
the
high
level
status
report.
Number
of
days
in
the
time
period
Amount
of
time
represented
by
each
column
Number
of
columns
in
the
display
10
days
or
less
1
day
Up
to
10
columns
11
to
70
days
1
week
Up
to
10
columns
71
to
549
days
1
month
Up
to
19
columns
550
days
or
more
1
year
Up
to
10
columns
The
report
table
cells
for
the
time
periods
are
color
coded,
with
the
colors
having
the
following
meanings:
Figure
2.
A
sample
Customer
Status
by
Realms
report,
showing
customers
that
are
ranked
by
violations
and
trends
Web-Based
SLM
Reports
3
Black
This
represents
a
Not
Active
state,
meaning
that
the
SLA
is
not
yet
active
or
is
cancelled.
Green
This
represents
a
Normal
state,
meaning
that
the
number
of
trends
and
violations
detected
during
this
time
period
are
at
or
below
the
acceptable
normal
threshold
level.
You
can
configure
these
threshold
levels
(see
“Configuring
High
Level
Status
Thresholds”).
Yellow
This
represents
a
Warning
state,
meaning
that
either
the
number
of
trends
or
the
number
of
violations
detected
during
this
time
period
is
above
the
Normal
threshold,
but
has
not
yet
reached
a
Critical
threshold.
A
warning
icon
is
displayed
in
the
table
cell,
along
with
the
count
of
trends
and
violations
detected.
Red
This
represents
a
Critical
state,
meaning
that
either
the
number
of
trends
or
the
number
of
violations
detected
during
this
time
period
is
above
the
Critical
threshold.
An
icon
representing
the
critical
state
is
displayed
in
the
table
cell,
along
with
the
count
of
trends
and
violations
detected.
Below
the
high
level
status
report
is
a
Legend
box,
as
shown
in
Figure
3,
which
defines
the
icons
used
to
signify
the
Critical,
Warning,
and
Normal
states,
and
the
cells
that
have
no
active
data
(Not
Active
state).
In
the
SLA
Status
by
Customers
report,
if
the
report
includes
results
from
intermediate
evaluations,
and
if
your
user
name
has
been
enabled
to
view
intermediate
results,
an
Intermediate
icon
is
displayed
next
to
the
SLA
name.
See
the
Command
Reference
for
information
on
enabling
user
names
for
view
authority,
and
see
Managing
Service
Level
Agreements
for
more
information
on
intermediate
evaluations.
Configuring
High
Level
Status
Thresholds
If
your
user
name
is
assigned
to
a
user
type
of
operations,
a
Web
link
is
displayed
(see
Figure
3)
below
the
Legend
box
that
points
to
the
Configuration
Status
Association
page,
where
you
can
configure
the
Critical,
Warning,
and
Normal
thresholds
for
trends
and
violations.
Click
this
link
to
display
the
Configure
Status
Association
page,
as
shown
in
Figure
4
on
page
5.
Figure
3.
The
Legend
box
defines
the
colors
and
symbols
in
the
report.
4
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Use
this
page
to
configure
the
threshold
definitions
for
Critical
(red),
Warning
(yellow),
and
Normal
(green)
states
for
trends
and
violations.
When
configuring
these
settings,
you
must
meet
the
following
conditions:
v
The
number
of
trends
or
violations
configured
for
the
Critical
state
must
be
at
least
one
greater
than
the
number
of
trends
or
violations
for
a
Normal
state
unless
zero
is
specified.
If
zero
is
specified
for
the
Critical
state,
then
the
Warning
state
automatically
is
not
applicable.
Similarly,
if
zero
is
specified
for
the
Warning
state,
then
the
Critical
state
is
not
applicable.
v
For
any
given
cell
in
the
high
level
status
report,
a
Critical
state
is
reported
if
the
number
of
trends
exceeds
the
critical
trend
threshold
setting
or
the
number
of
violations
exceeds
the
critical
violation
threshold
setting.
v
For
any
given
cell
in
the
high
level
status
report,
a
Warning
state
is
reported
if
the
number
of
trends
and
the
number
of
violations
are
both
below
the
critical
threshold
settings,
and
either
the
number
of
trends
or
the
number
of
violations
is
greater
than
the
normal
threshold
settings.
v
For
any
given
cell
in
the
high
level
status
report,
a
Normal
state
is
reported
if
the
number
of
trends
is
at
or
below
the
normal
trend
threshold
setting
and
the
number
of
violations
is
at
or
below
the
normal
violation
threshold
setting.
Figure
4.
Configure
the
threshold
levels
for
Critical,
Warning
and
Normal
states
on
high
level
status
reports.
Web-Based
SLM
Reports
5
After
you
configure
your
threshold
settings,
do
one
of
the
following
steps:
v
Click
OK
to
apply
your
changes
and
return
to
the
previous
page.
v
Click
Restore
Defaults
to
return
the
numeric
values
for
the
trends
and
violations
of
state
thresholds
to
the
original
default
settings.
v
Click
Cancel
to
return
to
the
previous
page
without
applying
your
changes.
Note:
These
configuration
changes
take
effect
immediately,
without
restarting
the
Web
server.
These
same
configuration
settings
apply
to
all
users.
You
can
customize
this
page
to
make
it
accessible
to
other
users.
(see
“Adding
the
Configure
Status
Association
Link”
on
page
52).
High
Level
Reports
The
high
level
report
that
is
displayed
depends
on
the
user
type
authorization
that
is
associated
with
your
user
name.
v
Users
with
a
user
type
of
executive
are
presented
with
the
Customer
Status
by
Realms
report,
similar
to
the
example
shown
in
Figure
2
on
page
3.
This
report
groups
customers
according
to
the
realm
in
which
they
are
associated,
and
for
each
customer
in
a
given
realm,
shows
the
state
in
terms
of
the
number
of
trends
and
violations
detected
during
each
time
segment
in
the
report
period.
By
default,
each
customer
name
in
the
report
is
also
a
Web
link
to
the
SLA
Status
by
Customers
report,
which
shows
details
of
each
SLA
for
that
customer
name.
You
can
customize
or
remove
this
Web
link
(see
Appendix
A,
“Customizing
SLM
Reports,”
on
page
31
for
information
about
customizing
reports).
v
Users
with
a
user
type
setting
of
customer
are
presented
with
the
SLA
Status
by
Customers
report,
as
shown
in
Figure
6
on
page
7.
This
report
is
organized
by
SLA
name
or
SLA
ID
for
each
customer.
A
customer
might
be
associated
with
more
than
one
SLA
ID
in
the
report.
By
default,
the
SLA
names
in
this
report
are
not
configured
as
Web
links,
but
they
can
be
customized
to
link
to
any
Web
page
(see
Appendix
A,
“Customizing
SLM
Reports,”
on
page
31
for
information
about
customizing
reports).
Figure
5.
Critical,
Warning,
and
Normal
threshold
states
can
be
configured
for
trends
and
violations.
6
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
v
Users
with
a
user
type
setting
of
operations
are
also
presented
with
the
SLA
Status
by
Customers
view,
as
shown
in
Figure
7
on
page
8.
This
report
includes
data
collected
during
the
immediate
past
week
in
a
Rolling
7
days
time
period.
Each
column
in
the
report
represents
data
collected
for
one
full
24-hour
time
period.
Figure
6.
A
sample
SLA
Status
by
Customers,
showing
overall
health
of
SLAs,
including
summaries
of
violations
and
trends
Web-Based
SLM
Reports
7
Examining
Evaluation
Results
in
High
Level
Reports
When
you
view
high
level
reports
of
evaluation
and
trend
analysis
results,
and
the
evaluation
period
ends
on
the
current
day,
the
results
for
the
current
day
(that
is,
whether
or
not
a
violation
or
trend
exists)
might
not
have
been
evaluated
yet.
This
is
because
the
evaluation
data
is
not
available
until
the
Process
ETL
completes
its
processing,
moving
data
from
Tivoli
Data
Warehouse
into
the
SLM
Measurement
Data
Mart.
For
example,
the
Rolling
7
days
report
includes
status
for
the
current
day,
and
indicates
it
as
Normal
status.
However,
evaluations
for
the
current
day
have
not
yet
been
performed,
so
even
though
there
might
be
violations
in
effect
for
the
current
day,
the
report
might
not
reflect
that
status
in
all
cases,
if
the
Process
ETL
has
not
yet
been
run
for
the
current
day.
For
daily
evaluations,
the
evaluation
end
date
occurs
every
day.
For
weekly
evaluations,
the
evaluation
end
date
occurs
on
Saturdays.
For
monthly
evaluations,
the
evaluation
end
date
occurs
on
the
last
day
of
the
month.
For
hourly
evaluations
(if
enabled)
the
evaluation
interval
might
be
every
hour
or
some
set
of
hours
that
evenly
divide
into
a
24-hour
time
period.
For
example,
the
Figure
7.
A
sample
SLA
Status
by
Customers
Report.
8
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
administrator
can
set
the
evaluation
interval
to
be
every
hour,
every
2
hours,
every
4
hours,
every
6
hours,
or
every
12
hours.
Displaying
Other
High
Level
Reports
Typically
when
a
user
signs
on
to
view
SLM
reports,
the
initial
high
level
report
that
is
displayed
is
either
the
Customer
Status
by
Realms
report
or
the
SLA
Status
by
Customers
report.
This
initial
Web
page
that
is
displayed
after
you
sign
on
is
also
referred
to
as
the
portal
page,
and
is
generated
using
a
JavaServer
Page
(JSP)
file
named
report.jsp.
The
SLM
Administrator
can
assign
a
different
portal
page
other
than
report.jsp
to
a
user
name.
The
portal
page
can
be
created
and
customized
for
that
particular
user.
See
your
SLM
Administrator
for
assistance,
and
see
the
Command
Reference
for
more
information
for
information
on
portal
pages
assigned
to
users,
using
the
scmd
report
addUser
and
scmd
report
changeUser
CLI
commands.
Refer
also
to
“An
Overview
of
the
JavaServer
Page
Files”
on
page
32
for
information
about
customizing
the
portal
page
for
users.
Viewing
Trend
and
Violation
Details
The
red,
yellow
and
green
colored
table
cells
in
the
high
level
reports
contain
Web
links
that
you
can
click
to
view
additional
details
about
the
trends
and
violations
that
were
detected
for
that
segment
of
the
reporting
time
period.
Note:
For
a
green
(Normal)
colored
cell,
click
anywhere
within
the
cell
to
display
the
Web
link.
For
red
(Critical)
or
yellow
(Warning)
colored
cells,
click
either
the
icon
or
the
numbers
within
the
colored
cell
to
display
the
Web
link.
When
you
click
a
high
level
report
cell
it
displays
an
Overall
Details
report
that
provides
additional
information
on
the
data
collected
during
that
report
period.
These
detailed
versions
of
reports
are
described
further
in
“Displaying
Report
Details”
on
page
21.
Additional
Reports
In
addition
to
the
high
level
summary
reports,
you
can
also
select
additional
reports
depending
on
your
user
type
authorization.
At
the
top
of
the
Web
page,
use
the
Report
Type
field
to
select
one
of
several
additional
reports
that
give
you
more
information
about
the
collected
report
data.
For
example,
if
your
user
type
authorization
is
executive,
you
can
select
the
Customer
Ranking
report
from
the
Report
Type
selection
list,
as
displayed
in
Figure
8
on
page
10.
Web-Based
SLM
Reports
9
The
Customer
Ranking
report,
as
shown
in
Figure
9
on
page
11,
displays
both
a
graphical
and
tabular
summary
of
the
number
of
violations
and
trends
detected
for
each
customer.
At
the
beginning
of
each
ranking
report
are
two
summary
charts,
in
pie,
bar,
or
stacked
bar
graph
format,
that
show
various
views
of
SLA
business
impact.
Depending
on
the
report
type
you
select,
the
charts
show
a
breakdown
of
the
violations
and
trends
per
customer,
realm,
SLA,
offering
component,
resource,
and
SLA
type.
For
example,
the
charts
in
Figure
9
on
page
11
include
a
pie
chart
of
the
percentage
of
total
violations
associated
with
each
customer,
and
a
stacked
bar
chart
showing
the
number
of
violations
per
time
period.
Figure
8.
Selecting
the
Customer
Ranking
report
from
the
Report
Type
list.
10
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
From
the
chart
type
list,
you
can
select
from
eight
different
chart
types
to
display
the
ranking
data,
as
shown
in
Figure
10
on
page
12.
At
the
end
of
each
color
chart
is
a
View
Data
link
that
opens
a
separate
browser
page
displaying
the
actual
data
used
to
draw
the
color
chart.
Figure
9.
A
sample
Customer
Ranking
Report,
showing
customers
that
are
ranked
by
violations
and
trends.
Web-Based
SLM
Reports
11
Additional
examples
of
summary
charts
are
shown
in
Table
2.
Table
2.
Additional
examples
of
summary
graphs
that
you
can
display
in
ranking
reports
Figure
10.
You
can
select
from
one
of
eight
different
chart
types
to
display
in
ranking
reports.
12
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Table
2.
Additional
examples
of
summary
graphs
that
you
can
display
in
ranking
reports
(continued)
After
the
two
charts,
the
ranking
data
is
also
displayed
in
a
table
showing
the
number
of
violations
and
trends
for
each
customer
and
a
calculated
ranking
number
that
takes
into
account
all
SLAs
for
that
customer.
Customers
are
listed
by
ranking
number
in
descending
order.
When
you
click
the
ranking
number
link
in
the
Rank
column
heading
for
a
particular
customer
in
the
table,
the
Overall
Details
report
is
displayed,
showing
additional
details
about
the
violations,
trends,
and
service
level
objectives.
If
there
are
intermediate
evaluation
results
that
are
associated
with
the
SLAs
for
that
customer,
and
if
your
user
name
has
been
enabled
to
view
intermediate
evaluation
results
(see
the
scmd
report
listUser
and
scmd
report
changeUser
commands
in
the
Command
Reference
for
more
information),
the
results
are
displayed
in
the
Intermediate
SLO
Results
table
included
in
this
report
(see
Managing
Service
Level
Agreements
for
more
information
on
intermediate
evaluations).
Collapse
the
Intermediate
SLO
Results
table
in
the
report
by
clicking
the
arrow
next
to
the
table
title.
Even
if
your
user
name
has
not
been
enabled
to
view
intermediate
evaluation
results,
the
Intermediate
SLO
Results
table
is
collapsed
by
default.
Click
the
arrow
next
to
the
table
title
to
expand
the
table
and
view
the
intermediate
results.
Included
in
this
report
are
additional
bar
and
pie
summary
charts
(see
the
samples
in
Table
3):
v
Top
metrics
with
the
most
violations
v
Top
resources
with
the
most
violations
v
Top
metrics
with
the
most
trends
v
Top
resources
with
the
most
trends
Table
3.
Additional
summary
charts
are
available
showing
the
top
metrics
and
resources
with
the
most
trends
and
violations.
To
limit
the
level
of
detail
displayed
in
these
summary
ranking
charts,
the
data
that
is
represented
in
the
charts
includes
only
the
rows
that
are
currently
displayed
in
the
table.
To
see
additional
data,
you
must
do
one
of
the
following
tasks:
Web-Based
SLM
Reports
13
v
Navigate
to
subsequent
pages
of
data.
v
Adjust
the
maximum
number
of
rows
to
display
in
the
table,
to
show
more
data
in
the
display.
v
Search
for
the
data
of
interest.
In
some
of
the
small
bar
charts,
there
are
labels
that
are
not
displayed,
when
there
are
more
than
5
bars
in
the
chart.
Use
the
exploded
view
to
display
all
labels.
You
can
see
a
larger
representation
of
the
charts
by
clicking
the
chart
itself,
which
opens
another
browser
page
with
an
exploded
view
of
the
same
chart.
Use
this
to
display
the
chart
details
that
might
be
too
small
to
see
in
the
normal
sized
display.
You
can
also
customize
how
labels
are
displayed
in
charts.
See
“Displaying
Long
Labels
in
Pie
and
Bar
Charts”
on
page
55.
The
Ranking
Algorithm
The
ranking
column
in
reports
is
used
to
prioritize
the
list
of
SLA
items
that
are
being
displayed.
The
ranking
for
each
row
is
calculated
using
the
following
formula:
Ranking
=
(Mult1
*
NumViolations)
+
(Mult2
*
NumTrends)
+
NumSLAs
The
following
variables
are
used
in
the
formula:
Mult1
A
weighting
factor
multiplier
set
to
a
value
of
4000
for
an
external
view
of
the
report
data
by
the
customer
or
2000
for
an
internal
view
of
the
report
data.
NumViolations
The
number
of
violations
Mult2
A
weighting
factor
multiplier
set
to
a
value
of
3000
for
an
external
view
of
the
report
data
by
the
customer,
or
1000
for
an
internal
view
of
the
report
data.
NumTrends
The
number
of
trends.
NumSLAs
The
number
of
SLAs.
Internal
and
external
views
of
report
data
should
not
be
confused
with
internal
and
external
SLA
types.
The
internal
or
external
view
of
the
report
data
is
based
on
whether
or
not
the
metric
is
included
or
excluded
during
the
offering
creation
process
(see
Managing
Service
Level
Agreements
for
related
information
on
configuring
SLAs).
If
the
metric
is
included
(the
default
value),
then
report
data
for
that
metric
is
available
to
be
viewed
externally
by
the
customer.
If
the
metric
is
not
included,
report
data
for
that
metric
is
not
included
in
external
customer
views.
The
algorithm
calculates
the
ranking
differently
for
each
case.
For
example,
if
there
are
two
violations
and
one
trend
across
three
SLAs
for
a
particular
customer,
all
with
external
views
of
the
report
data,
the
ranking
value
for
this
customer
would
be
calculated
as
shown
in
the
following
example:
Ranking
=
(4000
*
2)
+
(3000
*
1)
+
3
=
11003
The
algorithm
is
similar
for
calculating
ranking
numbers
for
SLAs,
but
the
NumSLAs
value
is
always
1,
and
the
values
used
for
the
number
of
violations
and
trends
only
include
violations
and
trends
for
that
SLA.
Continuing
with
the
preceding
example,
if
the
customer
has
three
SLAs,
with
SLA
number
1000
having
14
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
one
violation
and
one
trend,
SLA
number
1001
has
1
violation
and
no
trends,
and
SLA
number
1002
has
no
violations
or
trends,
the
ranking
calculations
for
each
of
these
SLAs
is
calculated
as
shown
in
the
following
example:
SLA
1000
Ranking
=
(4000
*
1)
+
(3000
*
1)
+
1
=
7001
SLA
1001
Ranking
=
(4000
*
1)
+
(3000
*
0)
+
1
=
4001
SLA
1002
Ranking
=
(4000
*
0)
+
(3000
*
0)
+
1
=
1
Note
that
SLA
1000
has
more
violations
and
trends
than
the
other
SLAs,
and
so
its
ranking
number
is
higher.
Also
note
that
the
ranking
number
for
each
SLA
is
different
than
the
overall
ranking
number
for
the
customer.
Ranking
Categories
Depending
on
the
view
authorization
for
your
user
name,
you
can
select
different
types
of
reports
that
display
the
report
data
by
different
rankings
or
different
views.
The
available
ranking
reports
are
defined
below:
Customer
Ranking
Shows
overall
violation
and
trend
summaries
for
each
customer,
one
customer
name
per
entry.
The
ranking
number
is
calculated
across
all
SLAs
for
the
given
customer.
SLA
Ranking
Shows
overall
violation
and
trend
summaries
for
each
SLA.
A
single
customer
can
have
more
than
one
SLA
in
this
report.
Violation
and
trend
summaries
for
each
SLA
ID
are
displayed,
and
the
ranking
number
is
calculated
only
for
the
specific
SLA
ID.
If
an
SLA
contains
results
from
intermediate
evaluations,
and
your
user
name
has
been
enabled
to
display
intermediate
results
(see
the
scmd
report
addUser
and
changeUser
commands
in
the
Command
Reference
for
more
information),
an
Intermediate
icon
is
displayed
next
to
the
SLA
name
(see
Managing
Service
Level
Agreements
for
more
information
on
intermediate
evaluations).
Offering
Component
Ranking
Shows
each
offering
component
in
a
separate
entry,
with
associated
violations
and
trends.
The
ranking
number
is
calculated
for
each
offering
component,
based
on
the
total
number
of
violations
and
trends
across
all
SLAs
that
contain
this
particular
offering
component.
Realm
Ranking
Shows
each
realm
in
a
separate
entry,
with
violation
and
trend
summaries
for
all
customers
and
SLAs
associated
with
the
particular
realm.
The
ranking
number
is
calculated
across
all
customers
and
SLAs
in
that
realm.
Resource
Ranking
Shows
each
resource
in
a
separate
entry,
with
violation
and
trend
summaries
for
all
SLAs
that
monitor
the
specified
resource.
The
ranking
number
is
calculated
across
all
SLAs
that
include
that
resource
in
their
SLA.
SLA
Type
Ranking
Shows
each
type
of
SLA
(Internal,
External,
or
Outsourced)
in
a
separate
entry,
with
violation
and
trend
summaries
for
all
SLAs
that
are
classified
in
each
of
the
SLA
types.
The
ranking
number
is
calculated
across
all
SLAs
for
each
SLA
type.
Note:
The
level
of
restriction
that
is
placed
on
your
user
name
by
your
SLM
Administrator
limits
each
of
these
reports.
Information
that
is
displayed
in
these
reports
might
be
limited
to
specific
customers,
realms,
or
SLA
types.
Web-Based
SLM
Reports
15
Table
4
shows
the
ranking
reports
available
to
each
type
of
user.
Table
4.
The
ranking
reports
available
for
each
type
of
user
Ranking
report
Executive
Customer
Operations
Customer
Ranking
Yes
No
Yes
SLA
Ranking
Yes
Yes
Yes
Offering
Component
Ranking
No
No
Yes
Realm
Ranking
Yes
No
Yes
Resource
Ranking
No
No
Yes
SLA
Type
Ranking
Yes
No
Yes
Selecting
a
Ranking
Category
At
the
top
of
each
report
page,
use
the
Report
Type
drop
down
box
to
select
from
the
available
report
types
for
each
user
authorization
level.
Figure
8
on
page
10
shows
the
Report
Type
list
for
users
that
are
assigned
to
the
executive
user
type.
Select
a
report
type
and
click
Go
to
refresh
the
page
with
the
new
report.
If
you
have
a
user
type
setting
of
operations
you
can
select
the
following
additional
report
types
from
the
Report
Type
list:
v
Results
v
Trends
v
Violations
Specifying
Additional
Filtering
Criteria
In
addition
to
specifying
the
report
type,
you
can
filter
the
information
that
is
included
in
reports
to
display
the
ranking
information
in
different
ways.
Depending
on
the
type
of
report
that
you
display,
you
can
select
a
different
time
period,
a
specific
start
and
end
date,
or
limit
the
report
to
one
of
three
SLA
types.
The
Filter
Criteria
grouping
includes
additional
fields
that
you
use
to
do
any
of
the
following
tasks:
v
Select
from
a
number
of
predefined
time
periods.
v
Specify
a
particular
start
date
and
end
date.
v
Select
a
particular
SLA
type
(All,
Internal,
External,
or
Outsourced).
When
you
are
viewing
any
of
the
ranking
reports,
select
the
Show
All
Rows
check
box
to
view
all
available
rows
in
your
report.
However,
only
two
chart
types
are
shown
at
the
top
of
the
report.
For
example,
when
you
are
viewing
the
Resource
Ranking
report,
if
you
select
the
Show
All
Rows
check
box,
when
you
refresh
the
display
the
only
two
charts
shown
are
the
Top
resources
with
the
most
trends
and
the
Top
resources
with
the
most
violations
charts
at
the
top
of
the
report.
If
you
clear
the
Show
All
Rows
check
box,
after
refreshing
the
display
you
can
select
multiple
chart
types
to
display
again.
Note:
To
save
space
on
the
report
display,
hide
the
filter
criteria
section
of
the
report
by
clicking
the
arrow
next
to
the
Filter
Criteria
title.
The
filter
criteria
area
is
hidden
in
all
reports
until
you
click
the
arrow
again
to
expand
the
section.
16
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Selecting
Time
Periods
Use
the
Time
Period
filter
criteria
selection
to
select
one
of
several
time
periods
in
which
to
display
your
SLA
results.
Click
the
Time
Period
radio
button
and
select
a
time
period
from
the
list.
Click
Update
to
refresh
the
Web
page
with
your
new
display.
Figure
11
shows
the
Time
Period
list.
The
Time
Period
list
includes
a
list
of
valid
time
periods,
as
defined
in
Table
5:
Table
5.
Valid
time
periods
for
displaying
SLA
evaluation
results
Time
period
Definition
All
Dates
All
dates
in
the
database
Last
Month
From
00:00:00
on
the
first
day
of
the
previous
month
to
23:59:59
on
the
last
day
of
the
previous
month
Last
Quarter
From
00:00:00
on
the
first
day
of
the
previous
quarter
to
23:59:59
on
the
last
day
of
the
previous
quarter
Last
Week
From
00:00:00
on
the
Sunday
of
the
previous
week
to
23:59:59
on
the
Saturday
of
the
previous
week
Last
Year
From
00:00:00
on
the
first
day
of
the
previous
year
to
23:59:59
on
the
last
day
of
the
previous
year
Month
to
date
00:00:00
on
the
first
day
of
the
current
month
to
the
current
day
and
time
Quarter
to
date
00:00:00
on
the
first
day
of
the
current
quarter
to
the
current
day
and
time
Rolling
24
hours
From
the
previous
day
at
the
current
time
to
today
at
the
current
time
Rolling
7
days
From
00:00:00
six
days
ago
to
today
at
the
current
time
Rolling
4
weeks
From
00:00:00
three
weeks
and
six
days
ago
to
today
at
the
current
time
Rolling
30
days
From
00:00:00
29
days
ago
to
today
at
the
current
time
Rolling
365
days
From
00:00:00
364
days
ago
to
today
at
the
current
time
Week
to
date
From
00:00:00
on
the
previous
Sunday
to
today
at
the
current
time
Figure
11.
Use
the
Time
Period
drop-down
list
to
display
SLA
results
for
small
or
large
time
spans.
Web-Based
SLM
Reports
17
Table
5.
Valid
time
periods
for
displaying
SLA
evaluation
results
(continued)
Time
period
Definition
Year
to
date
From
00:00:00
on
the
first
day
of
the
current
year
to
today
at
the
current
time
Year
to
end
of
last
month
From
00:00:00
on
the
first
day
of
the
current
year
to
23:59:59
of
the
last
day
of
the
previous
month
Yesterday
From
00:00:00
on
the
previous
day
to
23:59:59
on
the
previous
day
The
term
rolling
refers
to
the
time
span
from
the
present
back
through
the
specified
period,
starting
at
00:00:00
and
ending
at
the
current
time.
For
example,
if
it
is
currently
Tuesday,
15:30
eastern
standard
time
(EST),
the
Rolling
7
days
time
period
specifies
the
time
period
from
last
Wednesday,
00:00:00
EST
through
Tuesday,
15:30
EST.
The
start
time
for
all
defined
time
periods
is
at
00:00:00
to
include
the
data
for
a
complete
first
day.
The
starting
and
ending
dates
for
quarterly
and
yearly
time
periods
are
related
to
how
your
fiscal
quarter
and
year
settings
have
been
customized.
See
Managing
Service
Level
Agreements
for
more
information
on
the
Customize
Schedules
task
in
the
portfolio
of
the
SLM
Administrative
Console.
The
default
setting
defines
the
fiscal
quarters
with
the
following
start
and
end
dates:
Table
6.
Default
start
and
end
settings
for
quarterly
and
yearly
time
periods
Quarter
Start
Date
End
Date
First
quarter
January
1
March
31
Second
quarter
April
1
June
30
Third
quarter
July
1
September
30
Fourth
quarter
October
1
December
31
Suppose
that
the
first
quarter
is
configured
to
run
from
March
10
to
June
10.
If
today
is
July
4,
2004,
the
Last
Quarter
time
period
is
defined
from
March
10
to
June
10,
and
the
Last
Year
time
period
is
defined
from
the
start
of
the
first
quarter
(March
10,
2003)
to
the
end
of
the
fourth
quarter,
for
example,
March
9,
2004.
Specifying
a
Start
and
End
Date
Instead
of
selecting
from
a
predefined
set
of
time
periods,
specify
a
particular
start
and
end
date
for
your
report.
Click
the
Start
Date
radio
button
and
enter
the
start
and
end
dates.
Enter
the
date
directly
into
the
fields,
or
select
the
calendar
icon
to
the
right
of
each
field
to
navigate
to
the
preferred
date
and
select
it
from
the
calendar.
If
you
enter
the
date
manually,
it
must
be
in
the
ISO
format,
year-month-day,
for
example,
2003-12-31.
After
you
enter
start
and
end
dates
for
the
report,
click
Update
to
refresh
the
report.
Selecting
an
SLA
Type
Use
the
SLA
Type
drop-down
list
to
select
the
types
of
SLAs
to
include
in
SLM
reports.
Figure
12
on
page
19
shows
the
SLA
Type
drop-down
list.
By
default,
users
assigned
to
a
user
type
of
customer
do
not
see
the
SLA
Type
drop-down
list
in
reports.
18
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Select
from
the
following
SLA
Types:
v
All
v
Internal
v
External
v
Outsourced
After
selecting
the
SLA
type,
click
Update
to
refresh
the
Web
page
with
a
new
display.
Refer
to
Managing
Service
Level
Agreements
for
more
information
about
SLA
types.
Searching
for
Customers,
Realms,
Resources,
or
SLAs
When
you
display
the
Customer
Ranking,
SLA
Ranking,
Realm
Ranking,
or
Resource
Ranking
reports,
the
Filter
Criteria
section
also
includes
a
Search
for...
field
that
you
can
use
to
enter
one
or
more
full
or
partial
text
strings
to
further
refine
the
data
displayed
in
the
color
charts
and
tables.
For
example,
at
the
beginning
of
the
Customer
Ranking
report,
this
field
is
labeled
Search
for
customers.
Search
for
customer
names
by
entering
one
or
more
full
or
partial
text
strings,
separated
by
commas.
Using
the
sample
report
shown
in
Figure
9
on
page
11,
three
of
the
four
customer
names
begin
with
the
string
IBM.
If
you
enter
the
partial
string
IBM*
in
the
Search
for
customers
field,
after
the
page
is
refreshed,
only
the
three
customers
that
start
with
IBM
are
included
in
the
chart
and
table.
Specify
one
or
more
full
text
strings
for
an
exact
match,
or
enter
one
or
more
partial
strings
to
return
all
data
that
matches
the
specified
strings,
for
example,
IBM*,
Acme*.
Each
specified
search
string
can
have
a
maximum
length
of
255
characters.
Note:
Use
an
asterisk
(*)
as
a
wild
card
character
in
the
search
string.
Additional
Report
Page
Features
Additional
report
functions
are
available
to
assist
you
in
viewing
and
working
with
SLM
Reports.
Specifying
the
Report
Table
Row
Count
Use
the
Maximum
rows
to
display
drop-down
list
to
specify
how
many
rows
of
data
to
display
in
your
report
output
table.
This
is
useful
if
you
have
a
large
amount
of
customers,
SLAs,
or
offering
components,
and
you
want
to
limit
the
view
to
a
certain
number
of
rows.
Specify
5,
10,
15,
or
20
rows
to
be
displayed.
Click
Go
to
update
the
table.
Figure
13
on
page
20
shows
this
portion
of
the
Web
page.
Figure
12.
Use
the
SLA
Type
drop-down
list
to
display
SLA
results
for
one
or
all
types
of
SLAs.
Web-Based
SLM
Reports
19
Additional
Web
Links
At
the
beginning
of
the
report
page
are
Web
links
providing
the
following
features:
v
Report
Definitions
displays
a
page
that
defines
the
various
reports
that
are
available,
to
assist
you
in
selecting
the
right
report
for
your
use.
v
Tips
opens
a
separate
browser
page
that
gives
configuration
tips
for
printing
SLA
reports.
v
Printable
Version
opens
a
separate
browser
page
containing
a
version
of
the
current
report
suitable
for
printing.
Input
selection
fields,
buttons,
links,
and
filter
criteria
(drop-down
lists)
are
displayed
in
a
read-only
format.
Use
the
function
for
your
browser
to
the
Web
page.
To
enable
printing
SLM
reports
to
files,
you
must
obtain
and
install
a
printer
driver
(a
printer
driver
is
not
delivered
with
IBM
Tivoli
Service
Level
Advisor).
For
example,
you
might
refer
to
Visage
eXPert
from
www.visagesoft.com,
or
eDocPrinter
Pro
from
www.iteksoft.com.
Note:
Neither
www.visagesoft.com
nor
www.iteksoft.com
are
affiliated
in
any
way
with
IBM.
These
references
are
provided
for
convenience
only
and
do
not
in
any
manner
serve
as
endorsements
of
the
Web
sites,
or
the
products
offered
by
Visagesoft
or
ITEKSOFT.
The
materials
at
www.visagesoft.com
and
www.iteksoft.com
are
not
part
of
the
materials
for
this
IBM
product.
Use
of
www.visagesoft.com
and
www.iteksoft
.com
and
the
materials
provided
by
Visagesoft
and
ITEKSOFT
is
at
your
own
risk,
and
it
is
your
sole
responsibility
to
evaluate
and
verify
the
operation
of
these
materials.
v
If
you
have
Adobe
Acrobat
installed
on
your
system,
you
can
use
this
link
to
to
a
file
format.
Note:
Reports
should
be
printed
in
Landscape
orientation.
v
Export
to
MS
Excel
exports
a
nongraphic
version
of
your
current
report
to
a
Microsoft
Excel
spreadsheet.
This
option
is
only
available
if
you
have
Microsoft
Excel
installed
on
the
machine
where
you
are
viewing
SLM
reports
using
your
Web
browser.
Note:
When
you
export
your
report
to
Microsoft
Excel
the
colors
that
are
displayed
on
the
spreadsheet
might
not
match
the
original
colors
from
your
report
because
the
standard
report
color
palette
is
different
than
the
palette
in
Microsoft
Excel.
v
Refresh
refreshes
the
Web
page
with
the
latest
data.
Figure
13.
Select
the
maximum
number
of
rows
to
display.
20
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
v
Sign
Off
signs
you
out
of
the
SLM
Reports
function
and
returns
you
to
the
initial
sign
on
window.
Navigational
Links
When
you
are
displaying
the
various
ranking
reports,
click
a
ranking
number
Web
link
in
the
Rank
column
heading
of
the
table
to
display
further
details
on
violations,
trends,
and
service
level
objectives.
As
you
navigate
further
into
the
details
of
your
violation
and
trend
data,
notice
at
the
top
of
the
Web
page
(just
under
the
additional
Web
links
discussed
in
the
previous
section
and
above
the
Report
Type
list)
a
set
of
navigational
links
that
show
you
where
you
are
in
the
level
of
detail.
For
example,
with
a
user
type
of
executive,
the
Customer
Status
by
Realms
high
level
report
page
is
initially
displayed.
From
there,
click
one
of
the
red,
yellow,
or
green
cells
in
the
report
to
display
a
new
Web
page
showing
report
details
in
the
Overall
Details
report.
At
the
top
of
this
Web
page,
notice
the
navigational
link:
Customer
Status
by
Realms
>
Report
Details
Click
this
link
to
return
to
the
previous
page.
Suppose
at
this
point
that
you
click
one
of
the
links
in
the
Actual
Value
column
heading
of
the
Violations
table.
A
new
Web
page
is
displayed,
with
further
details
on
Service
Level
Objectives.
Now,
the
navigational
link
at
the
top
of
the
Web
page
is
modified
to:
Customer
Status
by
Realms
>
Report
Details
>
Service
Level
Objective
Chart
Click
the
navigational
links
at
any
time
to
move
up
and
down
the
report
hierarchy.
Displaying
Report
Details
From
the
ranked
summary
table
listings
of
SLA
evaluation
results,
find
out
more
information
about
a
particular
entry
in
the
table
by
clicking
the
Web
link
of
the
ranking
number
in
the
Rank
column
heading
of
the
table.
A
new
Web
page
is
displayed,
showing
details
on
violations,
trends,
and
service
level
objectives
that
support
and
explain
the
overall
data
in
the
ranked
summary
listings.
Report
Details
for
the
Executive
User
Type
If
you
have
a
user
type
setting
of
executive,
click
a
Web
link
in
the
table
for
a
particular
realm
and
customer
in
the
Customer
Status
by
Realms
report.
The
default
setting
displays
the
report
details
for
the
selected
customer
that
uses
the
Overall
Details
report
type.
Depending
on
the
display,
this
report
includes
some
or
all
of
the
following
report
tables:
SLA
Information
Shows
the
details
about
the
SLA,
including
SLA
name,
SLA
type,
offering
description,
and
a
table
of
the
offering
components
that
are
part
of
the
offering,
including
associated
metrics,
schedule
states,
and
breach
values.
Tiered
SLAs
in
which
this
SLA
is
included
Shows
SLA
names,
offering
name,
and
SLA
type
of
the
immediate
parent
of
the
filtered
SLA,
if
the
SLA
is
multi-tiered.
SLAs
included
in
the
tiered
SLA
Shows
the
associated
immediate
component
SLA
details
of
the
filtered
SLA,
for
example,
SLA
name,
offering
name,
SLA
type,
association
date,
and
disassociation
date.
Select
a
component
SLA
to
view
its
report
details
Web-Based
SLM
Reports
21
and
to
navigate
down
the
hierarchy
of
the
component
SLAs
that
might
have
contributed
to
the
SLA
violations
or
trends.
Business
Schedule
Shows
schedule
periods
that
make
up
the
overall
business
schedule,
including
period
state,
start
and
stop
time
for
each
period,
time
zone,
frequency,
and
any
additional
details.
The
list
of
schedule
periods
can
include
periods
from
a
business
schedule
and
any
associated
auxiliary
schedules.
Violations
Shows
details
on
each
violation
detected
against
this
SLA,
including
the
specific
measurement
point
that
exceeded
the
breach
value.
Figure
14
on
page
23
shows
a
portion
of
the
Violations
table.
Trends
Shows
details
on
each
trend
detected,
including
the
projected
date
and
time
that
a
violation
is
predicted
to
occur
if
the
current
trend
continues
uncorrected.
Figure
15
on
page
24
shows
a
portion
of
the
Trends
table.
SLO
Results
Shows
the
history
of
monitoring
results
for
a
particular
state
of
a
metric
in
an
SLA.
It
includes
metric
details
that
show
the
resource
being
monitored,
including
the
metric
value
being
measured,
the
breach
value,
and
minimum,
maximum,
and
average
or
total
measured
values
over
a
specific
time
period.
Figure
18
on
page
27
shows
a
part
of
the
SLO
table.
Intermediate
SLO
Results
Shows
the
history
of
intermediate
evaluations
of
hourly
(if
enabled),
daily,
weekly,
and
monthly
service
level
objective
results
in
an
SLA.
This
section
displays
the
current
intermediate
state
of
a
metric,
resource,
and
schedule
state.
If
your
user
name
is
not
authorized
to
view
intermediate
results
(see
the
-int
option
of
the
scmd
report
addUser
command
in
the
Command
Reference),
this
table
is
collapsed
by
default
in
the
report.
Click
the
arrow
in
the
table
title
to
expand
the
table
for
viewing.
If
your
user
name
has
been
authorized
to
view
intermediate
results,
the
table
is
expanded
by
default.
Click
the
intermediate
result
value
link
to
view
an
SLO
graph
that
displays
all
of
the
updated
intermediate
results
for
an
evaluation
interval.
Refer
to
Managing
Service
Level
Agreements
for
additional
information
on
SLO
evaluations
and
intermediate
evaluations.
Note:
This
SLO
graph
is
only
displayed
if
your
user
name
has
been
enabled
to
view
intermediate
results.
See
the
scmd
report
addUser
and
scmd
report
changeUser
commands
in
the
Command
Reference
for
more
information
on
enabling
user
names
to
view
intermediate
results.
Violation
Reports
The
Violations
report
displays
the
violations
of
the
SLA
that
occurred
during
a
specified
time
period.
This
report
displays
the
date
that
each
violation
occurred,
the
breach
value
that
was
set
during
offering
creation,
and
the
actual
value
that
caused
the
violation.
Figure
14
on
page
23
shows
a
part
of
a
Violations
report.
If
you
have
violations
that
have
been
excluded
through
the
adjudication
process,
select
the
Show
excluded
violations
check
box
at
the
end
of
the
Violations
report
to
view
these
excluded
violations
in
the
report
.
The
Violations
report
is
refreshed
automatically,
and
violations
that
have
been
excluded
are
displayed
in
the
report
with
a
special
Excluded
Violation
icon
in
the
Actual
Value
column
(the
right-most
22
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
column
in
the
report
display)
next
to
the
actual
value,
as
shown
in
Figure
14.
Click
the
Excluded
Violation
icon
to
view
a
textual
reason
why
the
violation
was
excluded
from
the
evaluation
process
for
the
associated
SLA.
Refer
to
the
Managing
Service
Level
Agreements
and
the
Administrator’s
Guide
for
more
information
on
the
excluding
and
reinstating
of
violations
for
evaluation.
Trend
Reports
The
Trends
report
warns
of
trends
toward
violations
of
breach
values
of
specific
metrics.
As
a
result
of
the
trend
analysis
that
was
performed,
the
date
of
detection
is
displayed,
along
with
a
projected
date
that
the
metric
breach
value
is
predicted
to
be
violated
if
the
trend
continues.
Figure
15
on
page
24
shows
part
of
an
example
of
a
Trends
table.
Figure
14.
The
Violations
report
shows
details
on
violations
against
the
SLO
breach
values.
Web-Based
SLM
Reports
23
If
a
previously
reported
trend
has
been
canceled
because
it
is
no
longer
trending
toward
a
violation,
it
is
not
included
in
the
report,
unless
you
select
the
Show
canceled
trends
check
box
at
the
end
of
the
Trends
report.
The
Trends
report
is
refreshed
automatically,
and
trends
that
have
been
canceled
are
displayed
in
the
report
with
a
special
Canceled
Trend
icon
in
the
Breach
Value
column
next
to
the
breach
value,
as
shown
in
Figure
16
on
page
25.
In
a
trend
with
multiple
parts
(for
minimum,
maximum,
and
average
trends),
you
might
see
one
value
accompanied
by
the
icon
and
another
value
with
no
icon
in
the
report.
This
indicates
that
part
of
the
trend
was
reversed
or
possibly
canceled
since
the
time
that
it
was
first
detected.
A
cancel
trend
escalation
event
is
issued
only
when
all
parts
of
the
trend
have
been
canceled.
Figure
15.
The
Trends
report
predicts
when
violations
will
occur
unless
corrective
action
is
taken.
24
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Reporting
Imminent
Violations:
It
is
possible
to
have
a
scenario
where
the
projected
violation
date
occurs
earlier
than
the
detection
date
of
the
trend
(see
Managing
Service
Level
Agreements
for
a
discussion
of
this
case
and
an
example).
A
special
imminent
violation
icon
is
displayed
in
the
Breach
Value
column
of
the
Trends
report,
as
shown
in
Figure
17
on
page
26.
This
indicates
that
a
violation
might
be
about
to
occur
based
on
the
trend
analysis
of
the
available
data,
and
should
be
investigated
as
soon
as
possible
before
the
violation
actually
occurs.
The
imminent
violation
icon
is
only
displayed
on
active
trends.
Figure
16.
Canceled
trends
can
be
optionally
displayed
by
selecting
Show
canceled
trends
and
locating
the
Canceled
Trend
icon.
Web-Based
SLM
Reports
25
SLO
Results
Reports
Each
row
in
the
SLO
Results
report
displays
SLA
results
data
which
matches
the
input
request
criteria
for
filtering
customers,
SLAs,
realms,
offering
components,
and
resources
from
ranking
pages,
SLA
type
information,
and
the
time
period.
Your
results
are
only
displayed
for
the
schedule
states
of
the
breach
values
that
you
specify.
Figure
17.
A
special
icon
appears
in
the
Breach
Value
column
of
the
Trends
report
if
the
predicted
violation
date
occurs
earlier
than
the
detection
date.
26
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
The
Actual
Value
column
heading
displays
minimum,
maximum,
and
average
or
total
measured
values
for
the
metric
that
was
collected
over
the
specified
time
period.
Assuming
a
daily
evaluation
frequency,
each
day
during
the
specified
time
period
a
minimum,
maximum,
and
average
or
total
value
is
recorded.
For
example,
if
the
given
time
period
is
one
week,
then
the
metric
data
consists
of
seven
minimum
values,
seven
maximum
values,
and
seven
average
values,
one
per
day.
The
smallest
of
the
seven
minimum
values
and
the
greatest
of
the
seven
maximum
values
are
displayed
in
the
Actual
Value
column.
The
average
value
that
is
displayed
in
the
Actual
Value
column
heading
is
the
average
of
all
seven
average
values
collected
during
the
time
period.
The
values
displayed
in
the
Actual
Value
column
heading
are
also
Web
links
to
graphical
views
of
the
data
points
for
a
specific
time
period.
See
“Displaying
Graphs
and
Graph
Data”
on
page
28
for
more
information.
Tiered
SLAs
From
the
SLA
Ranking
or
the
SLA
Status
by
Customers
reports,
the
associated
tiered
SLA
information
is
listed
in
the
Overall
Details
report.
Besides
the
additional
SLA
information
that
is
displayed
for
every
user
type,
the
following
tables
of
tiered
SLA
detail
are
displayed:
v
Tiered
SLAs
in
which
this
SLA
is
included
shows
the
immediate
parent
SLAs
in
the
tiered
hierarchy
associated
with
the
selected
SLA.
v
SLAs
included
in
the
tiered
SLA
shows
the
immediate
component
SLAs
for
which
the
selected
SLA
is
a
parent
in
the
tiered
hierarchy
associated
with
the
Figure
18.
A
part
of
the
detailed
SLO
Results
report.
Web-Based
SLM
Reports
27
SLA.
Select
a
component
SLA
to
view
its
report
details,
and
continue
selecting
component
SLAs,
navigating
further
down
the
hierarchy
of
component
SLAs
to
determine
the
specific
SLAs
that
might
have
contributed
to
the
SLA
violations
or
trends.
If
a
tiered
SLA
also
contains
intermediate
evaluations,
then
the
Intermediate
SLO
Results
table
displays
the
history
of
hourly
(if
enabled),
daily,
weekly,
and
monthly
SLO
results
for
the
tiered
SLA
(see
Managing
Service
Level
Agreements
for
more
information
on
intermediate
evaluations).
Note:
If
your
user
name
has
not
been
enabled
to
view
intermediate
results,
this
table
is
collapsed
by
default.
Click
the
arrow
next
to
the
title
of
the
table
to
view
the
results.
See
the
scmd
report
addUser
and
changeUser
commands
in
the
Command
Reference
for
more
information.
Report
Details
for
Operations
View
If
you
have
a
user
type
setting
of
operations,
the
initial
high
level
report
that
is
displayed
is
the
SLA
Status
by
Customers
report.
In
this
report,
click
a
table
cell
for
a
particular
SLA
to
view
the
SLA
details.
This
user
type
setting
displays
report
details
on
a
selected
SLA.
The
report
also
includes
additional
details
about
the
SLA,
for
example,
the
SLA
information,
metrics
defined
in
the
SLA,
tiered
SLAs
in
which
this
SLA
is
included,
SLAs
that
are
included
in
this
SLA
(if
it
is
a
tiered
SLA),
and
the
business
schedule
defining
the
various
schedule
states
of
interest
to
the
customer.
On
the
SLA
Details
report
view,
if
your
user
type
is
operations
or
executive,
the
Go
button
is
not
enabled
because
the
SLA
Details
page
shows
details
for
a
specific
SLA.
This
button
is
available
on
the
Overall
Details
report
view
because
that
report
view
displays
information
for
all
SLAs.
From
the
SLA
Ranking
view,
the
details
of
associated
tiered
SLAs,
similar
to
the
executive
view,
are
listed
in
the
Overall
Details
report
summaries
of
the
selected
SLA.
Report
Details
for
Customer
View
A
user
with
a
user
type
setting
of
customer
initially
views
the
SLA
Status
by
Customers
high
level
report.
In
this
view,
click
on
the
table
cell
for
a
particular
SLA
ID
in
the
SLA
Status
by
Customers
display.
A
user
name
with
this
portal
page
setting
is
authorized
to
view
report
details
only
for
specific
customer
data
to
which
the
user
has
been
given
access.
By
default,
users
assigned
to
this
user
type
view
results
only
for
external
and
outsourced
SLAs.
See
the
Administrator’s
Guide
for
more
information
on
assigning
a
user
type
and
configuring
other
settings
for
a
user.
From
the
SLA
Ranking
view,
the
details
of
associated
component
SLAs,
similar
to
the
executive
view,
are
listed
in
the
overall
detail
report
summaries
of
the
selected
SLA.
Displaying
Graphs
and
Graph
Data
In
the
SLO
Results,
Intermediate
SLO
Results,
and
Violations
tables,
the
values
displayed
in
the
Actual
Value
column
heading
are
also
Web
links
to
graphical
views
of
the
data
points
for
a
specific
time
period.
When
you
click
a
Web
link
in
the
Actual
Value
column
heading,
an
area
graph
is
displayed
with
the
scale
for
the
x-axis
set
to
the
number
of
days
in
your
specified
time
period.
Adjust
the
time
period
setting
to
alter
the
contents
of
the
graph.
Figure
19
on
page
29
shows
an
example
of
an
area
graph.
28
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
If
the
breach
value
is
within
the
range
of
the
graph,
a
line
indicating
the
breach
value
is
displayed
on
the
graph,
to
illustrate
where
measurement
data
is
relative
to
the
breach
value
of
interest.
When
viewing
graphical
displays
of
the
evaluated
data,
a
linear
trend
line
relating
to
the
trend
is
also
displayed.
This
line
displays
the
most
recent
trending
information
corresponding
to
the
graph
data,
and
is
drawn
on
the
set
of
graph
data
points
that
currently
supports
a
trend,
should
one
exist,
or
on
the
set
of
graph
data
points
that
is
currently
under
analysis
for
trends
toward
breach
values.
Trend
lines
are
not
displayed
when
a
trend
has
recently
been
cancelled.
Refer
to
the
Managing
Service
Level
Agreements
and
the
Administrator’s
Guide
for
additional
information
relating
to
cancelling
trends.
If
the
evaluation
of
the
SLA
includes
intermediate
evaluation
results,
and
if
the
user
authorization
is
either
operations
or
executive,
the
View
Intermediate
SLO
Chart
Web
link
is
displayed.
Click
this
link
to
display
the
Intermediate
SLO
Chart
page.
You
can
optionally
modify
the
text
for
this
link
(see
“Modifying
the
View
Intermediate
SLO
Chart
Link”
on
page
60).
To
see
the
actual
data
points
used
to
construct
the
graph,
click
the
View
Data
Web
link
below
the
graph,
to
display
the
actual
measurement
data
behind
the
graph
data.
Figure
20
on
page
30
shows
an
example.
Figure
19.
A
sample
graph
of
actual
measurement
data.
Web-Based
SLM
Reports
29
Note:
When
you
are
displaying
graphs
or
graph
data
pages,
you
might
notice
that
the
Go
button
for
the
Report
Type
drop-down
list
is
disabled.
Selecting
a
report
type
other
than
the
SLO
Chart
or
Chart
Data
enables
the
Go
button
again.
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.
IBM
Tivoli
Service
Level
Advisor
provides
a
script
to
export
the
various
tables
of
interest
into
a
CSV
file,
or
you
can
export
tables
manually.
See
the
Administrator’s
Guide
for
details
on
exporting
report
data
to
CSV
files.
Figure
20.
View
the
data
points
behind
the
graph.
30
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Appendix
A.
Customizing
SLM
Reports
When
you
use
the
SLM
Reports
console,
the
reports
for
violations,
trends,
and
details
of
evaluations
are
displayed
in
both
graphical
and
tabular
format
in
your
Web
browser.
These
reports
are
immediately
usable
as
they
are
shipped
with
the
IBM
Tivoli
Service
Level
Advisor
product,
but
you
might
like
to
customize
parts
of
the
report
formats
to
integrate
more
seamlessly
into
your
Web
environment,
or
you
might
want
to
change
certain
preferences,
to
further
enhance
the
reports
for
your
specific
needs.
The
following
sections
describe
the
options
that
you
can
use
to
customize
your
SLM
Reports.
Controlling
Report
Web
Page
Formats
The
SLM
Reports
console
uses
report
servlets
that
are
designed
to
be
integrated
into
your
Web
site
HTML
code
using
JavaServer
Page
(JSP)
files.
When
these
servlets
are
embedded
in
your
HTML
code
and
customized
appropriately,
your
Web
site
can
initiate
report
requests
and
see
the
resulting
reports
displayed
as
part
of
your
Web
page.
The
following
aspects
of
report
tables
controlled
by
the
report
servlets
and
are
not
available
for
you
to
customize:
v
The
specific
charts
that
are
displayed
in
the
high
level
reports.
v
The
specific
columns
that
are
displayed
in
the
table.
v
The
order
of
the
columns
in
the
table.
v
Navigation
options
to
display
additional
pages
of
report
data.
You
can
customize
the
following
aspects
of
reports
that
are
displayed
in
your
Web
browser:
v
The
content
of
the
table,
based
on
the
use
of
optional
input
filter
parameters
that
control
what
is
displayed
in
the
report.
v
Various
HTML
table
parameters,
such
as
colors,
fonts,
titles,
and
table
cell
attributes.
v
User
authorization
that
restricts
users
of
your
Web
site
to
view
only
certain
reports.
v
The
title
and
alignment
of
each
column.
v
The
display
of
columns
in
the
table,
which
depends
on
the
selection
of
the
time
period.
For
example,
the
time
period
is
defined
as
the
current
day,
or
the
previous
day,
week,
or
month.
You
can
filter
the
output
display
by
any
of
the
following
objects:
v
Customer
v
SLA
v
Resource
v
Offering
component
v
Schedule
state
v
Offering
v
SLA
type
©
Copyright
IBM
Corp.
2002,
2004
31
v
Metric
v
Realm
Note:
Always
be
sure
that
your
JSP
Files
are
backed
up
before
making
any
changes.
An
Overview
of
the
JavaServer
Page
Files
The
IBM
Tivoli
Service
Level
Advisor
product
provides
a
set
of
JavaServer
Page
(JSP)
files
that
you
can
modify
to
display
report
tables
and
graphs
in
your
Web
site.
These
JSP
files
are
designed
to
be
chained
together,
so
that
you
can
navigate
from
report
to
report
and
initiate
search
requests
for
customers,
SLAs,
resources,
realms,
and
offering
components.
You
can
modify
some
parts
of
the
JSP
files
as
necessary
to
control
displayed
graphics,
filtering
functions,
text
outside
of
the
report
table,
and
all
other
aspects
of
the
Web
page
in
which
the
servlet
reports
are
embedded.
Table
7
shows
the
available
JSP
files
that
are
included
with
the
IBM
Tivoli
Service
Level
Advisor
product.
Table
7.
Available
Java
Server
Pages
Java
Server
Page
Description
breadCrumbs.jsp
Displays
a
trail
of
navigational
links
at
the
top
of
the
report
page
as
you
navigate
further
into
the
details
of
the
report.
Used
to
keep
track
of
where
you
are
in
the
report,
and
to
move
up
and
down
the
levels
of
report
detail,
or
to
link
to
other
reports.
completeReportDetail.jsp
Displays
the
Report
Details
tables,
including
results,
trends
and
violations,
all
on
one
page.
This
JSP
file
is
similar
to
reportDetail.jsp,
and
displays
one
or
more
of
the
following
report
tables:
v
SLA
information
v
Business
schedule
v
Associated
Parent
SLAs
v
Associated
Component
SLAs
v
Service
level
objective
(SLO)
results
v
Violations
v
Trends
v
Intermediate
SLO
Results
configureStatusAssociation.jsp
Displays
the
current
settings
for
high
level
report
thresholds.
Users
with
a
user
type
of
operations
can
modify
the
threshold
settings
in
the
Configure
Status
Association
page.
customerRanking.jsp
Displays
charts,
number
of
violations,
number
of
trends,
and
rank
of
customers.
custSLAStatusReport.jsp
Displays
high
level
summary
status
reports,
similar
to
report.jsp.
This
is
the
high
level
report
that
is
displayed
if
the
user
name
has
a
user
type
of
executive.
This
same
report
is
displayed
by
selecting
the
SLA
Status
by
Customers
report
from
the
list
of
available
report
types.
dateChooser.jsp
Displays
a
calendar
for
you
to
select
a
date.
32
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Table
7.
Available
Java
Server
Pages
(continued)
Java
Server
Page
Description
excludedReason.jsp
Displays
the
reason
for
an
adjudicated
violation.
explodedGraph.jsp
Displays
an
exploded
view
of
charts
in
ranking
pages.
filterCriteria.jsp
Creates
drop-down
lists
for
Report
Type
Filter
Criteria,
Chart
Type
sections
of
the
report.
filterCriteriaPrintVersion.jsp
Displays
a
version
of
the
filter
criteria
section
of
the
report
page,
suitable
for
printing.
filterValues.jsp
Displays
the
filter
values.
The
values
in
the
filterValues.jsp
file
apply
to
all
displayed
report
pages.
fullResourceName.jsp
Displays
the
full
name
for
a
resource
that
has
more
than
240
characters
in
its
name.
graph.jsp
Displays
the
bar
graph
linked
to
the
SLO
Results
table
and
the
Violations
table
in
reports.
Input
filters
are
available
to
restrict
the
data
to
specific
metrics,
offering
components,
customers,
SLAs,
offerings,
metric
value
type
(minimum,
maximum,
average,
total),
schedule,
period,
start
and
end
dates,
and
SLA
type
(Internal,
External,
and
Outsourced).
graphData.jsp
Displays
data
for
the
Service
Level
Objectives
(SLO)
chart.
hiLevelPeriods.jsp
Displays
the
drop-down
list
at
the
top
of
some
JSP
files.
Use
it
to
customize
the
time
period
for
the
report
view.
This
file
is
similar
to
periods.jsp.
index.html
This
page
is
part
of
the
sign
on
process.
It
does
not
display
a
page
to
the
viewer,
but
is
called
in
web.xml
by
IBM
WebSphere
Application
Server
as
the
default
page.
It
redirects
the
user
to
the
login.jsp
file
for
user
sign-on
if
WebSphere
security
has
been
enabled.
If
security
is
not
enabled,
it
loads
the
appropriate
high
level
report
page.
index2.jsp
An
example
of
user
authentication
using
Java
beans.
See“Authenticating
Users
Using
a
Java
Bean”
on
page
39
for
more
information
about
user
authentication
using
Java
beans.
intermediateResults.jsp
Displays
the
Intermediate
SLO
Results
section
of
reports,
including
the
function
to
optionally
collapse
or
expand
the
title.
links.jsp
Displays
the
drop-down
lists
at
the
top
of
most
JSP
files.
Use
it
to
navigate
from
page
to
page
by
selecting
an
option
from
the
drop-down
list.
login.jsp
Displays
the
sign
on
page
and
prompts
you
for
the
user
name
and
password
to
access
the
SLM
Reports
console.
If
the
user
name
and
password
are
authenticated,
the
portal
page
that
is
associated
with
this
user
is
displayed
(the
default
setting
is
report.jsp).
See
scmd
sla
addUser,
scmd
sla
changeUser,
and
scmd
sla
listUser
CLI
commands
in
the
Command
Reference
for
details
on
creating
user
names
and
assigning
portal
pages.
loginerr.jsp
Logs
a
sign
on
failure
to
the
message
and
ffdc
logs.
Appendix
A.
Customizing
SLM
Reports
33
Table
7.
Available
Java
Server
Pages
(continued)
Java
Server
Page
Description
maximumRowsToDisplay.jsp
Displays
the
drop-down
selection
box
for
the
user
to
specify
the
number
of
rows
to
display
at
once,
for
example,
5,
10,
15,
or
20
rows.
opOfferingComponentRanking.jsp
Displays
charts,
number
of
violations,
number
of
trends,
and
rank
of
offering
components.
This
is
only
available
to
users
with
a
user
type
setting
of
operations.
pageHeader.jsp
Displays
the
banner
at
the
top
of
every
report
page,
typically
displaying
your
company
logo.
You
can
replace
the
Tivoli
and
IBM
logos
with
your
own
company
logos.
periods.jsp
Displays
the
drop-down
list
at
the
top
of
some
JSP
files.
Use
this
file
to
customize
the
time
period
for
the
report
view.
This
file
is
similar
to
hiLevelPeriods.jsp.
printRefreshOff.jsp
Creates
Web
links
in
the
upper
right
portion
of
the
Web
page
labeled
Report
Definitions,
Tips,
Printable
Version,
Export
to
MS
Excel,
Refresh,
and
Sign
Off.
printTips.jsp
Opens
a
separate
page
that
displays
some
tips
on
printing
reports
to
your
local
printer.
realmCustomerStatusReport.jsp
Displays
high
level
summary
status
reports,
similar
to
report.jsp.
This
is
the
high
level
report
that
is
displayed
if
the
user
name
has
a
user
type
of
operations.
Display
this
same
report
by
selecting
the
Customer
Status
by
Realms
report
from
the
list
of
report
types.
realmRanking.jsp
Displays
charts,
number
of
violations,
number
of
trends,
and
rank
of
realms.
report.jsp
Displays
high
level
summary
status
reports.
The
default
setting
displays
report.jsp
as
the
first
high
level
report
page,
or
portal
page,
that
is
displayed
after
you
sign
on.
If
the
user
name
has
a
user
type
of
operations,
the
Customer
Status
by
Realms
report
is
displayed,
which
is
a
special
version
of
this
high
level
report
using
realmCustomerStatusReport.jsp.
reportDefinitions.jsp
Describes
all
report
types
that
are
available
to
the
user,
and
defines
what
each
report
provides.
reportDetail.jsp
Displays
the
Report
Details
tables,
including
results,
trends
and
violations
all
on
one
page.
This
JSP
file
is
similar
to
completeReportDetail.jsp,
and
displays
one
or
more
of
the
following
report
tables:
v
SLO
Results
v
Intermediate
SLO
Results
v
Violations
v
Trends
resourceRanking.jsp
Displays
charts,
number
of
violations,
number
of
trends,
and
rank
of
resources.
resultsDetail.jsp
Displays
the
SLO
Results
table.
34
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Table
7.
Available
Java
Server
Pages
(continued)
Java
Server
Page
Description
slaRanking.jsp
Displays
charts,
number
of
violations,
number
of
trends,
and
rank
of
SLAs.
slaTypeRanking.jsp
Displays
charts,
number
of
violations,
number
of
trends,
and
rank
of
SLA
types.
slaTypes.jsp
Determines
the
type
of
SLA:
Internal,
External,
or
Outsourced.
startEndDates.jsp
Displays
the
start
and
end
dates
that
a
user
selected
in
a
long
form.
For
example,
3/5/03
12:00:00
AM
EST
to
3/27/03
11:59:59
PM
EST
title.jsp
Displays
the
title
of
report
pages,
for
example,
Customer
Ranking.
trendsDetail.jsp
Displays
the
Trends
table.
viewChartData.jsp
Displays
the
data
details
associated
with
each
ranking
page
chart.
violationsDetail.jsp
Displays
the
Violations
table.
These
JSP
files
are
located
in
the
following
directory
where
SLM
Reports
was
installed:
<WebSphere_dir>/installedApps/<machine
name>/SLMReport.ear/SLMReport.war
In
this
directory
path,
<WebSphere_dir>
is
the
location
where
IBM
WebSphere
Application
Server
was
installed,
for
example,
C:\Program
Files\WebSphere\Appserver,
and
<machine
name>
is
the
hostname
of
the
machine
where
SLM
Reports
and
IBM
WebSphere
Application
Server
are
installed,
for
example,
myMachine01.
Embedding
Report
Servlets
To
add
SLM
Report
capabilities
to
your
Web
site,
embed
report
servlets
into
your
HTML
code.
These
report
servlets
perform
the
basic
functions
of
querying
the
SLM
Database
for
the
preferred
report
data,
and
then
displaying
the
data
that
is
returned
in
report
Web
pages
on
your
Web
site.
When
you
embed
these
report
servlets
into
HTML
code,
you
use
a
JSP
file
include
statement
to
include
three
servlet
classes
together.
SLMReport
is
the
main
class
that
calls
two
additional
classes,
one
that
performs
the
database
query
to
retrieve
the
preferred
data
from
the
SLM
Database,
and
the
other
class
that
displays
the
data
for
viewing.
The
general
format
for
the
JSP
file
include
statement
is
as
shown
in
the
following
example:
<jsp:include
page="/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMCustomerOrderRankQuery
&di=com.tivoli.managed.gui.report.servlets.SLMCustomerOrderRankDisplay
&link=reportDetail.jsp
&fontcolor=black
&fontsize=2
&titlefontsize=2
&bgcolor=#EDEDEB
Appendix
A.
Customizing
SLM
Reports
35
&tablewidth=500"
flush="true"/>
In
this
example,
note
that
a
?
character
occurs
immediately
after
SLMReport.
This
character
designates
the
beginning
of
the
parameter
list
that
is
passed,
starting
with
the
qi
parameter.
Each
parameter
that
follows
in
the
list
is
separated
in
the
include
statement
with
the
&
character,
with
no
blank
spaces
between
parameters.
Note:
No
spaces
are
allowed
between
parameters,
however
for
this
example
spaces
are
included
for
readability.
In
this
example,
qi
is
the
query
interface
parameter
that
calls
the
class
named
SLMCustomerOrderRankQuery
to
obtain
specific
data
for
the
report,
and
di
is
the
display
interface
parameter
that
calls
the
SLMCustomerOrderRankDisplay
class
to
format
and
display
the
data
on
the
Web
site.
Note
that
the
preceding
query
and
display
classes
are
paired
together
in
the
overall
call
of
the
main
SLMReport
class.
Table
8
shows
the
other
available
pairs
of
query
classes
and
display
classes
that
you
can
specify
for
various
types
of
reports.
Table
8.
Available
Query
and
Display
class
servlet
pairs
Query
Class
Display
Class
Link
Needed
Purpose
SLMComponentSLAQuery
SLMComponentSLADisplay
Yes
Display
component
SLAs
SLMCustomerOrderRank
Query
SLMCustomerOrderRank
Display
Yes
Display
SLA
ranking
SLMCustomerRankQuery
SLMCustomerRankDisplay
Yes
Display
customer
ranking
SLMIntermediateResultData
Query
SLMIntermediateResultsTable
Yes
Display
the
SLO
Intermediate
Results
table.
SLMOfferingComponent
RankQuery
SLMOfferingComponent
RankDisplay
Yes
Display
offering
component
ranking
SLMOrderInfoQuery
SLMOrderInfoTable
No
Display
SLA
information
SLMParentSLAQuery
SLMParentSLADisplay
No
Display
parent
SLAs
SLMRealmRankQuery
SLMRealmRankDisplay
Yes
Display
realm
ranking
SLMResourceRankQuery
SLMResourceRankDisplay
Yes
Display
resource
ranking
SLMResultsDataQuery
SLMResultsDetailTable
Yes
Display
SLO
results
table
SLMResultsQuery
SLMGraphDetailTable
No
Display
graph
data
SLMResultsQuery
SLMResultsGraph
No
Display
graph
SLMScheduleDataQuery
SLMScheduleDetailTable
No
Display
Business
Schedule
table
36
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Table
8.
Available
Query
and
Display
class
servlet
pairs
(continued)
Query
Class
Display
Class
Link
Needed
Purpose
SLMTrendsQuery
SLMTrendsDetailTable
No
Display
Trend
table
SLMViolationsQuery
SLMViolationsDetailTable
Yes
Display
Violation
table
TSLACustomerCustomer
OrderStatusQuery
TSLACustomerCustomer
OrderStatusDisplay
Yes
Display
the
high-level
view
for
SLA
Status
by
Customers
TSLARealmCustomerStatus
Query
TSLARealmCustomerStatus
Display
Yes
Display
the
high-level
view
for
Customer
Status
by
Realms
Following
the
qi
and
di
parameters
are
additional
parameters
that
you
can
specify
to
link
to
the
next
Web
page
to
be
displayed
and
to
customize
certain
table
parameters
that
affect
the
resulting
display.
These
parameters
are
described
in
the
following
sections.
Linking
Web
Pages
and
JSP
Files
For
some
query
and
display
class
pairs,
you
must
also
specify
a
link
parameter,
which
specifies
the
next
Web
page
or
JSP
file
to
which
the
user
is
taken.
For
example,
the
parameter
&link=reportDetail.jsp
might
be
included
in
the
parameter
list
to
specify
the
next
JSP
file
to
which
you
are
taken.
Refer
to
the
Link
Needed
column
in
Table
8
on
page
36
to
see
which
of
the
display
classes
requires
a
link
to
be
specified
in
the
JSP
file
include
statement.
Customizing
Results
Tables
Because
the
servlet
results
are
displayed
in
tables,
you
can
also
customize
various
table
parameters
by
specifying
them
in
the
JSP
file
include
statement.
Table
9
shows
the
properties
that
can
be
customized.
Table
9.
Table
properties
that
can
be
customized
for
displaying
report
results
Table
property
Parameter
specified
Default
value
Table
background
color
bgcolor
#EDEDEB
Font
size
fontsize
2
Font
color
fontcolor
black
Font
face
fontface
Arial
Column
header
alignment
titlealign
center
(other
values:
right,
left)
Title
font
size
titlefontsize
2,
always
bold
Title
font
color
titlefontcolor
black
Title
font
face
titlefontface
Arial
Title
background
color
titlebgcolor
#CFDAE3
Table
width
tablewidth
100%
Table
border
border
0
Table
cell
spacing
cellspacing
2
Appendix
A.
Customizing
SLM
Reports
37
Table
9.
Table
properties
that
can
be
customized
for
displaying
report
results
(continued)
Table
property
Parameter
specified
Default
value
Table
cell
padding
cellpadding
2
For
example,
an
include
statement
might
have
table
parameters
specified
as
shown
in
the
following
example:
&fontcolor=blue&cellspacing=0&tablewidth=450&titlefontsize=4
Add
as
many
of
these
parameters
as
you
want,
appending
each
parameter
in
sequence,
with
no
blank
spaces
between
parameters,
and
prefacing
each
parameter
with
the
&
character.
Notes:
1.
Parameter
names
are
case
sensitive.
For
example,
specify
&titlealign=,
not
&titleAlign=.
2.
Do
not
use
frames
in
servlet
reports,
because
the
code
has
to
check
the
URL
of
the
current
report.
There
might
also
be
security
exposures
using
frames.
3.
In
non-English
language
environments,
the
UTF-8
character
set
should
be
specified
in
the
JSP
file,
for
example:
<%@
page
contentType="text/html;
charset=UTF-8"
%>
Refer
to
the
index.jsp
file
for
an
example
of
this
usage.
Customizing
User
Authentication
If
you
are
the
owner
or
administrator
for
the
Web
site
where
users
view
SLM
reports,
it
is
your
responsibility
to
associate
a
user
name
with
the
proper
authorization
level
for
accessing
SLM
reports
from
your
Web
site.
When
users
sign
on
to
your
Web
server,
you
should
have
their
user
authentication
defined
in
a
property
file
or
database.
You
or
your
administrator
must
decide
whether
users
should
have
unrestricted,
restricted,
or
external
access
to
report
data.
After
you
have
configured
your
Web
site
for
handling
user
authentication,
the
IBM
Tivoli
Service
Level
Advisor
report
servlets
then
make
use
of
this
information
when
retrieving
the
data
from
the
SLM
Database
to
display
in
SLM
reports.
This
section
describes
two
example
methods
that
IBM
Tivoli
Service
Level
Advisor
provides
for
user
authentication
using
the
JSP
files.
You
can
use
either
of
these
methods
or
develop
your
own
methods.
In
either
case,
the
task
is
to
associate
a
user
name
and
password
with
the
authentication
parameters
view,
customer,
realm,
portal
page,
time
zone,
usertype,
and
int.
The
two
methods
that
are
described
in
the
following
sections
are:
v
Authenticating
Users
From
Data
in
the
SLM
Database
v
Authenticating
Users
Using
a
Java
Bean
Authenticating
Users
From
Data
in
the
SLM
Database
Use
this
method
if
you
do
not
already
have
a
method
of
authenticating
users
by
logging
on
to
the
Web
server.
If
you
are
an
SLM
Administrator,
add
an
existing
user
name
from
the
local
operating
system
user
repository
into
the
SLM
Database,
and
associate
with
that
user
name
the
following
authorization
information:
v
User
name
(120
characters
maximum)
A
password
is
not
specified
for
this
user
name
because
this
user
should
already
be
defined
in
the
local
operating
system
user
registry,
and
assigned
a
valid
password
to
sign
on
to
the
system.
38
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
v
View
(an
integer
value
of
1,
2,
or
3,
defining
the
level
of
view
authority
that
this
user
has
to
view
report
data
on
all
customers,
realms,
and
SLA
types,
or
restricting
this
user
to
view
only
certain
customers,
realms
and
SLA
types)
v
Customer
Name
(255
characters
maximum,
indicating
a
specific
customer
to
which
the
user’s
view
is
restricted)
v
Realm
Name
(255
characters
maximum,
indicating
the
ID
of
a
specific
realm
to
which
the
user
view
is
restricted)
v
Time
zone
(time
zone
index
number,
which
is
specified
for
users
that
are
located
in
a
different
time
zone
than
the
SLM
Report
server)
v
Portal
Page
(the
name
of
the
JSP
file
to
be
directed
to
after
successfully
signing
on.
This
is
the
first
SLM
Report
web
page
that
is
displayed
for
this
user.
This
can
be
one
of
the
default
pages
that
is
assigned
to
the
particular
user
type
associated
with
this
name,
or
it
can
be
a
customized
JSP
file
that
you
designate.)
The
report.jsp
page
displays
the
default
high
level
status
report
page.
If
you
still
want
to
point
to
this
page
name,
but
do
not
want
to
view
the
associated
high
level
report,
add
hilevel=n
to
the
value
specified
in
the
–page
parameter
for
the
portal
page,
for
example:
-page
"report.jsp?hilevel=n"
The
default
page
for
hilevel=n
is
the
SLA
Ranking
page
displayed
in
Rolling
7
days
view.
If
you
do
not
want
to
see
these
default
ranking
pages,
specify
another
page
directly,
for
example:
-page
"customerRanking.jsp"
v
User
type
(an
integer
value
of
1,
2,
or
3,
specifying
the
level
of
detail
displayed
in
reports,
from
an
operations
(1),
executive
(2),
or
customer
(3)
perspective.
v
Enabling
display
of
intermediate
results
in
SLM
Reports.
If
enabled,
a
special
icon
appears
in
reports
where
appropriate
to
identify
results
from
intermediate
evaluations.
Note
that
if
intermediate
evaluation
results
are
enabled
for
display,
you
might
experience
slower
performance
because
of
the
additional
processing
required.
See
your
SLM
Administrator
for
help
in
obtaining
valid
user
names
for
access
to
SLM
Reports,
and
refer
to
the
Administrator’s
Guide
for
details
on
creating
and
managing
users.
Sample
HTML
Form
for
Logging
On
The
sample
HTML
form
code
is
included
in
the
login.jsp
file.
Locate
the
code
between
the
<FORM>
and
</FORM>
HTML
tags.
Authenticating
Users
Using
a
Java
Bean
You
can
use
this
method
if
you
already
have
a
way
of
authenticating
users
by
logging
on
to
Web
server.
In
this
case
it
is
your
responsibility
to
determine
how
to
store
the
association
of
that
user
name
with
the
authentication
properties
of
customer,
realm,
view,
portal
page,
user
type,
time
zone,
and
showInt
(enabling
the
display
of
intermediate
evaluation
results
in
reports).
With
this
method
of
user
authentication,
the
SLM
Database
is
not
used
to
store
this
information.
To
authenticate
users
for
SLM
Reports
by
using
a
Java
bean,
perform
the
following
steps
to
customize
the
Web
page:
1.
For
the
user
that
is
currently
logged
on
to
the
Web
server,
provide
the
associated
values
for
customer,
realm,
view,
portal
page,
user
type,
time
zone,
and
showInt
to
the
Java
bean.
Appendix
A.
Customizing
SLM
Reports
39
2.
Create
an
HTML
form
button
called
View
Reports
to
call
the
servlet
class
SLMBeanAuthentication,
which
uses
the
properties
of
customer,
realm,
view,
portal
page,
user
type,
time
zone,
and
showInt
for
the
user
to
provide
access
control,
maintaining
the
level
of
access
until
the
user
signs
off
the
Web
site
or
the
session
time
expires.
The
index2.jsp
file
included
in
the
set
of
JSP
files
with
the
IBM
Tivoli
Service
Level
Advisor
product
provides
samples
of
these
customization
steps,
as
shown
in
the
following
sections.
Sample
Code
to
Set
Authentication
Values
in
the
Java
Bean
The
following
sample
code
sets
the
authentication
values
for
the
user
into
the
Java
bean:
<jsp:useBean
id="Login"
class="com.tivoli.managed.gui.report.servlets.SLMUserInfoImpl"
scope="session"
/>
<jsp:setProperty
name="Login"
property="consumer"
value="<%=consumer%>"/>
<!--
to
set
directly
and
assume
that
the
value
is
restricted,
the
line
will
be
like
this:
jsp:setProperty
name="Login"
property="consumer"
value="restricted"
-->
<jsp:setProperty
name="Login"
property="realm"
value="<%=realm%>"/>
<jsp:setProperty
name="Login"
property="view"
value="<%=view%>"/>
<jsp:setProperty
name="Login"
property="portalPage"
value="<%=portalPage%>"/>
<jsp:setProperty
name="Login"
property="userType"
value="<%=userType%>"/>
<jsp:setProperty
name="Login"
property="timezone"
value="<%=timezone%>"/>
<jsp:setProperty
name="Login"
property="showIntmed"
value="<%=showIntmed%>"/>
This
code
calls
the
SLMUserInfoImpl
class
and
passes
in
the
values
for
customer,
realm,
view,
portal
page,
user
type,
time
zone,
and
showInt.
If
you
want
to
set
the
property
directly
without
using
a
variable,
the
format
would
be,
for
the
view
property,
as
shown
in
the
following
example:
<jsp:useBean
id="Login"
class="com.tivoli.managed.gui.report.servlets.SLMUserInfoImpl"
scope="session"/>
<jsp:setProperty
name="Login"property="view"value="restricted
"/>
Sample
HTML
Form
Button
Code
The
following
sample
HTML
form
code
creates
a
button
called
View
Reports
that
is
displayed
in
your
customer’s
Web
site.
When
you
click
this
button,
the
authentication
values
for
your
user
name
are
passed
to
the
Java
bean
and
the
level
of
authentication
is
set
for
that
session.
The
link
page
then
displays
the
first
report
page
that
you
specified.
<FORM
action="servlet/com.tivoli.managed.gui.report.servlets.SLMBeanAuthentication"
method=POST>
<INPUT
type=submit
name=submit
value="<%=rsc.getString("ViewReports")%>">
</FORM>
40
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Including
a
Company
Logo
The
default
setting
displays
the
Tivoli
and
IBM
company
logos
at
the
top
of
every
report
page,
in
a
black
banner
that
spans
the
entire
page.
You
can
override
this
default
setting
and
replace
the
banner
with
your
own
company
logo
or
graphic
images.
At
the
bottom
of
the
pageHeader.jsp
file,
the
logo
image
files
are
called
from
the
following
HTML
table:
<table
border="0"
width="100%"
cellspacing="0"
cellpadding="0">
<tr>
<td
width="100%"
bgcolor="#000000">
<img
src="product_name.gif"
alt="<%=tslaAlt%>"></td>
<td
width="303">
<img
src="ibm_mark.gif"
alt="<%=ibmAlt%>"></td>
</tr>
</table>
The
files
named
product_name.gif
and
ibm_mark.gif
are
the
default
image
graphics
that
are
displayed
in
this
single
cell
table.
You
can
replace
these
graphic
files
with
your
own
images.
The
pageHeader.jsp
file
is
called
by
the
other
JSP
files
to
display
the
same
logo
images
on
all
report
pages.
Note:
For
accessibility,
alternate
text
is
also
assigned
to
these
images.
See
the
string
definitions
for
the
tslaAlt
and
ibmAlt
parameters
in
pageHeader.jsp,
and
modify
them
as
needed
to
provide
accessibility
function
with
your
replacement
images.
You
can
enter
the
alternate
text
in
your
language
directly
if
you
do
not
need
to
handle
multiple
languages.
Understanding
the
Links
Under
the
Banner
When
you
display
SLM
reports,
at
the
top
of
each
report
page
is
a
set
of
links
that
perform
various
functions:
v
Report
Definitions
v
Tips
v
Printable
Version
v
Export
to
MS
Excel
v
Refresh
v
Sign
Off
These
links
are
explained
in
“Additional
Web
Links”
on
page
20.
Using
the
printRefreshOff.jsp
JSP
file,
these
links
are
defined
in
a
single
cell
table,
and
included
in
the
report
page.
Report
Definitions
This
link
displays
a
short
description
of
each
available
report
type.
The
code
in
printRefreshOff.jsp
for
this
link
is
as
shown
in
the
following
example:
<!--
-----------
Report
Definitions
----------
-->
<%if(currentPage!=null
&&
!currentPage.equals("/SLMReport/reportDefinitions.jsp")){%>
<img
src="reportdef_icon.gif"
alt="<%=rsc.getString("ReportDefinitions")%>">
<a
href="reportDefinitions.jsp"
target="_parent"><%=rsc.getString("ReportDefinitions")%></a>
<%}//end
if
%>
Appendix
A.
Customizing
SLM
Reports
41
Tips
This
link
displays
some
hints,
and
tips
for
printing
reports
on
your
local
printer,
using
your
Web
browser
function.
The
code
in
printRefreshOff.jsp
for
this
link
is
as
shown
in
the
following
example:
<!--
-----------
Tips
------------
-->
<img
src="print_tips_icon.gif"
alt="<%=rsc.getString("PrintTips")%>">
<a
href="printTips.jsp"
target="blank"><%=rsc.getString("PrintTips")%></a>
Printable
Version
This
link
opens
a
separate
browser
page
containing
a
version
of
the
current
report
suitable
for
printing.
Input
selection
fields,
buttons,
links,
and
filter
criteria
(drop-down
lists)
are
displayed
in
read-only
format.
Use
the
function
for
your
browser
to
the
report
Web
page.
If
you
have
Adobe
Acrobat
installed
on
your
system,
use
this
link
to
to
a
file
format.
From
your
browser
page,
which
contains
the
contents
of
your
current
report,
use
your
Adobe
Distiller
function
to
create
a
printable
version
of
your
report.
Note:
Reports
should
be
printed
in
Landscape-oriented
mode.
The
code
in
printRefreshOff.jsp
for
this
link
is
as
shown
in
the
following
example:
<!--
-----------
Printable
Version
------------
-->
<img
src="printer_icon.gif"
alt="<%=rsc.getString("PrintableVersion")%>">
<a
href="<%=request.getRequestURI()+context%>"
target=_blank><%=rsc.getString("PrintableVersion")%></a>
Export
to
MS
Excel
Use
this
link
to
export
non-graphical
report
information
to
a
Microsoft
Excel
spreadsheet.
The
code
in
printRefreshOff.jsp
for
this
link
is
shown
in
the
following
example:
<!--
-----------
Excel
Version
------------
-->
<%
boolean
excelSupported
=
false;
excelSupported
=
utils.getBrowserHeader(request);
if
(excelSupported
&&
(currentPage!=null
&&
!currentPage.equals("/SLMReport/reportDefinitions.jsp")
&&
!currentPage.endsWith("configureStatusAssociation.jsp"))
)
{
%>
<img
src="exportexcel_icon.gif"
alt="<%=rsc.getString("ExcelVersion")%>">
<%if(currentPage!=null
&&
!currentPage.endsWith("graph.jsp")
){
%>
<a
href="<%=request.getRequestURI()+context+"&
"+SLMServletParameters.PARAM_EXCEL_VERSION+"=YES"%>"
target=_blank><%=rsc.getString("ExcelVersion")%></a>
42
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
<%}
out
chart
data
instead
of
the
chart
when
exporting
to
excel
else{
%>
<a
href="<%="graphData.jsp"+context+"&
"+SLMServletParameters.PARAM_EXCEL_VERSION+"=YES&showAllData=YES"%>"
target=_blank><%=rsc.getString("ExcelVersion")%></a>
<%}%>
<%}//end
if
%>
Refreshing
the
Report
Table
Display
At
the
beginning
of
each
Web
page
the
Refresh
link
is
displayed,
as
an
example
of
what
you
can
incorporate
into
your
Web
page
to
refresh
the
report
table
display.
After
you
click
this
link,
a
new
database
query
is
made,
and
the
resulting
updates
to
the
report
table
are
displayed.
The
HTML
code
in
the
printRefreshOff.jsp
JSP
file
that
performs
this
function
is
shown
in
the
following
example:
<!--
-----------
Refresh
---------------
-->
<!--
For
refreshing,
pass
in
the
filters
to
keep
the
same
query.
Do
not
pass
in
the
page
parameter
so
that
the
servlet
will
know
that
it
needs
to
go
to
the
database
again.
-->
<img
src="refresh_icon.gif"
alt="<%=rsc.getString("Refresh")%>">
<a
href="<%=link%>"><%=rsc.getString("Refresh")%></a>
When
the
Refresh
link
is
clicked,
the
JSP
file
calls
itself,
performing
another
database
query
and
displaying
the
table
again
with
updated
information.
The
variable
link
is
obtained
by
calling
TSLAJSPDisplayUtils.getRefreshLink(request),
as
shown
in
the
following
example:
<%
TSLAJSPDisplayUtils
utils=new
TSLAJSPDisplayUtils(request),
String
link=utils.getRefreshLink(request);
%>
Logging
Off
From
the
Report
Display
The
Sign
Off
link
signs
off
your
user
name
from
the
SLM
Reports
console
on
your
Web
site.
The
following
code
runs
an
IBM
WebSphere
Application
Server
servlet,
ibm_security_logout,
and
links
to
the
Login
Web
page,
referred
to
in
this
example
as
login.jsp:
<!--
-----------
Sign
Off
--------------
-->
<!--
link
parameter
passed
in
at
the
Sign
Off
link
below
is
the
Login
page
name.
The
path
is
in
relation
to
the
servlet
directory.
The
default
table
with
for
logout
message
is
100%
-->
<%
//Show
the
sign-off
button
only
if
user
authentication
has
been
enabled
(getUserName
returns
something
other
than
NO_SECURITY).
if
(showSignOff)
{
%>
Appendix
A.
Customizing
SLM
Reports
43
<img
src="signoff_icon.gif"
alt="<%=rsc.getString("SignOff")%>">
<a
href="ibm_security_logout?logoutExitPage=/login.jsp">
<%=rsc.getString("SignOff")%></a>
<%
}
%>
The
path
specified
for
the
login
file
login.jsp
is
relative
to
the
servlet
directory.
Getting
Filter
Parameters
Queries
to
the
SLM
Database
can
be
filtered
to
only
receive
data
on
specific
customers,
SLAs,
resources,
metrics,
and
other
attributes.
For
example,
in
the
resourceRanking.jsp
file,
a
search
function
is
used
for
a
particular
resource
using
the
frscm
filter
parameter
as
shown
in
the
following
example:
<%
String
search
=
request.getParameter("frscm");
%>
Additional
database
query
filters
are
listed
in
Table
10..
Table
10.
Available
database
query
filters
that
can
be
specified
Filter
parameter
Parameter
Name
Value
Customer
fcu
The
name
of
an
existing
customer.
Customer
match
(used
for
searching)
fcm
As
entered
by
the
user
End
date
fed
Only
ISO
format
is
acceptable.
Use
the
hyphen
character
″-″
as
the
separator,
for
example:
fsdd=2003-12-31
Metric
name
fmn
The
name
of
an
existing
metric.
Offering
fso
The
name
of
an
existing
offering.
Offering
component
fst
The
name
of
an
existing
offering
component.
Offering
component
match
focrm
As
entered
by
the
user
Realm
match
frm
As
entered
by
the
user
Realm
name
frn
The
name
of
an
existing
realm
Resource
frsc
The
name
of
an
existing
resource.
Resource
match
frscm
As
entered
by
the
user
Schedule
state
fss
An
available
schedule
state
key,
for
example:
SCHEDULE_PEAK.
SLA
fco
The
name
of
an
existing
SLA.
SLA
match
fcom
As
entered
by
the
user
SLA
type
match
fslam
As
entered
by
the
user
SLAType
fslatype
(external=1;
internal=2;
outsourced=3;
all=0)
44
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Table
10.
Available
database
query
filters
that
can
be
specified
(continued)
Filter
parameter
Parameter
Name
Value
Start
date
fsd
Available
values:
v
yesterday
v
week
(last
week)
v
month
(last
month)
v
quarter
(last
quarter)
v
year
(last
year)
v
wtd
(week
to
date)
v
mtd
(month
to
date)
v
qtd
(quarter
to
date)
v
ytd
(year
to
date)
v
r24h
(rolling
24
hours)
v
r7d
(rolling
7
days)
v
r4w
(rolling
4
weeks)
v
r30d
(rolling
30
days)
v
r365d
(rolling
365
days)
v
ytelm
(year
to
end
of
last
month)
For
example:
fsd=month
Start
date
(in
ISO
format)
fsdd
Only
ISO
format
is
acceptable.
Use
the
hyphen
character
″-″
as
the
separator,
for
example:
fsdd=2003-12-31
Value
type
fvt
(min=1;
avg=2;
max=3
Example:
fvt=3)
If
you
manually
pass
a
parameter,
such
as
passing
into
a
link,
encode
the
string
before
passing
it
in.
Spaces
are
replaced
by
the
plus
sign
(+)
character.
Add
the
encoded
characters
directly
or
use
a
class
to
encode
a
string
by
calling
SLMDisplayUtils.encodeURLString(String
s).
For
example,
passing
in
a
manually
encoded
string
(usually
applied
for
names
that
have
spaces
only),
you
might
specify
it
similar
to
the
following
example:
<a
href="page.jsp?fcu=My+customer>My
customer</a>
Example
using
the
encoder:
<a
href="page.jsp?fcu=<%=SLMDislayUtils.encodeURLString("My
customer
&
your
customer")%>>My
customer
&
your
customer</a>
Note:
Non-English
language
characters
in
filter
values
must
be
encoded
with
their
hexadecimal
equivalent.
Including
Selection
Fields
and
Input
Fields
In
addition
to
the
selection
fields
that
are
already
available
in
SLM
reports,
you
can
include
one
or
more
selection
or
input
fields
at
the
top
of
the
Web
page.
The
following
list
of
selection
fields
are
currently
included
in
reports:
Report
Type
Use
this
drop-down
list
to
jump
to
any
other
available
report
page.
The
links.jsp
file
controls
this
list.
Appendix
A.
Customizing
SLM
Reports
45
Time
Period
Use
this
drop-down
list
to
change
the
time
period
used
to
retrieve
and
display
results
data.
Selecting
a
different
time
period
from
this
list
causes
the
report
to
display
the
results
data
for
that
time
period.
Set
the
time
period
to
values
such
as
Yesterday,
Last
Month,
Week
to
date,
and
Rolling
7
days.
This
selection
field
is
controlled
by
the
periods.jsp
and
hiLevelPeriods.jsp
files.
Start
Date
Use
this
field
to
enter
the
start
date
of
the
period
for
which
you
want
to
view
data.
This
date
must
be
in
the
format
of
yyyy-mm-dd,
for
example,
2002-12-31.
Enter
the
date
directly
in
this
format,
or
click
the
Calendar
icon
to
the
right
of
the
input
field
to
navigate
to
the
preferred
day.
End
Date
Use
this
field
to
enter
the
end
date
of
the
period
for
which
you
want
to
view
data.
This
date
must
be
in
the
format
of
yyyy-mm-dd,
for
example,
2002-12-31.
Enter
the
date
directly
in
this
format,
or
click
the
calendar
icon
to
the
right
of
the
input
field
to
navigate
to
the
preferred
day.
SLA
Type
Use
this
drop-down
list
to
specify
the
type
of
SLA
to
include
in
reports.
Possible
selections
include:
v
All
v
Internal
v
External
v
Outsourced
The
HTML
code
to
include
these
selection
fields
in
the
Web
page
is
similar
to
the
following,
as
found
in
the
customerRanking.jsp
file:
<!--
-------------
Filter
Criteria
----------
-->
<%--
Pass
in
3
parameters:
-
page
(ex:
customerRanking.jsp)
-
searchFieldName:
the
name
of
the
search
field
(see
Administrator
Guide
for
ITSLA
for
more
details)
-
searchLabel:
the
label
or
text
for
the
search
input
(if
none
is
specified,
the
text
would
be
"Search"
only
--%>
<%
String
filterCriteriaPg
=
"filterCriteria.jsp?currentPage=customerRanking.jsp
&searchFieldName=fcm&searchLabel=CustomerSearch";
%>
<jsp:include
page="<%=filterCriteriaPg%>"
flush="true"/>
For
a
multiple
language
report,
the
value
for
searchLabel
is
the
key
name
of
that
label.
The
filterCriteria.jsp
file
gets
the
translated
name
using
that
key
name.
Refer
to
the
links.jsp,
periods.jsp,
hiLevelPeriods.jsp,
and
slaTypes.jsp
files
for
details
on
the
specific
selections
in
these
fields.
Including
the
Maximum
Rows
to
Display
Function
At
the
beginning
of
the
charts
and
tables
in
the
report
Web
pages,
use
the
Maximum
rows
to
display
drop-down
list
to
select
the
number
of
rows
that
are
displayed
in
the
table.
For
the
ranking
reports,
the
charts
above
the
tables
are
also
affected
because
they
display
only
the
data
reflected
in
the
rows
in
the
table.
The
46
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
maximumRowsToDisplay.jsp
file
contains
the
code
that
manages
this
function.
The
resulting
display
on
the
Web
page
looks
similar
to
Figure
13
on
page
20.
Selecting
the
preferred
number
causes
the
JSP
file
to
call
itself,
passing
in
the
current
page
name,
filters.toString()
along
with
other
parameters.
New
parameters
are
passed
as
hidden
input
fields
to
maintain
the
same
filtering
on
the
new
database
query,
along
with
the
new
maximum
number
of
rows
to
display
when
the
Web
page
is
refreshed
and
displayed
again.
From
a
main
page,
such
as
customerRanking.jsp,
call
the
maximumRowsToDisplay.jsp
file
as
shown
in
the
following
example:
<jsp:include
page="maximumRowsToDisplay.jsp?page=customerRanking.jsp&row=crrow"
flush="true"/>
Note:
Always
pass
in
two
parameters:
page
the
current
page
name,
for
example,
customerRanking.jsp
row
the
row
parameter
for
the
specified
ranking
page.
For
example,
for
the
customerRanking.jsp
file,
which
is
a
ranking
page,
the
row
parameter
defined
in
Table
11
is
crrow,
so
the
value
of
row
is
set
to
crrow.
Other
report
servlets
use
different
parameters
to
control
the
maximum
number
of
rows.
See
Table
11
for
the
available
parameters.
Table
11.
Parameters
used
to
control
the
maximum
number
of
rows
that
are
displayed
for
various
reports.
Row
parameter:
Defined
parameter
name
Associated
Component
SLAs
csrow
Associated
Parent
SLAs
psrow
Business
schedule
srow
Customer
ranking
crrow
Customer
Status
by
Realms
rcusrow
Graph
grow
(for
graph
data
table)
Intermediate
SLO
Results
irsltrow
Offering
component
ranking
ocrrow
Realm
ranking
rlmrrow
Resource
ranking
rscrrow
Result
reports
rsltrow
SLA
information
oirow
SLA
ranking
corrow
SLA
Status
by
Customers
cucosrow
SLA
type
ranking
slarrow
Trend
reports
trndrow
Violations
reports
viorow
Appendix
A.
Customizing
SLM
Reports
47
Customizing
Report
Column
Names
The
data
that
is
displayed
in
each
column
of
the
report
tables,
and
the
order
in
which
the
columns
are
displayed,
is
controlled
by
the
report
servlet.
Default
column
headers
are
also
provided
by
the
report
servlets,
but
these
can
be
customized
by
the
customer,
passing
the
appropriate
parameters
in
the
servlet
include
statement.
For
example,
a
report
table
might
have
Customer
defined
as
the
title
of
the
first
column.
To
change
this
label
to
My
Customer,
the
following
code
is
appended
to
the
parameters
passed
to
the
servlet
include
statement:
&lcu=My+Customer
where
lcu
is
the
label
parameter
for
the
Customer
column,
and
the
plus
sign
(+)
signifies
a
space
character
that
the
servlet
replaces
with
a
blank
space
in
the
displayed
output.
For
example,
in
the
customer.jsp
file,
the
servlet
embed
statement
would
be
similar
to
the
following
example:
<jsp:include
page="/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMFilterRankQuery
&di=com.tivoli.managed.gui.report.servlets.SLMFilterRankDisplay
&filter=fco
&link=custReportDetail.jsp
&fontcolor=black
&fontsize=2
&titlefontsize=2
&bgcolor=#EDEDEB
&tablewidth=500
&lcu=My+Customer"
flush="true"/>
Additional
label
parameters
that
can
be
customized
in
report
tables
are
listed,
along
with
their
associated
parameter
name,
in
Table
12.
Table
12.
Passing
in
these
parameters
can
modify
titles
of
report
table
columns.
Label
parameter
Parameter
name
Actual
value
lmav
Association
Date
lsad
Avg
(Average
metric
value
type)
lavg
Breach
value
lbv
Customer
lcu
Dates
ld
Details
lsd
Detection
date
ldd
Dissociation
Date
lsdd
End
time
lett
Evaluation
time
lget
Frequency
lfq
Graph
lg
48
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Table
12.
Passing
in
these
parameters
can
modify
titles
of
report
table
columns.
(continued)
Label
parameter
Parameter
name
Internal
use
only
liu
Max
(Maximum
metric
value
type)
lmax
(such
as
max
in
the
Results
Details
report
under
the
Metric
Value
column)
Mean
value
lmv
Metric
lmn
Min
(Minimum
metric
value
type)
lmin
Number
of
trends
ltn
Number
of
violations
lvn
Offering
lso
Offering
component
lst
Offering
description
lsod
Projected
state
lps
Projected
violation
date
lpvd
Rank
lrk
Realm
lrn
Resource
lrsc
Schedule
state
lss
Service
ID
lsvcid
Service
name
lsvcn
SLA
ID
lco
SLA
name
lonm
SLA
type
lsla
Start
time
lstt
Start
timezone
lstz
State
ls
Time
zone
ltz
Total
(total
metric
value
type)
ltot
Total
sample
ltos
Trend
period
ltap
Units
lmu
View
Intermediate
SLO
Chart
licl
Violation
date
lvd
Violation
value
lvv
%Error
(Confidence
factor)
lcf
Customizing
Graphs
Use
a
Web
link
from
a
metric
value
to
display
a
graph
of
the
report
information.
Because
a
graph
is
an
image,
to
embed
a
graph
in
a
JSP
file,
all
filters
passed
in
the
link
must
be
captured
to
draw
the
resulting
graph.
See
the
graph.jsp
file
as
an
example.
Appendix
A.
Customizing
SLM
Reports
49
To
embed
the
graph
image,
include
code
similar
to
the
following
example:
<IMG
SRC="servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMResultsQuery
&di=com.tivoli.managed.gui.report.servlets.SLMResultsGraph
&data1ChartType=AREA
&chartWidth=700
&chartHeight=350
&legendVisible=true
&<%=filters.toString()+titles%>"
ALT=’<%=graphAlt%>’>
The
parameter
filters.toString()
is
the
buffer
string
that
contains
all
of
the
filters.
This
must
be
included
in
the
embedded
statement
to
product
the
graph.
Data1ChartType,
chartWidth,
chartHeight,
and
legendVisible
are
additional
parameters
used
in
this
example
to
further
customize
the
resulting
graph.
Table
13
shows
the
list
of
graph
parameters
that
are
available.
Table
13.
Parameters
available
for
customizing
graphs
Customized
property
Parameter
for
the
property
Character
length
for
filters
in
exploded
chart
charlength(integer)
-
this
is
only
used
for
the
exploded
chart
in
ranking
pages
Chart
area
background
chartAreaBg
(color
name,
see
list)
Chart
background
chartBg
(color
name
only)
Chart
height
chartHeight
(integer,
example:
chartHeight=400)
Chart
type
data1ChartType
(area,
bar,
plot)
Chart
width
chartWidth
(integer)
Graph
encoder
ge
(png
or
jpeg)
Grid
color
gridColor
(color
name
only)
Grid
visible
gridVisible
(true
or
false)
Header
text
headerText
(name
of
header,
for
example:
headerText=graph+title)
Legend
visible
legendVisible
(true
or
false)
Plot
area
background
plotAreaBg
(color
name
only)
For
example:
<IMG
SRC="servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMResultsQuery
&di=com.tivoli.managed.gui.report.servlets.SLMResultsGraph
&chartAreaBg=white
&plotAreaBg=blue
&headerText=Graph+Title”>
You
can
include
the
following
colors:
v
Black
v
Blue
v
Cyan
v
DarkGray
v
Gray
50
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
v
Green
v
LightGray
v
Magenta
v
Orange
v
Pink
v
Red
v
White
v
Yellow
You
can
optionally
include
graph
data
in
the
Web
page
with
the
graph.
See
the
graph.jsp
file
for
an
example,
showing
where
you
need
to
remove
starting
and
ending
comment
lines
such
as:
<%
--
remove
this
line
to
view
chart
data
Be
sure
to
remove
both
starting
and
ending
comments.
Resizing
Graphs
If
you
find
that
certain
reports
are
not
displaying
fully,
for
example,
if
the
legend
does
not
display
fully
on
the
graph,
you
can
resize
the
chart
height
and
width
by
adjusting
the
values
for
chartHeight
and
chartWidth.
For
example:
&chartHeight=500
&chartWidth=600
Replacing
the
Back
and
Next
Buttons
The
image
files
backButton.gif
and
nextButton.gif
are
called
from
the
servlets.
To
change
these
buttons
to
a
different
displayed
image,
replace
these
files
with
your
own,
but
keep
these
same
file
names.
Creating
Reports
with
Third-Party
Reporting
Software
Use
your
third-party
reporting
software
to
present
SLM
Reports
information
in
different
formats.
The
IBM
Tivoli
Service
Level
Advisor
product
provides
three
views
that
correspond
to
reports
available
through
SLM
Reports:
v
Resultview:
Contains
information
to
build
a
SLO
Results
report
v
Violationview:
Contains
information
to
build
a
Violations
report
v
Trendview:
Contains
information
to
build
a
Trends
report
While
the
actual
procedure
varies
with
your
software,
you
can
follow
this
general
process
to
create
reports
with
third-party
reporting
software:
1.
Connect
to
the
SLM
Database
(dyk_cat).
2.
Open
any
of
the
following
views:
v
Resultview
v
Trendview
v
Violationview3.
If
you
opened
the
Resultview
view,
the
evaluator
type
determines
whether
the
value
is
an
average
or
a
sum.
To
summarize
the
data
in
a
similar
manner
as
SLM
Reports,
check
the
evaluator
type
attribute
to
understand
how
to
present
the
information.
If
the
evaluator
type
has
a
value
of
4,
the
information
is
an
Appendix
A.
Customizing
SLM
Reports
51
average
of
all
of
the
average
values
in
the
reporting
period.
If
the
evaluator
type
is
5,
the
information
is
a
sum
of
all
the
average
values,
and
labeled
as
a
total
value.
4.
Create
your
report
in
the
preferred
format.
Adding
the
Configure
Status
Association
Link
You
can
add
the
following
link
to
configure
the
status
association
on
the
high
level
status
report:
<a
href=configureStatusAssociation.jsp?prevpg=report.jsp
<%=filters%>>
<%=rsc.getString("ConfigureStatusAssociation")%></a>
The
prevpg
operator
specifies
the
Web
page
where
the
link
is
located.
When
you
finish
configuring,
you
are
redirected
to
this
page.
If
prevpg
is
not
specified
and
authentication
is
enabled,
you
are
redirected
to
the
portal
page.
If
prevpg
is
not
specified
and
authentication
is
not
enabled,
the
default
page
is
the
common
portal
page
defined
in
the
web.xml
file
as
shown
in
the
following
example:
<init-param>
<param-name>tsla.commonPortalPage</param-name>
<param-value>report.jsp</param-value>
</init-param>
The
default
setting
passes
in
the
time
period,
start
date,
end
date,
and
row
view
parameters
to
filters
(<%=filters%>>)
if
they
are
not
blank.
Filters
must
reflect
what
you
have
selected
on
that
page,
because
after
finishing
configuring,
you
are
redirected
to
the
same
page
from
where
you
started.
The
<%=rsc.getString("ConfigureStatusAssociation")%>
parameter
is
used
to
display
any
text
in
different
languages.
If
you
want
to
display
text
in
your
language
only,
you
can
enter
the
text
directly,
for
example,
to
display
the
phrase,
Configure
Status
Association
in
the
English
language
only,
specify
it
in
the
link
command
directly,
as
shown
in
the
following
example:
<a
href=configureStatusAssociation.jsp?prevpg=report.jsp
<%=filters.toString()%>>
Configure
Status
Association</a>
You
can
add
this
link
to
any
page
in
your
reports
that
you
prefer.
These
configuration
settings
apply
to
all
users.
Configuring
the
Configure
Status
Association
Page
The
developer
of
the
Web
pages
can
make
any
changes
to
the
Configure
Status
Association
page,
except
the
following
area:
<%--
-----------*********
Do
not
delete
this
section
*********------
--%>
<%--
pass
in
the
current
page
name
so
that
after
configuring
and
click
OK
or
Cancel,
the
user
is
taken
back
to
the
page
he/she
is
viewing
--%>
<input
type=hidden
name="prevpg"
value="<%=prevPg%>">
<input
type=hidden
name="prevpgf"
value="<%=pageFilters%>">
<input
type=hidden
name="spg"
value="configureStatusAssociation.jsp">
<input
type=hidden
name="applyFilters"
value="<%=request.getQueryString()%>">
<%--
-----------------
End
of
do
not
delete
------------------
--%>
52
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
If
the
line
<input
type=hidden
name="prevpg"
value="<%=currentPg%>">
is
removed,
the
default
page
for
that
user
is
always
displayed
after
the
user
finishes
configuring
status
and
all
filters
are
not
passed
in.
If
the
line:
<input
type=hidden
name="prevpgf"
value="<%=pageFilters%>">
is
removed,
a
500
Error
message
is
displayed
after
the
user
clicks
OK
or
Cancel.
Refer
to
the
configureStatusAssociation.jsp
for
information
on
how
to
get
page
filters.
If
the
line
<input
type=hidden
name="spg"
value="configureStatusAssociation.jsp">
is
removed,
do
not
change
the
name
of
the
page
from
configureStatusAssociation.jsp
to
some
other
name.
By
default,
if
this
line
is
not
in
the
code,
the
default
page
configureStatusAssociation.jsp
is
called
when
you
click
Restore
Defaults.
If
you
change
this
name
to
the
name
of
a
file
that
does
not
exist,
you
receive
an
error
telling
you
that
the
page
cannot
be
found.
If
the
line
<input
type=hidden
name="applyfilters"
value=<%=request.getQueryString()%>
is
removed,
after
you
click
OK,
all
of
the
filters
for
the
previous
page
are
removed.
If
you
click
Cancel
or
OK
to
go
back
to
the
previous
page,
it
is
not
the
last
page
that
was
displayed.
For
example,
the
previous
page
might
have
been
displayed
using
a
time
period
of
Rolling
7
days,
but
when
the
filters
are
removed,
the
time
period
reverts
to
All
Dates,
resulting
in
a
different
report
display.
Accessing
Reports
from
the
Report
Link
in
Escalated
When
you
use
notification
of
violations,
trends
and
trend
cancelled
events,
you
can
include
a
report
link
in
the
message.
The
recipient
can
then
click
the
link
and
be
directed
to
the
report
details
of
the
event
notification.
The
default
page
completeReportDetail.jsp
displays
the
Report
Detail
tables,
including
SLA
information,
parent
SLAs,
component
SLAs,
the
business
schedule,
results,
trends
and
violations.
If
an
SLM
Reports
session
is
currently
active
in
your
Web
browser,
clicking
the
link
in
the
immediately
directs
you
to
the
report
details.
If
an
active
SLM
Reports
session
is
not
currently
active
when
the
report
link
is
clicked,
you
need
to
first
be
directed
to
the
SLM
Reports
sign
on
page,
and
after
signing
on
to
SLM
Reports,
forwarded
to
the
Report
Detail
page.
To
accomplish
this
redirection
after
signing
on,
the
following
lines
of
JSP
file
code
must
be
added
to
your
customized
version
of
the
Report
Detail
page,
similar
to
the
completeReportDetail.jsp:
<%--
--------------
Redirect
user
to
logon
page
when
the
session
is
timed
out
--%>
<%@
page
import="com.tivoli.managed.gui.report.servlets.SLMUserInfo"
%>
<%@
page
import="com.tivoli.managed.gui.report.servlets.SLMReport"
%>
<%@
page
import="com.tivoli.managed.gui.report.servlets.SLMEmailInfo"
%>
<%@
page
import="com.tivoli.managed.gui.report.servlets.SLMServletParameters"
%>
<%@
page
import="com.tivoli.managed.gui.report.servlets.SLMReportConstants"
%>
<%
TSLAJSPDisplayUtils
utils
=
new
TSLAJSPDisplayUtils();
int
authentication
=
SLMReport.authentication;
if(authentication
==
SLMReportConstants.AUTHENTICATION_SESSION){
session
=
request.getSession();
SLMUserInfo
userInfo
=
Appendix
A.
Customizing
SLM
Reports
53
(SLMUserInfo)session.getAttribute(SLMServletParameters.PARAM_SESSION_USER_INFO);
if(userInfo==null)
{
//
Below
is
to
check
if
request
is
from
the
report
link
in
the
violation
and
-->
//
trend
events
email,
it
saves
the
page
name
to
forward
to
the
page
after
-->
//
logon
complete.
Note:
if
this
section
of
code
is
removed,
a
report
link
-->
//
click
from
the
will
not
forward
to
the
operation
overall
details
report
//
page,
i.e.,
completeReportDetail.jsp
after
user
logs
on
-->
String
fromEmail
=
request.getParameter("fmail");
SLMEmailInfo
emailInfo
=
new
SLMEmailInfo();
if
(fromEmail
!=
null
&&
fromEmail.equals("y")){
String
currentURL
=
request.getServletPath()
+
"?"
+
request.getQueryString();
emailInfo.setForwardPage
(currentURL);
}else{
String
currentPage
=
request.getServletPath()+"?"+utils.getTimeoutFilters(request.getQueryString());
emailInfo.setForwardPage
(currentPage);
}
session.setAttribute(SLMServletParameters.PARAM_SESSION_EMAIL_LINK,
emailInfo);
response.sendRedirect(SLMReport.SIGNON_PAGE+"?timeout=y");
return;
}//end
if
userInfo
}//end
if
authentication
Controlling
the
Number
of
Top
Violations
and
Trends
In
the
various
ranking
reports,
there
are
several
charts
that
you
can
choose
from
that
display
the
top
n
number
of
realms,
customers,
SLAs,
or
SLA
types
with
the
most
violations
and
trends.
Customize
the
number
n
by
specifying
the
topCount
parameter
in
your
servlet
code.
For
example:
<%
String
includePg
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMCustomerRankQuery
&di=com.tivoli.managed.gui.report.servlets.SLMCustomerRankDisplay
&link=reportDetail.jsp
&graphLink=explodedGraph.jsp
&viewDataLink=viewChartData.jsp
&topCount=20"+titles;
%>
<jsp:include
page="<%=includePg%>"
flush="true"/>
Pointing
to
Customized
Exploded
Chart
and
Chart
View
Data
JSP
Files
The
default
setting
for
the
JSP
file
name
for
the
exploded
chart
is
explodedGraph.jsp,
and
for
the
chart
view
data,
the
file
name
is
viewChartData.jsp.
To
point
users
to
pages
other
than
these,
include
graphLink=<exploded
chart
page>
and
viewDataLink=<view
data
page>.
For
example:
<%
String
includePg
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMCustomerRankQuery
&di=com.tivoli.managed.gui.report.servlets.SLMCustomerRankDisplay
&link=reportDetail.jsp
54
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
&graphLink=explodedGraph.jsp
&viewDataLink=viewChartData.jsp
Changing
the
Character
Length
of
Filters
in
Exploded
Charts
Because
of
limited
space,
when
drawing
exploded
charts
the
length
of
the
filter
names
are
limited
to
30
characters.
You
can
change
this
by
including
charLength=<number>
in
the
call
of
the
servlet
for
exploded
charts
in
ranking
reports.
For
example:
<%
String
includePg
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMCustomerRankQuery
&di=com.tivoli.managed.gui.report.servlets.SLMCustomerRankDisplay
&link=reportDetail.jsp
&graphLink=explodedGraph.jsp
&viewDataLink=viewChartData.jsp
&charLength=20"+titles;
%>
<jsp:include
page="<%=includePg%>"
flush="true"/>
Displaying
Long
Labels
in
Pie
and
Bar
Charts
When
you
display
pie
or
bar
charts
in
reports,
there
might
not
be
enough
room
for
long
resource
names
to
be
displayed
properly.
By
default,
resource
names
are
truncated
from
the
right
at
12
characters,
so
a
resource
name
such
as
thisisaverylongresourcename
is
displayed
as
thisisaveryl.
You
might
want
to
lengthen
or
shorten
the
displayed
portion
of
the
name,
or
you
might
want
to
truncate
the
name
from
the
left
instead
of
from
the
right.
To
change
the
way
long
resource
names
are
displayed
in
pie
and
bar
charts,
add
one
or
more
of
the
following
option
parameters
to
any
URL
associated
with
pie
or
bar
charts
in
SLM
Reports:
charLength=<number>
For
labels
on
the
y-axis
of
bar
charts,
this
option
truncates
the
label
at
<number>
characters.
charTrunc={left
|
right}
For
labels
on
the
y-axis
of
bar
charts,
this
option
defines
from
which
side
of
the
label
characters
are
truncated.
charLengthLegend=<number>
For
labels
in
the
legend
of
pie
and
bar
charts,
this
option
truncates
the
label
at
<number>
characters.
legendTrunc={left
|
right}
For
labels
in
the
legend
of
pie
and
bar
charts,
this
option
defines
from
which
side
of
the
label
characters
are
truncated.
For
example,
if
you
display
a
report
with
a
pie
or
bar
chart
that
includes
a
resource
name
of
AnotherVeryLongResourceName,
the
label
in
the
chart
is
displayed
as
AnotherVeryL.
Suppose
that
you
add
the
following
options
to
the
URL
and
refresh
the
Web
page:
&charLength=20&charTrunc=left
The
resulting
report
displays
the
resource
name
as
VeryLongResourceName.
Appendix
A.
Customizing
SLM
Reports
55
Specifying
these
options
in
a
URL
affects
only
the
specific
view
of
the
chart.
To
make
this
change
for
all
charts,
include
the
parameter
when
calling
the
servlet
from
the
JSP
file,
as
shown
in
the
example
in
“Changing
the
Character
Length
of
Filters
in
Exploded
Charts”
on
page
55.
Including
Navigational
Links
All
report
pages
already
include
navigational
links,
also
known
as
bread
crumbs,
at
the
top
of
the
report
page.
These
links
help
you
to
keep
track
of
where
you
are
in
the
various
levels
of
report
details,
and
you
can
use
them
to
navigate
back
to
previously
visited
report
pages.
The
following
steps
describe
generally
how
to
embed
these
navigational
links
in
your
customized
report
pages.
1.
In
the
Java
code
section,
insert
the
following
lines:
TSLAJSPDisplayUtils
utils
=
new
TSLAJSPDisplayUtils();
String
currentTitle
=
"<page
title>";
utils.setBreadCrumbPages(request,currentTitle);
//get
the
previous
titles
and
current
title
to
pass
in
servlet
String
titles
=
utils.getBreadCrumbTitles(request,currentTitle);
Note:
The
currentTitle
parameter
can
be
used
for
passing
non-English
language
titles.
The
title
can
be
specified
explicitly,
for
example:
setBreadCrumbPages(request,"This+is+my+title").
You
must
encode
the
string,
otherwise
errors
might
occur.
You
can
encode
the
string
as
shown
in
the
following
example:
<%
String
breadCrumbPage
=
"breadCrumbs.jsp
?currentTitle="+SLMDisplayUtils.encodeURLString
("This
is
my
title");
%>
2.
Pass
the
previously
specified
titles
into
the
servlet.
For
example:
<%
String
includePg
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMCustomerRankQuery
&di=com.tivoli.managed.gui.report.servlets.SLMCustomerRankDisplay
&link=reportDetail.jsp
&graphLink=explodedGraph.jsp
&viewDataLink=viewChartData.jsp"+titles;
%>
<jsp:include
page="<%=includePg%>"
flush="true"/>
3.
If
a
report
page
can
be
displayed
as
a
result
of
being
linked
from
another
report
page
(for
example,
clicking
the
rank
link
in
the
Customer
Ranking
report
page
and
displaying
the
Overall
Details
report
page),
display
the
navigational
link
by
calling
the
breadCrumbs.jsp
as
shown
in
the
following
example:
//bread
crumb
include
page
<%
String
breadCrumbPage
=
"breadCrumbs.jsp
?currentTitle="+SLMDisplayUtils.encodeURLString(currentTitle);
%>
//embed
this
line
in
the
HTML
section
<jsp:include
page="<%=breadCrumbPage%>"
flush="true"/>
56
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Adding
Charts
to
an
Overall
Details
Report
To
add
trend
charts
and
violation
charts
to
the
Overall
Details
report
do
the
following
steps:
1.
Get
the
filter
names
(such
as
resource
or
metric)
for
both
charts:
//--------
get
filter
name
for
charts
--------//
String
filterName1
=
request.getParameter(SLMServletParameters.PARAM_FILTER);
String
filterName2
=
request.getParameter(SLMServletParameters.PARAM_FILTER2);
filterName1
=
utils.getFilterNameKey(request,filterName1);
filterName2
=
utils.getFilterNameKey(request,filterName2);
2.
Add
the
following
line
to
the
HTML
body:
<%
TSLAJSPDisplayUtils
utils
=
new
TSLAJSPDisplayUtils()
%>
out.println("<br>"+utils.displayCharts(request,filterName1,filterName2,
SLMReportConstants.CHARTTYPE_TOP_FILTER_TRENDS,
SLMReportConstants.CHARTTYPE_TOP_FILTER_VIOLATIONS));
In
the
above
example,
filterName1
is
for
the
first
chart
and
filterName2
is
for
the
second
chart.
You
can
swap
the
positions
of
the
charts,
such
as
positioning
violations
before
trends.
Changing
the
Excluded
Violation
Page
By
default,
the
Excluded
Violations
page
uses
the
excludedReason.jsp
file
name.
If
you
want
to
change
this
page
name,
pass
the
excludedLink=<new
page
name>
parameter
to
the
includePg
tag.
For
example:
<%
String
includePg
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.SLMViolationsQuery
&di=com.tivoli.managed.gui.report.servlets.SLMViolationsDetailTable
&link=graph.jsp&excludedLink=newFileName.jsp&fontcolor=black
&fontsize=1&bgcolor=#EDEDEB&tablewidth=100%"+titles;
%>
<jsp:include
page="<%=includePg%>"
flush="true"/>
Changing
the
Full
Resource
Name
Page
If
a
resource
name
is
a
filter
value
of
a
report
page,
and
if
it
is
over
240
characters
in
length,
an
ellipse
symbol
(...)
is
displayed
after
the
240th
character
in
the
filter
criteria
area.
Click
this
continuation
symbol
to
display
the
full
name
of
the
resource.
For
example,
the
name
might
be
displayed
as
This
is
the
long
res...
In
the
filterValues.jsp
file,
call
the
following
line
to
get
filter
values:
Vector[]
titlesAndValues
=
utils.getFilterValues(request,"fullResourceName.jsp");
The
fullResourceName.jsp
is
the
file
that
displays
the
full
name
of
the
resource.
If
you
change
the
JSP
File
name,
you
must
pass
in
the
new
name
in
place
of
fullResourceName.jsp.
For
example:
Vector[]
titlesAndValues
=
utils.getFilterValues(request,"newName.jsp");
Appendix
A.
Customizing
SLM
Reports
57
Adding
a
Link
Name
When
the
Overall
Details
report
has
three
or
more
tables
of
results,
a
link
is
added
at
the
beginning
of
each
result
table.
For
example,
in
the
Overall
Details
report,
the
SLO
Results
table
is
displayed
at
the
end
of
the
report.
When
you
view
the
next
page
in
the
report,
the
page
is
reloaded,
directing
the
display
to
the
SLO
Results
table
section
instead
of
to
the
beginning
of
the
Web
page.
To
add
this
link
feature,
do
the
following
steps:
1.
Add
the
following
HTML
tag:
<a
name="<%=SLMReportConstants.RSLT_LINK_NAME%>">
2.
To
pass
the
link
name
anywhere
else,
specify
&lnkNm=<link
name>,
where
<link
name>
is
one
of
the
link
name
constants
listed
in
Table
14.
For
example,
in
the
code
for
passing
the
maximum
rows
to
display
parameter,
this
link
name
is
specified
using
the
constant,
rsltLnk:
<!--
-----------
max
rows
to
display
--------
-->
<TABLE
width=100%
border=0
cellspacing=2
cellpadding=0>
<td
align=right
valign=top>
<jsp:include
page="maximumRowsToDisplay.jsp
?page=completeReportDetail.jsp&row=rsltrow&lnkNm=rsltLnk"
flush="true"/>
</table>
Link
name
constants
for
report
pages
are
shown
in
Table
14:
Table
14.
Link
name
constants
for
report
pages
Report
table
Link
name
Business
schedule
BusSchedLnk
Intermediate
SLO
Results
IntmedLnk
SLA
included
in
the
tiered
SLA
CpntSLALnk
SLA
information
SLAInfoLnk
SLO
Results
RsltLnk
Tiered
SLA
TieredSLALnk
Trends
TrndLnk
Violations
VioLnk
Customizing
Web
Links
for
High
Level
Reports
Several
of
the
Web
links
that
are
associated
with
high
level
reports
can
be
customized
to
your
preferences
by
modifying
the
JSP
Files
for
these
report
pages.
Depending
on
the
user
type
that
is
associated
with
your
user
name,
when
you
sign
on
to
SLM
Reports,
by
default
you
are
directed
to
one
of
two
high
level
reports:
v
Users
with
the
executive
user
type
are
shown
the
Customer
Status
by
Realms
report.
v
Users
with
the
customer
or
operations
user
type
are
shown
the
SLA
Status
by
Customers
report.
Click
the
Web
links
within
the
red,
yellow,
and
green
cells
in
each
of
these
high
level
reports
to
a
different
Web
page
showing
a
more
detailed
view
of
the
results
for
that
cell.
These
Web
links
are
required
in
the
JSP
Files,
and
although
you
can
58
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
modify
the
JSP
Files
to
point
to
other
Web
pages,
you
cannot
remove
them
from
the
JSP
File.
If
these
links
are
removed,
you
receive
an
error
message
(DYKRP0010E).
The
JSP
Files
are
located
in
<WAS_Dir>/installedApps/<hostname>/SLMReport.ear/SLMReport.war,
where
<WAS_Dir>
is
the
location
where
WebSphere
Application
Server
was
installed
(for
example,
C:\Program
Files\WebSphere\Appserver),
and
<hostname>
is
the
hostname
of
the
machine,
for
example,
machine01,
on
which
SLM
Reports
was
installed.
Locate
the
following
JSP
Files
for
editing:
v
report.jsp
v
realmCustomerStatusReport.jsp
v
custSLAStatusReport.jsp
You
can
edit
these
files
in
your
preferred
text
editor.
Changing
the
Required
Web
Link
To
modify
the
required
Web
link
in
a
high
level
report
to
point
to
a
different
page,
complete
the
following
steps:
1.
Open
a
JSP
File,
for
example,
report.jsp,
in
your
preferred
text
editor.
2.
The
link
is
specified
by
the
variable
&link.
This
variable
must
not
be
deleted
from
the
JSP
File,
or
you
receive
an
error
message.
The
code
where
the
link
is
specified
looks
similar
to
the
following
example
from
the
report.jsp
file:
<%
}else
if(userType==SLMReportConstants.USER_TYPE_EXECUTIVE){
includePage
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.TSLARealmCustomerStatusQuery
&di=com.tivoli.managed.gui.report.servlets.TSLARealmCustomerStatusDisplay
&link=reportDetail.jsp&link2=custSLAStatusReport.jsp
¤tTitle="+SLMDisplayUtils.encodeURLString(titleKey);
%>
<jsp:include
page="<%=includePage%>"
flush="true"/>
In
the
above
example,
&link=reportDetail.jsp
points
to
the
detail
report
page
that
is
displayed
when
you
click
the
Web
link
in
the
high
level
report.
Search
the
JSP
file
for
the
text
string,
&link=.
3.
Modify
the
file
name
referenced
by
the
&link
variable.
For
example,
to
point
to
a
different
file
named
newReportDetail.jsp,
modify
the
text
to
the
following
example:
&link=newReportDetail.jsp&link2=custSLAStatusReport.jsp
4.
Save
the
JSP
file.
You
can
find
the
&link=
variable
in
the
other
two
JSP
files,
similar
to
the
following
example
code:
//make
include
page
strings
String
includePg
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.TSLARealmCustomerStatusQuery
&di=com.tivoli.managed.gui.report.servlets.TSLARealmCustomerStatusDisplay
&link=reportDetail.jsp&link2=report.jsp"+titles;
%>
Appendix
A.
Customizing
SLM
Reports
59
Changing
Optional
Web
Links
By
default,
each
customer
name
in
the
Customer
Status
by
Realms
high
level
report
is
also
a
Web
link
to
the
SLA
Status
by
Customers
report,
which
shows
details
of
each
SLA
for
that
customer
name.
Change
this
link
to
point
to
a
different
page,
or
optionally
delete
this
link
from
the
JSP
file.
The
link
is
represented
in
the
JSP
file
by
the
&link2
variable.
See
the
sample
JSP
file
code
in
the
examples
in
“Changing
the
Required
Web
Link”
on
page
59
to
see
how
this
link
is
coded.
Modify
the
JSP
file
to
change
the
link
to
another
file
name.
Removing
the
Optional
Web
Link
If
you
do
not
want
each
customer
name
in
the
Customer
Status
by
Realms
report
to
link
to
another
page,
delete
the
&link2=
variable
and
its
associated
value.
For
example,
after
removing
this
link
from
report.jsp,
the
resulting
code
is
similar
to
the
following
example:
<%
}else
if(userType==SLMReportConstants.USER_TYPE_EXECUTIVE){
includePage
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.TSLARealmCustomerStatusQuery
&di=com.tivoli.managed.gui.report.servlets.TSLARealmCustomerStatusDisplay
&link=reportDetail.jsp
¤tTitle="+SLMDisplayUtils.encodeURLString(titleKey);
%>
<jsp:include
page="<%=includePage%>"
flush="true"/>
Adding
the
Optional
Web
Link
By
default,
each
SLA
name
in
the
SLA
Status
by
Customers
report
is
not
configured
as
a
Web
link,
but
you
can
modify
the
JSP
file
code
to
configure
each
SLA
name
to
a
Web
link
by
adding
the
&link2=
variable
and
specifying
a
JSP
file
name.
For
example,
to
link
SLA
names
in
the
SLA
Status
by
Customers
report
to
the
SLA
Ranking
report
page,
complete
the
following
steps:
1.
Open
the
high
level
JSP
file
in
a
text
editor.
2.
Locate
the
code
that
calls
the
TSLACustomerCustomerOrderStatusDisplay
servlet.
In
the
report.jsp
file,
this
code
is
similar
to
the
following
example:
String
includePage
=
"/servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.TSLACustomerCustomerOrderStatusQuery
&di=com.tivoli.managed.gui.report.servlets.TSLACustomerCustomerOrderStatusDisplay
&link=completeReportDetail.jsp";
3.
To
this
code,
add
the
following
code:
&link2=slaRanking.jsp.
The
resulting
modified
line
of
code
then
looks
similar
to
the
following
example:
&link=completeReportDetail.jsp&link2=slaRanking.jsp";
4.
Save
the
file.
Modifying
the
View
Intermediate
SLO
Chart
Link
When
you
are
viewing
graphs
and
graph
data
to
see
the
details
of
evaluation
results
in
reports,
if
there
are
intermediate
evaluation
results
and
your
user
name
is
associated
with
either
the
executive
or
operations
user
type,
a
Web
link,
View
Intermediate
SLO
Chart,
is
displayed.
Click
this
link
to
display
the
Intermediate
SLO
Chart
to
view
the
details
of
these
intermediate
results.
You
can
change
the
text
for
this
Web
link
by
modifying
the
graph.jsp
file:
60
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
1.
Open
the
graph.jsp
file
in
your
preferred
text
editor.
2.
Locate
the
code
similar
to
the
following
example:
<%--
-----
display
intermediate
chart
link
if
applicable
-----------
--%>
<%
if(userType!=SLMReportConstants.USER_TYPE_CUSTOMER
&&
!displayIntermediate){
String
intChartLnk
=
"servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.TSLAIntermediateCheckQuery
&di=com.tivoli.managed.gui.report.servlets.TSLAIntermediateChartLinkDisplay"
+prevTitles;
%>
<jsp:include
page="<%=intChartLnk%>"
flush="true"/>
<%}
%>
3.
Insert
the
following
code
just
before
+prevTitles;:
&licl="+SLMDisplayUtils.encodeURLString("<new
text>")
In
the
above
text
string,
<new
text>
is
the
replacement
text
for
the
Web
link.
For
example,
to
change
the
text
for
the
Web
link
to
Daily
Chart,
the
modified
code
would
be
similar
to
the
following
sample:
<%--
-----
display
intermediate
chart
link
if
applicable
-----------
--%>
<%
if(userType!=SLMReportConstants.USER_TYPE_CUSTOMER
&&
!displayIntermediate){
String
intChartLnk
=
"servlet/com.tivoli.managed.gui.report.servlets.SLMReport
?qi=com.tivoli.managed.gui.report.servlets.TSLAIntermediateCheckQuery
&di=com.tivoli.managed.gui.report.servlets.TSLAIntermediateChartLinkDisplay"
&licl="+SLMDisplayUtils.encodeURLString("Daily
Chart")+prevTitles;
%>
<jsp:include
page="<%=intChartLnk%>"
flush="true"/>
<%}
%>
4.
Save
the
file.
Appendix
A.
Customizing
SLM
Reports
61
62
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Appendix
B.
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
63
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.
64
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Trademarks
IBM,
the
IBM
logo,
Lotus,
Rational,
Tivoli,
the
Tivoli
logo,
WebSphere,
DB2,
DB2
Universal
Database,
eServer,
iSeries,
Passport
Advantage,
pSeries,
and
Redbooks
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States,
other
countries,
or
both.
Microsoft,
Windows,
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
B.
Notices
65
66
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
Index
Aactual
values,
reports
27
adjudication
22
associated
component
order
21
associated
parent
order
21
authenticating
users
38
Bbar
chart,
displaying
long
labels
55
bread
crumbs
56
CCanceled
trend
icon
24
changing
optional
web
link
60
changing
the
required
web
link
59
character
length
in
chart
55
chartdisplaying
long
labels
55
exploded
view
13
exploded,
pointing
to
54
exploded,character
length
of
filters
55
maximum
rows
to
display
13
view
data
54
viewing
data
11
comma
separated
value
(CSV)
30
configure
status
association,
adding
link
52
CSV
file,
exporting
data
to
30
customer
report
1
customer
user
type
6
customer
view,
report
28
Ddata
exporting
to
CSV
files
30
datespecifying
start
and
end
18
Ee-mail
accessing
reports
from
link
53
end
date,
specifying
18
evaluationhourly
8
intermediate
4,
13
excluded
violationchanging
page
57
Excluded
violation
icon
22
executive
summary
1
executive
user
type
6
executive
view,
report
21
exploded
chart
54
export
to
Excel
20
export
to
MS
Excel
42
export
to
20
exporting
to
CSV
files
30
external
SLA
1,
19
Ffull
resource
name,
changing
page
57
Ggraph
1
resizing
51
graph
view,
linking
to
in
reports
27
graph,
customizing
for
reports
49
graph,
displaying
28
Hhigh
level
statusconfiguring
thresholds
4
high
level
status
reports
2
hourly
evaluation
8
HTML
v
Iimminent
violation
25
intermediateicon
4
intermediate
SLO
chart,
modifying
link
60
intermediate
SLO
resulttiered
SLA
27
intermediate
SLO
results
13
internal
SLA
1,
19
internal
use
only
14
Jjava
bean,
authenticating
user
39
java
server
page
32
Java
Server
Pages
v
JSPlinking
with
web
page
37
JSP
files
v
Llabels,
displaying
in
charts
55
linkaccessing
reports
from
53
configure
status
association,
adding
52
web
page
and
JSP
37
link
name,
adding
58
link,
changing
optional
60
link,
changing
required
59
link,
modifying
view
intermediate
SLO
chart
60
logo,
customizing
in
reports
41
MMaximum
rows
to
display
19
Nnavigational
link
56
navigational
links
21
Ooperations
report
1
operations
user
type
6
orderassociated
component
21
associated
parent
21
status,
high
level
report
2
outsourced
SLA
1,
19
Ppie
chart,
displaying
long
labels
55
portal
page
1,
2,
9
tips
20,
42
printable
version
20,
42
Rranked
listing,
reports
1
ranking
13
filtering
criteria
16
selecting
16
ranking
algorithm
14
ranking
categories
15
refresh
20
reportactual
value
column
27
adding
link
name
58
cell
colors,
defined
3
customer
view
28
definitions
20
details,
viewing
21
executive
view
21
graph
view,
link
to
27
graph,
displaying
28
high
level
1,
2
high
level
views,
described
6
high
level,
evaluation
results
8
high
level,customizing
links
58
legend
4
operations
view
28
overall
13
overall
details,
adding
charts
57
service
level
objective
26
SLO
26
©
Copyright
IBM
Corp.
2002,
2004
67
report
(continued)specifying
start
and
end
times
18
tiered
SLA
27
time
period,
selecting
17
trend
23
violation
22
report
definition
41
report
servlet,
embedding
in
web
page
35
reportsaccessing
1
sign
on
2
web-based
1
resource
namefull,
changing
page
57
rolling
period
1
rolling,
defined
17
Sscmd
report
addUser,
changeUser
9
report
listUser,
changeUser
13
searchcustomer,
realm,
resource,
SLA
19
service
level
agreement
1
tiered
27
Show
excluded
violations
22
sign
off
20
SLA
1
SLA
type
1
SLA
type,
selecting
18
SLA,
tiered
27
SLM
reports
1
SLM
Reportscolumn
names
48
company
logo,
including
41
controlling
page
format
31
creating
with
third-party
software
51
customizing
graphs
49
customizing
tables
37
embedding
report
servlet
35
filter
parameters
44
including
selection
fields
45
jsp
files
32
logging
out
43
maximum
rows
to
display
46
refreshing
the
display
43
replacing
back
and
next
buttons
51
user
authentication,
customizing
38
SLM
Reports,
customizing
31
start
date,
specifying
18
Tthird
party
software,
creating
reports
51
thresholdconfigure,
for
high
level
status
4
tiered
SLA
27
time
period,
selecting
for
reports
17
top
trends,controlling
54
top
violations,controlling
54
trenddetails,
viewing
9
number
of
top,controlling
54
trend
report
23
Uuser
authenticating
38
authentication,
java
bean
39
user
name
assigned
to
portal
page
9
user
type
6
VView
Data
link
11
view
trend
details
9
view
violation
details
9
viewing
additional
rows
13
violationdetails,
viewing
9
excluded,
changing
page
57
imminent
25
number
of
top,controlling
54
report
22
WWeb
links
20
WebSphere
v
68
IBM
Tivoli
Service
Level
Advisor:
SLM
Reports
����
Printed
in
USA
SC32-1248-00