Integration Guide for IBM Tivoli Netcool/OMNIbus, IBM Tivoli ...
IBM Tivoli Monitoring for Web Infrastructure - IBM - United States
178
IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide Version 5.1.2 SC32-1435-00
Transcript of IBM Tivoli Monitoring for Web Infrastructure - IBM - United States
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide
Version
5.1.2
SC32-1435-00
���
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide
Version
5.1.2
SC32-1435-00
���
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
Appendix
D,
“Notices,”
on
page
151.
First
Edition
(October
2003)
This
edition
applies
to
Version
5.1.2
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,
Version
5.1.0
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server,
Version
5.1.0
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server,
Version
5.1.0
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server,
Version
5.1.0
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server,
and
Version
5.1.0
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server,
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
2003.
All
rights
reserved.
US
Government
Users
Restricted
Rights
–
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
Figures
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Tables
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
About
this
guide
.
.
.
.
.
.
.
.
.
.
. ix
Who
should
read
this
guide
.
.
.
.
.
.
.
.
. ix
What
this
guide
contains
.
.
.
.
.
.
.
.
.
. ix
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. x
IBM
Tivoli
Monitoring
for
Web
Infrastructure
library
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. x
Related
publications
.
.
.
.
.
.
.
.
.
. xii
Accessing
publications
online
.
.
.
.
.
.
. xiii
Ordering
publications
.
.
.
.
.
.
.
.
.
. xiii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. xiv
Contacting
software
support
.
.
.
.
.
.
.
. xiv
Conventions
used
in
this
guide
.
.
.
.
.
.
. xiv
Typeface
conventions
.
.
.
.
.
.
.
.
.
. xiv
Operating
system-dependent
variables
and
paths
xv
Tivoli
command
syntax
.
.
.
.
.
.
.
.
. xv
Chapter
1.
Overview
.
.
.
.
.
.
.
.
. 1
Choosing
an
installation
method
.
.
.
.
.
.
.
. 1
Tivoli
monitoring
environment
.
.
.
.
.
.
.
. 2
Tivoli
management
region
.
.
.
.
.
.
.
.
. 3
Components
of
a
Tivoli
monitoring
environment
. 5
Chapter
2.
Guidelines
for
installation
and
setup
.
.
.
.
.
.
.
.
.
.
.
.
. 15
Chapter
3.
Pre-installation
requirements
.
.
.
.
.
.
.
.
.
.
.
. 19
Supported
operating
systems
.
.
.
.
.
.
.
. 19
Apache
HTTP
Server
endpoints
.
.
.
.
.
. 20
Internet
Information
Server
endpoints
.
.
.
. 20
iPlanet
Web
Server
endpoints
.
.
.
.
.
.
. 20
IBM
WebSphere
Application
Server
endpoints
.
. 21
WebLogic
Server
.
.
.
.
.
.
.
.
.
.
.
. 23
Required
and
optional
software
.
.
.
.
.
.
. 23
Disk
space
requirements
.
.
.
.
.
.
.
.
.
. 28
Elements
of
a
basic
Tivoli
environment
.
.
.
.
. 29
Permissions
and
privileges
.
.
.
.
.
.
.
.
. 29
About
upgrades
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Language
requirements
.
.
.
.
.
.
.
.
.
. 30
Backing
up
and
restoring
Tivoli
databases
.
.
.
. 30
Verifying
that
the
required
software
is
running
.
. 32
Completing
installation
planning
sheets
.
.
.
.
. 34
Obtaining
the
installation
files
.
.
.
.
.
.
.
. 41
Using
installation
files
from
CDs
.
.
.
.
.
. 41
Using
installation
files
from
the
Web
.
.
.
.
. 42
Downloading
installation
files
from
the
Web
.
. 46
Chapter
4.
Performing
an
Evaluation
installation
.
.
.
.
.
.
.
.
.
.
.
.
. 51
Chapter
5.
Performing
a
Typical
installation
.
.
.
.
.
.
.
.
.
.
.
.
. 57
Installing
the
product
using
the
Typical
option
.
. 57
Creating
a
Windows
proxy
endpoint
.
.
.
.
.
. 67
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
.
.
.
.
.
.
.
.
.
.
.
. 71
Road
map
for
manual
installations
and
upgrades
.
. 71
Accessing
the
Tivoli
Management
Framework
environment
.
.
.
.
.
.
.
.
.
.
.
.
.
. 73
Installing
new
Tivoli
software
.
.
.
.
.
.
.
. 74
Upgrading,
installing
Tivoli
patches,
and
installing
fix
packs
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 78
Special
considerations
for
upgrading
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
.
.
.
.
.
.
.
.
.
. 83
Chapter
7.
Completing
the
installation
of
the
product
.
.
.
.
.
.
.
.
.
.
. 85
Verifying
the
installation
of
the
product
.
.
.
.
. 86
Installing
the
Java
Runtime
Environment
.
.
.
. 87
Linking
to
an
existing
Java
Runtime
Environment
87
Installing
files
to
enable
customization
of
resource
models
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 88
Installing
support
for
WebSphere
Application
Server
3.5.6
and
3.5.7
.
.
.
.
.
.
.
.
.
.
.
.
. 90
Installing
files
to
enable
Tivoli
Enterprise
Data
Warehouse
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 91
Installing
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Pack
Fix
Pack
.
.
.
.
. 94
Installing
IBM
Tivoli
Language
Support
for
this
product
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 96
Updating
Web
Health
Console
files
.
.
.
.
.
. 99
Chapter
8.
Expanding
your
Tivoli
environment
.
.
.
.
.
.
.
.
.
.
.
. 101
Installing
managed
nodes
through
an
existing
Tivoli
environment
.
.
.
.
.
.
.
.
.
.
. 101
Installing
endpoints
through
an
existing
Tivoli
environment
.
.
.
.
.
.
.
.
.
.
.
.
.
. 105
Changing
the
gateway
assignment
of
an
endpoint
109
Installing
the
Web
Health
Console
manually
.
.
. 110
Chapter
9.
Migrating
from
previous
versions
of
this
product
.
.
.
.
.
.
. 113
Migrating
from
Tivoli
Web
Component
Manager
to
IBM
Tivoli
Monitoring
.
.
.
.
.
.
.
.
.
. 113
Mapping
Tivoli
Web
Component
Manager
tasks
and
Apache
HTTP
Server
resource
models
.
. 113
Mapping
Tivoli
Web
Component
Manager
tasks
and
Internet
Information
Server
resource
models
114
©
Copyright
IBM
Corp.
2003
iii
Migrating
from
Tivoli
Manager
for
WebSphere
Application
Server
.
.
.
.
.
.
.
.
.
.
.
. 115
Mapping
monitors
to
resource
models
.
.
.
. 116
Mapping
Tivoli
Manager
for
WebSphere
Application
Server
tasks
.
.
.
.
.
.
.
.
. 117
Chapter
10.
Setting
up
OS/400
endpoints
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
.
.
.
.
.
.
.
.
. 119
Installing
the
endpoint
.
.
.
.
.
.
.
.
.
. 119
Starting
an
OS/400
endpoint
.
.
.
.
.
.
.
. 122
Stopping
an
OS/400
endpoint
.
.
.
.
.
.
.
. 125
Removing
an
endpoint
from
an
OS/400
system
126
Chapter
11.
Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems
. 129
Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
in
proxy
mode
z/OS
systems
.
.
.
.
.
.
.
. 129
Configuring
timeouts
for
Tivoli
gateways
.
.
.
. 132
Updating
permissions
for
proxy
mode
z/OS
systems
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 132
Installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
a
proxy
mode
z/OS
system
.
.
.
.
.
.
.
.
. 134
Configuring
Tivoli
NetView
for
z/OS
for
monitoring
.
.
.
.
.
.
.
.
.
.
.
.
.
. 134
Configuring
the
proxy
mode
z/OS
security
environment
to
accept
monitoring
operations
.
.
. 135
Installing
the
task
server
for
the
first
time
.
.
.
. 136
Configuring
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
proxy
mode
z/OS
systems
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 138
Starting
communication
between
the
task
server
and
z/OS
.
.
.
.
.
.
.
.
.
.
.
.
.
. 141
Appendix
A.
Patches
and
fix
packs
145
Appendix
B.
Icons
and
options
in
the
Step
List
window
.
.
.
.
.
.
.
.
.
. 147
Appendix
C.
Uninstalling
the
product
149
Appendix
D.
Notices
.
.
.
.
.
.
.
. 151
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 153
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 155
iv
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Figures
1.
Installation
options
window:
Evaluation/Product
Demonstration
option
.
. 53
2.
Product
selection
panel
.
.
.
.
.
.
.
. 54
3.
Prompt
for
software
CD
.
.
.
.
.
.
.
. 54
4.
Installation
options
window:
Typical
option
61
5.
Basic
tab
for
managed
nodes
.
.
.
.
.
.
. 62
6.
Advanced
tab
for
managed
nodes
.
.
.
.
. 62
7.
Component
selection
window
.
.
.
.
.
. 63
8.
Basic
tab
for
endpoints
.
.
.
.
.
.
.
. 64
9.
Advanced
tab
for
endpoints
.
.
.
.
.
.
. 64
10.
Prompt
for
software
CD
.
.
.
.
.
.
.
. 65
11.
Stop
deployment
message
.
.
.
.
.
.
.
. 68
12.
Detail
window
for
TMA
installation
step
68
13.
Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
.
.
.
.
.
. 130
©
Copyright
IBM
Corp.
2003
v
vi
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Tables
1.
Guidelines
for
installation
and
setup
.
.
.
. 15
2.
Pre-installation
requirements
and
procedures
19
3.
Valid
operating
systems
for
the
Tivoli
management
region
server
and
managed
nodes
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
4.
Supported
operating
systems
for
Apache
HTTP
Server
endpoints
.
.
.
.
.
.
.
. 20
5.
Supported
operating
systems
for
Internet
Information
Server
endpoints
.
.
.
.
.
. 20
6.
Supported
operating
systems
for
iPlanet
Web
Server
endpoints
.
.
.
.
.
.
.
.
.
.
. 20
7.
Supported
operating
systems
for
IBM
WebSphere
Application
Server
endpoints
.
.
. 21
8.
Supported
operating
systems
for
WebLogic
Server
.
.
.
.
.
.
.
.
.
.
.
.
.
. 23
9.
Required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
.
.
.
.
. 23
10.
Disk
space
requirements
for
installing
the
Tivoli
environment
.
.
.
.
.
.
.
.
.
. 28
11.
Managed
resources
and
their
purpose
.
.
.
. 34
12.
Planning
sheet
for
creating
managed
nodes
37
13.
Planning
sheet
for
creating
endpoints
.
.
.
. 38
14.
Planning
sheet
for
creating
proxy
managed
objects
.
.
.
.
.
.
.
.
.
.
.
.
.
. 40
15.
CDs
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
. 41
16.
Web
download
links
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
.
.
.
.
.
.
.
.
.
.
.
. 43
17.
Download
directories
for
a
Typical
or
Evaluation
installation
.
.
.
.
.
.
.
.
. 47
18.
Guidelines
for
a
Typical
installation
.
.
.
. 57
19.
Procedures
for
creating
Windows
endpoints
58
20.
Startup
and
configuration
options
.
.
.
.
. 69
21.
Guidelines
for
installing
the
product
from
the
Tivoli
desktop
or
command
line
.
.
.
.
.
. 71
22.
Installation
and
upgrade
procedures
for
manual
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
.
.
.
.
.
.
.
.
. 72
23.
Information
required
to
install
the
software
75
24.
Information
required
for
installing
patches
for
Tivoli
Management
Framework,
Version
4.1
.
. 79
25.
Information
required
for
installing
patches
for
Tivoli
Management
Framework,
Version
3.7.1
. 79
26.
Information
required
for
installing
fix
packs
80
27.
Information
required
for
installing
upgrade
software
.
.
.
.
.
.
.
.
.
.
.
.
. 80
28.
Guidelines
for
completing
the
installation
of
the
product
.
.
.
.
.
.
.
.
.
.
.
. 85
29.
Language
support
and
names
of
corresponding
installation
index
(.IND)
files
. 97
30.
Guidelines
for
expanding
your
Tivoli
environment
.
.
.
.
.
.
.
.
.
.
.
. 101
31.
Guidelines
for
installing
the
product
through
an
existing
Tivoli
environment
.
.
.
.
.
. 105
32.
Apache
HTTP
Server
resource
models
corresponding
to
Tivoli
Web
Component
Manager
tasks
.
.
.
.
.
.
.
.
.
.
. 114
33.
Internet
Information
Server
resource
models
corresponding
to
Tivoli
Web
Component
Manager
tasks
.
.
.
.
.
.
.
.
.
.
. 114
34.
Guidelines
for
migrating
from
previous
versions
of
the
product
.
.
.
.
.
.
.
. 115
35.
Tivoli
Manager
for
WebSphere
Application
Server
monitors
and
the
corresponding
new
resource
models
.
.
.
.
.
.
.
.
.
.
. 116
36.
Comparison
of
Tivoli
Manager
for
WebSphere
Application
Server
tasks
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks
.
.
.
. 117
37.
Guidelines
for
setting
up
OS/400
endpoints
119
38.
User
profiles
that
Tivoli
creates
on
OS/400
119
39.
Parameters
for
the
STRTMEEPT
command
123
40.
Goals
for
installation
and
configuration
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
.
.
.
.
.
.
.
.
.
.
.
. 129
41.
Required
permissions
for
proxy
mode
z/OS
directories
.
.
.
.
.
.
.
.
.
.
.
. 133
42.
Specifications
of
required
patches
that
the
installer
installs
automatically
.
.
.
.
.
. 145
43.
Specifications
of
required
patches
for
other
required
and
optional
software
.
.
.
.
.
. 146
44.
Status
icons
and
options
for
the
Step
List
window
of
the
installer
.
.
.
.
.
.
.
. 147
©
Copyright
IBM
Corp.
2003
vii
viii
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
About
this
guide
This
guide
describes
how
to
install
and
set
up
IBM®
Tivoli®
Monitoring
for
Web
Infrastructure
monitoring
and
management
software
for
business-critical
hardware
and
software.
IBM
Tivoli
Monitoring
for
Web
Infrastructure
is
composed
of
the
following
five
components:
v
Apache
HTTP
Server
v
Internet
Information
Server
v
iPlanet
Web
Server
(Sun
ONE
Web
Server)
v
IBM
WebSphere®
Application
Server
v
WebLogic
Server
Who
should
read
this
guide
Network
and
system
administrators
who
want
to
install
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
This
guide
explains
how
to
install
and
set
up
the
following
basic
elements
of
the
Tivoli
environment:
v
A
Tivoli
server
v
Managed
nodes
v
Managed
Web
Infrastructure
computers,
which
are
hosts
for
the
Tivoli
endpoint
software
Readers
should
be
familiar
with
the
following:
v
UNIX®
or
Microsoft®
Windows®
operating
systems
v
Web
server
administration
What
this
guide
contains
This
guide
contains
the
following
sections:
v
Chapter
1,
“Overview,”
on
page
1
Provides
an
overview
of
the
installation
and
setup
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
v
Chapter
2,
“Guidelines
for
installation
and
setup,”
on
page
15
Provides
guidelines
for
installing
and
setting
up
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
v
Chapter
3,
“Pre-installation
requirements,”
on
page
19
Describes
how
to
plan
and
prepare
for
installing
the
product.
v
Chapter
4,
“Performing
an
Evaluation
installation,”
on
page
51
Describes
the
Evaluation
installation
method.
v
Chapter
5,
“Performing
a
Typical
installation,”
on
page
57
Describes
the
Typical
installation
method.
v
Chapter
6,
“Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment,”
on
page
71
Describes
how
to
install
the
product
manually.
v
Chapter
7,
“Completing
the
installation
of
the
product,”
on
page
85
©
Copyright
IBM
Corp.
2003
ix
Describes
how
to
verify
and
complete
the
installation
of
the
product.
v
Chapter
8,
“Expanding
your
Tivoli
environment,”
on
page
101
Describes
how
to
add
managed
nodes,
endpoints,
or
installations
of
the
IBM
Tivoli
Monitoring
Web
Health
Console
to
your
Tivoli
environment.
v
Chapter
9,
“Migrating
from
previous
versions
of
this
product,”
on
page
113
Describes
how
to
migrate
from
previous
versions
of
Tivoli
monitoring
products.
This
chapter
also
describes
how
to
map
the
monitors
and
tasks
from
these
other
products
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
v
Chapter
10,
“Setting
up
OS/400
endpoints
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,”
on
page
119
Describes
the
OS/400®
commands
that
enable
you
to
set
up
and
manage
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
endpoints.
v
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129
Describes
the
installation
and
configuration
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
proxy
mode
OS/390®
or
z/OS™
systems.
v
Appendix
A,
“Patches
and
fix
packs,”
on
page
145
Describes
the
patches
and
fix
packs
required
for
the
installation.
v
Appendix
B,
“Icons
and
options
in
the
Step
List
window,”
on
page
147
Describes
the
icons
and
options
of
the
Step
List
window
of
the
installer.
v
Appendix
C,
“Uninstalling
the
product,”
on
page
149
Describes
how
to
uninstall
the
product.
v
Appendix
D,
“Notices,”
on
page
151
Provides
information
about
copyrights
and
trademarks.
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
library
and
any
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online
and
how
to
order
Tivoli
publications.
IBM
Tivoli
Monitoring
for
Web
Infrastructure
library
The
following
documents
are
available
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
library:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
user’s
guides
Provides
information
about
how
to
use
IBM
Tivoli
Monitoring
for
Web
Infrastructure
to
manage
IBM
Tivoli
Monitoring
for
Web
Infrastructure
resources.
There
are
four
user’s
guides
for
this
product,
one
for
each
component:
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide,
SH19-4572
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
User’s
Guide,
SH19-4573
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
User’s
Guide,
SH19-4574
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide,
SC23-4705
x
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
User’s
Guide,
GC23-4718v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide,
GC23-4720
Provides
detailed
information
about
IBM
Tivoli
Monitoring
for
Web
Infrastructure
resource
models,
tasks,
and
commands.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide,
SC32–1435–00
Provides
instructions
for
installing
Tivoli
Manager
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
and
setting
it
up
to
manage
IBM
Tivoli
Monitoring
for
Web
Infrastructure
resources.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Problem
Determination
Guide,
SC09–7783–02
Provides
instructions
for
installing
Tivoli
Manager
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
and
setting
it
up
to
manage
IBM
Tivoli
Monitoring
for
Web
Infrastructure
resources.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0,
Release
Notes,
GI11-0925
Describes
product
features
and
provides
information
about
the
latest
changes
to
the
installation
requirements
and
procedures.
The
release
notes
also
describe
known
limitations
related
to
installation
and
explain
how
to
work
around
each
limitation.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
Program
Directory
Provides
SMP/E
installation
information
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Tivoli
Enterprise
Data
Warehouse
implementation
documentation
Provides
information
about
how
to
implement
the
warehouse
enablement
packs
for
each
component
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
There
are
four
implementation
guides,
as
listed
below:
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Warehouse
Enablement
Pack
Implementation
Guide,
SC09-7786
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Warehouse
Enablement
Pack
Implementation
Guide,
SC09-7787
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Warehouse
Enablement
Pack
Implementation
Guide,
SC09-7788
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Pack
Implementation
Guide,
SC09-7783
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Warehouse
Enablement
Pack
Implementation
Guide,
SC09-7792v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Version
5.1.0:
Limitations
and
Workarounds
Supplements
Provides
the
latest
information
about
known
product
limitations
and
workarounds.
There
is
one
Limitations
and
Workarounds
document
for
each
component.
To
ensure
that
the
information
is
the
latest
available,
these
documents
are
provided
only
on
the
Web,
where
they
are
updated
on
a
regular
basis.
You
can
access
the
Limitations
and
Workarounds
documents
through
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
link
on
the
Tivoli
Information
Center
Web
site:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
About
this
guide
xi
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Workarounds
and
Limitations
Supplement,
SH19-4577
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Workarounds
and
Limitations
Supplement,
SH19-4578
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Workarounds
and
Limitations
Supplement,
SH19-4579
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Workarounds
and
Limitations
Supplement,
GI11-0928
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Workarounds
and
Limitations
Supplement,
SC09-7773
Related
publications
The
following
documents
provide
related
information:
v
IBM
Tivoli
Monitoring:
Resource
Model
Builder
User’s
Guide,
SH19-4571
Describes
how
to
use
the
IBM
Tivoli
Monitoring
Resource
Model
Builder
to
create
new
resource
models
and
to
modify
existing
ones.
v
IBM
Tivoli
Monitoring
User’s
Guide,
SH19-4569
Describes
how
to
use
the
IBM
Tivoli
Monitoring
user
interface.
v
IBM
Tivoli
Monitoring
Collection
Reference,
SH19-4570
Describes
the
resource
models
that
come
with
IBM
Tivoli
Monitoring
software.
v
Tivoli
Management
Framework
User’s
Guide
,
GC31-8433-04
Describes
the
Tivoli
environment,
including
profiles
and
profile
management.
v
Tivoli
Management
Framework
Reference
Manual,
SC31-8434-04
Provides
detailed
information
about
Tivoli
commands.
v
Tivoli
Enterprise,
Version
3.7.1:
Installation
Guide,
GC32-0395-01
Provides
information
and
procedures
for
installing
and
upgrading
Tivoli
Management
Framework
(Tivoli
management
region
server,
managed
nodes,
gateways,
and
endpoints),
and
provides
the
procedures
for
installing
and
upgrading
Tivoli
Enterprise™
products.
v
Tivoli
Management
Framework,
Version
3.7.1:
Planning
for
Deployment
Guide,
GC32-0393-01
Explains
how
to
plan
for
deploying
your
Tivoli
environment,
and
describes
Tivoli
Management
Framework
and
its
services.
v
Tivoli
Enterprise
Console
User’s
Guide,
Version
3.7.1,
GC32-0667-01
Describes
how
to
use
the
Tivoli
Enterprise
Console®
to
correlate
events
and
determine
the
severity
and
relationship
of
those
events.
v
Tivoli
Enterprise
Console,
Version
3.7:
Rule
Builder’s
Guide,
GC32-0669-00
Provides
information
about
developing
rules
for
managing
events
with
Tivoli
Enterprise
Console
with
a
text
editor
and
a
graphical
rule
builder.
v
TME
10
Software
Installation
Service
User’s
Guide,
sis36ga
Describes
how
to
use
the
Tivoli
Software
Installation
Service
(SIS)
to
install
Tivoli
products.
v
Tivoli
Business
Systems
Manager,
Version
1.5:
User’s
Guide
Describes
how
to
use
the
Tivoli
Business
Systems
Manager
product.
v
Tivoli
Business
Systems
Manager
Console,
Version
1.5:
User’s
Guide
Describes
how
to
use
the
Tivoli
Business
Systems
Manager
console.
v
Tivoli
Enterprise
Data
Warehouse
documentation
xii
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Describes
how
to
use
Tivoli
Enterprise
Data
Warehouse
to
compile
historical
data
to
monitor
your
system
and
to
help
you
make
strategic
management
decisions
regarding
your
network.
The
Tivoli
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Glossary
is
available,
in
English
only,
at
the
following
Web
site:
http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm
Accessing
publications
online
The
documentation
CD
contains
the
publications
that
are
in
the
product
library.
The
format
of
the
publications
is
PDF,
HTML,
or
both.
Refer
to
the
readme
file
on
the
CD
for
instructions
on
how
to
access
the
documentation.
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
M
to
access
all
of
the
IBM
Tivoli
Monitoring
product
manuals.
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.
The
IBM
Tivoli
Software
Support
Web
site
provides
the
latest
information
about
known
product
limitations
and
workarounds
for
your
product.
You
can
view
this
information
at
the
following
Web
site:
http://www-3.ibm.com/software/support
Ordering
publications
You
can
order
many
Tivoli
publications
online
at
the
following
Web
site:
http://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/
About
this
guide
xiii
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
most
features
of
the
graphical
user
interface.
For
additional
information,
see
the
Accessibility
Appendix
in
the
user’s
guide
for
this
product.
Contacting
software
support
Before
contacting
IBM
software
support
with
a
problem,
refer
to
the
IBM
software
support
Web
site:
http://www.ibm.com/software/support
To
access
Tivoli
support,
click
the
Tivoli
support
link
at
the
bottom
right
of
the
support
page.
If
you
want
to
contact
software
support,
see
the
IBM
Software
Support
Guide
at
the
following
Web
site:
http://techsupport.services.ibm.com/guides/handbook.html
The
guide
provides
information
about
how
to
contact
IBM
Software
Support,
depending
on
the
severity
of
your
problem,
and
the
following
information:
v
Registration
and
eligibility
v
Telephone
numbers,
depending
on
the
country
in
which
you
are
located
v
Information
you
must
have
before
contacting
IBM
Software
Support
Conventions
used
in
this
guide
This
guide
uses
several
conventions
for
special
terms
and
actions,
and
operating
system-dependent
commands
and
paths.
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
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
xiv
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
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
The
publications
in
this
library
use
the
UNIX
convention
for
specifying
environment
variables
and
for
directory
notation.
When
using
the
Windows
command
line,
replace
$variable
with
%variable%
for
environment
variables
and
replace
each
forward
slash
(/)
with
a
backslash
(\)
in
directory
paths.
The
names
of
environment
variables
are
not
always
the
same
in
Windows
and
UNIX.
For
example,
%TEMP%
in
Windows
is
equivalent
to
$tmp
in
UNIX.
Note:
If
you
are
using
the
bash
shell
on
a
Windows
system,
you
can
use
the
UNIX
conventions.
Tivoli
command
syntax
The
following
special
characters
define
Tivoli
command
syntax:
[
]
Identifies
elements
that
are
optional.
Required
elements
do
not
have
brackets
around
them.
...
Indicates
that
you
can
specify
multiple
values
for
the
previous
element.
Separate
multiple
values
by
a
space,
unless
otherwise
directed
by
command
information.
If
the
ellipsis
for
an
element
follows
a
closing
bracket,
use
the
syntax
within
the
brackets
to
specify
multiple
values.
For
example,
to
specify
two
administrators
for
the
option
[–a
admin]...,
use
–a
admin1
–a
admin2.
If
the
ellipsis
for
an
element
is
within
the
brackets,
use
the
syntax
of
the
last
element
to
specify
multiple
values.
For
example,
to
specify
two
hosts
for
the
option
[–h
host...],
use
–h
host1
host2.
|
Indicates
mutually
exclusive
information.
You
can
use
the
element
on
either
the
left
or
right
of
the
vertical
bar.
{
}
Delimits
a
set
of
mutually
exclusive
elements
when
a
command
requires
one
of
them.
Brackets
([
])
are
around
elements
that
are
optional.
In
addition
to
the
special
characters,
Tivoli
command
syntax
uses
the
typeface
conventions
described
in
“Typeface
conventions”
on
page
xiv.
The
following
examples
illustrate
the
typeface
conventions
used
in
Tivoli
command
syntax:
v
wcrtpr
[–a
admin]...
[–s
region]
[–m
resource]...
name
The
name
argument
is
the
only
required
element
for
the
wcrtpr
command.
The
brackets
around
the
options
indicate
they
are
optional.
The
ellipsis
after
the
–a
admin
resource
option
means
that
you
can
specify
multiple
administrators
multiple
times.
The
ellipsis
after
the
–m
resource
option
means
that
you
can
specify
multiple
resources
multiple
times.v
wchkdb
[–o
outfile]
[–u]
[–x]
{–f
infile
|
–i
|
object...}
About
this
guide
xv
The
–f,
–i,
and
object
elements
are
mutually
exclusive.
Braces
that
surround
elements
indicate
that
you
are
including
a
required
element.
If
you
specify
the
object
argument,
you
can
specify
more
than
one
object.
xvi
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
1.
Overview
This
guide
describes
installation
and
setup
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
monitoring
and
management
software
for
business-critical
hardware
and
software.
This
document
includes
information
on
the
following
topics:
v
Determining
the
proper
installation
for
your
environment
v
Overview
of
a
Tivoli
environment
v
Guidelines
and
worksheets
for
planning
your
installation
and
setup
v
Using
the
installation
wizard
(also
referred
to
in
this
document
as
the
installer)
to
evaluate
the
product
v
Using
the
installation
wizard
to
install
or
upgrade
the
product
in
a
production
environment
v
Using
the
Tivoli
desktop
or
command
line
to
install
or
upgrade
the
product
v
Using
the
Tivoli
desktop
or
command
line
to
expand
an
existing
Tivoli
environment
Choosing
an
installation
method
The
IBM
Tivoli
Monitoring
products
offer
several
options
for
installing
the
software,
depending
on
the
complexity
of
your
environment
and
your
knowledge
of
Tivoli
management
systems.
Your
choices
include
the
following:
Installation
wizard
The
installation
wizard
(also
referred
to
in
this
guide
as
the
installer)
installs
the
product
and
creates
a
Tivoli
environment
if
none
exists.
The
installer
also
installs
supplemental
software,
such
as
the
Java
Runtime
Environment
and
language
packs.
If
you
use
the
installer,
you
must
choose
between
a
Typical
or
Evaluation
installation
path.
Use
the
following
criteria
to
determine
which
path
you
want
to
take:
v
Use
the
Typical
installation
path
if
you
want
to
install
the
product
on
a
target
computer
that
matches
one
of
the
following
profiles:
–
Has
no
software
installed
for
the
Tivoli
Management
Framework
—OR—
–
Has
Tivoli
Management
Framework
Version
3.7.1
or
a
later
version
installed.
You
cannot
install
this
product
on
systems
that
run
previous
versions
of
the
Tivoli
Management
Framework.
The
Typical
installation
is
suitable
for
a
production
environment.
v
Use
the
Evaluation
installation
path
if
you
want
to
install
a
limited
Tivoli
environment
and
IBM
Tivoli
Monitoring
for
Web
Infrastructure
on
one
computer
so
that
you
can
test
and
evaluate
the
product.
Use
the
Evaluation
installation
path
only
if
you
have
no
Tivoli
software
installed
on
the
computer.
The
Evaluation
installation
is
not
intended
for
use
in
a
production
environment.
Tivoli
desktop
or
command
line
interface
installation
Use
one
of
these
options
(both
referred
to
in
this
guide
as
a
manual
installation)
if
either
of
the
following
conditions
is
true:
©
Copyright
IBM
Corp.
2003
1
v
You
are
an
existing
Tivoli
user
with
a
version
of
the
Tivoli
Management
Framework
earlier
than
Version
3.7.1
—OR—
v
You
have
expert
knowledge
of
the
Tivoli
environment
and
plan
to
extensively
customize
your
installation.
The
manual
installation
method
enables
you
to
create
interconnected
Tivoli
management
regions
and
to
create
environments
with
more
than
50
endpoints.
Chapter
6,
“Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment,”
on
page
71
provides
manual
installation
instructions.
For
further
information,
see
the
documentation
for
Tivoli
Management
Framework,
available
with
IBM
Tivoli
Monitoring
for
Business
Integration.
Tivoli
Software
Installation
Service
Tivoli
Software
Installation
Service
(SIS)
can
install
multiple
Tivoli
products
on
multiple
systems
in
parallel.
This
Java™-based
product
can
install
more
products
on
more
systems
in
less
time
than
the
install
facility
of
Tivoli
Management
Framework.
SIS
performs
product
prerequisite
checks
and,
if
defined,
user-specified
prerequisite
checks,
ensuring
as
few
installation
failures
as
possible.
In
most
cases,
failures
occur
only
when
machines
are
turned
off
or
removed
from
the
network.
Tivoli
Software
Installation
Service
also
creates
an
installation
repository
into
which
you
can
import
the
installation
image
of
one
or
more
Tivoli
products.
You
can
import
only
those
interpreter
types
needed
in
your
environment,
which
saves
disk
space
and
import
time.
The
installation
repository
is
then
the
source
of
all
your
Tivoli
installations.
You
can
share
a
single
installation
repository
across
multiple
Tivoli
management
regions.
This
guide
does
not
cover
Tivoli
Software
Installation
Service.
For
instructions
on
how
to
install
Tivoli
Software
Installation
Service
in
your
Tivoli
environment
and
how
to
use
it
to
install
products,
refer
to
the
Tivoli
Software
Installation
Service
User’s
Guide.
Setting
up
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
The
Tivoli
Business
Systems
Manager
task
server
enables
communication
between
Tivoli
distributed
environments
and
z/OS
environments.
For
more
information
about
working
with
z/OS
systems,
see
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129.
The
task
server
is
a
component
of
Tivoli
Business
Systems
Manager
event
enablement.
Both
terms
(″task
server″
and
″Tivoli
Business
Systems
Manager
event
enablement″)
are
used
in
this
document
to
refer
to
the
software
that
enables
communication
between
Tivoli
distributed
environments
and
z/OS
environments.
Tivoli
monitoring
environment
A
basic
monitoring
solution
begins
with
a
set
of
core
monitoring
products.
You
can
extend
the
basic
monitoring
solution
with
additional
products
to
take
full
advantage
of
the
collected
performance
and
availability
data.
The
following
products
constitute
a
full
monitoring
solution:
2
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Core
monitoring
products
v
Tivoli
Management
Framework
v
IBM
Tivoli
Monitoring
Additional
products
to
extend
monitoring
capabilities
and
collected
data
v
Tivoli
Enterprise
Console
v
IBM
Tivoli
Monitoring
Web
Health
Console
v
Tivoli
Enterprise
Data
Warehouse
v
IBM
Tivoli
Monitoring
Resource
Model
Builder
v
Tivoli
Business
Systems
Manager
The
additional
products
use
components
that
are
installed
on
the
Tivoli
server
and
gateways
to
link
with
IBM
Tivoli
Monitoring
on
the
endpoint.
The
IBM
Tivoli
Monitoring
and
Web
Health
Console
components
are
automatically
enabled
on
the
endpoints
at
the
first
profile
distribution.
Tivoli
management
region
A
Tivoli
region
contains
three
tiers
of
resources:
the
Tivoli
server,
managed
nodes
and
gateways,
and
endpoints.
In
a
Tivoli
environment,
a
managed
resource
is
a
database
object
that
represents
a
system
or
network
resource
and
is
governed
by
policies.
A
resource
is
a
hardware,
software,
or
data
entity
that
is
managed
by
Tivoli
software.
Anything
that
affects
the
operation
of
a
computer
system
is
a
resource,
for
example,
physical
and
logical
disks,
CPUs,
memory,
printers,
processes
that
are
running,
and
service
such
as
LanMan,
Windows
event
log,
UNIX
syslogd
(logging
system
daemon),
and
TCP/IP.
Chapter
1.
Overview
3
Tivoli
management
region
server
Tivoli
Management
Framework
software
provides
the
base
component
for
Tivoli
products.
The
computer
in
which
this
software
is
installed
becomes
the
Tivoli
management
region
server.
The
Tivoli
server
includes
the
libraries,
binaries,
data
files,
and
the
graphical
user
interface
(GUI)
(the
Tivoli
desktop)
that
are
required
to
install
and
manage
your
Tivoli
environment.
See
“1-
Tivoli
Management
Framework”
on
page
5
for
more
information.
Managed
nodes
A
managed
node
runs
the
same
software
that
runs
on
a
Tivoli
server.
Managed
nodes
maintain
their
own
object
databases
that
can
be
accessed
by
the
Tivoli
server.
When
managed
nodes
communicate
directly
with
other
managed
nodes,
they
perform
the
same
communication
or
security
operations
that
the
Tivoli
server
performs.
The
difference
between
a
Tivoli
server
and
a
managed
node
is
that
the
Tivoli
server
object
database
is
global
to
the
entire
region
including
all
managed
nodes.
In
contrast,
the
managed
node
database
is
local
to
the
particular
managed
node.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
uses
two
types
of
endpoints:
local
endpoints
and
proxy
endpoints.
A
local
endpoint
represents
an
IBM
WebSphere
server
resources
running
on
a
non-z/OS
platform,
such
as
Windows
or
AIX®.
A
proxy
endpoint
is
a
non-z/OS
system
that
communicates
with
an
IBM
WebSphere
server
resource
running
on
a
z/OS
system.
To
manage
IBM
WebSphere
Application
Server
resources
on
local
endpoints,
the
Tivoli
endpoint
must
be
installed
on
each
IBM
WebSphere
Application
Server
node.
For
z/OS
systems,
the
proxy
endpoint
must
be
installed
on
a
separate
system
from
z/OS.
Note:
In
the
Tivoli
environment,
the
term
node
is
used
to
refer
to
any
managed
resource
with
Tivoli
Management
Framework
installed.
In
the
WebSphere
environment,
the
term
node
is
used
to
refer
to
the
IBM
WebSphere
server
resources.
In
this
document,
unless
specifically
indicated,
the
Tivoli
environment
definition
of
node
is
used.
Gateways
A
gateway
controls
communication
and
operations
with
endpoints.
Each
gateway
can
support
thousands
of
endpoints.
A
gateway
can
launch
methods
on
an
endpoint
or
run
methods
on
behalf
of
the
endpoint.
A
gateway
is
generally
created
on
an
existing
managed
node.
This
managed
node
provides
access
to
the
endpoint
methods
and
provides
the
communication
with
the
Tivoli
server
that
the
endpoints
occasionally
require.
Endpoints
Endpoints
communicate
with
the
Tivoli
management
region
through
assigned
gateways.
An
endpoint
can
be
created
on
UNIX
or
PC
operating
systems,
including
Windows
NetWare
and
OS/2®.
An
endpoint
runs
the
IBM
Tivoli
Monitoring
engine.
See
“7-
Endpoints”
on
page
12
for
more
information
about
endpoints.
4
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Components
of
a
Tivoli
monitoring
environment
A
Tivoli
monitoring
environment
consists
of
the
following
components:
1.
Tivoli
Management
Framework
2.
Tivoli
Enterprise
Console
3.
RIM
database
4.
IBM
Tivoli
Monitoring
5.
IBM
Tivoli
Monitoring
Web
Health
Console
6.
Profile
(resource
models)
7.
Endpoints
8.
Tivoli
Enterprise
Data
Warehouse
9.
IBM
Tivoli
Monitoring
Resource
Model
Builder
10.
Tivoli
Business
Systems
Manager
The
following
sections
provide
descriptions
of
the
components
in
the
Tivoli
monitoring
environment.
1-
Tivoli
Management
Framework
(Requires
separate
installation)
Tivoli
Management
Framework
is
the
base
component
for
Tivoli
products.
Using
Tivoli
Management
Framework
and
a
combination
of
Tivoli
software,
you
can
manage
large
distributed
networks
with
multiple
operating
systems,
various
network
services,
diverse
system
operations,
and
constantly
changing
nodes
and
users.
Chapter
1.
Overview
5
The
Tivoli
Management
Framework
function
in
your
IBM
Tivoli
Monitoring
software
is
installed
in
your
Tivoli
management
region
or
on
your
Tivoli
management
region
server.
When
installed,
you
have
the
following
tools
for
managing
your
resources:
Policy
regions
The
policy
region
is
the
entry
point
into
the
management
functions
for
your
software
installations.
It
is
installed
on
your
administrator
desktop.
Task
libraries
Each
IBM
Tivoli
Monitoring
software
contains
two
or
more
task
libraries.
The
name
of
each
task
library
indicates
the
type
of
tasks
that
the
task
library
contains.
For
example,
configuration
task
libraries
contain
tasks
that
support
the
discovery
and
Tivoli
configuration
functions.
Operations
task
libraries
contains
tasks
that
support
the
daily
operations
for
managing
resources.
Profile
managers
A
profile
manager
contains
resource
model
profiles
for
monitoring
your
resources.
Profiles
A
profile
contains
the
resource
models
for
monitoring
your
resources.
See
also
9
and
“6-
Profile
(resource
models)”
on
page
11.
Resource
models
The
resource
models
provide
best
practices
monitoring
functions
for
your
resources.
Tivoli
Enterprise
Console
event
classes
and
rules
The
event
classes
and
rules
provide
a
set
of
event
definitions
for
viewing
changes
on
your
Tivoli
Enterprise
Console
console,
and
provide
a
set
of
rules
that
aggregate
and
consolidate
events
to
minimize
Tivoli
Enterprise
Console
event
traffic.
Icons
for
resources
Icons
represent
various
resources
in
your
software.
The
icons
graphically
show
the
current
state
of
a
resource.
Context
menus
from
which
you
can
easily
access
the
functions
required
to
manage
a
resource
are
available
using
the
following
icons:
v
Software
icon
on
your
administrator
desktop
v
Resource
icons,
one
icon
for
each
resource
or
object
being
managed
2-
Tivoli
Enterprise
Console
(Requires
separate
installation)
6
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Tivoli
Enterprise
Console
is
a
rules-based
event
management
application
that
collects,
processes,
and
automatically
responds
to
events.
You
can
install
Tivoli
Enterprise
Console
on
the
server
or
any
managed
node
or
gateway
within
the
Tivoli
management
region.
When
you
install
an
endpoint,
you
can
enable
the
sending
of
events
generated
by
IBM
Tivoli
Monitoring
applications
to
the
Tivoli
Enterprise
Console.
You
can
the
enable
sending
of
events
either
through
a
Tivoli
environment,
which
enables
you
to
take
advantage
of
multiple
Tivoli
Enterprise
Console
servers,
or
directly
to
a
specific
Tivoli
Enterprise
Console
server.
Tivoli
Enterprise
Console
event
classes
and
rules
provide
a
set
of
event
definitions
for
viewing
changes
on
your
Tivoli
Enterprise
Console
console,
and
provide
a
set
of
rules
that
aggregate
and
consolidate
events
to
minimize
Tivoli
Enterprise
Console
event
traffic.
Chapter
1.
Overview
7
3-
RIM
database
You
can
configure
an
endpoint
to
send
events
generated
by
IBM
Tivoli
Monitoring
applications
to
Tivoli
Enterprise
Console.
Events
sent
from
the
endpoints
are
stored
in
a
RIM
database.
An
RDBMS
Interface
Module
(RIM)
database
is
used
to
store
data
from
resource
monitoring.
You
can
have
multiple
RIMs
in
your
environment.
Various
applications
use
the
data
stored
in
RIMs
to
produce
reports
about
your
monitored
environment.
You
create
a
RIM
database
with
an
RDBMS
server
installation.
The
RIM
database
can
be
part
of
the
Tivoli
Management
Framework
or
not.
System
configurations
do
not
require
the
RDBMS
to
reside
on
the
same
system
as
the
Tivoli
management
region
server
or
managed
node.
The
RDBMS
client
on
those
systems
must
connect
to
the
remote
RDBMS.
8
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
4-
IBM
Tivoli
Monitoring
IBM
Tivoli
Monitoring
is
an
application
that
applies
preconfigured
best
practices
to
the
automated
monitoring
of
essential
system
resources.
The
application
detects
bottlenecks
and
other
potential
problems
and
provides
for
automatic
recovery
from
critical
situations.
IBM
Tivoli
Monitoring
performs
the
following
tasks:
v
Monitors
operating
system
status
v
Sends
notification
of
system
or
performance
problems
and
takes
automated,
corrective
actions
v
Collects
and
stores
system
data
A
Common
Information
Model
(CIM)
interface
provides
all
data
to
the
IBM
Tivoli
Monitoring
engine.
In
a
Windows
environment,
Windows
Management
Instrumentation
(WMI
–
an
implementation
of
CIM
by
Microsoft)
provides
the
data.
In
a
UNIX
environment,
Touchpoint
(an
implementation
of
CIM
by
IBM
Tivoli)
provides
the
data.
IBM
Tivoli
Monitoring
is
installed
on
the
Tivoli
management
region
server.
This
application
provides
three
important
monitoring
elements:
Profile
The
profile
is
a
collected
set
of
information
corresponding
to
a
Tivoli
application
resource.
For
example,
the
profile
contains
resource
models
that
define
monitoring
configurations
that
monitor
specific
criteria
in
your
environment.
See
also
“6-
Profile
(resource
models)”
on
page
11.
Heartbeat
A
heartbeat
function
regularly
monitors
endpoints
to
verify
that
they
are
Chapter
1.
Overview
9
available
and
running
correctly.
This
function
provides
notification
if
the
engine
on
an
endpoint
fails.
The
heartbeat
function
is
enabled
on
the
gateway
of
the
monitored
endpoints.
The
heartbeat
monitoring
function
sends
events
to
Tivoli
Enterprise
Console
and
Tivoli
Business
Systems
Manager
(provided
that
the
Tivoli
Business
Systems
Manager
Adapter
component
is
installed
at
the
gateway)
and
sends
notices
to
the
IBM
Tivoli
Monitoring
notice
group.
Data
collector
The
data
collector
is
a
component
that
uploads
data
from
the
endpoints
to
the
RIM
database
for
data
collection.
This
RIM
database
can
be
the
same
database
that
is
used
for
Tivoli
Enterprise
Console
or
a
separate
database.
5-
IBM
Tivoli
Monitoring
Web
Health
Console
IBM
Tivoli
Monitoring
Web
Health
Console,
a
part
of
IBM
Tivoli
Monitoring,
is
a
Web-based
graphical
interface
that
runs
on
any
system
that
can
be
connected
through
a
TCP/IP
interface
to
the
Tivoli
management
region.
The
IBM
Tivoli
Monitoring
Web
Health
Console
enables
you
to
view
the
health
of
resources
on
an
endpoint
and
view
real-time
or
historical
monitored
data.
A
numeric
value
between
100
(perfect
health)
and
zero
(corresponding
event
conditions
met)
represents
the
health
of
each
resource.
You
can
access
and
use
the
IBM
Tivoli
Monitoring
Web
Health
Console
from
any
Netscape
6.2
(or
later)
and
Internet
Explorer
6.x
browser
on
any
machine.
You
can
connect
the
IBM
Tivoli
Monitoring
Web
Health
Console
to
any
Tivoli
management
region
server
or
managed
node
and
configure
it
to
monitor
any
or
all
of
the
endpoints
that
are
found
in
that
region
(assuming
that
all
of
the
gateways
are
interconnected).
To
connect
to
the
IBM
Tivoli
Monitoring
Web
Health
Console
you
need
access
to
the
server
on
which
the
IBM
Tivoli
Monitoring
Web
Health
Console
server
is
installed
and
the
IBM
Tivoli
managed
region
on
which
you
want
to
10
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
monitor
health.
All
user
management
and
security
is
handled
through
the
IBM
Tivoli
management
environment.
This
includes
creating
users
and
passwords
as
well
as
assigning
authority.
6-
Profile
(resource
models)
The
profile
is
a
collected
set
of
information
corresponding
to
a
Tivoli
application
resource.
For
example,
the
profile
contains
resource
models
that
define
monitoring
configurations
that
monitor
specific
criteria
in
your
environment.
IBM
Tivoli
Monitoring
enables
you
to
deploy
preconfigured
best
practices
resource
models
as
well
as
standard
and
customized
resource
models
to
automate
the
monitoring
of
essential
resources.
A
resource
model
accesses
specific
performance
and
operational
data
from
the
system
at
runtime.
(For
example,
the
Process
resource
model
gathers
data
about
processes
running
on
the
system.)
The
resource
models
process
the
data
they
collect
using
an
algorithm
that
determines
whether
or
not
the
system
is
performing
according
to
expectations.
This
enables
you
to
detect
bottlenecks
and
other
potential
problems
and
define
automatic
recovery
from
critical
situations
affecting
your
resources.
This
ability
frees
system
administrators
from
manually
scanning
extensive
performance
and
operational
data.
Chapter
1.
Overview
11
7-
Endpoints
An
endpoint
provides
the
primary
interface
for
system
management.
An
endpoint
is
any
computer
that
runs
the
lcfd
service
(or
daemon),
which
is
configured
using
the
lcfd
command.
Typically,
an
endpoint
is
installed
on
a
computer
system
that
is
not
used
for
daily
management
operations.
Endpoints
run
a
very
small
amount
of
software
and
do
not
maintain
an
object
database.
The
majority
of
computers
in
a
Tivoli
environment
should
be
endpoints.
The
Tivoli
desktop
is
not
installed
with
the
endpoint
software.
If
you
choose
to
run
a
desktop
on
an
endpoint,
you
must
install
Tivoli
Desktop
for
Windows
or
telnet
to
a
UNIX
managed
node.
8-
Tivoli
Enterprise
Data
Warehouse
(Requires
separate
installation)
12
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Tivoli
Enterprise
Data
Warehouse
provides
a
data
warehouse
with
which
you
can
view
historical
reports
and
graphs,
enabling
you
to
analyze
historical
patterns
and
trends
of
your
environment.
The
software
maintains
historical
data
for
resources
that
the
IBM
Tivoli
Monitoring
for
Business
Integration
resource
models
capture.
The
warehouse
enablement
pack
for
each
IBM
Tivoli
Monitoring
for
Business
Integration
component
provides
prepackaged
reports
to
analyze
this
historical
data.
You
can
also
create
reports
to
meet
your
specific
needs.
Tivoli
Enterprise
Data
Warehouse
is
installed
on
the
Tivoli
management
region
server.
The
Tivoli
Enterprise
Data
Warehouse
Support
Component
(required
for
interaction
with
IBM
Tivoli
Monitoring)
is
installed
on
the
Tivoli
management
region
server,
and,
optionally,
on
one
or
more
managed
nodes.
You
must
install
the
component
on
the
server
before
you
install
it
on
the
managed
nodes.
After
installing
the
component
on
the
server,
you
can
optionally
install
the
component
on
one
or
more
managed
nodes
as
well.
This
component
collects
the
monitored
data
and
stores
it
in
a
RIM
database.
9-
IBM
Tivoli
Monitoring
Resource
Model
Builder
(Requires
separate
installation)
IBM
Tivoli
Monitoring
Resource
Model
Builder
is
an
application
that
enables
you
to
develop,
debug,
and
package
resource
models
for
IBM
Tivoli
Monitoring.
IBM
Tivoli
Monitoring
Resource
Model
Builder
is
independent
of
the
Tivoli
Management
Framework
environment.
You
can
install
it
on
a
machine
that
is
not
within
the
Tivoli
Management
Framework.
IBM
Tivoli
Monitoring
Resource
Model
Builder
is
a
Windows-only
tool.
Although
it
does
not
run
on
UNIX
systems,
you
can
create
resource
models
for
UNIX
systems.
Chapter
1.
Overview
13
10-
Tivoli
Business
Systems
Manager
(Requires
separate
installation)
Tivoli
Business
Systems
Manager
provides
a
graphical
interface
to
determine
the
health
of
an
information
technology
(IT)
infrastructure.
The
software
enables
you
to
discover
and
create
a
set
of
topology
views
for
your
resources.
Use
Tivoli
Business
Systems
Manager
to
examine
how
individual
components
or
resources
affect
a
business
function.
You
can
monitor
and
manage
these
resources
from
an
Tivoli
Business
Systems
Manager
console.
Tivoli
Business
Systems
Manager
can
be
installed
on
a
stand-alone
computer
that
can
be
part
of
the
Tivoli
management
environment
or
not.
You
must
install
an
Tivoli
Business
Systems
Manager
adapter
on
all
gateways
in
a
region
to
be
able
to
receive
IBM
Tivoli
Monitoring
events.
14
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
2.
Guidelines
for
installation
and
setup
Table
1
summarizes
the
procedures
for
installing
and
setting
up
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
It
also
tells
you
where
you
can
find
the
information
and
procedures
that
guide
you
through
the
installation.
Table
1.
Guidelines
for
installation
and
setup
What
you
do
Refer
to
Before
installation
1.
Check
the
system
for
compliance
with
the
system
requirements,
complete
the
planning
sheets,
and
set
up
or
check
the
prerequisite
software.
Chapter
3,
“Pre-installation
requirements,”
on
page
19
2.
Back
up
an
existing
Tivoli
environment,
if
you
have
one.
If
you
encounter
a
problem
during
an
installation,
use
the
backup
copy
to
restore
the
databases
to
a
known
working
state.
“Backing
up
and
restoring
Tivoli
databases”
on
page
30
3.
Complete
the
planning
sheets
for
the
managed
nodes
and
endpoints
you
want
to
install.
(Optional)
“Completing
installation
planning
sheets”
on
page
34
4.
Obtain
the
installation
files.
“Obtaining
the
installation
files”
on
page
41
5.
If
you
have
Solaris
Operating
Environment
(referred
to
as
Solaris),
you
must
install
the
latest
patches
on
the
target
system
before
you
install
the
product.
Patches
are
available
from
the
following
Sun
Web
site:
http://sunsolve.sun.com..
6.
If
you
have
AIX
Version
4.3.x,
install
the
IBM
AIX
maintenance
package
9
to
enable
required
Java
runtime
features.
Obtain
the
maintenance
package
at
http://techsupport.services.ibm.com/rs6k/mlfixes.html
7.
Use
the
ping
command
to
test
network
names
of
the
target
computers
for
the
installation;
this
ensures
that
the
network
recognizes
the
names.
The
target
computer
replies
to
the
ping
command
with
its
IP
address
and
statistics
regarding
the
transaction
if
the
name
is
valid,
the
network
connection
is
active,
and
the
target
computer
is
running.
Run
the
following
command
to
contact
target
computer:
ping
name
where
name
is
the
name
of
the
target
computer.
8.
Confirm
that
the
required
software
services
are
running
on
the
target
computers.
“Verifying
that
the
required
software
is
running”
on
page
32
Installation
©
Copyright
IBM
Corp.
2003
15
Table
1.
Guidelines
for
installation
and
setup
(continued)
What
you
do
Refer
to
9.
Install
the
product.
The
installation
might
include
the
following:
v
Managed
nodes
v
Endpoints
v
The
IBM
Tivoli
Monitoring
Web
Health
Console
Note:
You
can
create
these
components
before
or
after
installation.
You
can
also
use
the
Web
Health
Console’s
installation
executable
to
install
it
on
any
computer
in
your
Tivoli
environment.
Chapter
4,
“Performing
an
Evaluation
installation,”
on
page
51
—OR—Chapter
5,
“Performing
a
Typical
installation,”
on
page
57
—OR—
Chapter
6,
“Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment,”
on
page
71
and
Chapter
8,
“Expanding
your
Tivoli
environment,”
on
page
101.
—OR—
Use
Tivoli
Software
Installation
Service
(SIS)
to
install
product
components.
After
installation
10.
Back
up
the
Tivoli
environment.
If
you
encounter
a
problem
during
final
configuration,
use
the
backup
copy
to
restore
the
environment
to
a
known
state.
“Backing
up
and
restoring
Tivoli
databases”
on
page
30
11.
Create
managed
nodes
and
endpoints
if
you
did
not
create
them
during
installation.
Tivoli
Enterprise
Installation
Guide,
which
comes
with
the
Tivoli
Management
Framework
software
12.
Verify
the
functionality
of
the
Tivoli
management
region
by
running
communication
commands.
“Verifying
the
installation
of
the
product”
on
page
86
13.
(Optional)
Migrate
or
map
older
versions
of
Tivoli
management
and
monitoring
software
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Chapter
9,
“Migrating
from
previous
versions
of
this
product,”
on
page
113
14.
Install
software
to
enable
resource
models,
the
Web
Health
Console,
historical
reporting,
and
national
language
versions
of
the
product.
Chapter
7,
“Completing
the
installation
of
the
product,”
on
page
85
15.
If
you
want
to
monitor
IBM
WebSphere
Application
Server
on
OS/400
systems,
install
and
configure
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
OS/400.
Chapter
10,
“Setting
up
OS/400
endpoints
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,”
on
page
119
16.
If
you
want
to
monitor
IBM
WebSphere
Application
Server
on
z/OS
systems,
install
and
configure
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS.
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129
16
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
1.
Guidelines
for
installation
and
setup
(continued)
What
you
do
Refer
to
17.
Create
server
objects
for
the
product
to
manage.
See
the
user’s
guide
for
the
component
you
are
installing:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
User’s
Guide
Chapter
2.
Guidelines
for
installation
and
setup
17
18
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
3.
Pre-installation
requirements
This
chapter
provides
the
following
pre-installation
requirements
and
procedures
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Table
2.
Pre-installation
requirements
and
procedures
Goal
Refer
to
Review
installation
requirements
so
that
you
can
ensure
your
environment
is
prepared
for
installation.
v
“Supported
operating
systems”
v
“Required
and
optional
software”
on
page
23
v
“Disk
space
requirements”
on
page
28
v
“Elements
of
a
basic
Tivoli
environment”
on
page
29
v
“Permissions
and
privileges”
on
page
29
v
“About
upgrades”
on
page
30
v
“Language
requirements”
on
page
30
Prepare
your
environment.
v
“Backing
up
and
restoring
Tivoli
databases”
on
page
30
v
“Verifying
that
the
required
software
is
running”
on
page
32
v
“Completing
installation
planning
sheets”
on
page
34
Obtain
the
files
you
need
for
installation.
v
“Obtaining
the
installation
files”
on
page
41
Supported
operating
systems
This
section
lists
the
operating
systems
that
work
with
the
Tivoli
management
region
server,
managed
nodes,
and
endpoints
in
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
The
following
table
lists
the
supported
operating
systems
for
the
Tivoli
management
region
server
and
managed
nodes.
Table
3.
Valid
operating
systems
for
the
Tivoli
management
region
server
and
managed
nodes
Operating
System
Version
AIX
4.3.3,
5.1,
5.2*,
and
5L*
HP-UX
11.0
and
11i
Sun
Solaris
Operating
Environment
(referred
to
in
this
document
as
Solaris)
2.8
and
2.9*
Windows
NT®
Service
Pack
6a
Windows
2000
Server,
Advanced
Server,
Professional,
all
with
Service
Pack
2
Red
Hat
Linux
7.2
Server,
Advanced
Server
2.1,
7.2
on
zSeries*
SuSE
Linux
Enterprise
Server
7
for
IA32
(7.2
base),
7
for
zSeries
(7.2
base)*
©
Copyright
IBM
Corp.
2003
19
Table
3.
Valid
operating
systems
for
the
Tivoli
management
region
server
and
managed
nodes
(continued)
Operating
System
Version
Note:
AIX
5.2,
AIX
5L,
Solaris
2.9,
Red
Hat
Linux,
and
SuSE
Linux
operating
systems
are
supported
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
only.
The
following
endpoints
are
supported.
Apache
HTTP
Server
endpoints
Apache
HTTP
Server,
Versions
1.3.22,
1.3.26,
and
1.3.27
are
supported
as
endpoints
on
the
following
operating
systems:
Table
4.
Supported
operating
systems
for
Apache
HTTP
Server
endpoints
Operating
system
Version
AIX
4.3.3,
5.1,
and
5.2
Red
Hat
Linux
Red
Hat
for
Intel
7.1
or
7.2,
and
Red
Hat
Enterprise
Linux
2.1
SuSE
Linux
SuSE
for
Enterprise
Server
7
for
IA32
(7.2
base)
United
Linux
United
Linux
1
for
IA32
(7.2
base)
Solaris
2.7,
2.8,
and
9
Windows
NT
4.0,
Service
Pack
6A
Windows
2000
Server,
Advanced
Server,
Professional
with
Service
Pack
2,
and
Data
Center
Windows
2003
Data
Center
Internet
Information
Server
endpoints
Internet
Information
Server,
Version
4.0,
5.0,
is
supported
as
an
endpoint
on
the
following
operating
systems:
Table
5.
Supported
operating
systems
for
Internet
Information
Server
endpoints
Operating
system
Version
Windows
NT
Server
4.0,
Service
Pack
6A
Windows
2000
Server,
Advanced
Server,
Professional
with
Service
Pack
2,
Advanced
Server
with
Service
Pack
3,
and
Data
Center
Windows
2003
Data
Center
iPlanet
Web
Server
endpoints
iPlanet
Web
Server,
Version
6.0
with
patches
SP2
and
SP3
is
supported
as
an
endpoint
on
the
following
operating
systems:
Table
6.
Supported
operating
systems
for
iPlanet
Web
Server
endpoints
Operating
system
Version
Solaris
2.7
and
2.8
Windows
NT
Service
Pack
6A
20
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
6.
Supported
operating
systems
for
iPlanet
Web
Server
endpoints
(continued)
Operating
system
Version
Windows
2000
Server,
Advanced
Server,
Professional
with
Service
Pack
2,
Advanced
Server
with
Service
Pack
3,
and
Data
Center
Windows
2003
Standard
and
Enterprise
Server
IBM
WebSphere
Application
Server
endpoints
IBM
Tivoli
Monitoring
for
Web
Infrastructure
supports
the
following
versions
of
IBM
WebSphere
Application
Server
as
endpoints
on
the
operating
systems
listed
in
Table
7,
with
the
exceptions
noted
in
the
table,
and
with
the
exception
of
z/OS,
Zos.e,
and
OS/390
operating
systems:
v
Versions
3.5.6
and
3.5.7
of
IBM
WebSphere
Application
Server
Advanced
Edition.
(The
table
collectively
refers
to
these
versions
as
IBM
WebSphere
Application
Server
3.5.x.)
v
Versions
4.0.2,
4.0.3,
4.0.4,
4.0.5,
4.0.6,
and
4.0.7
of
IBM
WebSphere
Application
Server
Advanced
Edition.
(The
table
collectively
refers
to
these
versions
as
IBM
WebSphere
Application
Server
4.
This
does
not
include
Versions
4.0
or
4.0.1
of
Advanced
Edition.)
v
Versions
5.0,
5.0.1,
and
5.0.2
of
IBM
WebSphere
Application
Server
Base
Edition,
Network
Deployment,
Express
Edition,
embedded
Express,
and
Enterprise
Edition.
(The
table
collectively
refers
to
these
versions
as
IBM
WebSphere
Application
Server
5.)
IBM
WebSphere
Application
Server
for
z/OS
and
OS/390,
Version
4.0.1,
supports
z/OS,
Zos.e,
and
OS/390
endpoints.
Table
7.
Supported
operating
systems
for
IBM
WebSphere
Application
Server
endpoints
Operating
system
Version
AIX
4.3.3,
5.1,
and
5.2
5L
(IBM
WebSphere
Application
Server
42
only)
HP-UX
11.0
11i
(IBM
WebSphere
Application
Server
3.5.x1
and
4
only)
Red
Hat
Linux
Red
Hat
for
Intel
7.1
and
7.2
Server
(IBM
WebSphere
Application
Server
3.5.x
and
4
only)
Advanced
Server
2.1
Red
Hat
for
Intel
7.3
(IBM
WebSphere
Application
Server
4
only)
Red
Hat
for
zSeries
7.2
(IBM
WebSphere
Application
Server
53
only)
Chapter
3.
Pre-installation
requirements
21
Table
7.
Supported
operating
systems
for
IBM
WebSphere
Application
Server
endpoints
(continued)
Operating
system
Version
SuSE
Linux
SuSE
for
Intel
7.1
(IBM
WebSphere
Application
Server
4
only)
SuSE
for
Intel
7.2
(IBM
WebSphere
Application
Server
3.5.x
and
4
only)
SuSE
for
Intel
7.3
(IBM
WebSphere
Application
Server
4
and
5
only)
SuSE
for
Enterprise
Server
7
for
IA32
(7.2
base)
(IBM
WebSphere
Application
Server
4
and
5
only)
SuSE
for
Enterprise
Server
7
for
zSeries
(7.2
base)
(IBM
WebSphere
Application
Server
5
only)
OS/400
Version
5,
Release
1
or
2
Solaris
4.x
2.7
(IBM
WebSphere
Application
Server
4
only)
2.8
(IBM
WebSphere
Application
Server
4
and
5
only)
Windows
NT
Version
4.0,
Service
Pack
6a
Windows
2000
Server,
Advanced
Server
with
Service
Pack
2
or
Service
Pack
3
OS/390
Version
2,
Release
10
z/OS
Version
1,
Release
1
or
higher
Zos.e
Version
1,
Release
3
or
4
Notes:
1.
Support
for
OS/390
and
z/OS
endpoints
are
provided
through
the
use
of
proxy
endpoints.
The
proxy
endpoints
can
run
on
AIX,
Windows,
or
Solaris
operating
systems
at
the
levels
listed
in
Table
7
on
page
21.
2.
IBM
WebSphere
Application
Server
Single
Server
3.5
or
4.0
is
not
supported.
3.
You
cannot
use
one
system
both
as
an
endpoint
and
a
z/OS
proxy
endpoint.
For
additional
information
about
z/OS
proxy
endpoints,
see
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129.
4.
The
Alternate
Configuration
Option
of
IBM
WebSphere
Application
Server
is
not
supported.
5.
Except
for
OS/400
and
z/OS
proxy
endpoints,
multiple
separate
IBM
WebSphere
Application
Server
versions
are
supported
on
a
single
endpoint.
For
example,
IBM
Tivoli
Monitoring
for
Web
Infrastructure
can
manage
IBM
WebSphere
Application
Server
Versions
4.0.4
and
5.0
on
the
same
endpoint.
6.
For
OS/400
and
z/OS
proxy
endpoints,
multiple
configurations
of
the
same
version
of
IBM
WebSphere
Application
Server
are
supported.
For
example,
IBM
Tivoli
Monitoring
for
Web
Infrastructure
can
manage
more
than
one
instance
of
IBM
WebSphere
Application
Server
Version
5
on
the
same
OS/400
endpoint.
22
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
WebLogic
Server
WebLogic
Server,
Version
6.1
with
patch
SP3
and
Version
7.0
with
patch
SP1,
is
supported
as
an
endpoint
on
the
following
operating
systems:
Table
8.
Supported
operating
systems
for
WebLogic
Server
Operating
system
Version
AIX
4.3.3
and
5.1
HP-UX
11.0
and
11i
Red
Hat
Linux
Red
Hat
for
Intel
7.1
and
7.2
SuSE
Linux
SuSE
for
Intel
7.1
and
7.2
Solaris
2.7
and
2.8
Windows
NT
4.0,
Service
Pack
6a
Windows
2000
Advanced,
Professional,
Advanced
Server
with
Service
Pack
2
Required
and
optional
software
This
section
lists
the
required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Table
9.
Required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Product
Release
Required
base
Tivoli
software
This
section
of
the
table
lists
the
base
Tivoli
software
required
for
all
installations.
All
software
listed
in
this
section
is
installed
by
the
installer.
Tivoli
Management
Framework
The
installer
detects
an
existing
installation
of
Tivoli
Management
Framework,
Version
3.7.1,
and
performs
the
following
actions:
v
If
you
are
performing
an
Evaluation
installation,
the
installer
automatically
upgrades
Tivoli
Management
Framework
to
Version
4.1
with
the
required
patches.
v
If
you
are
performing
a
Typical
installation,
you
have
the
following
choices:
–
You
can
remain
at
Version
3.7.1.
If
necessary,
the
installer
deploys
the
required
patches
for
Version
3.7.1.
–
You
can
upgrade
to
Version
4.1
with
the
required
patches.
Appendix
A,
“Patches
and
fix
packs,”
on
page
145
lists
the
patches
that
the
installer
deploys.
3.7.1,
4.1
IBM
Tivoli
Monitoring
The
installer
detects
an
existing
installation
of
IBM
Tivoli
Monitoring,
Version
4.1.x
or
Version
5.1.0,
and
upgrades
it
to
the
required
Version
5.1.1
with
Fix
Pack
5.
5.1.1
with
Fix
Pack
5
(5.1.1-ITM-FP05)
IBM
Tivoli
Monitoring
Component
Services
The
installer
detects
an
existing
version
of
IBM
Tivoli
Monitoring
Component
Services
and
automatically
upgrades
it
to
the
required
Version
5.1.1.
5.1.1
Chapter
3.
Pre-installation
requirements
23
Table
9.
Required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Product
Release
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Component
Software
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
is
required
to
manage
IBM
WebSphere
Application
Server
endpoints.
The
installer
detects
an
existing
prior
version
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
and
upgrades
it
to
the
current
version.
5.1.2
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
is
required
to
manage
Apache
HTTP
Server
endpoints.
5.1.0
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
is
required
to
manage
Internet
Information
Server
endpoints.
5.1.0
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
is
required
to
manage
iPlanet
Web
Server
endpoints.
5.1.0
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
is
required
to
manage
IBM
WebLogic
Server
endpoints.
5.1.0
Products
monitored
by
IBM
Tivoli
Monitoring
for
Web
Infrastructure
See
“Supported
operating
systems”
on
page
19
for
a
full
list
of
supported
operating
systems
for
these
products.
IBM
WebSphere
Application
Server
Advanced
Edition
3.5.6,
3.5.7,
4.0.2,
4.0.3,
4.0.4,
4.0.5,
4.0.6,
4.0.7
IBM
WebSphere
Application
Server
Base
Edition
5.0,
5.0.1,
5.0.2
IBM
WebSphere
Server
Network
Deployment
5.0,
5.0.1,
5.0.2
IBM
WebSphere
Application
Server
Enterprise
Edition
5.0,
5.0.1,
5.0.2
IBM
WebSphere
Application
Server,
embedded
version
of
the
IBM
WebSphere
Server
–
Express
5.0,
5.0.1,
5.0.2
IBM
WebSphere
Application
Server
Express
Edition
5.0,
5.0.1,
5.0.2
IBM
WebSphere
Application
Server
for
z/OS
and
OS/390
4.0.1
Apache
HTTP
Server
1.3.22,
1.3.26,
1.3.27
IBM
HTTP
Server
(for
Apache
HTTP
Server)
1.3.19,
1.3.27
Internet
Information
Server
4.0,
5.0
iPlanet
Web
Server
6.0
with
patches
SP2
and
SP3
WebLogic
Server
6.0
with
patch
SP3,
Version
7.0
with
patch
SP1
Additional
required
software
IBM
SDK
for
OS/390,
Java
2
Technical
Edition
1.3.1,
Service
Release
15
To
enable
endpoints
for
all
components:
Java
Runtime
Environment
(JRE),
Version
1.3.
1.3.0
or
1.3.1
Solaris
endpoints
must
have
Version
1.3.1_08
To
enable
monitoring
of
Windows
endpoints:
Microsoft
Windows
Management
Instrumentation
(WMI).
This
software
comes
with
Windows
2000.
You
must
install
it
manually
on
Windows
NT
endpoints.
5.1
Search
for
″wmi″
on
the
following
Web
site
for
more
information:
http://msdn.microsoft.com
24
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
9.
Required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Product
Release
To
enable
data
logging
on
Windows
NT
and
Windows
2000
endpoints:
ODBC
driver
for
Microsoft
Access
2000.
The
Microsoft
Data
Access
Components
2.1
software
on
the
Microsoft
Web
site
also
offers
this
driver.
To
enable
communication
with
z/OS
systems:
Tivoli
Business
Systems
Manager
Event
Enablement
The
following
patch
is
required:
15-BSM-0038
Different
patches
are
required
if
you
install
Tivoli
Business
Systems
Manager
Event
Enablement
on
the
IBM
Tivoli
Enterprise
Console
to
support
the
forwarding
of
events
to
Tivoli
Business
Systems
Manager.
See
the
Optional
software
section
of
this
table
for
more
information.
1.5
Tivoli
Business
Systems
Manager
Event
Enablement
is
included
on
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
component
CD.
To
enable
communication
with
z/OS
systems:
Tivoli
NetView
for
OS/390
or
Tivoli
NetView
for
z/OS
If
you
use
Tivoli
NetView
for
OS/390,
Version
1.3,
you
must
apply
the
fixes
for
the
following
APARs:
v
OW54528
v
OW52785
v
OW46984
If
you
use
Tivoli
NetView
for
OS/390,
Version
1.4,
you
must
apply
the
fix
for
APAR
OW50595.
If
you
use
Tivoli
NetView
for
OS/390,
Version
1.3
or
1.4,
you
must
apply
the
fix
for
the
OA02015
APAR.
If
you
use
Tivoli
NetView
for
z/OS
5.1.0,
you
must
apply
the
fix
for
the
OA02073
APAR.
If
you
are
monitoring
IBM
WebSphere
Application
Server
in
a
sysplex
and
you
will
target
monitoring
command
systems
other
than
the
one
that
issued
the
NETCONV,
you
must
apply
one
of
the
following
APAR
fixes:
v
For
Tivoli
NetView
for
OS/390,
Version
1.3
or
1.4:
OA02799
v
For
Tivoli
NetView
for
z/OS
5.1.0:
OA02748
Tivoli
NetView
for
OS/390:
1.3
or
higher
Tivoli
NetView
for
z/OS:
5.1.0
Chapter
3.
Pre-installation
requirements
25
Table
9.
Required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Product
Release
For
IBM
WebSphere
Application
Server:
For
IBM
WebSphere
Application
Server,
Version
3.5.6:
fix
PQ63262
For
IBM
WebSphere
Application
Server,
Version
4.0.2:
fixes
PQ56667
and
PQ63116
Note:
If
you
have
an
HP-UX
system,
you
must
also
apply
fix
PQ65896.
Note:
If
you
have
security
enabled,
you
must
also
apply
fixes
PQ63116,
PQ56667,
PQ65264,
PQ65264.
For
IBM
WebSphere
Application
Server,
Version
4.0.3:
fix
PQ63116
Note:
If
you
have
security
enabled,
you
must
also
apply
fixes
PQ63116,
PQ65264,
PQ65264.
For
HP-UX
systems
running
IBM
WebSphere
Application
Server
4.0.2,
4.0.3,
or
4.0.4,
fix
PQ65264
Note:
If
you
also
have
security
enabled
for
IBM
WebSphere
Application
Server,
Version
4.0.4,
you
must
also
apply
fix
PQ65264.
For
IBM
WebSphere
Application
Server
for
z/OS,
fix
PQ69950
See
the
IBM
Support
and
downloads
Web
site
at
www.ibm.com/support
Before
applying
any
version
upgrade
or
fix,
you
must
shut
down
the
Tivoli
Enterprise
Console
event
adapter
and
the
IBM
Tivoli
Monitoring
engine
on
the
endpoint.
See
the
note
below
for
information
on
stopping
these
functions.
For
SSL
authentication
on
z/OS
proxy
endpoints:
Java
Runtime
Environment
(JRE)
1.3.1,
SR15
For
Windows
endpoints:
Microsoft
Windows
Script
Host
5.6
See
the
Microsoft
Web
site
for
more
information:http://msdn.microsoft.com
Optional
software
IBM
Tivoli
Monitoring
Web
Health
Console
The
installer
optionally
installs
IBM
Tivoli
Monitoring
Web
Health
Console.
5.1.1
Tivoli
Enterprise
Data
Warehouse
The
following
fix
packs
and
efixes
are
required:
v
Fix
Pack
1.1-TDW-FP02
v
efix
1.1-TDW-0011LA
v
efix
1.1-TDW-0013LA
For
DBCS
systems,
an
additional
fix
pack
is
required.
See
the
IBM
Support
and
downloads
Web
site
at
www.ibm.com/support
for
additional
information.
1.1
Database
support
for
the
Tivoli
Enterprise
Data
Warehouse:
IBM
DB2
Universal
Database
Enterprise
Edition
The
following
fix
pack
and
efix
are
required
for
DB2,
Version
7.2:
v
IBM
DB2
Universal
Database
Enterprise
Edition,
Version
7.2,
Fix
Pack
8
v
efix
1.1-TDW-0002
7.2
26
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
9.
Required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Product
Release
IBM
Tivoli
Monitoring
Warehouse
Enablement
Pack
support
This
software
is
required
to
enable
Tivoli
Enterprise
Data
Warehouse
Install
Patch
5.1.1-ITM-FP05
in
both
your
IBM
Tivoli
Monitoring
application
and
Tivoli
Enterprise
Data
Warehouse
system.
If
you
are
using
the
installer,
this
patch
is
automatically
installed
with
IBM
Tivoli
Monitoring.
5.1.1
IBM
Tivoli
Enterprise
Console
3.7.1,
3.8,
3.9
Adapter
configuration
facility
This
is
required
to
use
event
adapters
with
IBM
Tivoli
Enterprise
Console.
The
adapter
configuration
facility
is
supplied
with
the
supported
IBM
Tivoli
Enterprise
Console
releases
Tivoli
Business
Systems
Manager
v
Version
1.5
requires
TBSM
Patch
35
v
Version
2.1.1
requires
Fix
Pack
2.1.1-BSM-0001
1.5,
2.1.1
Tivoli
Business
Systems
Manager
Event
Enablement
If
you
use
Tivoli
Business
Systems
Manager
in
your
Tivoli
environment,
you
can
install
Tivoli
Business
Systems
Manager
Event
Enablement
on
the
IBM
Tivoli
Enterprise
Console
to
enable
forwarding
of
events
from
the
IBM
Tivoli
Enterprise
Console
to
Tivoli
Business
Systems
Manager.
When
used
for
this
purpose,
Tivoli
Business
Systems
Manager
Event
Enablement
requires
the
following
patches:
v
Version
1.5
requires
Patch
1.5-BSM-0043
v
Version
2.1.1
requires
Fix
Pack
2.1.1-BSM-0004
IBM
Tivoli
Monitoring
for
Web
Infrastructure
requires
Tivoli
Business
Systems
Manager
Event
Enablement
for
a
different
purpose:
to
enable
communication
with
z/OS
systems.
(See
the
Additional
required
software
section
of
this
table.)
When
used
for
this
purpose,
a
different
patch
is
required.
1.5,
2.1.1
Tivoli
Software
Installation
Service
3.6.1,
3.7
Tivoli
Software
Distribution
Tivoli
Software
Distribution
is
part
of
the
IBM
Tivoli
Configuration
Manager,
Version
4.2
product.
Formerly,
Tivoli
Software
Distribution
was
a
separate
product.
Tivoli
Software
Distribution
4.0,
4.1
IBM
Tivoli
Configuration
Manager
4.2
Notes:
1.
On
HP-UX
systems,
whenever
operations
require
the
Java
runtime
environment,
Version
1.3,
HP-UX
Version
11.x
must
be
running
on
target
computers.
This
runtime
environment
is
not
available
for
previous
versions
of
HP-UX.
The
following
operations
on
HP-UX
require
the
Java
run-time
environment:
v
Installation
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
through
the
installer
v
Running
Tivoli
endpoint
software
on
HP-UX
endpoints
Chapter
3.
Pre-installation
requirements
27
You
can
use
versions
of
the
HP-UX
operating
system
prior
to
Version
11.x
for
Tivoli
managed
nodes
because
the
Java
runtime
environment
is
not
required
on
managed
nodes.
Also,
you
can
use
versions
of
the
HP-UX
system
prior
to
Version
11.x
if
you
use
the
Tivoli
desktop
or
command
line
interface
to
install
on
an
HP-UX
computer.
The
Java
runtime
environment
is
not
required
when
you
use
the
installation
options
in
the
Tivoli
desktop
or
command
line
interface.
Check
the
system
prerequisites
for
other
software
transactions
that
require
the
Java
runtime
environment.
For
example,
the
Java
run-time
environment
must
be
running
on
endpoints
to
enable
resource
models.
2.
Before
applying
an
upgrade
or
fix
to
IBM
WebSphere
Application
Server,
perform
the
following
steps
to
stop
the
Tivoli
Enterprise
Console
event
adapter
and
the
IBM
Tivoli
Monitoring
engine:
a.
Stop
the
monitoring
engine
on
the
endpoint
by
running
the
following
command
from
the
Tivoli
management
region
server:
wdmcmd
-stop
-e
<endpoint_name>
where
<endpoint_name>
is
the
name
of
the
endpoint.
b.
Run
the
Stop_WebSphere_TEC_Adapter
task
against
the
endpoint
to
stop
the
event
adapter.
c.
Apply
the
IBM
WebSphere
Application
Server
version
upgrade
or
fix.
d.
Run
the
Start_WebSphere_TEC_Adapter
task
to
restart
the
event
adapter.
e.
Restart
the
IBM
Tivoli
Monitoring
engine
by
running
the
following
command
from
the
Tivoli
management
region
server:
wdmcmd
-restart
-e
<endpoint_name>
where
<endpoint_name>
is
the
name
of
the
endpoint.
Disk
space
requirements
This
section
lists
the
disk
space
requirements
for
the
elements
in
the
Tivoli
environment.
Table
10.
Disk
space
requirements
for
installing
the
Tivoli
environment
Element
Disk
space
requirements
Tivoli
management
region
server
v
Tivoli
Management
Framework
and
IBM
Tivoli
Monitoring:
500
MB
v
The
installation
depot
(temporary
directory):
2.6
GB
Note:
On
Windows,
the
depot
directory
must
reside
on
the
target
computer.
You
cannot
use
a
depot
directory
that
is
located
on
a
remote
system.
On
UNIX,
provide
a
directory
path
that
is
accessible
from
the
installation
computer
to
the
installation
depot.
v
Files
that
the
installer
places
in
the
temporary
($TEMP
or
%TEMP%)
directories
that
are
defined
for
your
operating
system:
3
MB
Additional
Information:
Obtain
the
name
of
this
directory
by
accessing
the
Tivoli
command
line
environment
(as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73)
and
entering
this
command:
wtemp.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Apache
HTTP
Server
:
5
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Internet
Information
Server:
4
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
iPlanet
Web
Server:
5
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
50
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
WebLogic
Server:
12
MB
28
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
10.
Disk
space
requirements
for
installing
the
Tivoli
environment
(continued)
Element
Disk
space
requirements
Managed
node
v
Tivoli
Management
Framework
and
IBM
Tivoli
Monitoring:
500
MB
(Includes
the
space
required
by
the
gateway
software
that
enables
the
managed
node
to
communicate
with
an
endpoint.)
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Apache
HTTP
Server
:
5
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Internet
Information
Server:
4
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
iPlanet
Web
Server:
5
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
12
MB
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
WebLogic
Server:
12
MB
Endpoint
v
The
endpoint
daemon
for
Tivoli
Management
Framework:
2
MB
v
Java
runtime
environment,
Version
1.3:
space
requirement
varies
v
Required
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server:
.5MB
v
Required
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server:
.5
MB
v
Required
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server:
.5
MB
v
Required
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
8
MB
v
Required
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server:
12
MB
v
Windows
Management
Instrumentation
(WMI):
refer
to
Microsoft
specifications
For
z/OS
endpoints,
you
must
have
an
adequate
MAXASSIZE.
See
the
MVS
Initialization
and
Tuning
Reference
for
details.
Elements
of
a
basic
Tivoli
environment
The
following
list
describes
the
elements
of
a
basic
Tivoli
environment.
The
installation
wizard
can
create
the
Tivoli
environment
during
a
Typical
or
Evaluation
installation.
v
Mandatory:
One
Tivoli
management
region
server
to
monitor
endpoints
v
One
managed
node
v
Endpoints.
The
Typical
installation
is
designed
to
create
up
to
50
endpoints.
v
One
Web
Health
Console
on
a
managed
node
or
endpoint.
After
installation,
you
can
create
an
endless
number
of
Web
Health
Consoles
on
an
unlimited
number
of
computers.
Permissions
and
privileges
You
must
have
the
following
to
install
the
product:
v
The
license
key
for
Tivoli
Management
Framework.
Obtain
this
key
in
the
printed
document
that
comes
with
the
installation
CDs
for
the
Tivoli
Management
Framework.
v
On
UNIX,
the
user
who
installs
the
product
must
have
root
privileges.
On
Windows,
the
user
must
have
membership
in
the
Administrator
group.
Tivoli
recommends
that
you
log
on
as
root
on
UNIX
and
Administrator
on
Windows.
v
A
valid
host
name
for
all
managed
nodes
and
endpoints
you
create.
Specify
the
unique
domain
name
for
the
host
name
when
multiple
computers
in
the
system
have
the
same
host
name.
For
example,
the
fully
qualified
name
of
the
tokyo
computer
might
be
tokyo.sales.mycompany.com,
where
sales
is
the
domain
name
of
the
Sales
Department’s
domain
at
the
company
mycompany.
The
full
name
distinguishes
the
Sales
Department’s
server
from
a
tokyo
server
in
the
marketing
domain
called
tokyo.marketing.mycompany.com.
Chapter
3.
Pre-installation
requirements
29
About
upgrades
This
guide
provides
the
following
information
about
upgrades,
depending
on
the
type
of
installation
you
are
performing:
v
If
you
are
performing
an
Evaluation
installation,
the
installer
detects
existing
installations
of
required
software,
and
upgrades
it
to
the
required
versions.
However,
it
is
best
if
you
perform
an
Evaluation
installation
on
a
computer
that
has
no
Tivoli
software
installed.
See
Chapter
4,
“Performing
an
Evaluation
installation,”
on
page
51
for
a
list
of
software
that
is
installed
during
an
Evaluation
installation.
v
If
you
are
performing
a
Typical
installation,
the
installer
gives
you
some
options
about
whether
or
not
to
upgrade
existing
software
to
the
current
version.
See
Chapter
5,
“Performing
a
Typical
installation,”
on
page
57
for
a
description
of
the
options.
v
If
you
are
installing
the
product
from
the
Tivoli
desktop
or
command
line
in
an
existing
Tivoli
environment,
you
can
perform
any
required
upgrades
as
described
in
Chapter
6,
“Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment,”
on
page
71.
Chapter
9,
“Migrating
from
previous
versions
of
this
product,”
on
page
113
describes
how
to
migrate
from
previous
versions
of
Tivoli
monitoring
products.
The
chapter
also
describes
how
to
map
Tivoli
monitors
from
previous
versions
of
monitoring
products
to
resource
models.
Language
requirements
For
a
non-English
Tivoli
environment,
you
must
install
the
kbdus.dll
file
before
installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
You
can
obtain
this
file
from
Microsoft
or
on
the
product
CDs
for
Windows
NT
or
Windows
2000
in
all
language
versions
of
these
operating
systems.
The
kbdus.dll
file
must
reside
in
the
%SystemRoot%\system32
directory.
You
can
enable
other
languages
during
installation.
You
can
also
enable
other
languages
after
you
complete
the
installation.
See
“Installing
IBM
Tivoli
Language
Support
for
this
product”
on
page
96
for
procedures
regarding
installing
the
product
in
these
national
languages:
Brazilian
Portuguese,
Chinese
(simplified),
Chinese
(traditional),
French,
German,
Italian,
Japanese,
Korean,
and
Spanish.
Backing
up
and
restoring
Tivoli
databases
Objective
To
back
up
existing
Tivoli
object
databases
for
all
computers
in
the
Tivoli
management
region
so
you
can
use
these
backup
copies
to
restore
them
to
a
known
working
state
if
you
encounter
a
problem
during
installation.
Background
information
Note:
This
procedure
describes
a
routine
backup
method
that
you
can
use
frequently.
In
addition
to
this
backup,
arrange
a
complete
backup
of
the
Tivoli
environment
whenever
you
make
significant
changes
to
the
system,
such
as
the
installation
of
this
product.
If
you
encounter
a
problem
during
a
change
operation,
you
can
use
the
system
backup
to
restore
the
entire
Tivoli
environment
to
a
known
working
state.
30
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
This
procedure
provides
a
stable
and
complete
snapshot
of
the
Tivoli
database
and
related
files
and
a
safer
alternative
to
manually
compressing
the
database
files
in
a
.tar
or
.zip
format.
For
example,
when
you
save
a
database
to
a
.tar
or
.zip
file,
an
error
might
occur
if
the
Tivoli
object
dispatcher
is
simultaneously
writing
to
the
Tivoli
database.
This
procedure
also
enables
you
to
estimate
the
size
of
the
backup
files
to
ensure
that
you
have
sufficient
disk
space
in
the
target
directory
to
complete
the
operation.
You
back
up
or
restore
databases
using
the
wbkupdb
command.
In
a
large
Tivoli
management
region,
the
wbkupdb
process
can
take
a
long
time
because
backups
of
the
managed
node
databases
are
performed
serially.
Concurrent
backup
processes
are
not
allowed
in
the
same
Tivoli
management
region.
You
must
complete
one
wbkupdb
command
before
you
execute
a
second
instance
of
the
command.
The
backup
file
is
saved
to
the
default
location,
which
is
the
\backups
directory
in
the
Tivoli
database
directory.
The
\backups
directory
is
created
if
it
does
not
exist.
Tivoli
Management
Framework
must
be
running
on
the
Tivoli
management
region
server
and
on
the
managed
node
whose
database
is
being
restored.
Otherwise
the
wbkupdb
command
cannot
restore
any
database
(managed
node
or
Tivoli
management
region
server).
See
the
Tivoli
Management
Framework
Reference
Manual
for
a
description
of
all
the
capabilities
of
the
wbkupdb
command.
Required
authorization
role
backup
or
super
Note:
The
default
directory
to
which
backup
files
are
written
has
root
write
permissions
only.
If
you
cannot
log
in
as
the
root
administrator,
you
must
change
the
location
of
the
backup
file
to
a
directory
for
which
you
have
write
access.
Before
you
begin
You
must
have
a
valid
user
login
name
and
a
group
name
for
the
computer
on
which
the
backup
file
is
stored.
On
UNIX,
set
umask
to
022
for
root.
When
you
finish
None
Procedure
You
can
perform
backups
from
the
command
line
interface
(CLI)
or
in
the
Tivoli
desktop.
You
can
perform
restore
operations
from
the
command
line
interface
only.
Command
line:
Use
the
wbkupdb
command.
wbkupdb
[–d
device]
[–r]
[node_name
...]
where:
–d
device
Specifies
the
file
or
device
to
which
the
backup
file
is
saved
or
from
which
the
backup
file
is
retrieved.
If
you
specify
a
file
name
with
this
option,
you
Chapter
3.
Pre-installation
requirements
31
can
insert
a
file
date
and
time
anywhere
in
the
file
name
by
adding
the
variable
%t.
The
variable
is
replaced
with
a
date/time
stamp
in
the
form
Mondd-hhmm.
For
example,
if
you
specify
–d
/usr/backups/TMR1%t.bk,
the
resulting
file
is
named
TMR1Dec21-0955.bk.
The
time
is
displayed
in
24-hour
mode.
–r
Restores
the
databases
for
the
specified
nodes.
node_name
Specifies
the
node
to
be
backed
up
or
restored.
You
can
specify
multiple
nodes.
See
the
description
of
the
wbkupdb
command
in
the
Tivoli
Management
Framework
Reference
Manual
for
more
options.
Examples:
The
following
example
backs
up
the
Tivoli
databases
for
all
managed
nodes
in
the
Tivoli
management
region
from
which
the
wbkupdb
command
is
run.
The
backups
are
written
to
the
user-defined
file
/usr/backups/TMR1.bk.
wbkupdb
-d
/usr/backups/TMR1.bk
The
following
example
backs
up
the
database
of
a
single
managed
node,
sherman.
In
this
example,
the
backup
file
is
saved
to
the
default
location.
wbkupdb
sherman
The
following
example
restores
a
single
managed
node,
sherman.
The
-r
flag
restores
the
backed
up
database
on
sherman.
The
-d
flag
identifies
/usr/backups/TMR1.bk
as
the
backup
file
to
restore.
wbkupdb
-r
-d
/usr/backups/TMR1.bk
sherman
Tivoli
desktop:
1.
Select
Backup
from
the
Desktop
menu
to
display
the
Backup
Tivoli
Management
Region
window.
2.
Select
one
or
more
managed
nodes
from
the
Available
managed
nodes
scrolling
list.
3.
Click
the
left-arrow
option
to
move
them
to
the
Backup
these
managed
nodes
area.
4.
Type
the
name
of
the
managed
node
on
which
the
backup
image
or
device
is
located
in
the
Save
image
on
node
field.
5.
Type
the
full
path
name
for
the
backup
file
in
the
Device/File
field.
6.
Click
Estimate
Backup
Size
to
see
the
estimated
backup
size
required
for
each
managed
node.
Ensure
that
sufficient
disk
space
exists
for
the
target
directory.
7.
Click
Close
to
display
the
Backup
Tivoli
Management
Region
window.
8.
Click
Start
Backup
to
display
the
Backup
Status
window
and
begin
backup
operation.
9.
Click
Close
to
close
the
Backup
Tivoli
Management
Region
window
and
display
the
Tivoli
desktop
window.
Verifying
that
the
required
software
is
running
Objective
To
confirm
that
software
required
to
enable
Tivoli
transactions
is
running
on
the
remote
target
computers
that
you
configure
during
installation.
32
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Note:
This
procedure
applies
to
local
systems.
For
information
about
the
required
software
for
z/OS
systems,
see
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129.
Background
information
One
of
the
following
basic
execution
daemons
must
be
running
on
computers
where
you
intend
to
install
managed
nodes
or
endpoints:
v
For
installation
on
UNIX
target
computers,
test
the
rexecd
daemon.
v
For
installation
on
Windows
target
computers,
test
the
Tivoli
Remote
Execution
Service
(TRIP)
process.
Required
authorization
role
On
UNIX,
the
user
must
have
root
privileges.
On
Windows,
the
user
must
have
membership
in
the
Administrators
group.
Before
you
begin
None
When
you
finish
Install
the
product
using
one
of
the
following
methods:
v
Chapter
5,
“Performing
a
Typical
installation,”
on
page
57
v
Chapter
6,
“Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment,”
on
page
71
Procedure
You
can
perform
this
procedure
from
the
command
line
only.
Command
line
in
UNIX:
1.
Run
an
rexec
command
string
against
the
target
computer.
The
rexec
command
runs
commands
on
remote
hosts
that
are
running
the
rexec
service.
For
example,
run
the
following
command:
rexec
<target_computer_name>
echo
test
2.
Respond
to
the
prompt
for
a
user
ID
and
password
by
typing
the
root
ID
and
password.
If
the
command
is
unsuccessful,
you
receive
an
error,
for
example,
an
authentication
error,
a
notice
that
the
server
is
down,
or
a
notice
that
rexec
failed
to
run.
Do
not
continue
installing
this
product
until
you
can
enable
the
rexec
daemon
accessible
on
the
target
computer.
Note:
The
syntax
for
the
rexec
command
varies,
depending
on
the
operating
system
you
are
using.
You
might
have
different
syntax
options
than
shown
in
the
example
above.
Command
line
in
Windows:
1.
Run
an
rexec
command
string
against
the
target
computer.
The
rexec
command
runs
commands
on
remote
hosts
that
are
running
the
rexec
service.
For
example,
run
the
following
command:
rexec
<target_computer_name>
cmd
/c
echo
test
Note:
The
syntax
for
the
rexec
command
varies,
depending
on
the
operating
system
you
are
using.
You
might
have
different
syntax
options
than
shown
in
the
example
above.
2.
Respond
to
the
prompt
for
a
user
ID
and
password
by
typing
the
Administrator
ID
and
password.
Chapter
3.
Pre-installation
requirements
33
3.
If
the
command
is
unsuccessful,
you
receive
an
error,
for
example,
an
authentication
error,
a
notice
that
the
server
is
down,
or
a
notice
that
the
process
failed
to
run.
Do
not
continue
installing
this
product
until
you
complete
these
steps:
a.
Log
on
to
the
target
computer
on
which
you
want
to
confirm
that
the
Tivoli
Remote
Execution
Service
exists.
b.
Access
the
Services
user
interface
in
the
Windows
control
panel.
c.
Find
the
Tivoli
Remote
Execution
Service
in
the
Services
list
and
perform
one
of
the
following
actions:
v
If
this
service
exists
and
the
status
is
″Stopped,″
click
Start.
—OR—
v
If
this
service
exists
and
the
status
is
″Started,″
resolve
firewall
blocks
or
other
network
connectivity
problems
between
this
computer
and
the
computer
on
which
you
are
installing
IBM
Tivoli
Monitoring.
For
example,
you
can
increase
access
privileges
to
resolve
some
types
communication
failure.
—OR—
v
If
this
service
does
not
exist,
run
the
setup.exe
executable
in
the
TRIP
directory
of
the
software
installation
CD
for
Tivoli
Management
Framework.
Follow
the
instructions
in
the
panels
of
the
installation
wizard
for
this
service.
Completing
installation
planning
sheets
A
planning.html
planning
sheet
exists
in
the
root
directory
of
the
documentation
CD
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Use
the
planning
sheet
to
plan
the
installation
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
You
can
open
this
.html
file
in
an
HTML
editor,
a
word
processor,
or
a
spreadsheet
application
and
type
the
values
for
your
installation
plan.
You
can
also
photocopy
the
sheets
in
this
document
or
the
sheets
from
the
version
of
this
document
and
complete
them
by
hand.
Table
11
describes
the
following
types
of
managed
resources
that
each
planning
sheet
covers:
v
Managed
nodes
and
the
gateway
on
each
managed
node.
v
Endpoints.
v
Proxy
managed
nodes,
which
are
repositories
for
sets
of
managed
objects.
You
can
use
proxy
managed
nodes
when
you
manage
applications
that
have
multiple
objects,
such
as
database
instances
in
a
database
application.
Table
11.
Managed
resources
and
their
purpose
Managed
resource
Purpose
Managed
nodes
Create
managed
nodes
on
servers
to
supplement
the
Tivoli
management
region
server.
A
managed
node
runs
the
same
software
that
runs
on
a
Tivoli
server.
It
can
communicate
with
other
managed
nodes
and
can
help
the
Tivoli
server
manage
endpoints.
When
a
managed
node
supplements
the
Tivoli
server,
you
achieve
the
following
benefits:
v
The
managed
nodes
share
the
processing
burden
of
the
Tivoli
server.
The
Tivoli
server
works
more
efficiently
because
it
performs
fewer
management
and
user
administration
operations.
v
Tivoli
network
transactions
flow
to
multiple
servers
instead
of
to
the
Tivoli
server
only.
34
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
11.
Managed
resources
and
their
purpose
(continued)
Managed
resource
Purpose
Gateways
Create
gateways
on
managed
nodes
to
enable
the
managed
node
to
perform
endpoint
management
operations
on
behalf
of
the
Tivoli
management
region
server.
A
gateway
transfers
large
amounts
of
data
to
endpoints
more
efficiently.
By
default,
the
maximum
amount
of
memory
to
use
for
storing
transient
data
is
set
to
10
MB.
Always
enable
managed
nodes
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
as
gateways
so
that
they
can
perform
endpoint
management
operations.
When
you
perform
a
Typical
installation
for
this
product,
the
installer
automatically
establishes
gateways
on
the
managed
nodes
that
you
create
during
installation.
Be
sure
to
create
gateways
on
any
managed
nodes
that
you
create
without
using
the
installer.
Endpoints
Create
endpoints
on
the
computers
that
you
want
to
manage.
Endpoints
communicate
with
the
Tivoli
management
region
through
a
specific
gateway
on
a
managed
node.
Proxy
managed
nodes
When
to
use:
When
you
monitor
and
manage
multiple
objects
on
a
single
endpoint,
you
can
use
a
proxy
managed
node
to
store
unique
information
about
each
object.
For
example,
multiple
database
objects
can
exist
on
a
single
endpoint.
The
Tivoli
management
region
server
must
have
information
to
identify
each
database
object,
such
as
the
name
of
the
database
and
the
password
for
the
database.
When
not
to
use:
You
do
not
need
a
proxy
managed
node
if
the
servers
in
the
Tivoli
environment
do
not
need
to
store
unique
information
about
multiple
objects
on
a
single
endpoint.
For
example,
in
some
cases
only
one
managed
object
exists
on
a
single
endpoint.
If
you
manage
server
objects
for
messaging
products
like
Lotus
Domino
or
Microsoft
Exchange,
the
managed
object
is
the
server
itself.
The
Tivoli
endpoint
that
runs
on
the
server
and
the
server
object
together
supply
complete
information
for
the
Tivoli
server.
No
proxy
managed
node
is
required
because
there
is
only
one
managed
server
object
on
the
endpoint.
Remember
that
even
if
a
database
object
exists
alone
on
an
endpoint,
it
has
unique
identifiers
and
possibly
a
password
that
enables
co-existence
with
other
objects.
The
Tivoli
server
must
have
this
information.
You
must
store
this
information
on
a
gateway
or
consider
storing
it
on
a
proxy
managed
node.
Benefits:
Proxy
managed
nodes
are
optional,
but
can
add
efficiency
to
the
Tivoli
environment.
Depending
on
its
power
and
location
in
the
network,
the
proxy
node
can
enable
the
Tivoli
server
to
access
information
it
needs
more
easily.
The
node
also
enables
the
Tivoli
server
to
restore
operations
quicker
when
a
gateway
server
shuts
down
temporarily.
By
default,
Tivoli
stores
unique
information
about
managed
objects
on
the
gateway.
When
the
managed
node
that
contains
this
gateway
is
geographically
remote
from
the
Tivoli
server,
the
connection
to
the
gateway
can
be
lost.
Tivoli
enables
transfer
of
operations
to
an
alternate
gateway
when
a
server
goes
down.
However,
that
alternate
gateway
does
not
contain
the
unique
information
on
managed
objects
that
is
required
for
operations
that
affect
specific
managed
objects.
In
this
case,
execution
of
these
operations
must
wait
until
the
original
gateway
returns
to
service.
Optimizing
a
proxy
managed
node:
When
you
want
to
ensure
that
the
Tivoli
server
maintains
access
to
unique
information
on
managed
objects,
create
a
proxy
managed
node
on
a
computer
that
has
optimal
network
connectivity
with
the
Tivoli
server.
For
example,
if
an
endpoint
gateway
server
is
geographically
remote
from
the
Tivoli
server,
local
network
connectivity
might
be
faster
and
more
stable
than
remote
connectivity.
If
so,
create
a
proxy
managed
node
at
the
same
geographic
site
as
the
Tivoli
server.
See
the
Tivoli
Management
Framework
documentation
for
details
on
creating
a
proxy
managed
node.
Use
the
following
planning
sheets
to
compile
the
information
you
need
during
installation:
v
Planning
sheet
for
creating
managed
nodes
in
Table
12
on
page
37
v
Planning
sheet
for
creating
endpoints
in
Table
13
on
page
38
Chapter
3.
Pre-installation
requirements
35
v
Planning
sheet
for
creating
proxy
managed
nodes
in
Table
14
on
page
40
36
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Tabl
e
12.
Pla
nnin
g
shee
t
for
crea
ting
man
aged
node
s
Key
Con
cep
t:
One
man
aged
nod
e
mus
t
exis
t
in
a
Tivo
li
man
agem
ent
regi
on.
Thi
s
prin
cipa
l
man
aged
nod
e
is
calle
d
the
Tivo
li
man
agem
ent
regi
on
serv
er.
Hos
t
nam
e
Nam
e
of
the
targ
et
com
pute
r
in
the
netw
ork
Gat
eway
nam
e
*
Nam
e
of
the
gate
way
**
Pla
tfor
m
Ope
rati
ng
syst
em
of
the
man
aged
nod
e
Use
r
nam
e
root
or
Ad
min
istr
ator
Pas
swor
d
Pass
wor
d
of
the
user
on
the
serv
er
Des
tin
atio
n
of
inst
alla
tion
file
s
Path
on
the
targ
et
com
pute
r
for
inst
alla
tion
of
the
prod
uct
Exa
mpl
e:
visi
on03
Exa
mpl
e:
visi
on03
_gw
Exa
mpl
e:
Sola
ris
Exa
mpl
e:
root
—
Exa
mpl
e:
/dat
a/my
node
*
Thi
s
nam
e
can
incl
ude
alph
anum
eric
char
acte
rs,
und
ersc
ores
(_),
hyph
ens
(-),
and
peri
ods
(.).
The
nam
es
are
case
-sen
siti
ve.
For
exam
ple,
the
nam
e
GW
Nam
e
is
dif
fere
nt
from
gwna
me.
**
You
mus
t
crea
te
a
gate
way
on
all
man
aged
nod
es
for
this
prod
uct.
A
gate
way
enab
les
the
man
aged
nod
e
to
com
mun
icat
e
wit
h
end
poin
ts.
In
a
Typi
cal
inst
alla
tion
,
the
inst
alle
r
auto
mat
ical
ly
crea
tes
a
gate
way
on
ever
y
man
aged
nod
e
that
you
crea
te.
The
inst
alle
r
crea
tes
a
uniq
ue
nam
e
for
thes
e
gate
way
s
by
add
ing
the
_gw
suff
ix
to
the
host
nam
e.
Chapter
3.
Pre-installation
requirements
37
Tabl
e
13.
Pla
nnin
g
shee
t
for
crea
ting
endp
oint
s
An
end
poin
t
is
a
com
pute
r
on
whi
ch
Tivo
li
soft
war
e
is
inst
alle
d
to
enab
le
com
mun
icat
ion
wit
h
the
Tivo
li
man
agem
ent
regi
on
serv
er.
Hos
t
nam
e
Nam
e
of
the
targ
et
com
pute
r
in
the
netw
ork
En
dp
oin
t
nam
e
*
Nam
e
you
assi
gn
to
the
end
poin
t
Pla
tfor
m
Ope
rati
ng
syst
em
of
the
end
poin
t
Use
r
nam
e
root
or
Ad
min
istr
ator
Pas
swor
d
Pass
wor
d
of
the
user
on
the
serv
er
Des
tin
atio
n
of
inst
alla
tion
file
s
Path
on
the
targ
et
com
pute
r
for
inst
alla
tion
of
the
prod
uct
Exa
mpl
e:
visi
on03
Exa
mpl
e:
visi
on03
_ep
Exa
mpl
e:
Sola
ris
Exa
mpl
e:
root
—
Exa
mpl
e:
/dat
a/my
node
*
Thi
s
nam
e
can
incl
ude
alph
anum
eric
char
acte
rs,
und
ersc
ores
(_),
hyph
ens
(-),
and
peri
ods
(.).
The
nam
es
are
case
-sen
siti
ve.
For
exam
ple,
the
nam
e
EP
Nam
e
is
dif
fere
nt
from
epna
me.
The
end
poin
t
nam
e
mus
t
be
dif
fere
nt
than
the
man
aged
nod
e
nam
e.
38
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
3.
Pre-installation
requirements
39
Tabl
e
14.
Pla
nnin
g
shee
t
for
crea
ting
prox
y
man
aged
obje
cts
Hos
t
nam
e
Nam
e
of
the
targ
et
com
pute
r
in
the
netw
ork
Man
aged
nod
e
nam
e
Nam
e
of
the
man
aged
nod
e
you
use
as
prox
y
En
dp
oin
t
nam
e
The
end
poin
t
whe
re
one
or
mor
e
dat
abas
e
inst
ance
exis
ts
Man
aged
obje
ct
nam
e
*
Nam
e
of
the
man
aged
obje
ct
on
the
man
aged
nod
e
Ob
ject
typ
e
Type
of
obje
ct
asso
ciat
ed
wit
h
the
prox
y
serv
er
Exa
mpl
e:
my_h
ost
Exa
mpl
e:
my_h
ost_
mn
—
Exa
mpl
e:
my_d
atab
ase@
my_e
ndpo
int
Exa
mpl
e:
Orac
le
11i
*
Thi
s
nam
e
can
incl
ude
alph
anum
eric
char
acte
rs,
und
ersc
ores
(_),
hyph
ens
(-),
and
peri
ods
(.).
The
nam
es
are
case
-sen
siti
ve.
For
exam
ple,
the
nam
e
MN
Nam
e
is
dif
fere
nt
from
mnn
ame.
40
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Obtaining
the
installation
files
You
can
use
CDs
or
files
downloaded
from
the
Web
to
perform
an
installation.
This
section
lists
the
CDs
and
Web
downloads
that
you
need
for
installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure
using
the
installer.
It
also
describes
the
directory
structure
you
need
to
set
up
when
downloading
files
from
the
Web.
If
you
are
planning
to
perform
manual
installations
or
upgrades
(installation
from
the
Tivoli
desktop
or
command
line),
see
Chapter
6,
“Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment,”
on
page
71
for
instructions
on
what
CDs
or
Web
downloads
you
need.
Using
installation
files
from
CDs
When
you
perform
an
installation,
the
installer
prompts
for
the
CDs
that
it
needs
as
you
go
through
the
installation
procedure.
Table
15
lists
the
required
and
optional
CDs
for
an
installation.
The
CDs
that
you
need
depend
partly
on
whether
you
are
doing
a
Typical
or
Evaluation
installation,
which
options
you
select
during
the
installation,
and
which
IBM
Tivoli
Monitoring
for
Web
Infrastructure
components
you
are
installing.
Read
the
explanations
in
the
table
to
determine
which
CDs
you
need.
Table
15.
CDs
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installation
CDs
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
1
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
2
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
3
The
Installation
Disk
1
and
Installation
Disk
2
CDs
are
required
for
all
installations.
Installation
Disk
3
is
required
for
Typical
installations
only
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed
and
want
to
remain
at
this
version.
The
installer
uses
this
CD
to
apply
required
patches
to
Version
3.7.1.
This
installation
CD
is
not
required
for
Evaluation
installations.
Tivoli
software
CDs
for
an
Evaluation
installation
Tivoli
Management
Framework
1
of
2,
Version
4.1
Tivoli
Management
Framework
2
of
2,
Version
4.1
Tivoli
Management
Framework
Language
Support,
Version
4.1
The
Tivoli
Management
Framework
CDs
are
required
if
you
have
no
version
of
Tivoli
Management
Framework
installed.
They
are
not
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed.
The
language
support
CD
is
required
if
you
want
to
install
Tivoli
Management
Framework
Version
4.1
in
a
supported
language
other
than
English.
Tivoli
Management
Framework
Upgrade
Version
3.7
to
Version
4.1
This
CD
is
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed.
When
you
are
performing
an
Evaluation
installation,
the
installer
requires
you
to
upgrade
Tivoli
Management
Framework
Version
3.7.1
to
Version
4.1.
IBM
Tivoli
Monitoring,
Version
5.1.1
IBM
Tivoli
Monitoring
Language
Support,
Version
5.1.1
The
IBM
Tivoli
Monitoring
CD
is
required
for
all
installations.
The
language
support
CD
is
required
if
you
want
to
install
IBM
Tivoli
Monitoring
in
a
supported
language
other
than
English.
IBM
Tivoli
Monitoring
Web
Health
Console
for
AIX,
HP,
SUN,
Version
5.1
IBM
Tivoli
Monitoring
Web
Health
Console
for
Windows,
Linux,
Version
5.1
Use
these
CDs
to
install
the
IBM
Tivoli
Monitoring
Web
Health
Console
on
the
operating
systems
specified
in
the
CD
title.
When
you
are
performing
an
Evaluation
installation,
the
installer
requires
you
to
install
the
Web
Health
Console.
Chapter
3.
Pre-installation
requirements
41
Table
15.
CDs
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Tivoli
software
CDs
for
a
Typical
installation
Tivoli
Management
Framework
1
of
2,
Version
4.1
Tivoli
Management
Framework
2
of
2,
Version
4.1
Tivoli
Management
Framework
Language
Support,
Version
4.1
The
Tivoli
Management
Framework
CDs
are
required
if
you
have
no
version
of
Tivoli
Management
Framework
installed.
They
are
not
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed.
The
language
support
CD
is
required
if
you
want
to
install
Tivoli
Management
Framework
Version
4.1
in
a
supported
language
other
than
English.
Tivoli
Management
Framework
Upgrade
Version
3.7
to
Version
4.1
This
CD
is
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed
and
you
want
to
upgrade
to
Version
4.1.
When
you
are
performing
a
Typical
installation,
you
can
choose
to
remain
at
the
current
version.
IBM
Tivoli
Monitoring,
Version
5.1.1
IBM
Tivoli
Monitoring
Language
Support,
Version
5.1.1
The
IBM
Tivoli
Monitoring
CD
is
required
for
all
installations.
The
language
support
CD
is
required
if
you
want
to
install
IBM
Tivoli
Monitoring
installed
in
a
supported
language
other
than
English.
IBM
Tivoli
Monitoring
Web
Health
Console
for
AIX,
HP,
SUN,
Version
5.1
IBM
Tivoli
Monitoring
Web
Health
Console
for
Windows,
Linux,
Version
5.1
Use
these
CDs
to
install
the
IBM
Tivoli
Monitoring
Web
Health
Console
on
the
operating
systems
specified
in
the
CD
title.
Installation
of
the
IBM
Tivoli
Monitoring
Web
Health
Console
is
optional.
Component
Software
CDs
for
Typical
or
Evaluation
installations
Use
the
following
CDs
as
needed,
depending
on
which
products
you
are
monitoring.
The
language
support
CDs
are
required
for
installing
in
supported
languages
other
than
English.
WebSphere
Application
Server
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
Component
Software
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
Language
Support
Apache
HTTP
Server
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Apache
HTTP
Server
Component
Software
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Apache
HTTP
Server
Language
Support
Internet
Information
Server
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Internet
Information
Server
Component
Software
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Internet
Information
Server
Language
Support
WebLogic
Server
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
WebLogic
Server
Component
Software
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
WebLogic
Server
Language
Support
iPlanet
Web
Server
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
iPlanet
Web
Server
Component
Software
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
iPlanet
Web
Server
Language
Support
Using
installation
files
from
the
Web
The
installation
files
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
are
available
from
the
Passport
Advantage
Web
site.
Passport
Advantage
is
an
IBM
licensing
program
for
distributed
software.
You
can
download
installation
files
from
42
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Passport
Advantage
if
you
enroll
in
the
program.
Upon
enrolling,
you
are
assigned
a
user
name
and
password
with
which
to
access
the
software
files
to
which
you
are
entitled.
You
can
access
Passport
Advantage
at
the
following
Web
site:
http://www-3.ibm.com/software/passportadvantage/
Table
16
lists
the
required
and
optional
downloads
for
installations
using
the
installer.
The
downloads
that
are
required
for
an
installation
depend
partly
on
whether
you
are
doing
a
Typical
or
Evaluation
installation,
which
options
you
select
during
the
installation,
and
which
IBM
Tivoli
Monitoring
for
Web
Infrastructure
components
you
are
installing.
Read
the
explanations
in
the
table
to
determine
which
downloads
you
need.
Before
you
perform
an
installation
from
downloaded
files
using
the
installer,
you
must
set
up
a
directory
structure
to
contain
the
files,
as
described
in
“Downloading
installation
files
from
the
Web”
on
page
46.
Table
16.
Web
download
links
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installation
software
downloads
Tivoli
Monitoring
for
Web
Infrastructure,
Install
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Tivoli
Monitoring
for
Web
Infrastructure,
Install
2
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Tivoli
Monitoring
for
Web
Infrastructure,
Install
3
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
The
Install
and
Install
2
downloads
are
required
for
all
installations.
The
Install
3
download
is
required
for
Typical
installations
only
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed
and
want
to
remain
at
this
version.
The
installer
uses
this
downloaded
file
to
apply
required
patches
to
Version
3.7.1.
This
download
is
not
required
for
Evaluation
installations.
Tivoli
software
downloads
for
an
Evaluation
installation
Tivoli
Management
Framework
v4.1
1
of
2,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
Tivoli
Management
Framework
v4.1
2
of
2,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
Tivoli
Management
Framework
Language
Support
v4.1,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
The
Tivoli
Management
Framework
downloads
are
required
if
you
have
no
version
of
Tivoli
Management
Framework
installed.
They
are
not
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed.
The
language
support
download
is
required
if
you
want
to
install
Tivoli
Management
Framework
Version
4.1
in
a
supported
language
other
than
English.
Tivoli
Management
Framework
Upgrade
v3.7
to
v4.1,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
This
download
is
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed.
When
you
are
performing
an
Evaluation
installation,
the
installer
requires
you
to
upgrade
Tivoli
Management
Framework
Version
3.7.1
to
Version
4.1.
Chapter
3.
Pre-installation
requirements
43
Table
16.
Web
download
links
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
IBM
Tivoli
Monitoring
V5.1.1
for
WinNT,
Win
2000,
WinXP,
HP-UX,
Solaris,
AIX,
Linux
Int
English
IBM
Tivoli
Monitoring
Lang
Support
V5.1.1
for
WinXP,
WinNT,
Win
2000,
AIX,
Solaris,
Linux,
HP-UX
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin
The
IBM
Tivoli
Monitoring
download
is
required
for
all
installations.
The
language
support
download
is
required
if
you
want
to
install
IBM
Tivoli
Monitoring
in
a
supported
language
other
than
English.
IBM
Tivoli
Monitoring
Web
Health
Console
V5.1.1
for
HP-UX,
Solaris,
AIX
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin,
Int
English
IBM
Tivoli
Monitoring
Web
Health
Console
V5.1.1
for
Windows,
Linux
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin,
Int
English
Use
these
downloads
to
install
the
IBM
Tivoli
Monitoring
Web
Health
Console
on
the
operating
systems
specified
in
the
download
title.
When
you
perform
an
Evaluation
installation,
the
installer
requires
you
to
install
the
Web
Health
Console.
44
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
16.
Web
download
links
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Tivoli
software
downloads
for
a
Typical
installation
Tivoli
Management
Framework
v4.1
1
of
2,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
Tivoli
Management
Framework
v4.1
2
of
2,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
Tivoli
Management
Framework
Language
Support
v4.1,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
The
Tivoli
Management
Framework
downloads
are
required
if
you
have
no
version
of
Tivoli
Management
Framework
installed.
They
are
not
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed.
The
language
support
download
is
required
if
you
want
to
install
Tivoli
Management
Framework
Version
4.1
in
a
supported
language
other
than
English.
Tivoli
Management
Framework
Upgrade
v3.7
to
v4.1,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
This
download
is
required
if
you
have
Tivoli
Management
Framework
Version
3.7.1
installed
and
you
want
to
upgrade
to
Version
4.1.
When
you
are
performing
a
Typical
installation,
you
can
choose
to
remain
at
the
current
version.
IBM
Tivoli
Monitoring
V5.1.1
for
WinNT,
Win
2000,
WinXP,
HP-UX,
Solaris,
AIX,
Linux
Int
English
IBM
Tivoli
Monitoring
Lang
Support
V5.1.1
for
WinXP,
WinNT,
Win
2000,
AIX,
Solaris,
Linux,
HP-UX
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin
The
IBM
Tivoli
Monitoring
download
is
required
for
all
installations.
The
language
support
download
is
required
if
you
want
to
install
IBM
Tivoli
Monitoring
a
supported
language
other
than
English.
IBM
Tivoli
Monitoring
Web
Health
Console
V5.1.1
for
HP-UX,
Solaris,
AIX
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin,
Int
English
IBM
Tivoli
Monitoring
Web
Health
Console
V5.1.1
for
Windows,
Linux
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin,
Int
English
Use
these
downloads
to
install
the
IBM
Tivoli
Monitoring
Web
Health
Console
on
the
operating
systems
specified
in
the
download
title.
Installation
of
the
IBM
Tivoli
Monitoring
Web
Health
Console
is
optional.
Chapter
3.
Pre-installation
requirements
45
Table
16.
Web
download
links
for
Evaluation
or
Typical
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Component
Software
downloads
for
Typical
or
Evaluation
installations
Use
the
following
downloads
as
needed,
depending
on
which
products
you
are
monitoring.
The
language
support
downloads
are
required
for
installing
in
supported
languages
other
than
English.
WebSphere
Application
Server
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Component
Software
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Language
Support
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Apache
HTTP
Server
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Internet
Information
Server
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
WebLogic
Server
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
iPlanet
Web
Server
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Downloading
installation
files
from
the
Web
Objective
To
obtain
the
installation
files
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
from
the
Web
and
to
set
up
the
required
directory
structure
to
contain
the
files
so
that
you
can
perform
an
installation
using
the
installer.
Background
information
This
procedure
describes
how
to
download
the
installation
software
from
the
Web.
The
procedure
also
describes
how
to
place
the
files
in
a
depot
structure
so
that
the
installation
program
can
find
them.
You
can
reference
a
single
depot
located
in
the
network
to
perform
installations
on
multiple
computers.
Table
17
on
page
47
lists
the
Web
download
links
for
the
installation
files
and
the
directories
to
contain
the
files.
You
need
to
create
directories
only
for
the
46
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
downloaded
files
that
you
need.
Use
Table
16
on
page
43
to
determine
which
downloads
are
necessary
for
your
installation.
Note:
You
do
not
need
to
create
a
depot
directory
structure
if
you
have
obtained
installation
CDs
because
the
installation
program
prompts
you
to
insert
the
CDs
it
requires
during
installation.
See
“Using
installation
files
from
CDs”
on
page
41
for
more
information.
Table
17.
Download
directories
for
a
Typical
or
Evaluation
installation
Download
link
Download
directory
Tivoli
Monitoring
for
Web
Infrastructure,
Install
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Any
directory
other
than
<depot>
Tivoli
Monitoring
for
Web
Infrastructure,
Install
2
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Tivoli
Monitoring
for
Web
Infrastructure,
Install
3
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
<depot>/
Tivoli
Management
Framework
v4.1
1
of
2,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
<depot>/TMF41Disk1
Tivoli
Management
Framework
v4.1
2
of
2,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
<depot>/TMF41Disk2
Tivoli
Management
Framework
Language
Support
v4.1,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
<depot>/TMF41Lang
Tivoli
Management
Framework
Upgrade
v3.7
to
v4.1,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
<depot>/TMF41Upg37
IBM
Tivoli
Monitoring
V5.1.1
for
WinNT,
Win
2000,
WinXP,
HP-UX,
Solaris,
AIX,
Linux
Int
English
<depot>/ITM
IBM
Tivoli
Monitoring
Lang
Support
V5.1.1
for
WinXP,
WinNT,
Win
2000,
AIX,
Solaris,
Linux,
HP-UX
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin
<depot>/ITMLang
IBM
Tivoli
Monitoring
Web
Health
Console
V5.1.1
for
HP-UX,
Solaris,
AIX
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin,
Int
English
<depot>/WHC
IBM
Tivoli
Monitoring
Web
Health
Console
V5.1.1
for
Windows,
Linux
Braz
Port,
French,
Italian,
German,
Spanish,
Japanese,
Korean,
Simp
Chin,
Trad
Chin,
Int
English
<depot>/WHC
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Component
Software
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
<depot>/WAS
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Language
Support
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
<depot>/WASLang
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
<depot>/Apache
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
<depot>/ApacheLang
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
<depot>/IIS
Chapter
3.
Pre-installation
requirements
47
Table
17.
Download
directories
for
a
Typical
or
Evaluation
installation
(continued)
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
<depot>/IISLang
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
<depot>/iPlanet
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
<depot>/iPlanetLang
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
<depot>/WebLogic
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Language
Support
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
<depot>/WebLogicLang
Required
authorization
role
None.
Before
you
begin
Determine
which
Web
download
links
you
need
to
access
by
reading
the
explanations
in
Table
16
on
page
43.
When
you
finish
You
are
ready
to
install
the
product
using
the
installer.
Follow
the
instructions
for
a
Typical
or
Evaluation
installation.
See
Chapter
5,
“Performing
a
Typical
installation,”
on
page
57
or
Chapter
4,
“Performing
an
Evaluation
installation,”
on
page
51.
Procedure
All
downloadable
files
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
are
self-extracting
archives.
You
can
log
into
Passport
Advantage
with
your
assigned
user
name
and
password
and
download
any
required
and
optional
parts.
1.
Create
a
depot
directory
(<depot>
on
the
hard
drive
of
the
computer
to
which
you
want
to
download
the
installation
files.
2.
Create
another
directory,
separate
from
the
depot
directory,
on
the
same
computer.
Additional
Information:
This
separate
directory
is
required
for
the
main
installation
download,
indicated
in
the
first
row
of
Table
16
on
page
43.
All
other
downloaded
files
are
stored
in
the
depot
directory.
3.
Create
the
required
subdirectories
within
the
installation
depot.
Additional
Information:
You
can
create
all
of
the
directories
listed
in
Table
17
on
page
47
or
you
can
create
just
the
subdirectories
that
correspond
to
the
downloads
required
for
your
installation.
(Read
the
explanations
in
Table
16
on
page
43
to
determine
which
downloads
are
required.)
For
example,
if
you
do
not
plan
to
install
the
IBM
Tivoli
Monitoring
Web
Health
Console,
you
do
not
need
to
create
a
WHC
directory.
4.
Download
from
the
Passport
Advantage
Web
site
the
compressed
files
that
contain
the
product
software
to
the
appropriate
directories,
as
indicated
in
Table
17
on
page
47.
Additional
Information:
For
example,
click
the
links
for
the
Install
and
Install
2
downloads
(first
two
rows
of
Table
17
on
page
47)
to
access
the
compressed
48
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
files.
Download
the
Install
compressed
file
to
the
directory
that
you
created
in
Step
2
on
page
48.
Download
the
Install
2
compressed
file
into
the
root
level
of
the
depot
directory
(<depot>/)
5.
Uncompress
the
software
packages
that
you
downloaded
within
their
respective
directories.
6.
Perform
the
following
additional
steps
if
you
downloaded
installation
files
for
the
IBM
Tivoli
Monitoring
Web
Health
Console:
Note:
The
following
steps
show
sample
commands
for
UNIX.
$depot
represents
the
depot
directory.
Use
Windows
Explorer
to
accomplish
the
same
results
on
Windows
systems.
a.
Create
a
new
subdirectory
named
HCONSOLE
at
the
root
level
of
the
$depotdirectory
($depot/HCONSOLE).
cd
$depot
mkdir
HCONSOLE
b.
Display
all
HCONSOLE
subdirectories
that
exist
within
the
<depot>
directory.
ls
*/HCONSOLE
Additional
Information:
When
you
uncompress
the
software
packages
in
Step
5,
several
directories,
including
an
HCONSOLE
directory,
are
created
within
each
of
the
depot’s
subdirectories
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
components.
For
example,
if
you
downloaded
files
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2,
an
HCONSOLE
directory
is
created
within
the
$depot/WAS
subdirectory
when
you
uncompress
the
files.
The
HCONSOLE
directories
contain
class
files
for
installation
into
the
IBM
Tivoli
Monitoring
Web
Health
Console.
c.
Move
the
contents
of
each
of
the
component
subdirectories
to
the
top-level
HCONSOLE
directory
that
you
created
in
Step
6a.
For
example:
mv
WAS/HCONSOLE/*
HCONSOLE
As
an
alternative
to
performing
the
preceding
steps
for
Web
Health
Console
files,
you
can
run
one
of
the
following
programs:
v
On
UNIX,
create
and
run
the
following
shell
script:
#!/bin/sh
#
Change
to
depot
dir
depot=/my/depotdir
cd
$depot
||
(
echo
"directory
$depot
does
not
exist"
;
exit
1
)
#
make
the
HCONSOLE
dir
mkdir
HCONSOLE
#
Move
all
product
HCONSOLE
dirs
for
i
in
*/HCONSOLE
;
do
mv
$i/*
HCONSOLE/.
done
v
On
Windows,
create
and
run
the
following
.bat
file:
@echo
off
set
depot=\my\depotdir
REM
Change
to
depot
dir
cd
%depot%
||
(
echo
directory
%depot%
does
not
exist
EXIT
/B
1
)
REM
make
the
HCONSOLE
dir
if
NOT
EXIST
HCONSOLE
mkdir
HCONSOLE
REM
Move
all
product
HCONSOLE
dirs
for
/D
%%i
in
(
*
)
do
(
Chapter
3.
Pre-installation
requirements
49
if
EXIST
%depot%\%%i\HCONSOLE
(
for
%%j
in
(
%depot%\%%i\HCONSOLE\*
)
do
move
%%j
%depot%\HCONSOLE
for
/D
%%j
in
(
%depot%\%%i\HCONSOLE\*
)
do
move
%%j
%depot%\HCONSOLE
)
)
50
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
4.
Performing
an
Evaluation
installation
This
chapter
describes
how
to
install
an
Evaluation
version
of
the
product
using
the
Evaluation
option
in
the
installer.
When
you
select
the
Evaluation
option,
the
installer
installs
IBM
Tivoli
Monitoring
for
Web
Infrastructure
and
a
limited
Tivoli
environment
on
one
computer
so
that
you
can
test
and
evaluate
the
product.
The
Evaluation
installation
is
not
intended
for
use
in
a
production
environment.
Objective
To
install
a
limited
Tivoli
environment
and
IBM
Tivoli
Monitoring
for
Web
Infrastructure
component
software
on
one
computer
so
that
you
can
test
and
evaluate
the
product.
Background
information
The
Evaluation
installation
works
best
if
the
target
computer
does
not
have
any
Tivoli
software
installed.
During
an
Evaluation
installation,
the
installer
creates
one
local
endpoint
on
the
computer.
No
software
is
installed
on
any
remote
computers.
When
you
perform
an
Evaluation
installation,
the
following
Tivoli
software
is
installed:
v
Tivoli
Management
Framework,
Version
4.1
v
IBM
Tivoli
Monitoring,
Version
5.1.1
v
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1
v
IBM
Tivoli
Monitoring
Web
Health
Console,
Version
5.1.1
During
the
installation
procedure,
you
can
choose
to
install
one
or
more
of
the
following
IBM
Tivoli
Monitoring
for
Web
Infrastructure
monitoring
components:
v
Apache
HTTP
Server
v
Internet
Information
Server
v
iPlanet
Web
Server
v
WebLogic
Server
v
WebSphere
Application
Server
Required
authorization
On
UNIX,
the
user
who
installs
the
product
must
have
root
privileges.
On
Windows,
the
user
must
have
membership
in
the
Administrators
group.
Before
you
begin
v
If
you
want
to
install
from
CDs,
collect
the
following
CDs
from
the
list
in
Table
15
on
page
41.
–
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installation
CDs
–
The
Tivoli
software
CDs
for
an
Evaluation
installation,
as
needed.
Read
the
explanations
in
the
table
to
determine
which
CDs
you
need
–
The
component
software
CDs
for
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
monitoring
components
that
you
want
to
install
–
The
language
support
CDs
for
the
monitoring
components
that
you
want
to
install
in
languages
other
than
English
©
Copyright
IBM
Corp.
2003
51
v
If
you
want
to
install
from
files
downloaded
from
the
Web,
you
must
create
an
installation
depot
to
contain
the
downloaded
files.
Refer
to
the
following
sections
to
determine
which
files
you
need
to
download
from
the
Web
and
how
to
set
up
an
installation
depot:
–
“Using
installation
files
from
the
Web”
on
page
42
–
“Downloading
installation
files
from
the
Web”
on
page
46v
If
you
are
installing
the
product
on
a
Solaris,
HP-UX,
or
AIX
operating
system,
ensure
that
the
required
fix
packs,
patches,
or
maintenance
packages
are
installed.
See
Table
1
on
page
15
for
information.
v
Close
all
running
applications.
When
you
finish
Complete
the
activities
described
in
Chapter
7,
“Completing
the
installation
of
the
product,”
on
page
85.
Procedure
1.
Log
on
to
the
computer
where
you
want
to
install
an
evaluation
version
of
the
product.
2.
Run
one
of
the
following
setup
executables
to
start
the
installation:
v
For
Windows,
run
setupWEB.bat.
v
For
UNIX,
run
setupWEB.sh.
Additional
Information:
v
The
setup
executable
is
located
in
the
root
directory
of
the
CD
labeled
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
1.
v
If
you
are
installing
from
files
downloaded
from
the
Web,
the
setup
executable
is
located
in
the
directory
where
you
downloaded
and
uncompressed
installation
files
from
the
following
Web
download
link:
Tivoli
Monitoring
for
Web
Infrastructure,
Install
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin.
3.
Click
Next
to
display
the
license
agreement.
4.
Select
I
accept
the
terms
in
the
license
agreement.
5.
Click
Next.
Third
Party
License
Terms
and
Conditions,
Notices
and
Information
is
displayed.
6.
Click
Next.
7.
Specify
the
directory
path
where
you
want
to
install
the
product.
8.
Click
Next.
9.
Specify
the
directory
path
where
you
want
to
create
a
depot
(temporary
directory)
for
product
installation.
Additional
Information:
The
depot
directory
contains
all
the
files
required
for
installation.
If
you
click
Cancel
in
an
installer
panel
always
delete
the
temporary
depot
directory.
You
can
begin
installation
again
by
running
the
setup
executable
on
the
installation
CD.
After
the
installation
is
complete,
the
installer
provides
an
option
to
automatically
delete
this
directory.
Note:
On
Windows,
the
depot
must
reside
on
the
target
computer.
You
cannot
perform
an
installation
of
the
product
on
Windows
using
a
depot
that
is
located
on
a
remote
system.
On
UNIX,
provide
a
directory
path
that
is
accessible
from
the
installation
computer
to
the
installation
depot.
10.
Click
Next
to
copy
the
files
to
the
installation
directories.
52
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
11.
Click
Next
when
the
installer
prompts
you
to
restart
the
application
and
continue
the
installation.
The
installation
options
window
is
displayed.
12.
Select
Evaluation/Product
Demonstration.
13.
Click
Next
to
display
the
user
password
window.
14.
Type
the
password
corresponding
to
the
displayed
User
ID
in
the
Password
and
Verify
Password
fields.
15.
Click
Next
to
display
the
language
option
window.
16.
Select
the
check
box
next
to
any
language
you
want
to
install.
17.
Click
Next
to
display
the
component
selection
window.
Figure
1.
Installation
options
window:
Evaluation/Product
Demonstration
option
Chapter
4.
Performing
an
Evaluation
installation
53
18.
Select
the
monitoring
components
that
you
want
to
install.
19.
Click
Next
to
display
the
first
of
a
series
of
windows,
each
of
which
prompts
you
for
the
directory
location
of
a
specified
CD
or
CD
image
that
contains
the
software
to
be
installed.
Additional
Information:
If
you
are
installing
from
files
that
were
downloaded
from
the
Web,
the
CD
images
must
be
located
in
specific
directories
within
the
depot
directory,
as
described
in
“Downloading
installation
files
from
the
Web”
on
page
46.
Figure
2.
Product
selection
panel
Figure
3.
Prompt
for
software
CD
54
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
20.
For
each
CD
prompt
window
that
is
displayed,
perform
the
following
steps:
a.
Insert
the
specified
CD
into
the
drive
if
you
are
not
installing
from
CD
image
files
that
were
downloaded
from
the
Web.
b.
Type
a
directory
path
or
click
Browse
to
specify
the
path
to
the
CD
or
CD
image.
c.
Click
Next.
d.
If
you
are
installing
from
CD
image
files
that
were
downloaded
from
the
Web,
click
No
in
response
to
the
message
that
asks
if
you
want
to
copy
the
files
to
the
depot
directory.
Additional
Information:
If
you
are
installing
from
CDs,
each
CD
image
is
copied
to
the
depot
directory.
21.
Click
Next
on
the
final
CD
prompt
window
to
display
the
Step
List
window.
Additional
Information:
When
the
Step
List
window
is
displayed,
the
installer
begins
installation
of
the
software
from
the
depot
to
the
install
location.
The
Step
List
shows
the
software
components
that
the
installer
installs,
and
it
displays
status
updates
for
the
installation
process.
The
first
two
steps
might
require
a
system
restart.
If
you
are
prompted
to
restart
the
system,
click
Finish
to
restart
the
computer.
See
Appendix
B,
“Icons
and
options
in
the
Step
List
window,”
on
page
147
for
a
description
of
status
icons
and
options
in
the
Step
List
window.
22.
(Optional)
If
you
want
to
cancel
the
installation
while
the
Step
List
is
running,
perform
the
following
steps:
a.
Click
Stop
and
allow
the
currently
running
process
to
finish.
Additional
Information:
If
you
click
Cancel
without
allowing
the
currently
running
process
to
finish,
the
system
might
remain
in
an
unpredictable
state.
b.
Click
Cancel
to
stop
the
installation
and
close
the
installer.
c.
Delete
the
temporary
depot
directory
created
by
the
installer.23.
(Optional)
Double-click
any
item
in
the
list
to
see
details
and
to
set
processing
instructions
for
that
step
in
the
Details
window.
24.
Click
OK
in
the
final
prompt
of
the
Step
List.
Additional
Information:
This
final
prompt
is
displayed
when
all
steps
in
the
Step
List
show
a
Passed
status.
If
all
steps
do
not
show
a
Passed
status,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Problem
Determination
Guide
for
troubleshooting
information.
25.
Click
Next.
26.
Select
Delete
the
temporary
files
to
delete
the
directory
of
temporary
installation
files
that
you
specified
at
the
beginning
of
the
installation
process.
27.
Click
Next.
28.
Click
Finish.
Chapter
4.
Performing
an
Evaluation
installation
55
56
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
5.
Performing
a
Typical
installation
This
chapter
describes
how
to
install
the
product
using
the
Typical
installation
option
in
the
installer.
This
installation
option
creates
a
Tivoli
server
and
installs
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Version
5.1.1.
During
a
Typical
installation,
you
can
specify:
v
Additional
computers
to
configure
as
managed
nodes
that
run
the
IBM
Tivoli
Monitoring
Version
5.1.1
software.
The
managed
nodes
can
share
the
workload
with
the
Tivoli
server.
v
Computers
that
you
want
to
monitor
(endpoints)
v
Computers
on
which
you
want
to
install
the
Web
Health
Console
Table
18
provides
an
overview
of
the
topics
covered
in
this
chapter.
Table
18.
Guidelines
for
a
Typical
installation
Goal
Refer
to
Install
the
product
using
the
Typical
option
in
the
installer.
“Installing
the
product
using
the
Typical
option”
If
necessary,
create
a
Windows
proxy
endpoint
to
enable
the
creation
of
Windows
endpoints
when
installing
from
a
UNIX-based
Tivoli
management
region
server.
“Creating
a
Windows
proxy
endpoint”
on
page
67
Installing
the
product
using
the
Typical
option
Objective
To
use
the
installation
wizard
with
predefined
default
values
to
automatically
create
a
Tivoli
environment
and
install
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
The
wizard
optionally
creates
managed
resources
in
the
Tivoli
environment,
as
described
in
this
procedure.
Note:
If
you
want
to
manage
z/OS
systems
running
IBM
WebSphere
for
z/OS,
see
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129.
Background
information
The
target
computer,
which
becomes
the
Tivoli
management
region
server,
must
match
one
of
the
following
profiles:
v
Has
no
software
installed
for
the
Tivoli
Management
Framework
—OR—
v
Has
Tivoli
Management
Framework
Version
3.7.1
or
a
later
version
installed.
You
cannot
install
this
product
on
systems
that
run
previous
versions
of
the
Tivoli
Management
Framework.
When
you
perform
a
Typical
installation,
the
following
Tivoli
software
is
installed
or
upgraded.
In
some
cases,
the
upgrade
is
optional.
v
Tivoli
Management
Framework
©
Copyright
IBM
Corp.
2003
57
The
installer
installs
Tivoli
Management
Framework,
Version
4.1
if
no
Tivoli
Management
Framework
software
exists.
If
Version
3.7.1
is
installed,
the
installer
asks
if
you
want
to
upgrade
to
Tivoli
Management
Framework,
Version
4.1.
You
can
upgrade
or
choose
to
remain
at
the
current
level.
In
either
case,
the
installer
applies
the
required
patches.
(The
required
patches
for
Version
3.7.1
and
Version
4.1
are
listed
in
Appendix
A,
“Patches
and
fix
packs,”
on
page
145.)
v
IBM
Tivoli
Monitoring,
Version
5.1.1
If
you
have
a
back-level
version
installed
(Tivoli
Distributed
Monitoring
Advanced
Edition,
Version
4.1
or
higher),
the
installer
automatically
upgrades
to
IBM
Tivoli
Monitoring,
Version
5.1.1.
v
IBM
Tivoli
Monitoring
Component
Services
The
installer
installs
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1
if
no
IBM
Tivoli
Monitoring
Component
Services
software
exists.
If
a
back-level
version
is
installed,
the
installer
asks
if
you
want
to
upgrade
to
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1.
You
can
upgrade
or
choose
to
remain
at
the
current
level.
v
(Optional)
IBM
Tivoli
Monitoring
Web
Health
Console,
Version
5.1.1
During
installation,
you
can
choose
whether
or
not
to
install
the
Web
Health
Console
on
target
computers
that
you
specify.
If
a
back-level
version
already
exists,
the
installer
automatically
upgrades
to
the
current
version.
During
the
installation
procedure,
you
can
choose
to
install
one
or
more
of
the
following
IBM
Tivoli
Monitoring
for
Web
Infrastructure
monitoring
components:
v
Apache
HTTP
Server
v
Internet
Information
Server
v
iPlanet
Web
Server
v
WebLogic
Server
v
WebSphere
Application
Server
During
the
installation
procedure,
you
can
optionally
create
managed
nodes
(other
than
the
Tivoli
server),
endpoints,
and
Web
Health
Consoles.
To
create
Windows
endpoints
using
the
installer,
at
least
one
Windows
endpoint
must
exist
in
the
domain
of
the
Tivoli
management
region
server
(the
computer
from
which
you
start
the
installer).
If
you
are
installing
from
a
Windows
system,
and
no
Windows
endpoints
exist,
the
installer
automatically
creates
a
Windows
proxy
endpoint,
which
enables
you
to
create
additional
Windows
endpoints.
If
you
are
installing
from
a
UNIX-based
system,
you
must
create
the
Windows
proxy
endpoint
by
following
a
separate
procedure.
Table
19
summarizes
what
you
need
to
do
under
various
conditions.
Table
19.
Procedures
for
creating
Windows
endpoints
What
is
the
operating
system
of
the
Tivoli
server?
Do
Windows
endpoints
already
exist
in
the
domain
of
the
Tivoli
server?
Yes
No
Windows
Complete
this
procedure
(Installing
the
product
using
the
Typical
option)
only.
Complete
this
procedure
(Installing
the
product
using
the
Typical
option)
only.
The
installer
automatically
creates
one
Windows
proxy
endpoint,
which
enables
you
to
create
Windows
endpoints
using
the
installer.
58
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
19.
Procedures
for
creating
Windows
endpoints
(continued)
UNIX-based
Complete
this
procedure
(Installing
the
product
using
the
Typical
option)
only.
1.
Complete
this
procedure
(Installing
the
product
using
the
Typical
option)
to
Step
31
on
page
66.
During
the
procedure,
specify
the
Windows
endpoints
that
you
want
to
create.
2.
Create
a
Windows
proxy
endpoint
by
completing
the
procedure
“Creating
a
Windows
proxy
endpoint”
on
page
67.
3.
Return
to
the
installer
and
complete
the
Installing
the
product
using
the
Typical
option
procedure.
The
installer
creates
the
endpoints
that
you
specified
earlier
in
the
procedure.
Required
authorization
On
UNIX,
the
user
who
installs
the
product
must
have
root
privileges.
On
Windows,
the
user
who
installs
the
product
must
have
membership
in
the
Administrators
group.
Before
you
begin
v
If
you
want
to
install
from
CDs,
collect
the
following
CDs
from
the
list
in
Table
15
on
page
41.
–
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installation
CDs
–
The
Tivoli
software
CDs
for
a
Typical
installation,
as
needed.
Read
the
explanations
in
the
table
to
determine
which
CDs
you
need
–
The
component
software
CDs
for
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
monitoring
components
that
you
want
to
install
–
The
language
support
CDs
for
the
monitoring
components
that
you
want
to
install
in
languages
other
than
Englishv
If
you
want
to
install
from
files
downloaded
from
the
Web,
you
must
create
an
installation
depot
to
contain
the
downloaded
files.
Refer
to
the
following
sections
to
determine
which
files
you
need
to
download
from
the
Web
and
how
to
set
up
an
installation
depot:
–
“Using
installation
files
from
the
Web”
on
page
42
–
“Downloading
installation
files
from
the
Web”
on
page
46v
Ensure
that
target
computers
on
which
you
plan
to
create
managed
nodes
are
running
the
following
processes
to
enable
Tivoli
transactions:
–
On
Windows
systems,
the
Tivoli
Remote
Execution
Service
(TRIP)
process
must
be
running.
–
On
UNIX-based
systems,
the
rexecd
daemon
must
be
running.
See
“Verifying
that
the
required
software
is
running”
on
page
32
for
more
information.
v
See
Chapter
2,
“Guidelines
for
installation
and
setup,”
on
page
15
for
information
about
additional
activities
required
prior
to
installation.
v
Close
all
local
applications
during
installation
except
for
Tivoli
Management
Framework,
if
installed.
If
Tivoli
Management
Framework
is
installed,
it
must
be
running
on
the
Tivoli
server
and
on
any
managed
nodes
and
endpoints
that
are
part
of
the
Framework.
Note:
For
Windows
installations,
the
installer
requires
that
you
restart
the
computer
after
the
following
events:
Chapter
5.
Performing
a
Typical
installation
59
–
Creation
of
the
user
ID
for
the
Tivoli
Management
Framework
software
–
Installation
of
the
Tivoli
Management
Framework
software
When
you
finish
Perform
the
following
steps
on
any
endpoints
that
you
installed.
The
command
starts
the
monitoring
engine
so
that
you
can
distribute
and
run
resource
models:
1.
Access
the
command
line
interface
for
the
Tivoli
environment
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
2.
Run
the
following
command:
wdmcmd
-restart
-e
<endpoint_label>
where
<endpoint_label>
is
the
name
of
the
endpoint.
Complete
the
activities
described
in
Chapter
7,
“Completing
the
installation
of
the
product,”
on
page
85.
Before
you
use
this
product
to
manage
resources,
complete
the
configuration
steps
documented
in
the
user’s
guide
for
each
product
component.
Procedure
Note:
In
the
following
steps
and
on
the
installation
windows,
the
term
Tivoli
server
refers
to
a
managed
node.
The
term
a
computer
to
monitor
refers
to
an
endpoint.
1.
Log
on
to
the
computer
that
you
want
to
be
the
Tivoli
server.
2.
Run
one
of
the
following
setup
executables
to
start
the
installation:
v
For
Windows,
run
setupWEB.bat.
v
For
UNIX,
run
setupWEB.sh.
Additional
Information:
v
The
setup
executable
is
located
in
the
root
directory
of
the
CD
labeled
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
1.
v
If
you
are
installing
from
files
downloaded
from
the
Web,
the
setup
executable
is
located
in
the
directory
where
you
downloaded
and
uncompressed
installation
files
from
the
following
Web
download
link:
Tivoli
Monitoring
for
Web
Infrastructure,
Install
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin.
3.
Click
Next
to
display
the
license
agreement.
4.
Select
I
accept
the
terms
in
the
license
agreement.
5.
Click
Next.
Third
Party
License
Terms
and
Conditions,
Notices
and
Information
is
displayed.
6.
Click
Next.
7.
Specify
the
directory
path
where
you
want
to
install
the
product.
8.
Click
Next.
9.
Specify
the
directory
path
where
you
want
to
create
a
depot
(temporary
directory)
for
product
installation.
Additional
Information:
The
depot
directory
contains
all
the
files
required
for
installation.
If
you
click
Cancel
in
an
installer
panel
always
delete
the
temporary
depot
directory.
You
can
begin
installation
again
by
running
the
60
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
setup
executable
on
the
installation
CD.
After
the
installation
is
complete,
the
installer
provides
an
option
to
automatically
delete
this
directory.
Note:
On
Windows,
the
depot
must
reside
on
the
target
computer.
You
cannot
perform
an
installation
of
the
product
on
Windows
using
a
depot
that
is
located
on
a
remote
system.
On
UNIX,
provide
a
directory
path
that
is
accessible
from
the
installation
computer
to
the
installation
depot.
10.
Click
Next
to
copy
the
files
to
the
installation
directories.
11.
Click
Next
when
the
installer
prompts
you
to
restart
the
application
and
continue
the
installation.
The
installation
options
window
is
displayed.
12.
Select
Typical
and
click
Next.
13.
(Optional)
Select
languages
that
you
want
to
enable
for
users
of
the
product.
Additional
Information:
English
is
always
enabled
for
this
product.
The
installer
installs
the
language
enablement
packages
for
additional
languages
that
you
choose.
14.
Click
Next.
A
list
of
existing
managed
nodes
is
displayed.
Additional
Information:
At
least
one
managed
node
is
displayed
in
the
list.
This
managed
node
is
the
Tivoli
management
region
server
(referred
to
on
the
installation
windows
as
the
principal
Tivoli
server).
The
installer
creates
the
Tivoli
management
region
server
on
the
computer
on
which
you
are
installing
this
product.
The
installer
also
discovers
and
lists
any
managed
nodes
that
were
created
in
a
previous
installation
of
Tivoli
Management
Framework.
15.
(Optional)
Click
Add
to
create
additional
managed
nodes.
Additional
Information:
v
If
you
are
creating
a
Windows
managed
node,
the
target
computer
must
have
the
Tivoli
Remote
Execution
Service
(TRIP)
process
running.
If
you
are
creating
a
UNIX
managed
node,
the
target
computer
must
have
the
rexecd
daemon
running.
See
“Verifying
that
the
required
software
is
running”
on
page
32
for
more
information.
Figure
4.
Installation
options
window:
Typical
option
Chapter
5.
Performing
a
Typical
installation
61
v
After
adding
a
managed
node
to
the
list,
you
can
use
the
Edit
and
Remove
buttons
to
edit
it
or
remove
it
from
the
list.
You
can
edit
or
remove
only
the
managed
nodes
that
you
added.
You
cannot
edit
or
remove
any
of
the
managed
nodes
that
were
originally
displayed
in
the
list.
Note:
When
you
click
OK,
you
save
settings
for
both
the
Basic
tab
and
the
Advanced
tab.
16.
Follow
these
steps
to
create
a
managed
node:
a.
Specify
values
for
the
managed
node
in
the
fields
of
the
Basic
tab:
v
Host
Name
–
Type
the
fully
qualified
host
name
for
the
computer
on
which
you
create
the
managed
node.
For
example,
the
fully
qualified
host
name
for
tokyo
might
be
tokyo.sales.mycompany.com.
v
Platform
—
Click
the
drop-down
list
and
select
the
name
of
the
operating
system
on
the
managed
node.
v
User
—
Type
the
login
user
ID
of
the
person
who
performs
the
installation
on
the
managed
node.
This
user
ID
must
have
full
administrative
privileges
(Administrator
on
Windows
and
root
on
UNIX)
on
the
target
computer.
v
Password
and
Verify
Password
—
The
login
password
of
the
user
specified
in
the
User
field.b.
Click
the
Advanced
tab.
c.
Specify
values
in
the
fields
of
the
Advanced
tab.
v
Destination
—
(Optional)
A
customer
path
on
the
target
machine
where
you
want
to
install
the
Tivoli
software.
Otherwise,
Tivoli
uses
the
default
path
specification.
Figure
5.
Basic
tab
for
managed
nodes
Figure
6.
Advanced
tab
for
managed
nodes
62
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
v
Reboot
—
You
must
select
this
check
box
when
you
add
Windows
managed
nodes
to
the
Tivoli
management
region.
The
managed
node
software
is
activated
after
you
restart
the
Windows
computer.
v
Gateway
–
Specify
if
this
computer
is
a
gateway.d.
Click
OK
to
save
your
settings
and
return
to
the
installer.17.
Click
Next
to
display
the
product
selection
panel.
18.
Select
the
monitoring
components
that
you
want
to
install.
19.
Click
Next
to
display
a
list
of
Tivoli
servers.
20.
Select
each
Tivoli
server
that
you’re
going
to
use
to
communicate
with
endpoints
that
will
use
the
product
or
products
you
selected
in
Step
18.
Additional
Information:
When
the
product
is
already
installed
on
a
managed
node,
the
row
is
not
in
edit
mode.
The
check
box
is
selected
and
you
cannot
modify
it.
21.
Click
Next
to
display
the
endpoint
option
panel.
22.
Select
the
endpoints
that
you
want
to
monitor.
23.
(Optional)
You
can
create
endpoints
for
Tivoli
to
monitor
and
manage.
Additional
Information:
By
default
the
installer
assigns
endpoints
to
managed
nodes
whenever
possible.
The
installer
assigns
endpoints
to
the
Tivoli
management
region
server
only
when
no
managed
node
is
available.
If
you
want
to
change
gateway
assignments
for
an
endpoint
after
installation,
see
“Changing
the
gateway
assignment
of
an
endpoint”
on
page
109.
Note:
For
z/OS
proxy
endpoints,
see
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129
for
information.
Follow
these
steps
to
specify
endpoints
for
the
installer
to
create:
a.
Click
Add.
Figure
7.
Component
selection
window
Chapter
5.
Performing
a
Typical
installation
63
b.
Specify
values
for
the
endpoint
in
the
fields
of
the
Basic
tab:
v
Host
Name
–
Type
the
fully
qualified
host
name
for
the
computer
on
which
you
create
the
endpoint.
For
example,
the
fully
qualified
host
name
for
tokyo
might
be
tokyo.sales.mycompany.com.
v
Label
—
Type
a
unique
name
for
the
endpoint.
This
name
can
include
alphanumeric
characters,
underscores
(_),
hyphens
(-),
and
periods
(.).
The
names
are
case-sensitive.
For
example,
the
name
EPName
is
different
from
epname.
Note:
This
label
should
be
different
than
the
name
of
any
managed
node
in
the
Tivoli
management
region.
v
Platform
—
Click
the
drop-down
list
and
select
the
name
of
the
operating
system
on
the
endpoint.
v
User
—
Type
the
login
user
ID
of
the
person
who
performs
the
installation
on
the
endpoint.
Tivoli
recommends
that
you
use
Administrator
for
Windows,
and
root
for
UNIX.
v
Password
and
Verify
Password
—
The
login
password
of
the
user
specified
in
the
User
field.c.
Click
the
Advanced
tab.
d.
Specify
values
in
the
fields
of
the
Advanced
tab,
if
necessary.
v
Port
—
A
port
number
dedicated
to
communication
with
the
Tivoli
server.
The
default
is
9495.
v
Destination
—
The
path
on
the
target
machine
where
you
want
to
install
the
Tivoli
software.
Figure
8.
Basic
tab
for
endpoints
Figure
9.
Advanced
tab
for
endpoints
64
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
v
Reboot
—
You
must
select
this
check
box
when
you
add
Windows
endpoints.
The
endpoint
software
is
activated
after
you
restart
the
target
Windows
computer.e.
Click
OK
to
save
your
settings
and
continue
installation
in
the
installer
panels.24.
Click
Next
to
display
the
Web
Health
Console
panel.
25.
(Optional)
Install
the
Web
Health
Console
as
follows:
a.
Click
Install
the
Web
Health
Console,
then
click
Next
to
display
the
list
of
available
managed
nodes.
b.
Place
a
check
mark
in
the
Web
Health
Console
column
beside
the
name
of
each
managed
node
on
which
you
want
to
install
the
console.
Additional
Information:
When
you
specify
the
installation
of
the
Web
Health
Console
on
a
pre-existing
managed
node,
you
must
supply
the
user
ID
and
password.
The
installer
prompts
you
for
this
information
when
you
click
Next.
If
the
Web
Health
Console
is
already
installed,
do
not
place
a
check
mark
here.
Otherwise,
the
console
is
installed
again
because
the
installer
cannot
detect
previous
installations
of
the
Web
Health
Console.26.
Click
Next
to
display
the
first
of
a
series
of
windows,
each
of
which
prompts
you
for
the
directory
location
of
a
specified
CD
or
CD
image
that
contains
the
software
to
be
installed.
Additional
Information:
If
you
are
installing
from
files
that
were
downloaded
from
the
Web,
the
CD
images
must
be
located
in
specific
directories
within
the
depot
directory,
as
described
in
“Downloading
installation
files
from
the
Web”
on
page
46.
27.
For
each
CD
prompt
window
that
is
displayed,
perform
the
following
steps:
a.
Insert
the
specified
CD
into
the
drive
if
you
are
not
installing
from
CD
image
files
that
were
downloaded
from
the
Web.
Figure
10.
Prompt
for
software
CD
Chapter
5.
Performing
a
Typical
installation
65
b.
Type
a
directory
path
or
click
Browse
to
specify
the
path
to
the
CD
or
CD
image.
c.
Click
Next.
d.
If
you
are
installing
from
CD
image
files
that
were
downloaded
from
the
Web,
click
No
in
response
to
the
message
that
asks
if
you
want
to
copy
the
files
to
the
depot
directory.
Additional
Information:
If
you
are
installing
from
CDs,
each
CD
image
is
copied
to
the
depot
directory.
28.
Click
Next
on
the
final
CD
prompt
window
to
display
the
Step
List
window.
Additional
Information:
When
the
Step
List
window
is
displayed,
the
installer
begins
installation
of
the
software
from
the
depot
to
the
install
location.
The
Step
List
shows
the
software
components
that
the
installer
installs,
and
it
displays
status
updates
for
the
installation
process.
The
first
two
steps
might
require
a
system
restart.
If
you
are
prompted
to
restart
the
system,
click
Finish
to
restart
the
computer.
See
Appendix
B,
“Icons
and
options
in
the
Step
List
window,”
on
page
147
for
a
description
of
status
icons
and
options
in
the
Step
List
window.
29.
(Optional)
If
you
want
to
cancel
the
installation
while
the
Step
List
is
running,
perform
the
following
steps:
a.
Click
Stop
and
allow
the
currently
running
process
to
finish.
Additional
Information:
If
you
click
Cancel
without
allowing
the
currently
running
process
to
finish,
the
system
might
remain
in
an
unpredictable
state.
b.
Click
Cancel
to
stop
the
installation
and
close
the
installer.
c.
Delete
the
temporary
depot
directory
created
by
the
installer.30.
(Optional)
Double-click
any
item
in
the
list
to
see
details
and
to
set
processing
instructions
for
that
step
in
the
Details
window.
31.
(UNIX-based
Tivoli
management
region
servers
only)
If
you
specified
Windows
endpoints
to
create
in
Step
23
on
page
63,
and
no
Windows
endpoints
currently
exist
in
the
domain
of
the
Tivoli
management
region
server,
perform
the
following
steps:
a.
Click
Stop
at
the
top
of
the
Step
List.
b.
Perform
the
procedure
described
in
“Creating
a
Windows
proxy
endpoint”
on
page
67.
Additional
Information:
The
installer
creates
the
Windows
endpoints
that
you
specified
in
Step
23
on
page
63
after
you
create
the
Windows
proxy
endpoint
and
successfully
complete
the
steps
in
the
Step
List.
32.
Click
OK
in
the
final
prompt
of
the
Step
List.
Additional
Information:
This
final
prompt
is
displayed
when
all
steps
in
the
Step
List
show
a
Passed
status.
If
all
steps
do
not
show
a
Passed
status,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Problem
Determination
Guide
for
troubleshooting
information.
33.
Click
Next.
34.
Select
Delete
the
temporary
files
to
delete
the
depot
directory
that
you
specified
at
the
beginning
of
the
installation
process.
35.
Click
Next.
36.
Click
Finish.
66
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Creating
a
Windows
proxy
endpoint
Objective
To
enable
the
installer
to
create
Windows
endpoints
if
you
are
installing
from
a
UNIX-based
Tivoli
management
region
server
when
there
are
no
existing
Windows
endpoints
in
the
domain
of
the
server.
This
procedure
is
not
necessary
if
you
are
installing
from
a
Windows
system.
Background
information
The
installer
can
create
Windows
endpoints
for
the
Tivoli
management
region
server
that
you
are
installing.
However,
this
capability
exists
only
when
you
are
installing
the
Tivoli
management
region
server
on
a
Windows
operating
system.
A
proxy
endpoint
must
exist
in
a
Windows
domain
to
enable
the
installer
to
create
Windows
endpoints.
When
the
Tivoli
management
region
server
runs
on
Windows
and
you
want
to
create
Windows
endpoints,
the
installer
automatically
creates
the
proxy
endpoint
in
the
domain
in
which
that
server
resides.
This
proxy
should
share
the
same
domain
as
the
Tivoli
management
region
domain
because
it
uses
Windows
Universal
Naming
Convention
(UNC)
methods
to
provide
remote
access
to
newly
created
Window
endpoints.
The
proxy
endpoint
enables
creation
of
Windows
endpoints
in
any
domain
that
has
a
trusted
relationship
with
the
domain
that
contains
the
proxy.
The
Tivoli
server
uses
the
user
ID
and
password
for
the
proxy
endpoint
to
obtain
access
to
the
file
system
of
the
other
Windows
servers.
The
installer
also
associates
the
proxy
endpoint
with
a
gateway
in
the
Tivoli
management
region.
Otherwise,
the
Tivoli
management
region
server
cannot
use
the
proxy
endpoint.
You
perform
this
procedure
at
a
specific
point
during
the
installation
process
when
a
gateway
has
been
created
to
associate
with
the
proxy
endpoint.
With
this
proxy
access,
the
Tivoli
server
is
able
to
install
endpoints
on
Windows
systems
in
that
domain
and
in
other
Windows
domains
in
the
network
that
have
a
trusted
relationship.
Without
a
proxy
endpoint,
the
Tivoli
server
cannot
create
Windows
endpoints
in
that
remote
domain.
In
UNIX
installations,
the
installer
does
not
automatically
create
the
proxy
endpoint
that
Windows
requires.
When
the
Tivoli
management
region
server
you
are
installing
runs
a
UNIX
operating
system,
you
must
use
this
procedure.
The
procedure
sets
up
the
required
proxy
endpoint
in
the
Windows
domain
that
contains
target
Windows
servers
that
you
want
to
monitor
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Required
authorization
On
UNIX
systems,
the
user
who
installs
the
product
must
have
root
privileges.
On
Windows
systems,
the
user
must
have
membership
in
the
Administrators
group.
Before
you
begin
Perform
the
Typical
installation
procedure
through
Step
31
on
page
66.
Identify
the
Windows
computer
that
will
serve
as
the
proxy
endpoint.
You
need
the
endpoint
name
as
well
as
the
host
name
for
the
machine.
For
instance,
if
the
host
name
is
vision35.mycompany.com,
you
might
want
to
name
the
endpoint
vision35_ep.
When
you
finish
Complete
the
Typical
installation
steps
that
follow
31
on
page
66.
After
the
Typical
installation
process
finishes,
perform
the
procedures
in
Chapter
7,
“Completing
the
Chapter
5.
Performing
a
Typical
installation
67
installation
of
the
product,”
on
page
85,
which
include
verification
of
the
installation
of
all
endpoints
and
managed
nodes.
Procedure
You
perform
this
procedure
in
the
installer
and
in
the
Tivoli
Management
Framework
Endpoint
Setup
wizard.
This
procedure
supplements
the
Typical
installation
process,
at
the
point
when
the
installer
begins
to
process
the
Step
List.
Use
this
procedure
only
if
you
are
installing
the
product
on
a
UNIX-based
server.
This
procedure
is
not
necessary
if
you
are
installing
the
product
on
a
Windows-based
server.
1.
Click
Stop
at
the
top
of
the
Step
List
when
the
installer
starts
running
Step
1.
The
system
displays
a
message
indicating
that
it
will
stop
at
the
end
of
the
current
step.
2.
Click
OK
and
wait
for
the
step
to
finish
processing.
3.
In
the
Step
List
scroll
to
the
TMA
installation
step.
4.
Double-click
on
the
TMA
installation
step
to
access
the
Detail
window
for
the
step.
5.
Perform
the
following
steps:
a.
Click
Toggle
Breakpoint.
b.
Click
OK.
Figure
11.
Stop
deployment
message
Figure
12.
Detail
window
for
TMA
installation
step
68
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Additional
Information:
This
action
sets
a
breakpoint
for
when
the
installer
begins
to
install
endpoints.
A
stop
sign
icon
indicates
the
step
at
which
you
inserted
a
breakpoint.
While
this
step
is
in
breakpoint
mode,
you
enable
the
endpoint
proxy
as
described
in
Step
7.
6.
Click
Run
All
at
the
top
of
the
Step
List
window.
Additional
Information:
Processing
of
the
steps
in
the
Step
List
resumes,
until
the
installer
reaches
the
breakpoint
and
stops.
Prior
to
the
breakpoint
you
set
in
Step
5
the
installer
completes
the
creation
of
a
gateway.
To
install
correctly,
the
proxy
endpoint
must
refer
to
this
gateway.
Otherwise
the
Tivoli
management
region
server
cannot
recognize
the
proxy
endpoint.
7.
When
the
installer
reaches
the
breakpoint
you
created
in
Step
5,
install
the
proxy
endpoint
as
follows.
Perform
these
steps
on
the
computer
where
you
are
going
to
install
the
proxy
endpoint,
not
on
the
Tivoli
management
region
server.
a.
Insert
the
CD
labeled
Tivoli
Management
Framework
1
of
2,
Version
4.1
into
the
CD
drive
of
the
computer
that
you
want
to
be
the
endpoint.
b.
Run
the
setup
executable
located
in
the
following
subdirectory
path
of
the
Tivoli
installation
directory:
..\pc\lcf\winnt
c.
Click
Next
in
the
Tivoli
Management
Framework
Endpoint
Setup
window.
d.
Read
the
license
agreement.
e.
Click
Next
to
display
the
Endpoint
installation
options
window.
f.
(Optional)
Click
Browse
to
change
the
destination
directory
for
the
software.
g.
Click
Next
to
display
the
Tivoli
Remote
Access
Account
window.
h.
Type
the
user
name
and
password
of
the
account
through
which
Tivoli
Management
Framework
accesses
remote
file
systems.
If
you
do
not
require
access
to
remote
domains,
click
Next
to
skip
this
step.
i.
Click
Next
to
access
the
Advanced
Configuration
window.
j.
Specify
the
startup
and
configuration
options
information
listed
in
the
following
table:
Table
20.
Startup
and
configuration
options
Field
name
Use
when
...
Gateway
The
gateway
uses
a
port
number
other
than
the
default
9494.
Endpoint
You
want
to
specify
a
port
for
the
endpoint
to
use
other
than
the
default.
The
default
is
9495.
Other
Use
the
–g
<host_name_of_the_gateway>
option
to
specify
the
intercepting
gateway.
Use
the
–n
<host_name_of_the_endpoint>
option
to
specify
the
name
of
the
endpoint
you
are
installing
as
the
proxy.
k.
Click
Next
to
continue
the
installation
process.
Additional
Information:
The
installer
reports
that
communication
of
the
proxy
endpoint
and
the
gateway
was
successful.
The
endpoint
is
installed
and
logged
into
a
gateway.
The
installation
process
configures
the
endpoint
system
to
automatically
start
the
endpoint
service
when
the
system
starts.
If
the
system
does
not
start,
there
might
be
a
problem
with
the
communication
between
the
proxy
endpoint
and
the
gateway.
Remove
and
then
reinstall
the
endpoint.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Problem
Determination
Guide
for
information
on
how
to
remove
an
endpoint.
l.
Click
Next
to
display
the
Setup
Complete
window.
Chapter
5.
Performing
a
Typical
installation
69
m.
Click
Finish
to
display
the
Restart
Windows
window.
n.
Select
No
to
prevent
the
restarting
of
the
operating
system.
Additional
Information:
You
can
restart
the
system
after
the
installation
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
is
complete.
When
you
restart
the
computer,
the
Tivoli
Endpoint
service
is
created,
with
the
startup
type
set
to
automatic.8.
Press
OK
to
complete
the
endpoint
installation.
9.
On
the
Tivoli
management
region
server,
click
Run
All
in
the
installer
and
complete
the
installation
steps
that
follow
Step
31
on
page
66
in
the
Typical
installation
procedure.
70
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
This
chapter
describes
how
to
install
or
upgrade
IBM
Tivoli
Monitoring
for
Web
Infrastructure
using
the
Tivoli
desktop
or
command
line.
(This
book
refers
to
installations
using
the
Tivoli
desktop
or
command
line
as
manual
installations.)
These
procedures
enable
you
to
install
or
upgrade
the
required
base
software
and
one
or
more
product
components
without
using
the
installer.
You
might
find
it
more
convenient
to
perform
manual
installations,
rather
than
using
the
installer,
when
adding
computers
to
your
initial
configuration.
Note
that
this
chapter
describes
only
the
installation
of
the
base
and
component
software.
Depending
on
your
configuration,
additional
steps
might
be
required
before
you
can
use
the
product
to
start
managing
installed
applications.
For
example,
after
you
discover
resources
to
be
managed,
you
will
need
to
deploy
resource
models
or
event
adapters
to
monitor
those
resources.
If
you
need
to
add
additional
computers
to
your
configuration,
refer
to
Chapter
8,
“Expanding
your
Tivoli
environment,”
on
page
101
for
procedures
that
you
can
use
to
manually
install
managed
nodes,
endpoints,
or
Web
Health
Consoles.)
Version
3.7.1
or
4.1
of
the
Tivoli
Management
Framework
must
be
installed,
with
the
required
patches,
in
the
Tivoli
environment
before
you
perform
any
of
the
procedures
for
installing
or
upgrading
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
This
software
comes
with
the
installation
CDs
for
this
product.
Table
21.
Guidelines
for
installing
the
product
from
the
Tivoli
desktop
or
command
line
Goal
Refer
to
Access
the
Tivoli
environment
as
the
first
step
for
performing
any
of
the
procedures
described
in
this
chapter.
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73
Install
Tivoli
patches
to
update
performance
of
the
Tivoli
Management
Framework
software
or
to
upgrade
the
software.
You
must
have
Version
3.7.1
or
Version
4.1
installed,
with
required
patches,
before
you
install
or
upgrade
the
base
and
component
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
For
a
list
of
required
patches,
see
Appendix
A,
“Patches
and
fix
packs,”
on
page
145.
To
install
the
patches
or
to
upgrade
the
software,
follow
the
procedure
described
in“Upgrading,
installing
Tivoli
patches,
and
installing
fix
packs”
on
page
78.
Determine
which
base
and
component
software
you
need
to
install
and
upgrade,
and
in
what
order,
based
on
what
software
is
currently
installed
in
your
environment.
“Road
map
for
manual
installations
and
upgrades”
Based
on
this
determination,
perform
installations
of
new
software
and
upgrades
of
current
software
in
the
correct
order.
For
installations
of
new
software,
see
“Installing
new
Tivoli
software”
on
page
74.
To
install
patches,
fix
packs,
or
upgrades,
see
“Upgrading,
installing
Tivoli
patches,
and
installing
fix
packs”
on
page
78.
Road
map
for
manual
installations
and
upgrades
Table
22
on
page
72
lists
the
procedures
you
must
perform
to
manually
install
or
upgrade
the
product,
depending
on
what
software
is
currently
installed
in
your
Tivoli
environment.
Before
you
install
or
upgrade
any
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
component
software,
you
must
install
or
upgrade
to
the
©
Copyright
IBM
Corp.
2003
71
required
versions
of
IBM
Tivoli
Monitoring
and
IBM
Tivoli
Monitoring
Component
Services,
as
described
in
the
first
two
rows
of
the
table.
The
remaining
rows
of
the
table
describe
procedures
for
installing
or
upgrading
the
component
software.
Installation
or
upgrade
of
any
individual
component
is
optional.
Use
the
following
procedures
to
perform
all
installations
and
upgrades
specified
in
the
table:
v
Use
the
procedure
“Installing
new
Tivoli
software”
on
page
74
for
fresh
installations.
v
Use
the
procedure
“Upgrading,
installing
Tivoli
patches,
and
installing
fix
packs”
on
page
78
to
install
fix
packs
or
to
upgrade
existing
software
to
the
required
version.
Table
22.
Installation
and
upgrade
procedures
for
manual
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Required
version
of
product
or
component
If
the
following
version
or
predecessor
product
is
currently
installed...
...perform
the
following
procedures:
IBM
Tivoli
Monitoring,
Version
5.1.1
with
Fix
Pack
5
No
version
of
IBM
Tivoli
Monitoring
and
no
predecessor
product
—OR—
Distributed
Monitoring,
Version
3.7
1.
Install
IBM
Tivoli
Monitoring,
Version
5.1.1.
2.
Install
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5.
Tivoli
Distributed
Monitoring,
Version
4.1
Advanced
Edition
1.
Upgrade
to
IBM
Tivoli
Monitoring,
Version
5.1.0
from
4.1.
2.
Upgrade
to
IBM
Tivoli
Monitoring,
Version
5.1.1
from
5.1.0.
3.
Install
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5.
IBM
Tivoli
Monitoring,
Version
5.1.0
1.
Upgrade
to
IBM
Tivoli
Monitoring,
Version
5.1.1
from
5.1.0.
2.
Install
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5.
IBM
Tivoli
Monitoring,
Version
5.1.1
Install
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5.
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1
No
version
Install
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1.
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.0
Upgrade
to
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1
from
5.1.0.
72
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
22.
Installation
and
upgrade
procedures
for
manual
installations
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
(continued)
Required
version
of
product
or
component
If
the
following
version
or
predecessor
product
is
currently
installed...
...perform
the
following
procedures:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
No
version
Install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2.
Tivoli
Manager
for
WebSphere
Application
Server,
Version
1.1
1.
Uninstall
Tivoli
Manager
for
WebSphere
Application
Server,
Version
1.1.
See
the
Tivoli
Manager
for
WebSphere
Application
Server
documentation.
2.
Install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2.
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
WebSphere
Application
Server
(with
or
without
Fix
Pack
1
or
Fix
Pack
2)
Upgrade
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2.
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.1:
WebSphere
Application
Server
Upgrade
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2.
Accessing
the
Tivoli
Management
Framework
environment
Objective
To
access
the
Tivoli
Management
Framework
environment
so
that
you
can
use
the
operations
and
functions
of
IBM
Tivoli
Monitoring
software.
Background
information
You
can
access
the
Tivoli
Management
Framework
desktop
(Tivoli
desktop)
or
the
Tivoli
command
line
interface
in
order
to
use
the
operations
and
functions
of
IBM
Tivoli
Monitoring
software.
The
Tivoli
desktop
is
a
user
interface
that
provides
point-and-click
access
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure
features
and
functions.
The
Tivoli
desktop
provides
a
central
control
point
for
you
to
organize,
manage,
and
delegate
system
management
operations.
IBM
Tivoli
Monitoring
for
Web
Infrastructure
also
provides
a
command
line
interface
(CLI)
that
enables
you
to
enter
commands
from
the
keyboard.
You
can
use
these
commands
in
shell
scripts
and
with
system
utilities
such
as
the
UNIX
cron
utility.
For
more
information
about
using
commands,
refer
to
the
Tivoli
Management
Framework
Reference
Guide.
Required
authorization
role
Not
applicable.
Before
you
begin
Not
applicable.
When
you
finish
Not
applicable.
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
73
Procedure
There
are
separate
logon
procedures
for
UNIX
and
Windows.
For
a
Windows
operating
system,
use
the
Windows
menu
structure.
For
a
UNIX
operating
system,
use
the
UNIX
command
line.
UNIX:
1.
Log
on
to
a
UNIX
managed
node
or
Tivoli
management
region
server.
2.
Run
the
environment
initialization
and
setup
script.
v
If
you
are
using
the
Bourne,
Korn,
or
bash
shell,
run
the
following
command:
.
/etc/Tivoli/setup_env.sh
v
If
you
are
using
the
C
shell,
run
the
following
command:
source
/etc/Tivoli/setup_env.csh
3.
Type
the
tivoli
command
at
a
command
prompt
to
bring
up
the
Tivoli
logon
screen.
See
the
Tivoli
Management
Framework
Reference
Guide
for
more
information
on
this
command.
Windows
NT:
1.
Log
on
to
a
Windows
NT
managed
node
or
Tivoli
management
region
server.
2.
Bring
up
the
Tivoli
logon
screen.
Note:
If
you
are
using
a
port
other
than
port
94,
configure
the
shortcut
to
include
″-port
<port
number>″.
3.
Click
Start
→
Programs
→Tivoli
→
Tivoli
in
the
Windows
task
bar
to
access
the
login
screen
of
the
Tivoli
desktop.
4.
Type
the
following
values
in
the
fields
of
the
login
screen:
Host
Machine
Specifies
the
Tivoli
managed
node,
including
the
Tivoli
server
where
the
Tivoli
desktop
should
connect
Log
In
As
Specifies
the
login
name
to
the
managed
node
Password
Specifies
the
password
for
the
specified
login
name5.
Click
OK
to
open
the
Tivoli
desktop.
Installing
new
Tivoli
software
Objective
To
install
new
Tivoli
software
products
without
using
the
installer.
Background
information
Use
this
procedure
to
perform
new
installations
of
the
latest
versions
of
the
base
product
software
(IBM
Tivoli
Monitoring
and
IBM
Tivoli
Monitoring
Component
Services)
and
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
component
software.
See
“Road
map
for
manual
installations
and
upgrades”
on
page
71
to
determine
which
new
software
you
need
to
install.
Install
the
new
software
on
the
following
computers:
v
The
Tivoli
management
region
server
(Tivoli
server)
v
All
managed
nodes
(preferred)
or
at
a
minimum,
all
managed
nodes
that
host
gateways,
that
are
used
for
Tivoli
object
storage,
or
that
host
a
Tivoli
Business
Systems
Manager
task
server
74
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
23
lists
the
base
product
software
and
the
component
software,
with
associated
information
required
to
perform
the
installation
procedure.
Repeat
the
procedure
for
each
software
item
required
to
install.
Table
23.
Information
required
to
install
the
software
Install:
IBM
Tivoli
Monitoring,
Version
5.1.1
CD
name:
IBM
Tivoli
Monitoring,
Version
5.1.1
Web
download:
IBM
Tivoli
Monitoring
V5.1.1
for
WinNT,
Win
2000,
WinXP,
HP-UX,
Solaris,
AIX,
Linux
Int
English
IND
file
name:
/cdrom/DM511.IND
Software
name:
IBM
Tivoli
Monitoring,
Version
5.1.1
Install:
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
2
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure,
Install
2
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
IND
file
name:
/ITMCS/CMPTSVCS.IND
Software
name:
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1
Install:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
Component
Software
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Component
Software
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
IND
file
name:
/PRODUCT/ITMWAS.IND
Software
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure
–
WebSphere
Application
Server
5.1.2
Install:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Apache
HTTP
Server
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Apache
HTTP
Server
Component
Software
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
IND
file
name:
/PRODUCT/APACHE.IND
Software
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure
–
WebSphere
Application
Server
5.1.2
Install:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Internet
Information
Server
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Internet
Information
Server
Component
Software
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
IND
file
name:
/PRODUCT/IIS.IND
Software
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0
–
Internet
Information
Server
Install:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
WebLogic
Server
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
75
Table
23.
Information
required
to
install
the
software
(continued)
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
WebLogic
Server
Component
Software
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
IND
file
name:
/PRODUCT/WLS_510.IND
Software
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0
–
WebLogic
Server
Install:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
iPlanet
Web
Server
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
iPlanet
Web
Server
Component
Software
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Component
Software
V5.1
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
IND
file
name:
/PRODUCT/IPLANET.IND
Software
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0
–
iPlanet
Web
Server
Required
authorization
role
install_product
Also,
you
must
install
as
root
on
UNIX
and
Administrator
on
Windows.
Before
you
begin
v
Start
the
Tivoli
environment
for
the
installation
method
(command
line
interface
or
Tivoli
desktop)
that
you
plan
to
use,
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
v
Back
up
the
Tivoli
management
region
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
v
Prepare
a
list
of
all
the
computers
on
which
to
install
the
software.
You
can
use
the
following
command
to
display
a
list
of
managed
nodes:
wlookup
-a
-r
ManagedNode
v
Obtain
the
necessary
CDs
or
downloads.
Table
23
on
page
75
specifies
the
CD
and
Web
download
link
for
each
software
product
or
component.
v
Ensure
that
all
managed
nodes
are
running
and
communicating
with
the
Tivoli
server.
When
you
finish
Before
you
use
this
product
to
manage
resources,
complete
the
configuration
steps
documented
in
the
user’s
guide
for
each
product
component.
Procedure
You
can
perform
this
procedure
from
the
command
line
or
from
the
Tivoli
desktop.
Command
line:
Run
the
following
command
from
the
command
prompt:
winstall
-c
<source_dir>
[-s
<server>]
-i
<IND_file>
[-y]
[-n]
where:
-c
<source_dir>
Specifies
the
complete
path
to
the
directory
containing
the
installation
image.
76
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
-s
<server>
Specifies
the
name
of
the
managed
node
to
use
as
the
installation
server.
By
default,
the
installation
server
is
the
Tivoli
server.
-i
<IND_file>
Specifies
the
product
index
file
(.IND
file)
to
reference
for
the
installation.
See
Table
23
on
page
75
for
the
name
of
the
.IND
file
corresponding
to
the
software
that
you
are
installing.
-y
Installs
the
product
without
requesting
confirmation.
-n
Installs
the
product
on
all
managed
nodes
that
do
not
currently
have
the
product
installed.
Refer
to
the
Tivoli
Management
Framework
Reference
Manual
for
more
information
about
this
command.
Refer
to
“Tivoli
command
syntax”
on
page
xv
for
information
about
Tivoli
command
line
syntax.
Tivoli
desktop:
1.
Select
Install
from
the
Desktop
menu.
2.
Select
Install
Product
in
the
menu
to
display
the
Install
Product
window.
3.
If
necessary,
click
OK
to
bypass
a
harmless
error
message
about
the
media
settings.
4.
Click
Select
Media
to
display
the
File
Browser
window.
5.
In
the
Path
Name
text
field,
enter
the
full
path
to
the
.IND
file
for
the
software
that
you
are
installing.
Table
23
on
page
75
specifies
the
name
of
the
.IND
file
for
each
software
product
or
component.
Be
sure
to
use
backward
slashes
(\)
for
Windows
path
names
instead
of
forward
slashes
(/).
6.
Click
Set
Path.
The
File
Browser
window
displays
the
contents
of
the
specified
media
in
the
Files
scrolling
list.
7.
Click
Set
Media
&
Close.
8.
Select
the
software
name
from
the
Select
Product
to
Install
scrolling
list
in
the
Install
Product
window.
Refer
to
the
Software
name
row
in
Table
23
on
page
75
that
corresponds
to
the
product
or
component
software
that
you
are
installing.
9.
Prepare
the
Clients
to
Install
On
list
of
targets
for
software
installation:
a.
Disable
software
installation
for
some
clients,
as
needed:
1)
Take
no
action
if
the
client
is
listed
in
the
Available
Clients
scrolling
list.
2)
Select
a
client
that
does
not
require
the
software,
but
is
listed
in
the
Clients
to
Install
On
scrolling
list
by
default.
3)
Click
the
right
arrow
to
move
the
client
to
the
Available
Clients
scrolling
list.b.
Enable
software
installation
for
some
clients,
as
needed:
1)
Take
no
action
if
the
client
is
listed
in
the
Clients
to
Install
On
scrolling
list.
2)
Select
a
client
requires
the
software,
but
is
listed
in
the
Available
Clients
scrolling
list
by
default.
3)
Click
the
left
arrow
to
move
the
client
to
the
Available
Clients
scrolling
list.10.
Click
Install
&
Close
to
display
the
Product
Install
window
and
a
list
of
pending
installation
actions.
11.
Click
Continue
Install
to
begin
the
installation
process.
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
77
Additional
Information:
The
Product
Install
window
displays
the
progress
of
the
installation.
View
the
messages
in
the
task
output
window
to
determine
whether
the
product
installation
was
successful.
If
necessary,
see
the
IBM
Tivoli
Monitoring
for
Business
Integration
Problem
Determination
Guide
for
information
on
problem
determination.
12.
Click
Close
to
close
the
Product
Install
window.
13.
Select
Refresh
from
the
View
menu
bar.
The
desktop
displays
the
icon
for
the
product
you
installed.
14.
As
a
precautionary
measure,
back
up
the
Tivoli
management
region
databases
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
Use
a
unique
name
for
the
new
backup
files.
Upgrading,
installing
Tivoli
patches,
and
installing
fix
packs
Objective
To
install
a
Tivoli
software
patch,
fix
pack,
or
product
upgrade
without
using
the
installer.
Background
information
Use
this
procedure
to
update
or
upgrade
the
following
required
and
optional
software
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
v
Tivoli
Management
Framework,
Version
3.7.1
or
Version
4.1
–
You
can
update
Tivoli
Management
Framework,
Version
4.1,
by
installing
the
required
patches,
listed
in
Table
24
on
page
79.
–
You
can
update
Tivoli
Management
Framework,
Version
3.7.1,
by
installing
the
required
patches,
listed
in
Table
25
on
page
79.
The
result
of
this
procedure
is
that
you
remain
at
Version
3.7.1.
–
You
can
upgrade
from
Tivoli
Management
Framework,
Version
3.7.1,
to
Tivoli
Management
Framework,
Version
4.1,
by
installing
the
required
fix
pack,
listed
in
Table
27
on
page
80.
When
you
perform
this
procedure,
it
is
not
necessary
to
install
patches.v
The
required
base
product
software,
IBM
Tivoli
Monitoring
and
IBM
Tivoli
Monitoring
Component
Services
v
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure
component
software
Use
“Road
map
for
manual
installations
and
upgrades”
on
page
71
to
determine
which
fix
packs
and
upgrades
you
need
to
install
for
the
base
product
software
and
product
component
software.
Install
the
fix
packs
or
upgrade
software
on
all
computers
on
which
the
base
product
(IBM
Tivoli
Monitoring
and
IBM
Tivoli
Monitoring
Component
Services)
is
installed.
The
following
tables
list
information
that
you
need
while
performing
the
installation
procedure
for
a
patch,
fix
pack,
or
upgrade.
v
Table
24
on
page
79
and
Table
25
on
page
79
list
information
for
Tivoli
Management
Framework
patches.
v
Table
26
on
page
80
lists
information
for
fix
packs.
v
Table
27
on
page
80
lists
information
for
upgrades.
Repeat
the
installation
procedure
for
each
patch,
fix
pack,
or
upgrade.
78
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
24.
Information
required
for
installing
patches
for
Tivoli
Management
Framework,
Version
4.1
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
2
Web
link:
Tivoli
Monitoring
for
Web
Infrastructure,
Install
2
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Patch
name
IND
file
name
Software
name
4.1-TMF-0013
/patches/41TMF013/41TMF013.IND
Tivoli
Framework
Patch
4.1-TMF-0013
(build
05/28)
4.1-TMF-0014
/patches371/361TMF34/TMF3134.IND
Tivoli
Framework
Patch
4.1-TMF-0014
(build
05/30)
Table
25.
Information
required
for
installing
patches
for
Tivoli
Management
Framework,
Version
3.7.1
Note:
Install
the
patches
for
Tivoli
Management
Framework,
Version
3.7.1,
in
the
order
shown.
Some
patches
are
needed
only
for
Linux
or
OS/400
support.
Table
42
on
page
145
shows
which
patches
apply
only
to
Linux
or
OS/400.
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
3
Web
link:
Tivoli
Monitoring
for
Web
Infrastructure,
Install
3
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
Patch
name
IND
file
name
Software
name
3.6.1-TMF-0034
/patches371/361TMF34/41TMF36134.IND
Tier2
3.6.1
Tivoli
Framework
Endpoints
(3.6.1-TMF-0034)
3.6.1-TMF-0062
/patches371/361TMF62/361TMF62.IND
Linux
3.6.1
Tivoli
Framework
Endpoint
Bundle
(3.6.1-TMF-0062)
3.7-TMF-0021
/patches371/37TMF21/37TMF021.IND
3.7-TMF-0021
Tier
2
3.7
Endpoint
Bundles
for
Tier1
Gateways
3.7-TMF-0035
/patches371/37TMF35/37TMF035.IND
3.7-TMF-0035
Tivoli
Framework
Patch
3.7-TMF-0043
/patches371/37TMF43/37TMF43.IND
Tivoli
Management
Agent
3.7
(37TMF43-85)
for
AS/400
Endpoint
3.7.1-TMF-0059
/patches371/371TMF59/371TMF59.IND
Tivoli
Framework
Patch
3.7.1-TMF-0059
(build
03/19)
3.7.1-TMF-0066
/patches371/371TMF66/371TMF66.IND
Tivoli
Framework
Patch
3.7.1-TMF-0066
(build
05/31)
3.7.1-TMF-0073
/patches371/371TMF73/371TMF73.IND
Tivoli
Framework
Fixpack
3.7.1-TMF-0073
(build
07/25)
3.7.1-TMF-0074A
/patches371/371TMF74A/371TMF74A.IND
Tivoli
Framework
Patch
3.7.1-TMF-0074A
(build
03/19)
3.7.1-TMF-0083
/patches371/371TMF83/371TMF83.IND
Tivoli
Framework
Patch
3.7.1-TMF-0083
(build
08/05)
3.7.1-TMF-0087
/patches371/371TMF87/371TMF87.IND
Tivoli
Framework
Patch
3.7.1-TMF-0087
(build
09/12)
3.7.1-TMF-0097
/patches371/371TMF97/371TMF97.IND
Tivoli
Framework
Patch
3.7.1-TMF-0097
(build
04/03)
3.7.1-TMF-0099
/patches371/371TMF99/371TMF99.IND
Tivoli
Framework
Patch
3.7.1-TMF-0099
(build
02/13)
3.7.1-TMF-0114
/patches371/371TMF114/371TMF114.IND
Tivoli
Framework
Patch
3.7.1-TMF-0114
(build
10/16)
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
79
Table
26.
Information
required
for
installing
fix
packs
Fix
pack:
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
2
Web
Link:
Tivoli
Monitoring
for
Web
Infrastructure,
Install
2
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
Braz
Port
French
Italian
German
Spanish
Japan
Korea
Simp
Chin
Trad
Chin
IND
file
name:
/511ITM05.IND
Software
name:
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5
Table
27.
Information
required
for
installing
upgrade
software
Upgrade
to:
Tivoli
Management
Framework,
Version
4.1
From:
Tivoli
Management
Framework,
Version
3.7.1
CD
name:
Tivoli
Management
Framework
Upgrade
Version
3.7
to
Version
4.1
Web
download:
Tivoli
Management
Framework
Upgrade
v3.7
to
v4.1,
Multiplatform,
International
English,
Brazilian
Portuguese,
French,
German,
Italian,
Spanish
IND
file
name:
/TMF_41.IND
Software
name:
Tivoli
Management
Framework
Upgrade
Version
3.7
to
Version
4.1
Upgrade
to:
IBM
Tivoli
Monitoring,
Version
5.1.1
From:
Distributed
Monitoring,
Version
4.1
Advanced
Edition
CD
name:
IBM
Tivoli
Monitoring,
Version
5.1.1
Web
download:
IBM
Tivoli
Monitoring
V5.1.1
for
WinNT,
Win
2000,
WinXP,
HP-UX,
Solaris,
AIX,
Linux
Int
English
IND
file
name:
/upg41to51/DM51UPG.IND
Software
name:
IBM
Tivoli
Monitoring
Upgrade,
Version
4.1
(DM
Advanced
Edition)
to
5.1.0
Upgrade
to:
IBM
Tivoli
Monitoring,
Version
5.1.1
From:
IBM
Tivoli
Monitoring,
Version
5.1.0
CD
name:
IBM
Tivoli
Monitoring,
Version
5.1.1
Web
download:
IBM
Tivoli
Monitoring
V5.1.1
for
WinNT,
Win
2000,
WinXP,
HP-UX,
Solaris,
AIX,
Linux
Int
English
IND
file
name:
/upgrade/DM51UPG.IND
Software
name:
IBM
Tivoli
Monitoring
Upgrade,
Version
5.1.0
to
5.1.1
Upgrade
to:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
From:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.1:
WebSphere
Application
Server
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
Component
Software
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Component
Software
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
IND
file
name:
/UPGRADE/510WAS00.IND
80
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
27.
Information
required
for
installing
upgrade
software
(continued)
Software
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure
–
WebSphere
Application
Server
Upgrade
to
5.1.2
Upgrade
to:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
From:
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
WebSphere
Application
Server
CD
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
Component
Software
Web
download:
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Component
Software
V5.1.2
AIX
HP-UX
Linux
Solaris
Win2000
WinNT
WinXP
Int
Engl
IND
file
name:
/UPGRADE/510WAS00.IND
Software
name:
IBM
Tivoli
Monitoring
for
Web
Infrastructure
–
WebSphere
Application
Server
Upgrade
to
5.1.2
Required
authorization
role
install_product
Before
you
begin
v
If
you
are
upgrading
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2,
see
“Special
considerations
for
upgrading
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2”
on
page
83.
v
Start
the
Tivoli
environment
for
the
installation
method
(command
line
interface
or
Tivoli
desktop)
that
you
plan
to
use,
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
v
Back
up
the
Tivoli
management
region
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
v
Prepare
a
list
of
all
managed
nodes
on
which
to
install
the
software.
To
display
a
list
of
all
installed
Tivoli
software
by
managed
node,
run
the
wlsinst
-ah
command
from
the
Tivoli
command
line.
Install
the
patches,
fix
pack,
or
upgrade
software
on
all
managed
nodes
that
have
the
base
software
installed.
For
example,
install
Tivoli
Management
Framework
patches
or
the
Tivoli
Management
Framework
upgrade
software
on
all
managed
nodes
that
have
Tivoli
Management
Framework
installed.
v
Obtain
the
necessary
CDs
or
downloads:
–
Table
24
on
page
79
and
Table
25
on
page
79
specify
CD
and
Web
download
links
for
Tivoli
Management
Framework
patches.
–
Table
26
on
page
80
specifies
CD
and
Web
download
links
for
fix
packs.
–
Table
27
on
page
80
specifies
CD
and
Web
download
links
for
software
upgrades.v
Ensure
that
all
managed
nodes
are
running
and
communicating
with
the
Tivoli
server.
When
you
finish
If
you
are
upgrading
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2,
see
“Special
considerations
for
upgrading
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2”
on
page
83
for
information
about
event
processing.
Before
you
use
this
product
to
manage
resources,
complete
the
configuration
steps
documented
in
the
user’s
guide
for
each
product
component.
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
81
After
you
install
the
upgrade
on
the
Tivoli
management
region
server,
perform
the
following
procedures
if
any
resource
models
were
previously
distributed:
v
On
Windows
endpoints:
1.
Stop
the
IBM
Tivoli
Monitoring
engine
on
each
endpoint
by
running
the
following
command:
wdmcmd
-stop
-e
<endpoint_label>
where
<endpoint_label>
is
the
name
of
the
endpoint.
2.
Wait
15
minutes
after
stopping
the
engine
so
that
the
monitoring
processes
can
time
out
and
die
on
the
endpoints.
3.
Redistribute
all
profiles
that
contain
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
resource
models.v
On
UNIX
endpoints,
redistribute
all
profiles
that
contain
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
resource
models.
(On
UNIX
endpoints,
it
is
not
necessary
to
stop
the
IBM
Tivoli
Monitoring
engine
before
redistributing
the
profiles.)
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Run
the
following
command
from
the
command
prompt:
wpatch
-c
<source_dir>
-i
<IND_file>
[-y]
[-n]
where:
-c
<source_dir>
Specifies
the
complete
path
to
the
directory
containing
the
installation
image.
-i
<IND_file>
Specifies
the
product
index
file
(.IND
file)
to
reference
for
the
installation.
v
Table
24
on
page
79
and
Table
25
on
page
79
specify
.IND
files
for
Tivoli
Management
Framework
patches.
v
Table
26
on
page
80
specifies
.IND
files
for
fix
packs.
v
Table
27
on
page
80
specifies
.IND
files
for
software
upgrades.
-y
Installs
the
software
without
requesting
confirmation.
-n
Installs
the
patch,
fix
pack
or
upgrade
software
on
all
managed
nodes
that
do
not
currently
have
the
software
installed.
Tivoli
desktop:
1.
Select
Install
from
the
Desktop
menu.
2.
Select
Install
Patch.
3.
If
necessary,
click
OK
to
bypass
a
harmless
error
message
about
the
media
settings.
4.
Click
Select
Media
to
display
the
File
Browser
window.
5.
In
the
Path
Name
text
field,
enter
the
full
path
to
the
.IND
file
for
the
software
that
you
are
installing.
v
Table
24
on
page
79
and
Table
25
on
page
79
specify
.IND
files
for
Tivoli
Management
Framework
patches.
v
Table
26
on
page
80
specifies
.IND
files
for
fix
packs.
v
Table
27
on
page
80
specifies
.IND
files
for
software
upgrades.
82
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Be
sure
to
use
backward
slashes
(\)
for
Windows
path
names
instead
of
forward
slashes
(/).
6.
Click
Set
Path.
The
File
Browser
window
displays
the
contents
of
the
specified
media
in
the
Files
scrolling
list.
7.
Click
Set
Media
&
Close.
8.
Select
the
patch,
fix
pack,
or
upgrade
software
from
the
Select
Patch
to
Install
scrolling
list
in
the
Install
Patch
window.
See
the
tables
in
the
Before
You
Begin
section
for
the
software
names
of
patches,
fix
packs,
or
upgrades
that
are
displayed
in
the
Install
Patch
window.
9.
Select
the
target
clients
on
which
to
install
the
software
from
the
Available
Clients
scrolling
list.
10.
Click
the
right
arrow
to
move
the
selected
clients
to
the
Clients
to
Install
On
scrolling
list.
11.
Click
Install
&
Close
to
display
the
Patch
Install
window
and
a
list
of
pending
installation
actions.
12.
Click
Continue
Install
to
begin
the
installation
process.
Additional
Information:
The
Patch
Install
window
displays
the
progress
of
the
installation.
View
the
messages
in
the
task
output
window
to
determine
whether
the
patch
installation
was
successful.
13.
Click
Close
to
close
the
Patch
Install
window.
14.
As
a
precautionary
measure,
back
up
the
Tivoli
management
region
databases
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
Use
a
unique
name
for
the
new
backup
files.
Special
considerations
for
upgrading
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
Perform
the
following
procedures,
as
required,
when
you
upgrade
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
from
5.1.0
or
5.1.1:
v
Event
server
After
installing
the
upgrade
to
5.1.2,
rerun
the
Configure
Event
Server
task.
Configuration
data
that
is
needed
by
the
event
server
has
changed
in
this
release
and
must
be
rewritten
to
the
server.
Ensure
that
the
latest
Tmw2k.baroc
file
(included
with
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5)
has
been
loaded
into
the
current
rule
base.
The
new
Tmw2k.baroc
file
adds
a
definition
for
fqhostname,
which
must
be
loaded
into
the
event
server.
v
Event
adapter
Perform
the
following
procedures
if
any
adapters
were
previously
configured
and
running:
–
Prior
to
installing
the
upgrade,
stop
the
existing
event
adapter.
(The
stop
task
has
been
updated
to
conform
to
new
configuration
data
that
needs
to
be
passed
in.)
–
After
installing
the
upgrade,
rerun
the
Configure
TEC
Adapter
task.
Configuration
data
that
is
needed
by
the
adapter
has
changed
this
release
and
must
be
rewritten.
Running
the
Configure
TEC
Adapter
task
saves
the
new
configuration
data
and
restarts
the
adapter.
Chapter
6.
Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment
83
84
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
7.
Completing
the
installation
of
the
product
This
section
describes
how
to
verify
the
installation
and
enable
functionality
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Table
28.
Guidelines
for
completing
the
installation
of
the
product
Goal
Refer
to
Verify
the
success
of
the
installation
of
the
managed
nodes
and
endpoints.
“Verifying
the
installation
of
the
product”
on
page
86
Run
the
DMLinkJre
Tivoli
task
on
all
computers
that
have
existing
versions
of
the
Java
Runtime
Environment.
If
IBM
Tivoli
Monitoring
for
Web
Infrastructure
cannot
link
to
this
software,
you
cannot
distribute
and
run
resource
models.
“Installing
the
Java
Runtime
Environment”
on
page
87
“Linking
to
an
existing
Java
Runtime
Environment”
on
page
87
(Optional)
Load
class
files
that
enable
you
to
customize
the
resource
models
that
come
with
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
“Installing
files
to
enable
customization
of
resource
models”
on
page
88
See
IBM
Tivoli
Monitoring
for
Web
Infrastructure
users’
guides
for
information
on
using
the
resource
models:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
User’s
Guide
See
IBM
Tivoli
Monitoring
Resource
Model
Builder
User’s
Guide
to
learn
how
to
use
the
optional
Resource
Model
Builder
tool
to
create
custom
resource
models
to
use
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
(Optional)
Install
support
for
WebSphere
Application
Server
3.5.6
or
3.5.7.
“Installing
support
for
WebSphere
Application
Server
3.5.6
and
3.5.7”
on
page
90
Enable
the
storage
of
historical
data
that
you
can
use
in
the
Tivoli
Enterprise
Data
Warehouse.
“Installing
files
to
enable
Tivoli
Enterprise
Data
Warehouse”
on
page
91
Upgrade
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
warehouse
enablement
pack.
“Installing
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Pack
Fix
Pack”
on
page
94
©
Copyright
IBM
Corp.
2003
85
Table
28.
Guidelines
for
completing
the
installation
of
the
product
(continued)
Goal
Refer
to
Assign
authorization
roles
required
to
use
the
product
to
manage
and
monitor
servers.
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure
users’
guides
describe
required
authorization
roles:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
User’s
Guide
Install
available
language
support
packages
after
installation
when
you
choose
to
not
install
language
packs
during
installation.
“Installing
IBM
Tivoli
Language
Support
for
this
product”
on
page
96
Update
the
files
for
the
Web
Health
Console.
“Updating
Web
Health
Console
files”
on
page
99
Note:
Before
you
use
this
product
to
manage
resources,
complete
the
configuration
steps
documented
in
the
user’s
guide
for
each
product
component.
Verifying
the
installation
of
the
product
Objective
To
verify
successful
installation
of
the
product.
Background
information
This
procedure
describes
how
to
use
the
Tivoli
command
line
interface
to
list
the
elements
of
the
Tivoli
environment.
You
should
complete
this
procedure
before
running
the
product
to
confirm
correct
installation
and
connectivity
for
all
elements.
Required
authorization
role
The
installation
routine
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
creates
the
Tivoli
administrator
who
is
authorized
to
perform
this
procedure.
On
UNIX,
the
user
must
have
root
privileges.
On
Windows,
the
user
must
have
membership
in
the
Administrators
group.
For
other
users,
one
of
the
following
Tivoli
roles
is
recommended:
user,
admin,
senior,
or
super.
Before
you
begin
Access
the
Tivoli
environment
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
When
you
finish
None
Procedure
You
can
perform
this
procedure
from
the
Tivoli
desktop
or
from
the
command
line.
Command
Line:
Run
the
wlsinst
command
to
list
the
products
and
patches
for
each
managed
node
in
the
Tivoli
environment:
wlsinst
-p
-h
where:
86
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
–p
Lists
all
products
installed
in
the
Tivoli
management
region.
–h
Lists
the
host
name
and
interpreter
type
of
the
machines
on
which
the
products
are
installed.
Run
the
wep
command
to
list
all
gateways
in
the
Tivoli
management
region.
This
command
returns
a
list
of
gateways
that
includes
the
Tivoli
object
ID
number
and
name
of
all
endpoints
associated
with
the
gateway.
In
the
recommended
configuration
for
this
product,
you
install
a
gateway
on
each
managed
node
that
you
create.
So
the
following
command
lists
all
managed
nodes
or
gateways
in
the
Tivoli
management
region:
wep
ls
See
the
Tivoli
Management
Framework
Reference
Manual
for
a
complete
description
of
all
options
available
for
these
commands.
Tivoli
desktop:
To
verify
the
installation
from
the
Tivoli
desktop,
view
the
icons
for
the
managed
resources
and
products
that
you
installed
to
verify
that
they
exist.
Installing
the
Java
Runtime
Environment
Various
components
of
IBM
Tivoli
Monitoring
require
Java
Runtime
Environment
(JRE),
Version
1.3.x.
There
are
three
available
installation
methods:
v
JRE
1.3.x
is
available
on
the
IBM
Tivoli
Monitoring
installation
CD
for
installation
using
the
Tivoli
Software
Installation
Service
(SIS).
v
JRE
1.3.x
is
also
available
on
the
IBM
Tivoli
Monitoring
installation
CD
in
compressed
format,
for
manual
installation
or
installation
through
the
wdmdistrib
–J
command.
For
information
about
this
command,
see
the
Tivoli
Management
Framework
Reference
Manual.
v
If
the
endpoint
already
has
an
appropriate
version
of
JRE
installed,
you
need
to
link
only
the
product
component
to
the
existing
JRE
using
a
task
provided
with
the
product.
See
“Linking
to
an
existing
Java
Runtime
Environment”
for
information.
Notes:
1.
For
WebLogic
Server,
you
must
use
the
WebLogic
Server’s
JRE.
For
Linux,
you
must
install
the
WebLogic
Server’s
JRE
manually.
2.
If
the
JRE
is
not
installed
as
described
here,
the
creation
of
the
Apache
HTTP
Server,
iPlanet
Web
Server,
IBM
WebSphere
Application
Server,
or
WebLogic
Server
objects
might
fail
and
the
resource
models
will
not
work
properly.
3.
The
use
of
an
IBM
version
of
the
JRE
is
recommended.
4.
All
versions
of
the
JRE
on
the
CD
are
supplied
by
IBM,
except
for
the
HP-UX
version.
5.
Prerequisites
for
the
JRE
can
be
found
on
the
appropriate
README
file
in
the
JRE
directory
on
the
product
CD.
Linking
to
an
existing
Java
Runtime
Environment
Objective
To
link
the
endpoint
software
to
the
Java
Runtime
Environment.
Background
information
All
endpoints
for
all
components,
with
the
exception
of
Internet
Information
Server
(IIS),
require
access
to
the
Java
Runtime
Environment
(JRE)
to
enable
running
resource
models.
Chapter
7.
Completing
the
installation
of
the
product
87
The
Tivoli
DMLinkJre
task
enables
the
endpoint
to
identify
the
correct
path
to
the
Java
software.
You
must
run
this
against
each
endpoint
where
you
will
be
running
resource
models.
Note:
You
do
not
need
to
run
DMLinkJre
for
OS/400
or
z/OS
endpoints.
However,
you
must
ensure
that
Java
Version
1.3
or
1.3.1
is
installed
on
the
endpoints.
See
the
IBM
Tivoli
Monitoring,
Version
5.1.1,
User’s
Guide
for
information
about
the
Java
product
number,
options,
and
required
PTF
levels
for
OS/400
or
z/OS
endpoints.
Required
authorization
role
On
UNIX,
the
user
must
have
root
privileges.
On
Windows,
the
user
must
have
membership
in
the
Administrators
group.
Before
you
begin
Load
the
required
version
of
the
Java
Runtime
Environment
on
the
endpoint.
When
you
finish
None
Procedure
You
can
perform
this
procedure
from
the
Tivoli
desktop
only.
Tivoli
desktop:
1.
Click
TMR
Connections
in
the
Desktop
menu.
2.
Click
Top
Level
Policy
Regions.
3.
Double-click
TivoliDefaultMw2kRegion-TMRname,
where
TMRname
is
the
name
of
the
Tivoli
management
region
server.
The
Policy
Region
window
is
displayed.
4.
Double-click
the
IBM
Tivoli
Monitoring
Tasks
task
library
icon
to
display
the
Task
Library
window.
5.
Double-click
DMLinkJre
to
display
the
Execute
Task
window.
6.
Select
the
endpoint
or
endpoints
that
you
want
to
link
to
the
Java
software.
Additional
Information:
Alternatively,
you
can
select
target
endpoints
by
selecting
the
profile
managers
that
contain
those
endpoints.
The
installation
path
for
the
Java
software
on
each
endpoint
must
be
the
same
on
each
target
endpoint
in
that
profile.
This
is
also
true
if
you
select
more
than
one
endpoint.
7.
Click
Execute
to
display
the
Configure
Task
Arguments
window.
8.
Type
the
fully
qualified
path
to
the
top-level
directory
of
the
Java
software.
Note:
The
task
validates
the
link
to
the
Java
software
or
advises
you
of
a
path
error.
A
path
error
becomes
evident
later
when
the
distribution
of
resource
models
to
the
endpoint
generates
an
error
stating
that
the
Java
software
is
missing
or
not
installed.
9.
Click
Set
&
Execute.
Installing
files
to
enable
customization
of
resource
models
Objective
To
load
class
files
that
enable
you
to
customize
the
resource
models
that
come
with
the
product.
88
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Background
information
The
IBM
Tivoli
Monitoring
Resource
Model
Builder
is
a
programming
tool
for
creating,
modifying,
debugging,
and
packaging
resource
models
for
use
with
IBM
Tivoli
Monitoring
products.
Samples
of
best
practice
resource
models
have
also
been
provided
for
your
use
within
the
Resource
Model
Builder.
You
can
use
these
resource
models
as
working
examples
to
create
new
resource
models.
The
Tivoli
Maintenance
and
Support
Contract
covers
assistance
with
problems
and
issues
relative
to
the
operation
of
the
IBM
Tivoli
Monitoring
Resource
Model
Builder,
but
does
not
cover
assistance
for
new
or
modified
resource
models
other
than
the
ones
that
are
included
in
the
Resource
Model
Builder.
The
IBM
Tivoli
Monitoring
Resource
Model
Builder
User’s
Guide
describes
how
to
use
the
optional
Resource
Model
Builder
tool
to
create
custom
resource
models
based
on
the
standard
resource
models
that
come
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
When
you
customize
one
of
these
resource
models
in
the
Resource
Model
Builder,
you
must
associate
the
new
resource
model
with
a
class
file
called
a
Managed
Object
Format
(MOF)
file.
This
procedure
describes
how
to
make
the
.mof
files
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
available
to
the
Resource
Model
Builder.
A
.mof
file
is
an
ASCII
file
that
contains
the
formal
definition
of
a
resource.
For
example,
the
Apache
performance
resource
model
monitors
the
performance
of
a
Web
site
or
of
all
the
Web
sites
hosted
by
a
specific
Apache
HTTP
Server
instance.
The
.mof
file
for
this
resource
model
defines
the
properties
of
this
resource.
The
.mof
file
format
adheres
to
the
platform-neutral
Common
Information
Model
(CIM)
standard
of
the
Distributed
Management
Task
Force
(DMTF)
industry
consortium.
This
standard
reduces
the
cost
and
complexity
of
managing
computer
resources.
The
Resource
Model
Builder
tool
is
available
on
Windows
only
and
it
must
have
access
to
the
resources
of
the
Microsoft
Windows
Management
Instrumentation
(WMI)
SDK.
Information
and
software
for
the
SDK
is
available
from
Microsoft
Corporation.
Specifically,
this
procedure
uses
the
MOF
Compiler,
mofcomp.exe,
that
comes
with
the
SDK.
See
the
Windows
Management
Instrumentation:
Platform
SDK
online
help
for
more
information.
For
additional
information
about
the
.mof
files
included
in
this
product,
see
the
user’s
guide
for
each
component:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
User’s
Guide
Required
authorization
role
No
Tivoli
role
needed.
Before
you
begin
Install
the
Microsoft
Windows
Management
Instrumentation
(WMI)
SDK
from
Microsoft
Corporation.
Note:
WMI
is
already
installed
on
Windows
2000
endpoints.
Chapter
7.
Completing
the
installation
of
the
product
89
When
you
finish
See
the
IBM
Tivoli
Monitoring
Resource
Model
Builder
User’s
Guide
to
learn
how
use
the
optional
Resource
Model
Builder
tool.
You
use
the
Resource
Model
Builder
to
create
resource
models
based
on
the
standard
resource
models
that
come
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
As
part
of
the
creation
process,
you
create
a
dependency
between
the
new
resource
model
and
one
of
the
.mof
files
you
have
installed.
Procedure
You
can
perform
this
procedure
from
the
command
line
only.
Command
line:
1.
Access
the
mofcomp.exe
executable
in
the
%SystemRoot%\system32\wbem
directory.
2.
Run
the
following
command:
mofcomp
-N:\root\CIMv2
mof_file_name
where
mof_file_name
is
the
name
of
a
.mof
file
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
″\root\Cimv2″
refers
to
the
namespace
in
the
class
repository
that
includes
resource
model
information.
Additional
Information:
The
product
.mof
files
are
located
on
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
component
software
installation
CD.
Installing
support
for
WebSphere
Application
Server
3.5.6
and
3.5.7
Objective
To
install
support
for
WebSphere
Application
Server
3.5.6
or
3.5.7.
Background
information
If
you
are
managing
WebSphere
Application
Server
3.5.6
or
3.5.7,
you
must
install
support
for
the
correct
management
APIs.
These
are
provided
on
the
product
CD
in
the
3.5_SUPPORT_FILES
directory.
Required
authorization
role
No
Tivoli
role
required
Before
you
begin
Locate
the
3.5_SUPPORT_FILES
directory
on
the
product
CD.
When
you
finish
None
Procedure
To
install
these
files,
do
the
following:
1.
Copy
the
ITMJARS.tar
file
to
the
endpoint
to
be
managed.
2.
Move
to
the
WebSphere
Application
Server
install
directory
(cd
$WAS_HOME).
By
default,
this
is
c:\WebSphere\AppServer
on
Windows
systems,
and
/usr/WebSphere/AppServer
on
AIX
systems.
3.
Unpack
the
file
(tar
-xvf
<location
of
the
tar
file>/ITMJARS.tar).
This
procedure
creates
a
directory
called
ITMJARS
that
contains
jar
files.
This
file
must
be
unpacked
in
this
location.
The
product
will
access
it
from
this
location
as
part
of
its
operation
90
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Installing
files
to
enable
Tivoli
Enterprise
Data
Warehouse
Objective
To
install
the
extract,
transform,
and
load
(ETL)
programs
that
enable
reporting
in
the
Tivoli
Enterprise
Data
Warehouse.
Background
information
Note:
This
procedure
describes
installation
of
enablement
files
on
a
Tivoli
Enterprise
Data
Warehouse
environment
that
exists
on
a
single
computer.
This
type
of
installation
simplifies
configuration
and
setup,
but
might
serve
only
as
a
test
or
demonstration
environment,
and
can
only
be
installed
on
Windows.
Most
monitoring
environments
require
a
distributed
installation
of
Tivoli
Enterprise
Data
Warehouse.
To
learn
how
to
install
and
configure
enablement
files
for
a
distributed
environment,
see
Installing
and
Configuring
Tivoli
Enterprise
Data
Warehouse,
Version
1,
Release
1.
You
can
retrieve
and
store
data
from
resource
models
in
Tivoli
Enterprise
Data
Warehouse,
which
uses
the
data
to
produce
historical
reports.
IBM
Tivoli
Monitoring
for
Web
Infrastructure
provides
warehouse
enablement
packs
for
each
component.
This
procedure
describes
installing
the
warehouse
enablement
packs
on
a
single,
dedicated
computer
that
runs
Tivoli
Enterprise
Data
Warehouse.
The
extract,
transform,
and
load
(ETL)
programs
provided
by
the
IBM
Tivoli
Monitoring
Warehouse
Enablement
pack
extracts
data
from
resource
models
and
stores
it
in
the
central
data
warehouse.
The
IBM
Tivoli
Monitoring
Warehouse
Enablement
packs
enable
data
collection
for
all
products
that
are
based
on
IBM
Tivoli
Monitoring,
Version
5.1.1.
The
warehouse
enablement
packs
provided
by
the
individual
components
(such
as
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server)
extract
data
from
the
Warehouse
for
use
in
tabular
and
graphical
reports.
This
program
enables
custom
functionality
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
This
installation
has
the
following
requirements:
v
The
server
requires
250
MB
of
free
disk
space
for
the
enablement
files.
This
space
requirement
is
in
addition
to
the
space
required
for
Tivoli
Enterprise
Data
Warehouse
and
for
the
DB2
database
that
comes
with
the
product.
The
warehouse
enablement
packs
reside
in
the
installation
directory
for
Tivoli
Enterprise
Data
Warehouse.
v
The
installer
must
have
a
valid,
fully
qualified
host
name
to
complete
the
installation.
v
The
user
who
performs
the
installation
must
have
a
valid
user
name
and
password
to
access
the
DB2
instance
for
this
product.
See
the
Installing
and
Configuring
Tivoli
Enterprise
Data
Warehouse,
Version
1,
Release
1,
Guide
for
detailed
information
on
all
installation
and
configuration
options
for
the
enablement
files,
as
well
as
uninstallation
information.
Required
authorization
role
On
Windows,
the
user
must
have
membership
in
the
Administrators
group.
You
will
also
need
the
user
ID
and
password
to
configure
DB2.
Chapter
7.
Completing
the
installation
of
the
product
91
Before
you
begin
Install
Tivoli
Enterprise
Data
Warehouse
and
the
required
DB2
database
software
as
described
in
the
Installing
and
Configuring
Tivoli
Enterprise
Data
Warehouse,
Version
1,
Release
1,
Guide.
Reboot
each
system
in
your
Tivoli
Enterprise
Data
Warehouse
configuration
at
least
once
after
installing
Tivoli
Enterprise
Data
Warehouse
1.1
Fix
Pack
2,
before
installing
the
component
files.
When
you
finish
See
the
IBM
Tivoli
Monitoring
Warehouse
Enablement
Pack
Implementation
Guide
for
information
about
configuring
Tivoli
Enterprise
Data
Warehouse
for
IBM
Tivoli
Monitoring.
See
the
Warehouse
Enablement
Pack
Implementation
Guide
for
your
component
for
specific
post-installation
steps
you
must
perform.
Enable
data
logging
for
Tivoli
Enterprise
Data
Warehouse
as
described
in
the
user’s
guides
listed
below.
Refer
to
the
user’s
guide
for
your
component
for
information
about
using
the
Tivoli
Enterprise
Data
Warehouse
reports:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
User’s
Guide
Procedure
You
can
perform
this
procedure
in
the
Tivoli
Enterprise
Data
Warehouse
installation
wizard.
Installation
wizard:
1.
Log
on
to
the
computer
that
runs
Tivoli
Enterprise
Data
Warehouse.
2.
Insert
the
Tivoli
Enterprise
Data
Warehouse
installation
CD.
3.
Run
the
setup
executable
in
the
root
directory.
Additional
Information:
The
executable
launches
the
installation
wizard.
Select
the
executable
that
matches
your
operating
system:
v
For
Windows,
setup.exe
v
For
UNIX,
see
the
procedures
in
Installing
and
Configuring
Tivoli
Enterprise
Data
Warehouse,
Version
1,
Release
1,
Guide.4.
Insert
the
IBM
Tivoli
Monitoring
installation
CD.
5.
Install
the
extract,
transform,
and
load
program
that
extracts
data
and
places
it
into
the
central
data
warehouse
by
doing
the
following
steps.
This
program
comes
on
the
installation
CDs
for
IBM
Tivoli
Monitoring.
a.
Click
Next
to
display
the
installation
options
panel.
b.
Select
Application
Installation
only.
c.
Click
Next.
d.
Select
the
directory
where
you
want
to
install
the
files.
92
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Additional
Information:
Install
the
files
in
the
installation
directory
for
Tivoli
Enterprise
Data
Warehouse.
By
default,
this
directory
path
is
C:\Program
Files\TWH.
Check
the
environment
variable
TWH_TOPDIR
for
the
location
in
your
installation.
e.
Type
the
host
name.
Additional
Information:
The
wizard
requires
the
fully
qualified
host
name
for
the
computer.
For
example,
the
fully
qualified
host
name
for
myhost
might
be
myhost.mycompany.com.
f.
Type
the
user
name
and
password
that
you
used
to
configure
DB2.
g.
Type
the
directory
path
of
the
program
files:
\tedw_apps_etl\AMX.
This
is
the
path
for
the
CD
directory
that
contains
the
twh_app_install_list.cfg
configuration
file.
h.
Select
Now
to
verify
the
source
directory
immediately.
i.
Click
Next.
j.
If
the
wizard
detects
a
path
error,
modify
the
source
directory
path
and
click
Next
again.
k.
Click
Next.
Additional
Information:
This
procedure
does
not
require
use
of
the
option
to
install
additional
packages.
The
wizard
displays
a
summary
of
the
program
installation,
including
disk
space
required.
l.
Click
Install.
m.
Click
Finish
in
the
final
summary
screen.
Additional
Information:
The
twh.log
file
lists
events
that
occur
during
the
installation.
This
file
is
located
in
the
directory
containing
the
installed
Tivoli
Enterprise
Data
Warehouse
program.6.
Install
the
extract,
transform,
and
load
program
that
extracts
data
from
the
warehouse
for
use
in
tabular
and
graphical
reports
by
doing
the
following.
(This
program
comes
on
the
installation
CDs
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.)
For
example,
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,
insert
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Component
CD.
a.
Repeat
Steps
1
and
3
to
re-launch
the
Tivoli
Enterprise
Data
Warehouse
installation
wizard.
b.
Click
Next
to
display
the
installation
options
panel.
c.
Select
Application
Installation
only.
d.
Click
Next.
e.
Select
the
directory
path
where
you
want
to
install
the
program.
Additional
Information:
By
default,
this
directory
path
is
C:\Program
Files\TWH.
Check
the
environment
variable
TWH_TOPDIR
for
the
location
in
your
installation.
f.
Type
the
host
name.
Additional
Information:
The
wizard
requires
the
fully
qualified
host
name
for
the
computer.
For
example,
the
fully
qualified
host
name
for
myhost
might
be
myhost.mycompany.com.
g.
Type
the
user
name
and
password
that
you
used
to
configure
DB2.
h.
Type
the
directory
path
of
the
program
files:
/tedw_apps_etl.
This
is
the
path
for
the
CD
directory
that
contains
the
twh_app_install_list.cfg
configuration
file.
i.
Select
Now
to
verify
the
source
directory
immediately.
Chapter
7.
Completing
the
installation
of
the
product
93
j.
Click
Next.
k.
If
the
wizard
detects
a
path
error,
modify
the
source
directory
path
and
click
Next
again.
l.
Click
Next.
Additional
Information:
This
procedure
does
not
require
use
of
the
option
to
install
additional
packages.
The
wizard
displays
a
summary
of
the
program
installation,
including
disk
space
required.
m.
Click
Install.
n.
Click
Finish
in
the
final
summary
screen.
Additional
Information:
The
twh.log
file
lists
events
that
occur
during
the
installation.
This
file
is
located
in
the
directory
containing
the
installed
Tivoli
Enterprise
Data
Warehouse
program.
By
default,
this
directory
path
is
C:\Program
Files\TWH.
Check
the
environment
variable
TWH_TOPDIR
for
the
location
in
your
installation.7.
Stop
and
restart
the
following
services
for
Tivoli
Presentation
Services:
v
Server
for
IBM
Console
v
Web
Services
for
the
IBM
Console
See
the
Tivoli
Enterprise
Data
Warehouse
documentation
for
more
information.
Installing
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Pack
Fix
Pack
Objective
To
upgrade
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
warehouse
enablement
pack
by
installing
the
latest
fix
pack.
Attention:
Installing
this
fix
pack
results
in
the
deletion
of
all
reports
and
any
output
associated
with
them.
The
reports
are
re-added
after
the
installation
of
the
fix
pack,
but
you
cannot
restore
any
pre-existing
report
output.
Background
information
None
Required
authorization
role
On
Windows,
you
must
have
membership
in
the
Administrators
group.
Note:
These
instructions
apply
only
to
Windows
systems.
You
must
also
have
the
user
ID
and
password
to
configure
DB2.
Before
you
begin
Before
you
install
the
fix
pack,
perform
the
following
actions:
v
Upgrade
the
Tivoli
management
region
server.
v
Upload
all
data
collected
from
prior
versions
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
Data
logged
from
prior
versions
is
not
compatible
with
this
fix
pack
.
v
Install
all
prerequisite
software
as
listed
in
Chapter
3,
“Pre-installation
requirements,”
on
page
19.
v
Install
the
Warehouse
Enablement
Pack
for
the
IBM
WebSphere
Application
Server
component.
See
“Installing
files
to
enable
Tivoli
Enterprise
Data
Warehouse”
on
page
91
for
information.
94
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Note:
Before
applying
the
fix
pack
on
the
Tivoli
Enterprise
Data
Warehouse,
ensure
that
all
the
processes
that
belong
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
warehouse
enablement
pack
are
in
development
mode.
v
Perform
a
manual
backup
of
the
following
Tivoli
Enterprise
Data
Warehouse
components:
–
Tivoli
Enterprise
Data
Warehouse
databases
–
Tivoli
Enterprise
Data
Warehouse
application
software
–
Tivoli
Presentation
Services,
which
provides
the
user
interface
used
for
Tivoli
Enterprise
Data
Warehouse
Reporting
Interface
There
is
no
automated
uninstallation
provided
for
this
fix
pack.
If
there
are
issues
or
problems,
you
can
restore
the
environment
to
the
backed
up
level.
For
information
about
backing
up
your
environment,
see
Installing
and
Configuring
Tivoli
Enterprise
Data
Warehouse,
Version
1,
Release
1,
Guide.
v
Take
all
Tivoli
Enterprise
Data
Warehouse
databases
offline.
The
fix
pack
installation
must
be
completed
on
all
systems
where
it
is
required
before
you
bring
the
databases
online.
When
you
finish
See
the
Warehouse
Enablement
Pack
Implementation
Guide
for
specific
post-installation
steps
you
must
perform.
Enable
data
logging
for
Tivoli
Enterprise
Data
Warehouse
as
described
in
the
user’s
guides
listed
below.
Refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
information
about
using
the
Tivoli
Enterprise
Data
Warehouse
reports.
Procedure
Use
the
following
steps
to
install
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
warehouse
enablement
pack
fix
pack:
1.
From
a
bash
shell,
run
$TWH_TOPDIR/install/bin/tedw_wpack_patchadm.sh
to
create
the
twh_app_patcher.cfg
configuration
file
in
the
directory
specified
by
the
TEMP
environment
variable.
2.
Edit
the
twh_app_patcher.cfg
configuration
file
to
complete
the
″USER
SUPPLIED
SECTION″
section:
############
USER
SUPPLIED
SECTION
#####################################
#
Edit
the
following
lines
with
the
information
specific
to
your
#
setup.
For
more
information
on
the
definition
of
each
of
these
tags,
#
please
look
at
the
template
config
file
(twh_core_patcher.cfg)
located
#
in
the
generic/install/bin
directory
of
this
patch.
#
APP_MEDIA_DIR=
PS_HOME=
DB2PASS=
COPT_CTRL_DB2PASS=
COPT_CDW_DB2PASS=
COPT_MART_DB2PASS=
#
############
AUTO-GENERATED
SECTION
####################################
where:
APP_MEDIA_DIR
Specifies
the
path
for
the
CD
directory
that
contains
the
twh_app_install_props.cfg
configuration
file.
For
this
fix
pack,
Chapter
7.
Completing
the
installation
of
the
product
95
APP_MEDIA_DIR
must
refer
to
the
path
on
the
CD
that
contains
the
/tedw_apps_etl/fixpack_v1102/izy/
directory.
PS_HOME
Specifies
the
directory
where
Tivoli
Presentation
Services
is
installed.
Set
this
value
on
systems
that
have
the
Tivoli
Enterprise
Data
Warehouse
Reporting
Interface
(RPI)
component
installed.
DB2PASS
Specifies
the
user
password
indicated
by
the
″DB2USER″
tag
in
the
″AUTO-GENERATED
SECTION,″
which
appears
immediately
below
the
″USER
SUPPLIEDSECTION.″
This
is
a
DB2
user
defined
for
the
current
system.
COPT_CTRL_DB2PASS
Specifies
the
user
password
indicated
by
the
″COPT_CTRL_DB2USER″
tag
in
the
″AUTO-GENERATED
SECTION.″
This
is
a
DB2
user
defined
for
the
system
where
the
Tivoli
Enterprise
Data
Warehouse
Control
Server
component
is
installed.
COPT_CDW_DB2PASS
Specifies
the
user
password
indicated
by
the
″COPT_CDW_DB2USER″
tag
in
the
″AUTO-GENERATED
SECTION.″
This
is
a
DB2
user
defined
for
the
system
where
the
Tivoli
Enterprise
Data
Warehouse
Central
Data
Warehouse
database
is
installed.
COPT_MART_DB2PASS
Specifies
the
user
password
indicated
by
the
″COPT_MART_DB2USER″
tag
in
the
″AUTO-GENERATED
SECTION.″
This
is
a
DB2
user
defined
for
the
system
where
the
Tivoli
Enterprise
Data
Warehouse
Data
Mart
database
is
installed.3.
From
a
bash
shell,
run
the
$TWH_TOPDIR/install/bin/tedw_wpack_patchadm.sh
script
again
to
complete
the
installation
of
the
fix
pack.
Installing
IBM
Tivoli
Language
Support
for
this
product
Objective
To
install
language
support
packages
is
to
enable
one
or
more
of
the
nine
available
national
language
versions
of
the
product.
Background
information
By
default,
IBM
Tivoli
Monitoring
for
Web
Infrastructure
is
enabled
in
English.
To
enable
other
languages,
install
the
appropriate
language
support
pack
from
one
of
the
Language
Support
installation
CDs
for
each
product
component.
You
can
install
multiple
language
support
packages
for
a
single
product.
Language
support
packages
exist
for
the
languages
listed
in
Table
29
on
page
97.
The
table
also
shows
product-name
prefixes
and
language-support
suffixes.
You
concatenate
a
prefix
and
a
suffix
to
form
the
name
of
the
.IND
file.
For
example,
the
following
.IND
files
contain
German
language
support
packages
for
different
components
of
IBM
Tivoli:
v
IZY_DE.IND
is
the
name
of
the
German
language
support
package
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
v
ITM_DE.IND
is
the
name
of
the
German
language
support
package
for
IBM
Tivoli
Monitoring.
96
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
29.
Language
support
and
names
of
corresponding
installation
index
(.IND)
files
Language
Prefix
for
Monitoring
for
Apache
HTTP
Server
Prefix
for
Monitoring
for
Internet
Information
Server
Prefix
for
Monitoring
for
iPlanet
Web
Server
Prefix
for
Monitoring
for
WebSphere
Application
Server
Prefix
for
Monitoring
for
WebLogic
Server
Prefix
for
IBM
Tivoli
Monitoring
Language
code
suffix
Brazilian
Portuguese
GWA
GWI
GWP
IZY
GWL
ITM
_PTBR
(Exception:
the
suffix
for
ITM
is
_PT_B)
Chinese
(simplified)
GWA
GWI
GWP
IZY
GWL
ITM
_ZHCH
(Exception:
the
suffix
for
ITM
is
_ZH_C)
Chinese
(traditional)
GWA
GWI
GWP
IZY
GWL
ITM
_ZHTW
(Exception:
the
suffix
for
ITM
is
_ZH_T)
French
GWA
GWI
GWP
IZY
GWL
ITM
_FR
German
GWA
GWI
GWP
IZY
GWL
ITM
_DE
Italian
GWA
GWI
GWP
IZY
GWL
ITM
_IT
Japanese
GWA
GWI
GWP
IZY
GWL
ITM
_JA
Korean
GWA
GWI
GWP
IZY
GWL
ITM
_KO
Spanish
GWA
GWI
GWP
IZY
GWL
ITM
_ES
Some
command
line
and
keyword
options
are
not
translated
in
the
language
support
packages.
This
approach
avoids
any
programming
complexities
for
scripts
that
can
run
under
multiple
locales.
Run
the
scripts
under
the
locale
in
which
the
retrieved
data
is
stored.
Tivoli
Management
Framework
also
uses
the
software
in
the
language
support
packages.
For
more
information,
see
the
following
documents
on
the
installation
CDs
for
Tivoli
Management
Framework:
v
Chapter
2
″Internationalization″
in
the
Tivoli
Enterprise
Installation
Guide
v
Release
Notes
Required
authorization
role
install_product
Before
you
begin
As
a
precautionary
measure,
back
up
the
Tivoli
management
region
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
Start
the
command
line
interface
or
Tivoli
desktop
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
Refer
to
the
Tivoli
Management
Framework
Reference
Manual
for
more
information
about
the
winstall
command.
Refer
to
“Tivoli
command
syntax”
on
page
xv
for
information
on
Tivoli
command
line
syntax.
Chapter
7.
Completing
the
installation
of
the
product
97
When
you
finish
If
you
manually
installed
the
Web
Health
Console,
see
“Installing
the
Web
Health
Console
manually”
on
page
110.
If
you
used
the
Typical
or
Evaluation
installation,
the
installer
enables
language
support
for
the
Web
Health
Console
automatically.
If
you
install
a
language
pack
after
you
create
one
or
more
objects,
the
message
catalog
files
are
not
automatically
updated
on
the
endpoints
for
those
objects.
To
update
the
message
catalogs
for
the
language
pack,
push
the
product
dependencies
to
the
endpoints.
Note:
To
update
the
message
catalogs
for
the
language
pack
for
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
component
software,
you
can
use
a
script
provided
on
the
product
CD
to
push
the
updated
files
to
an
endpoint.
The
script
takes
an
endpoint
name
as
an
argument.
The
name
of
the
script
and
its
location
are
as
follows:
$BINDIR/../generic_unix/TME/WSAPPSVR/tasks/
\
itmwas_push_dependencies.sh
Alternatively,
you
can
recreate
the
objects
that
you
created
before
installing
the
language
pack.
See
the
user’s
guides
for
each
component
for
more
information
on
creating
objects:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
User’s
Guide
Procedure
You
can
perform
this
procedure
from
the
Tivoli
desktop
or
from
the
command
line.
Command
line:
1.
Insert
the
language
CD
for
the
component
you
are
installing:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Language
Support
2.
Access
the
Tivoli
command
line
interface
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
3.
Type
bash
and
press
Enter
to
access
the
complete
libraries
of
Tivoli
commands.
4.
Run
the
following
command:
winstall
-c
/cdromdrive
-i
product
index
–y
where
cdromdrive
is
the
path
to
the
location
of
the
files
and
product
index
is
the
language
you
want
to
install,
such
as
IZY_DE.IND
for
the
German
version
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
98
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Additional
Information:
When
the
command
completes,
the
message
″Finished
Product
Installation″
is
displayed.
Refer
to
the
Tivoli
Management
Framework
Reference
Manual
for
more
information
about
the
winstall
command.
Refer
to
“Tivoli
command
syntax”
on
page
xv
for
information
on
Tivoli
command
line
syntax.
5.
Repeat
Step
4
to
install
additional
language
support
packages.
Tivoli
desktop:
1.
Insert
the
language
CD
for
the
component
you
are
installing:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Language
Support
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Server
Language
Support
2.
On
the
main
Tivoli
window,
click
Install
in
the
Desktop
menu.
3.
Click
Install
Product.
4.
If
necessary,
click
OK
to
bypass
a
harmless
error
message
about
the
media
settings.
5.
Click
Select
Media
to
display
the
File
Browser
window.
6.
In
the
Path
Name
text
field,
enter
the
full
path
to
the
language
support
files.
Be
sure
to
use
backward
slashes
(\)
for
Windows
path
names
instead
of
forward
slashes
(/).
7.
Click
Set
Path
to
refresh
the
view.
Additional
Information:
The
Directories
list
displays
directories
and
the
Files
list
displays
the
.IND
files
that
include
the
names
of
all
nine
languages.
8.
Click
Set
Media
&
Close
to
return
to
the
Install
Product
window.
9.
Select
the
language
that
you
want
to
install
in
the
Select
Product
to
Install
list.
For
example,
select
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2,
[de]
German
language
to
choose
German
language
support
for
installation.
10.
Select
the
target
endpoints
on
which
to
install
language
support
from
the
Available
Clients
list.
11.
Click
the
right
arrow
to
move
the
selected
clients
to
the
Clients
to
install
On
list.
12.
Click
Install
&
Close
to
launch
the
installation
progress
window.
13.
Click
Continue
Install
when
the
prompt
is
displayed.
14.
Click
Close
when
the
″Finished
Product
Installation″
message
is
displayed.
15.
Repeat
these
steps
to
install
another
language
support
package.
Updating
Web
Health
Console
files
Objective
To
update
the
Web
Health
Console
files
when
you
install
a
new
component
or
upgrade
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Chapter
7.
Completing
the
installation
of
the
product
99
Background
information
This
procedure
describes
how
to
update
the
class
files
for
the
Web
Health
Console
when
you
add
a
component
of
the
product.
The
class
files
specify
the
standard
text
that
the
console
displays.
Whenever
you
add
or
upgrade
components
for
your
installation
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
you
must
perform
this
procedure.
For
example,
if
you
upgrade
the
product
to
a
later
release,
you
must
update
the
class
files
located
on
the
computer
that
hosts
the
Web
Health
Console.
The
new
class
files
become
available
after
you
restart
the
Web
Application
Server
that
enables
the
console.
When
you
install
the
Web
Health
Console
for
the
first
time,
the
installer
automatically
installs
the
required
class
files
and
this
procedure
is
not
necessary.
When
you
install
the
product
without
using
the
installer,
use
the
procedure
“Installing
the
Web
Health
Console
manually”
on
page
110.
Required
authorization
role
Logon
privileges
for
the
computer
that
hosts
the
Web
Health
Console.
Before
you
begin
Obtain
the
following
CDs:
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
5.1.1
Component
Software
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
5.1.0
Component
Software
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
5.1.1
Component
Software
When
you
finish
Restart
the
console’s
Web
application
server
to
make
the
new
class
files
available.
Procedure
You
can
perform
this
procedure
from
the
command
line
only.
Command
line:
1.
Copy
the
contents
of
the
HCONSOLE
directory
of
catalog
files
from
one
of
the
following
installation
CDs:
v
For
the
English
language
updates
to
IBM
Tivoli
Monitoring,
copy
catalog
files
from
the
IBM
Tivoli
Monitoring
V5.1.1
installation
CD.
v
For
the
English
language
updates
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
copy
catalog
files
from
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installation
CDs
that
are
labeled
″Component
Software.″
v
For
other
languages,
copy
catalog
files
from
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Language
Support
installation
CDs.2.
Insert
the
contents
of
the
HCONSOLE
directory
in
the
following
resources
directory
on
the
target
computer
that
hosts
the
Web
Health
Console:
INSTALL_DIR/installedApps/dm.ear/dm.war/WEB-INF/classes/com/tivoli/
\
DmForNt/resources
100
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
8.
Expanding
your
Tivoli
environment
Before
or
after
you
install
the
product,
either
by
using
the
installer
or
by
performing
manual
installations,
you
might
want
to
add
managed
nodes,
endpoints,
or
installations
of
the
IBM
Tivoli
Monitoring
Web
Health
Console
to
your
Tivoli
environment.
This
chapter
describes
how
to
add
managed
nodes,
endpoints,
or
installations
of
the
Web
Health
Console
without
using
the
installer.
The
following
examples
describe
situations
that
require
expansion
of
your
Tivoli
environment:
v
After
using
the
installer
to
set
up
your
initial
configuration,
you
manually
installed
IBM
Tivoli
Monitoring
for
Web
Infrastructure
component
software
on
additional
servers
that
are
not
Tivoli
endpoints.
You
need
to
install
the
Tivoli
endpoint
software
on
these
computers
before
you
can
use
the
product
to
manage
applications.
v
Your
management
environment
has
expanded
so
you
want
to
add
Tivoli
managed
nodes
and
gateways.
You
decide
to
add
the
managed
nodes
and
gateways
from
the
Tivoli
command
line
or
desktop
before
installing
all
the
necessary
software
(including
IBM
Tivoli
Monitoring
for
Web
Infrastructure
on
some
or
all
of
the
additional
computers).
v
The
monitoring
staff
at
your
company
has
grown
and
they
need
access
to
the
IBM
Tivoli
Monitoring
Web
Health
Console
to
observe
real-time
status
of
managed
resources.
You
need
to
install
the
Web
Health
Console
on
additional
machines
and
then
install
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
software
on
these
machines.
Table
30
summarizes
the
procedures
for
adding
managed
nodes,
endpoints,
and
installations
of
the
Web
Health
Console
to
your
Tivoli
environment.
Table
30.
Guidelines
for
expanding
your
Tivoli
environment
Goal
Refer
to
Access
the
Tivoli
environment
as
the
first
step
for
performing
any
of
the
procedures
described
in
this
chapter.
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73
Install
managed
nodes
to
assist
the
Tivoli
server
with
management
and
monitoring
operations.
“Installing
managed
nodes
through
an
existing
Tivoli
environment”
on
page
101
Install
endpoint
software
to
enable
target
computers
to
communicate
in
the
Tivoli
environment.
“Installing
endpoints
through
an
existing
Tivoli
environment”
on
page
105
(Optional)
Change
the
gateway
assignment
for
an
endpoint.
“Changing
the
gateway
assignment
of
an
endpoint”
on
page
109
Install
the
IBM
Tivoli
Monitoring
Web
Health
Console
on
computers
to
display
real-time
status
of
managed
resources.
“Installing
the
Web
Health
Console
manually”
on
page
110
See
the
IBM
Tivoli
Monitoring
User’s
Guide
for
information
about
using
the
Web
Health
Console.
Installing
managed
nodes
through
an
existing
Tivoli
environment
Objective
To
install
managed
nodes
using
an
existing
Tivoli
user
interface.
©
Copyright
IBM
Corp.
2003
101
Background
information
This
procedure
enables
you
to
install
and
set
up
managed
nodes
without
using
the
Typical
or
Evaluation
installation
options
in
the
installer.
This
procedure
uses
the
default
settings
for
a
managed
node.
See
the
Tivoli
Enterprise
Installation
Guide
to
learn
how
to
override
the
defaults.
Required
authorization
role
super
or
install_client
Before
you
begin
As
a
precautionary
measure,
back
up
the
Tivoli
management
region
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
Start
the
command
line
interface
or
Tivoli
desktop
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
If
you
have
a
UNIX
Tivoli
management
region
server
and
you
want
to
create
Windows
managed
nodes,
you
need
to
install
the
Tivoli
Remote
Execution
Service
(TRIP)
process
on
the
Windows
system.
This
does
not
apply
to
Windows
Tivoli
management
region
server.
When
you
finish
None
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wclient
command
to
create
a
managed
node.
wclient
-c
<CD_path>
-d
-p
<policy_region>
<managed_node>
where
-c
<CD_path>
Specifies
the
path
to
the
Tivoli
Management
Framework
installation
CD.
–d
Sets
installation
variables
to
their
last
set
values.
Commonly,
each
installed
managed
node
uses
the
same
set
of
installation
variables.
This
option
provides
a
shortcut
for
setting
the
variables.
In
this
case,
the
managed
node
obtains
settings
for
the
installation
variables
from
the
Tivoli
server.
–p
<policy_region>
Specifies
the
policy
region
with
which
the
managed
node
will
be
associated.
<managed_node>
Specifies
the
host
name
of
the
new
managed
node.
After
creating
a
managed
node
on
a
Windows
NT
or
Windows
2000
system,
you
must
reboot
the
system
to
complete
the
installation.
Each
managed
node
must
have
a
gateway
to
enable
communication
with
endpoints.
Use
the
wcrtgate
command
to
create
a
gateway
on
the
managed
node.
The
following
command
creates
a
gateway
on
managed
node
everest
using
the
default
settings:
wcrtgate
-h
everest
102
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
After
creating
the
gateway,
you
can
configure
its
behavior
as
a
repeater
and
as
a
vehicle
for
software
distribution
using
the
wrpt
and
wmdist
commands.
For
additional
information
on
these
commands
see
the
Tivoli
Management
Framework
Reference
Manual.
See
“Tivoli
command
syntax”
on
page
xv
for
information
on
Tivoli
command
line
syntax.
Tivoli
desktop:
1.
From
the
Tivoli
desktop,
open
the
policy
region
where
you
want
to
create
the
managed
node.
2.
From
the
Create
menu,
click
Managed
Node
to
display
the
Client
Install
window.
Additional
Information:
The
managed
node
is
created
in
the
current
policy
region.
See
the
Tivoli
Enterprise
Installation
Guide
to
learn
about
creating
managed
nodes
in
other
policy
regions.
3.
In
the
TMR
Installation
Password
field,
type
the
installation
password.
Additional
Information:
If
a
password
was
not
specified
when
the
Tivoli
management
region
server
was
created,
leave
this
field
empty.
If
a
password
was
specified,
you
must
use
this
password
for
each
managed
node.
4.
Select
the
radio
button
in
the
Default
Access
Method
area
to
indicate
how
the
Tivoli
management
region
contacts
each
system:
v
Account—In
the
Account
field,
type
the
name
and
password
of
the
privileged
user
to
contact
the
system.
In
the
Password
field,
type
the
password
for
this
user.
This
option
applies
to
UNIX,
Windows
NT,
and
Windows
2000
systems.
v
Trusted
Host—(UNIX
only)
For
trusted
host
access,
the
/.rhost
file
on
each
system
must
grant
access
to
the
system
performing
the
installation
by
adding
an
entry
for
root@hostname,
where
hostname
is
the
host
name
of
the
Tivoli
management
region
server
or
managed
node
performing
the
installation.
Note:
You
can
override
the
access
method
when
you
add
a
single
system,
load
systems
from
a
file,
or
after
the
systems
are
added
to
the
list.
5.
Click
Add
Clients.
6.
Configure
the
client
as
follows:
a.
In
the
Add
Client
field,
type
the
name
of
the
system
you
want
to
configure
as
a
managed
node.
b.
Specify
the
access
method
that
the
Tivoli
management
region
server
uses
to
contact
the
system:
v
Select
Use
Default
Access
Method
to
use
the
default
access
method
that
you
specified
in
Step
4.
—OR—
v
Select
Account
to
use
account
access.
—OR—
v
Select
Trusted
Host
Access
to
use
trusted
host
access
in
UNIX.c.
Click
Add
&
Close
to
add
the
system
to
the
list
and
return
to
the
Client
Install
window.7.
Repeat
Steps
5
and
6
for
each
computer
that
you
want
to
configure
as
a
managed
node.
8.
If
you
need
to
change
the
access
method
for
any
of
the
listed
systems,
perform
the
following
steps
in
the
Client
Install
window:
a.
Select
the
system
to
change.
Chapter
8.
Expanding
your
Tivoli
environment
103
b.
Click
Access
Method.
c.
Select
the
access
method
you
want.
d.
Click
Set
to
return
to
the
Client
Install
window.9.
Click
Select
Media
to
display
the
File
Browser
window
in
which
you
specify
the
path
to
the
directory
that
contains
the
installation
images.
10.
Use
the
File
Browser
window
to
navigate
to
the
correct
file.
11.
Click
Set
Media
&
Close
to
save
your
setting
and
display
the
Install
Options
window
Additional
Information:
See
the
Tivoli
Management
Framework
User’s
Guide
for
instructions
on
how
to
use
the
File
Browser
window.
Note:
Normally,
you
use
same
installation
image
to
create
the
Tivoli
management
region
server
and
managed
nodes.
12.
Modify
the
installation
options,
if
necessary.
Additional
Information:
The
options
in
this
window
apply
to
all
listed
systems.
For
details
on
the
fields
available
in
this
window,
see
the
online
help.
13.
Click
Set
to
save
your
changes
and
return
to
the
Client
Install
window.
14.
Click
Install
&
Close
to
start
the
installation
of
the
managed
node.
Additional
Information:
A
new
Client
Install
window
is
displayed.
This
window
lists
operations
that
will
take
place
during
the
installation
and
any
problems
that
you
might
want
to
correct
before
continuing
the
installation.
15.
Click
Continue
Install.
16.
(Windows
only)
Perform
the
following
steps
in
the
Tivoli
Remote
Access
Account
window
that
is
displayed:
a.
Select
one
of
the
following
radio
buttons:
v
Account—Defines
an
account
other
than
the
default
access
account.
v
None—Specifies
that
there
is
no
Tivoli
remote
access
account.
If
reinstalling
and
there
is
a
previous
Tivoli
remote
access
account,
this
option
does
not
overwrite
the
original
account.
v
Use
Installation
’Access
Method’
Account—Specifies
that
Tivoli
remote
access
account
is
the
default
access
account.
This
selection
grants
the
full
rights
that
the
default
access
account
has.
For
more
information
about
Tivoli
remote
access
account,
see
the
Tivoli
Enterprise
Installation
Guide.
b.
Click
Continue.
Additional
Information:The
Client
Install
window
returns
and
displays
information
on
the
progress
of
installation.
c.
Windows
only:
Click
OK
in
the
Confirm
Reboot
of
Clients
prompt
to
reboot
these
systems.
Additional
Information:
You
can
click
Close
and
restart
the
computer
later,
if
necessary.
The
managed
node
is
enabled
only
after
you
restart.17.
Click
Close
when
the
Client
Install
window
displays
the
Finished
client
install
message
18.
Click
Refresh
in
the
View
menu
to
display
the
icon
of
the
managed
nodes
you
created
and
verify
success
of
this
procedure.
19.
(Windows
only)
Configure
Simple
Transfer
Protocol
(SMTP)
as
follows.
This
protocol
enables
Tivoli
to
generate
for
alerts
and
other
messages:
a.
Access
the
Tivoli
command
line
environment
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
104
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
b.
Enter
the
following
command:
wmailhost
hostname
where
hostname
is
the
name
of
the
network
server.
For
additional
information,
see
the
Tivoli
Enterprise
Installation
Guide.20.
Install
gateway
software
on
the
managed
node
as
follows:
a.
In
the
main
Tivoli
desktop
window,
right-click
EndpointManager
and
select
Create
Gateway
to
access
the
Create
Gateway
window.
b.
In
the
Name
field,
type
a
unique
name
for
the
gateway.
It
is
recommended
to
use
<host
name>_gw
to
distinguish
this
gateway
from
other
gateways
and
endpoints.
For
example,
if
the
host
name
of
the
managed
node
is
vision35,
name
the
gateway
vision35_gw.
c.
In
the
Port
field,
type
the
port
number
through
which
the
gateway
will
communicate
with
its
endpoints
in
TCP/IP.
d.
In
the
Managed
Node
Proxy
field,
type
the
name
of
the
managed
node
on
which
the
gateway
will
run.
You
can
also
click
Managed
Nodes
to
list
the
available
managed
nodes
and
select
from
the
list.
e.
Click
Create
&
Close.
Installing
endpoints
through
an
existing
Tivoli
environment
Objective
To
install
and
configure
the
endpoint
software
on
an
endpoint
using
the
Tivoli
desktop
or
command
line
interface.
This
procedure
does
not
apply
to
the
creation
of
endpoints
on
proxy
mode
z/OS
or
OS/400
systems.
Refer
to
the
chapters
listed
in
Table
31
for
information
about
installing
and
configuring
endpoints
on
these
systems.
Table
31.
Guidelines
for
installing
the
product
through
an
existing
Tivoli
environment
Goal
Refer
to
Install
endpoints
for
IBM
WebSphere
Application
Server
systems
running
on
proxy
mode
z/OS
systems.
Chapter
11,
“Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems,”
on
page
129
Install
OS/400
endpoints
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Chapter
10,
“Setting
up
OS/400
endpoints
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,”
on
page
119
Background
information
Creation
of
endpoints
during
installation
of
the
product
is
optional.
This
procedure
describes
how
to
create
endpoints
after
you
have
installed
the
product.
You
must
install
the
endpoint
software
on
an
IBM
Tivoli
Monitoring
for
Web
Infrastructure
endpoint
to
enable
communication
with
the
Tivoli
server.
You
perform
this
procedure
from
the
Tivoli
server.
Note:
If
you
have
a
UNIX
Tivoli
management
region
server
and
you
want
to
create
Windows
endpoints,
the
first
endpoint
you
create
must
be
on
the
actual
endpoint
system.
Chapter
8.
Expanding
your
Tivoli
environment
105
You
can
perform
this
procedure
in
the
Endpoint
Setup
Wizard
or
in
the
command
line
interface.
You
must
provide
configuration
values
that
match
the
requirements
of
specific
operating
systems
as
follows:
v
For
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
hosts
that
reside
on
UNIX
machines,
you
must
provide
the
root
user
ID
and
password
of
the
host
machine
to
install
the
endpoint
software,
as
described
in
this
procedure.
v
For
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
hosts
that
reside
on
Windows
machines,
you
must
have
at
least
one
proxy
endpoint
in
each
Windows
domain
that
contains
servers
that
you
want
to
manage.
At
the
end
of
this
procedure
the
endpoint
is
running
on
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
host.
Required
authorization
role
admin
Before
you
begin
(Optional)
Use
the
Planning
sheet
for
creating
endpoints
in
Table
13
on
page
38
to
prepare
to
perform
this
procedure
for
multiple
IBM
Tivoli
Monitoring
for
Web
Infrastructure
endpoints.
When
you
finish
Perform
the
following
steps
on
any
endpoints
that
you
installed.
The
command
starts
the
monitoring
engine
so
that
you
can
distribute
and
run
resource
models:
1.
Access
the
command
line
interface
for
the
Tivoli
environment
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
2.
Run
the
following
command:
wdmcmd
-restart
-e
<endpoint_label>
where
<endpoint_label>
is
the
name
of
the
endpoint.
Procedure
This
procedure
describes
installation
of
endpoints
from
the
command
line
or
using
the
Endpoint
Setup
Wizard
in
Windows.
You
can
use
the
Endpoint
Setup
Wizard
to
install
an
endpoint
on
a
local
Windows
system.
Endpoint
Setup
Wizard
(for
Windows
only):
1.
Insert
the
Tivoli
Management
Framework,
Version
4.1
CD
into
the
CD-ROM
drive
of
the
endpoint
computer.
2.
Run
the
setup
executable
located
in
the
following
subdirectory
path:
\pc\lcf\winnt
3.
Click
Next
in
the
Tivoli
Management
Framework
Endpoint
Setup
window.
4.
Read
the
license
agreement.
5.
Click
Next
to
display
the
Endpoint
Installation
Options
window.
6.
(Optional)
Click
Browse
to
change
the
destination
directory
for
the
software.
7.
Click
Next
to
display
the
Tivoli
Remote
Access
Account
window.
8.
Type
the
user
name
and
password
of
the
account
through
which
Tivoli
Management
Framework
accesses
remote
file
systems.
If
you
do
not
require
access
to
remote
domains,
click
Next
to
skip
this
step.
9.
Click
Next
to
access
the
Advanced
Configuration
window.
10.
Specify
the
startup
and
configuration
options
information
listed
in
the
following
table:
106
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Field
Name
Use
When
...
Gateway
The
gateway
uses
a
port
number
other
than
the
default
9494.
Endpoint
You
want
to
specify
a
port
for
the
endpoint
to
use.
The
default
is
9495.
Other
Use
the
–g
<hostname>
option
to
specify
the
intercepting
gateway.
Use
the
–n
<hostname
of
the
endpoint>
option
to
specify
the
name
of
the
endpoint
you
are
installing.
11.
Click
Next
to
continue
the
installation
process.
Additional
Information:
The
wizard
reports
that
communication
of
the
endpoint
and
the
gateway
was
successful.
The
endpoint
is
installed
and
logged
into
a
gateway.
The
installation
process
configures
the
endpoint
system
to
automatically
start
the
endpoint
service
when
the
system
starts.
If
the
system
does
not
start,
there
might
be
a
problem
with
the
communication
between
the
endpoint
and
the
gateway.
Remove
and
then
reinstall
the
endpoint.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Problem
Determination
Guide
for
information
on
how
to
remove
an
endpoint.
12.
Click
Next
to
display
the
Setup
Complete
window.
13.
Click
Finish
to
display
the
Restart
Windows
window.
14.
Select
No.
Additional
Information:
You
can
restart
the
system
after
the
installation
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure
is
complete.
When
you
restart
the
computer
the
Tivoli
Endpoint
service
is
created,
with
the
startup
type
set
to
automatic.
Command
line:
Use
the
winstlcf
command
to
install
an
endpoint
from
the
command
line.
This
command
enables
you
to
remotely
install
endpoints
on
UNIX,
Windows
NT,
and
Windows
2000
systems.
Partial
CLI
syntax
for
the
winstlcf
command
is
included
in
the
following
section.
See
the
Tivoli
Management
Framework
Reference
Manual
for
a
complete
description
of
the
winstlcf
command.
Notes:
1.
For
Windows
systems,
in
the
–N
parameter,
you
must
use
the
endpoint
you
created
with
the
Endpoint
Setup
Wizard
to
create
more
Windows
endpoints
for
a
UNIX
Tivoli
management
region.
See
“Endpoint
Setup
Wizard
(for
Windows
only)”
on
page
106
for
more
information.
2.
The
installation
password
that
you
specify
with
the
winstlcf
command
becomes
the
default
for
all
subsequent
installations
(unless
you
specify
a
different
password
with
the
–P
parameter).
winstlcf
[–C
<locale_name>]
[–d
<dir_name>]
[–f
<file_name>]
[–g
<machine[+port]>]
[–L
<config_options>]
[–l
<ep_port>]
[–N
<endpoint>]
[–n
<ep_label>]
[–P
]
[–Y
]
<host>
[<user_acct>
<password>]
where:
–C
<locale_name>
(UNIX
only)
Specifies
the
language
locale
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
endpoints
that
use
the
UNIX
operating
system.
–d
<dir_name>
Specifies
the
target
directory
on
which
to
install
the
endpoint.
The
default
Chapter
8.
Expanding
your
Tivoli
environment
107
location
is
/opt/Tivoli/lcf
for
UNIX
and
C:\Tivoli\lcf
for
Windows
NT
and
Windows
2000.
When
installing
a
Windows
NT
or
Windows
2000
endpoint
from
a
UNIX
server,
forward
slashes
in
path
names
are
also
supported.
–f
<file_name>
Specifies
the
file
containing
a
list
of
systems
on
which
to
install
endpoints.
This
file
contains
one
system
name
per
line,
specifying
the
user
ID
and
password
to
be
used.
Use
the
following
format
for
each
line
in
this
file:
host_name
[
userID
[
password]]
–g
<machine[+port]>
Specifies
the
Internet
Protocol
(IP)
address
or
host
name
and,
optionally,
the
port
number
of
the
gateway
to
which
the
endpoint
logs
in.
–L
<config_options>
Passes
configuration
options
to
the
lcfd
command
for
starting
the
endpoint.
See
the
lcfd
command
in
the
Tivoli
Management
Framework
Reference
Manual
for
a
list
of
valid
options.
The
example
in
this
section
shows
how
to
specify
options.
If
you
specify
multiple
options
or
have
spaces
in
a
single
option,
you
must
enclose
the
text
in
double
quotation
marks
(″).
–l
<ep_port>
Specifies
the
port
number
for
the
endpoint.
The
default
port
number
is
9495.
–N
<endpoint>
(for
Windows
only)
Specifies
the
reference
endpoint
from
which
you
install
other
endpoints
in
a
Windows
domain.
In
IBM
Tivoli
Monitoring
for
Web
Infrastructure
specify
one
of
the
following
values
for
the
<endpoint>
in
the
Windows
domain
where
you
are
installing
the
endpoint:
v
For
Windows
server
endpoints
in
the
domain
of
the
Tivoli
server,
specify
the
hostname
for
the
proxy
endpoint
(such
as
%HOST%_ep).
v
For
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
endpoints
in
a
domain
other
than
the
domain
of
the
Tivoli
server,
specify
the
name
of
the
reference
endpoint
that
you
manually
create,
as
described
in
“Endpoint
Setup
Wizard
(for
Windows
only)”
on
page
106.
–n
Specifies
an
endpoint
label
provided
by
a
user.
If
you
do
not
assign
a
name,
the
command
generates
a
unique
name
automatically.
Note:
This
label
must
be
different
than
the
one
used
for
the
managed
node.
–P
This
option
is
useful
only
when
you
are
installing
on
remote
hosts
with
different
passwords.
If
each
machine
has
the
same
password
or
if
you
do
not
use
the
–P
option,
you
are
prompted
for
a
global
password
to
use
for
each
machine.
–Y
Specifies
that
the
installation
proceeds
without
confirmation.
By
default,
this
command
identifies
the
actions
that
you
must
take
to
perform
the
installation
and
requests
confirmation
before
continuing.
When
you
use
the
-Y
option,
the
winstlcf
command
identifies
the
actions
and
performs
the
installation
without
requesting
confirmation.
<host>
[<user_acct>
<password>]
Specifies
the
name
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
host
on
which
to
install
the
endpoint.
When
you
specify
only
the
host
name,
the
winstlcf
command
uses
the
root
or
Administrator
account
108
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
and
prompts
you
for
the
password.
If
you
want
to
specify
a
different
account
and
password
on
the
host,
enclose
the
host
name,
account
name,
and
password
in
single
quotation
marks.
For
example,
the
following
command
installs
the
endpoint
on
the
host
vernon,
using
the
DOMAIN-NT\chris
account
with
the
password
pa55word:
winstlcf
’vernon
DOMAIN-NT\chris
pa55word’
where
DOMAIN-NT
is
the
domain
in
which
chris
is
located.
When
the
Windows
NT
or
Windows
2000
domain
and
the
local
computer
use
the
same
name
for
user_acct,
you
must
provide
the
fully
qualified
name
for
the
account.
For
example,
if
you
want
to
specify
a
user
account
named
Administrator
in
a
domain
called
DOMAIN-NT,
you
must
use
the
fully
qualified
name
DOMAIN-NT\Administrator
for
the
variable
user_acct.
Examples:
v
The
following
example
installs
and
starts
the
endpoint
software
on
a
UNIX
workstation
named
vernon.
The
–C
fr
statement
specifies
that
the
endpoint
process
uses
the
French
locale.
By
default,
winstlcf
uses
the
root
account
and
prompts
you
for
the
root
password
on
vernon.
winstlcf
-C
fr
vernon
v
The
following
example
installs
the
endpoint
on
a
machine
named
cedar
and
prompts
you
for
a
password.
The
password
you
enter
becomes
the
default
password
for
all
subsequent
installations.
winstlcf
-P
cedar
v
In
the
following
example,
the
winstlcf
command
installs
the
endpoint
on
an
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
host
named
server06
in
the
domain
mycompany.com.
The
winstlcf
command
passes
configuration
options
to
the
lcfd
command
to
use
when
it
starts
the
endpoint.
The
command
assigns
port
9131
for
endpoint
transactions.
The
–g
option
specifies
the
gateway
cedar
and
the
port
1616
as
the
gateway
to
contact
for
initial
login.
The
–L
flag
specifies
options
for
the
–D
flag
of
the
lcfd
command.
The
–D
lcs.machine_name
flag
assigns
the
name
server06_ep
to
the
endpoint.
winstlcf
-g
cedar+1616
-l
9131
-L
"-D
lcs.machine_name=server06_ep"
server06.mycompany.com
Changing
the
gateway
assignment
of
an
endpoint
Objective
To
assign
an
endpoint
to
a
different
gateway
on
a
managed
node.
Background
information
An
endpoint
communicates
with
the
Tivoli
management
region
through
gateway
software
that
exists
on
a
managed
node.
By
default,
the
installer
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
assigns
each
endpoint
to
a
gateway
on
a
managed
node
whenever
possible.
This
configuration
increases
performance
in
the
Tivoli
environment
by
reducing
traffic
on
the
Tivoli
management
region
server.
In
a
typical
configuration
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
the
Tivoli
management
region
server
administers
a
set
of
managed
nodes.
In
turn,
the
managed
nodes
administer
endpoints.
If
you
use
the
Tivoli
management
region
server
to
administer
endpoints,
you
decrease
the
amount
of
system
resources
available
for
the
administration
of
managed
nodes
and
other
operations.
If
you
want
the
Tivoli
management
region
to
administer
endpoints,
you
can
change
the
gateway
assignment
as
described
in
this
procedure.
Chapter
8.
Expanding
your
Tivoli
environment
109
Required
authorization
role
senior
Before
you
begin
Prepare
the
following
information:
v
List
of
endpoints
that
you
want
to
reassign
v
List
of
gateways
that
will
host
the
reassigned
endpoints
(You
can
run
the
wgateway
command
to
view
gateway
assignments.)
v
A
plan
for
the
new
mapping
of
endpoints-to-gateways
When
you
finish
None
Procedure
You
can
perform
this
procedure
from
the
command
line.
Command
line:
1.
Access
the
Tivoli
command
line
interface
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
2.
Run
the
following
command:
wep
<endpoint>
migrate
<gateway>
where
<endpoint>
is
the
name
of
the
endpoint
to
migrate
and
<gateway>
is
the
name
of
the
new
gateway
assignment.
Additional
Information:
When
you
reassign
an
endpoint
to
a
new
gateway,
IBM
Tivoli
Monitoring
for
Web
Infrastructure
must
be
installed
in
the
managed
node
that
hosts
that
gateway.
Keep
in
mind
that
gateway
assignments
are
not
permanent
in
the
Tivoli
environment.
The
Tivoli
server
might
change
gateway
assignments
during
a
recovery
operation.
Installing
the
Web
Health
Console
manually
Objective
To
install
the
Web
Health
Console
using
a
command
line
interface.
Background
information
This
procedure
enables
you
to
install
and
set
up
the
Web
Health
Console
without
using
the
Typical
or
Evaluation
installation
options
in
the
installer.
Required
authorization
role
Log
on
privileges
for
the
target
computer.
Before
you
begin
None
When
you
finish
See
the
IBM
Tivoli
Monitoring
User’s
Guide
for
information
on
using
the
console.
Procedure
You
can
perform
this
procedure
from
the
command
line
only.
Command
line:
110
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
1.
Copy
the
contents
of
the
HCONSOLE
directory
of
catalog
files
from
one
of
the
following
installation
CDs:
v
For
the
English
language
updates
to
IBM
Tivoli
Monitoring,
copy
catalog
files
from
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
Installation
Disk
2.
v
For
other
languages,
copy
catalog
files
from
the
appropriate
CD:
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Apache
HTTP
Server
Language
Support
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
Internet
Information
Server
Language
Support
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
iPlanet
Web
Server
Language
Support
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
Language
Support
–
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.0:
WebLogic
Server
Language
Support
2.
Paste
the
contents
of
the
directory
in
the
INSTALL_DIR/installedApps/dm.ear/dm.war/WEB-INF/classes/com/tivoli/
DmForNt/resources
directory
on
the
target
computer,
where
INSTALL_DIR
is
the
directory
where
the
product
is
installed.
3.
Run
the
following
setup
executable
to
launch
the
installation
wizard:
v
On
UNIX:
./setupPLATFORM.bin
where
PLATFORM
is
the
name
of
the
operating
system.
v
On
Windows:
setup.exe4.
Follow
the
instructions
in
the
wizard
panels.
Additional
Information:
See
the
IBM
Tivoli
Monitoring
User’s
Guide
for
more
information.
Chapter
8.
Expanding
your
Tivoli
environment
111
112
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
9.
Migrating
from
previous
versions
of
this
product
This
chapter
provides
information
you
need
when
you
decide
to
upgrade
from
a
previous
version
of
one
of
the
product
components
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
The
following
topics
are
discussed:
v
“Migrating
from
Tivoli
Web
Component
Manager
to
IBM
Tivoli
Monitoring”
v
“Migrating
from
Tivoli
Manager
for
WebSphere
Application
Server”
on
page
115
Migrating
from
Tivoli
Web
Component
Manager
to
IBM
Tivoli
Monitoring
IBM
Tivoli
Monitoring
provides
a
tool
named
Tims2XML
to
facilitate
the
migration
of
Tivoli
Web
Component
Manager
users
to
Tivoli
Monitoring.
Tims2XML
is
a
Java
application
that
parses
the
database
on
the
Tivoli
Web
Component
Manager
server
(also
referred
to
as
TIMS
server)
and
retrieves
information
about
all
the
Tivoli
Web
Component
Manager
tasks
that
have
been
configured.
After
the
data
are
collected,
they
are
automatically
formatted
into
XML.
IBM
Tivoli
Monitoring
for
Web
Infrastructure
uses
the
information
formatted
in
the
XML
file
to
map
the
Tivoli
Web
Component
Manager
tasks
with
the
Tivoli
Monitoring
for
Web
Infrastructure
resource
models.
Refer
to
the
following
sections
for
a
description
of
how
to
map
the
tasks
with
the
resource
models.
Tims2XML
is
available
on
the
IBM
Tivoli
Monitoring,
Version
5.1.1
CD.
For
more
information
about
how
to
use
Tims2XML,
refer
to
the
IBM
Tivoli
Monitoring
User’s
Guide.
Mapping
Tivoli
Web
Component
Manager
tasks
and
Apache
HTTP
Server
resource
models
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
collects
the
same
metrics
that
are
collected
by
Tivoli
Web
Component
Manager
tasks
by
running
resource
models.
With
a
Tivoli
Web
Component
Manager
task
you
can
choose
the
metrics
to
collect,
but
an
Apache
HTTP
Server
resource
model
monitors
the
overall
status
of
an
Apache
HTTP
Server
resource
and
collects
a
set
of
metrics.
Typically,
a
resource
model
defines
one
or
more
thresholds
with
a
value
that,
if
exceeded
or
not
reached,
determines
the
generation
of
an
event.
Events
are
sent
to
Tivoli
Enterprise
Console
or
Tivoli
Business
Systems
Manager
to
notify
the
persistence
of
an
indication.
Table
32
on
page
114
shows
the
Tivoli
Web
Component
Manager
tasks
and
their
corresponding
Apache
HTTP
Server
resource
models.
It
also
indicates
whether
a
metric
has
an
associated
threshold.
©
Copyright
IBM
Corp.
2003
113
Table
32.
Apache
HTTP
Server
resource
models
corresponding
to
Tivoli
Web
Component
Manager
tasks
Tivoli
Web
Component
Manager
task
Apache
HTTP
Server
resource
model
Associated
threshold
WebServerStatus
Web
Site
Availability
Yes
HitCount
Performance
Not
applicable
FailedPages
Performance
Not
applicable
ServerFailureCount
Performance
Not
applicable
RequestsPerSec
Performance
Yes
KBytesPerSec
Performance
Yes
After
running
a
resource
model,
the
collected
data
can
be
viewed
in
real
time
by
using
the
IBM
Tivoli
Monitoring
Web
Health
Console.
Historical
data
are
logged
into
the
central
data
warehouse.
For
more
information
about
how
to
use
the
Web
Health
Console,
refer
to
the
IBM
Tivoli
Monitoring
User’s
Guide.
For
more
information
about
how
to
upload
data
to
the
central
data
warehouse,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide.
For
a
more
detailed
description
of
the
resource
models
provided
with
the
product,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide.
Mapping
Tivoli
Web
Component
Manager
tasks
and
Internet
Information
Server
resource
models
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
collects
the
metrics
that
are
collected
by
Tivoli
Web
Component
Manager
tasks,
by
running
resource
models.
The
only
metrics
that
are
not
currently
supported
by
a
corresponding
Internet
Information
Server
resource
model
are
ServerFailuresCount
and
CurrentSessionsASP.
With
a
Tivoli
Web
Component
Manager
task
you
can
specify
which
metrics
to
collect,
but
an
Internet
Information
Server
resource
model
monitors
the
overall
status
of
an
Internet
Information
Server
resource
and
collects
a
set
of
metrics.
Typically,
a
resource
model
defines
one
or
more
thresholds
with
a
value
that,
if
exceeded
or
not
reached,
determines
the
generation
of
an
event.
Events
are
sent
to
Tivoli
Enterprise
Console
or
Tivoli
Business
Systems
Manager
to
notify
the
persistence
of
an
indication.
Table
33
on
page
114
shows
the
Tivoli
Web
Component
Manager
tasks
and
their
corresponding
Internet
Information
Server
resource
models.
It
also
indicates
whether
a
metric
has
an
associated
threshold.
Table
33.
Internet
Information
Server
resource
models
corresponding
to
Tivoli
Web
Component
Manager
tasks
Tivoli
Web
Component
Manager
task
Internet
Information
Server
resource
model
Associated
threshold
WebServerStatus
Web
Site
Availability
Yes
HitCount
Web
Site
Performance
Not
applicable
FailedPages
Web
Site
Performance
Not
applicable
RequestsPerSec
Web
Site
Performance
Not
applicable
BytesSentPerSec
Web
Site
Performance
Yes
114
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
33.
Internet
Information
Server
resource
models
corresponding
to
Tivoli
Web
Component
Manager
tasks
(continued)
Tivoli
Web
Component
Manager
task
Internet
Information
Server
resource
model
Associated
threshold
BytesReceivedPerSec
Web
Site
Performance
Yes
TotalRequestsASP
ASP
Performance
Not
applicable
RequestsFailedASP
ASP
Performance
Not
applicable
RequestsNotFoundASP
ASP
Performance
Not
applicable
ErrorsPerSecASP
ASP
Performance
Yes
RequestsExecutingASP
ASP
Performance
Not
applicable
RequestsQueuedASP
ASP
Performance
Yes
After
running
a
resource
model,
the
collected
data
can
be
viewed
in
real
time
by
using
the
IBM
Tivoli
Monitoring
Web
Health
Console.
Historical
data
are
logged
into
the
central
data
warehouse.
For
more
information
about
how
to
use
the
Web
Health
Console,
refer
to
the
IBM
Tivoli
Monitoring
User’s
Guide.
For
more
information
about
how
to
upload
data
to
the
central
data
warehouse,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Internet
Information
Server
User’s
Guide.
For
a
more
detailed
description
of
the
resource
models
provided
with
the
product,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide.
Migrating
from
Tivoli
Manager
for
WebSphere
Application
Server
Because
of
the
new
architecture
used
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
you
cannot
migrate
all
of
the
functionality
that
was
included
in
the
previous
Tivoli
product.
However,
IBM
Tivoli
Monitoring
for
Web
Infrastructure
is
compatible
with
the
Tivoli
Manager
for
WebSphere
Application
Server
product.
You
can
continue
to
run
the
Tivoli
Manager
for
WebSphere
Application
Server
monitors
until
you
are
ready
to
move
to
the
new
resource
models.
The
following
table
lists
the
steps
needed
to
migrate
from
Tivoli
Manager
for
WebSphere
Application
Server.
Table
34.
Guidelines
for
migrating
from
previous
versions
of
the
product
Goal
Refer
to
Upgrade
your
system
to
meet
the
system
and
software
requirements
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
This
includes
upgrading
Tivoli
Enterprise
Console
and
Tivoli
Management
Framework.
Chapter
3,
“Pre-installation
requirements,”
on
page
19
Uninstall
Tivoli
Manager
for
WebSphere
Application
Server
from
endpoints.
See
Tivoli
Manager
for
WebSphere
Application
Server
documentation.
Upgrade
Tivoli
Distributed
Monitoring
software
to
IBM
Tivoli
Monitoring
software.
“Upgrading,
installing
Tivoli
patches,
and
installing
fix
packs”
on
page
78
Install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
“Installing
new
Tivoli
software”
on
page
74
Chapter
9.
Migrating
from
previous
versions
of
this
product
115
Table
34.
Guidelines
for
migrating
from
previous
versions
of
the
product
(continued)
Goal
Refer
to
Map
monitors
in
Tivoli
Distributed
Monitoring
to
resource
models
in
IBM
Tivoli
Monitoring,
Version
5.1.1.
IBM
Tivoli
Monitoring
for
Web
Infrastructure
supports
concurrency
with
Tivoli
Distributed
Monitoring.
You
can
continue
to
run
the
old
monitoring
systems
in
Tivoli
Distributed
Monitoring
after
you
have
installed
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
For
each
endpoint
you
must
choose
to
use
either
the
old
monitors
or
the
new
resource
models.
You
cannot
run
both
monitors
and
resource
models
on
the
same
endpoint.
The
“Mapping
monitors
to
resource
models”
section
lists
the
specific
monitors
that
correspond
to
each
resource
model.
Map
tasks
in
Tivoli
Manager
for
WebSphere
Application
Server
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks.
You
use
configuration
tasks
in
the
new
product
just
as
you
used
them
in
the
Tivoli
Manager
for
WebSphere
Application
Server.
“Mapping
Tivoli
Manager
for
WebSphere
Application
Server
tasks”
on
page
117
compares
the
tasks
from
the
old
product
to
the
new
product.
Mapping
monitors
to
resource
models
The
following
table
lists
the
Tivoli
Manager
for
WebSphere
Application
Server
monitors
and
the
corresponding
resource
models.
Table
35.
Tivoli
Manager
for
WebSphere
Application
Server
monitors
and
the
corresponding
new
resource
models
Monitor
Resource
model
Administration
Server
Status
WebSphereAS
Administration
Server
Status
Application
Server
Status
WebSphereAS
Application
Server
Status
Database
Connections
WebSphereAS
DB
Pools
Enterprise
JavaBeans
WebSphereAS
EJBs
HTTP
WebSphereAS
HTTP
Sessions
Integration
Server
Status
withdrawn
Java
Virtual
Machine
WebSphereAS
JVM
Runtime
Servlets
WebSphereAS
Web
Applications
Thread
Pools
WebSphereAS
Thread
Pools
N/A
WebSphereAS
Transactions
After
running
a
resource
model,
the
collected
data
can
be
viewed
in
real
time
by
using
the
IBM
Tivoli
Monitoring
Web
Health
Console.
Historical
data
are
logged
into
the
central
data
warehouse.
For
more
information
about
how
to
use
the
Web
Health
Console,
refer
to
the
IBM
Tivoli
Monitoring
User’s
Guide.
For
more
information
about
how
to
upload
data
to
the
central
data
warehouse,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide.
For
a
more
detailed
description
of
the
resource
models
provided
with
the
product,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide.
116
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Mapping
Tivoli
Manager
for
WebSphere
Application
Server
tasks
The
following
table
lists
the
Tivoli
Manager
for
WebSphere
Application
Server
tasks
and
the
corresponding
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks.
For
a
more
detailed
description
of
the
tasks
provided
with
the
product,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide.
Table
36.
Comparison
of
Tivoli
Manager
for
WebSphere
Application
Server
tasks
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks
Tivoli
Manager
for
WebSphere
Application
Server
task
New
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
task
Comments
Administration
Server
Status
Check
Administration
Server
Status
Application
Server
Status
Check
Application
Server
Status
Configure
Event
Server
Configure
Event
Server
Configure
WAS
Endpoint
Configure
WebSphere
TEC
Adapter
The
Integration
Server
has
been
replaced
with
a
Tivoli
Enterprise
Console
event
adapter.
Delete
Endpoint
Dependencies
withdrawn
Delete
Endpoint
Logs
Delete
Trace
Logs
Delete
Trace
Logs
removes
all
logs
associated
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
from
the
endpoint
or
managed
node.
It
does
not
delete
other
related
files
from
the
endpoint
or
managed
node.
N/A
Discover
WebSphere
Resources
Display
WAS
Endpoint
Configuration
Display
WebSphere
TEC
Adapter
Configuration
List
Application
Servers
List
Application
Servers
List
Endpoint
Logs
List
Trace
Logs
N/A
Send
WebSphere
Discovery
Events
to
TBSM
Start
Administration
Server
Start
Administration
Server
Start
Application
Server
Start
Application
Server
Start
Debugging
withdrawn
Start
Integration
Server
Start
WebSphere
TEC
Adapter
The
Integration
Server
has
been
replaced
with
a
Tivoli
Enterprise
Console
event
adapter.
Start
Monitors
withdrawn
Monitoring
is
now
performed
with
resource
models.
To
start
monitoring,
add
a
resource
model
to
a
profile
manager
and
distribute
the
profile
to
endpoints.
Stop
Administration
Server
Stop
Administration
Server
Stop
Application
Server
Stop
Application
Server
Stop
Debugging
withdrawn
Chapter
9.
Migrating
from
previous
versions
of
this
product
117
Table
36.
Comparison
of
Tivoli
Manager
for
WebSphere
Application
Server
tasks
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks
(continued)
Tivoli
Manager
for
WebSphere
Application
Server
task
New
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
task
Comments
Stop
Integration
Server
Stop
WebSphere
TEC
Adapter
The
Integration
Server
has
been
replaced
with
a
Tivoli
Enterprise
Console
event
adapter.
Stop
Monitors
withdrawn
118
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
10.
Setting
up
OS/400
endpoints
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
This
chapter
describes
the
OS/400
commands
that
enable
you
to
set
up
and
manage
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
endpoints.
These
endpoints
reside
on
iSeries
servers
that
run
the
OS/400
operating
system.
Table
37.
Guidelines
for
setting
up
OS/400
endpoints
Goal
Refer
to
Install
endpoint
software.
“Installing
the
endpoint”
Start
an
OS/400
endpoint.
“Starting
an
OS/400
endpoint”
on
page
122
Stop
an
0S/400
endpoint.
“Stopping
an
OS/400
endpoint”
on
page
125
Remove
an
endpoint
from
an
OS/400
system.
“Removing
an
endpoint
from
an
OS/400
system”
on
page
126
Installing
the
endpoint
Objective
To
install
Tivoli
endpoint
software
on
an
OS/400
system.
Background
information
The
w4inslcf.pl
script
installs
and
optionally
starts
the
OS/400
endpoint
daemon
on
one
or
more
iSeries
systems.
The
w4inslcf.pl
script
is
installed
on
your
endpoint
gateway
when
you
install
the
3.7-TMF-0043
patch.
The
location
or
path
of
this
script
is
as
follows:
$BINDIR/../lcf_bundle.40/generic/w4inslcf.pl
Tivoli
automatically
creates
the
following
required
software
entities
when
you
create
an
endpoint
on
OS/400:
v
Tivoli
creates
the
QTMELCF
library
when
you
install
an
endpoint
on
OS/400.
v
Tivoli
creates
the
QTIVOLI,
QTIVROOT,
and
QTIVUSER
user
profiles
when
you
configure
the
endpoint.
These
profiles
do
not
require
passwords
and
are
used
by
the
endpoint.
Table
38
describes
these
profiles.
Note:
If
any
of
these
profiles
are
deleted
or
corrupted,
you
must
delete
and
reinstall
the
endpoint
to
recreate
the
user
profiles
and
the
objects
that
belong
to
them.
Table
38.
User
profiles
that
Tivoli
creates
on
OS/400
User
profile
Description
Required
authority
QTIVOLI
QLCFD
job
runs
under
QTIVOLI.
This
user
profile
is
required
to
start
the
endpoint
and
owns
all
iSeries
unique
Tivoli
objects.
This
profile
must
have
*UPDATE
authority
to
all
the
directories
in
the
path
to
the
configuration
files.
*JOBCTL
*SAVSYS
*SPLCTL
©
Copyright
IBM
Corp.
2003
119
Table
38.
User
profiles
that
Tivoli
creates
on
OS/400
(continued)
User
profile
Description
Required
authority
QTIVROOT
Use
when
the
management
server
requires
root
authority.
*ALLOBJ
*AUDIT
*IOSYSCFG
*JOBCTL
*SAVSYS
*SECADM
*SERVICE
*SPLCTL
QTIVUSER
Equivalent
to
the
UNIX
nobody
user
ID.
No
special
authority
required.
Instead
of
the
w4inslcf.pl
command,
you
can
use
Tivoli
Software
Installation
Service
to
install
an
endpoint
on
OS/400.
You
use
the
File
Transfer
Protocol
(FTP)
for
this
option
and
select
the
os400
interpreter
type.
Tivoli
Software
Installation
Service
uses
the
w4inslcf.pl
script
to
install
an
endpoint.
See
the
following
documents
for
further
information
on
installation
using
Tivoli
Software
Installation
Service:
v
TME
10
Software
Installation
Service
User’s
Guide
v
Chapter
10,
“Checking
Prerequisites”
in
the
Tivoli
Enterprise
Installation
Guide
for
the
Tivoli
Management
Framework.
Required
authorization
role
To
use
the
RSTLICPGM
command
you
need
to
have
*ALLOBJ
and
*SECADM
authority
roles.
Before
you
begin
Enable
TCP/IP
for
the
OS/400
system.
For
information
on
configuring
TCP/IP
for
OS/400
systems,
see
the
following
Web
site:
http://www.ibm.com/eserver/iseries/infocenter
When
you
finish
None
Procedure
For
OS/400
endpoints,
use
the
w4inslcf.pl
command
on
the
command
line
of
the
Tivoli
server
to
install
an
endpoint.
This
section
provides
basic
CLI
syntax
for
the
command.
Run
the
w4inslcf.pl
–h
command
to
display
complete
information
on
the
syntax
for
this
command.
w4inslcf.pl
[–F]
[–g<machine[+port]>]
[–l
<ep_port>]
[–L
<config_options>]
[–Y]
[–T]
{<endpoint>...
|
–f
<file_name>}
where:
–F
Enables
the
command
to
overwrite
an
existing
installation
of
the
endpoint.
120
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
–g
<machine[+port]>
Specifies
the
Internet
Protocol
(IP)
address
or
host
name
and,
optionally,
the
port
number
of
the
gateway
to
which
the
endpoint
logs
in.
–l
<ep_port>
Specifies
the
port
number
for
the
endpoint.
The
default
port
number
is
9495.
–L
<config_options>
Passes
configuration
options
to
the
lcfd
command
for
starting
the
endpoint.
See
the
lcfd
command
in
the
Tivoli
Management
Framework
Reference
Manual
for
a
list
of
valid
options.
The
example
in
this
section
shows
how
to
specify
options.
If
you
specify
multiple
options
or
have
spaces
in
a
single
option,
you
must
enclose
the
text
in
double
quotation
marks
(″).
–N
<code>
Specifies
additional
languages
to
support.
The
following
codes
are
valid:
v
Chinese,
Simplified
(Code
2989)
v
Chinese,
Traditional
(Code
2987)
v
English,
uppercase
and
lowercase
(Code
2924)
v
English,
uppercase
DBCS
(Code
2938)
v
French
(Code
2928)
v
German
(Code
2929)
v
Italian
(Code
2932)
v
Japanese
(Code
2962)
v
Korean
(Code
2986)
v
Portuguese,
Brazilian
(Code
2980)
v
Spanish
(Code
2931)
To
specify
multiple
languages,
enclose
them
in
quotation
marks.
The
defaults
are
2924
and
2938.
–P
Specifies
to
prompt
the
user
for
a
password.
This
option
overrides
existing
entries
in
a
$HOME/.netrc
file
used
for
automatic
logins.
–Y
Specifies
that
the
installation
proceeds
without
confirmation.
The
default
behavior
is
to
request
confirmation.
–T
Specifies
an
IP
address
that
the
Tivoli
server
uses
to
connect
to
the
machine
on
which
the
agent
is
to
be
installed.
Use
this
flag
to
install
from
a
Tivoli
management
region
that
has
more
than
one
Network
Interface
Card.
endpoint
Specifies
the
names
or
IP
addresses
of
the
iSeries
systems
on
which
the
endpoint
is
installed.
–f
<file_name>
Specifies
the
file
containing
a
list
of
systems
on
which
to
install
endpoints.
This
file
contains
one
system
name
per
line,
specifying
the
user
ID
and
password
to
be
used.
Each
line
in
this
file
must
be
in
the
following
format:
hostname
[
userID
[
password]]
For
each
OS/400
endpoint
that
you
configure,
the
w4inslcf.pl
command
creates
the
/tmp/tivoli.<epname>.w4log
log
file
in
the
temporary
directory
of
the
Tivoli
server,
where
<epname>
is
the
name
of
the
OS/400
endpoint.
Chapter
10.
Setting
up
OS/400
endpoints
121
If
an
installation
fails,
the
w4inslcf.pl
command
creates
the
os4LcfH.err
error
file
in
the
directory
from
which
you
run
the
command.
The
file
lists
the
OS/400
endpoints
where
failure
occurred.
This
error
file
uses
name
syntax
that
is
valid
for
use
with
the
–f
flag
in
the
w4inslcf.pl
command.
After
you
eliminate
the
causes
of
an
installation
failure,
re-run
the
w4inslcf.pl
command.
The
w4inslcf.pl
command
checks
for
the
following
prerequisites:
v
Disk
space:
Checks
that
at
least
40
MB
of
free
space
exists
for
the
installation
and
running
of
the
endpoint.
v
Authority:
Checks
for
authority
to
the
RSTOBJ
and
RSTLICPGM
commands
and
to
*SAVSYS.
v
Allow
object
restore:
Checks
that
the
QALWOBJRST
system
value
has
*ALL
or
*ALWPGMADP
rights.
This
value
specifies
whether
objects
with
security-sensitive
attributes
can
be
restored.
v
Slip
installation:
Checks
whether
the
ITMELCF
product
was
already
installed
or
not.
v
Connection
with
the
gateway:
Checks
whether
it
can
open
a
socket
to
the
gateway
and
port
specified.
In
the
following
example,
the
w4inslcf.pl
command
installs
the
OS/400
endpoint
named
tomato
in
a
domain
named
myorg.mycompany.com.
w4inslcf.pl
tomato.myorg.mycompany.com
In
the
following
example,
the
w4inslcf.pl
command
installs
the
endpoint
named
server06
in
the
domain
mycompany.com.
The
w4inslcf.pl
command
passes
configuration
options
to
the
lcfd
command
to
use
when
it
starts
the
endpoint.
The
command
assigns
port
9131
for
endpoint
transactions.
The
–g
flag
specifies
the
gateway
cedar
and
the
port
1616
as
the
endpoint
to
contact
for
initial
login.
The
–L
flag
specifies
options
for
the
–D
flag
of
the
lcfd
command.
The
–D
lcs.machine_name
flag
assigns
the
name
server06-ep
to
the
endpoint.
w4inslcf.pl
-g
cedar+1616
-l
9131
-L
"-D
lcs.machine_name=server06-ep"\
server06.mycompany.com
For
more
information
on
Tivoli
Management
Framework
commands,
see
the
Tivoli
Management
Framework
Reference
Manual.
Starting
an
OS/400
endpoint
Objective
To
start
the
endpoint
daemon
process
for
an
endpoint
in
an
OS/400
operating
system.
Background
information
The
STRTMEEPT
command
starts
the
endpoint
daemon
process
for
an
endpoint.
This
endpoint
daemon
communicates
with
the
endpoint
gateway
to
receive
and
launch
endpoint
methods.
The
endpoint
daemon
job
is
always
submitted
to
the
QSYS/QSYSNOMAX
job
queue.
This
command
is
an
iSeries
command
that
you
can
run
from
any
iSeries
command
line
after
the
endpoint
code
is
installed
on
the
OS/400
endpoint.
You
can
also
launch
the
command
from
a
remote
machine.
Note:
STRTMEEPT
is
equivalent
to
the
$BINDIR/./lcf_bundle/generic/lcfd.sh
script,
which
is
available
for
other
platforms.
122
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
The
STRTMEEPT
command
starts
the
QLCD
job
on
the
OS/400
endpoint
with
the
appropriate
configuration
information.
The
default
value
for
all
parameters
is
*NONE.
When
you
use
*NONE,
the
STRTMEEPT
command
uses
the
parameter
values
from
the
last.cfg
file.
If
these
parameters
are
not
available
in
the
last.cfg
file
or
the
last.cfg
file
is
not
available,
the
STRTMEEPT
command
uses
the
internal
default
values.
The
following
table
lists
and
describes
parameters
that
are
available
for
the
STRTMEEPT
command:
Table
39.
Parameters
for
the
STRTMEEPT
command
Keyword
and
description
Parameter
Value
LGNINTRFC—Specifies
the
IP
address,
or
host
name
and
port
number,
of
one
or
more
gateways
to
which
the
endpoint
sends
the
login
packet.
This
option
is
required
for
the
endpoint
to
log
in
to
a
gateway
on
a
different
subnet
or
to
log
in
to
a
specific
gateway
when
two
or
more
gateways
exist
on
a
subnet.
Login
interface
*NONE
Name
Hostname
Port
Port
number
GATEWAY—Specifies
the
name
of
the
Tivoli
management
gateway
that
is
used
after
the
endpoint
has
successfully
logged
in.
If
the
endpoint
has
not
previously
logged
in,
use
the
LGNINTRFC
(or
the
lcs.login_interfaces
option
in
the
configuration
file)
to
provide
one
or
more
gateways
through
which
the
endpoint
may
log
in.
Gateway
*NONE
Name
Hostname
Port
Port
number
BCASTDSBL—Disables
the
UDP
broadcast.
If
you
set
this
option
to
yes,
you
must
use
the
lcs.login_interfaces
option.
Broadcast
disable
*NONE
*YES
or
1
to
disable
*NO
or
0
to
enable.
EPTNAME—Specifies
the
name
of
this
endpoint.
This
name
is
displayed
when
the
wep
ls
command
is
executed
in
the
gateway.
Endpoint
name
*NONE
*HOSTNAME
Use
the
host
name
as
the
name
for
this
endpoint.
endpoint_name-
Use
a
valid
OS/400
endpoint
name
PORT—Specifies
the
port
on
which
the
endpoint
daemon
(lcfd)
monitors
gateway
communications.
The
default
value
is
9494.
Local
TCP/IP
port
*NONE
port_number
MACHINEID—Identifies
the
endpoint.
Machine
unique
ID
machine_unique_id
Use
a
string
that
contains
a
unique
identifier
Chapter
10.
Setting
up
OS/400
endpoints
123
Table
39.
Parameters
for
the
STRTMEEPT
command
(continued)
Keyword
and
description
Parameter
Value
THRESHOLD—Defines
the
level
of
debug
messages
written
to
the
lcfd.log
file.
Note:
Level
3
and
greater
logging
generates
a
large
number
of
messages.
For
troubleshooting
endpoints,
Level
2
is
recommended.
Log
threshold
The
following
are
valid
entries:
0
No
message
logging
1
Minimal
logging
(default)
2
Tracing
and
moderate
output
3
Data
buffers
and
tight
loops
4
Data
LOGSIZE—Specifies
the
maximum
size
in
bytes
of
the
log
file.
Log
size
*NONE
size
Use
a
value
between
10240
and
10240000.
LOGQSIZE—Specifies
the
maximum
size
in
bytes
of
the
log
queue.
Log
queue
size
*NONE
size
Use
a
value
between
10240
and
10240000.
LOGFILE—Specifies
the
name
of
the
log
file
to
be
used
for
logging
messages.
Log
name
*NONE
path_name
Where
path
name
is
the
name
of
the
integrated
file
system
(IFS)
file
used
for
the
log.
CACHESIZE—Specifies
the
maximum
size
of
the
method
cache.
Note:
When
the
maximum
size
is
reached,
the
least
recently
used
methods
are
deleted
from
the
cache.
Cache
size
*NONE
size
and
integer
UPINTRVL—The
number
of
seconds
between
endpoint
broadcast
calls.
UDP
interval
*NONE
seconds
UDPATTMPT—The
number
of
times
an
endpoint
transmits
a
broadcast
call.
UDP
attempts
*NONE
number
of
times
where
number
is
an
integer
value
STRTMEOUT—The
amount
of
time
in
seconds
before
a
communications
timeout
occurs
during
login.
Start
timeout
*NONE
seconds
RUNTMEOUT—The
amount
of
time
in
seconds
before
a
communications
timeout
occurs
following
a
successful
login.
Run
timeout
*NONE
seconds
CFGFILE—The
name
of
the
configuration
file
to
be
used
to
start
the
endpoint.
Configuration
file
name
*NONE
config_file_name
124
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
39.
Parameters
for
the
STRTMEEPT
command
(continued)
Keyword
and
description
Parameter
Value
RUNDIR—Specifies
the
name
of
the
directory
from
which
the
endpoint
code
runs
on
the
OS/400
endpoint.
Running
directory
*NONE
directory_name
Required
authorization
role
The
authority
for
this
command
is
PUBLIC(*EXCLUDE)
by
default.
You
must
grant
privileges
to
any
users
who
will
be
using
these
commands.
Additionally,
you
must
authorize
these
users
to
access
the
following
associated
command
processing
programs
that
are
located
in
the
QTMELCF
library:
v
QLCFSTAR
v
QLCFEND
You
must
have
the
*USE
authority
to
grant
this
authorization.
Before
you
begin
None
When
you
finish
(Optional)
To
configure
the
endpoint
to
automatically
start
an
initial
program
load
(IPL)
operation,
modify
the
program
QSYS/QSTRUP
as
follows:
1.
Retrieve
CL
source
into
a
member
of
a
source
file
by
executing
the
following
command:
RTVCLSRC
PGM(QSYS/QSTRUP)
SRCFILE(QGPL/QCLSRC)
2.
Start
the
source
entry
utility:
STRSEU
SRCFILE(QGPL/QCLSRC)
SRCMBR(QSTRUP)
TYPE(CLP)
3.
Add
the
following
lines
as
the
last
job
to
start:
QSYS/STRTMEEPT
MONMSG
MSGID(CPF0000)
4.
Save
the
old
program
if
desired.
5.
Compile
the
program,
which
replaces
the
old
QSYS
program:
CRTCLPGM
PGM(QSYS/QSTRUP)
SRCFILE(QGPL/QCLSRC)
CHGOBJOWN
OBJ(QSYS/QSTRUP)
OBJTYPE(*PGM)
NEWOWN(QSYS)
Procedure
1.
Enter
the
STRTMEEPT
command.
2.
(Optional)
Press
F4
to
change
the
default
settings
for
the
command,
which
are
described
in
“Background
information.”
Stopping
an
OS/400
endpoint
Objective
To
stop
the
endpoint
daemon
process
for
an
endpoint
in
an
OS/400
operating
system.
Background
information
The
ENDTMEEPT
command
stops
the
endpoint
daemon
process
for
an
endpoint.
The
job
might
be
on
a
job
queue,
it
might
be
active
within
a
system,
or
it
might
have
already
completed
running.
This
command
is
an
iSeries
command
that
you
can
run
from
any
iSeries
command
line
after
the
endpoint
code
is
installed
on
the
OS/400
endpoint.
You
can
also
launch
the
command
from
a
remote
machine.
Chapter
10.
Setting
up
OS/400
endpoints
125
Spooled
files
for
an
endpoint
process
that
has
been
stopped
remain
in
the
output
queue.
However,
when
the
ENDTMEEPT
command
does
not
end
application
jobs
that
have
been
started
by
the
endpoint
daemon,
these
jobs
continue
to
run.
Use
the
DELAY
option
with
the
ENDTMEEPT
command
to
specify
that
the
endpoint
process
ends
in
a
controlled
manner
with
a
time
delay.
The
following
syntax
specifies
valid
parameters
for
the
ENDTMEEPT
command:
ENDTMEEPT
[OPTION(*CTRLD|*IMMED)[DELAY(30|1–9999999)]]
where:
*CTRLD
Specifies
the
default
option
that
enables
the
endpoint
daemon
to
finish
any
pending
requests
within
the
amount
of
time
specified
by
DELAY
(in
seconds).
The
default
delay
is
30
seconds.
*IMMED
Specifies
to
stop
the
endpoint
immediately.
Use
this
option
only
when
a
*CTRLD
end
fails
to
end
the
job
and
a
delay
time
is
not
used.
DELAY
Specifies
the
timed
delay
in
seconds
after
which
the
endpoint
daemon
is
stopped.
Required
authorization
role
The
authority
for
this
command
is
PUBLIC(*EXCLUDE)
by
default.
You
must
grant
privileges
to
any
users
who
will
be
using
these
commands.
Additionally,
you
must
authorize
these
users
to
access
the
following
associated
command
processing
programs
which
are
located
in
the
QTMELCF
library:
v
QLCFSTAR
v
QLCFEND
You
must
have
the
*USE
authority
to
grant
this
authorization.
Before
you
begin
None
When
you
finish
None
Procedure
1.
Enter
the
ENDTMEEPT
command.
2.
(Optional)
Press
F4
to
change
the
default
settings
for
the
command,
which
are
described
in
“Background
information.”
Removing
an
endpoint
from
an
OS/400
system
Objective
To
remove
the
endpoint
software
from
an
OS/400
system.
Background
information
None
Required
authorization
role
To
use
the
DLTLICPGM
command
you
need
to
have
*ALLOBJ
authority
or
have
specific
authority
from
the
security
officer.
126
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Before
you
begin
None
When
you
finish
None
Procedure
1.
Stop
all
Tivoli
jobs
or
any
other
jobs
that
were
started
by
Tivoli
Enterprise
products
and
are
running
on
the
endpoint,
and
make
sure
that
no
job
has
any
locks
to
any
language
libraries,
as
follows:
a.
Run
the
ENDTMEEPT
command
to
stop
the
endpoint
process.
b.
Stop
all
jobs
as
follows:
1)
Run
the
WRKUSRJOB
QTIVROOT
command
to
display
all
jobs
for
the
QTIVROOT
user
profile.
2)
Run
option
4,
End
Job,
against
each
running
job
listed
for
the
QTIVROOT
profile.
3)
Run
the
WRKUSRJOB
QTIVOLI
command
to
display
all
jobs
for
the
QTIVOLI
user
profile.
4)
Run
option
4,
End
Job,
against
each
running
job
listed
for
the
QTIVOLI
profile.
5)
Run
the
WRKUSRJOB
QTIVUSER
command
to
display
all
jobs
for
the
QTIVUSER
user
profile.
6)
Run
option
4,
End
Job,
against
each
running
job
listed
for
the
QTIVUSER
profile.c.
Run
the
WRKOBJLCK
command
to
determine
who
added
any
of
the
Tivoli
language
libraries
to
the
job
library
list.
For
example,
to
determine
who
added
English,
you
would
enter:
WRKOBJLCK
OBJ(QSYS/QTME2924)
OBJTYPE(*LIB)
2.
Delete
the
licensed
program
by
entering
the
following
command:
DLTLICPGM
LICPGM(ITMELCF)
3.
Execute
the
following
WRKOBJOWN
commands
on
each
Tivoli
user
account
to
display
all
objects
owned
by
the
specified
user:
WRKOBJOWN
USRPRF(QTIVUSER)
WRKOBJOWN
USRPRF(QTIVROOT)
WRKOBJOWN
USRPRF(QTIVOLI)
The
WRKOBJOWN
command
lists
all
objects
that
belong
to
a
user.
To
prevent
any
listed
object
from
being
deleted,
you
must
change
the
ownership
of
that
object
by
selecting
option
9
for
the
object
from
the
Work
with
Objects
by
Owner
display.
Repeat
this
step
for
each
object
that
you
want
to
save.
4.
Delete
the
user
account
names
by
specifying
the
*DLT
option,
which
deletes
all
objects
owned
by
a
user.
The
DLTUSRPRF
commands
must
be
entered
in
the
following
order:
DLTUSRPRF
USRPRF(QTIVUSER)
OWNOBJOPT(*DLT)
DLTUSRPRF
USRPRF(QTIVROOT)
OWNOBJOPT(*DLT)
DLTUSRPRF
USRPRF(QTIVOLI)
OWNOBJOPT(*DLT)
Note:
If
you
delete
QTIVOLI
before
deleting
other
user
accounts,
some
objects
might
not
be
deleted,
and
you
might
have
problems
reinstalling
the
endpoint.
Chapter
10.
Setting
up
OS/400
endpoints
127
128
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Chapter
11.
Installing
and
configuring
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems
This
chapter
describes
the
installation
and
configuration
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
proxy
mode
z/OS
systems.
For
a
list
of
the
specific
operating
systems,
applications,
and
protocols
that
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
requires,
refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
Program
Directory
and
“Supported
operating
systems”
on
page
19.
Table
40
shows
the
goals
for
installation
and
configuration
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS.
Table
40.
Goals
for
installation
and
configuration
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
Goal
Refer
to
1.
Review
the
architecture
details
to
ensure
that
you
understand
all
prerequisites
and
components.
“Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
in
proxy
mode
z/OS
systems”
on
page
129
2.
Increase
timeout
settings
for
gateway
transactions
that
require
more
than
the
default
time
period.
“Configuring
timeouts
for
Tivoli
gateways”
on
page
132
3.
Update
permissions
on
the
proxy
mode
z/OS
system
“Updating
permissions
for
proxy
mode
z/OS
systems”
on
page
132
4.
Configure
NetView
on
a
proxy
mode
z/OS
system.
“Configuring
Tivoli
NetView
for
z/OS
for
monitoring”
on
page
134
5.
Install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS.
“Installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
a
proxy
mode
z/OS
system”
on
page
134
6.
Set
up
security
permissions
in
the
proxy
mode
z/OS
system.
“Configuring
the
proxy
mode
z/OS
security
environment
to
accept
monitoring
operations”
on
page
135
7.
Install
a
task
server
to
be
used
for
monitoring
a
proxy
mode
z/OS
system.
“Installing
the
task
server
for
the
first
time”
on
page
136
8.
Enable
communications
between
the
task
server
and
the
proxy
mode
z/OS
system.
“Configuring
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
proxy
mode
z/OS
systems”
on
page
138
9.
Start
communications
between
the
task
server
and
the
proxy
mode
z/OS
system.
“Starting
communication
between
the
task
server
and
z/OS”
on
page
141
Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
in
proxy
mode
z/OS
systems
A
Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
spans
multiple
systems,
as
shown
in
Figure
13
on
page
130.
Items
1
to
4
show
the
distributed
(non-z/OS)
area
of
the
Tivoli
management
region.
Items
5
and
6
show
the
z/OS
area
of
the
Tivoli
©
Copyright
IBM
Corp.
2003
129
management
region.
The
list
following
the
figure
describes
software
requirements
for
each
item
in
the
figure.
The
following
list
summarizes
the
required
software
for
each
element
in
Figure
13:
1.
The
Tivoli
server
requires
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
2.
This
optional
computer
communicates
directly
with
z/OS
using
TCP/IP
and
runs
the
event
server
of
the
Tivoli
Enterprise
Console
to
provide
event
filtering
and
correlation.
You
must
install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
this
computer.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
more
information
about
using
Tivoli
Enterprise
Console
with
this
product.
This
product
does
not
support
local
event
correlation
on
a
proxy
mode
z/OS
system.
The
proxy
mode
z/OS
system
sends
Tivoli
Enterprise
Console
events
directly
to
the
Tivoli
Enterprise
Console
server.
The
event
classes
and
event
rules
are
the
same
for
proxy
mode
z/OS
systems
and
for
distributed
systems.
1.
Tivoli
management
region
server
2.
(Optional)
A
computer
to
host
a
Tivoli
Enterprise
Console
event
server
for
collecting
events
from
proxy
mode
z/OS
systems
proxy
mode
z/OS
systems
communicate
directly
with
the
event
server
running
on
this
computer.
3.
Managed
node
with
gateway
4.
Managed
node
with
endpoint
This
computer
communicates
directly
with
a
proxy
mode
z/OS
system.
It
acts
as
a
″proxy″
endpoint
for
a
z/OS
system.
5.
Target
and
focal
point
z/OS
system
You
can
configure
this
z/OS
system
to
be
a
focal
point
for
Tivoli
communication
with
multiple
z/OS
systems.
6.
(Optional)
Additional
target
z/OS
systems
operating
in
a
system
complex
and
communicating
through
the
IBM
Tivoli
NetView
for
z/OS
focal
point
Item
5
is
the
focal
point
for
Tivoli
communication
with
these
z/OS
systems.
Figure
13.
Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
130
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
3.
This
managed
node
with
gateway
runs
the
following
software:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
v
Tivoli
gateway
software
to
enable
communication
with
endpoints4.
This
managed
node
with
endpoint
runs
the
following
software:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
v
Tivoli
endpoint
software
to
enable
communication
with
the
Tivoli
environment
v
The
task
server,
a
Tivoli
Business
Systems
Manager
component
that
enables
communication
with
a
proxy
mode
z/OS
system
or
with
multiple
proxy
mode
z/OS
systems
in
a
system
complex.
This
communication
is
encrypted.
A
system
complex,
called
sysplex,
is
a
set
of
z/OS
systems
communicating
and
cooperating
with
each
other
through
multisystem
hardware
components
and
software
services
to
process
customer
workloads.
The
task
server
communicates
directly
with
a
single
proxy
mode
z/OS
system
using
TCP/IP
or
Systems
Network
Architecture
(SNA).
However,
it
can
communicate
with
multiple
NetView
Operators
on
that
one
system
to
improve
performance.
Item
4
in
the
diagram
represents
the
proxy
endpoint,
which
is
located
in
the
distributed
area
of
the
Tivoli
management
region.
The
proxy
endpoint
represents
the
z/OS
system
for
management
tasks.
Information
flows
from
the
Tivoli
management
software
through
the
task
server
to
the
z/OS
system
and
back
again.
Note:
This
proxy
endpoint
cannot
also
be
a
local,
or
non-z/OS,
endpoint.
5.
The
proxy
mode
z/OS
system
runs
the
following
software:
v
Communication
Server
for
OS/390,
which
provides
TCP/IP
or
Systems
Network
Architecture
(SNA)
v
IBM
Tivoli
NetView
for
z/OS.
The
purpose
of
IBM
Tivoli
NetView
for
z/OS
is
to
serve
as
a
focal
point
for
Tivoli
communication
with
multiple
z/OS
systems.
A
focal
point
system
only
needs
to
run
IBM
Tivoli
NetView
for
z/OS.
It
is
possible
for
a
system
to
be
a
focal
point
and
not
run
IBM
WebSphere
Application
Server
software
or
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
software.
In
this
case,
the
system
only
enables
communication
between
Tivoli
and
other
proxy
mode
z/OS
systems
that
are
running
IBM
WebSphere
Application
Server.
Note:
You
must
have
REXX
enabled
for
IBM
Tivoli
NetView.
v
IBM
WebSphere
Application
Server
for
z/OS6.
Additional
target
z/OS
systems
that
operate
and
communicate
through
the
IBM
Tivoli
NetView
for
z/OS
focal
point
run
the
following
software:
v
Communication
Server
for
OS/390
v
IBM
Tivoli
NetView
for
z/OS
Note:
You
must
define
Virtual
Telecommunications
Access
Method
(VTAM)
Cross
Domain
Resource
Manager
on
each
system
in
the
sysplex
to
enable
NetView
communication
between
the
systems.
v
IBM
WebSphere
Application
Server
for
z/OS
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
Chapter
11.
Installing
and
configuring
for
z/OS
131
This
configuration
enables
you
to
manage
multiple
instances
of
IBM
WebSphere
Application
Server
on
multiple
z/OS
systems
using
the
same
proxy
endpoint.
These
systems
must
be
part
of
a
sysplex.
Configuring
timeouts
for
Tivoli
gateways
Objective
To
extend
the
default
duration
for
gateway
transactions
to
match
requirements
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
systems.
Background
information
Several
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks
might
take
more
time
to
complete
on
the
proxy
mode
z/OS
systems
than
the
default
five-minute
timeout
value
that
is
configured
on
Tivoli
gateways.
You
can
allocate
more
time
to
these
tasks
so
that
they
complete
successfully.
Required
authorization
role
senior
Before
you
begin
None
When
you
finish
None
Procedure
Increase
the
default
gateway
timeout
value
to
600
seconds
or
greater
on
all
gateways
that
service
endpoints
located
on
a
Tivoli
Business
Systems
Manager
task
server.
Run
the
following
command
from
the
command
line
on
any
managed
node
in
the
Tivoli
management
region
that
has
the
Tivoli
environment
sourced:
wgateway
<gateway_name>
set_session_timeout
600
where
<gateway_name>
is
the
name
of
the
gateway
with
the
timeout
you
want
to
change.
For
more
information
on
the
wgateway
command,
see
the
Tivoli
Management
Framework
Reference
Manual.
Updating
permissions
for
proxy
mode
z/OS
systems
Objective
To
ensure
that
you
have
the
required
level
of
permissions
on
your
proxy
mode
z/OS
systems.
Background
information
Before
you
can
install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
z/OS
systems,
you
need
specific
permissions
on
z/OS
systems,
such
as
access
to
the
/var/itmwas
directory
and
subdirectories.
On
the
proxy
mode
z/OS
system,
you
must
have
the
required
permissions
as
listed
below:
132
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Table
41.
Required
permissions
for
proxy
mode
z/OS
directories
Directory
User
ID
and
level
of
permission
required
/var/itmwas
/var/itmwas/log
/var/itmwas/trace
Read/write
permissions
for
the
WebSphere
administrator
IDs
associated
with
the
NETCONV
session
/var/itmwas/trace
/var/itmwas/log
Read/write
permissions
for
the
user
ID
associated
with
the
z/OS
collector.
This
is
either
the
user
ID
that
runs
the
collectorStart
script
from
USS
or
the
user
ID
associated
with
the
ITDWAS
JCL.
Required
authorization
role
No
Tivoli
role
is
required
Before
you
begin
None
When
you
finish
Install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
your
proxy
mode
z/OS
system,
as
described
in
“Installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
a
proxy
mode
z/OS
system”
on
page
134.
Procedure
For
z/OS
version
1.2
or
earlier,
use
the
following
steps
to
update
your
permissions:
1.
Ensure
that
group
access
checking
is
active
in
your
security
server.
If
you
have
RACF,
issue
SETR
LIST
and
look
for
″LIST
OF
GROUPS
ACCESS
CHECKING
IS
ACTIVE.
2.
Create
a
group.
For
RACF,
issue
ADDGROUP
<group_name>
OMVS(GID(2)),
where
<group_name>
is
the
name
of
the
new
group,
such
as
″WASPAC.″
3.
Connect
the
following
users
to
this
group:
v
IBM
WebSphere
Application
Server
administrator
ID
(such
as
CBADMIN)
v
The
user
IDs
under
which
the
monitored
IBM
WebSphere
Application
Server
application
or
applications
will
be
running
(such
as
CBASRU1
or
CBACRU1)
v
The
user
specified
in
the
JCL
of
the
Tivoli
NetView
UNIX
Command
Server
(such
as
ROOT)
v
The
Tivoli
NetView
operator
ID
used
for
the
NETCONV
connection
from
the
z/OS
system
to
the
proxy
endpoint.
This
might
be
the
same
as
the
IBM
WebSphere
Application
Server
administrator
ID.
v
The
user
ID
under
which
the
Data
Collector
runs.
This
should
be
ITDSRV
if
you
are
running
the
Data
Collector
as
a
started
task.
Otherwise,
it
should
be
the
user
ID
that
runs
the
collectorStart.sh
script,
if
the
Data
Collector
is
started
in
USS.
v
If
you
plan
to
implement
a
proxy
mode
z/OS
Tivoli
Enterprise
Console
event
adapter,
the
user
ID
under
which
the
adapter
will
run4.
Run
the
following
USS
commands:
cd
/var
chmod
-R
770
itmwas
chgrp
-R
<group_name>
itmwas
Chapter
11.
Installing
and
configuring
for
z/OS
133
where
<group_name>
is
the
name
of
the
group
you
created.
For
z/OS
version
1.3
or
higher,
you
can
use
the
steps
above
or
you
can
use
the
USS
setfacl
command
to
add
additional
authorities
to
a
directory
or
file
to
give
the
list
of
user
IDs
above
the
appropriate
authorities.
See
the
UNIX
System
Services
Command
Reference
for
more
information.
Installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
a
proxy
mode
z/OS
system
Objective
To
plan
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
installation
on
a
proxy
mode
z/OS
system.
Note:
You
install
other
elements
of
a
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
system
in
the
distributed
area
of
the
Tivoli
management
region,
as
shown
in
“Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
in
proxy
mode
z/OS
systems”
on
page
129.
Background
information
Install
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
on
each
proxy
mode
z/OS
system
that
is
running
IBM
WebSphere
Application
Server
resources
that
you
want
to
manage.
The
z/OS
software
distribution
tape
contains
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
software.
Installation
from
the
tape
is
performed
by
the
System
Modification
Program
Extended
(SMP/E).
Before
you
begin
IBM
Tivoli
NetView
for
z/OS
must
be
installed
on
each
z/OS
system.
When
you
finish
Install
the
task
server
as
described
in
“Installing
the
task
server
for
the
first
time”
on
page
136.
Procedure
Use
the
System
Modification
Program
Extended
(SMP/E)
to
install
the
product
from
the
software
distribution
tape.
Additional
Information:
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
Program
Directory
comes
with
the
software
distribution
tape
and
describes
the
requirements
and
procedures
for
installation.
You
can
also
install
the
product
from
the
installation
CD.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
Program
Directory
and
the
Supplemental
Installation
Instructions
for
more
information.
Configuring
Tivoli
NetView
for
z/OS
for
monitoring
Objective
To
set
up
Tivoli
NetView
for
z/OS
to
facilitate
communication
with
the
proxy
mode
z/OS
system
from
a
managed
node
endpoint.
134
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Background
information
See
“Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
in
proxy
mode
z/OS
systems”
on
page
129
for
a
diagram
of
the
Tivoli
management
region
for
proxy
mode
z/OS
systems,
including
the
managed
node
endpoint.
The
following
documents
provide
comprehensive
information
on
this
procedure:
v
For
Version
1.3
of
Tivoli
NetView
for
OS/390:
Tivoli
NetView
for
OS/390,
Version
1.3,
Installation
and
Administration
Guide
and
the
chapters
entitled
“Preparing
the
MVS
System”
and
“Installing
NetView”
v
For
Version
1.4
of
Tivoli
NetView
for
OS/390:
Tivoli
NetView
for
OS/390,
Version
1.4,
Installation:
Configuring
Additional
Components
and
the
chapter
entitled
“Setting
Up
UNIX
System
Services
for
the
NetView
Program”
v
For
Version
5.1
of
Tivoli
NetView
for
z/OS:
Tivoli
NetView
for
z/OS,
Version
5.1,
Installation:
Configuring
Additional
Components
and
the
chapter
entitled
“Setting
Up
UNIX
System
Services
for
the
NetView
Program”
Before
you
begin
Tivoli
NetView
for
z/OS
must
be
installed
and
set
up
as
described
in
the
documentation
for
that
product.
When
you
finish
Configure
the
security
environment
as
described
in
“Configuring
the
proxy
mode
z/OS
security
environment
to
accept
monitoring
operations.”
Procedure
Follow
the
procedures
in
the
Tivoli
NetView
documentation
to
set
up
the
NetView
UNIX
Command
Server.
Configuring
the
proxy
mode
z/OS
security
environment
to
accept
monitoring
operations
Objective
To
configure
the
security
server
in
your
proxy
mode
z/OS
system
to
accept
operations
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
Background
information
This
procedure
provides
examples
of
configuration
settings
for
a
Resource
Access
Control
Facility
(RACF)
security
server.
Use
equivalent
settings
to
configure
other
security
servers.
The
following
documents
are
available
on
the
IBM
Publications
Center
Web
site,
and
provide
further
information
on
RACF
security
servers
in
proxy
mode
z/OS:
v
z/OS
Security
Server
RACF
Command
Language
Reference
v
z/OS
Security
Server
RACF
Security
Administrator’s
Guide
The
following
list
shows
equivalent
documents
for
previous
versions
of
z/OS
(OS/390):
v
For
z/OS,
Version
1.1
to
Version
1.4:
z/OS
SecureWay
Security
Server
RACF
Command
Language
Reference
and
z/OS
SecureWay
Security
Server
RACF
Security
Administrator’s
Guide
v
For
OS/390,
Version
2.10:
OS/390
V2R10.0
SecureWay
Security
Server
RACF
Command
Language
Reference
and
OS/390
V2R10.0
SecureWay
Security
Server
RACF
Security
Administrator’s
Guide
Chapter
11.
Installing
and
configuring
for
z/OS
135
Required
authorization
role
The
NetView
operator
IDs
used
to
communicate
between
the
proxy
endpoint
and
z/OS
systems
must
be
IBM
WebSphere
Application
Server
administrators.
If
the
system
is
running
under
program
control,
the
following
NetView
datasets
require
APF
authorization
and
need
to
be
program
controlled:
NetView
HLQ.SEAGALT
and
HLQ.SEKGLNK1
(or
HLQ.SCNMLNKN
for
NetView
5.1),
where
HLQ
is
the
high
level
qualifier
for
NetView
datasets.
Use
RACF’s
RALTER
PROGRAM
command
to
put
these
datasets
under
program
control.
Before
you
begin
Perform
the
procedure
mentioned
in
“Configuring
Tivoli
NetView
for
z/OS
for
monitoring”
on
page
134.
When
you
finish
Start
the
task
communication
with
the
z/OS
system
as
described
in
“Starting
communication
between
the
task
server
and
z/OS”
on
page
141.
Procedure
1.
Define
an
OMVS
segment
for
each
of
the
NetView
operators
that
you
define
on
the
task
server
located
on
the
managed
node
endpoint
to
communicate
with
the
z/OS
system.
Additional
Information:
See
“Configuring
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
proxy
mode
z/OS
systems”
on
page
138
for
information
on
defining
operators
on
the
task
server.
You
must
perform
this
step
for
each
NetView
operator
that
you
want
to
define
on
the
task
server.
Note:
The
UID
in
the
OMVS
segment
of
the
NetView
operator
must
be
unique
in
the
Security
Server
on
the
proxy
mode
z/OS
system.
If
RACF
is
the
Security
Server
on
your
system,
see
the
RACF
administrator
to
determine
a
unique
user
ID.
2.
Define
BPX.DAEMON
facility
class.
Then
assign
permissions
to
the
user
ID
that
the
NetView
UNIX
server
runs
under.
This
user
(and
password)
is
specified
in
the
job
card
of
the
CNMSJUNX
proc
and
needs
to
have
UID=0
authority.
Use
the
following
commands:
RDEFINE
FACILITY
BPX.DAEMON
UACC(NONE)
PERMIT
BPX.DAEMON
CLASS(FACILITY)
ID(ROOT)
ACCESS(READ)
SETROPTS
RACLIST(FACILITY)
REFRESH
Note:
Perform
this
step
one
time
on
the
system.
BPX.DAEMON
might
already
be
activated
on
your
system.
Installing
the
task
server
for
the
first
time
Objective
To
install
the
task
server
that
sends
and
receives
commands
and
monitoring
data
for
proxy
mode
z/OS
systems.
Background
information
Use
one
installation
of
the
task
server
on
a
dedicated
server
to
communicate
with
the
proxy
mode
z/OS
system.
Use
a
separate
installation
of
the
task
server
for
Tivoli
Business
Systems
Manager.
Install
the
task
server
in
the
distributed
area
of
the
Tivoli
management
region.
See
“Tivoli
environment
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
in
proxy
mode
z/OS
systems”
on
page
129
for
a
diagram
of
the
136
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Tivoli
management
region
for
proxy
mode
z/OS
systems.
The
target
computer
can
be
Windows,
an
AIX,
or
a
Solaris
managed
node
that
has
IP
connectivity
with
the
proxy
mode
z/OS
system
that
is
running
the
focal
point
NetView.
The
task
server
is
not
available
on
HP-UX.
The
task
server
is
installed
as
part
of
the
Tivoli
Business
Systems
Manager
Event
Enablement
product,
which
is
provided
on
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
Version
5.1.2:
WebSphere
Application
Server
Component
Software
installation
CD
in
the
\TBSM\EE
directory.
The
task
server
process
starts
automatically
when
you
start
the
operating
system.
You
can
verify
or
modify
this
behavior
as
follows:
v
On
Windows,
access
the
Windows
service
called
Tivoli
BSM
Task
Server
in
the
Services
window
through
the
Windows
Control
Panel.
v
On
AIX
and
Solaris,
access
the
ihscts
daemon
in
the
following
configuration
files:
–
For
AIX:
/etc/rc.tbsm
–
For
Solaris:
/etc/rc3.d/S95tbsm
and
/etc/rc0.d/K05tbsm
An
entry
is
added
to
the
inittab
file
with
the
ID
rctbsm.
The
Version
1.5
task
server
cannot
coexist
with
a
previous
version
of
the
task
server
or
the
Tivoli
Global
Enterprise
Manager
topology
server.
If
a
previous
version
of
the
task
server
or
the
topology
server
is
installed,
use
the
tserver
remove
command
to
uninstall
it
before
installing
the
Version
1.5
task
server.
Required
authorization
role
super
Before
you
begin
See
Chapter
2,
“Guidelines
for
installation
and
setup,”
on
page
15
for
a
checklist
of
activities
prior
to
installation.
As
a
precautionary
measure,
back
up
the
Tivoli
management
region
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
Start
the
Tivoli
desktop
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
When
you
finish
Install
Tivoli
Business
Systems
Manager
patch
1.5-BSM-0038
to
update
the
task
server,
as
described
in
“Upgrading,
installing
Tivoli
patches,
and
installing
fix
packs”
on
page
78.
Patch
15-BSM-0043
supersedes
the
15-BSM-0038
patch
when
that
patch
becomes
available.
Configure
the
task
server
as
described
in
“Configuring
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
proxy
mode
z/OS
systems”
on
page
138.
Start
communication
between
the
proxy
mode
z/OS
system
and
the
task
server
as
described
in
“Starting
communication
between
the
task
server
and
z/OS”
on
page
141.
Chapter
11.
Installing
and
configuring
for
z/OS
137
Procedure
Tivoli
desktop:
1.
Click
Install
in
the
Desktop
menu.
2.
Click
Install
Product
to
display
the
Install
Product
window.
3.
If
necessary,
click
OK
to
bypass
a
harmless
error
message
about
the
media
settings.
4.
Click
Select
Media
to
display
the
File
Browser
window.
5.
In
the
Path
Name
text
field,
enter
the
full
path
to
the
.IND
file
on
the
CD-ROM
drive.
Additional
Information:
The
index
(.IND)
file
contains
details
regarding
the
components
of
the
product
installation.
Be
sure
to
use
backward
slashes
(\)
for
Windows
path
names
instead
of
forward
slashes
(/).
6.
Click
Set
Path
to
display
the
File
Browser
windows
containing
the
specified
media
in
the
Files
scrolling
list.
7.
Click
Set
Media
&
Close.
8.
Select
Tivoli
Business
Systems
Manager
Event
Enablement
1.5
in
the
Select
Product
to
Install
scrolling
list.
9.
Select
the
target
client
from
the
Available
Clients
scrolling
list.
10.
Click
the
left
arrow
to
move
the
selected
client
to
the
Clients
to
Install
On
scrolling
list.
11.
If
necessary,
select
the
clients
on
which
you
do
not
want
to
install
the
task
server
from
the
Clients
to
Install
On
list
and
click
the
right
arrow
to
move
them
to
the
Available
Clients
list.
12.
Click
Install
&
Close
to
display
the
Product
Install
window
and
a
list
of
pending
installation
actions.
13.
Click
Continue
Install
to
begin
the
installation
process.
Additional
Information:
The
Product
Install
window
displays
the
progress
of
the
installation.
View
the
messages
in
the
task
output
window
to
determine
whether
the
product
installation
was
successful.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Problem
Determination
Guide
for
information
on
problem
determination.
14.
Click
Close
to
close
the
Product
Install
window.
15.
As
a
precautionary
measure,
back
up
the
Tivoli
management
region
databases
as
described
in
“Backing
up
and
restoring
Tivoli
databases”
on
page
30.
Use
a
unique
name
for
the
new
backup
files.
Configuring
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
proxy
mode
z/OS
systems
Objective
To
enable
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
the
z/OS
NetView
system
with
commands
that
you
enter
on
the
Tivoli
managed
node
that
hosts
the
task
server.
Background
information
Use
one
installation
of
the
task
server
for
communication
with
the
proxy
mode
z/OS
system.
Note:
Use
a
separate
installation
of
the
task
server
for
Tivoli
Business
Systems
Manager
Event
Enablement.
138
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
The
following
actions
included
in
this
procedure
enable
the
task
server
to
communicate
with
the
proxy
mode
z/OS
system:
Give
a
user
account
the
required
privileges
and
rights
in
Windows
(Windows
only)
A
user
account
must
have
several
privileges
and
rights
that
Windows
systems
require
to
enable
Tivoli
operations.
Change
TCP/IP
port
numbers,
if
other
applications
use
these
port
numbers:
If
other
applications
use
the
default
TCP/IP
ports
for
the
task
server
(4020
and
4042)
you
must
assign
new,
unique
port
numbers.
Enable
the
task
server
to
reference
multiple
operator
IDs
on
the
z/OS
system
The
task
server
achieves
multithreading
of
communications
by
referencing
multiple
operator
IDs
when
it
sends
hostcmd
commands
to
IBM
Tivoli
NetView
for
z/OS.
The
task
server
alternates
between
the
available
operator
IDs,
invoking
them
concurrently
to
improve
performance
and
response
time.
See
the
Tivoli
Business
Systems
Manager
Administration
Guide,
Version
1.5
for
more
information
on
this
set
of
commands.
Required
authorization
role
This
procedure
requires
the
following
authorizations:
v
On
UNIX:
root
v
On
Windows:
Administrator
v
Within
Tivoli:
super
Before
you
begin
Install
the
task
server
as
described
in
“Installing
the
task
server
for
the
first
time”
on
page
136.
When
you
finish
None
Procedure
1.
(Windows
only)
Give
a
user
account
the
required
privileges
and
rights
in
Windows
by
doing
the
following:
a.
Log
on
to
the
computer
that
runs
the
task
server
using
a
user
account
with
Administrator
privileges.
b.
Click
Start→Programs.
c.
Click
User
Manager
or
User
Manager
for
Domains
for
NT
servers
in
the
Administrative
Tools
(Common)
menu.
d.
Select
the
user
you
want
to
modify
in
the
Username
list.
e.
Add
the
user
to
the
Administrators
group
as
follows:
1)
Double-click
the
user
name
to
access
the
Users
Properties
window.
2)
Click
Groups
to
access
the
Group
Memberships
window.
3)
Select
Administrators
in
the
Not
member
of
list.
4)
Click
Add
to
move
Administrators
to
the
Member
of
list.
5)
Click
OK
to
return
the
Users
Properties
window.
6)
Click
OK
to
save
your
changes
and
to
return
to
the
User
Manager
window.f.
Click
User
Rights
in
the
Policies
menu
to
access
the
User
Rights
Policy
window.
g.
Click
Show
Advanced
User
Rights.
h.
Assign
the
Act
as
part
of
the
operating
system
user
right
to
the
user
as
follows:
Chapter
11.
Installing
and
configuring
for
z/OS
139
1)
Click
Act
as
part
of
the
operating
system
in
the
Right
drop-down
list.
2)
Click
Add
to
access
the
Add
Users
and
Groups
window.
3)
Click
Show
Users.
4)
Select
the
user
in
the
Names
list.
5)
Click
Add.
6)
Click
OK
to
return
to
the
User
Rights
Policy
window.i.
Repeat
Step
1h
to
assign
the
Replace
a
process
level
token
user
right
to
the
user.
In
Step
1h1
you
select
Replace
a
process
level
token
instead
of
Act
as
part
of
the
operating
system.
j.
Repeat
Step
1h
to
assign
the
Log
on
as
a
service
user
right
to
the
user.
In
Step
1h1
you
select
Log
on
as
a
service
instead
of
Act
as
part
of
the
operating
system.
k.
Click
OK
to
save
the
user
rights
assignments.
l.
Click
Close
to
close
the
User
Manager
window.
m.
Log
off
your
user
account
to
apply
these
changes.2.
(Optional)
Change
TCP/IP
port
numbers
by
doing
the
following
if
other
applications
use
these
port
numbers:
a.
Open
the
services
text
file
in
the
following
directory
path:
v
On
AIX
or
Solaris:
/etc
v
On
Windows:
%SystemRoot%\system32\drivers\etcb.
Find
the
following
entries
and
change
the
default
port
settings
(4020
or
4042)
to
unique
port
numbers:
tserver_tbsm
4020/tcp
#server
z/OS
port
tserver_ts
4042/tcp
#task
server
port
Additional
Information:
If
you
reassign
the
default
z/OS
port
number
(4020),
you
must
also
customize
the
IBM
Tivoli
NetView
for
z/OS
Port
keyword
in
the
DUIFPMEM
file.
For
more
information
about
the
Port
keyword,
see
IBM
Tivoli
NetView
for
OS/390
Administration
Reference.3.
Identify
one
or
more
z/OS
NetView
operators
to
the
task
server:
a.
Access
the
Tivoli
environment
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
b.
Access
the
following
bin
directory
on
the
task
server
in
the
path
defined
by
the
Tivoli
BINDIR
environment
variable:
v
On
UNIX:
$BINDIR/TDS/EventService/bin
v
On
Windows:
%BINDIR%\TDS\EventService\binc.
(Windows
only)
Type
bash
to
access
the
bash
command-line
interface.
d.
Enter
the
following
command
to
enable
the
task
server
to
reference
the
IBM
Tivoli
NetView
for
z/OS
operator
ID
and
password:
./hostcmdoper
-u
operator_ID
-p
password
where
operator_ID
and
password
correspond
to
a
NetView
operator
on
the
proxy
mode
z/OS
system.
The
hostcmdoper
command
encrypts
the
password
and
stores
it
on
disk
on
the
task
server.
See
the
Tivoli
Business
Systems
Manager
Administration
Guide,
Version
1.5
for
more
information
on
this
command.
e.
Repeat
3d
for
each
operator
ID
that
you
want
to
reference.
f.
Run
the
following
command
to
verify
success
of
Step
3d:
./hostcmdoper
-s
140
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Additional
Information:
Refer
to
the
Tivoli
Business
Systems
Manager
Administration
Guide,
Version
1.5
for
more
information
on
this
command.
g.
(Optional)
Run
the
following
command
to
delete
a
reference
to
NetView
operator
IDs.
This
command
deletes
the
first
operator
ID
reference
that
you
defined
in
Step
3d:
./hostcmdoper
-d
operator_ID
4.
If
necessary,
start
the
task
server
as
follows
to
enable
communication
with
NetView
in
the
z/OS
system.
Additional
Information:
The
task
server
process
is
configured
to
run
by
default,
but
might
be
stopped
manually.
The
process
must
be
running
to
complete
this
procedure.
a.
Access
the
bin
directory
for
the
task
server.
v
For
AIX
and
Solaris:
$BINDIR/TDS/EventService/bin
v
For
Windows:
%BINDIR%\TDS\EventService\binb.
Enter
the
following
command:
tserver
start
Starting
communication
between
the
task
server
and
z/OS
Objective
To
initiate
and
verify
the
communication
between
the
task
server
and
IBM
Tivoli
NetView
for
z/OS
on
the
proxy
mode
z/OS
system.
Background
information
The
task
server
starts
automatically
as
a
process
when
you
start
the
operating
system.
This
procedure
tells
how
to
establish
communication
between
the
task
server
and
IBM
Tivoli
NetView
for
z/OS
on
the
proxy
mode
z/OS
system.
Examples
in
this
procedure
describe
how
to
set
up
authorization
and
access
in
a
Resource
Access
Control
Facility
(RACF)
security
system.
The
Resource
Access
Control
Facility
program
provides
access
control
on
the
OS/390
Security
Server
and
is
also
available
as
a
separate
program
for
the
Multiple
Virtual
Storage
(MVS)
environment
within
a
proxy
mode
z/OS
system.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
has
no
RACF
options,
but
you
can
enable
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
programs
to
access
a
protected
resource.
See
the
documentation
for
Resource
Access
Control
Facility
for
instructions
on
enabling
access
to
protected
resources.
If
you
use
IBM
Tivoli
NetView
security
features
to
control
authorization
and
access,
see
IBM
Tivoli
NetView
for
z/OS
Security
Reference
for
more
information.
Required
authorization
role
This
procedure
requires
the
following
authorizations:
v
On
UNIX:
root
v
On
Windows:
Administrator
v
Within
the
Tivoli
environment:
super
Before
you
begin
Perform
the
procedure
“Configuring
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
proxy
mode
z/OS
systems”
on
page
138.
Chapter
11.
Installing
and
configuring
for
z/OS
141
The
task
server
must
be
running
when
you
perform
this
procedure.
The
task
server
is
configured
to
run
automatically.
To
verify
that
it
is
running,
check
the
status
of
one
of
the
following
processes:
v
On
Windows,
the
task
server
starts
automatically
as
a
Windows
service
called
Tivoli
BSM
Task
Server.
To
review
or
alter
these
settings,
access
the
Services
window
through
the
Windows
Control
Panel.
v
On
AIX
and
Solaris,
the
task
server
starts
automatically
as
the
daemon
ihscts.
To
review
or
alter
these
settings,
see
the
following
configuration
files:
–
For
AIX:
/etc/rc.tbsm
–
For
Solaris:
/etc/rc3.d/S95tbsm
and
/etc/rc0.d/K05tbsm
When
you
finish
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
further
configuration
steps.
Procedure
1.
In
the
distributed
area
of
the
Tivoli
management
region,
start
the
task
server
if
it
is
not
already
running.
Additional
Information:
The
task
server
is
configured
to
run
automatically.
Normally
you
do
not
need
to
start
it
manually.
The
procedure
for
configuring
the
task
server
describes
how
to
start
the
task
server
manually
in
Step
4
on
page
141.
If
you
want
to
verify
that
the
task
server
is
running,
check
the
status
of
the
task
server
process,
which
is
mentioned
in
the
“Before
you
begin”
section.
2.
In
the
proxy
mode
z/OS
system,
confirm
that
the
IBM
Tivoli
NetView
for
z/OS
CNMTAMEL
task
is
active,
as
follows:
a.
Access
the
NetView
Command
Facility
console
(called
NCCF).
b.
Type
the
list
cnmtamel
command.
c.
If
the
command
does
not
generate
a
result,
type
the
following
command
to
start
the
task:
start
task=cnmtamel
Additional
Information:
See
IBM
Tivoli
NetView
for
z/OS
documentation
for
more
information.
3.
Run
the
following
command
on
the
operator
console
of
IBM
Tivoli
NetView
for
z/OS:
netconv
action=start
ip=hostname
where
hostname
is
the
IP
address
or
the
fully
qualified
host
name
of
the
computer
on
which
the
task
server
runs.
Additional
Information:
The
following
example
establishes
a
TCP/IP
connection
with
a
task
server
located
on
a
computer
whose
IP
address
is
69.200.60.65:
netconv
action=start
ip=69.200.60.65
This
session
enables
TCP/IP
communication
with
the
task
server
and
must
remain
active.
Whenever
you
stop
and
start
the
task
server,
you
must
enter
the
NETCONV
command
again.
4.
Run
the
following
command
on
the
IBM
Tivoli
NetView
for
z/OS
operator
console
to
start
the
NetView
UNIX
Command
Server:
start
unixserv=*
142
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Additional
Information:
The
start
unixserv=*
command
allows
NetView
to
route
commands
to
the
NetView
UNIX
Command
Server.
The
following
command
stops
the
NetView
UNIX
Command
Server:
stop
unixserv=*
5.
Verify
that
communication
between
IBM
Tivoli
NetView
for
z/OS
and
MVS
is
successful
by
doing
the
following:
a.
Access
the
Tivoli
environment
as
described
in
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
73.
b.
Access
the
following
bin
directory
on
the
task
server
in
the
path
defined
by
the
Tivoli
BINDIR
environment
variable:
v
On
UNIX:
$BINDIR/TDS/EventService/bin
v
On
Windows:
%BINDIR%/TDS/EventService/binc.
(Windows
only)
Type
bash
to
access
the
bash
command-line
interface.
d.
Run
the
following
command
on
the
task
server:
./hostcmd
"mvs
d
a,l"
-h
hostname
where
hostname
is
the
IP
address
or
the
fully
qualified
host
name
of
the
proxy
mode
z/OS
system
on
which
the
command
is
to
be
executed.
The
hostcmd
command
displays
the
list
of
all
active
tasks
running
on
the
proxy
mode
z/OS
system.
See
the
Tivoli
Business
Systems
Manager
Administration
Guide,
Version
1.5
for
more
information
on
the
hostcmd
command.
e.
Verify
that
the
task
server
is
communicating
correctly
with
the
NetView
Command
Server
by
entering
the
following
command
on
the
task
server
workstation
from
a
bash
command
line
interface:
./hostcmd
"netvasis
pipe
unix
pwd
|
corrwait
30
|
console"
-h
hostname
where
hostname
is
the
IP
address
or
the
fully
qualified
host
name
of
the
proxy
mode
z/OS
system
on
which
the
command
is
to
be
executed.
The
hostcmd
command
displays
the
list
of
all
active
tasks
running
on
the
proxy
mode
z/OS
system.
Note:
NetView
communicates
with
UNIX
System
Services
through
the
NetView
UNIX
Command
Server.
This
server
must
be
running
to
enable
communication.
Additional
Information:
Successful
output
consists
of
a
display
of
the
home
directory
of
the
NetView
operator
ID
that
was
used
to
run
the
command,
such
as
in
this
example:
/u/oper1.
If
verification
fails,
ensure
that
the
following
conditions
are
true
before
you
attempt
to
verify
communication
again:
v
Proper
host
name
authorization
exists.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Problem
Determination
Guide
for
more
information.
v
Other
authorization
and
security
setup
is
correct.
If
you
use
a
Resource
Access
Control
Facility
(RACF)
security
system,
check
the
authorizations
and
setup.
v
NetView
UNIX
Command
Server
is
started,
as
described
in
Step
4.
Chapter
11.
Installing
and
configuring
for
z/OS
143
144
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Appendix
A.
Patches
and
fix
packs
This
appendix
divides
required
patches
and
fix
packs
into
two
groups:
v
Patches
and
fix
packs
that
the
installer
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installs
automatically.
(If
you
are
installing
the
product
from
the
Tivoli
desktop
or
command
line,
see
Chapter
6,
“Installing
or
upgrading
the
product
manually
in
an
existing
Tivoli
environment,”
on
page
71
for
information
on
how
to
install
these
patches.)
v
Patches
that
you
must
install
for
the
required
and
optional
software
for
the
product.
Patches
and
fix
packs
that
the
installer
installs
Table
42.
Specifications
of
required
patches
that
the
installer
installs
automatically
Software
release
Patch
or
fix
pack
name
Prerequisite
patches
Purpose
Tivoli
Management
Framework,
Version
4.1
4.1-TMF-0013
—
—
4.1-TMF-0014
—
—
Tivoli
Management
Framework,
Version
3.7.1
The
installer
installs
the
Version
3.7.1
patches,
as
required,
if
you
are
performing
a
Typical
installation
and
choose
to
remain
at
Version
3.7.1
3.6.1-TMF-0034
—
Linux
support
3.6.1-TMF-0062
3.6.1-TMF-0034
Linux
support
3.7-TMF-0021
3.6.1-TMF-0034
&
–0062
Linux-390
support
3.7-TMF-0035
—
Linux
support
3.7-TMF-0043
—
OS/400
support
3.7.1-TMF-0059
—
—
3.7.1-TMF-0066
—
—
3.7.1-TMF-0073
—
—
3.7.1-TMF-0074A
—
—
3.7.1-TMF-0083
3.7.1-TMF-0073
—
3.7.1-TMF-0087
3.7.1-TMF-0073
—
3.7.1-TMF-0097
—
—
3.7.1-TMF-0099
—
—
3.7.1-TMF-0114
3.7.1-TMF-0097
—
IBM
Tivoli
Monitoring,
Version
5.1.1
–
Fix
Pack
5
5.1.1–ITM-FP05
—
—
©
Copyright
IBM
Corp.
2003
145
Patches
and
fix
packs
that
you
must
install
Table
43.
Specifications
of
required
patches
for
other
required
and
optional
software
Software
release
Patch
or
fix
pack
name
Tivoli
Enterprise
Data
Warehouse,
Version
1.1
v
Fix
Pack
1.1-TDW-FP02
v
efix
1.1-TDW-0011LA
v
efix
1.1-TDW-0013LA
For
DBCS
systems,
an
additional
fix
pack
is
required.
See
the
IBM
Support
and
downloads
Web
site
at
www.ibm.com/support
for
additional
information.
Database
support
for
the
Tivoli
Enterprise
Data
Warehouse:
IBM
DB2
Universal
Database
Enterprise
Edition,
Version
7.2
v
IBM
DB2
Universal
Database
Enterprise
Edition,
Version
7.2,
Fix
Pack
8
v
efix
1.1-TDW-0002
IBM
Tivoli
Monitoring
Warehouse
Enablement
Pack
This
software
is
required
to
enable
Tivoli
Enterprise
Data
Warehouse.
5.1.1-ITM-FP05
Install
Patch
5.1.1-ITM-FP05
in
both
your
IBM
Tivoli
Monitoring
application
and
the
Tivoli
Enterprise
Data
Warehouse
environment.
If
you
are
using
the
installer,
this
patch
is
automatically
installed
with
IBM
Tivoli
Monitoring.
IBM
Tivoli
Enterprise
Console,
Version
3.7.1,
3.8,
or
3.9
v
Version
3.7.1
requires
Fix
Pack
3.7.1-TEC-FP04
v
Version
3.8
requires
Fix
Pack
3.8-TEC-FP01
Tivoli
Inventory,
Version
4.0
or
IBM
Tivoli
Configuration
Manager,
Version
4.2
Tivoli
Inventory
is
part
of
the
IBM
Tivoli
Configuration
Manager,
Version
4.2
product.
Formerly,
Tivoli
Inventory
(Version
4.0
and
prior
releases)
was
a
separate
product.
3.7.1-CLL-0002
This
patch
adds
Linux-x86
endpoints
to
MCollect
for
use
with
Tivoli
Inventory
4.0.
It
depends
on
Tivoli
Management
Framework,
Version
3.7.1.
Tivoli
Business
Systems
Manager,
Version
1.5
or
2.1.1
Version
1.5
requires
TBSM
Patch
35
Version
2.1.1
requires
Fix
Pack
2.1.1-BSM-0001
Tivoli
Business
Systems
Manager
Event
Enablement,
Version
1.5
or
2.1.1
The
following
patch
is
required
for
Tivoli
Business
Systems
Manager
Event
Enablement,
Version
1.5,
to
enable
communication
with
z/OS
systems:
1.5-BSM-0038
The
following
patches
are
required
if
you
install
Tivoli
Business
Systems
Manager
Event
Enablement
on
the
IBM
Tivoli
Enterprise
Console
to
support
the
forwarding
of
events
to
Tivoli
Business
Systems
Manager:
v
Version
1.5
requires
Patch
1.5-BSM-0043.
v
Version
2.1.1
requires
Fix
Pack
2.1.1-BSM-0004.
146
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Appendix
B.
Icons
and
options
in
the
Step
List
window
The
following
table
describes
the
icons
and
options
that
are
displayed
in
the
Step
List
window.
The
Step
List
window
is
displayed
in
the
installer
when
installation
is
about
to
begin.
For
troubleshooting
procedures
for
the
Step
List
window,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Problem
Determination
Guide.
Table
44.
Status
icons
and
options
for
the
Step
List
window
of
the
installer
Name
Icon
Value
Status
icons
in
the
Step
List
Pending
None
The
step
has
not
been
run
yet.
Passed
The
step
completed
successfully.
Passed_Reboot
The
step
completed
successfully
and
you
must
reboot
the
system.
This
status
causes
the
installer
to
prompt
you
to
restart
the
computer.
Passed_Warning
The
step
completed
with
one
or
more
warnings.
For
example,
the
installer
might
warn
you
to
restart
computers
on
which
you
installed
the
Web
Health
Console.
Otherwise,
the
console
is
not
activated.
The
installer
might
also
list
warnings
from
the
installation
logs
of
the
Tivoli
Management
Framework.
You
can
consult
the
documentation
that
comes
on
the
installation
CDs
for
Tivoli
Management
Framework
for
information
on
this
type
of
warning.
Also
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Problem
Determination
Guidefor
information
on
error
logs.
Failed
The
step
failed.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Problem
Determination
Guide
for
instructions
on
how
to
analyze
and
handle
failed
steps.
Deferred
The
step
was
postponed.
This
icon
is
displayed
after
you
defer
a
step
in
the
Detail
window,
as
described
near
the
end
of
the
installation
procedure.
See
the
description
of
Defer
in
this
table
for
more
information.
Locked
The
step
will
be
skipped
because
it
is
dependent
on
a
previous
step
that
has
been
deferred.
The
only
way
a
locked
step
can
be
unlocked
is
to
enable
(or
″un-defer″)
all
steps
on
which
the
locked
step
is
dependent.
To
see
a
list
of
these
dependencies,
double-click
the
locked
step
and
read
the
error
message
in
its
Detail
window.
Breakpoint
The
step
was
placed
in
breakpoint
mode.
The
installer
stops
processing
steps
at
the
breakpoint.
You
can
check
progress
and
change
settings,
if
necessary.
Options
Defer/Enable
Postpones
the
step
to
a
later
time.
If
a
step
has
failed,
you
can,
as
a
last
resort,
defer
the
step.
After
that,
the
only
way
to
reactivate
that
step
is
by
pressing
Execute
(see
description
below).
If
you
defer
a
step
before
it
is
executed
(such
as
when
it
has
a
″Pending″
status),
you
can
enable
the
step.
The
Defer
option
turns
into
Enable,
allowing
you
to
return
its
status
from
″Deferred″
to
″Pending.″
If
subsequent
steps
are
dependent
on
a
deferred
step,
they
will
automatically
be
locked.
A
locked
step
cannot
be
run.
For
instance,
if
you
defer
a
step
for
creating
a
managed
node,
all
other
steps
that
install
to
that
managed
node
would
be
locked,
since
they
are
dependent
upon
its
creation.
These
locked
steps
would
only
be
reset
when
the
deferred
step
changes
status.
©
Copyright
IBM
Corp.
2003
147
Table
44.
Status
icons
and
options
for
the
Step
List
window
of
the
installer
(continued)
Name
Icon
Value
Toggle
Breakpoint
Activate
or
Deactivate
the
breakpoint.
If
you
activate
the
breakpoint,
the
automatic
installation
process
is
interrupted
when
it
reaches
that
step
and
you
are
asked
for
input.
If
you
want
the
installer
to
pause
after
specific
steps
are
complete,
activate
a
breakpoint
on
the
subsequent
step.
For
example,
you
can
set
a
breakpoint
to
enable
installation
of
proxy
endpoints
as
described
in
“Creating
a
Windows
proxy
endpoint”
on
page
67.
OK
Returns
to
the
previous
window.
Execute
Executes
a
deferred
step
that
occurs
prior
to
the
current
step.
After
the
completion
of
the
deferred
step,
any
locked
steps
that
were
dependent
on
this
step
change
to
the
″Pending″
status.
Click
Run
Steps
on
the
Step
List
to
run
the
subsequent
steps.
Change
Enables
you
to
make
the
following
types
of
change:
v
Change
the
user
ID
or
password.
v
Change
the
destination
directory
for
the
creation
of
a
managed
node
or
endpoint.
Note:
Some
steps
do
not
have
Change
as
an
active
option.
Steps
that
do
have
Change
as
an
option
include
managed
node
and
endpoint
creation.
148
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Appendix
C.
Uninstalling
the
product
This
section
describes
how
to
uninstall
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Objective
To
uninstall
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
product
from
a
specified
node
or
from
the
entire
Tivoli
management
region.
Background
information
Before
you
can
uninstall
IBM
Tivoli
Monitoring,
you
must
first
uninstall
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
components.
Use
Tivoli
command-line
procedure
to
uninstall
the
product
at
the
end
of
the
product’s
life
cycle.
Note:
For
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
z/OS
systems,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Program
Directory
for
information
about
using
SMP/E
to
uninstall
the
product.
After
using
SMP/E,
you
must
remove
the
/var/itmwas
and
/usr/sbin/collectorStart
directories
and
their
contents.
Required
authorization
role
apachewebserver_super,
iiswebserver_super,
iplanetwebserver_super,
websphereappsvr_super,
weblogic_super
For
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,
you
must
be
a
IBM
WebSphere
Application
Server
administrator
with
super-user
permissions.
Before
you
begin
Apache
HTTP
Server-specific
information:
Note
that
on
Windows
the
uninstallation
process
does
not
remove
on
the
endpoint
machine
the
services
created
for
the
different
instances
of
Apache
HTTP
Server
running.
Refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
User’s
Guide,
Appendix
C,
″Problem
determination,″
for
details
about
how
to
stop
and
deregister
these
services.
IBM
WebSphere
Application
Server-specific
information:
Remove
the
following
files
or
directories
from
endpoints
before
uninstalling
the
product:
v
Remove
the
$LCF_DATDIR/LCFNEW/IZY
directory
and
its
contents.
This
removes
the
log
files
from
the
endpoint.
v
Remove
the
$LCF_DATDIR/../../bin/generic_unix/TME/WSAPPSVR
directory
and
its
contents.
v
Remove
the
$LCF_DATDIR/../../bin/$INTERP/TME/WSAPPSVR
directory
and
its
contents.
v
Remove
$LCF_DATDIR/../../generic/msg_cat/C/itmwas*.cat.
v
Remove
$LCF_DATDIR/../../generic/msg_cat/C/WebSphereAS*.cat.
v
Remove
$LCF_DATDIR/../../generic/msg_cat/C/WebSphere_Msg*.cat.
©
Copyright
IBM
Corp.
2003
149
When
you
finish
None
Procedure
You
can
perform
this
command
from
the
bash
command
line
only.
Command
line:
Use
wuninst.
Enter
one
or
more
of
the
following
commands.
The
example
below
removes
all
product
files
from
the
Tivoli
management
region
server
and
throughout
the
Tivoli
management
region:
wuninst
ITMWIAPACHE
<TMR_name>
-rmfiles
wuninst
ITMWIIIS
<TMR_name>
-rmfiles
wuninst
ITMWIIPLANET
<TMR_name>
-rmfiles
wuninst
ITMWAS
<TMR_name>
-rmfiles
wuninst
ITMWLS
<TMR_name>
-rmfiles
where
<TMR_name>
is
the
name
of
the
Tivoli
management
region
server.
Run
the
following
command
to
verify
that
IBM
Tivoli
Monitoring
for
Web
Infrastructure
has
been
successfully
uninstalled:
wlsinst
-h
-p
For
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,
if
you
created
custom
policy
regions,
you
might
receive
the
following
error
messages
when
you
attempt
to
uninstall
the
product:
FRWSL0024E
A
failure
was
detected
by
the
oserv
daemon:
FRWOG0040E
Transaction
Error
Error
in
$DBDIR/IZY/logs/trace_itmwas_uninstall_prod.log:
+
wdel
@PolicyRegion:<Policy_Region_Name>
FRWSL0002E
An
invalid
internal
parameter
found:
FRWOG0006E
named
resource
already
exists
Please
refer
to
the
TME
10
Framework
Planning
and
Installation
Guide,
"TME
Maintenance
and
Troubleshooting"
for
details
on
diagnosing
internal
errors
or
contact
your
Tivoli
support
provider.
The
uninstall
command
removes
only
profile
managers
directly
under
the
Monitoring
for
WebSphere
Application
Server
policy
region.
Because
the
profile
manager
is
not
deleted
under
the
new
policy
region,
the
command
to
delete
the
policy
region
fails
because
the
policy
region
is
not
empty.
Manually
delete
the
profile
managers
and
the
policy
region,
including
the
Monitoring
for
WebSphere
Application
Server
policy
region.
Then
run
the
following
commands:
wdel
@ProductInfo:ITMWAS
wchkdb
-u
Note:
You
must
perform
these
steps
before
you
can
reinstall
the
product.
150
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Appendix
D.
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.
2003
151
IBM
may
use
or
distribute
any
of
the
information
you
supply
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
Licensees
of
this
program
who
wish
to
have
information
about
it
for
the
purpose
of
enabling:
(i)
the
exchange
of
information
between
independently
created
programs
and
other
programs
(including
this
one)
and
(ii)
the
mutual
use
of
the
information
which
has
been
exchanged,
should
contact:
IBM
Corporation
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.
You
may
copy,
modify,
and
distribute
these
sample
programs
in
any
form
without
payment
to
152
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
IBM
for
the
purposes
of
developing,
using,
marketing,
or
distributing
application
programs
conforming
to
IBM’s
application
programming
interfaces.
Each
copy
or
any
portion
of
these
sample
programs
or
any
derivative
work,
must
include
a
copyright
notice
as
follows:
©
(your
company
name)
(year).
Portions
of
this
code
are
derived
from
IBM
Corp.
Sample
Programs.
©
Copyright
IBM
Corp.
_enter
the
year
or
years_.
All
rights
reserved.
If
you
are
viewing
this
information
in
softcopy
form,
the
photographs
and
color
illustrations
might
not
appear.
Trademarks
AIX,
IBM,
the
IBM
logo,
OS/400,
OS/390,
Tivoli,
the
Tivoli
logo,
Tivoli
Enterprise
Console,
WebSphere,
and
z/OS
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States,
other
countries,
or
both.
Microsoft,
Windows,
Windows
NT,
and
the
Windows
logo
are
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,
all
Java-based
trademarks,
and
Solaris
Operating
Environment
are
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States,
other
countries,
or
both.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
Appendix
D.
Notices
153
154
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
Index
Special
characters.
/etc/Tivoli/setup_env.sh
command
74
Aaccessibility
xiv
Apache
HTTP
ServerIBM
HTTP
Server,
supported
version
24
supported
operating
systems
for
endpoints
20
supported
version
24
uninstalling
149
architecture
of
Tivoli
environmentfor
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
129
Bbacking
upTivoli
management
region
30
booksfeedback
x
online
x
ordering
x
see
publications
xiii
Ccommand
lineuser
interface
options
73
command
line
installation
1,
71
commands.
/etc/Tivoli/setup_env.sh
74
QALWOBJRST
122
RSTLICPGM
122
RSTOBJ
122
source
/etc/Tivoli/setup_env.csh
74
special
characters
xv
syntax
xv
tivoli
74
w4inslcf.pl
120,
121
winstall
76
winstlcf
107
wlookup
-a
-r
ManagedNode
76
wlsinst
-ah
81
wpatch
82
communication
between
task
server
and
z/OS,
starting
141
configuringIBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
135
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
134
configuring
(continued)IBM
Tivoli
NetView
for
z/OS
134,
135
security
server
inproxy
mode
z/OS
135
task
server
for
proxy
mode
z/OS
138
timeouts
for
Tivoli
gateways
132
conventionstypeface
xiv
customer
supportsee
software
support
xiv
Ddirectory
names,
notation
xv
disk
space
requirements
28
Eendpoint
installingusing
Tivoli
Management
Agent
Wizard
for
106
endpointschanging
gateway
assignment
109
creating
63
installing
105
Windows
proxy
endpoint,
creating
67
environment
variables,
notation
xv
Evaluation
installation
51
reasons
to
use
1
Expanding
your
Tivoli
environment
101
Ffiles
os4LcfH.err
121
Ggateway
assignment,
changing
for
endpoints
109
HHP-UX,
JRE
requirements
27
IIBM
HTTP
Server,
supported
version
24
IBM
Tivoli
Monitoring
23
installing
manually
74
manual
installation
74
manual
installation
requirements
75
IBM
Tivoli
Monitoring
Component
Services
23
IBM
Tivoli
Monitoring
Component
Services
(continued)installing
manually
74
manual
installation
74
manual
installation
requirements
75
IBM
Tivoli
Monitoring
for
Web
Infrastructureinstallation
and
setup
guidelines
15
overview
1
uninstalling
149
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
24
manual
installation
requirements
75
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Apache
HTTP
Server
resource
models
113
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
24
manual
installation
requirements
75
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Internet
Information
Server
resource
models
114
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
iPlanet
Web
Server
24
manual
installation
requirements
76
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
24
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebLogic
Servermanual
installation
requirements
75
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
24
JRE
requirements
87
manual
installation
requirements
75
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
resource
models
116
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks
117
IBM
Tivoli
Monitoring
Web
Health
Console
26
IBM
Tivoli
NetView
for
z/OS,
configure
134
IBM
Tivoli
NetView
for
z/OS,
configure
security
135
IBM
Tivoli
NetView
requirements
25
IBM
WebSphere
Application
ServerJRE
requirements
87
OS/390
endpoints
129
OS/400
endpoints
119
required
fixes
26
supported
operating
systems
for
endpoints
21
supported
versions
24
Tivoli
Enterprise
Data
Warehouse
fix
pack
94
uninstalling
from
149
z/OS
endpoints
129
©
Copyright
IBM
Corp.
2003
155
installationbacking
up
the
Tivoli
management
region
30
choosing
a
method
1
disk
space
requirements
28
endpoints,
installing
105
Evaluation
method
1,
51
from
the
command
line
1,
71
from
the
Tivoli
desktop
1,
71
guidelines
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
15
language
requirements
30
language
support
96
managed
nodes,
installing
101
manual
71
optional
software
23
patches
145
planning
19
planning
sheets
34
prerequisites
23
recommended
environment
29
required
permissions
and
privileges
29
required
software
23
resource
models,
enabling
88
resources,
definitions
and
planning
for
34
setup
and
access
Tivoli
environment
73
supported
operating
systems
19
Tivoli
Enterprise
Data
Warehouse
91
Tivoli
patches,
installing
manually
78
Tivoli
Software
Installation
Service
2
Typical
method
1,
57
upgrades
30
verifying
86
verifying
required
software
is
running
32
Web
Health
Console
110
installation
wizard
1
using
57
installingendpoints
105
files
to
enable
Tivoli
Enterprise
Data
Warehouse
91
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS
134
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
proxy
mode
z/OS,
overview
129
task
server
for
proxy
mode
z/OS
communication
136
Tivoli
software
manually
74
command
line
76
Tivoli
desktop
77
installing
endpointusing
Tivoli
Management
Agent
Wizard
for
106
Internet
Information
Serversupported
operating
systems
for
endpoints
20
supported
versions
24
iPlanet
Web
Serversupported
operating
systems
for
endpoints
20
supported
version
24
JJava
runtime
environmentHP-UX
requirements
27
installing
87
linking
to
existing
87
Java
Runtime
environmentrequired
versions
24
Llanguage
requirements
30
language
supportinstalling
96
Mmanaged
nodedisplaying
list
76
managed
node,
creating
61
manual
installation
71
base
product
and
component
software
74
fix
packs
and
upgrades
78
creating
Windows
proxy
endpoint
67
endpoints,
installing
105
guidelines
71
managed
nodes,
installing
101
on
managed
nodes
74
on
Tivoli
management
region
server
74
overview
of
procedures
71
product
and
component
software
75
road
map
71
Tivoli
fix
packs
78
command
line
82
Tivoli
desktop
82
Tivoli
Management
Framework
patches
78
Tivoli
patches
78
command
line
82
Tivoli
desktop
82
Tivoli
software
74
command
line
76
Tivoli
desktop
77
Tivoli
upgrades
78
command
line
82
Tivoli
desktop
82
Web
Health
Console
110
when
adding
computers
71
manualsfeedback
x
online
x
ordering
x
see
publications
xiii
Microsoft
Windows
Management
Instrumentation
(WMI)
24
migrating
113
Tivoli
Manager
for
WebSphere
Application
Server
tasks
117
migrating
(continued)Tivoli
Manager
for
WebSphere
Application
Server
tasks
to
resource
models
116
Tivoli
Manager
for
WebSphere
Application
Server
to
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
115
Tivoli
Web
Component
Manager
to
IBM
Tivoli
Monitoring
113
mof
files
88
NNetView,
see
IBM
Tivoli
NetView
134,
135
notationenvironment
variables
xv
path
names
xv
typeface
xv
Oonline
publicationsaccessing
xiii
operating
systemsAIX,
supported
versions
19,
20,
21
HP-UX,
supported
versions
19,
20,
21
Linux,
supported
versions
20,
21
Microsoft
Windows,
supported
versions
19,
20,
21,
23
Sun
Solaris
Operating
Environment,
supported
versions
19,
20,
21
ordering
publications
xiii
OS/390,
see
z/OS
systems
129
OS/400
endpoints
119
installing
119
removing
from
a
system
126
starting
122
stopping
125
os4LcfH.err
file
121
Ppatches
145
installed
by
deployment
145
that
you
must
install
146
path
names,
notation
xv
permissions
and
privileges
29
planning
19
planning
sheets
34
endpoint
38
managed
node
37
proxy
managed
objects
40
port
numbers
for
endpoints
69,
107
prerequisite
software
23
proxy
endpoints
4
for
z/OS
systems
131
proxy
mode
z/OS
systemsinstalling
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
129
publicationsaccessing
online
xiii
online
x
156
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
publications
(continued)ordering
x,
xiii
submitting
feedback
about
x
QQALWOBJRST
command
122
Rrequired
softwareverifying
32
resource
models,
enabling
88
RSTLICPGM
command
122
RSTOBJ
command
122
Sscripts
setup_env.csh
74
setup_env.sh
74
security
server
in
proxy
mode
z/OS
135
setup_env.csh
script
74
setup_env.sh
script
74
software
supportcontacting
xiv
source
/etc/Tivoli/setup_env.csh
command
74
Ttask
serverconfiguring
for
proxy
mode
z/OS
systems
138
installing
136
timeouts
for
Tivoli
gateways,
configuring
132
Tims2XML
113
Tivoli
Adapter
Configuration
Facility
27
Tivoli
Business
Systems
Manager
27
Tivoli
Business
Systems
Manager
Event
Enablement
27
tivoli
command
74
Tivoli
desktopand
manual
installation
71
user
interface
options
73
Tivoli
Enterprise
Console
27
Tivoli
Enterprise
Data
Warehouse
26
enablement
files
91
installing
91
Tivoli
environmentaccessing
73
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
for
z/OS
129
logon
screen
74
setting
up
73
Tivoli
fix
packs,
manually
installing
78
Tivoli
gateways,
configuring
timeouts
132
Tivoli
logon
screen
74
Tivoli
Management
Agent
Wizardusing
to
install
endpoint
106
Tivoli
Management
Framework
23
accessing
73
Tivoli
Management
Framework
(continued)and
manual
installation
71
manually
installing
software
for
78
patches,
manually
installing
78
purpose
73
set
up
and
start
of
the
Tivoli
environment
73
Tivoli
management
regionarchitecture
for
z/OS
129
backing
up
30
server
74
Tivoli
Manager
for
WebSphere
Application
Server
115,
116
Tivoli
Manager
for
WebSphere
Application
Server
tasks
117
Tivoli
NetView,
see
IBM
Tivoli
NetView
134,
135
Tivoli
patches,
manually
installing
78
Tivoli
Software
Distribution
27
Tivoli
software
information
center
xiii
Tivoli
Software
Installation
Service
2,
27
Tivoli
software,
manual
installation
74
command
line
76
Tivoli
desktop
77
Tivoli
upgrades,
manually
installing
78
Tivoli
Web
Component
Managermapping
tasks
with
Apache
HTTP
Server
resource
models
113
mapping
tasks
with
Internet
Information
Server
resource
models
114
migrating
to
IBM
Tivoli
Monitoring
113
tmd
RIM
databaseuninstalling
149
typeface
conventions
xiv
Typical
installation
57
reasons
to
use
1
Uuninstalling
IBM
Tivoli
Monitoring
for
Web
Infrastructure
149
UNIXcron
utility
73
logon
procedure
74
upgrades
30
upgradingoverview
78
procedure
82
user
interface
optionscommand
line
73
Tivoli
desktop
73
Tivoli
Management
Framework
73
Vvariables,
notation
for
xv
Ww4inslcf.pl
command
120,
121
Web
Health
Consoleinstalling
manually
110
Web
Health
Console
(continued)updating
99
WebLogic
Serversupported
operating
systems
for
endpoints
23
supported
version
24
WebSphere
Application
Serversupport
for
version
3.5.6
and
3.5.7
90
Windowslogon
procedure
74
Microsoft
Windows
Script
Host
26
ODBC
driver
for
Microsoft
Access
2000
25
Windows
proxy
endpoint,
manually
creating
67
winstall
command
76
winstlcf
command
107
wlookup
-a
-r
ManagedNode
command
76
wlsinst
-ah
command
81
wpatch
command
82
Zz/OS
endpointsrequired
level
of
Java
26
z/OS
security
server
in
proxy
mode
135
z/OS
systemsconfiguring
communication
for
proxy
mode
138
configuring
security
in
proxy
mode
135
installing
proxy
mode
134
installing
the
task
server
for
proxy
mode
136
proxy
endpoints
4
proxy
mode
architecture
129
requirements
25
starting
communication
on
proxy
mode
141
updating
permissions
on
proxy
mode
132
Index
157
158
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
Installation
and
Setup
Guide
����
Part
Number:
CT171IE
Printed
in
USA
SC32-1435-00
(1P)
P/N:
CT17
1IE
