t l tivoli monitoring for messaging and ... -...
TRANSCRIPT
Tivoli® IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
User’s
Guide
Version
5.1.2
SC32-9110-00
���
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
Appendix
C,
“Notices,”
on
page
79.
First
Edition
(July
2004)
This
edition
applies
to
version
1,
release
5,
modification
2
of
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
2004.
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
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. ix
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
library
. ix
Prerequisite
publications
.
.
.
.
.
.
.
.
. x
Related
publications
.
.
.
.
.
.
.
.
.
.
. x
Accessing
publications
online
.
.
.
.
.
.
.
. x
Ordering
publications
.
.
.
.
.
.
.
.
.
. xi
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. xi
Tivoli
technical
training
.
.
.
.
.
.
.
.
.
. xi
Contacting
IBM
Software
Support
.
.
.
.
.
.
. xi
Determine
the
business
impact
of
your
problem
xii
Describe
your
problem
and
gather
background
information
.
.
.
.
.
.
.
.
.
.
.
.
. xii
Submit
your
problem
to
IBM
Software
Support
xiii
Searching
knowledge
bases
.
.
.
.
.
.
.
. xiii
Obtaining
fixes
.
.
.
.
.
.
.
.
.
.
.
. 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
Administrators
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Authorization
roles
.
.
.
.
.
.
.
.
.
.
.
. 2
User
interface
options
.
.
.
.
.
.
.
.
.
.
. 2
Chapter
2.
Quick-reference
to
common
user
scenarios
.
.
.
.
.
.
.
.
.
.
.
. 3
Monitoring
the
availability
of
servers
in
the
Microsoft
Exchange
organization
.
.
.
.
.
.
.
.
.
.
. 3
Ensuring
that
Microsoft
Exchange
servers
are
configured
and
running
efficiently
.
.
.
.
.
.
. 4
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Accessing
the
Tivoli
Management
Framework
environment
.
.
.
.
.
.
.
.
.
.
.
.
.
. 8
Setting
authorization
roles
.
.
.
.
.
.
.
.
.
. 9
Configuring
Microsoft
Exchange
servers
to
communicate
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 10
Creating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects
.
. 16
Configuring
authentication
for
Tivoli
objects
.
.
. 19
Creating
profiles
and
profile
managers
.
.
.
.
. 20
Subscribing
resources
to
profile
managers
.
.
.
. 21
Adding
a
resource
model
to
a
profile
manager
.
. 22
Distributing
profiles
.
.
.
.
.
.
.
.
.
.
. 24
Configuring
the
IBM
Tivoli
Enterprise
Console
event
server
.
.
.
.
.
.
.
.
.
.
.
.
.
. 26
Chapter
4.
Monitoring
Microsoft
Exchange
Server
with
resource
models
29
Resource
model
concepts
.
.
.
.
.
.
.
.
.
. 29
Monitoring
performance
and
availability
.
.
.
. 31
Monitoring
the
availability
of
servers
.
.
.
.
. 31
Monitoring
the
performance
of
Microsoft
Exchange
components
.
.
.
.
.
.
.
.
.
. 32
Monitoring
alerts
and
events
.
.
.
.
.
.
.
. 33
Monitoring
Microsoft
Exchange
Server
alerts
.
. 33
Viewing
events
with
IBM
Tivoli
Enterprise
Console
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 34
Chapter
5.
Customizing
resource
models
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 35
Customizing
indications
and
events
.
.
.
.
.
. 35
Specifying
a
response
task
for
an
indication
.
.
. 36
Notifying
administrators
when
an
event
occurs
.
. 37
Customizing
parameters
.
.
.
.
.
.
.
.
.
. 38
Scheduling
when
a
resource
model
runs
.
.
.
.
. 39
Logging
data
for
a
resource
model
.
.
.
.
.
. 41
Managing
profiles
and
resource
models
.
.
.
.
. 42
Determining
which
resource
models
have
been
distributed
to
endpoints
.
.
.
.
.
.
.
.
.
. 43
Determining
which
resource
models
are
running
on
endpoints
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 44
Chapter
6.
Monitoring
performance
and
availability
with
tasks
and
jobs
.
.
.
. 45
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
.
. 45
Monitoring
with
tasks
.
.
.
.
.
.
.
.
.
.
. 46
Gathering
information
with
tasks
.
.
.
.
.
. 47
Starting
and
stopping
services
.
.
.
.
.
.
. 47
Running
a
task
.
.
.
.
.
.
.
.
.
.
.
.
. 48
Customizing
a
task
.
.
.
.
.
.
.
.
.
.
.
. 50
Creating
a
job
.
.
.
.
.
.
.
.
.
.
.
.
. 51
Running
a
job
.
.
.
.
.
.
.
.
.
.
.
.
. 53
Scheduling
a
job
.
.
.
.
.
.
.
.
.
.
.
.
. 54
Chapter
7.
Tracking
the
performance
of
Microsoft
Exchange
servers
.
.
.
.
. 57
Creating
a
report
about
space
usage
.
.
.
.
.
. 57
Creating
a
report
about
inactivity
.
.
.
.
.
.
. 58
IBM
Tivoli
Data
Warehouse
reports
.
.
.
.
.
. 59
Chapter
8.
Working
with
Tivoli
objects
63
Viewing
Microsoft
Exchange
server
object
properties
63
©
Copyright
IBM
Corp.
2004
iii
Editing
Microsoft
Exchange
server
properties
.
.
. 65
Starting
Microsoft
Exchange
services
.
.
.
.
.
. 66
Stopping
Microsoft
Exchange
services
.
.
.
.
. 67
Chapter
9.
Using
Microsoft
Exchange
Server
utilities
to
address
problems
.
. 69
Appendix
A.
Integrating
with
IBM
Tivoli
Business
Systems
Manager
.
.
.
.
. 71
IBM
Tivoli
Business
Systems
Manager
overview
.
. 71
Prerequisites
.
.
.
.
.
.
.
.
.
.
.
.
.
. 72
Integrating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
with
IBM
Tivoli
Business
Systems
Manager
.
.
.
.
. 72
Configuring
the
IBM
Tivoli
Enterprise
Console
event
server
to
work
with
IBM
Tivoli
Business
Systems
Manager
.
.
.
.
.
.
.
.
.
.
.
. 73
Discovering
resources
for
IBM
Tivoli
Business
Systems
Manager
.
.
.
.
.
.
.
.
.
.
.
. 74
Working
with
IBM
Tivoli
Business
Systems
Manager
75
Uninstalling
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
from
IBM
Tivoli
Business
Systems
Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 75
Appendix
B.
Accessibility
.
.
.
.
.
. 77
Navigating
the
interface
using
the
keyboard
.
.
. 77
Magnifying
what
is
displayed
on
the
screen
.
.
. 77
Appendix
C.
Notices
.
.
.
.
.
.
.
.
. 79
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 80
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 81
iv
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Figures
1.
Application
proxy
object
properties
.
.
.
. 64
2.
Application
proxy
object
properties
—
edit
view
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 66
©
Copyright
IBM
Corp.
2004
v
vi
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Tables
1.
Guidelines
for
setting
up
the
product
.
.
.
. 7
2.
Working
with
resource
models
.
.
.
.
.
. 29
3.
Working
with
tasks
and
jobs
.
.
.
.
.
.
. 45
4.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
45
5.
Tasks
that
run
Microsoft
utilities
.
.
.
.
. 69
6.
Integrating
with
IBM
Tivoli
Business
System
Manager
.
.
.
.
.
.
.
.
.
.
.
.
. 71
©
Copyright
IBM
Corp.
2004
vii
viii
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
About
this
guide
The
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
User’s
Guide
provides
information
about
setting
up
and
using
the
IBM®
Tivoli®
Monitoring
for
Messaging
and
Collaboration:
Microsoft®
Exchange
Server
component
software
to
monitor
Microsoft
Exchange
servers.
Who
should
read
this
guide
This
guide
is
for
system
administrators
who
monitor
and
manage
Microsoft
Exchange
servers.
Readers
should
be
familiar
with
the
following
topics:
v
Microsoft
Exchange
server
and
services
v
and
message
routing
v
Tivoli
management
software
v
Microsoft
Windows®
operating
systems
v
IBM
Tivoli
Data
Warehouse
(optional)
v
IBM
Tivoli
Enterprise
Console®
(optional)
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
library
and
any
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online,
how
to
order
Tivoli
publications,
and
how
to
submit
comments
on
Tivoli
publications.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
library
The
following
publications
are
available
in
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
library:
v
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration
Installation
and
Setup
Guide
Provides
information
about
installing
and
configuring
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration
product.
v
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
Provides
information
about
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
to
monitor
your
Microsoft
Exchange
resource
models,
tasks,
and
commands.
v
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Problem
Determination
Guide
Provides
information
about
troubleshooting
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server,
including
error
and
informational
messages,
and
information
about
trace
and
log
files.
v
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Warehouse
Enablement
Pack
Implementation
Guide
©
Copyright
IBM
Corp.
2004
ix
Provides
information
about
configuring
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Warehouse
Enablement
Pack
to
work
with
IBM
Tivoli
Data
Warehouse.
Prerequisite
publications
To
use
the
information
in
this
book
effectively,
you
must
have
some
prerequisite
knowledge
of
IBM
Tivoli
Monitoring,
which
you
can
get
from
the
following
books:
v
IBM
Tivoli
Monitoring
User’s
Guide,
SC23-4567
Provides
an
overview
of
IBM
Tivoli
Monitoring,
especially
of
resource
models.
It
also
describes
how
to
use
the
user
interface.
v
IBM
Tivoli
Monitoring
Resource
Model
Builder
User’s
Guide,
SC23-5678
Describes
using
the
IBM
Tivoli
Monitoring
Resource
Model
Builder
to
create
and
customize
resource
models.
Related
publications
The
following
documents
also
provide
useful
information:
v
Microsoft
Exchange
Server
Administration
Guide
and
other
product
documentation
v
Tivoli
Management
Framework
User’s
Guide
v
Tivoli
Enterprise
Console
Installation
Guide
v
Tivoli
Management
Framework
Reference
Manual
v
Tivoli
Enterprise
Console
Event
Integration
Facility
User’s
Guide
v
Tivoli
Enterprise
Console
Reference
Manual
v
Tivoli
Enterprise
Console
Rule
Builder’s
Guide
v
IBM
IBM
Tivoli
Business
Systems
Manager
product
documentation
v
IBM
Tivoli
Data
Warehouse
product
documentation
v
IBM
Tivoli
Monitoring
product
documentation
v
Road
Map
for
the
Typical
Installation
Option
of
IBM
Tivoli
Monitoring
Products,
GI11-0959
v
Road
Map
for
Enabling
Tivoli
Enterprise
Data
Warehouse
for
IBM
Tivoli
Monitoring
Products
The
Tivoli
Software
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Software
Glossary
is
available,
in
English
only,
at
http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.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.
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.
x
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
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
Software
Support
Web
site
provides
the
latest
information
about
known
product
limitations
and
workarounds
in
the
form
of
technotes
for
your
product.
You
can
view
this
information
at
the
following
Web
site:
http://www.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/
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.
Tivoli
technical
training
For
Tivoli
technical
training
information,
refer
to
the
following
IBM
Tivoli
Education
Web
site:
http://www-306.ibm.com/software/tivoli/education/
Contacting
IBM
Software
Support
IBM
Software
Support
provides
assistance
with
product
defects.
Before
contacting
IBM
Software
Support,
your
company
must
have
an
active
IBM
software
maintenance
contract,
and
you
must
be
authorized
to
submit
problems
to
IBM.
The
type
of
software
maintenance
contract
that
you
need
depends
on
the
type
of
product
you
have:
v
For
IBM
distributed
software
products
(including,
but
not
limited
to,
Tivoli,
Lotus®,
and
Rational®
products,
as
well
as
DB2®
and
WebSphere®
products
that
run
on
Windows
or
UNIX
operating
systems),
enroll
in
Passport
Advantage
in
one
of
the
following
ways:
About
this
guide
xi
–
Online:
Go
to
the
Passport
Advantage®
Web
page
(http://www.lotus.com/services/passport.nsf/WebDocs/
Passport_Advantage_Home)
and
click
How
to
Enroll
–
By
phone:
For
the
phone
number
to
call
in
your
country,
go
to
the
IBM
Software
Support
Web
site
(http://techsupport.services.ibm.com/guides/contacts.html)
and
click
the
name
of
your
geographic
region.v
For
IBM
eServer
software
products
(including,
but
not
limited
to,
DB2
and
WebSphere
products
that
run
in
zSeries®,
pSeries®,
and
iSeries®
environments),
you
can
purchase
a
software
maintenance
agreement
by
working
directly
with
an
IBM
sales
representative
or
an
IBM
Business
Partner.
For
more
information
about
support
for
eServer
software
products,
go
to
the
IBM
Technical
Support
Advantage
Web
page
(http://www.ibm.com/servers/eserver/techsupport.html).
If
you
are
not
sure
what
type
of
software
maintenance
contract
you
need,
call
1-800-IBMSERV
(1-800-426-7378)
in
the
United
States
or,
from
other
countries,
go
to
the
contacts
page
of
the
IBM
Software
Support
Handbook
on
the
Web
(http://techsupport.services.ibm.com/guides/contacts.html)
and
click
the
name
of
your
geographic
region
for
phone
numbers
of
people
who
provide
support
for
your
location.
Follow
the
steps
in
this
topic
to
contact
IBM
Software
Support:
1.
Determine
the
business
impact
of
your
problem.
2.
Describe
your
problem
and
gather
background
information.
3.
Submit
your
problem
to
IBM
Software
Support.
Determine
the
business
impact
of
your
problem
When
you
report
a
problem
to
IBM,
you
are
asked
to
supply
a
severity
level.
Therefore,
you
need
to
understand
and
assess
the
business
impact
of
the
problem
you
are
reporting.
Use
the
following
criteria:
Severity
1
Critical
business
impact:
You
are
unable
to
use
the
program,
resulting
in
a
critical
impact
on
operations.
This
condition
requires
an
immediate
solution.
Severity
2
Significant
business
impact:
The
program
is
usable
but
is
severely
limited.
Severity
3
Some
business
impact:
The
program
is
usable
with
less
significant
features
(not
critical
to
operations)
unavailable.
Severity
4
Minimal
business
impact:
The
problem
causes
little
impact
on
operations,
or
a
reasonable
circumvention
to
the
problem
has
been
implemented.
Describe
your
problem
and
gather
background
information
When
explaining
a
problem
to
IBM,
be
as
specific
as
possible.
Include
all
relevant
background
information
so
that
IBM
Software
Support
specialists
can
help
you
solve
the
problem
efficiently.
To
save
time,
know
the
answers
to
these
questions:
v
What
software
versions
were
you
running
when
the
problem
occurred?
v
Do
you
have
logs,
traces,
and
messages
that
are
related
to
the
problem
symptoms?
IBM
Software
Support
is
likely
to
ask
for
this
information.
v
Can
the
problem
be
recreated?
If
so,
what
steps
led
to
the
failure?
v
Have
any
changes
been
made
to
the
system?
(For
example,
hardware,
operating
system,
networking
software,
and
so
on.)
xii
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
v
Are
you
currently
using
a
workaround
for
this
problem?
If
so,
please
be
prepared
to
explain
it
when
you
report
the
problem.
Submit
your
problem
to
IBM
Software
Support
You
can
submit
your
problem
in
one
of
two
ways:
v
Online:
Go
to
the
″Submit
and
track
problems″
page
on
the
IBM
Software
Support
site
(http://www.ibm.com/software/support/probsub.html).
Enter
your
information
into
the
appropriate
problem
submission
tool.
v
Do
you
have
logs,
traces,
and
messages
that
are
related
to
the
problem
symptoms?
IBM
Software
Support
is
likely
to
ask
for
this
information.
v
Can
the
problem
be
recreated?
If
so,
what
steps
led
to
the
failure?
v
Have
any
changes
been
made
to
the
system?
(For
example,
hardware,
operating
system,
networking
software,
and
so
on.)
v
Are
you
currently
using
a
workaround
for
this
problem?
If
so,
please
be
prepared
to
explain
it
when
you
report
the
problem.
If
the
problem
you
submit
is
for
a
software
defect
or
for
missing
or
inaccurate
documentation,
IBM
Software
Support
creates
an
Authorized
Program
Analysis
Report
(APAR).
The
APAR
describes
the
problem
in
detail.
Whenever
possible,
IBM
Software
Support
provides
a
workaround
for
you
to
implement
until
the
APAR
is
resolved
and
a
fix
is
delivered.
IBM
publishes
resolved
APARs
on
the
IBM
product
support
Web
pages
daily,
so
that
other
users
who
experience
the
same
problem
can
benefit
from
the
same
resolutions.
For
more
information
about
problem
resolution,
see
Searching
knowledge
bases
and
Obtaining
fixes.
Searching
knowledge
bases
If
you
have
a
problem
with
your
IBM
software,
you
want
it
resolved
quickly.
Begin
by
searching
the
available
knowledge
bases
to
determine
whether
the
resolution
to
your
problem
is
already
documented:
1.
Search
the
information
center
on
your
local
system
or
network.
2.
Search
the
Internet.
Search
the
information
center
on
your
local
system
or
network
IBM
provides
extensive
documentation
that
can
be
installed
on
your
local
machine
or
on
an
intranet
server.
You
can
use
the
search
function
of
this
information
center
to
query
conceptual
information,
instructions
for
completing
tasks,
reference
information,
and
support
documents.
Search
the
Internet
If
you
cannot
find
an
answer
to
your
question
in
the
information
center,
search
the
Internet
for
the
latest,
most
complete
information
that
might
help
you
resolve
your
problem.
To
search
multiple
Internet
resources
for
your
product,
expand
the
product
folder
in
the
navigation
frame
to
the
left
and
select
Support
on
the
Web.
From
this
topic,
you
can
search
a
variety
of
resources
including:
v
IBM
technotes
v
IBM
downloads
v
IBM
Redbooks
v
IBM
DeveloperWorks
v
Forums
and
newsgroups
v
About
this
guide
xiii
Obtaining
fixes
A
product
fix
might
be
available
to
resolve
your
problem.
You
can
determine
what
fixes
are
available
for
your
IBM
software
product
by
checking
the
product
support
Web
site:
1.
Go
to
the
IBM
Software
Support
Web
site
(http://www.ibm.com/software/support).
2.
Under
Products
A
-
Z,
select
your
product
name.
This
opens
a
product-specific
support
site.
3.
Under
Self
help,
follow
the
link
to
All
Updates,
where
you
will
find
a
list
of
fixes,
fix
packs,
and
other
service
updates
for
your
product.
For
tips
on
refining
your
search,
click
Search
tips.
4.
Click
the
name
of
a
fix
to
read
the
description
and
optionally
download
the
fix.
Tip:
To
receive
weekly
notifications
about
fixes
and
other
news
about
IBM
products,
follow
these
steps:
1.
From
the
support
page
for
any
IBM
product,
click
My
support
in
the
upper-right
corner
of
the
page.
2.
If
you
have
already
registered,
skip
to
the
next
step.
If
you
have
not
registered,
click
register
in
the
upper-right
corner
of
the
support
page
to
establish
your
user
ID
and
password.
3.
Sign
in
to
My
support.
4.
On
the
My
support
page,
click
Edit
profiles
in
the
left
navigation
pane,
and
scroll
to
Select
Preferences.
Select
a
product
family
and
check
the
appropriate
boxes
for
the
type
of
information
you
want.
5.
Click
Submit.
6.
For
notification
for
other
products,
repeat
Steps
4
and
5.
For
more
information
about
types
of
fixes,
see
the
Software
Support
Handbook
(http://techsupport.services.ibm.com/guides/handbook.html).
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
(for
example,
″Use
the
word
that
to
introduce
a
restrictive
clause.″)
v
New
terms
in
text
(except
in
a
definition
list)
v
Variables
and
values
you
must
provide
xiv
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Monospace
v
Code
and
other
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
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
1.
Overview
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
identifies,
notifies,
and
cures
common
problems
with
Microsoft
Exchange
2000
and
2003
servers.
The
component
software
includes
the
following
features:
Discovery
The
discovery
process
searches
your
Microsoft
Exchange
organization
(the
set
of
computers
running
Microsoft
Exchange
Server)
and
adds
them
to
the
Tivoli
monitoring
environment
to
ensure
you
are
managing
all
available
resources.
Availability
monitoring
Availability
resource
models
periodically
check
the
status
of
Microsoft
Exchange
servers
and
services
to
ensure
that
they
are
running.
You
can
configure
the
resource
models
to
customize
the
monitoring
cycle
and
to
change
the
triggering
thresholds.
You
can
also
use
tasks
to
monitor
the
availability
of
Microsoft
Exchange
services.
Performance
monitoring
Performance
resource
models
monitor
the
flow
of
messages
through
your
Microsoft
Exchange
organization.
If
there
is
a
spike
in
the
number
of
messages
or
if
a
queue
is
performing
poorly,
you
are
notified
and
can
take
preventive
measures
before
the
Microsoft
Exchange
server
is
unusable.
Operations
management
Tasks
enable
you
to
manage
your
Microsoft
Exchange
servers
on
a
daily
basis.
You
can
use
these
tasks
to
do
the
following:
v
View
information
about
the
configuration
of
mailboxes
and
folders
v
Create
reports
about
the
current
performance
of
the
servers
in
your
organization
The
following
sections
provide
additional
information
about
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
environment.
Administrators
Tivoli
administrators
are
system
or
Microsoft
Exchange
Server
administrators
who
have
the
authorization
to
perform
system
or
Microsoft
Exchange
Server
resource
management
tasks
using
the
Tivoli
monitoring
environment.
Each
administrator
or
group
of
administrators
is
represented
by
an
icon
on
the
Tivoli
desktop.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
fully
integrates
into
Tivoli
security.
To
perform
administration
functions,
administrators
must
have
authorization
roles
for
both
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
and
the
Tivoli
management
environment.
©
Copyright
IBM
Corp.
2004
1
Authorization
roles
Authorization
roles
determine
the
range
of
actions
an
administrator
can
perform.
You
assign
roles
to
administrators
so
they
can
perform
system
or
Microsoft
Exchange
Server
resource
management
tasks.
An
authorization
role
can
be
for
the
entire
Tivoli
management
region
or
a
specific
set
of
resources,
such
as
those
contained
in
a
policy
region.
Super,
senior,
admin,
and
user
are
examples
of
standard
authorization
roles.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
provides
the
following
additional
authorization
roles:
v
msexchgserver_user
v
msexchgserver_admin
User
interface
options
You
can
use
the
following
interfaces
to
work
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
v
The
Tivoli
desktop,
which
is
the
traditional
Tivoli
graphical
user
interface
(GUI)
v
The
command-line
interface
(CLI)
v
IBM
Tivoli
Monitoring
Web
Health
Console
to
monitor
the
health
of
resource
models
v
IBM
Tivoli
Enterprise
Console
to
work
with
event
management
v
IBM
Tivoli
Business
Systems
Manager
to
work
with
event
management
and
to
run
some
tasks
v
IBM
Tivoli
Data
Warehouse
to
gather
data
In
many
cases,
this
guide
provides
procedures
that
you
can
run
from
either
the
desktop
or
the
command-line
interface
(CLI).
You
can
choose
to
use
the
desktop
when
you
want
to
take
advantage
of
visual
input
prompting,
which
includes
drop-down
lists
of
options,
and
the
defaults
provided
by
options.
Use
the
command-line
interface
when
you
want
to
create
scripts,
set
tasks
to
respond
to
resource
models,
and
run
commands
directly.
2
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
2.
Quick-reference
to
common
user
scenarios
This
chapter
provides
quick-reference
material
to
accomplish
common
goals
for
using
this
product.
The
following
scenarios
provide
an
overview
of
the
high-level
steps
necessary
to
accomplish
each
common
goal:
v
“Monitoring
the
availability
of
servers
in
the
Microsoft
Exchange
organization”
v
“Ensuring
that
Microsoft
Exchange
servers
are
configured
and
running
efficiently”
on
page
4
Monitoring
the
availability
of
servers
in
the
Microsoft
Exchange
organization
The
following
table
outlines
the
steps
required
to
monitor
the
availability
of
the
servers
in
your
organization.
Overview
of
steps
Additional
information
Monitor
the
availability
of
Microsoft
Exchange
servers
Deploy
the
following
resource
models:
v
Availability
v
Reachability
v
Space
usage
v
Queues
v
Message
volume
These
resource
models
monitor
the
availability
of
Microsoft
Exchange
servers.
See
“Monitoring
performance
and
availability”
on
page
31
for
information
about
configuring
and
deploying
these
resource
models.
Configure
response
tasks
to
automatically
address
availability
issues
Configure
the
Availability
resource
model
to
launch
the
StartExchangeServer
task
in
response
to
an
indication
that
a
service
is
down.
The
StartExchangeServer
task
automatically
attempts
to
restart
the
stopped
service.
See
“Specifying
a
response
task
for
an
indication”
on
page
36
for
information.
Monitor
your
environment
and
respond
to
alerts
Deploy
the
Logs
resource
model
to
monitor
the
Microsoft
Exchange
Server
event
logs
for
alerts.
Every
time
that
a
system
alert
is
logged
to
a
Microsoft
Exchange
log
file,
you
are
notified
in
the
IBM
Tivoli
Enterprise
Console
event
console.
See
“Monitoring
Microsoft
Exchange
Server
alerts”
on
page
33
for
information
about
the
Logs
resource
model.
Check
the
IBM
Tivoli
Enterprise
Console
event
console
regularly
for
notifications
regarding
changes
in
Microsoft
Exchange
servers.
See
the
IBM
Tivoli
Enterprise
Console
product
documentation
for
information
about
using
and
configuring
the
event
consoles.
See
“Viewing
events
with
IBM
Tivoli
Enterprise
Console”
on
page
34
for
additional
information
about
events.
Customize
existing
resource
models
Change
any
of
the
default
values
(such
as
monitoring
cycle
or
what
triggers
an
event)
to
match
the
monitoring
needs
of
your
Microsoft
Exchange
organization.
See
Chapter
5,
“Customizing
resource
models,”
on
page
35
for
information
about
customizing
existing
resource
models.
©
Copyright
IBM
Corp.
2004
3
Overview
of
steps
Additional
information
Create
custom
resource
models
based
on
the
specific
needs
of
the
organization
You
can
create
custom
resource
models
based
on
the
needs
of
your
Microsoft
Exchange
organization.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
information
about
the
data
collected
and
how
to
create
custom
resource
models.
Ensuring
that
Microsoft
Exchange
servers
are
configured
and
running
efficiently
The
following
table
outlines
the
steps
required
to
ensure
that
your
servers
are
running
efficiently.
Overview
of
steps
Additional
information
Monitor
the
flow
of
messages
through
the
organization
Deploy
the
following
resource
models:
v
Queues
v
Message
volume
v
Mailbox
monitors
These
resource
models
monitor
the
flow
of
messages
through
your
Microsoft
Exchange
organization.
See
“Monitoring
performance
and
availability”
on
page
31
for
information
about
configuring
and
deploying
these
resource
models.
View
information
about
mailboxes,
folders,
and
servers
in
the
organization
View
information
about
current
space
usage
for
mailboxes
and
folders.
Use
the
MailboxInfo
task
to
display
information
about
mailboxes
and
folders.
Use
the
DisplayExchangeServerStatus
task
to
display
information
about
the
Microsoft
Exchange
services
installed
on
the
server.
See
“Gathering
information
with
tasks”
on
page
47
for
information.
Create
reports
about
any
resources
that
are
approaching
or
exceeding
limits
Create
a
report
about
the
current
space
consumption
by
mailboxes
and
folders.
See
“Creating
a
report
about
space
usage”
on
page
57
for
information.
This
report
provides
details
about
which
mailboxes
and
folders
are
consuming
the
most
space
on
the
Microsoft
Exchange
server.
Create
a
report
about
mailboxes
and
folders
that
are
no
longer
being
used.
See
“Creating
a
report
about
inactivity”
on
page
58
for
information.
This
report
identifies
mailboxes
and
folders
that
you
can
remove.
Use
the
IBM
Tivoli
Data
Warehouse
reports
to
analyze
the
space
usage
and
availability
of
Microsoft
Exchange
Server
over
a
period
of
time.
See
“IBM
Tivoli
Data
Warehouse
reports”
on
page
59
for
information.
Adjust
or
set
limits
for
mailboxes,
folders,
and
servers
4
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Overview
of
steps
Additional
information
Use
Microsoft
Exchange
Server
management
tools.
See
the
Microsoft
Exchange
Server
Administrator’s
Guide
for
information
Repair
problems
with
services
or
queues
Run
Microsoft
Exchange
utility
tasks
to
repair
logical
or
physical
disk
issues.
See
Chapter
9,
“Using
Microsoft
Exchange
Server
utilities
to
address
problems,”
on
page
69
for
information.
Chapter
2.
Quick-reference
to
common
user
scenarios
5
6
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
This
chapter
describes
how
to
configure
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server.
The
following
table
describes
the
steps
required
to
set
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server,
as
well
as
links
to
where
to
find
more
information.
Table
1.
Guidelines
for
setting
up
the
product
Goal
Where
to
find
information
Access
the
interfaces
in
the
Tivoli
environment
so
you
can
use
the
operations
and
functions
of
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
software.
“Accessing
the
Tivoli
Management
Framework
environment”
on
page
8
Assign
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
authorizations
to
one
or
more
Tivoli
administrators
“Setting
authorization
roles”
on
page
9
Configure
Microsoft
Exchange
Server
to
communicate
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
v
Create
a
user
on
each
Microsoft
Exchange
server.
v
Grant
the
user
administrator
rights
on
Microsoft
Exchange
Server.
v
Make
the
user
a
local
administrator.
v
Create
an
Exchange
profile
for
each
Exchange
server
that
you
want
to
monitor.
v
Optionally
configure
Microsoft
Outlook
to
automatically
respond
to
e-mail.
You
must
perform
this
step
if
you
plan
to
use
the
Reachability
resource
model
to
monitor
the
availability
of
servers.
“Configuring
Microsoft
Exchange
servers
to
communicate
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server”
on
page
10
Create
Tivoli
objects
to
represent
your
Microsoft
Exchange
servers.
“Creating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects”
on
page
16
Authenticate
user
information
for
Microsoft
Exchange
servers.
“Configuring
authentication
for
Tivoli
objects”
on
page
19
Create
profile
managers
and
profiles.
“Creating
profiles
and
profile
managers”
on
page
20
Configure
and
deploy
basic
resource
models.
“Adding
a
resource
model
to
a
profile
manager”
on
page
22
“Distributing
profiles”
on
page
24
Configure
the
IBM
Tivoli
Enterprise
Console
event
server
to
monitor
events
from
resource
models.
“Configuring
the
IBM
Tivoli
Enterprise
Console
event
server”
on
page
26
©
Copyright
IBM
Corp.
2004
7
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
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
Messaging
and
Collaboration:
Microsoft
Exchange
Server
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
Messaging
and
Collaboration:
Microsoft
Exchange
Server
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
Manual.
Required
authorization
role
user
Before
you
begin
Not
applicable.
When
you
finish
Not
applicable.
Procedure
Use
the
following
steps
to
access
the
Tivoli
Management
Framework
environment:
1.
Log
on
to
the
computer
that
hosts
the
Tivoli
server
or
a
managed
node.
2.
Do
one
of
the
following
to
set
up
the
Tivoli
environment
variables:
v
On
UNIX
operating
systems
only,
do
one
of
the
following:
–
If
you
are
using
the
Bourne,
Korn,
or
bash
shell,
run
the
following
command:
.
/etc/Tivoli/setup_env.sh
–
If
you
are
using
the
C
shell,
run
the
following
command:
source
/etc/Tivoli/setup_env.csh
—OR—
v
On
Windows
operating
systems
only,
do
one
of
the
following:
–
From
a
bash
shell,
enter
the
following
command:
.$SystemRoot/system32/drivers/etc/Tivoli/setup_env.sh
Be
sure
to
include
the
period
(.)
at
the
beginning
of
the
command
to
successfully
source
the
Tivoli
environment.
–
From
a
Windows
command
prompt,
enter
the
following
command:
%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd
8
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
–
To
create
a
shortcut
to
the
Windows
command
line
that
automatically
sources
the
Tivoli
environment,
perform
the
following
steps:
a.
Right-click
a
blank
area
on
the
Windows
desktop.
b.
Click
New
→
Shortcut.
c.
Type
CMD.exe
in
the
text
box
on
the
Create
Shortcut
window.
d.
Click
Next.
e.
Type
a
name
for
the
shortcut
in
the
text
box.
For
example,
type
Tivoli
command
line.
f.
Click
Finish.
g.
Right-click
the
new
shortcut
icon
on
the
Windows
desktop.
h.
Click
Properties.
i.
Click
the
Shortcut
tab.
j.
In
the
Target
text
box,
enter
the
following
commands
on
a
single
line:
%SystemRoot%\system32\cmd.exe
/k
%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd
3.
Perform
the
following
steps
if
you
want
to
access
the
Tivoli
desktop:
a.
Do
one
of
the
following
to
access
the
login
screen
for
the
Tivoli
desktop:
v
On
UNIX
or
Windows
operating
systems,
type
tivoli
at
a
command
prompt.
See
the
Tivoli
Management
Framework
Reference
Manual
for
more
information
about
the
tivoli
command.
—OR—
v
On
Windows
operating
systems
only,
click
Start
→
Programs
→
Tivoli
→
Tivoli
in
the
Windows
task
bar.b.
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
must
connect
Log
In
As
Specifies
the
login
name
to
the
managed
node
Password
Specifies
the
password
for
the
specified
login
namec.
Click
OK
to
open
the
Tivoli
desktop.
Setting
authorization
roles
Objective
To
assign
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
authorization
roles
for
managing
resources
to
administrators
and
users.
Background
information
When
you
install
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server,
the
following
roles
are
created:
v
msexchgserver_user
v
msexchgserver_admin
All
tasks
require
that
you
assign
at
least
one
of
these
roles
to
the
Tivoli
administrator
who
performs
the
task.
In
addition,
some
tasks
require
Tivoli
authorization
as
defined
by
Tivoli
management
region
roles.
To
run
tasks
and
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
9
processes,
the
Tivoli
administrator
must
have
the
required
Tivoli
authorization
and
must
be
assigned
one
of
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
authorization
roles.
Required
authorization
role
senior
Before
you
begin
Before
setting
authorization
roles,
you
must
have
installed
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration
Installation
and
Setup
Guide
for
information
on
installation.
When
you
finish
Add
managed
resources
to
a
policy
region
as
described
in
“Subscribing
resources
to
profile
managers”
on
page
21.
Procedure
You
can
perform
this
procedure
from
the
command
line
or
the
Tivoli
desktop.
Command
Line:
Use
the
wsetadmin
command
to
set
or
change
resource
authorization
roles.
See
the
Tivoli
Management
Framework
Reference
Manual
for
more
information.
Tivoli
desktop:
Follow
these
steps
to
perform
this
procedure
from
the
Tivoli
desktop:
1.
Double-click
Administrators.
2.
Right-click
the
administrator
whose
role
you
want
to
modify
to
access
the
pop-up
menu.
3.
Click
Edit
TMR
Roles
to
access
the
Set
TMR
Roles
window.
4.
Add
or
remove
roles
for
the
selected
resources
as
follows:
v
To
add
roles
for
the
selected
resources,
double-click
an
entry
in
the
Available
Roles
list
to
move
it
to
the
Current
Roles
list.
v
To
remove
roles
for
the
selected
resources,
double-click
an
entry
in
the
Current
Roles
list
to
move
it
to
the
Available
Roles
list.5.
Click
Change
&
Close
or
Change
to
add
and
remove
the
selected
roles
and
save
your
changes.
6.
Restart
the
Tivoli
desktop
so
that
changes
can
take
effect.
Configuring
Microsoft
Exchange
servers
to
communicate
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Before
you
can
monitor
Microsoft
Exchange
servers,
you
must
configure
those
servers
to
permit
communication
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server.
The
following
table
lists
the
configuration
steps:
Goal
Where
to
find
information
Create
a
Microsoft
Exchange
Server
user
for
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
on
each
server.
“Create
a
user
on
each
Microsoft
Exchange
server”
on
page
11
10
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Goal
Where
to
find
information
Grant
the
user
administrator
rights
on
Microsoft
Exchange
Server.
“Assign
administrative
rights
to
the
Microsoft
Exchange
Server
user”
on
page
12
Make
the
user
a
local
administrator
on
the
computer
where
Microsoft
Exchange
Server
is
installed.
“Make
the
Microsoft
Exchange
Server
user
a
local
administrator”
on
page
13
Create
a
MAPI
profile
for
the
user.
“Create
a
MAPI
profile
for
each
server”
on
page
14
Optionally,
configure
Microsoft
Exchange
Server
to
communicate
with
the
Reachability
resource
model.
“Set
up
communication
for
the
Reachability
resource
model
(optional)”
on
page
15
To
view
simulations
of
these
configuration
steps,
open
the
simulations.html
file
located
in
the
\docs
directory
of
the
installation
media.
Create
a
user
on
each
Microsoft
Exchange
server
Objective
To
establish
communication
and
authentication
between
Microsoft
Exchange
Server
and
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
by
creating
a
Microsoft
Exchange
Server
user
for
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server.
Background
information
To
communicate
with
and
gather
data
from
Microsoft
Exchange
Server,
you
must
authenticate
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
to
Microsoft
Exchange
Server.
This
is
accomplished
by
creating
a
user
for
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server.
Required
authorization
role
A
domain
administrator
with
full
administrator
rights
for
Microsoft
Exchange
Before
you
begin
Install
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration
on
the
Tivoli
management
region
server.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration
Installation
and
Setup
Guide
for
information.
When
you
finish
Make
the
Microsoft
Exchange
Server
user
a
local
administrator
on
the
system,
as
described
in
“Make
the
Microsoft
Exchange
Server
user
a
local
administrator”
on
page
13.
Procedure
Use
the
following
steps
on
each
Microsoft
Exchange
server
that
you
want
to
monitor:
1.
Create
the
user:
a.
Open
Active
Directory
Users
and
Computers
by
clicking
Start
→
Programs
→
Microsoft
Exchange
→
Active
Directory
Users
and
Computers.
b.
Expand
the
domain
in
which
you
want
to
create
the
user
by
clicking
the
plus
sign
(+)
next
to
the
name
of
the
domain.
c.
Right-click
Users.
d.
Click
New
→
User.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
11
e.
Complete
the
following
user
information
and
click
Next:
First
name
Type
a
first
name
(such
as
″Tivoli″)
for
the
user.
Last
name
Type
a
last
name
(such
as
the
name
of
the
endpoint)
for
the
user.
User
logon
name
Type
a
user
name
for
the
user
(such
as
tivoliendpoint,
where
endpoint
is
the
name
of
the
endpoint
you
specified
in
the
Last
name
field.f.
Type
a
password
for
the
user
in
the
Password
field.
Additional
information:
Follow
the
password
restrictions
established
for
the
domain.
By
default,
Active
Directory
has
no
password
restrictions.
g.
Select
Password
never
expires
and
click
Next.
h.
Verify
the
following:
v
Create
an
Exchange
mailbox
is
selected.
v
The
alias
for
the
user
(in
the
Alias
field)
is
correct.
v
The
Microsoft
Exchange
server
and
mailbox
information
store
on
which
the
user
is
being
created
is
correct.
Click
Next.
i.
Review
the
information
and
click
Finish.2.
Click
View
→
Advanced
Features
in
the
Active
Directory
Users
and
Computers
window.
3.
Grant
user
permissions
for
the
user:
a.
Expand
the
Users
folder
and
double-click
the
new
user.
Click
the
Exchange
Advanced
tab.
b.
Click
Mailbox
Rights.
A
permissions
window
is
displayed
for
the
user.
Before
you
can
assign
permissions
to
a
user,
you
must
add
the
user
account.
c.
Click
Add.
d.
Select
the
name
of
the
user
you
just
created
and
click
Add.
e.
Click
OK.
f.
Highlight
the
name
of
the
user.
g.
Set
Full
Mailbox
Access
to
Allow.
h.
Repeat
the
previous
steps
for
the
account
with
which
you
are
logged
into
the
computer
where
Microsoft
Exchange
Server
is
installed
(usually,
the
″Administrator″
account).
i.
Click
OK.
j.
Click
OK
on
the
Properties
page.
Assign
administrative
rights
to
the
Microsoft
Exchange
Server
user
Objective
To
give
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
user
full
administrator
rights
for
Microsoft
Exchange
Server.
12
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Background
information
The
user
that
you
created
for
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
needs
the
appropriate
level
of
rights
and
access
to
Microsoft
Exchange
Server
in
order
to
monitor
the
Microsoft
Exchange
Server
components.
Required
authorization
role
A
domain
administrator
with
full
administrator
rights
for
Microsoft
Exchange
Before
you
begin
Create
an
Microsoft
Exchange
Server
user,
as
described
in
“Create
a
user
on
each
Microsoft
Exchange
server”
on
page
11.
When
you
finish
Make
the
user
a
local
administrator
of
the
computer
where
Microsoft
Exchange
Server
is
installed,
as
described
in
“Make
the
Microsoft
Exchange
Server
user
a
local
administrator.”
Procedure
Perform
the
following
steps
on
each
Microsoft
Exchange
server
that
you
want
to
monitor:
1.
Open
the
Microsoft
Exchange
Systems
Manager
by
clicking
Start
→
Programs
→
Microsoft
Exchange
→
System
Manager.
2.
Click
Action
→
Delegate
control
to
launch
the
Exchange
Administration
Delegation
Wizard.
3.
Click
Next.
4.
Click
Add.
The
Delegate
Control
window
is
displayed.
5.
Click
Browse.
6.
Select
the
name
of
the
user
you
created
and
click
OK.
7.
Select
Exchange
Full
Administrator
from
the
Role
list
and
click
OK.
8.
Click
Next
and
then
Finish.
9.
A
message
is
displayed
that
instructs
you
to
make
the
user
a
local
administrator
of
the
computer
where
Microsoft
Exchange
Server
is
installed.
Click
OK.
Make
the
Microsoft
Exchange
Server
user
a
local
administrator
Objective
To
assign
the
role
of
Administrator
of
the
local
computer
to
the
Microsoft
Exchange
Server
user,
enabling
the
user
to
access
the
computer.
Background
information
To
access
the
Microsoft
Exchange
Server
data,
the
user
that
represents
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
must
have
administrator
authority
on
the
computer
where
Microsoft
Exchange
Server
is
installed.
Note:
There
are
many
different
ways
to
make
a
user
a
local
administrator
on
a
computer,
such
as
using
group
policies.
The
following
procedure
is
what
must
be
accomplished
for
the
Tivoli
component
software
to
function
properly.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
13
Required
authorization
role
A
domain
administrator
with
full
administrator
rights
for
Microsoft
Exchange
Before
you
begin
Create
an
Microsoft
Exchange
Server
user,
as
described
in
“Create
a
user
on
each
Microsoft
Exchange
server”
on
page
11.
When
you
finish
Create
a
MAPI
profile
for
each
user,
as
described
in
“Create
a
MAPI
profile
for
each
server.”
Procedure
Perform
the
following
steps
on
each
Microsoft
Exchange
server
that
you
want
to
monitor:
1.
Right-click
My
Computer
on
the
computer
desktop
and
click
Manage.
2.
Expand
Local
Users
and
Groups.
3.
Click
Groups.
4.
Double-click
Administrators
to
display
the
Administrators
Properties
window.
5.
Click
Add.
6.
Select
Entire
Directory
from
the
Look
in
list.
7.
Select
the
name
of
the
user
you
created
and
click
Add.
8.
Click
OK.
9.
Click
OK.
Create
a
MAPI
profile
for
each
server
Objective
To
create
a
Messaging
Application
Programming
Interface
(MAPI)
for
the
user
that
you
created.
Background
information
A
Messaging
Application
Programming
Interface
(MAPI)
profile
is
the
set
of
MAPI
configuration
settings,
stored
in
the
registry,
that
enable
users
to
connect
to
various
messaging
services,
such
as
Microsoft
Exchange
Server.
Required
authorization
role
A
domain
administrator
with
full
administrator
rights
for
Microsoft
Exchange
Before
you
begin
Make
the
user
a
local
administrator,
as
described
in
“Make
the
Microsoft
Exchange
Server
user
a
local
administrator”
on
page
13.
When
you
finish
Optionally
configure
your
Microsoft
Exchange
server
to
respond
to
messages,
as
described
in
“Set
up
communication
for
the
Reachability
resource
model
(optional)”
on
page
15.
Procedure
Perform
the
following
steps
on
each
Microsoft
Exchange
server
that
you
want
to
monitor:
1.
Log
on
to
the
computer
as
the
user
you
created
in
“Create
a
user
on
each
Microsoft
Exchange
server”
on
page
11.
14
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
2.
Download
and
install
MAPI
Profile
Manager
2.0
(also
called
″Profman″)
from
the
Microsoft
support
Web
site.
3.
Open
MAPI
Profile
Manager.
4.
Click
New
→
Profile.
5.
Type
a
name
for
the
new
profile
and
click
OK.
Use
a
name
that
identifies
the
purpose
of
this
profile,
such
as
″TivoliProfile.″
Do
not
use
a
space
in
the
profile
name.
6.
Select
the
empty
profile
that
you
created
and
click
New
→
Service.
7.
Select
MSEMS
and
click
OK.
8.
Type
the
name
of
the
Microsoft
Exchange
server
and
user
name
in
the
server
and
user
fields.
9.
Click
OK.
10.
Expand
the
profile
to
verify
that
the
Microsoft
Exchange
server
and
user
name
information
is
correct.
Set
up
communication
for
the
Reachability
resource
model
(optional)
Objective
To
configure
Microsoft
Exchange
Server
to
respond
to
an
message.
This
enables
you
to
monitor
whether
the
server
can
be
reached.
This
is
an
optional
step.
Perform
this
step
if
you
want
to
use
the
Reachability
resource
model.
Background
information
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
provides
the
Reachability
resource
model
to
monitor
whether
your
servers
can
be
reached
through
e-mail.
This
resource
model
sends
an
message
to
the
server
and
measures
the
amount
of
time
it
takes
to
receive
an
automated
response.
Before
you
can
use
the
Reachability
resource
model,
you
must
configure
Microsoft
Exchange
Server
to
respond
automatically
to
messages.
Required
authorization
role
Domain
users
Before
you
begin
Create
a
user
mailbox
on
the
Microsoft
Exchange
server
that
you
want
to
monitor,
as
described
in
“Create
a
user
on
each
Microsoft
Exchange
server”
on
page
11.
Ensure
that
the
servers
in
your
Microsoft
Exchange
organization
are
configured
for
flow
between
servers.
See
the
Microsoft
Exchange
Server
2003
Administration
Guide
for
information
about
configuring
message
routing.
When
you
finish
Create
application
proxy
objects
to
represent
your
Microsoft
Exchange
servers.
Procedure
Perform
the
following
steps
on
each
Microsoft
Exchange
server
that
you
want
to
monitor
with
the
Reachability
resource
model:
Note:
These
steps
might
differ
depending
on
the
version
of
Microsoft
Outlook
you
have
installed
on
your
system.
1.
Log
in
to
Microsoft
Outlook
using
the
user
you
created
in
“Create
a
user
on
each
Microsoft
Exchange
server”
on
page
11.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
15
2.
Click
Next
on
the
Startup
window.
3.
Select
Yes
and
click
Next.
4.
Type
the
name
of
the
Microsoft
Exchange
server
in
the
Microsoft
Exchange
Server
field.
5.
Type
the
name
of
the
user
you
created
in
the
Mailbox
field.
6.
Click
Finish.
7.
Click
OK.
8.
Click
Tools
→
Rules
and
Alerts
→
New
Rule.
9.
Select
Start
from
a
blank
rule.
10.
Select
Check
messages
when
they
arrive
and
click
Next.
11.
Select
the
following
options:
v
Where
my
name
is
in
the
To:
box
v
With
specific
words
in
the
subject
or
body
12.
Under
Step
2
in
the
window,
click
Specific
words.
13.
Type
the
following
in
the
Specify
words
or
phrases
to
search
for
in
the
subject
or
body
field:
AVAILABILITY
CHECK
Click
Add.
14.
Click
OK
and
then
Next.
15.
Select
Have
the
server
reply
using
a
specific
message
and
click
a
specific
message.
16.
In
the
message
editor,
type
the
following
text
in
the
subject
field
of
the
message:
CHECK
RECEIVED:
MAILBOX
AVAILABLE
17.
Close
the
message
editor
and
click
Yes
to
save
these
changes.
18.
Click
Next.
19.
When
you
are
asked
about
exceptions,
do
not
specify
any
restrictions.
20.
Click
Next.
21.
Click
Finish
and
then
OK.
Creating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects
Objective
To
register
your
Microsoft
Exchange
servers
with
the
Tivoli
monitoring
environment
by
creating
Tivoli
objects
to
represent
those
servers.
Background
information
Tivoli
objects
(MicrosoftExchangeServer)
that
represent
Microsoft
Exchange
servers
are
registered
in
the
Tivoli
management
region
and
monitored
by
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
resource
models
and
can
be
acted
against
by
the
product
tasks.
There
are
two
ways
to
create
Tivoli
objects:
v
Automatically
using
the
DiscoverExchangeServers
task
or
job
v
Manually
from
the
Tivoli
command
line
or
desktop
16
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Use
the
DiscoverExchangeServers
task
or
job
to
search
your
environment
for
all
available
servers
and
to
register
those
servers
with
the
default
properties.
Use
the
manual
object
creation
options
if
you
want
to
register
only
one
or
two
servers
and
you
know
the
server
properties
or
if
you
do
not
want
to
use
the
default
properties.
Required
authorization
role
msexchgserver_admin
Before
you
begin
Configure
Microsoft
Exchange
Server
to
communicate
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server.
When
you
finish
You
must
authenticate
the
user
ID,
user
domain,
user
profile,
and
password
for
the
Microsoft
Exchange
servers
to
the
Tivoli
software,
as
described
in
“Configuring
authentication
for
Tivoli
objects”
on
page
19.
Procedure
You
can
perform
this
procedure
from
the
command
line,
as
a
job,
as
a
task,
or
through
the
Tivoli
desktop.
Command
Line:
Use
the
wxregsvr
command
to
manually
create
Tivoli
objects.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
the
syntax
and
options
of
this
command.
Job:
Use
the
following
steps
to
create
Tivoli
objects
with
the
DiscoverExchangeServers
job:
1.
Double-click
Monitoring
for
Microsoft
Exchange
Server
in
the
Tivoli
desktop.
2.
Double-click
ITMMicrosoftExchangeServerTasks.
3.
Double-click
DiscoverExchangeServers
Job.
4.
Complete
the
following
fields:
Select
Endpoints
Specifies
the
endpoint
on
which
to
search
for
objects.
Click
Endpoints
to
display
all
endpoints
available
to
search.
Select
Proxy
Managed
Node
(optional)
Specifies
whether
to
select
a
managed
node
to
contain
the
object
for
the
Microsoft
Exchange
Server
servers
being
discovered.
Click
Proxy
Managed
Nodes
to
display
a
list
of
available
proxy
managed
nodes.
If
you
do
not
specify
a
proxy
managed
node,
the
task
uses
the
managed
node
(gateway)
that
is
currently
defined
for
the
endpoints.5.
Click
Set
&
Execute.
When
the
job
completes
successfully,
you
receive
a
list
of
the
names
and
types
of
resources
discovered.
The
application
proxy
objects
that
this
job
creates
to
represent
your
resources
have
the
following
naming
format:
server_name@endpoint_name.
Task:
Use
the
following
steps
to
create
Tivoli
objects
with
the
DiscoverExchangeServers
task:
1.
Double-click
Monitoring
for
Microsoft
Exchange
Server
in
the
Tivoli
desktop.
2.
Double-click
ITMMicrosoftExchangeServerTasks.
3.
Double-click
DiscoverExchangeServers.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
17
4.
Select
Display
on
Desktop
to
display
the
output
of
the
task
on
the
desktop.
5.
Select
the
Tivoli
management
region
server
that
you
want
to
search
from
the
Available
Task
Endpoints
list.
6.
Increase
the
timeout
value
for
the
task.
Allow
600
seconds
for
each
Tivoli
management
region
server
on
which
you
are
running
the
task.
7.
Click
Execute
or
Execute
and
Dismiss
to
display
the
DiscoverExchangeServers
window.
8.
Complete
the
following
fields:
Select
Endpoints
Specifies
the
endpoint
on
which
to
search
for
objects.
Click
Endpoints
to
display
all
endpoints
available
to
search.
Select
Proxy
Managed
Node
(optional)
Specifies
whether
to
select
a
managed
node
to
contain
the
object
for
the
Microsoft
Exchange
Server
servers
being
discovered.
Click
Proxy
Managed
Nodes
to
display
a
list
of
available
proxy
managed
nodes.
If
you
do
not
specify
a
proxy
managed
node,
the
task
uses
the
managed
node
(gateway)
that
is
currently
defined
for
the
endpoints.9.
Click
Set
&
Execute.
When
the
task
completes
successfully,
you
receive
a
list
of
the
names
and
types
of
resources
discovered.
The
application
proxy
objects
that
this
task
creates
to
represent
your
resources
have
the
following
naming
format:
server_name@endpoint_name.
Additional
information:
You
can
run
the
DiscoverExchangeServers
task
from
the
command
line
with
the
wruntask
command.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
information.
Tivoli
desktop:
Use
the
following
steps
to
create
Tivoli
objects
manually
through
the
Tivoli
desktop:
1.
Double-click
the
Monitoring
for
Microsoft
Exchange
Server
policy
region.
2.
Click
Create
→
MicrosoftExchangeServer.
3.
Complete
the
following
fields:
Name
Specify
the
name
of
the
Microsoft
Exchange
Server
for
which
you
want
to
create
a
Tivoli
object.
This
name
must
exactly
match
the
name
of
the
server
as
it
is
defined
to
Microsoft
Exchange
Server
and
should
be
in
uppercase.
Home
Specify
the
home
(or
directory)
where
Microsoft
Exchange
Server
is
installed.
Use
UNIX
style
slashes
for
the
directory.
For
example,
use
c:/Program
Files/Exchsrvr
instead
of
c:\Program
Files\Exchsrvr.
Username
Specify
a
user
name
with
access
to
the
server
you
want
to
register.
Password
Specify
the
password
for
the
MicrosoftExchangeServer
to
be
registered.
Version
Specify
the
version
of
Microsoft
Exchange
Server
installed
(2000
or
2003).
18
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
UserProfile
Specify
the
Microsoft
Exchange
Server
profile
for
the
user.
This
is
the
profile
that
you
created
in
“Create
a
MAPI
profile
for
each
server”
on
page
14.
UserDomain
Specify
the
domain
for
the
user.
Endpoint
Specify
the
name
of
the
endpoint
in
which
to
register
the
Microsoft
Exchange
server.
Proxy
Managed
Node
Specify
the
managed
node
upon
which
you
want
the
proxy
object
to
reside.4.
Click
Create.
Configuring
authentication
for
Tivoli
objects
Objective
To
authenticate
user
information
for
the
Tivoli
objects
that
represent
Microsoft
Exchange
servers.
This
enables
the
Tivoli
software
to
access
data
on
the
servers.
Background
information
When
you
use
the
DiscoverExchangeServers
task
to
create
Tivoli
objects
or
modify
the
servers
that
those
objects
represent,
you
must
authenticate
the
user
ID,
domain,
profile,
and
password
for
the
server.
Required
authorization
role
msexchgserver_admin
Before
you
begin
Create
Tivoli
objects
to
represent
your
Microsoft
Exchange
servers,
as
described
in
“Creating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects”
on
page
16.
When
you
finish
Configure
and
deploy
resource
models
to
monitor
your
Microsoft
Exchange
servers,
as
described
in
“Creating
profiles
and
profile
managers”
on
page
20.
Procedure
You
can
perform
this
procedure
as
a
task
or
through
the
application
proxy
object.
Task:
Use
the
following
steps
to
authenticate
using
a
task:
1.
Double-click
Monitoring
for
Microsoft
Exchange
Server
in
the
Tivoli
desktop.
2.
Double-click
ITMMicrosoftExchangeServerTasks.
3.
Double-click
MSExchangeAuthentication.
4.
Select
Display
on
Desktop
to
display
the
output
of
the
task
on
the
desktop.
5.
Select
the
Tivoli
management
region
server
from
the
list
of
available
endpoints.
6.
Click
Execute
or
Execute
and
Dismiss
to
display
the
MSExchangeAuthentication
window.
7.
Complete
the
following
fields:
Select
Exchange
objects
The
specific
objects
on
which
to
perform
the
authentication
change.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
19
User
Name
(required)
The
new
or
existing
user
name
that
you
want
to
define.
Password
(required)
The
new
or
existing
password
for
the
user
specified
in
UserName.
User
Profile
(optional)
The
new
or
existing
user
profile
that
you
want
to
define.
User
Domain
(optional)
The
new
or
existing
user
domain
that
you
want
to
define.8.
Click
Set
&
Execute.
Application
proxy
object:
See
“Editing
Microsoft
Exchange
server
properties”
on
page
65
for
information
about
performing
the
authentication
through
the
application
proxy
object.
Creating
profiles
and
profile
managers
Objective
To
create
profile
managers
and
profiles
so
you
can
organize
and
distribute
your
resource
models
more
efficiently.
The
installation
process
creates
a
profile
manager
and
profile
and
subscribes
all
resources
models
to
that
profile
(all
enabled
with
default
monitoring
settings).
You
can
use
this
procedure
to
create
new
profiles
and
profile
managers.
Background
information
A
monitoring
profile
is
a
group
of
defined
resource
models
that
you
can
distribute
(download
or
push)
to
a
subscribed
(marked
to
receive)
managed
resource
in
a
profile
manager.
In
addition
to
activating
default
resource
models,
profile
managers
and
profiles
can
group
resources
to
enable
simultaneous
monitoring
of
multiple
resources.
You
can
hierarchically
organize
the
profile
managers.
The
profile
manager
is
the
top
level
of
the
organization
and
contains
specific
profiles
that
contain
specific
resource
models.
Microsoft
Exchange
servers
are
then
subscribed
to
the
profile
managers,
which
enable
the
monitoring
information
to
be
channeled
to
those
resources.
You
can
create
an
unlimited
number
of
profile
managers
but
might
group
them
to
reflect
a
logical
or
functional
grouping
of
resources
or
the
organizational
structure
of
the
business.
For
example,
profile
managers
might
be
labeled
Sales
and
Marketing,
Administration
and
Finance,
and
Operations
to
reflect
a
business
organization.
You
can
create
a
dataless
profile
manager
that
distributes
profiles
without
regard
to
the
existence
of
a
database
on
its
subscribers.
A
dataless
profile
manager
distributes
to
the
system
files
on
endpoints
and
other
managed
resources
that
have
a
profile
database.
However,
it
bypasses
the
profile
database
on
these
systems.
Therefore,
profiles
are
available
only
with
database
profile
managers.
A
profile
manager
(database
or
dataless)
cannot
subscribe
to
a
dataless
profile
manager.
Likewise,
dataless
profile
managers
cannot
distribute
to
other
profile
managers
because
they
require
profiles
to
be
written
to
a
profile
database.
Required
authorization
role
admin
20
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Before
you
begin
Not
applicable
When
you
finish
Add
resources
to
the
profile,
as
described
in
“Subscribing
resources
to
profile
managers.”
Procedure
You
can
perform
this
procedure
from
the
command
line
or
the
Tivoli
desktop.
Command
Line:
Use
the
following
steps
to
create
a
profile
manager
and
profile:
1.
Use
the
wcrtprfmgr
command
to
create
a
profile
manager.
For
example,
to
create
a
profile
manager
called
ProfMgr2
in
the
TestRegion
policy
region,
enter
the
following
command:
wcrtprfmgr
@PolicyRegion:TestRegion
ProfMgr2
2.
Optional:
Use
the
wsetpm
command
to
make
the
profile
manager
operate
in
dataless
mode.
For
example,
to
make
the
profile
manager
ProfMgr2
dataless,
enter
the
following
command:
wsetpm
-d
@ProfileManager:ProfMgr2
where
-d
specifies
that
the
profile
manager
operates
in
a
dataless
mode.
3.
Use
the
wcrtprf
command
to
create
a
profile.
For
example,
to
create
a
profile
called
MarketingProf2
in
the
ProfMgr2
profile
manager,
enter
the
following
command:
wcrtprf
@ProfileManager:ProfMgr2
Tm2kProfile
MarketingProf2
For
additional
information
about
these
commands,
see
the
Tivoli
Management
Framework
Reference
Guide.
Tivoli
desktop:
Use
the
following
steps
to
create
a
profile
manager
and
profile
from
the
desktop:
1.
Double-click
a
policy
region
icon
to
open
the
policy
region.
2.
Select
Create
→
Profile
Manager.
3.
Type
a
unique
name
in
the
Name/Icon
Label
text
box.
4.
Optional:
Select
Dataless
Endpoint
Mode
to
create
the
profile
manager
in
dataless
mode.
5.
Click
Create
&
Close.
6.
Double-click
the
profile
manager
icon.
7.
Select
Create
→
Profile.
8.
Type
a
unique
name
for
the
profile
in
the
Name/Icon
text
box.
9.
Select
the
Tmw2kProfile
resource
from
the
Type
list.
10.
Click
Create
&
Close.
An
icon
for
the
new
profile
is
displayed
in
the
Profiles
area
of
the
Profile
Manager
window.
Subscribing
resources
to
profile
managers
Objective
To
add
managed
resources
to
a
monitoring
profile
so
administrators
can
define
which
resources
are
monitored.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
21
Background
information
Subscribing
resources
to
a
profile
manager
determines
which
resources
receive
a
profile
when
the
profile
is
distributed.
IBM
Tivoli
Monitoring
uses
the
list
of
subscribers
to
determine
which
systems
are
monitored.
To
add
a
subscriber
to
a
distributed
monitoring
profile,
you
must
add
the
subscriber
to
the
profile
manager.
Note:
Resources
can
also
be
subscribed
to
profiles
from
the
IBM
Tivoli
Monitoring
Profile
dialog.
See
“Distributing
profiles”
on
page
24.
Required
authorization
role
admin
Before
you
begin
Create
a
monitoring
profile
with
monitoring
sources.
See
“Creating
profiles
and
profile
managers”
on
page
20
for
information.
When
you
finish
Distribute
the
monitoring
profile
to
the
subscribed
resource.
See“Distributing
profiles”
on
page
24
for
information.
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
Line:
Use
the
wsub
command
to
add
subscribers
to
the
profile
manager.
For
example,
to
add
a
database
called
Sample@bburns
as
a
subscriber
to
the
profile
manager
DatabaseMonitors,
enter
the
following
command:
wsub
@ProfileManager:DatabaseMonitors
@PolicyRegionName:Sample@bburns
See
the
Tivoli
Management
Framework
Reference
Manual
for
more
information.
Desktop:
1.
Double-click
a
policy
region
icon.
2.
Double-click
a
profile
manager
icon.
3.
Click
Profile
Manager
→
Subscribers.
4.
Select
the
subscribers
to
receive
the
profile
distribution
from
the
Available
to
become
Subscribers
list.
5.
Click
the
left-arrow
button
to
move
the
selected
subscribers
to
the
Current
Subscribers
list.
6.
Click
Set
Subscriptions
&
Close
to
add
the
subscribers.
Subscribers
are
displayed
in
the
Subscribers
field
of
the
Profile
Manager
window.
Adding
a
resource
model
to
a
profile
manager
Objective
To
add
a
resource
model
to
a
profile
so
you
can
run
the
resource
model
immediately.
The
installation
process
automatically
subscribes
all
resource
models
to
the
profile
created
during
installation.
Use
this
procedure
to
add
resource
models
to
a
custom
profile.
22
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Background
information
A
resource
model
captures
and
returns
information
about
a
resource
or
application.
You
set
up
resource
models
and
distribute
them
to
the
subscribers.
Each
resource
model
can
monitor
multiple
resources.
Choose
the
resource
models
to
add
to
a
profile
based
on
the
resources
you
want
to
monitor.
Adding
one
or
more
of
these
resource
models
to
a
profile
enables
you
to
begin
monitoring
resources
immediately.
If
you
want
to
perform
historical
or
IBM
Tivoli
Data
Warehouse
data
logging
with
the
data
from
resource
models,
you
must
customize
the
data
logging
features.
See
Chapter
5,
“Customizing
resource
models,”
on
page
35
for
more
information
about
using
and
configuring
resource
models.
Required
authorization
role
admin
Before
you
begin
Create
a
profile
and
profile
manager,
as
described
in
“Creating
profiles
and
profile
managers”
on
page
20.
When
you
finish
Distribute
the
profile.
Procedure
You
can
perform
this
procedure
from
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wdmeditprf
command
to
add
a
resource
model
to
a
profile.
See
the
Tivoli
Management
Framework
Reference
Manual
for
information.
Desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window
by
following
these
steps:
a.
Double-click
a
policy
region
icon
to
open
the
policy
region.
b.
Double-click
the
profile
manager
icon
to
open
the
profile
manager.
c.
Double-click
the
profile
icon
to
which
you
want
to
add
a
customized
resource
model.2.
To
add
a
resource
model
with
all
default
values
(such
as
the
cycle
time),
use
the
following
steps:
a.
Click
Add
With
Defaults.
b.
Select
Microsoft
Exchange
Server
in
the
Category
list.
c.
Select
the
resource
model
you
want
from
the
Resource
Model
list.3.
To
add
a
resource
model
with
customized
monitoring
settings,
use
the
following
steps:
a.
Click
Add.
b.
Select
Microsoft
Exchange
Server
in
the
Categorylist.
c.
Select
the
resource
model
that
you
want
to
customize
from
the
Resource
Model
list.
d.
Set
the
frequency
(in
seconds)
with
which
the
resource
model
monitors
the
data
in
the
Cycle
Time
text
box.
e.
Use
the
following
steps
to
change
any
of
the
threshold
values:
1)
Select
the
Threshold
Name
that
you
want
to
change.
2)
Change
the
currently
assigned
threshold
value
to
a
value
appropriate
to
your
requirements.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
23
3)
Click
Apply
to
set
and
display
the
new
value
in
the
Threshold
Value
window.f.
Click
one
or
more
of
the
options
along
the
bottom
of
the
Add
Resource
Models
to
Profile
window
one
at
a
time
to
change
the
following
settings:
v
Indications
(occurrences,
holes,
where
to
send
events,
severity,
tasks)
See
“Customizing
indications
and
events”
on
page
35.
See
“Specifying
a
response
task
for
an
indication”
on
page
36.
v
Parameters
See
“Customizing
parameters”
on
page
38
for
how
to
change
the
parameters
for
the
resource
model.
v
Logging
See
“Logging
data
for
a
resource
model”
on
page
41
for
how
to
enable
logging
and
how
to
aggregate
data.
v
Schedule
See
“Scheduling
when
a
resource
model
runs”
on
page
39
for
how
to
set
the
schedule
for
running
a
resource
model.4.
Click
Add
&
Close.
The
resource
model
is
added
to
the
IBM
Tivoli
Monitoring
Profile.
Distributing
profiles
Objective
To
distribute
profiles
to
specified
subscribers.
Background
information
You
can
distribute
profiles
to
the
following
groups:
Next
level
of
subscribers
This
selection
distributes
the
profile
only
to
the
subscribers
of
the
profile
manager.
It
does
not
distribute
to
lower-level
subscribers.
If
a
profile
manager
with
subscribers
resides
at
the
next
lower
level,
you
need
to
perform
the
distribution
process
from
profile
managers
at
more
than
one
level
to
reach
all
the
profile
endpoints.
All
levels
of
subscribers
Distributes
the
profile
to
all
subscribers
in
the
hierarchy.
For
example,
you
have
a
profile
hierarchy
where
a
dataless
profile
manager
subscribed
to
a
profile
manager,
and
the
dataless
profile
manager
has
an
endpoint
subscribed.
If
you
distribute
to
the
next
level
of
subscribers,
the
profile
manager
distributes
the
profile
only
to
the
dataless
profile
manager.
If
you
distribute
to
all
levels
of
subscribers,
the
profile
manager
distributes
the
profile
to
the
dataless
profile
manager
and
to
the
endpoint.
Select
this
option
if
you
want
to
distribute
a
profile
in
which
your
resource
is
the
only
subscriber.
Required
authorization
role
admin
Before
you
begin
v
Create
a
profile
manager
and
profile.
See
“Creating
profiles
and
profile
managers”
on
page
20
for
information.
v
Add
subscribers
to
a
profile
manager.
See
“Subscribing
resources
to
profile
managers”
on
page
21
for
information.
24
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
v
Add
a
resource
model
to
a
profile.
See
“Adding
a
resource
model
to
a
profile
manager”
on
page
22
for
information.
When
you
finish
Not
applicable
Procedure
Use
the
following
steps
to
distribute
a
profile:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window.
2.
Click
Profile
→
Distribute.
3.
Select
one
of
the
Distribute
To
options
based
on
the
following
descriptions:
Next
level
of
subscribers
Distributes
the
profile
only
to
the
subscribers
named
in
the
Distribute
to
These
Subscribers:
scrolling
list
of
the
Distribute
Profile
window.
This
selection
distributes
the
profile
only
to
the
subscribers
of
the
profile
manager.
It
does
not
distribute
to
lower-level
subscribers.
If
a
profile
manager
with
subscribers
resides
at
the
next
lower
level,
you
need
to
perform
the
distribution
process
from
profile
managers
at
more
than
one
level
to
reach
all
the
profile
endpoints.
All
levels
of
subscribers
Distributes
the
profile
to
all
subscribers
in
the
hierarchy.
For
example,
you
have
a
profile
hierarchy
where
a
dataless
profile
manager
subscribed
to
a
profile
manager,
and
the
dataless
profile
manager
has
an
endpoint
subscribed.
If
you
distribute
to
the
next
level
of
subscribers,
the
profile
manager
distributes
the
profile
only
to
the
dataless
profile
manager.
If
you
distribute
to
all
levels
of
subscribers,
the
profile
manager
distributes
the
profile
to
the
dataless
profile
manager
and
to
the
endpoint.
Select
this
option
if
you
want
to
distribute
a
profile
in
which
your
resource
is
the
only
subscriber.4.
Select
Make
each
subscriber’s
profile
an
EXACT
COPY
of
this
profile
from
the
Distribution
Will
options.
Additional
Information:
This
option
overwrites
the
subscriber’s
profile
with
an
exact
copy
of
the
profile
that
you
are
distributing.
Note:
Do
not
distribute
a
profile
to
an
IBM
Tivoli
Enterprise
Console
endpoint
with
the
Preserve
modifications
in
subscriber’s
copies
of
the
profile
option
set.
You
must
always
use
the
Make
each
subscriber’s
profile
an
EXACT
COPY
of
this
profile
option.
5.
Select
the
subscribers
to
receive
the
profile
using
the
following
steps:
a.
Click
the
subscribers
that
you
want
to
distribute
the
profile
to
from
the
Do
Not
Distribute
to
These
Subscribers
scrolling
list.
b.
Click
the
left
arrow
to
move
the
subscribers
to
the
Distribute
to
These
Subscribers
scrolling
list.
Note:
Make
sure
that
each
subscriber
in
the
Distribute
to
These
Subscribers
scrolling
list
is
either
a
profile
manager
or
a
supported
Tivoli
management
agent
endpoint.
IBM
Tivoli
Monitoring
does
not
support
other
types
of
endpoints.
6.
Click
one
of
the
following
buttons:
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
25
Distribute
&
Close
Distributes
the
profile
immediately,
closes
the
Distribute
Profile
window,
saves
the
settings
you
have
made,
and
returns
to
the
IBM
Tivoli
Monitoring
Profile
window.
Distribute
Distributes
the
profile
immediately,
saves
the
settings
you
have
made,
and
leaves
the
Distribute
Profile
window
open.
Schedule
Schedules
the
distribution
of
the
profile
with
the
Tivoli
Scheduler.
For
details
about
using
the
Tivoli
Scheduler,
refer
to
the
Tivoli
Management
Framework
User’s
Guide.
Configuring
the
IBM
Tivoli
Enterprise
Console
event
server
Objective
To
set
up
your
IBM
Tivoli
Enterprise
Console
event
server
to
process
Microsoft
Exchange
Server
events.
Background
information
You
must
set
up
the
event
server
before
events
can
be
sent
to
IBM
Tivoli
Enterprise
Console.
Use
the
Configure
Event
Server
task
to
set
up
the
IBM
Tivoli
Enterprise
Console
event
server.
The
Configure
Event
Server
task
performs
the
following
actions:
v
Imports
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
event
classes
and
rule
set
v
Imports
the
IBM
Tivoli
Monitoring
event
classes
(if
they
are
not
already
present)
v
Imports
the
IBM
Tivoli
Business
Systems
Manager
rule
set
(if
you
have
IBM
Tivoli
Business
System
Manager
in
your
environment)
v
Compiles
the
rule
base
to
incorporate
new
classes
and
rules
v
Loads
the
new
rule
base
(optional)
v
Optionally
stops
and
restarts
the
event
server
You
can
configure
only
one
IBM
Tivoli
Enterprise
Console
event
server
for
each
Tivoli
management
region.
When
you
have
interconnected
Tivoli
management
regions,
run
the
Configure
Event
Server
task
against
each
Tivoli
management
region
that
contains
a
IBM
Tivoli
Enterprise
Console
event
server.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
includes
event
classes
and
rules
specific
to
Microsoft
Exchange
Server.
Required
authorization
role
senior
Before
you
begin
Verify
that
IBM
Tivoli
Monitoring
Component
Services,
Version
5.1.1,
is
installed
on
each
computer
that
hosts
a
IBM
Tivoli
Enterprise
Console
event
server.
When
you
finish
Optionally
configure
IBM
Tivoli
Business
Systems
Manager
to
receive
events.
See
Appendix
A,
“Integrating
with
IBM
Tivoli
Business
Systems
Manager,”
on
page
71
for
more
information.
26
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Procedure
Follow
these
steps
to
perform
this
procedure
from
the
Tivoli
desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Component
Services
task
library
by
doing
the
following:
a.
In
the
Tivoli
desktop,
click
Desktop
→
Navigator.
b.
Select
TaskLibrary.
All
available
task
libraries
are
displayed
in
the
Resources
list.
c.
Select
IBM
Tivoli
Monitoring
Component
Services.
d.
Click
Go
To.2.
Double-click
Configure
Event
Server.
3.
Select
the
managed
node
on
which
you
want
configure
the
event
server.
4.
Select
Display
on
Desktop
to
display
the
output
of
the
task
on
the
desktop.
5.
Increase
the
timeout
value
in
the
Timeout
field
because
the
Configure
Event
Server
task
can
take
a
considerable
amount
of
time
to
finish.
6.
Click
Execute
&
Dismiss
to
display
the
Configure
Event
Server
window.
7.
Click
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
in
the
Product
to
configure
list.
Additional
information:
The
fields
on
the
Configure
Event
Server
window
are,
by
default,
completed
with
the
information
needed
to
run
this
procedure.
The
Configure
Event
Server
tasks
creates
a
new
rule
base
by
using
the
contents
of
an
existing
rule
base
as
a
starting
point.
The
name
of
the
new
rule
base
is
displayed
in
the
New
Rule
Base
Name
field
and
its
location
is
displayed
in
the
New
Rule
Base
Path
field.
Click
Help
for
information
about
the
other
options
in
this
window.
8.
Select
Load
Rule
Base
and
Restart
Server
from
the
Rule
Base
Activation
list.
9.
Click
Set
and
Execute.
A
confirmation
window
displays
the
job
status
after
the
task
completes.
Chapter
3.
Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
27
28
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
4.
Monitoring
Microsoft
Exchange
Server
with
resource
models
You
can
use
resource
models
to
constantly
monitor
the
performance
and
availability
of
your
Microsoft
Exchange
servers.
The
following
sections
describe
the
product
resource
models
and
provide
basic
configuration
information
for
those
resource
models.
Note:
Before
you
can
use
resource
models,
you
must
deploy
them
to
resources,
as
described
in
Chapter
3,
“Setting
up
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server,”
on
page
7.
Table
2
shows
the
goals
for
customizing
resource
models
and
where
to
find
the
information.
Table
2.
Working
with
resource
models
Goal
Where
to
find
information
Understand
resource
models
and
their
components.
“Resource
model
concepts”
Monitor
performance
and
availability
of
Microsoft
Exchange
servers.
“Monitoring
performance
and
availability”
on
page
31
Monitor
system
alerts
and
resource
model
events.
“Monitoring
alerts
and
events”
on
page
33
Customize
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
resource
models
based
on
the
needs
of
your
organization.
Chapter
5,
“Customizing
resource
models,”
on
page
35
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
descriptions
of
these
resource
models,
including
all
events,
thresholds,
and
parameters.
Resource
model
concepts
A
resource
model
captures
and
returns
information,
such
as
status,
about
a
resource
or
software
application
in
the
Tivoli
management
environment.
To
use
a
resource
model,
you
must
define
it
and
distribute
it
to
an
endpoint.
You
can
either
use
the
default
values
for
a
resource
model
to
collect
performance
data
or
customize
a
resource
model
to
match
specific
requirements
in
your
environment.
Distributing
resource
models
using
default
values
enables
you
to
begin
monitoring
immediately.
As
you
become
more
familiar
with
the
monitoring
process
and
feedback,
you
might
choose
to
customize
the
resource
model
information.
You
can
use
the
IBM
Tivoli
Monitoring
software
to
customize
existing
resource
models.
When
you
customize
a
resource
model,
you
can
modify
the
following
elements
of
the
resource
model
configuration:
Cycles
When
a
resource
model
runs
on
an
endpoint,
it
gathers
data
at
regular
intervals,
known
as
cycles.
The
interval
between
monitoring
cycles
is
the
©
Copyright
IBM
Corp.
2004
29
cycle
time
and
is
displayed
in
seconds.
A
resource
model
with
a
cycle
time
of
60
seconds
gathers
data
every
60
seconds.
Each
of
the
pre-configured
resource
models
has
a
default
cycle
time
that
you
can
modify
when
you
define
the
resource
model.
At
each
cycle,
the
resource
model
collects
data,
analyzes
it,
generates
the
events,
and
triggers
specified
actions.
The
data
collected
are
a
snapshot
of
the
status
of
the
resources
specified
in
the
resource
model.
Indications
and
events
An
indication
occurs
when
the
state
of
a
given
resource
meets
defined
criteria.
By
itself,
an
indication
does
not
trigger
any
specific
action.
Indications
are
aggregated
to
become
an
event.
An
event
is
a
notification
of
change
in
the
status
of
a
resource.
An
event
is
triggered
when
an
indication
occurs
and
does
not
occur
(referred
to
as
a
hole)
in
a
set
pattern
or
a
set
number
of
times.
When
you
define
an
event,
you
also
specify
whether
these
indications
must
be
consecutive,
or
whether
the
sequence
can
be
interrupted
by
one
or
more
monitoring
cycles
that
do
not
register
any
indication
(holes).
For
example,
for
the
Availability
resource
model,
an
event
is
triggered
when
an
indication
occurs
once
during
the
cycle
time.
However,
for
the
Message
Volume
resource
model,
an
event
is
triggered
when
an
indication
occurs
four
times
and
does
not
occur
twice
during
consecutive
cycle
times.
If
this
pattern
of
occurrences
and
holes
is
met,
an
event
is
generated.
The
event
notifies
the
system
administrator
about
the
state
of
a
specific
resource.
Events
can
trigger
an
action,
and,
if
enabled,
send
a
notification
to
the
IBM
Tivoli
Enterprise
Console
event
server
or
to
IBM
Tivoli
Business
Systems
Manager.
Thresholds
A
threshold
is
a
point
that
must
be
exceeded
before
a
resource
model
triggers
an
event.
Each
threshold
has
a
default
numeric
value
that
you
can
change.
Typically,
this
value
represents
a
limit
for
a
satisfactory
resource
state.
If
the
monitored
resource
exceeds
this
limit,
an
indication
occurs.
For
example,
if
you
are
monitoring
disk
space
and
do
not
want
it
to
drop
under
70%,
you
can
set
70
as
the
threshold.
The
system
generates
an
indication
each
time
disk
space
is
less
than
70%.
Parameters
A
parameter
is
a
value
that
is
used
to
control
how
a
resource
model
operates.
Parameters
can
represent
the
instances
that
you
want
to
monitor
(such
as
the
addresses
to
monitor
for
reachability)
or
a
limit
you
do
not
want
a
resource
to
exceed.
While
thresholds
can
only
be
numeric
values,
parameters
can
be
numeric
or
string
values.
Parameters
display
in
the
IBM
Tivoli
Monitoring
windows.
Some
resource
models
have
no
parameters,
others
have
one
or
more
parameters.
Scheduling
IBM
Tivoli
Monitoring
contains
a
scheduling
feature
that
enables
you
to
determine
a
period
within
which
monitoring
takes
place
and
specific
scheduling
rules.
The
scheduling
rules
enable
you
to
define
time
periods
on
specific
days
of
the
week
during
which
monitoring
takes
place.
Any
number
of
rules
can
be
defined,
allowing
you
to
set
up
a
complex
pattern
of
resource
monitoring
for
a
profile,
covering
the
time
periods
important
to
you.
30
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Logging
Resource
models
support
data
logging
to
collect
and
store
monitoring
data
in
a
local
database.
You
can
choose
to
store
raw
or
aggregated
data.
For
raw
data,
view
results
through
the
History
View
of
the
IBM
Tivoli
Monitoring
Web
Health
Console.
For
aggregated
data,
use
IBM
Tivoli
Data
Warehouse
to
view
the
results.
You
use
IBM
Tivoli
Monitoring
Resource
Model
Builder
to
develop
new
resource
models.
See
the
IBM
Tivoli
Monitoring
Resource
Model
Builder
User’s
Guide
for
information
about
how
to
develop
a
new
resource
model.
Monitoring
performance
and
availability
Monitoring
the
availability
and
performance
of
Microsoft
Exchange
servers
provides
a
picture
of
the
overall
health
of
your
Microsoft
Exchange
organization
at
a
given
time
and
notifies
you
to
potential
server
problems
or
message
bottlenecks
that
can
delay
the
processing
of
information
through
your
servers.
This
section
provides
information
about
the
following
topics:
v
“Monitoring
the
availability
of
servers”
v
“Monitoring
the
performance
of
Microsoft
Exchange
components”
on
page
32
Monitoring
the
availability
of
servers
Deploy
the
following
resource
models
to
monitor
the
status
and
availability
of
Microsoft
Exchange
servers
and
services.
Availability
resource
model
Monitors
the
status
of
the
different
services
(such
as
the
Simple
Transfer
Protocol)
that
make
up
the
Microsoft
Exchange
Server.
If
a
service
is
unavailable,
Microsoft
Exchange
Server
might
not
be
functioning
properly,
depending
on
the
service.
For
example,
Microsoft
Exchange
Server
cannot
process
messages
if
the
Simple
Transfer
Protocol
service
is
stopped.
All
available
services
on
an
endpoint
are
monitored
by
default.
You
can
specify
the
services
that
you
want
to
monitor
by
changing
the
value
for
the
parameter
for
each
service.
See
“Customizing
parameters”
on
page
38
for
information
about
changing
these
parameters.
Use
this
resource
model
to
monitor
services
continuously
to
ensure
the
availability
of
your
Microsoft
Exchange
Server.
Reachability
resource
model
Monitors
whether
Microsoft
Exchange
Server
servers
are
available
by
sending
an
message
to
and
receiving
a
response
from
an
account
on
a
server.
The
Reachability
resource
model
also
captures
the
round-trip
response
time
for
sending
an
message
and
receiving
a
response.
Monitor
one
address
on
each
Microsoft
Exchange
server
in
your
environment
to
ensure
each
server
can
be
reached
from
the
local
server.
Before
you
can
use
this
resource
model,
you
must
configure
each
Microsoft
Exchange
server
to
automatically
respond
to
an
message.
See
“Set
up
communication
for
the
Reachability
resource
model
(optional)”
on
page
15
for
information.
This
resource
model
uses
thresholds
to
define
the
amount
of
time
a
server
has
to
respond
to
an
message.
See
“Customizing
indications
and
events”
on
page
35
for
information
about
setting
threshold
levels.
Chapter
4.
Monitoring
Microsoft
Exchange
Server
with
resource
models
31
This
resource
model
uses
a
parameter,
addresses,
to
specify
the
server
or
servers
to
monitor.
See
“Customizing
parameters”
on
page
38
for
information
about
setting
this
parameter.
To
ensure
the
availability
of
your
servers,
run
this
resource
model
24
hours
per
day.
Monitoring
the
performance
of
Microsoft
Exchange
components
Deploy
the
following
resource
models
to
monitor
the
performance
and
communication
flows
for
mailboxes,
folders,
and
message
queues,
and
the
overall
space
consumption
of
the
Microsoft
Exchange
server.
Mailbox
Monitors
resource
model
Gathers
basic
information
about
the
individual
user
mailboxes
and
folders
defined
on
the
monitored
Microsoft
Exchange
server.
This
information
can
help
you
understand
and
manage
the
day-to-day
traffic
in
your
organization.
You
can
use
thresholds
to
determine
the
size
and
space
usage
limits
for
your
organization.
When
a
mailbox
or
folder
exceeds
a
specified
threshold,
you
are
alerted
and
can
take
preventive
or
corrective
action
(such
as
deleting
unneeded
messages
or
increasing
the
number
of
permitted
messages)
without
losing
service
to
the
mailbox
or
folder.
See
“Customizing
indications
and
events”
on
page
35
for
information
about
setting
threshold
levels.
Message
Volume
resource
model
Monitors
the
number
of
messages
for
both
Microsoft
Exchange
servers
and
message
agents.
A
high
number
of
messages
sent
or
received
can
indicate
a
space
or
availability
problem
with
a
Microsoft
Exchange
server,
while
a
high
number
of
connection
errors
related
to
messages
can
indicate
that
the
server
is
failing.
This
resource
model
monitors
SMTP
and
MTA
messages
and
connections,
Information
Store
messages,
and
the
space
usage
for
Information
Stores.
The
resource
model
counts
the
number
of
messages
sent
or
received
during
the
cycle
time.
That
number
is
compared
with
the
number
from
the
previous
monitoring
cycle
and
the
delta
amount
is
logged.
If
that
delta
exceeds
the
threshold
that
you
define,
an
event
is
triggered.
See
“Customizing
indications
and
events”
on
page
35
for
information
about
setting
threshold
levels.
Run
this
resource
model
24
hours
per
day
to
constantly
monitor
your
critical
message
services.
Queues
resource
model
Monitors
Microsoft
Exchange
Server
message
queues,
including
message
transfer
agent
(MTA)
queues,
information
store
(IS)
queues,
and
Simple
Transfer
Protocol
(SMTP)
queues.
This
resource
model
monitors
queue
performance
by
measuring
the
number
of
items
in
a
queue.
A
high
number
of
messages
in
a
queue
can
indicate
a
problem
with
a
specific
queue.
Depending
on
the
queue,
there
might
be
a
problem
with
a
related
service,
a
looping
or
corrupted
message,
or
with
the
Exchange
Server
that
is
supposed
to
accept
the
messages.
This
resource
model
uses
thresholds
to
define
the
permitted
length
of
each
queue.
See
“Customizing
indications
and
events”
on
page
35
for
information
about
setting
threshold
levels.
32
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Run
this
resource
model
24
hours
per
day
to
monitor
the
flow
of
messages.
Space
Usage
resource
model
Monitors
space
usage
in
the
Microsoft
Exchange
Server
to
ensure
that
the
server
has
adequate
space
for
operation.
This
resource
model
gathers
size
and
growth
information
about
the
Microsoft
Exchange
Server
application,
databases,
log
files,
and
information
stores.
This
resource
model
monitors
the
following
space
usage
elements
for
the
overall
Microsoft
Exchange
Server,
storage
groups,
and
mailbox
and
public
information
stores:
v
Percent
free
space
(indicates
the
size
of
Microsoft
Exchange
Server
or
the
log
files
for
Microsoft
Exchange
Server)
v
Database
percentage
of
space
used
(size)
v
Database
growth
This
resource
model
uses
thresholds
to
define
the
permitted
percentage
of
available
free
space
and
the
rate
of
growth
for
the
server
and
its
components.
See
“Customizing
indications
and
events”
on
page
35
for
information
about
setting
threshold
levels.
Monitoring
alerts
and
events
Alerts
and
events
notify
you
to
changes
in
your
Microsoft
Exchange
servers.
This
section
provides
information
about
the
following
topics:
v
“Monitoring
Microsoft
Exchange
Server
alerts”
v
“Viewing
events
with
IBM
Tivoli
Enterprise
Console”
on
page
34
Monitoring
Microsoft
Exchange
Server
alerts
Microsoft
Exchange
Server
alerts
and
error
conditions
are
logged
in
system
event
log
files.
The
Logs
resource
model
monitors
the
contents
of
these
files.
When
an
alert
is
logged
to
an
event
log
file,
you
are
immediately
notified
with
an
event
in
the
IBM
Tivoli
Enterprise
Console.
The
event
specifies
the
file
that
contains
the
alert
and
the
ID
of
the
alert.
You
can
then
view
the
specified
file
and
search
for
the
event.
Notes:
1.
To
monitor
event
log
messages,
you
must
configure
your
services
to
send
events
to
the
event
log
files.
If
you
do
not
configure
your
services
in
this
way,
the
Logs
resource
model
does
not
send
events
to
IBM
Tivoli
Enterprise
Console.
Use
the
DiagnosticLoggingSet
task
to
configure
logging
for
your
services.
See
Chapter
6,
“Monitoring
performance
and
availability
with
tasks
and
jobs,”
on
page
45
for
additional
information.
2.
If
you
clear
the
event
log
files
between
resource
model
cycles,
events
generated
before
and
after
the
clearing
action
was
processed
are
not
captured.
You
can
monitor
the
event
log
files
both
by
service
and
by
event
severity.
This
filtering
enables
you
to
focus
your
monitoring
of
alerts,
since
all
system
actions
are
logged
into
the
event
log
files.
You
are
alerted
only
when
an
alert
matching
your
specified
criteria
(such
as
a
critical
error
with
the
MSExchangeIS
service)
occurs
and
you
have
the
detailed
information
you
need
to
locate
the
specific
alert.
To
monitor
events
by
severity,
use
the
Event
Severity
parameter,
a
Boolean
value
for
each
of
the
available
severities.
Microsoft
Exchange
Server
events
have
the
following
corresponding
IBM
Tivoli
Enterprise
Console
values:
Chapter
4.
Monitoring
Microsoft
Exchange
Server
with
resource
models
33
Microsoft
Exchange
Server
event
severities
Corresponding
IBM
Tivoli
Enterprise
Console
events
Error
Critical
Warning
Warning
Information
Harmless
Success
Audit
Harmless
Failure
Audit
Warning
To
configure
the
resource
model
to
monitor
the
event
log
files
for
only
critical
errors,
set
the
Error
value
to
TRUE
and
all
other
values
to
FALSE.
To
monitor
by
service,
use
the
Event
Source
parameter,
a
Boolean
value
for
each
of
the
available
Microsoft
Exchange
services.
By
default,
the
following
services
are
monitored:
v
Microsoft
Exchange
Event
v
Microsoft
Exchange
Information
Store
v
Microsoft
Exchange
MTA
Stacks
v
Microsoft
Exchange
System
Attendant
See
“Customizing
parameters”
on
page
38
for
information
about
setting
these
parameters.
Viewing
events
with
IBM
Tivoli
Enterprise
Console
The
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
resource
models
send
events
to
the
IBM
Tivoli
Enterprise
Console
event
server
when
conditions
change
on
the
resources
that
you
are
monitoring.
An
event
carries
information
including
the
event
class,
event
identity,
severity,
location
(host
where
the
event
originated),
and
description.
The
event
that
is
sent
depends
on
the
resource
model
that
you
deploy
and
how
it
is
configured.
For
example,
you
deploy
the
Availability
resource
model
to
an
Microsoft
Exchange
server
and
configure
the
resource
model
to
monitor
the
status
of
the
MSExchangeIS
service.
If
the
MSExchangeIS
service
stops
running,
the
resource
model
sends
the
Microsoft_Exchange_Server_Stopped_Service
event
to
the
IBM
Tivoli
Enterprise
Console
event
server.
IBM
Tivoli
Enterprise
Console
provides
tools
for
the
following
functions:
v
Receiving
events
from
various
sources
v
Processing
events
using
rules
v
Grouping
events
and
delegating
the
groups
selectively
to
administrators
v
Viewing
events
from
multiple
sources
at
a
console
IBM
Tivoli
Enterprise
Console
provides
both
a
Java-based
and
a
Web-based
console
for
viewing
events.
For
information
about
viewing
events,
see
the
IBM
Tivoli
Enterprise
Console
User’s
Guide.
34
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
5.
Customizing
resource
models
The
following
sections
describe
how
to
customize
the
resource
models
provided
with
the
product
to
ensure
that
they
monitor
your
resources
appropriately.
Goal
Where
to
find
information
Customize
indication
rules
so
that
resources
are
monitored
and
events
generated
in
the
manner
most
appropriate
to
your
environment.
“Customizing
indications
and
events”
Specify
a
task
so
you
can
determine
corrective
or
reporting
tasks
for
an
event.
“Specifying
a
response
task
for
an
indication”
on
page
36
Send
a
notice
in
response
to
an
event
so
you
can
take
the
appropriate
actions
or
responses.
“Notifying
administrators
when
an
event
occurs”
on
page
37
Change
the
parameters
of
a
resource
model
to
customize
the
resources
that
are
monitored.
“Customizing
parameters”
on
page
38
Customize
the
time
periods
and
days
when
monitoring
takes
place.
“Scheduling
when
a
resource
model
runs”
on
page
39
Customize
the
way
that
a
resource
model
logs
data.
“Logging
data
for
a
resource
model”
on
page
41
Manage
IBM
Tivoli
Monitoring,
profiles,
and
resource
models
on
endpoints
and
IBM
Tivoli
Monitoring
from
the
gateway.
“Managing
profiles
and
resource
models”
on
page
42
Determine
which
resource
models
are
running
on
an
endpoint.
“Determining
which
resource
models
are
running
on
endpoints”
on
page
44
Customizing
indications
and
events
Objective
To
customize
a
resource
model
to
generate
an
event
that
notifies
you
when
a
monitored
resource
is
not
performing
as
required.
Background
information
You
can
customize
the
following
values
for
indications
and
events:
v
Occurrences
v
Holes
v
Send
TEC
Events
v
Severity
v
Tasks
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model,
including
the
default
settings
for
an
indication.
©
Copyright
IBM
Corp.
2004
35
When
you
finish
Modify
any
other
resource
model
settings
that
you
want
to
change.
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wdmeditprf
command
to
customize
a
resource
model
for
a
profile.
See
the
IBM
Tivoli
Monitoring
documentation
for
information
about
this
command.
Desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window
by
following
these
steps:
a.
Double-click
a
policy
region
icon
to
open
the
policy
region.
b.
Double-click
the
profile
manager
icon
to
open
the
profile
manager.
c.
Double-click
the
profile
icon
in
which
you
want
to
customize
a
resource
model.2.
Select
the
resource
model
that
you
want
to
customize.
3.
Click
Edit
to
open
the
Edit
Resource
Model
window.
4.
Click
Indications
to
open
the
Indications
and
Actions
window
and
the
indications
relevant
to
the
selected
resource
model.
5.
Select
the
indication
you
want
to
customize.
6.
Make
the
following
changes
as
appropriate
for
your
requirements:
Send
event
to
IBM
Tivoli
Enterprise
Console
Specifies
to
send
any
event
triggered
by
an
indication
to
IBM
Tivoli
Enterprise
Console.
Send
event
to
IBM
Tivoli
Business
Systems
Manager
Specifies
to
send
any
event
triggered
by
an
indication
to
IBM
Tivoli
Business
Systems
Manager.
Occurrences
Specifies
the
number
of
monitoring
cycles
during
which
an
indication
can
occur
before
an
event
is
triggered.
This
value
works
in
conjunction
with
the
Holes
option.
Holes
Specifies
the
number
of
monitoring
cycles
during
which
an
indication
cannot
occur
before
an
event
is
triggered.
This
value
works
in
conjunction
with
the
Occurrences
option.
Severity
Specifies
the
severity
for
any
events
generated
in
response
to
indications:
fatal,
critical,
warning,
harmless,
or
minor.
Execute
Tasks
Specifies
any
tasks
to
run
automatically
in
response
to
the
indication.7.
Click
Apply
Changes
&
Close
to
save
your
changes
to
the
indication.
Specifying
a
response
task
for
an
indication
Objective
To
automatically
run
a
task
in
response
to
an
indication.
36
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Background
information
You
can
select
one
or
more
tasks
to
perform
when
an
indication
is
raised.
These
tasks
can
access
the
IBM
Tivoli
Monitoring
event
name
by
accessing
the
environment
variables.
For
information
about
each
automated
task,
see
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Modify
any
other
resource
model
settings
that
you
want
to
change.
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wdmeditprf
command
to
customize
a
resource
model
for
a
profile.
Desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window.
2.
Select
the
resource
model
that
you
want
to
customize
from
the
IBM
Tivoli
Monitoring
Profile
window.
3.
Click
Edit
to
open
the
Edit
Resource
Model
window.
4.
Click
Indications
to
open
the
Indications
and
Actions
window
and
the
indications
appropriate
to
the
selected
resource
model.
5.
Select
the
indication
for
which
you
want
to
run
a
task.
6.
Click
Tasks
in
the
Action
List
area
of
the
Indications
and
Actions
window.
7.
Double-click
the
appropriate
task
library
from
the
list
in
the
Libraries
panel.
The
tasks
contained
in
the
library
are
displayed
in
the
Tasks
panel.
8.
Double-click
the
appropriate
task
in
the
Tasks
panel.
9.
Specify
the
appropriate
parameters
in
the
Configure
Task
window.
Additional
information:
Run
the
wlsnotif
-g
command
to
see
the
available
Notice
Groups.
10.
Click
Change
&
Close
to
add
the
task
to
the
Action
List
panel
in
the
Indications
and
Actions
window.
—OR—
Click
Apply
Change
and
Close
to
save
the
updated
action
information.
—OR—
Click
Modify
and
Close
to
save
the
updated
resource
model.
Notifying
administrators
when
an
event
occurs
Objective
To
notify
administrators
when
an
event
occurs
so
that
administrators
can
take
appropriate
actions
to
address
the
event.
Chapter
5.
Customizing
resource
models
37
Background
information
To
set
up
tasks
that
send
notices
when
an
event
occurs,
you
use
the
procedure,
“Specifying
a
response
task
for
an
indication”
on
page
36.
In
this
procedure,
you
specify
the
IBM
Tivoli
Monitoring
Utility
Tasks
task
library
and
the
send
notices
task.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Modify
any
other
resource
model
settings
that
you
want
to
change:
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wdmeditprf
command
to
customize
a
resource
model
for
a
profile.
Desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window.
2.
Select
the
resource
model
that
you
want
to
customize.
3.
Click
Edit
to
open
the
Edit
Resource
Model
window.
4.
Click
Indications
to
open
the
Indications
and
Actions
window
and
the
indications
appropriate
to
the
selected
resource
model.
5.
Select
the
indication
that
you
want
to
generate
a
task
from
the
Indications
and
Actions
window.
6.
Click
Tasks
in
the
Action
List
window
next
to
the
Action
List
to
open
the
Tasks
window.
7.
Double-click
the
IBM
Tivoli
Monitoring
Utility
Tasks
task
library
in
the
scroll
list
of
the
Libraries
panel.
The
tasks
in
the
IBM
Tivoli
Monitoring
Utility
Tasks
task
library
are
displayed
in
the
Tasks
panel.
8.
Double-click
dm_mn_send_notice
in
the
Tasks
panel
to
open
the
Configure
Task
window.:
9.
Specify
the
appropriate
parameters
in
the
Configure
Task
window.
Additional
Information:
Run
the
wlsnotif
-g
command
to
see
the
available
notice
groups.
10.
Click
Change
&
Close
to
add
the
task
to
the
Action
List
panel
in
the
Indications
and
Actions
window
so
the
list
of
tasks
runs
when
the
indication
occurs.
Customizing
parameters
Objective
To
change
the
parameters
of
a
resource
model
to
customize
the
resources
that
are
monitored.
38
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Background
information
Some
resource
models
have
one
or
more
parameters.
Each
parameter
can
take
the
form
of
a
list
of
strings,
a
list
of
numeric
values,
a
Boolean
list
of
predetermined
values
from
which
you
can
make
any
combination
of
selections,
or
a
choice
list
of
mutually
exclusive
alternatives.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Modify
any
other
resource
model
settings
that
you
want
to
change.
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wdmeditprf
command
to
customize
a
resource
model
for
a
profile.
Desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window.
2.
Select
the
resource
model
that
you
want
to
customize
from
the
IBM
Tivoli
Monitoring
Profile
window.
3.
Click
Edit
to
open
the
Edit
Resource
Model
window.
4.
Click
Parameters.
5.
Select
the
type
of
parameter
from
the
Name
drop-down
list
in
the
Parameters
window.
6.
Add
or
delete
the
parameter
values
as
required
by
checking
or
clearing
the
boxes.
7.
Click
Apply
Changes
and
Close
to
save
your
changes.
Scheduling
when
a
resource
model
runs
Objective
To
determine
the
time
periods
and
days
when
monitoring
takes
place.
Background
information
IBM
Tivoli
Monitoring
contains
a
scheduling
feature
that
enables
you
to
determine
when
monitoring
takes
place
and
specific
scheduling
rules.
You
can
divide
the
overall
collection
period
into
active
and
inactive
intervals
by
applying
one
or
more
schedule
rules.
The
scheduling
rules
enable
you
to
define
time
periods
on
specific
weekdays
during
which
monitoring
takes
place.
You
can
define
any
number
of
rules
that
enable
you
to
set
up
a
complex
pattern
of
resource
monitoring
for
a
profile
and
covers
the
periods
that
you
want
to
monitor.
The
scheduled
times
are
always
interpreted
as
local
times,
enabling
you
to
set
up
a
single
rule
that
monitors
the
same
local
time
period
in
different
time
zones.
For
example,
if
your
region
covers
several
time
zones,
but
you
want
to
monitor
Chapter
5.
Customizing
resource
models
39
morning
activities
in
each
time
zone,
a
single
rule
defining
the
monitoring
period
of
between
08:00
and
13:00
is
interpreted
locally
in
each
of
the
time
zones,
so
that
you
monitor
the
same
relative
period.
All
of
the
times
for
events
or
activities
reported
from
endpoints
or
gateways
are
also
logged
in
the
local
time
of
the
system
where
they
originated.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Modify
any
other
resource
model
settings
that
you
want
to
change.
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wdmeditprf
command
to
customize
a
resource
model
for
a
profile.
Desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window.
2.
Select
the
resource
model
that
you
want
to
customize
from
the
IBM
Tivoli
Monitoring
Profile
window.
3.
Click
Edit
to
open
the
Edit
Resource
Model
window.
4.
Click
Schedule
to
open
the
Scheduling
window.
Additional
information:
The
Scheduling
window
contains
the
following
groups
of
options:
Schedule
Sets
the
data
collection
period.
By
default,
all
resource
models
are
set
to
always
collect
data.
Schedule
Rules
Manages
time
intervals
during
which
the
resource
model
is
active.
Rule
Editor
Creates
and
edits
schedule
rules.5.
Clear
the
Always
check
box
if
you
want
to
customize
the
schedule.
6.
If
you
clear
the
Always
check
box,
do
the
following
to
customize
the
schedule:
a.
Click
New
Rule
in
the
Schedule
Rules
area.
b.
Type
a
name
for
the
rule
in
the
Rule
Name
text
box
of
the
Rule
Editor
panel.
c.
Select
one
or
more
items
in
the
weekday
list
to
specify
the
day
or
days
on
which
you
want
the
collections
active
during
the
collection
period.
Additional
information:
Use
the
Shift
or
Ctrl
key
as
necessary
to
select
more
than
one
day
from
the
list.
d.
Set
the
Start
Date
and
Stop
Date
for
the
collection
activity.
e.
Set
the
Start
Time
and
Stop
Time
for
the
collection
activity
or
select
the
All
Day
check
box.
40
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Additional
information:
Times
are
always
interpreted
as
local
time
where
the
endpoint
engine
runs.
Setting
a
time
interval
of
08:00
to
13:00
ensures
that
monitoring
takes
place
between
those
times
in
all
time
zones
to
which
you
distribute
the
profile.
f.
Click
Set
Rule.
Your
new
rule
is
displayed
in
the
Schedule
Rules
list.
Additional
information:
To
display
the
details
of
any
rule,
select
the
rule
in
the
Schedule
Rules
list.
The
rule
settings
are
displayed
in
the
Rule
Editor
section
of
the
window.
If
the
Schedule
Rules
list
contains
more
than
one
schedule
rule,
all
the
time
intervals
are
respected,
and
rules
are
combined
by
adding
together
the
time
periods
they
define.
For
example,
if
you
specify
a
rule
that
requests
monitoring
between
8:00
and
14:00
every
day
and
another
that
requests
all-day
monitoring
on
Fridays,
the
sum
of
the
two
rules
gives
all-day
monitoring
only
on
Fridays,
and
monitoring
between
8:00
and
14:00
on
all
other
days.
If
the
second
rule
instead
requested
monitoring
from
12:00
to
18:00
on
Fridays,
the
sum
of
the
rules
would
give
monitoring
between
8:00
and
18:00
on
Fridays
and
between
08:00
and
14:00
on
all
other
days.7.
Click
Modify
&
Close
to
save
your
rule
and
close
the
Scheduling
window.
Logging
data
for
a
resource
model
Objective
To
customize
the
way
that
a
resource
model
logs
data.
Background
information
You
can
configure
a
resource
model
to
write
logged
data
in
a
local
database
so
you
can
view
the
data
through
the
IBM
Tivoli
Monitoring
Web
Health
Console.
You
can
store
one
of
the
following
types
of
data
in
the
database:
Raw
data
Data
is
written
exactly
as
the
resource
model
collects
it.
All
the
monitored
values
are
collected
and
copied
in
the
database.
Aggregated
data
Data
is
collected
and
aggregated
at
fixed
intervals
that
you
define
(Aggregation
Period).
Only
the
aggregated
values
are
written
in
the
database.
The
aggregated
data
is
calculated
on
the
basis
of
one
or
more
of
the
following
options:
v
Maximum
v
Minimum
v
Average
TEDW
data
Data
is
aggregated
for
use
in
the
IBM
Tivoli
Data
Warehouse.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Modify
any
other
resource
model
settings
that
you
want
to
change.
Chapter
5.
Customizing
resource
models
41
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wdmeditprf
command
to
customize
a
resource
model
for
a
profile.
Desktop:
1.
Open
the
IBM
Tivoli
Monitoring
Profile
window.
2.
Select
the
resource
model
that
you
want
to
customize
from
the
IBM
Tivoli
Monitoring
Profile
window.
3.
Click
Edit
to
open
the
Edit
Resource
Model
window
4.
Click
Logging
to
open
the
Logging
window.
5.
Select
the
Enable
Data
Logging
check
box
in
the
Data
Logging
Settings
pane
to
enable
logging.
Additional
information:
This
enables
the
Aggregate
Data
and
Historical
Period
options.
6.
Perform
the
following
steps
to
specify
the
aggregation
rule
applied
to
the
data
before
it
is
written
to
the
database:
a.
Set
Hours
and
Minutes
of
the
Aggregation
Period
to
the
required
values.
b.
Select
one
or
more
of
the
following
functions
to
perform
on
the
numerical
data
collected
during
the
aggregation
period
before
it
is
written
to
the
database:
Maximum
Calculates
and
logs
the
peak
value
in
each
aggregation
period.
Minimum
Calculates
and
logs
the
lowest
value
in
each
aggregation
period.
Average
Calculates
and
logs
the
average
of
all
values
in
each
aggregation
period.
Average
is
the
default
setting.7.
If
you
want
to
log
the
raw
data
instead
of
aggregate
data,
do
the
following:
a.
Clear
the
Aggregate
Data
check
box.
b.
Select
Raw
Data.
c.
Optional:
If
IBM
Tivoli
Data
Warehouse
is
installed,
you
can
check
the
TEDW
Data
option
to
store
the
raw
data
for
use
in
IBM
Tivoli
Data
Warehouse.
Note:
You
cannot
choose
both
aggregate
data
and
raw
data
at
the
same
time,
or
aggregate
data
and
TEDW
data
at
the
same
time.
8.
Set
the
Hours
and
Minutes
of
the
Historical
Period
to
the
required
values.
9.
Click
Apply
Changes
and
Close
to
save
your
changes
and
close
the
Logging
window.
Managing
profiles
and
resource
models
Objective
To
manage
profiles
and
resource
models
on
endpoints.
Also,
to
manage
IBM
Tivoli
Monitoring
from
the
gateway.
42
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Background
information
Not
applicable.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Not
applicable.
Procedure
Use
the
wdmcmd
command
to
stop
or
restart
IBM
Tivoli
Monitoring
on
one
or
more
endpoints
from
a
gateway
or
server.
Use
the
wdmdistrib
command
to
distribute
a
profile
to
one
or
more
subscribers.
Use
the
wdmeng
command
to
stop
or
start
profiles
or
resource
models
at
endpoints
or
to
delete
profiles
at
endpoints.
Use
the
wdmlseng
command
to
return
a
list
and
the
status
of
all
resource
models
that
have
been
distributed
on
a
specified
endpoint.
Use
the
wdmtrceng
command
to
set
the
trace
parameters
of
the
IBM
Tivoli
Monitoring
engine
at
the
endpoint.
Use
the
wdmmn
command
to
stop
or
start
selected
IBM
Tivoli
Monitoring
processes
on
one
or
all
gateways.
See
the
IBM
Tivoli
Monitoring
documentation
for
more
information
about
the
wdm
commands.
Determining
which
resource
models
have
been
distributed
to
endpoints
Objective
To
determine
which
resource
models
have
been
distributed
to
an
endpoint.
Background
information
Open
an
endpoint
window
from
the
desktop
to
see
if
a
monitor
has
been
distributed
to
it.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Not
applicable.
Chapter
5.
Customizing
resource
models
43
Procedure
You
can
perform
this
procedure
from
the
Tivoli
desktop
only.
Desktop:
1.
Open
the
Profile
Manager
window
by
following
these
steps:
a.
Double-click
a
policy
region
icon
to
open
the
policy
region.
b.
Double-click
the
profile
manger
icon
to
open
the
Profile
Manager
window.2.
Double-click
the
endpoint
icon
from
the
Subscribers
area
to
open
the
endpoint
window.
3.
Double-click
the
monitoring
profile
icon
to
open
the
TME
10
Distributed
Monitoring
Profile
Properties
window,
which
lists
the
resource
models
distributed
to
the
endpoint.
Determining
which
resource
models
are
running
on
endpoints
Objective
To
determine
which
resource
models
are
running
on
an
endpoint.
Background
information
Use
the
Tivoli
command
line
to
determine
which
monitors
are
running
on
an
endpoint.
Required
authorization
role
admin
Before
you
begin
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
information
about
each
resource
model.
When
you
finish
Not
applicable.
Procedure
Use
the
wdmlseng
command
to
determine
which
resource
models
are
running
on
an
endpoint.
For
example,
to
view
the
list
of
resource
models
on
an
endpoint,
enter
the
following
command.
wdmlseng
-e
endpoint
Refer
to
the
IBM
Tivoli
Monitoring
User’s
Guide
for
more
information.
44
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
6.
Monitoring
performance
and
availability
with
tasks
and
jobs
This
chapter
provides
information
about
using
tasks
and
jobs
to
manage
your
Microsoft
Exchange
Server
resources.
Table
3
shows
the
options
to
manage
tasks
and
jobs.
Table
3.
Working
with
tasks
and
jobs
Goal
Where
to
find
information
Determine
which
tasks
to
run
based
on
the
needs
of
your
organization.
“IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks”
Monitor
the
status
of
your
resources
with
tasks.
“Monitoring
with
tasks”
on
page
46
Run
a
task
to
perform
a
specific
operation.
“Running
a
task”
on
page
48
Define
a
standard
task
with
specific
arguments
to
customize
the
task.
“Customizing
a
task”
on
page
50
Create
a
job
from
a
task
so
that
it
can
be
scheduled
to
run.
“Creating
a
job”
on
page
51
Run
a
job
with
predefined
arguments.
“Running
a
job”
on
page
53
Schedule
jobs
to
run
at
specified
times.
“Scheduling
a
job”
on
page
54
The
installation
process
installs
the
task
library
in
the
product
policy
region.
The
task
library
contains
default
policies
that
affect
how
the
task
library
works.
The
policy
region
containing
the
task
library
defines
task
and
job
policies.
Default
policies
set
profile
manager
options
and
endpoints
for
tasks.
Validation
policies
control
the
creation
and
execution
of
tasks.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
provides
the
following
tasks:
Table
4.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
Task
name
Description
DiagnosticLoggingSet
Sets
the
diagnostic
logging
level
for
a
service.
DiagnosticLoggingView
Reports
the
diagnostic
logging
level
for
all
Microsoft
Exchange
services.
DiscoverExchangeServers
Discovers
Microsoft
Exchange
servers
that
reside
on
Tivoli
endpoints
and
registers
them
with
the
Tivoli
management
region
server
as
an
application
proxy
object.
DisplayServerInfo
Returns
server
information
for
the
target
server.
©
Copyright
IBM
Corp.
2004
45
Table
4.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
(continued)
Task
name
Description
DisplayExchangeServerStatus
Returns
the
status
of
each
of
the
installed
Microsoft
Exchange
services
on
the
target
server.
InactiveReport
Identifies
inactive
public
folders
and
mailboxes.
InactiveReportStartCollection
Initiates
the
logging
of
last
logon
data
for
targeted
public
folders
and
mailboxes.
InactiveReportStopCollection
Stops
the
logging
of
last
logon
data
for
targeted
public
folders
and
mailboxes.
LimitReport
Lists
mailboxes
that
exceed
message
count
or
storage
limits.
MailboxInfo
Returns
information
about
the
mailbox
objects
for
the
server.
MSExchangeAuthentication
Modifies
the
user
name,
password,
user
domain,
and
user
profile
attributes
for
a
previously
discovered
Microsoft
Exchange
Server
object.
MSExchangeTBSMDiscovery
Defines
Microsoft
Exchange
Server
application
proxy
objects
to
IBM
Tivoli
Business
Systems
Manager.
RunESEUTILChecksum
Runs
the
ESEUTIL
Checksum
utility
on
the
target
server.
RunESEUTILDefrag
Runs
the
ESEUTIL
defragmentation
utility
on
the
target
server.
RunESEUTILInteg
Runs
the
ESEUTIL
Integrity
utility
on
the
target
server.
RunISINTEG
Runs
the
ISINTEG
utility
on
the
target
server.
RunMTACHECK
Runs
the
MTACHECK
utility
on
the
target
server.
StartExchangeServices
Starts
the
services
that
make
up
a
Microsoft
Exchange
Server.
StopExchangeServices
Stops
the
services
that
make
up
a
Microsoft
Exchange
Server.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
descriptions
of
these
tasks.
Monitoring
with
tasks
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
monitor
resources
and
address
availability
issues
(such
as
starting
a
stopped
service).
The
following
sections
discuss
the
actions
that
you
can
take
with
tasks:
v
Gathering
information
about
resources
v
Starting
and
stopping
services
46
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
descriptions
of
the
tasks,
including
GUI
field
descriptions
and
CLI
syntax.
Gathering
information
with
tasks
The
following
tasks
provide
availability
and
performance
information
about
the
current
status
of
resources:
DisplayExchangeServerStatus
Returns
the
status
of
each
installed
Microsoft
Exchange
service
on
the
target
server.
Use
this
task
to
determine
whether
required
services
are
running.
If
a
needed
service
is
not
running
(such
as
MSExchangeIS),
you
can
start
it
with
the
StartExchangeServices
task.
MailboxInfo
Returns
detailed
information
about
mailbox
and
folders
on
the
target
server.
Use
this
task
to
determine
how
a
mailbox
is
being
used,
such
as
the
number
of
messages
that
it
contains
and
the
last
time
it
was
accessed.
Starting
and
stopping
services
There
are
two
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
that
address
the
availability
of
resources:
StartExchangeServices
Starts
the
services
that
make
up
a
Microsoft
Exchange
Server.
You
can
also
use
this
task
to
continue
paused
services.
Note:
You
cannot
start
paused
services;
you
must
continue
them.
Attempting
to
start
a
paused
service
does
not
change
the
status
of
that
service.
You
can
only
start
stopped
services.
Selecting
a
service
to
start
might
start
more
than
one
service
because
of
dependencies
between
services.
For
example,
starting
the
MSExchangeIS
service
also
starts
the
MSExchangeSA
service.
The
StartExchangeServices
task
reports
these
dependencies
when
initiating
start
commands.
You
can
use
this
task
as
a
response
task
from
the
Availability
resource
model.
StopExchangeServices
Stops
(or
pauses)
the
services
that
make
up
a
Microsoft
Exchange
Server.
Note:
You
cannot
stop
paused
services.
You
can
only
stop
running
services.
If
you
need
to
stop
a
paused
service,
use
the
StartExchangeServices
task
to
continue
the
service,
then
run
this
task
to
stop
the
service.
Selecting
a
service
to
stop
might
stop
more
than
one
service
because
of
dependencies
between
services.
For
example,
stopping
the
MSExchangeSA
service
also
stops
the
MSExchangeIS
service.
The
StopExchangeServices
task
reports
these
dependencies
when
initiating
stop
commands.
You
can
use
this
task
as
a
response
task
from
the
Availability
resource
model.
Chapter
6.
Monitoring
performance
and
availability
with
tasks
and
jobs
47
Running
a
task
Objective
To
run
one
of
the
standard
tasks
in
the
task
library.
Background
information
A
task
is
an
action
that
must
be
routinely
performed
on
selected
endpoints
or
managed
nodes
for
systems
throughout
the
network.
A
task
defines
the
executable
files
to
be
run,
the
authorization
role
required
to
run
the
task,
and
the
user
or
group
name
under
which
the
task
is
run.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
provides
standard
tasks
in
a
task
library.
Standard
tasks
run
on
any
system
without
consideration
of
platform
type.
Required
authorization
roles
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
the
authorization
role
required
for
each
task.
Before
you
begin
Not
applicable
When
you
finish
Not
applicable
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
Line:
Use
the
wruntask
command
to
run
a
task.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
information
about
running
tasks
from
the
command
line.
For
more
information
about
the
wruntask
command,
see
the
Tivoli
Framework
Reference
Manual.
Tivoli
desktop:
1.
Open
the
task
library
window
by
performing
the
following
steps:
a.
Open
the
Tivoli
desktop.
b.
Double-click
the
Monitoring
for
Microsoft
Exchange
Server
policy
region
icon
to
display
the
policy
region.
c.
Double-click
ITMMicrosoftExchangeServerTasks
to
open
the
product
task
library
window.
2.
Double-click
the
task
icon
that
you
want
to
run
to
open
the
Execute
Task
window.
Additional
information:
The
Execute
Task
window
is
a
generic
window
that
contains
execution
parameters
for
all
tasks.
3.
Select
one
of
the
following
check
boxes
in
the
Execution
Mode
group
box:
Parallel
Runs
the
task
simultaneously
on
all
targets.
Parallel
is
typically
the
fastest
method
of
execution.
Serial
Runs
the
task
sequentially
on
all
targets
in
alphabetical
order.
48
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Staged
Runs
the
task
on
all
targets
in
alphabetical
order
according
to
a
schedule
you
specify.
Staged
execution
is
useful
if
you
are
running
the
task
on
a
large
number
of
endpoints.
Complete
Step
5
to
specify
the
Staging
Count
(number
of
targets
to
run
against
per
stage)
and
the
Staging
Interval
(number
of
seconds
between
each
set).
4.
Type
a
timeout
value
(in
seconds)
for
the
task
in
the
Timeout
text
box.
Additional
information:
The
Timeout
value
does
not
stop
the
task.
This
value
specifies
the
number
of
seconds
the
Tivoli
desktop
waits
for
the
task
to
complete
before
it
issues
an
error.
The
task
continues
to
run
on
the
endpoint
without
displaying
the
output
results.
Setting
an
early
timeout
enables
your
Tivoli
desktop
to
become
available
again
if
the
task
takes
a
long
time
to
run.
The
default
is
60
seconds.
If
the
task
takes
longer
to
complete
than
the
specified
Timeout
and
is
running
in
Serial
or
Staged
mode,
the
product
moves
on
to
other
endpoints
after
this
time
expires.
5.
Optional:
If
you
selected
Staged
in
Step
3,
specify
the
number
of
endpoints
to
include
in
each
staged
set
in
the
Staging
Count
text
box
and
the
number
of
seconds
between
the
startup
time
of
each
set
in
the
Staging
Interval
text
box.
6.
Select
one
or
more
of
the
following
output
format
options:
Header
Includes
a
descriptive
header
for
each
record,
such
as
the
task
name
and
target.
Return
Code
Includes
the
programming
codes
produced
when
the
task
runs.
Standard
Error
Includes
all
error
messages
encountered
when
the
task
runs.
Standard
Output
Includes
all
information
that
results
from
the
task
execution.
7.
Select
one
of
the
following
output
destinations:
v
Click
Display
on
Tivoli
desktop
to
display
the
task
output
on
the
Tivoli
desktop.
Additional
information:
If
you
choose
Display
on
Desktop,
you
have
the
option,
inside
the
output
display
window,
of
saving
the
information
to
a
file.
v
Click
Save
to
File
to
save
the
output
to
a
file.
a.
Type
the
name
of
the
endpoint
on
which
to
save
the
output
in
the
On
Host
text
box.
Additional
information:
The
endpoint
must
be
a
Tivoli
client.
b.
Type
the
absolute
path
name
for
the
output
file
in
the
Output
File
text
box.
Additional
information:
Example:
/tmp/mytask.out
c.
Click
Set
&
Close
to
set
your
choices
and
return
to
the
Execute
Task
window.
8.
Choose
the
endpoints
on
which
you
want
to
run
the
task
by
doing
one
of
the
following:
v
Run
the
task
on
specific
endpoints
by
selecting
the
endpoints
from
the
Available
Task
Endpoints
list
and
moving
them
to
the
Selected
Task
Endpoints
list.
Chapter
6.
Monitoring
performance
and
availability
with
tasks
and
jobs
49
v
Run
the
task
on
all
endpoints
subscribed
to
a
profile
manager
by
selecting
the
profile
manager
from
the
Available
Profile
Managers
list
and
moving
it
to
the
Selected
Profile
Managers
list.
9.
Click
Execute
or
Execute
and
Dismiss.
If
the
task
requires
additional
input
parameters,
the
task
argument
window
is
displayed.
Otherwise,
the
task
runs.
Additional
information:
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
or
click
Task
Description
to
display
the
online
help
for
more
information
about
a
specific
task.
10.
Click
Set
&
Execute
to
run
the
task.
Customizing
a
task
Objective
To
customize
one
of
the
standard
tasks
in
the
task
library
so
you
can
save
defined
arguments
for
future
use.
Note:
You
can
only
customize
tasks
that
use
additional
arguments.
Background
information
A
customized
task
is
a
standard
task
with
defined
arguments
that
you
create
and
save
in
the
task
library
with
a
unique
name.
For
example,
you
can
customize
a
task
to
save
task
output
results
to
a
file
after
each
execution.
Because
you
can
customize
task
arguments,
the
Tivoli
environment
does
not
display
argument
windows
when
you
run
the
task
from
the
Tivoli
desktop.
However,
if
you
run
a
customized
task
from
the
command
line,
you
still
must
specify
the
task
arguments.
Running
a
customized
task
requires
additional
information
before
it
runs,
such
as
the
target
of
the
task.
Required
authorization
roles
msexchgserver_admin
Before
you
begin
Not
applicable
When
you
finish
You
can
run
the
task
by
following
the
procedure
in
“Running
a
task”
on
page
48.
When
you
run
a
customized
task,
the
Tivoli
desktop
does
not
display
the
task
argument
dialog.
Procedure
Use
the
following
steps
to
perform
this
task
from
the
Tivoli
desktop:
1.
Open
the
task
library
window.
2.
Double-click
a
task
icon
to
open
the
Execute
Task
window
for
that
task.
3.
Click
Execute
to
open
the
task
argument
window.
4.
Enter
the
appropriate
values
for
this
customized
task.
Additional
information:
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
or
click
Task
Description
to
display
the
online
help
for
more
information
about
a
specific
task.
5.
Click
Save
to
open
the
Save
Argument
window.
6.
Type
the
following
information
to
define
the
customized
task:
a.
Type
a
name
for
the
task
in
the
Name
text
box.
50
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Additional
information:
This
name
is
displayed
in
the
Library
Contents
field
so
you
can
view
the
customized
tasks
that
are
based
on
the
parent
task.
b.
Type
an
identifier
for
this
task.
Additional
information:
An
identifier
is
the
name
of
the
task
icon
that
will
appear
in
the
Task
Library
window.
A
customized
task
identifier
has
two
parts.
The
first
part
is
the
standard
task
name.
The
second
part
is
descriptive
information.
The
software
generates
a
unique
default
name
if
no
identifier
is
entered.
c.
Type
a
description
of
this
task
in
the
Description
text
box.
Additional
information:
This
description
is
displayed
when
you
click
Task
Description
in
the
task
argument
window
for
this
customized
task.
d.
Optional:
Select
Show
by
Identifier
to
change
the
Library
Contents
list
to
use
the
task
identifier
instead
of
the
task
name.
e.
Click
Save
&
Close
to
return
to
the
task
argument
window.7.
Click
Cancel
in
the
task
argument
window.
8.
Click
Close
in
the
Execute
Task
window
to
return
to
the
Task
Library
window.
9.
Click
View→Refresh
to
display
the
new
customized
task.
Creating
a
job
Objective
To
create
a
job,
a
resource
that
consists
of
a
task
and
its
pre-configured
parameters.
Among
other
things,
the
parameters
specify
the
targets
on
which
the
job
is
to
run.
Background
information
A
job
is
a
task
with
defined
and
saved
arguments
that
can
be
run
many
times
on
specific
managed
resources.
You
can
create
jobs
from
both
standard
and
customized
tasks
in
the
product
task
library.
Like
tasks,
you
store
jobs
in
task
libraries
so
you
can
reuse
them.
Required
authorization
roles
msexchgserver_admin
Before
you
begin
Not
applicable
When
you
finish
After
you
create
a
job,
you
can
run
it
immediately
using
the
procedure
described
in
“Running
a
job”
on
page
53.
You
can
schedule
jobs
to
run
at
certain
times
in
the
Scheduler,
as
described
in
“Scheduling
a
job”
on
page
54.
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
Line:
Use
the
wcrtjob
command
to
create
jobs
from
the
command
line.
See
the
Tivoli
Management
Framework
Reference
Manual
for
information.
Tivoli
desktop:
1.
Open
the
task
library
window.
2.
Click
Create
→
Job
to
open
the
Create
Job
window.
3.
Type
a
descriptive
job
name
in
the
Job
Name
field.
Chapter
6.
Monitoring
performance
and
availability
with
tasks
and
jobs
51
Additional
information:
The
job
name
identifies
the
icon
on
the
Tivoli
desktop.
The
name
can
include
any
alphanumeric
character,
an
underscore
(_),
dash
(–),
period
(.),
or
a
blank
space.
4.
Select
the
task
on
which
the
job
is
based
from
the
Task
Name
list.
5.
In
the
Execution
Mode
group
box,
select
one
of
the
following
check
boxes:
Parallel
Runs
the
task
simultaneously
on
all
targets.
Parallel
is
typically
the
fastest
method
of
execution.
Serial
Runs
the
task
sequentially
on
all
targets
in
alphabetical
order.
Staged
Runs
the
task
on
all
targets
in
alphabetical
order
according
to
a
schedule
you
specify.
Staged
execution
is
useful
if
you
are
running
the
task
on
a
large
number
of
endpoints.
Complete
Step
5
to
specify
the
Staging
Count
(number
of
targets
to
run
against
per
stage)
and
the
Staging
Interval
(number
of
seconds
between
each
set).
6.
In
the
Execution
Parameters
group
box,
type
the
timeout
value
(in
seconds)
for
the
task
in
the
Timeout
text
box.
Additional
information:
The
timeout
value
specifies
the
number
of
seconds
the
product
waits
for
the
task
or
job
to
complete
before
it
issues
an
error.
The
default
is
60
seconds.
If
the
task
takes
longer
to
complete
than
the
specified
Timeout
and
is
running
in
Serial
or
Staged
mode,
the
product
moves
on
to
other
endpoints
after
this
time
expires.
The
task
continues
to
run
on
the
endpoint,
even
though
the
product
stopped
waiting
for
it
to
end.
7.
Optional:
If
you
selected
Staged
in
Step
5,
specify
the
number
of
endpoints
to
include
in
each
staged
set
in
the
Staging
Count
text
box
and
the
number
of
seconds
between
the
startup
time
of
each
set
in
the
Staging
Interval
text
box.
8.
Select
one
or
more
of
the
following
output
format
options:
Header
Includes
a
descriptive
header
for
each
record.
Return
Code
Includes
the
programming
codes
produced
when
the
job
runs.
Standard
Error
Includes
all
error
messages
encountered
when
the
job
runs.
Standard
Output
Includes
all
information
that
results
from
the
job
execution.
9.
Select
one
of
the
following
output
destinations:
v
Click
Display
on
Tivoli
desktop
to
display
the
job
output
on
the
Tivoli
desktop.
Go
to
Step
11.
Additional
information:
If
you
choose
Display
to
Desktop,
you
have
the
option,
inside
the
output
display
window,
to
save
the
information
to
a
file.
v
Click
Save
to
File
to
save
the
output
to
a
file
and
open
the
Destination
for
Task
Output
window.
Go
to
Step
10.10.
Use
the
following
steps
in
the
Destination
for
Task
Output
window
to
save
the
job
output
to
a
file:
a.
Type
a
Tivoli
client
endpoint
name
in
the
On
Host
field.
b.
Type
the
absolute
path
name
for
the
output
file
in
the
Output
File
field.
For
example,
type
/tmp/myjob.out.
c.
Click
Set
&
Close
to
set
your
choices
and
return
to
the
Create
Job
window.
52
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
11.
Choose
the
endpoints
on
which
you
want
to
run
the
job
by
doing
one
of
the
following:
v
Run
the
task
on
specific
endpoints
by
selecting
the
endpoints
from
the
Available
Task
Endpoints
list
and
moving
them
to
the
Selected
Task
Endpoints
list.
v
Run
the
task
on
all
endpoints
subscribed
to
a
profile
manager
by
selecting
the
profile
manager
from
the
Available
Profile
Managers
list
and
moving
it
to
the
Selected
Profile
Managers
list.:12.
Click
Create
&
Close
to
create
the
job
and
return
to
the
Task
Library
window.
Additional
information:
The
new
job
icon
appears
in
the
Task
Library
window.
Running
a
job
Objective
To
run
a
job
on
specific
endpoints
immediately
so
you
can
perform
a
management
operation.
Background
information
If
you
created
a
job
from
a
standard
task,
the
Tivoli
desktop
displays
the
task
argument
window
so
that
you
can
fill
in
any
required
information.
Jobs
created
from
customized
tasks
run
without
further
input
because
all
required
information
is
specified.
(See
“Customizing
a
task”
on
page
50
for
information
about
how
to
create
a
customized
task.)
Required
authorization
roles
msexchgserver_admin
Before
you
begin
Before
you
can
run
a
job,
you
must
create
it,
as
described
in
“Creating
a
job”
on
page
51.
When
you
finish
After
you
create
a
job,
you
can
set
it
up
to
run
on
a
regular
schedule
as
described
in
“Scheduling
a
job”
on
page
54.
Procedure
You
can
perform
this
procedure
from
the
command
line
or
the
Tivoli
desktop.
Command
Line:
Use
the
wrunjob
command
to
run
jobs
from
the
command
line.
See
the
Tivoli
Framework
Reference
Manual
for
information
about
this
command.
Tivoli
desktop:
1.
Open
the
task
library
window.
2.
Do
one
of
the
following:
v
Double-click
the
job
icon
created
from
a
customized
task
to
begin
executing
the
job.
v
Double-click
the
job
icon
created
from
a
standard
task.3.
Type
the
values
in
the
task
window.
Additional
information:
For
information
about
specific
fields,
see
the
task
description
in
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
or
click
Task
Description
to
display
the
online
help.
Chapter
6.
Monitoring
performance
and
availability
with
tasks
and
jobs
53
The
job
runs
and
displays
the
output
on
the
Tivoli
desktop
or
sends
it
to
a
file.
Scheduling
a
job
Objective
To
schedule
jobs
to
occur
regularly
so
you
can
routinely
perform
management
operations.
Background
information
The
product
uses
Scheduler,
a
service
that
enables
you
to
run
jobs
unattended.
You
can
schedule
a
job
to
run
one
time
or
multiple
times.
Scheduler
notifies
you
when
a
job
is
complete.
Required
authorization
roles
msexchgserver_admin
Before
you
begin
To
schedule
a
job,
the
job
must
exist
in
the
task
library.
You
create
a
job
by
following
the
procedure
described
in
“Creating
a
job”
on
page
51.
When
you
finish
Not
applicable
Procedure
You
can
perform
this
procedure
from
either
the
command
line
or
the
Tivoli
desktop.
Command
Line:
Use
the
wschedjob
command
to
schedule
a
job
in
the
Task
Library
from
the
command
line.
From
the
command
line,
you
can
only
schedule
jobs
that
already
exist
in
the
task
library.
See
the
Tivoli
Framework
Reference
Manual.
for
information.
Tivoli
desktop:
1.
Open
the
task
library
window.
2.
Drag
the
job
icon
that
you
want
to
schedule
onto
the
Scheduler
icon
located
in
the
TME®
Desktop
for
Administrator
root_admin_name
window
on
the
Tivoli
desktop.
3.
Optional:
Do
the
following
if
a
task
argument
window
opens:
a.
Type
the
appropriate
information
for
each
field
in
the
argument
window.
Additional
information:
Refer
to
the
task
description
in
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
or
click
Task
Description
to
display
the
online
help
for
this
task.
b.
Click
Set
&
Execute
to
set
the
task
arguments
and
open
the
Add
Scheduled
Job
window.
4.
Type
a
label
for
the
job
icon
in
the
Job
Label
text
box
of
the
Add
Scheduled
Job
window.
Additional
information:
The
label
identifies
the
icon
on
the
Tivoli
desktop.
The
job
label
can
include
alphanumeric
character,
underscores
(_),
dashes
(–),
periods
(.),
and
blanks.
If
you
do
not
specify
a
label,
the
job
name
is
used.
5.
Do
one
of
the
following:
v
Select
Disable
the
Job
to
stop
a
scheduled
job
from
running.
v
Clear
Disable
the
Job
to
continue
running
a
scheduled
job.
54
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Additional
information:
See
the
Tivoli
Management
Framework
User’s
Guide
for
more
information
about
job
disabling.
6.
Optional:
Type
a
job
description
in
the
Description
field.
7.
Set
the
date
and
time
to
begin
scheduling
in
the
Schedule
Job
For
group
box:
a.
Type
a
date
in
the
Month,
Day,
and
Year
fields.
b.
Enter
the
time
using
the
Hour
and
Minute
drop-down
lists
and
the
AM
and
PM
radio
buttons.
8.
Optional:
Set
the
job
to
repeat
by
doing
the
following
in
the
Repeat
the
Job
group
box:
a.
Specify
the
number
of
times
the
job
should
repeat
by
choosing
one
of
the
following:
v
Set
the
job
to
repeat
indefinitely
by
selecting
Repeat
the
job
indefinitely.
v
Set
the
job
to
repeat
a
set
number
of
times
by
selecting
Repeat
the
job
and
typing
the
number
of
times
you
want
the
job
to
run.b.
Set
the
interval
between
start
times
for
the
job
in
the
The
job
should
start
every
field.
9.
Select
any
of
the
following
check
boxes
in
the
When
Job
Completes
group
box
to
send
job
completion
notification:
v
Send
a
notice
to
a
specific
group:
a.
Select
Post
Tivoli
Notice.
b.
Click
Available
Groups
to
open
the
Available
Groups
window.
c.
Select
a
group
from
the
list
of
notice
groups.
d.
Click
Set
to
set
your
group
and
return
to
the
Add
Scheduled
Job
window.
Additional
information:
You
can
read
notices
from
the
Tivoli
desktop
by
clicking
Notices.
v
Send
a
notice
to
your
Tivoli
desktop:
a.
Select
Post
Status
Dialog
on
Tivoli
desktop.
b.
Type
the
message
you
want
displayed
in
the
text
box
next
to
the
check
box.v
Send
an
to
a
specified
user:
a.
Select
the
Send
to.
b.
Type
the
complete
address
in
the
text
box
next
to
the
check
box.v
Log
the
job
completion
status
to
a
file:
a.
Select
Log
to
File.
b.
Enter
the
file
destination
by
doing
one
of
the
following:
–
Type
the
file
destination
in
the
Host
and
File
text
boxes.
The
host
must
be
a
Tivoli
client
endpoint
and
the
file
must
be
a
fully
qualified
path
name.
For
example:
/tmp/mytask.out
–OR–
–
Browse
for
the
file
destination
by
doing
the
following:
1)
Click
File
Browser
to
open
the
File
Browser
window.
2)
Double-click
on
a
host
name
to
display
the
directories
and
files
for
that
host.
3)
Select
a
directory
and
file
from
the
Directories
and
Files
lists.
4)
Click
Set
File
&
Close
to
return
to
the
Add
Scheduled
Job
window.
Chapter
6.
Monitoring
performance
and
availability
with
tasks
and
jobs
55
10.
Optional:
Set
retry,
cancel,
or
restriction
options
by
doing
the
following:
a.
Click
Set
Retry/Cancel/Restriction
Options
to
open
the
Set
Retry/Cancel
Restrictions
Options
window.
b.
Choose
one
of
the
following
cancel
job
options:
v
Clear
Cancel
job
to
have
the
Scheduler
continue
trying
the
job
indefinitely.
—OR—
v
Set
the
Scheduler
to
cancel
a
job
in
a
specified
time
frame
by
doing
the
following:
1)
Select
Cancel
job.
2)
Type
the
time
frame
for
the
Scheduler
to
wait
before
canceling
a
job
that
has
not
started.c.
Click
one
of
the
following
retry
options:
v
Click
Retry
the
job
until
success
to
retry
the
job
until
it
runs
successfully.
—OR—
v
Specify
the
number
of
times
a
job
attempts
to
run
by
doing
the
following:
1)
Select
Retry
the
job.
2)
Type
the
number
of
attempts
to
start
the
job
in
the
text
box.
3)
Type
the
amount
of
time
the
Scheduler
waits
before
retrying
in
the
The
job
should
retry
every
field.d.
Select
any
of
the
following
check
boxes
in
the
Restrictions
group
box
to
specify
the
job
run
times:
During
the
day
Set
the
beginning
and
ending
hour
of
the
day
for
the
job
to
run.
At
night
Set
the
beginning
and
ending
hour
of
the
night
for
the
job
to
run.
During
the
week
Set
the
beginning
and
ending
day
of
the
week
for
the
job
to
run.
On
weekends
Set
the
beginning
and
ending
day
of
the
weekend
for
the
job
to
run.e.
Click
Set
to
set
the
options
and
return
to
the
Add
Scheduled
Job
window.11.
Click
Schedule
Job
&
Close
to
schedule
the
job
and
return
to
the
Tivoli
desktop.
56
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
7.
Tracking
the
performance
of
Microsoft
Exchange
servers
Reports
enable
you
to
analyze
the
health
and
performance
of
your
Microsoft
Exchange
servers
over
a
period
of
time.
You
can
also
use
reports
to
predict
resource
usage
and
diagnose
potential
problems
before
they
occur.
While
any
status
task
creates
a
report
about
the
current
status
of
your
resources,
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
also
provides
detailed
reports
about
the
following
topics:
v
Mailbox
and
folder
space
usage
v
Mailbox
and
folder
inactivity
v
Detailed
performance
and
availability
information
through
IBM
Tivoli
Data
Warehouse
Creating
a
report
about
space
usage
Objective
To
determine
which
mailboxes
are
consuming
the
most
storage
space
so
that
you
can
take
actions
to
remedy
the
situation,
such
as
setting
storage
and
message
limits.
Background
information
The
LimitReport
task
lists
mailboxes
and
public
folders
that
exceed
message
count
or
storage
limits,
including
those
mailboxes
without
a
specified
storage
limit.
The
following
information
is
returned:
v
Alias
name
v
Current
message
count
v
Current
storage
size
v
Maximum
storage
size
Required
authorization
role
msexchgserver_admin
Before
you
begin
Not
applicable
When
you
finish
If
you
notice
an
unusual
growth
spurt
in
your
components,
you
might
need
to
check
the
overall
performance
of
the
Microsoft
Exchange
Server.
If
you
see
an
unusual
growth
in
message
count,
you
might
need
to
check
the
system
for
an
virus,
as
this
can
be
indicated
by
a
high
number
of
messages.
You
can
also
use
the
Microsoft
Exchange
Server
System
Manager
to
set
or
change
limits
for
mailboxes
and
folders.
See
the
Exchange
Server
Administration
Guide
for
more
information.
Procedure
Use
the
following
steps
to
create
a
limit
report:
1.
Double-click
Monitoring
for
Microsoft
Exchange
Server
in
the
Tivoli
desktop.
©
Copyright
IBM
Corp.
2004
57
2.
Double-click
ITMMicrosoftExchangeServerTasks.
3.
Double-click
LimitReport.
4.
Select
Display
on
Desktop
to
display
the
output
of
the
task
on
the
desktop.
5.
Click
Execute
or
Execute
and
Dismiss
to
display
the
LimitReport
window.
6.
Complete
the
following
fields:
Report
on
Mailboxes
Specify
whether
to
gather
information
for
mailboxes
on
the
server.
Report
on
Public
Folders
Specify
whether
to
gather
information
for
public
folders
on
the
server.
Message
Count
Threshold
Specify
the
maximum
number
of
messages
for
all
mailboxes
or
public
folders.
All
mailboxes
or
public
folders
that
exceed
this
number
of
messages
are
included
in
the
report.
Storage
Percentage
Threshold
Specify
a
percentage
of
the
defined
storage
size
for
mailboxes
or
public
folders.
All
mailboxes
or
public
folders
that
exceed
this
percentage
are
included
in
the
report.
Storage
Size
Threshold
Specify
a
numerical
maximum
storage
size
(in
kilobytes)
for
mailboxes
or
public
folders
with
no
storage
limits.
All
mailboxes
or
public
folders
without
size
limits
that
exceed
this
size
are
included
in
the
report.7.
Click
Set
&
Execute.
Creating
a
report
about
inactivity
Objective
To
determine
which
mailboxes
or
public
folders
are
not
currently
being
used.
Background
information
The
InactiveReport
task
identifies
inactive
public
folders
and
mailboxes.
You
can
regain
disk
space
by
removing
these
inactive
folders
and
mailboxes.
This
task
checks
the
last
logon
date
for
folders
and
mailboxes.
That
date
is
compared
to
the
inactive
threshold;
any
object
that
exceeds
the
threshold
is
included
in
the
report.
Required
authorization
role
msexchgserver_admin
Before
you
begin
Not
applicable
When
you
finish
Delete
any
unused
mailboxes
or
public
folders.
See
the
Exchange
Server
Administration
Guide
for
more
information.
Procedure
Use
the
following
steps
to
create
an
inactivity
report:
1.
Initiate
the
logging
of
activity
data
for
mailboxes
and
public
folders
by
running
the
InactiveReportStartCollection
task:
a.
Double-click
Monitoring
for
Microsoft
Exchange
Server
in
the
Tivoli
desktop.
58
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
b.
Double-click
ITMMicrosoftExchangeServerTasks.
c.
Double-click
InactiveReportStartCollection.
d.
Select
Display
on
Desktop
to
display
the
output
of
the
task
on
the
desktop.
e.
Click
Execute
or
Execute
and
Dismiss.
f.
Complete
the
following
fields
and
click
Set
&
Execute.
Logging
Interval
Specify
the
number
of
minutes
between
logging
sessions.
The
default
is
240
minutes
(4
hours).
Ignored
Profiles
Specify
any
logon
profiles
to
ignore.
For
example,
you
can
ignore
any
anti-virus
logons
by
entering
the
profile
name
of
anti-virus
software.
Separate
multiple
profiles
with
a
semi-colon
(;).
Enter
″@″
to
monitor
all
profiles.
Collection
Start
Mode
Specify
the
mode
for
starting
the
collection.
You
have
two
choices:
Reinitialize
Erases
any
existing
logged
information
and
begins
logging
from
that
point
on.
Update
Retains
existing
logging
information
and
uses
the
new
Logging
Interval
and
Ignored
Profiles
values.2.
Create
the
report
by
running
the
InactiveReport
task:
a.
In
the
ITMMicrosoftExchangeServerTasks
task
library,
double-click
InactiveReport.
b.
Select
Display
on
Desktop
to
display
the
output
of
the
task
on
the
desktop.
c.
Click
Execute
or
Execute
and
Dismiss.
d.
In
the
Inactive
Threshold
field,
specify
the
maximum
number
of
days
that
a
mailbox
or
folder
can
go
without
being
accessed
before
being
considered
″inactive.″
The
default
value
is
30.
e.
Click
Set
&
Execute.3.
After
you
create
the
report
and
no
longer
want
to
log
activity
data,
run
the
InactiveReportStopCollection
data.
a.
In
the
ITMMicrosoftExchangeServerTasks
task
library,
double-click
InactiveReportStopCollection.
b.
Select
Display
on
Desktop
to
display
the
output
of
the
task
on
the
desktop.
c.
Click
Execute
or
Execute
and
Dismiss.
IBM
Tivoli
Data
Warehouse
reports
IBM
Tivoli
Data
Warehouse
enables
you
to
access
application
reports
(from
Crystal
Reports)
from
various
Tivoli
and
customer
applications.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
reports
provide
information
about
the
availability
and
performance
of
Microsoft
Exchange
Server
over
a
period
of
time.
Use
this
detailed
information
to
analyze
how
your
Microsoft
Exchange
server
is
performing
in
regard
to
space
usage,
message
flow,
and
availability.
Chapter
7.
Tracking
the
performance
of
Microsoft
Exchange
servers
59
See
the
IBM
Tivoli
Data
Warehouse
documentation
for
information
about
generating
reports.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
provides
the
following
reports.
Each
of
these
reports
contains
three
sub-reports,
as
described
below.
Availability
Report
Reports
on
changes
in
server
availability.
v
Exchange
Server
Availability
Summary:
Provides
information
about
the
availability
of
the
server
within
a
time
period.
v
Exchange
Server
Maximum
Availability:
Provides
the
maximum
percentage
of
time
that
the
Microsoft
Exchange
server
was
available
during
the
time
period.
v
Exchange
Server
Availability
Health
Check:
Provides
details
about
availability
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Server
Queue
Report
Reports
on
changes
in
server
queue
activity.
v
Exchange
Server
Queue
Summary:
Provides
a
summary
of
activity
in
message
queues
within
a
time
period.
v
Exchange
Server
Queue
Extreme
Case:
Provides
information
about
the
maximum
number
of
messages
in
each
queue.
v
Exchange
Server
Queue
Health
Check:
Provides
details
about
queue
activity
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Storage
Group
Report
Reports
changes
in
the
size
of
server
databases.
v
Database
Space
Summary:
Provides
the
maximum
sizes
of
database
files.
Use
this
report
to
determine
the
change
in
database
sizes
related
to
an
increased
volume
of
activity.
v
Database
Space
Extreme
Case:
Provides
the
maximum
amount
of
space
used
by
databases.
v
Database
Space
Health
Check:
Provides
details
about
the
size
of
databases
on
a
server
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Use
this
report
to
determine
the
change
in
database
sizes
related
to
an
increased
volume
of
activity.
Server
Log
Space
Report
Reports
on
changes
in
Microsoft
Exchange
Server
log
files
sizes.
v
Log
Space
Summary:
Provides
the
maximum
size
of
the
Microsoft
Exchange
Server
log
files.
v
Log
Space
Extreme
Case:
Provides
the
maximum
amount
of
log
space
used.
v
Log
Space
Health
Check:
Provides
details
about
the
size
of
log
space
on
a
server
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Use
this
report
to
determine
the
change
in
log
space
used
related
to
an
increased
volume
of
activity.
Message
Volume
Report
Reports
on
changes
in
messages
volume
and
size.
v
Message
Volume
Summary:
Provides
the
following
information
for
a
time
period:
60
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
–
Number
of
messages
sent
and
received
for
each
Microsoft
Exchange
server
in
your
organization
–
Average
message
size
–
Number
of
messages
sent
and
received
from
SMTPv
Message
Volume
Extreme
Case:
Provides
the
maximum
values
for
the
information
in
the
Message
Volume
Summary
report.
v
Message
Volume
Health
Check:
Provides
details
about
message
volumes
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Information
Store
Public
Folder
Report
Reports
changes
in
the
information
store
public
folder
sizes.
v
Information
Store
Public
Folder
Summary:
Provides
the
size
of
public
folders.
v
Information
Store
Public
Folder
Extreme
Case:
Provides
the
maximum
size
of
the
public
folders
during
a
time
period.
v
Information
Store
Public
Folder
Health
Check:
Provides
details
about
the
amount
of
space
used
by
public
folders
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Information
Store
Private
Folder
Report
Reports
changes
in
the
information
store
private
folder
sizes.
v
Information
Store
Private
Folder
Summary:
Provides
the
size
of
private
folders.
v
Information
Store
Private
Folder
Extreme
Case:
Provides
the
maximum
size
of
the
private
folders
during
a
time
period.
v
Information
Store
Private
Folder
Health
Check:
Provides
details
about
the
amount
of
space
used
by
private
folders
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Active
Users
Report
Reports
changes
in
the
number
of
Active
Users
per
server.
v
Active
Users
Summary:
Provides
the
number
of
active
users
for
each
Microsoft
Exchange
server
during
a
time
period.
v
Active
Users
Extreme
Case:
Provides
the
maximum
number
of
active
users
during
a
time
period.
v
Active
Users
Health
Check:
Provides
details
about
the
number
of
active
users
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Round
Trip
Response
Time
Report
Reports
how
message
round
trip
response
times
trend
over
time.
v
Round
Trip
Response
Time
Summary:
Provides
the
response
time
for
an
message
during
a
time
period.
v
Round
Trip
Response
Time
Extreme
Case:
Provides
the
maximum
amount
of
time
for
a
response
for
an
message
during
the
time
period.
v
Round
Trip
Response
Time
Health
Check:
Provides
details
about
the
response
time
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
Server
Mailbox
Store
Queue
Report
Reports
changes
in
the
SMTP
and
MTA
queues.
v
Microsoft
Exchange
Server
Queue
Summary:
Provides
queue
activity
within
a
time
period.
Chapter
7.
Tracking
the
performance
of
Microsoft
Exchange
servers
61
v
Microsoft
Exchange
Server
Queue
Extreme
Case:
Provides
the
maximum
queue
activity.
v
Microsoft
Exchange
Server
Queue
Health
Check:
Provides
details
about
Microsoft
Exchange
Server
queue
activity
at
a
particular
date
and
time
or
during
a
range
of
dates
and
times.
62
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
8.
Working
with
Tivoli
objects
This
chapter
provides
information
about
working
with
the
Tivoli
application
proxy
objects
that
represent
your
Microsoft
Exchange
servers.
The
following
table
lists
the
actions
you
can
perform
through
the
objects
and
where
to
find
more
information.
Goal
Where
to
find
information
View
the
properties
for
an
endpoint.
“Viewing
Microsoft
Exchange
server
object
properties”
Edit
the
properties
for
an
endpoint.
“Editing
Microsoft
Exchange
server
properties”
on
page
65
Start
Microsoft
Exchange
services.
“Starting
Microsoft
Exchange
services”
on
page
66
Stop
Microsoft
Exchange
services.
“Stopping
Microsoft
Exchange
services”
on
page
67
Viewing
Microsoft
Exchange
server
object
properties
Objective
To
view
information
about
the
application
proxy
object
associated
with
a
Microsoft
Exchange
server.
Background
information
An
application
proxy
object
(also
called
a
″Tivoli
object″)
represents
the
Microsoft
Exchange
server
that
is
monitored
by
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server.
You
can
view
the
properties
of
this
object
to
determine
the
specific
Microsoft
Exchange
server
that
is
being
monitored.
Required
authorization
role
msexchgserver_user
Before
you
begin
Create
an
application
proxy
object,
as
described
in
“Creating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects”
on
page
16.
When
you
finish
Edit
any
properties
of
the
application
proxy
object
that
you
want
to
change,
as
described
in
“Editing
Microsoft
Exchange
server
properties”
on
page
65.
Procedure
Use
the
following
steps
to
view
the
properties
of
an
application
proxy
object:
1.
Right-click
the
Tivoli
object
that
represents
the
Microsoft
Exchange
server.
2.
Click
View
Properties.
The
following
window
is
displayed:
©
Copyright
IBM
Corp.
2004
63
The
View
Properties
window
lists
the
following
information:
Name
The
name
of
the
Microsoft
Exchange
server
with
which
the
object
is
associated
Home
The
home
directory
for
Microsoft
Exchange
Server
Username
The
name
of
the
user
that
has
access
to
the
Microsoft
Exchange
server
Password
The
password
for
the
user
UserDomain
The
domain
to
which
the
user
belongs
UserProfile
The
Microsoft
Exchange
Server
profile
for
the
user
Version
The
version
of
Microsoft
Exchange
Server
installed
on
the
computer
Endpoint
The
name
of
the
Tivoli
object
Proxy
Managed
Node
The
managed
node
on
which
the
application
proxy
object
resides
Figure
1.
Application
proxy
object
properties
64
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Editing
Microsoft
Exchange
server
properties
Objective
To
change
the
properties
for
an
application
proxy
object
that
represents
a
Microsoft
Exchange
server.
Background
information
Any
time
you
make
a
change
to
a
monitored
Microsoft
Exchange
server,
you
must
change
the
same
information
for
the
application
proxy
object.
This
ensures
that
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
can
communicate
with
Microsoft
Exchange
Server.
Note:
You
can
also
use
the
MSExchangeAuthentication
task
to
change
information
for
an
application
proxy
object.
Required
authorization
role
msexchgserver_admin
Before
you
begin
Create
an
application
proxy
object,
as
described
in
“Creating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects”
on
page
16.
View
the
current
properties
for
the
application
proxy
object,
as
described
in
“Viewing
Microsoft
Exchange
server
object
properties”
on
page
63.
When
you
finish
Not
applicable
Procedure
Use
the
following
steps
to
edit
the
properties
of
an
application
proxy
object:
1.
Right-click
the
Tivoli
object
that
represents
the
Microsoft
Exchange
server.
2.
Click
Edit
Properties.
The
following
window
is
displayed:
Chapter
8.
Working
with
Tivoli
objects
65
You
can
change
any
of
the
following
properties:
Home
The
home
directory
for
Microsoft
Exchange
Server
Username
The
name
of
the
user
that
has
access
to
the
Microsoft
Exchange
server
UserDomain
The
domain
to
which
the
user
belongs
UserProfile
The
Microsoft
Exchange
Server
profile
for
the
user
Password
The
password
for
the
user
Version
The
version
of
Microsoft
Exchange
Server
installed
on
the
computer
Starting
Microsoft
Exchange
services
Objective
To
start
(or
continue)
the
services
that
comprise
Microsoft
Exchange
Server.
Background
information
You
can
start
stopped
services
and
continue
paused
services.
Figure
2.
Application
proxy
object
properties
—
edit
view
66
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Selecting
a
service
to
start
might
start
more
than
one
service
because
of
dependencies
between
services.
For
example,
starting
the
MSExchangeIS
service
also
starts
the
MSExchangeSA
service.
Note:
You
cannot
start
paused
services;
you
must
continue
them.
Attempting
to
start
a
paused
service
does
not
change
the
status
of
that
service.
You
can
only
start
stopped
services.
Required
authorization
role
msexchgserver_admin
Before
you
begin
You
can
verify
the
status
of
installed
services
with
the
DisplayExchangeServerStatus
task.
When
you
finish
Not
applicable
Procedure
You
can
start
services
either
with
a
task
or
through
the
Tivoli
desktop.
Task:
Use
the
StartExchangeServices
task
to
start
or
continue
services
on
a
Microsoft
Exchange
server.
See
Chapter
6,
“Monitoring
performance
and
availability
with
tasks
and
jobs,”
on
page
45
for
information
about
running
tasks.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
additional
information
about
this
task.
Tivoli
desktop:
Use
the
following
steps
to
start
a
service
from
the
Tivoli
desktop:
1.
Right-click
the
application
proxy
object
that
represents
the
Microsoft
Exchange
server
for
which
you
want
to
start
services.
2.
Click
Start.
Stopping
Microsoft
Exchange
services
Objective
To
stop
(or
pause)
the
services
that
comprise
Microsoft
Exchange
Server.
Background
information
You
can
stop
running
services.
You
can
also
pause
some
services.
Selecting
a
service
to
stop
might
stop
more
than
one
service
because
of
dependencies
between
services.
For
example,
stopping
the
MSExchangeSA
service
also
stops
the
MSExchangeIS
service.
Note:
You
cannot
stop
paused
services.
You
can
only
stop
running
services.
If
you
need
to
stop
a
paused
service,
use
the
StartExchangeServices
task
to
continue
the
service,
then
run
this
task
to
stop
the
service.
Required
authorization
role
msexchgserver_admin
Before
you
begin
You
can
verify
the
status
of
installed
services
with
the
DisplayExchangeServerStatus
task.
Chapter
8.
Working
with
Tivoli
objects
67
When
you
finish
Not
applicable
Procedure
You
can
stop
services
either
with
a
task
or
through
the
Tivoli
desktop.
Task:
Use
the
StopExchangeServices
task
to
stop
or
pause
services
on
a
Microsoft
Exchange
server.
See
Chapter
6,
“Monitoring
performance
and
availability
with
tasks
and
jobs,”
on
page
45
for
information
about
running
tasks.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
additional
information
about
this
task.
Tivoli
desktop:
Use
the
following
steps
to
stop
all
services
from
the
Tivoli
desktop:
1.
Right-click
the
application
proxy
object
that
represents
the
Microsoft
Exchange
server
for
which
you
want
to
start
services.
2.
Click
Stop.
All
services
on
the
server
are
stopped.
68
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Chapter
9.
Using
Microsoft
Exchange
Server
utilities
to
address
problems
Problems
can
occur
with
Microsoft
Exchange
servers
because
of
data
integrity
problems
or
logical
errors
in
public
and
private
databases
(information
stores)
or
queues.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
provides
the
ability
to
run
Microsoft
utilities
that
address
these
problems.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
provides
the
following
tasks
to
run
Microsoft
utilities:
Table
5.
Tasks
that
run
Microsoft
utilities
Task
name
Description
RunESEUTILChecksum
Runs
the
ESEUTIL
Checksum
utility
on
the
target
server.
This
utility
confirms
the
data
integrity
of
pages
in
private
and
public
databases
(for
Microsoft
Exchange
Server
2000)
and
also
for
information
stores
(in
Microsoft
Exchange
Server
2003).
RunESEUTILDefrag
Runs
the
ESEUTIL
defragmentation
utility
on
the
target
server.
This
utility
can
defragment
the
information
store
and
check
the
private,
public,
or
directory
databases.
Run
this
task
to
defragment
the
information
store
after
you
delete
data
from
mailboxes
or
folders
or
move
mailboxes
to
another
information
store
or
server.
RunESEUTILInteg
Runs
the
ESEUTIL
Integrity
utility
on
the
target
server.
This
utility
verifies
the
physical
(not
logical)
integrity
of
public
and
private
information
store
databases.
Use
this
task
to
verify
the
data
in
your
database
after
a
recovery.
Note:
This
utility
is
intended
to
be
used
for
disaster
recovery
situations,
not
for
routine
maintenance.
RunISINTEG
Runs
the
ISINTEG
utility
on
the
target
server.
This
utility
finds
and
eliminates
common
logical
errors
in
the
Microsoft
Exchange
Server
public
and
private
information
store
databases.
The
ISINTEG
utility
can
also
repair
problems
that
are
detected.
Run
this
task
after
you
recover
a
database
with
the
ESEUTIL
utility.
Note:
This
utility
is
intended
to
be
used
for
disaster
recovery
situations,
not
for
routine
maintenance.
©
Copyright
IBM
Corp.
2004
69
Table
5.
Tasks
that
run
Microsoft
utilities
(continued)
Task
name
Description
RunMTACHECK
Runs
the
MTACHECK
utility
on
the
target
server.
This
utility
scans
the
message
transfer
agent
(MTA)
for
any
damaged
objects
that
might
interfere
with
queue
processing.
Run
this
task
when
the
MTA
does
not
start
and
you
suspect
that
the
MTA
database
is
corrupted.
Another
indication
that
there
is
a
problem
with
the
MTA
is
when
the
length
of
the
MTA
work
queue
grows
and
message
flow
stops.
Note:
These
tasks
are
intended
to
run
against
one
endpoint
at
a
time
only
as
needed.
They
are
not
intended
for
routine
maintenance.
See
Chapter
6,
“Monitoring
performance
and
availability
with
tasks
and
jobs,”
on
page
45
for
information
about
how
to
run
these
tasks.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
detailed
descriptions
of
these
tasks.
70
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Appendix
A.
Integrating
with
IBM
Tivoli
Business
Systems
Manager
This
chapter
provides
information
on
using
IBM
Tivoli
Business
Systems
Manager
to
manage
Microsoft
Exchange
servers
and
events.
Integrating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
into
IBM
Tivoli
Business
Systems
Manager
includes
the
following
steps:
Table
6.
Integrating
with
IBM
Tivoli
Business
System
Manager
Goal
Refer
to
Install
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program
on
the
IBM
Tivoli
Business
Systems
Manager
server
“Integrating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
with
IBM
Tivoli
Business
Systems
Manager”
on
page
72
Configure
your
IBM
Tivoli
Enterprise
Console
event
server
to
forward
events
to
IBM
Tivoli
Business
Systems
Manager
“Configuring
the
IBM
Tivoli
Enterprise
Console
event
server
to
work
with
IBM
Tivoli
Business
Systems
Manager”
on
page
73
Define
the
specific
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects
for
IBM
Tivoli
Business
Systems
Manager
using
a
discovery
task.
“Discovering
resources
for
IBM
Tivoli
Business
Systems
Manager”
on
page
74
This
chapter
also
provides
a
list
of
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
that
you
can
run
from
IBM
Tivoli
Business
Systems
Manager
and
information
about
uninstalling
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
from
IBM
Tivoli
Business
Systems
Manager.
IBM
Tivoli
Business
Systems
Manager
overview
IBM
Tivoli
Business
Systems
Manager
is
a
business
systems
management
tool
that
enables
you
to
graphically
monitor
and
control
interconnected
business
components
and
operating
system
resources.
A
business
component
and
its
resources
are
referred
to
as
a
Line
of
Business
(LOB).
Note:
In
IBM
Tivoli
Business
System
Manager,
Version
2.1,
lines
of
business
are
referred
to
as
″business
systems.″
IBM
Tivoli
Business
Systems
Manager
consists
of
the
following
components:
IBM
Tivoli
Business
Systems
Manager
management
server
Processes
all
the
availability
data
that
is
collected
from
various
sources.
Availability
data
is
inserted
in
the
IBM
Tivoli
Business
Systems
Manager
database,
where
intelligent
agents
provide
alerts
on
monitored
objects
and
then
broadcast
those
alerts
to
IBM
Tivoli
Business
Systems
Manager
workstations.
The
management
server
processes
all
user
requests
that
originate
from
the
workstations
and
includes
a
database
server
that
is
built
around
a
Microsoft
SQL
Server
database.
©
Copyright
IBM
Corp.
2004
71
IBM
Tivoli
Business
Systems
Manager
console
Displays
objects
in
customized
views,
called
Line
of
Business
Views.
Objects
are
presented
in
a
hierarchical
TreeView
so
that
users
can
see
the
relationship
between
objects.
Alerts
are
overlaid
on
the
objects
when
the
availability
of
the
object
is
threatened.
IBM
Tivoli
Business
Systems
Manager
Event
Enablement
Enables
the
event
server
to
forward
events
to
IBM
Tivoli
Business
Systems
Manager
and
defines
event
classes
and
rules
for
handling
events
related
to
IBM
Tivoli
Business
Systems
Manager.
Event
Enablement
is
installed
on
the
IBM
Tivoli
Enterprise
Console
event
server.
See
the
IBM
Tivoli
Business
System
Manager
documentation
for
more
information.
Prerequisites
Before
you
integrate
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
into
IBM
Tivoli
Business
Systems
Manager,
perform
the
following
prerequisite
steps:
v
Install
IBM
Tivoli
Business
Systems
Manager,
as
described
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
You
must
install
IBM
Tivoli
Business
Systems
Manager
Version
2.1.1,
Fix
Pack
9.
IBM
Tivoli
Business
Systems
Manager
Version
1.5
with
patch
35
or
higher
is
also
supported.
v
Install
and
configure
the
Tivoli
Event
Enablement
Version
2.1.1,
Fix
Pack
4,
on
all
IBM
Tivoli
Enterprise
Console
event
servers
that
receive
events
that
you
want
to
forward
to
IBM
Tivoli
Business
Systems
Manager.
See
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
v
Configure
IBM
Tivoli
Business
Systems
Manager
to
communicate
with
each
Tivoli
Event
Enablement
installed
in
the
previous
step.
See
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
Integrating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
with
IBM
Tivoli
Business
Systems
Manager
Objective
To
integrate
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
with
IBM
Tivoli
Business
Systems
Manager
so
you
can
receive
Microsoft
Exchange
Server
events
on
the
IBM
Tivoli
Business
Systems
Manager.
Background
information
To
enable
IBM
Tivoli
Business
Systems
Manager
to
manage
Microsoft
Exchange
Server
events,
you
must
install
an
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program
on
the
IBM
Tivoli
Business
Systems
Manager
server.
This
integration
program
performs
the
following
steps:
v
Defines
the
Microsoft
Exchange
servers
in
IBM
Tivoli
Business
Systems
Manager
v
Adds
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
to
the
object
types
in
IBM
Tivoli
Business
Systems
Manager
v
Defines
a
line
of
business
for
Microsoft
Exchange
servers
Required
authorization
role
Administrator
authority
on
the
IBM
Tivoli
Business
Systems
Manager
server
72
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Before
you
begin
Ensure
that
your
IBM
Tivoli
Business
Systems
Manager
environment
is
configured
correctly
and
that
you
have
Tivoli
Event
Enablement
installed
on
each
IBM
Tivoli
Enterprise
Console
event
server
that
you
want
to
forward
events.
See
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
Before
installing
this
integration
program,
stop
the
Tivoli
BSM
Application
Server
NT
Service
and
then
stop
the
Tivoli
BSM
Propagation
Dispatcher
NT
Service.
When
you
finish
Configure
the
IBM
Tivoli
Enterprise
Console
event
server
to
forward
events
to
IBM
Tivoli
Business
Systems
Manager.
See
“Configuring
the
IBM
Tivoli
Enterprise
Console
event
server
to
work
with
IBM
Tivoli
Business
Systems
Manager”
for
more
information.
Procedure
Use
the
following
steps
to
install
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program:
1.
On
the
IBM
Tivoli
Business
Systems
Manager
server,
insert
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
CD
and,
from
a
command
prompt,
navigate
to
the
\TBSM
directory.
2.
Type
install
to
start
the
installation
wizard.
3.
Click
Next
on
the
welcome
panel.
4.
Specify
an
installation
location
for
the
IBM
Tivoli
Business
Systems
Manager
integration
program.
Click
Browse
to
select
a
different
installation
location.
Click
Next
to
continue.
5.
Provide
the
following
Microsoft
SQL
Server
information
and
click
Next
to
start
the
installation.
SQL
Server
The
name
of
the
SQL
server
with
which
this
IBM
Tivoli
Business
Systems
Manager
server
is
associated
SQL
Userid
The
SQL
user
ID
SQL
Password
The
password
for
the
user
ID
defined
aboveA
progress
bar
is
displayed
to
show
the
progress
of
the
installation.
When
installation
is
complete,
a
message
is
displayed.
6.
Click
Finish
to
exit
the
installation
wizard.
Configuring
the
IBM
Tivoli
Enterprise
Console
event
server
to
work
with
IBM
Tivoli
Business
Systems
Manager
Objective
To
configure
the
IBM
Tivoli
Enterprise
Console
event
server
to
forward
events
to
IBM
Tivoli
Business
Systems
Manager.
Background
information
You
must
configure
your
event
servers
before
they
can
forward
events
to
IBM
Tivoli
Business
Systems
Manager.
Appendix
A.
Integrating
with
IBM
Tivoli
Business
Systems
Manager
73
Required
authorization
role
senior
Before
you
begin
Install
the
Tivoli
Event
Enablement
on
each
IBM
Tivoli
Enterprise
Console
event
server
that
you
want
to
forward
events
to
IBM
Tivoli
Business
Systems
Manager.
See
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
When
you
finish
Define
your
Microsoft
Exchange
servers
for
IBM
Tivoli
Business
Systems
Manager
with
the
MSExchangeTBSMDiscovery
task,
as
described
in
“Discovering
resources
for
IBM
Tivoli
Business
Systems
Manager.”
Procedure
Use
the
Configure
Event
Server
task
to
configure
(or
re-configure)
each
event
server.
If
you
installed
the
Tivoli
Event
Enablement
on
the
event
server,
this
task
recognizes
that
and
compiles
the
rule
base
that
forwards
events
to
IBM
Tivoli
Business
Systems
Manager.
For
information
on
running
this
task,
see
“Configuring
the
IBM
Tivoli
Enterprise
Console
event
server”
on
page
26.
Discovering
resources
for
IBM
Tivoli
Business
Systems
Manager
Objective
To
define
the
specific
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
objects
for
IBM
Tivoli
Business
Systems
Manager.
Background
information
The
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program
that
you
installed
in
“Integrating
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
with
IBM
Tivoli
Business
Systems
Manager”
on
page
72
defined
the
types
of
objects
that
you
want
IBM
Tivoli
Business
Systems
Manager
to
manage.
After
you
define
the
object
types,
define
the
specific
objects
with
the
MSExchangeTBSMDiscovery
task.
This
task
searches
a
managed
node
for
Microsoft
Exchange
servers
and
sends
a
DISCOVER
event
to
IBM
Tivoli
Business
Systems
Manager
for
each
object.
The
MSExchangeTBSMDiscovery
task
also
maintains
a
list
of
the
objects
that
have
been
discovered
and
alerts
IBM
Tivoli
Business
Systems
Manager
when
they
have
been
deleted
by
sending
IBM
Tivoli
Business
Systems
Manager
a
GONE
event
for
each
object
that
no
longer
exists
on
the
managed
node.
Required
authorization
role
msexchgserver_admin
Before
you
begin
Configure
your
IBM
Tivoli
Enterprise
Console
event
server,
as
described
in
“Configuring
the
IBM
Tivoli
Enterprise
Console
event
server
to
work
with
IBM
Tivoli
Business
Systems
Manager”
on
page
73.
When
you
finish
Use
IBM
Tivoli
Business
Systems
Manager
to
view
and
manage
your
Microsoft
Exchange
servers.
See
the
IBM
Tivoli
Business
Systems
Manager
User’s
Guide
for
more
information
on
using
IBM
Tivoli
Business
Systems
Manager.
For
information
on
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
that
you
can
run
from
IBM
Tivoli
Business
Systems
Manager,
see
“Working
with
IBM
Tivoli
Business
Systems
Manager”
on
page
75.
74
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Procedure
You
can
perform
this
procedure
from
the
command
line
or
the
Tivoli
desktop.
Command
line:
Use
the
wruntask
command
to
run
the
MSExchangeTBSMDiscovery
task
from
the
command
line.
For
information
on
the
CLI
syntax
for
this
task,
see
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide.
Tivoli
desktop:
Use
the
following
steps
to
run
this
procedure
as
a
task:
1.
In
the
ITMMicrosoftExchangeServerTasks
task
library,
double-click
MSExchangeTBSMDiscovery.
2.
Select
the
managed
node
where
the
IBM
Tivoli
Enterprise
Console
event
server
is
running.
3.
Select
Display
on
Desktop
to
display
the
output
on
the
desktop.
4.
Increase
the
timeout
value
if
you
selected
more
than
one
managed
node
because
this
can
cause
the
task
to
take
longer
to
display
output.
5.
Click
Execute.
If
the
task
completes
successfully,
you
receive
a
list
of
the
DISCOVER
and
GONE
events
that
were
sent
to
IBM
Tivoli
Business
Systems
Manager.
Working
with
IBM
Tivoli
Business
Systems
Manager
In
addition
to
using
IBM
Tivoli
Business
Systems
Manager
to
monitor
the
state
of
your
resources,
you
can
also
run
tasks
on
the
objects.
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
tasks
are
loaded
into
IBM
Tivoli
Business
Systems
Manager
when
you
install
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program.
IBM
Tivoli
Business
Systems
Manager
also
monitors
the
status
of
resource
models.
Events
generated
by
the
IBM
Tivoli
Enterprise
Console
adapter
or
resource
models
are
forwarded
from
IBM
Tivoli
Enterprise
Console
to
IBM
Tivoli
Business
Systems
Manager.
See
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
Reference
Guide
for
more
information
about
tasks
and
resource
models.
Uninstalling
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
from
IBM
Tivoli
Business
Systems
Manager
Objective
To
remove
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program
from
IBM
Tivoli
Business
Systems
Manager.
Background
information
Uninstalling
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program
removes
the
Microsoft
Exchange
server
definitions
and
objects
from
IBM
Tivoli
Business
Systems
Manager.
Required
authorization
role
Administrator
authority
on
the
IBM
Tivoli
Business
Systems
Manager
server.
Appendix
A.
Integrating
with
IBM
Tivoli
Business
Systems
Manager
75
Before
you
begin
Not
applicable
When
you
finish
Not
applicable
Procedure
Use
the
following
steps
to
perform
this
procedure:
1.
From
a
command
prompt
on
the
IBM
Tivoli
Business
Systems
Manager
server,
navigate
to
the
directory
where
you
installed
the
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
integration
program.
2.
Type
uninstall
to
start
the
uninstallation
wizard.
3.
Click
Next
on
the
welcome
screen.
4.
The
installation
location
for
the
IBM
Tivoli
Business
Systems
Manager
integration
program
is
displayed.
Click
Next
to
continue.
5.
Provide
the
following
Microsoft
SQL
Server
information
and
click
Next
to
start
the
uninstallation:
SQL
Server
The
name
of
the
SQL
server
with
which
this
IBM
Tivoli
Business
Systems
Manager
server
is
associated
SQL
Userid
The
SQL
user
ID
SQL
Password
The
password
for
the
user
ID
defined
above6.
Click
Finish
to
exit
the
installation
wizard.
76
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Appendix
B.
Accessibility
Accessibility
features
help
users
with
physical
disabilities,
such
as
restricted
mobility
or
limited
vision,
to
use
software
products
successfully.
The
major
accessibility
features
in
this
product
enable
users
to
do
the
following:
v
Use
assistive
technologies,
such
as
screen-reader
software
and
digital
speech
synthesizer,
to
hear
what
is
displayed
on
the
screen.
Consult
the
product
documentation
of
the
assistive
technology
for
details
on
using
those
technologies
with
this
product.
v
Operate
specific
or
equivalent
features
using
only
the
keyboard.
v
Magnify
what
is
displayed
on
the
screen.
In
addition,
the
product
documentation
was
modified
to
include
the
following
features
to
aid
accessibility:
v
All
documentation
is
available
in
both
HTML
and
convertible
formats
to
give
the
maximum
opportunity
for
users
to
apply
screen-reader
software.
v
All
images
in
the
documentation
are
provided
with
alternative
text
so
that
users
with
vision
impairments
can
understand
the
contents
of
the
images.
Navigating
the
interface
using
the
keyboard
Standard
shortcut
and
accelerator
keys
are
used
by
the
product
and
are
documented
by
the
operating
system.
Refer
to
the
documentation
provided
by
your
operating
system
for
more
information.
Magnifying
what
is
displayed
on
the
screen
You
can
enlarge
information
on
the
product
windows
using
facilities
provided
by
the
operating
systems
on
which
the
product
is
run.
For
example,
in
a
Microsoft
Windows
environment,
you
can
lower
the
resolution
of
the
screen
to
enlarge
the
font
sizes
of
the
text
on
the
screen.
Refer
to
the
documentation
provided
by
your
operating
system
for
more
information.
©
Copyright
IBM
Corp.
2004
77
78
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Appendix
C.
Notices
This
information
was
developed
for
products
and
services
offered
in
the
U.S.A.
IBM
may
not
offer
the
products,
services,
or
features
discussed
in
this
document
in
other
countries.
Consult
your
local
IBM
representative
for
information
on
the
products
and
services
currently
available
in
your
area.
Any
reference
to
an
IBM
product,
program,
or
service
is
not
intended
to
state
or
imply
that
only
that
IBM
product,
program,
or
service
may
be
used.
Any
functionally
equivalent
product,
program,
or
service
that
does
not
infringe
any
IBM
intellectual
property
right
may
be
used
instead.
However,
it
is
the
user’s
responsibility
to
evaluate
and
verify
the
operation
of
any
non-IBM
product,
program,
or
service.
IBM
may
have
patents
or
pending
patent
applications
covering
subject
matter
described
in
this
document.
The
furnishing
of
this
document
does
not
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.
2004
79
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.
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.
Trademarks
AIX,
IBM,
the
IBM
logo,
Tivoli,
the
Tivoli
logo,
and
Tivoli
Enterprise
Console
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States,
other
countries,
or
both.
Java,
all
Java-based
trademarks,
and
Solaris
Operating
Environment
are
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States,
other
countries,
or
both.
Intel
is
a
trademark
of
Intel
Corporation
in
the
United
States,
other
countries,
or
both.
Microsoft,
Windows,
Windows
NT
are
registered
trademarks
of
Microsoft
Corporation
in
the
United
States,
other
countries,
or
both.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
80
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
Index
Special
characters.
/etc/Tivoli/setup_env.sh
command
8
Aaccessibility
xi,
77
administrators
1
application
proxy
objectscreating
16
editing
properties
65
starting
services
66
stopping
services
67
viewing
properties
63
working
with
63
authentication
19
authorization
rolesassigning
9
overview
2
availability
monitoring
31
Availability
resource
model
31
Bbooks
see
publications
ix,
x
Ccommand
lineuser
interface
options
8
commands.
/etc/Tivoli/setup_env.sh
8
source
/etc/Tivoli/setup_env.csh
8
special
characters
xv
syntax
xv
wcrtjob
51
wdmeditprf
23
wdmlseng
44
wrunjob
53
wruntask
for
any
task
48
wschedjob
54
wsetadmin
10
wsub
22
configuration
7
configuringcommunication
for
resource
models
15
creating
a
local
administrator
13
creating
a
MAPI
profile
14
creating
application
proxy
objects
16
creating
Microsoft
Exchange
user
11
endpoints
10
IBM
Tivoli
Enterprise
Console
26
IBM
Tivoli
Enterprise
Console
event
server
73
profiles
and
profile
managers
20
conventionstypeface
xiv
customer
supportsee
Software
Support
xi
cycle
time
29
Ddata
logging
31
directory
names,
notation
xv
DiscoverExchangeServers
job
17
DiscoverExchangeServers
task
17
discovering
endpoints
16
discovery
17
Ee-mail
monitoring
31
editing
properties
65
educationsee
Tivoli
technical
training
xi
endpointsconfiguring
10
discovering
16
subscribing
21
environment
variables,
notation
xv
event
serverconfiguring
26
eventsconfiguring
event
server
26
customizing
for
resource
models
35
notice
to
administrators,
sending
37
resource
models
30
Ffixes,
obtaining
xiv
IIBM
Tivoli
Business
Systems
Managerdiscovering
resources
74
installing
73
integrating
with
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server
72
MSExchangeTBSMDiscovery
task
75
prerequisites
for
integrating
72
understanding
71
IBM
Tivoli
Data
Warehouselogging
resource
model
data
41
reports
59
IBM
Tivoli
Enterprise
Console
26,
34
event
server,
configuring
26,
73
IBM
Tivoli
Monitoringoverview
29
inactivity
report
58
indications
30
customizing
35
tasks,
specifying
36
information
centers,
searching
xiii
installationIBM
Tivoli
Business
Systems
Manager
73
setup
and
access
Tivoli
environment
8
Internet,
searching
to
find
software
problem
resolution
xiii,
xiv
Jjobs
creating
51
overview
45
running
53
scheduling
54
Kknowledge
bases,
searching
xiii
LLine
of
Business
71
loggingcustomizing
data
41
resource
models
31
Logs
resource
model
33
MMailbox
Monitors
resource
model
32
mailboxesinactivity
report
58
monitoring
information
about
32
monitoring
message
volume
32
managing
profiles
at
endpoints
42
manualssee
publications
ix,
x
MAPI
profile
14
message
queues
32
message
transporting
32
message
volume
32
Message
Volume
resource
model
32
Messaging
Application
Programming
Interface
profile
14
Microsoft
Exchange
Serveraddressing
problems
with
69
application
proxy
objects
16
authentication
19
configuring
10
configuring
communication
15
creating
a
local
administrator
13
creating
a
MAPI
profile
14
creating
a
user
11
editing
properties
65
starting
services
66
stopping
services
67
system
alerts,
monitoring
33
©
Copyright
IBM
Corp.
2004
81
Microsoft
Exchange
Server
(continued)utilities
69
viewing
properties
63
monitoringmessage
transporting
32
space
usage
33
using
tasks
46
monitoring
cycles
29
monitoring
flow
31
monitoring
performancecreating
reports
57
msexchgserver_admin
9
msexchgserver_user
9
Nnotation
environment
variables
xv
path
names
xv
typeface
xv
Oonline
publicationsaccessing
x
ordering
publications
xi
overview
1
Pparameters
30
customizing
38
path
names,
notation
xv
performance
57
IBM
Tivoli
Data
Warehouse
reports
59
inactivity
report
58
space
usage
57
performance
monitoring
32
problem
determinationdescribing
problem
for
IBM
Software
Support
xii
determining
business
impact
for
IBM
Software
Support
xii
submitting
problem
to
IBM
Software
Support
xiii
profile
managersadding
resource
models
22
creating
20
subscribing
endpoints
21
profiles
20
distributing
24
managing
at
endpoints
42
propertiesediting
65
viewing
63
publications
ix
accessing
online
x
ordering
xi
QQueues
resource
model
32
RReachability
configuring
communication
for
15
Reachability
resource
model
31
reportsIBM
Tivoli
Data
Warehouse
reports
59
inactivity
report
58
space
usage
57
resource
models
29
adding
to
a
profile
manager
22
Availability
31
concepts
29
customizing
35
cycle
29
deploying
24
determining
what
has
been
distributed
43
determining
what
is
running
44
events
30,
34,
35
indications
30,
35
logging
31
logging
data
41
Logs
33
Mailbox
Monitors
32
managing
at
endpoints
42
Message
Volume
32
monitoring
alerts
and
events
33
monitoring
performance
and
availability
31
parameters
30,
38
procedures,
working
with
35
Queues
32
Reachability
31
scheduling
30,
39
sending
notice
to
administrators
37
Space
Usage
33
tasks
for
an
indication,
specifying
36
thresholds
30
resourcesdiscovering
for
IBM
Tivoli
Business
Systems
Manager
74
response
task
36
rolesauthorization,
assigning
9
Sscenarios
3
ensuring
efficient
configuration
4
monitoring
servers
3
schedule,
resource
models
39
schedulingresource
models
30
scriptssetup_env.csh
8
setup_env.sh
8
servicescontinuing
66
pausing
67
starting
66
stopping
67
setting
up
7
setup_env.csh
script
8
setup_env.sh
script
8
Software
Supportcontacting
xi
describing
problem
for
IBM
Software
Support
xii
determining
business
impact
for
IBM
Software
Support
xii
submitting
problem
to
IBM
Software
Support
xiii
source
/etc/Tivoli/setup_env.csh
command
8
space
usage
report
57
Space
Usage
resource
model
33
subscribingendpoints
21
Ttask
standard
tasks
48
task
library
45
taskscontrolling
resource
status
with
47
customizing
50
descriptions
45
DiscoverExchangeServers
17
gathering
information
with
47
library
45
monitoring
with
46
MSExchangeTBSMDiscovery
75
overview
45
running
48
using
to
address
problems
69
utility
69
thresholds
30
Tivoli
Business
Systems
Managerconfiguring
IBM
Tivoli
Enterprise
Console
to
forward
events
73
uninstalling
75
Tivoli
desktopuser
interface
options
8
Tivoli
environmentaccessing
8
setting
up
8
Tivoli
login
screen
9
Tivoli
Management
Frameworkaccessing
8
set
up
and
start
of
the
Tivoli
environment
8
Tivoli
objectsauthenticating
19
creating
16
editing
properties
65
starting
services
66
stopping
services
67
viewing
properties
63
working
with
63
Tivoli
software
information
center
x
Tivoli
technical
training
xi
training,
Tivoli
technical
xi
typeface
conventions
xiv
Uuser
interface
options
2
command
line
8
Tivoli
desktop
8
82
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
user
interface
options
(continued)Tivoli
Management
Framework
8
utility
tasks
69
Vvariables,
notation
for
xv
viewing
properties
63
Wwcrtjob
command
51
wdmeditprf
command
23
wdmlseng
command
44
wrunjob
command
53
wruntask
commandfor
any
task
48
wschedjob
command
54
wsetadmin
command
10
wsub
command
22
wxregsvr
command
17
Index
83
84
IBM
Tivoli
Monitoring
for
Messaging
and
Collaboration:
Microsoft
Exchange
Server:
User’s
Guide
����
Printed
in
USA
SC32-9110-00