121
IBM Tivoli Monitoring for Transaction Performance Problem Determination Guide 5.2.0 SC32-1387-00
IBM
Tivoli
Monitoring
for
Transaction
Performance
Problem
Determination
Guide
5.2.0
SC32-1387-00
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
Notices,
on
page
105.
First
Edition
(October
2003)
This
edition
applies
to
version
5.2.0
of
IBM
Tivoli
Monitoring
for
Transaction
Performance
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
Copyright
International
Business
Machines
Corporation
2003.
All
rights
reserved.
US
Government
Users
Restricted
Rights
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
About
this
guide
.
.
.
.
.
.
.
.
.
.
. v
Who
should
read
this
guide
.
.
.
.
.
.
.
.
. v
What
this
guide
contains
.
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
IBM
Tivoli
Monitoring
for
Transaction
Performance
library
.
.
.
.
.
.
.
.
.
.
. vi
Prerequisite
publications
.
.
.
.
.
.
.
.
. vi
Related
publications
.
.
.
.
.
.
.
.
.
. vii
Accessing
publications
online
.
.
.
.
.
.
. vii
Ordering
publications
.
.
.
.
.
.
.
.
. viii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. viii
Contacting
software
support
.
.
.
.
.
.
.
. viii
Conventions
used
in
this
guide
.
.
.
.
.
.
. viii
Typeface
conventions
.
.
.
.
.
.
.
.
.
. ix
Operating
system-dependent
variables
and
paths
ix
Tivoli
command
syntax
.
.
.
.
.
.
.
.
. ix
Chapter
1.
Introduction
to
problem
determination
.
.
.
.
.
.
.
.
.
.
.
. 1
Product
overview
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Built-in
problem
determination
features
.
.
.
.
. 1
Problem
classification
.
.
.
.
.
.
.
.
.
.
. 2
Tivoli
Support
Technical
Exchange
.
.
.
.
.
.
. 2
Chapter
2.
Installation
Troubleshooting
5
Installation
overview
.
.
.
.
.
.
.
.
.
.
. 5
Instructions
for
mounting
CDs
on
UNIX-based
systems
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Manually
mounting
the
cdrom
device
.
.
.
.
. 5
Using
Volume
Manager
.
.
.
.
.
.
.
.
.
. 5
Examples
For
Solaris
8
.
.
.
.
.
.
.
.
.
. 6
Examples
For
RedHat
Linux
7.2
.
.
.
.
.
.
. 6
Examples
For
AIX
.
.
.
.
.
.
.
.
.
.
. 6
Installation
error
messages
and
logs
.
.
.
.
.
. 7
Installation
trace
levels
.
.
.
.
.
.
.
.
.
.
. 7
Installation
command-line
options
.
.
.
.
.
.
. 9
-W
options
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
-is
options
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
Installation
recovery
procedures
.
.
.
.
.
.
. 10
Common
installation
problems
.
.
.
.
.
.
.
. 10
Chapter
3.
Common
Problems
.
.
.
. 21
Synthetic
Transaction
Investigator
.
.
.
.
.
.
. 21
Generic
Windows
.
.
.
.
.
.
.
.
.
.
.
. 30
J2EE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 34
Quality
of
Service
.
.
.
.
.
.
.
.
.
.
.
. 43
Reports
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 46
DB2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 48
Tivoli
Enterprise
Console
.
.
.
.
.
.
.
.
.
. 51
Tivoli
Enterprise
Data
Warehouse
.
.
.
.
.
.
. 53
WebSphere
Application
Services
.
.
.
.
.
.
. 53
Configuration
.
.
.
.
.
.
.
.
.
.
.
.
. 53
J2EE
component
configuration
files
.
.
.
.
. 56
General
troubleshooting
.
.
.
.
.
.
.
.
.
. 58
Chapter
4.
Understanding
informational,
warning,
and
error
messages
.
.
.
.
.
.
.
.
.
.
.
.
. 65
Message
log
location
and
format
.
.
.
.
.
.
. 65
Message
log
location
.
.
.
.
.
.
.
.
.
. 65
Message
format
.
.
.
.
.
.
.
.
.
.
.
. 67
Logging.properties
file
.
.
.
.
.
.
.
.
.
. 68
Logging
objects
.
.
.
.
.
.
.
.
.
.
.
. 68
Other
logging
properties
.
.
.
.
.
.
.
.
. 69
Command
line
interface
.
.
.
.
.
.
.
.
. 69
Web
browser
interface
.
.
.
.
.
.
.
.
.
.
. 71
LoggingService
MBean
.
.
.
.
.
.
.
.
. 71
Product
messages
.
.
.
.
.
.
.
.
.
.
.
. 72
Chapter
5.
Trace
logging
and
other
diagnostic
tools
.
.
.
.
.
.
.
.
.
.
. 89
Trace
log
overview
.
.
.
.
.
.
.
.
.
.
.
. 89
Trace
log
location
.
.
.
.
.
.
.
.
.
.
.
. 89
Trace
log
format
.
.
.
.
.
.
.
.
.
.
.
.
. 89
Trace
levels
.
.
.
.
.
.
.
.
.
.
.
.
.
. 90
Changing
trace
levels
.
.
.
.
.
.
.
.
.
. 91
Logging
properties
.
.
.
.
.
.
.
.
.
.
. 91
Logging
on
the
management
server
.
.
.
.
. 92
Logging
on
the
management
agent
.
.
.
.
. 92
Configuration
collector
tool
.
.
.
.
.
.
.
.
. 93
ARM
Engine
logging
.
.
.
.
.
.
.
.
.
.
. 93
J2EE
Trace
Logs
.
.
.
.
.
.
.
.
.
.
.
.
. 94
Management
Agent
Trace
Logs
.
.
.
.
.
.
. 94
J2EE
Runtime
Trace
Logs
.
.
.
.
.
.
.
.
. 94
How
do
I
change
the
trace
levels
for
J2EE?
.
.
. 94
Running
Synthetic
Transaction
Investigator
in
visible
mode
.
.
.
.
.
.
.
.
.
.
.
.
.
. 95
Chapter
6.
Configuration
.
.
.
.
.
.
. 97
ARM
Engine
configuration
.
.
.
.
.
.
.
.
. 97
Monitoring
engine
configuration
.
.
.
.
.
.
. 99
Monitoring
engine
troubleshooting
.
.
.
.
.
. 100
Management
server
configuration
.
.
.
.
.
. 100
Event
configuration
for
the
management
server
and
agent
.
.
.
.
.
.
.
.
.
.
.
.
.
. 101
SMTP
configuration
for
the
management
server
102
SNMP
configuration
for
the
management
server
102
Store
and
Forward
configuration
.
.
.
.
.
.
. 103
Database
purge
configuration
.
.
.
.
.
.
.
. 104
Appendix.
Notices
.
.
.
.
.
.
.
.
. 105
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 107
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 109
iii
iv
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
About
this
guide
This
guide
provides
problem
determination
and
resolution
information
for
the
issues
most
commonly
encountered
with
IBM
Tivoli
Monitoring
for
Transaction
Performance.
You
can
use
this
guide
in
conjunction
with
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
Installation
Guide,
which
contains
installation
and
configuration
procedures,
and
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
Users
Guide,
which
contains
functional
procedures.
This
guide
can
assist
you
in
investigating
problems
you
might
have
with
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
and
isolating
these
problems
using
diagnostic
information.
After
you
isolate
a
problem,
you
can
search
known
problems
and
identify
circumvention
and
workarounds.
Who
should
read
this
guide
This
book
is
for
system
administrators.
It
explains
the
concepts
you
should
know
to
resolve
issues
with
IBM
Tivoli
Monitoring
for
Transaction
Performance.
Readers
should
be
familiar
with
the
following:
v
Operating
systems
on
which
you
intend
to
use
this
product.
Supported
operating
systems
include
Windows
NT,
Windows
2000,
Windows
XP,
AIX,
Solaris
Operating
Environment
(referred
to
as
Solaris
in
this
document),
Red
Hat
Linux,
SuSE
Linux,
and
TurboLinux.
v
Web
servers,
such
as
IBM
HTTP
Server,
Apache
HTTP
Server,
and
Microsoft
Internet
Information
Server.
v
Web
application
servers,
such
as
IBM
WebSphere
Application
Server.
v
Internet
protocols,
such
as
HTTP,
HTTPS,
TCP/IP,
Secure
Sockets
Layer
(SSL),
and
Transport
Layer
Security
(TLS).
v
Digital
certificates
for
secure
communication.
v
Oracle
or
IBM
DB2
database
management
systems.
What
this
guide
contains
This
guide
contains
the
following
sections:
v
Chapter
1,
Introduction
to
problem
determination,
on
page
1
Provides
an
overview
of
problem
determination
concepts
used
to
troubleshoot
IBM
Tivoli
Monitoring
for
Transaction
Performance
issues.
v
Chapter
2,
Installation
Troubleshooting,
on
page
5
Provides
information
on
troubleshooting
installation
for
IBM
Tivoli
Monitoring
for
Transaction
Performance.
v
Chapter
3,
Common
Problems,
on
page
21
Provides
information
and
troubleshooting
tips
about
common
problems
that
might
occur
with
IBM
Tivoli
Monitoring
for
Transaction
Performance.
v
Chapter
4,
Understanding
informational,
warning,
and
error
messages,
on
page
65
Provides
an
explanation
of
message
identification
and
lists
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
messages.
v
Chapter
5,
Trace
logging
and
other
diagnostic
tools,
on
page
89
v
Provides
trace
log
information
for
IBM
Tivoli
Monitoring
for
Transaction
Performance.
v
Chapter
6,
Configuration,
on
page
97
Provides
configuration
information
to
optimize
IBM
Tivoli
Monitoring
for
Transaction
Performance.
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
library
and
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online,
and
how
to
order
Tivoli
publications.
IBM
Tivoli
Monitoring
for
Transaction
Performance
library
The
following
documents
provide
information
about
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
product:
v
IBM
Tivoli
Monitoring
for
Transaction
Performance
Installation
Guide,
SC32-1385
Provides
prerequisite
information
and
instructions
for
installing
the
Web
Transaction
Performance
component.
This
guide
also
contains
information
that
you
might
find
useful
after
installing
the
product,
such
as
uninstallation
instructions
and
reference
information
about
digital
certificates.
v
IBM
Tivoli
Monitoring
for
Transaction
Performance
Users
Guide,
SC32-1386
Provides
detailed
procedures
for
using
each
of
the
Web
Transaction
Performance
applications.
The
guide
also
describes
the
browser-based
graphical
user
interface
(GUI),
the
help
system,
and
how
to
use
Tivoli
Decision
Support
to
produce
graphical
reports
from
Web
Transaction
Performance
v
IBM
Tivoli
Monitoring
for
Transaction
Performance
Warehouse
Enablement
Guide,
SC32-1388
Describes
how
to
install
and
configure
the
warehouse
enablement
pack
for
the
Web
Transaction
Performance
component.
This
document
also
describes
the
data
flow
and
data
structures
used
by
the
warehouse
pack.
The
warehouse
pack
enables
Web
Transaction
Performance
to
transfer
data
to
the
Tivoli
Enterprise
Data
Warehouse.
Prerequisite
publications
Web
Transaction
Performance
can
optionally
be
integrated
with
a
number
of
enterprise
products
to
provide
more
advanced
capabilities.
Following
is
a
list
of
these
products
and
some
of
the
publications
provided
by
each
product.
v
IBM
Tivoli
Enterprise
Console
IBM
Tivoli
Enterprise
Console
Installation
Guide,
GC320823
Discusses
how
to
install,
upgrade,
and
remove
IBM
Tivoli
Enterprise
Console
components
and
provides
details
about
using
the
event
database
installation
assistant.
IBM
Tivoli
Enterprise
Console
Users
Guide,
GC32-0667
Provides
information
needed
to
understand
and
set
up
the
IBM
Tivoli
Enterprise
Console
and
describes
procedures
for
using
all
components
of
the
product.
IBM
Tivoli
Enterprise
Console
Rule
Builders
Guide,
GC32-0669
Provides
information
about
developing
rules
for
automating
the
management
of
IBM
Tivoli
Enterprise
Console
events
received
by
the
IBM
Tivoli
Enterprise
Console
event
server.v
IBM
Tivoli
Enterprise
Data
Warehouse
vi
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
Tivoli
Enterprise
Data
Warehouse
Release
Notes,
GI11-0857
Provides
late-breaking
information
about
Tivoli
Enterprise
Data
Warehouse
and
lists
hardware
requirements
and
software
prerequisites.
Installing
and
Configuring
Tivoli
Enterprise
Data
Warehouse,
GC32-0744
Describes
how
Tivoli
Enterprise
Data
Warehouse
fits
into
your
enterprise,
explains
how
to
plan
for
its
deployment,
and
gives
installation
and
configuration
instructions.
It
provides
an
introduction
to
the
built-in
program
for
creating
and
running
reports,
and
contains
maintenance
procedures
and
troubleshooting
information.
Enabling
an
Application
for
Tivoli
Enterprise
Data
Warehouse,
GC32-0745
Provides
information
about
connecting
an
application
to
Tivoli
Enterprise
Data
Warehouse.
This
book
is
for
application
programmers
who
use
Tivoli
Enterprise
Data
Warehouse
to
store
and
report
on
their
applications
data,
data
warehousing
experts
who
import
Tivoli
Enterprise
Data
Warehouse
data
into
business
intelligence
applications,
and
customers
who
use
their
local
data
in
the
warehouse.v
IBM
WebSphere
Site
Analyzer
All
information
about
IBM
WebSphere
Site
Analyzer
is
provided
on
the
following
Web
site:
http://www-3.ibm.com/software/webservers/siteanalyzer/library.html
v
IBM
WebSphere
Application
Server,
Version
5.0.1
All
information
about
the
IBM
WebSphere
Application
Server
Version
5.0
is
provided
on
the
following
Web
site:
http://www-3.ibm.com/software/webservers/appserv/was/library/
Related
publications
The
Tivoli
Software
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Software
Glossary
is
available,
in
English
only,
at
the
following
Web
site:
http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm
Accessing
publications
online
The
documentation
CD
contains
the
publications
that
are
in
the
product
library.
The
format
of
the
publications
is
PDF,
HTML,
or
both.
Refer
to
the
readme
file
on
the
CD
for
instructions
on
how
to
access
the
documentation.
IBM
posts
publications
for
this
and
all
other
Tivoli
products,
as
they
become
available
and
whenever
they
are
updated,
to
the
Tivoli
software
information
center
Web
site.
Access
the
Tivoli
software
information
center
by
first
going
to
the
Tivoli
software
library
at
the
following
Web
address:
http://www.ibm.com/software/tivoli/library/
Scroll
down
and
click
the
Product
manuals
link.
In
the
Tivoli
Technical
Product
Documents
Alphabetical
Listing
window,
click
M
to
access
all
of
the
IBM
Tivoli
Monitoring
product
manuals.
Note:
If
you
documents
on
other
than
letter-sized
paper,
set
the
option
in
the
File
window
that
allows
Adobe
Reader
to
letter-sized
pages
on
your
local
paper.
About
this
guide
vii
http://www-3.ibm.com/software/webservers/siteanalyzer/library.htmlhttp://www-3.ibm.com/software/webservers/siteanalyzer/library.htmlhttp://www-3.ibm.com/software/webservers/appserv/was/library/http://www-3.ibm.com/software/webservers/appserv/was/library/http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htmhttp://www.ibm.com/software/tivoli/library/
The
IBM
Tivoli
Software
Support
Web
site
provides
the
latest
information
about
known
product
limitations
and
workarounds
for
your
product.
You
can
view
this
information
at
the
following
Web
site:
http://www-3.ibm.com/software/support
Ordering
publications
You
can
order
many
Tivoli
publications
online
at
the
following
Web
site:
http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi
You
can
also
order
by
telephone
by
calling
one
of
these
numbers:
v
In
the
United
States:
800-879-2755
v
In
Canada:
800-426-4968
In
other
countries,
see
the
following
Web
site
for
a
list
of
telephone
numbers:
http://www.ibm.com/software/tivoli/order-lit/
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
users
guide
for
this
product.
Contacting
software
support
If
you
have
a
problem
with
any
Tivoli
product,
refer
to
the
following
IBM
Tivoli
Software
Support
Web
site:
http://www.ibm.com/software/sysmgmt/products/support/
If
you
want
to
contact
software
support,
see
the
IBM
Software
Support
Guide
at
the
following
Web
site:
http://techsupport.services.ibm.com/guides/handbook.html
The
guide
provides
information
about
how
to
contact
IBM
Software
Support,
depending
on
the
severity
of
your
problem,
and
the
following
information:
v
Registration
and
eligibility
v
Telephone
numbers,
depending
on
the
country
in
which
you
are
located
v
Information
you
must
have
before
contacting
IBM
Software
Support
Conventions
used
in
this
guide
This
guide
uses
several
conventions
for
special
terms
and
actions,
and
operating
system-dependent
commands
and
paths.
viii
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
http://www-3.ibm.com/software/supporthttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/sysmgmt/products/support/http://techsupport.services.ibm.com/guides/handbook.html
Typeface
conventions
This
guide
uses
the
following
typeface
conventions:
Bold
v
Lowercase
commands
and
mixed
case
commands
that
are
otherwise
difficult
to
distinguish
from
surrounding
text
v
Interface
controls
(check
boxes,
push
buttons,
radio
buttons,
spin
buttons,
fields,
folders,
icons,
list
boxes,
items
inside
list
boxes,
multicolumn
lists,
containers,
menu
choices,
menu
names,
tabs,
property
sheets),
labels
(such
as
Tip:,
and
Operating
system
considerations:)
v
Keywords
and
parameters
in
text
Italic
v
Words
defined
in
text
v
Emphasis
of
words
(words
as
words)
v
New
terms
in
text
(except
in
a
definition
list)
v
Variables
and
values
you
must
provide
Monospace
v
Examples
and
code
examples
v
File
names,
programming
keywords,
and
other
elements
that
are
difficult
to
distinguish
from
surrounding
text
v
Message
text
and
prompts
addressed
to
the
user
v
Text
that
the
user
must
type
v
Values
for
arguments
or
command
options
Operating
system-dependent
variables
and
paths
The
publications
in
this
library
use
the
UNIX
convention
for
specifying
environment
variables
and
for
directory
notation.
When
using
the
Windows
command
line,
replace
$variable
with
%variable%
for
environment
variables
and
replace
each
forward
slash
(/)
with
a
backslash
(\)
in
directory
paths.
The
names
of
environment
variables
are
not
always
the
same
in
Windows
and
UNIX.
For
example,
%TEMP%
in
Windows
is
equivalent
to
$tmp
in
UNIX.
Note:
If
you
are
using
the
bash
shell
on
a
Windows
system,
you
can
use
the
UNIX
conventions.
Tivoli
command
syntax
The
following
special
characters
define
Tivoli
command
syntax:
[
]
Identifies
elements
that
are
optional.
Required
elements
do
not
have
brackets
around
them.
...
Indicates
that
you
can
specify
multiple
values
for
the
previous
element.
Separate
multiple
values
by
a
space,
unless
otherwise
directed
by
command
information.
If
the
ellipsis
for
an
element
follows
a
closing
bracket,
use
the
syntax
within
the
brackets
to
specify
multiple
values.
For
example,
to
specify
two
administrators
for
the
option
[a
admin]...,
use
a
admin1
a
admin2.
About
this
guide
ix
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
ix.
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...}
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.
x
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
Chapter
1.
Introduction
to
problem
determination
This
problem
determination
guide
explains
how
to
troubleshoot
IBM
Tivoli
Monitoring
for
Transaction
Performance.
Troubleshooting,
or
problem
determination,
is
the
process
of
determining
why
a
certain
product
is
malfunctioning.
This
chapter
introduces
troubleshooting
as
a
high-level
concept,
and
then
relates
it
back
to
the
product.
Product
overview
IBM
Tivoli
Monitoring
for
Transaction
Performance
monitors
the
availability
and
performance
of
Web-based
services.
The
monitoring
components
for
this
product
measure
the
following
aspects
of
system
performance
and
user
experience:
v
Round
trip
time
(also
called
user
experience
time)
v
Service
time
(also
called
back-end
service
time)
v
Page
display
time
v
Transaction
decomposition
v
System
performance
and
availability
for
a
synthetic
transaction
that
runs
under
varying
conditions
The
centralized
management
capability
of
IBM
Tivoli
Monitoring
for
Transaction
Performance
helps
you
keep
your
Web
services
available
and
performing
optimally.
The
IBM
Tivoli
Monitoring
for
Transaction
Performance
5.2
release
provides
the
following
key
features:
v
A
discovery
mechanism
to
identify
user
transactions
that
you
want
to
monitor
and
establish
baseline
thresholds.
v
The
capability
to
decompose
transaction
response
times
to
the
method
level
v
Dynamic
flexibility
to
configure
the
level
of
transaction
data
to
be
that
you
want
to
collect.
You
can
increase
or
reduce
instrumentation
levels
without
restarting
application
servers.
v
The
capability
to
collect
and
retain
a
configurable
number
of
transaction
instances
after
a
failure
occurrence.
Built-in
problem
determination
features
IBM
Tivoli
Monitoring
for
Transaction
Performance
provides
several
features
that
support
troubleshooting
during
deployment
and
product
use.
Logging,
event
messaging,
and
the
Java
Management
Extension
(JMX)
Server
Agent
enable
you
to
quickly
discover
problems
in
your
environment
and
take
corrective
action.
Logging
provides
information
on
the
state
of
the
system
and
any
problems
encountered
while
running
the
software.
IBM
logging
tools,
JLog
and
CCLOG,
enable
you
to
adjust
volume
and
severity
logging
levels.
See
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
Users
Guide
for
instructions
on
how
to
view
these
logs.
See
Chapter
4,
Understanding
informational,
warning,
and
error
messages,
on
page
65
for
an
explanation
of
message
log
contents.
1
Event
messages
are
messages
sent
to
alert
you
when
there
is
a
problem
in
your
environment.
Component
and
system
event
messages
are
displayed
on
the
user
interface
so
that
you
can
take
corrective
actions.
The
JMX
Server
Agent
provides
information
on
management
server
and
management
agent
issues.
You
can
check
the
status
of
any
management
server,
management
agent,
or
installed
IBM
Tivoli
Monitoring
for
Transaction
Performance
components
by
accessing
http://:6969,
where
is
the
name
of
the
management
server
or
http:/:6969
where
is
the
name
of
the
management
agent.
AIX
users::
As
a
default
setting
of
AIX
operating
systems,
core
files
are
truncated
by
the
kernel;
while
saving
some
disk
space,
it
makes
identifying
a
problem
more
difficult.
If
there
is
an
intermittent
problem,
follow
these
steps
to
ensure
that
the
core
file
is
not
truncated:
1.
Set
the
ulimit
setting
for
core
files
to
unlimited
by
running
the
following
command:
ulimit
-c
unlimited
2.
Set
smitty
to
use
full
core
files
by
running
the
following
command:
chdev
-l
sys0
-a
fullcore=true
3.
Reset
EXECUTE_DIR
in
the
start_tmtp.sh
file
to
point
to
a
partition
with
sufficient
free
disk
space.
Problem
classification
This
book
groups
common
problems
and
frequently
asked
questions
into
the
following
broad
categories:
v
Synthetic
Transaction
Investigator
on
page
21
v
Generic
Windows
on
page
30
v
J2EE
on
page
34
v
Quality
of
Service
on
page
43
v
Reports
on
page
46
v
DB2
on
page
48
v
Tivoli
Enterprise
Console
on
page
51
v
Tivoli
Enterprise
Data
Warehouse
on
page
53
v
WebSphere
Application
Services
on
page
53
v
Configuration
on
page
53
v
General
troubleshooting
on
page
58
Tivoli
Support
Technical
Exchange
You
can
become
a
participant
in
the
new
Tivoli
Support
Technical
Exchange.
Expand
your
technical
understanding
of
your
current
Tivoli
products
in
a
convenient
format
hosted
by
Tivoli
Support
Engineers.
This
program
provides
support
discussions
containing
product
information,
troubleshooting
tips,
common
issues,
problem
solving
resources
and
other
support
recommendations.
Tivoli
engineers
presenting
the
topics
provide
subject
matter
expert
direction
and
value
as
Exchange
leaders.
By
participating
in
the
Exchange,
we
add
to
your
ability
to
manage
your
Tivoli
products
with
increased
effectiveness.
How
does
Tivoli
Support
Technical
Exchange
work?
Review
the
schedule
of
Exchange
sessions.
Find
a
topic
of
interest
and
select
register.
Please
provide
your
2
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
name,
phone
number,
company
name,
number
of
attendees,
the
Exchange
Topic
and
IBM
Customer
number.
You
will
be
invited
to
attend
a
1
-
2
hour
conference
call
where
the
information
is
presented.
The
new
Tivoli
Support
Technical
Exchange
can
help
with
the
following
areas:
v
Increased
product
knowledge
v
Ways
to
avoid
common
pitfalls
v
Support
recommendations
v
Proactive
customer
support
v
Helpful
hints
and
tips
v
Knowledge
transfer
v
Expansion
of
your
knowledge
base
For
more
information
or
to
suggest
a
future
Exchange
session,
contact
Support
Technical
Exchange
To
learn
more,
visit
the
following
Web
site:
http://www-3.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
Chapter
1.
Introduction
to
problem
determination
3
http://www-3.ibm.com/software/sysmgmt/products/support/supp_tech_exch.htmlhttp://www-3.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
4
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
Chapter
2.
Installation
Troubleshooting
This
chapter
provides
information
about
problems
that
might
occur
during
the
installation
of
the
software
and
information
about
performing
recovery
actions.
See
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
Installation
Guide
for
additional
information
about
installation.
Installation
overview
Since
IBM
Tivoli
Monitoring
for
Transaction
Performance
requires
WebSphere
Application
Services
and
a
database
(DB2
or
Oracle),
you
can
choose
to
install
all
three
products
(using
DB2
as
the
database)
in
one
installation
process.
Alternatively,
if
you
already
have
a
database
in
your
environment,
you
can
perform
an
installation
process
to
maintain
your
existing
database
and
install
only
the
required
software.
See
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
Installation
Guide
for
installation
requirements
and
procedures.
Instructions
for
mounting
CDs
on
UNIX-based
systems
Follow
these
instructions
to
install
the
product
directly
from
CDs.
These
instructions
are
specifically
for
UNIX-based
operating
systems
because
a
mounted
filesystem
on
UNIX,
such
as
the
cdrom
device,
cannot
be
unmounted
if
any
process
is
using
the
filesystem.
The
cdrom
device
needs
to
be
unmounted
before
a
CD
can
be
changed.
The
cdrom
can
be
mounted
either
manually
or
automatically
by
using
volume
manager.
Either
method
is
valid.
The
important
thing
is
that
you
always
use
same
mount
point
for
all
CDs
that
need
to
be
read.
This
requirement
exists
because
IBM
Tivoli
Monitoring
for
Transaction
Performance
installation
program
saves
the
path
where
it
started
from
and
uses
same
path
to
install
any
additional
software
that
may
be
needed.
Manually
mounting
the
cdrom
device
Any
volume
manager
will
need
to
be
stopped
before
a
manual
mount
can
be
performed
and
for
each
new
CD,
the
CD-ROM
device
also
has
to
be
unmounted
manually
and
remounted
again.
Using
Volume
Manager
Many
UNIX
platforms
come
with
a
volume
manager
that
automounts
CD-ROM
device
whenever
it
detects
a
new
CD
on
the
system.
This
gets
mounted
to
a
default
location
automatically.
Mount
locations
may
vary
depending
on
the
platform.
If
any
link
is
created
that
points
to
the
actual
mount
point,
it
is
important
that
the
user
starts
the
install
from
the
link.
This
action
is
required
because
the
mount
point
will
be
different
for
each
CD
and
as
mentioned
earlier,
the
installation
program
uses
the
first
path
where
it
started
from
to
read
additional
CDs.
So
for
example,
on
Solaris,
a
link
is
created
as
follows:
/cdrom/cdrom0
->
./itmtp52_wtp_1
/cdrom/itmtp52_wtp_1
5
cdrom0
is
a
link
and
will
remain
same
for
all
CDs
that
get
mounted
to
the
same
CD-ROM
device,
so
the
user
needs
to
cd
into
/cdrom/cdrom0
and
then
start
the
install.
Note:
When
you
run
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
installation
from
CD,
if
it
detects
any
missing
component,
it
will
automatically
copy
all
files
from
the
CD
to
a
temporary
directory
and
restart
itself.
This
happens
so
that
the
CD-ROM
device
is
free
for
the
user
to
insert
new
CDs.
The
first
started
install
will
then
be
killed
and
also
any
terminal
window
where
the
first
install
started
from.
The
second
launching
of
the
installation
program
(in
the
temporary
directory)
will
continue
the
installation
process.
Examples
For
Solaris
8
To
start
volume
manager:
/etc/init.d/volmgt
start
To
stop
volume
manager:
/etc/init.d/volmgt
stop
To
do
a
manual
mount:
mount
-F
hsfs
-o
ro
/dev/dsk/c0t6d0s0
/cdrom/tmtp
To
do
a
manual
unmount:
umount
/cdrom/tmtp
Start
the
install
in
/cdrom/tmtp
When
automounted,
the
default
mount
point
is
/cdrom/cdrom0,
start
the
install
in
/cdrom/cdrom0
Examples
For
RedHat
Linux
7.2
Assuming
the
CD-ROM
device
has
been
configured
when
the
operating
system
was
configured,
there
should
be
an
entry
in
/etc/fstab
and
the
default
mount
location
is
/mnt/cdrom.
To
do
a
manual
mount:
mount
/mnt/cdrom
To
do
a
manual
unmount:
umount
/mnt/cdrom
Start
the
install
in
/mnt/cdrom
Examples
For
AIX
To
do
a
manual
mount,
map
the
CD-ROM
device
to
a
directory
if
not
already
done
so,
this
can
be
done
either
through
smit
or
using
following
commands:
%
mkdir
/cdrom
%
/usr/sbin/crfs
-v
cdrfs
-d
/dev/cd0
-m
/cdrom
-p
ro
crfs
appends
the
entry
in
/etc/filesystems
so
you
can
mount
it
with
the
mount
/cdrom
command.
The
entry
in
/etc/filesystems
looks
like:
/cdrom:
dev
=
/dev/cd0
vfs
=
cdrfs
mount
=
false
options
=
ro
account
=
false
To
mount:
mount
/cdrom
6
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
To
unmount:
unmount
/cdrom
Installation
error
messages
and
logs
The
following
tables
describe
the
error
and
message
logs
used
by
the
installation,
upgrade,
and
uninstallation
programs.
If
you
need
help,
contact
the
IBM
Customer
Support
staff
and
send
the
log
file.
(See
Contacting
software
support
on
page
viii.)
Because
entries
are
appended
to
a
log
file
as
the
program
runs,
the
last
entry
in
the
file
often
describes
the
cause
of
an
error.
Table
1.
Installation
and
log
files
Log
file
name
Description
In
an
existing
IBM
WebSphere
Application
Server
installation:
/WebSphere/AppServer/properties/version/log
For
a
default
MS
installation:
/opt/ibm/tivoli/MS/WAS/properties/version/log
IBM
WebSphere
Application
Server
5.0.1
fix
pack
installation
logs.
The
*selective-install.log
file
contains
the
record
of
the
approximately
149
install
steps.
Each
step
in
this
log
file
references
other
log
files
in
the
same
directory.
IBM
Tivoli
Monitoring
for
Transaction
Performance
installs
the
fix
pack
silently,
if
necessary,
during
any
installation.
The
installation
logs
are
located
in
the
common
logging
directory.
The
default
installation
directory
for
any
Web
Transaction
Performance
component
is
as
follows:
Windows
Systems:
%ProgramFiles%\ibm\tivoli\common\BWM\logs
UNIX
Systems:
/usr/ibm/tivoli/common/BWM/logs
Table
2.
Uninstallation
log
files
Log
File
Name
Description
trace-install.log,
trace-install1.log,
trace-install2.log,
trace-install3.log,
trace-install4.log,
trace-install5.log
These
logs
are
rolling
log
files.
When
the
capacity
is
full,
the
logs
rotate
to
record
data.
Logs
are
overwritten
as
the
rolling
process
cycles
through
the
log
files.
The
uninstallation
log
files
are
placed
in
the
following
temporary
directories:
Windows
Systems:
%ProgramFiles%\ibm\tivoli\common\BWM\logs
UNIX
Systems:
/usr/ibm/tivoli/common/BWM/logs
Installation
trace
levels
Trace
information
for
installation
is
written
to
the
trace-install.log
file.
The
installation,
upgrade,
and
uninstallation
programs
place
this
file
in
the
common
logging
directory.
The
log
file
names
follow
the
format
trace-install.log,
trace-install1.log,
trace-install2.log.
By
default,
the
trace
files
roll
when
they
reach
capacity
(10
MB)
with
a
maximum
of
five
existing
files.
This
means
that
after
the
Chapter
2.
Installation
Troubleshooting
7
trace-install.log
file
reaches
a
size
of
10
MB,
the
information
is
copied
from
this
file
into
a
new
file,
trace-install1.log
and
from
there
into
trace-install2.log.
The
trace-install.log,
file
always
contains
the
most
recent
logged
information.
Table
3
describes
the
trace
levels
that
you
can
set
for
installation.
The
trace
levels
are
cumulative
from
the
top
to
the
bottom
of
the
table.
For
example,
if
you
set
the
trace
level
to
INFO,
the
trace-install.log
file
logs
fatal,
error,
and
warning
messages
as
well
as
informational
messages,
but
does
not
log
any
debug
messages.
The
debug
settings
(DEBUG_MIN,
DEBUG_MID,
and
DEBUG_MAX)
are
used
by
developers
and
support
personnel
to
diagnose
software
problems.
DEBUG_MAX
is
the
default
setting
for
the
trace-install.log
file
for
install.
To
set
trace
levels,
use
the
command
option
shown
in
the
left
column
of
the
table
when
starting
an
installation,
upgrade,
or
uninstallation.
For
example,
the
following
command
starts
the
installation
of
the
management
server
on
an
AIX
system
and
sets
the
trace
level
to
DEBUG_MAX:
/cdrom/setup_MS_aix.bin
-W
logSettings.level=DEBUG_MAX
Table
3.
Trace
level
settings
for
trace-install.log
Trace
level
Description
-W
logSettings.level="FATAL"
Logs
fatal
messages,
which
report
errors
from
which
the
program
cannot
recover.
A
fatal
message
is
the
most
severe
message.
-W
logSettings.level="ERROR"
Logs
error
messages,
which
report
serious
failures.
An
error
message
is
less
severe
than
a
fatal
message.
-W
logSettings.level="WARNING"
Log
warning
messages,
which
report
that
abnormal
conditions
have
occurred.
The
condition
might
or
might
not
require
the
user
to
take
action.
-W
logSettings.level="INFO"
Logs
informational
messages,
which
indicate
conditions
that
are
worth
noting
but
that
do
not
require
the
user
to
take
action.
-W
logSettings.level="DEBUG_MIN"
Logs
debug
messages
that
provide
minimal
detail.
DEBUG_MIN
is
appropriate
for
a
software
trace
that
is
always
running.
It
provides
some
information
about
the
program
state
with
minimal
impact
to
performance.
This
is
the
default
setting.
-W
logSettings.level="DEBUG_MID"
Logs
debug
messages
that
provide
a
medium
amount
of
detail.
The
DEBUG_MID
setting
produces
a
level
of
detail
between
DEBUG_MIN
and
DEBUG_MAX.
-W
logSettings.level="DEBUG_MAX"
Logs
debug
messages
that
provide
the
most
detail
about
program
execution.
Use
this
mode
only
during
installation.
During
installation,
performance
is
not
an
issue.
-W
logSettings.level="ALL"
Enables
all
message
logging.
8
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
Installation
command-line
options
This
section
describes
a
set
of
options
that
are
useful
for
troubleshooting
a
failure
or
preventing
problems
before
they
occur.
This
is
the
set
of
options
denoted
in
commands
used
in
this
book
by
the
variable
[cmd_line_option...].
You
can
enter
zero
or
more
of
these
options
on
the
command
line
when
starting
an
installation,
upgrade,
or
uninstallation.
The
command-line
options
are
divided
into
the
following
two
groups:
v
W
options,
which
can
be
run
either
from
the
command
line
by
including
an
option
file
v
is
options,
which
can
be
used
only
on
the
command
line,
not
in
an
option
file
-W
options
You
can
use
the
following
-W
options
during
installation:
-W
logSettings.level="trace_level"
Specifies
a
trace
level
setting
for
the
trace-install.log
file.
This
file
logs
error,
warning,
informational,
and
debug
messages
issued
by
the
installation,
upgrade,
or
uninstallation
program.
See
Table
3
on
page
8
for
a
list
of
trace
level
settings
and
their
descriptions.
-W
logSettings.consoleOut="true
|
false"
Specifies
whether
to
display
messages
issued
by
installation,
upgrade,
or
uninstallation
program
on
the
console.
If
you
use
this
option
with
a
native
launcher,
you
must
also
use
the
-is:javaconsole
option.
-is
options
The
-is
options
have
the
following
format:
-is:option_name
parameter
where
option_name
specifies
the
name
of
the
option
and
parameter
specifies
the
required
parameter,
if
present.
Not
all
is
options
have
parameters.
The
following
list
describes
the
is
options.
-is:tempdir
temp_dir
Specifies
a
directory
for
storing
temporary
files.
If
the
directory
you
specify
does
not
exist,
or
is
not
a
directory,
the
installation,
upgrade,
or
uninstallation
program
writes
temporary
files
to
the
default
temporary
directory
(/tmp
on
UNIX,
%TEMP%
or
%TMP%
on
Windows).
No
error
message
is
issued.
-is:log
log_file_name
Specifies
the
name
of
a
file
for
logging
error
messages
issued
by
the
InstallShield
during
launcher
initialization.
You
can
specify
a
fully
qualified
or
a
relative
path
name.
If
you
specify
only
the
file
name,
the
program
creates
the
file
in
the
current
directory.
This
option
is
especially
useful
for
determining
problems
when
the
installation,
upgrade,
or
uninstallation
program
fails
just
after
starting.
-is:javaconsole
Specifies
that
error
messages
are
to
be
displayed
to
a
console
window
and
logged.
The
displayed
error
messages
are
not
necessarily
the
same
as
the
error
messages
logged
by
the
-is:log
option.
Chapter
2.
Installation
Troubleshooting
9
-is:silent
Suppresses
the
InstallShield
Wizard
message
window
that
is
displayed
at
the
start
of
an
installation,
upgrade,
or
uninstallation.
The
-silent
option,
used
for
silent
installations
or
uninstallations,
does
not
suppress
this
window.
Installation
recovery
procedures
Recovering
from
a
failed
installation,
uninstallation,
or
upgrade
consists
of
the
following
main
steps:
1.
Disable
Global
Security
and
save
the
configuration.
2.
Remove
the
JAAS
Authentication
entry.
3.
Remove
the
JDBC
Provider
entry.
4.
Remove
the
Virtual
Host
entry.
5.
Remove
the
tmtpSharedlib
shared
library.
6.
Remove
the
WebSphere
Variable
entry.
7.
Remove
the
HTTP
Transport
entries
9445
and
9446
and
save
the
configuration.
8.
Delete
the
SSL
settings
with
names
that
start
with
tmtpXXX.
After
you
delete
the
entry,
you
can
save
the
configuration
immediately.
Common
installation
problems
The
following
problems
might
occur
when
you
install
or
uninstall
IBM
Tivoli
Monitoring
for
Transaction
Performance.
Web
Transaction
Performance
supports
the
SOCKS
4
proxy
networking
protocol.
It
supports
implementations
of
SOCKS
5
that
are
compatible
with
SOCKS
4.
If
you
use
the
SOCKS
5
protocol,
use
an
implementation
that
is
compatible
with
SOCKS
4.
On
Windows,
installation
failed
with
the
following
error:
BWMCR8318E
Value
of
TEMP
or
variable
must
not
exceed
20
characters
long.
The
temporary
environment
variable
(TEMP
or
TMP)
path
is
defined
with
more
than
20
characters,
such
as:
C:\Documents
and
Settings\jsmith\Local
Settings\Temp.
This
directory
path
must
be
less
than
20
characters,
such
as
C:\temp,
due
to
WebSphere
limitations.
To
resolve
the
problem,
go
to
Control
Panel
System
Advanced
Environment
Variables
and
edit
the
path
for
the
TEMP
or
TMP
environment
variable
to
be
less
than
20
characters.
You
must
have
a
temp
environment
variable
such
as
TEMP
or
TMP.
If
you
have
both,
the
maximum
characters
for
both
of
them
combined
must
not
exceed
20
characters.
Due
to
an
InstallShield
MultiPlatform
limitation,
the
text
on
some
installation
or
uninstallation
windows
is
truncated
in
languages
other
than
English.
None.
The
STI
Recorder
GUI
is
displayed
in
English
on
computers
where
Windows
systems
are
set
to
a
Spanish
locale
instead
of
the
traditional
or
international
Spanish
(such
as
Ecuadorian
Spanish),
even
if
the
Spanish
language
pack
is
installed.
Add
traditional
Spanish
as
a
supported
locale
using
the
Regional
Settings
or
Regional
Options
selection
from
the
Control
Panel.
The
J2EE
monitoring
component
does
not
support
WebLogic
7.0
Clusters.
Do
not
deploy
the
J2EE
monitoring
component
to
WebLogic
7.0
Clusters.
10
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
Performing
this
deployment
can
result
in
one
of
two
behaviors.
In
one
behavior,
the
cluster
is
detected
and
the
J2EE
monitoring
component
installation
stops.
In
another
behavior,
the
cluster
is
not
detected.
After
you
start
the
installation
of
a
Quality
of
Service
management
agent
from
a
GNOME
terminal
emulator
window
on
a
Red
Hat
Linux
7.2
Japanese
system,
any
characters
displayed
in
the
emulator
window
become
unreadable.
Start
the
installation
from
a
different
kind
of
command
window
if
you
want
to
read
messages
displayed
in
the
window
during
installation.
The
management
server
installation
takes
over
five
minutes
to
copy
files.
This
occurs
when
the
installation
does
not
discover
IBM
WebSphere
Application
Server
or
DB2
on
your
system
and
is
preparing
to
do
an
embedded
installation.
This
behavior
does
not
occur
when
using
the
depot
installation
method.
The
installation
program
attempts
automatically
installs
IBM
WebSphere
Application
Server
and
DB2.
If
the
CD
image
location
for
IBM
WebSphere
Application
Server
is
not
specified
or
discovered,
the
installation
program
prompts
for
the
IBM
WebSphere
Application
Server
CD
to
be
inserted
when
required.
To
do
this,
the
installation
program
must
copy
itself
to
local
temp
disk
space
and
restart
from
there
so
that
you
can
eject
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
CD
and
insert
the
IBM
WebSphere
Application
Server
and
DB2
CD.
However,
if
you
specify
the
location
of
the
IBM
WebSphere
Application
Server
images
either
in
a
local
directory,
on
the
network,
or
in
a
depot
(explained
below),
the
installation
program
skips
the
copying
step
and
uses
those
images
directly
without
prompting
for
a
CD.
Use
the
following
command
line
option
to
specify
the
image
locations
for
the
IBM
WebSphere
Application
Server,
the
IBM
WebSphere
Application
Server
Fix
Pack
5.01,
and
DB2:
-P
msConfig.db2CdromDir=
-P
msConfig.wasCdromDir=
-P
msConfig.wasfp1CdromDir=
For
example,
the
following
command
specifies
the
installation
image
locations
on
a
Windows
system:
setup_MS_w32.exe
-P
msConfig.db2CdromDir=E:\db2_images\8.1\w32-
ix86\ESE\image
-P
msConfig.wasCdromDir=E:\was_images\was5_windows
-P
msConfig.wasfp1CdromDir=E:\was_images\was5fp1_windows
The
following
command
specifies
the
installation
image
locations
on
an
AIX
system:
./setup_MS_aix.bin
-P
msConfig.db2CdromDir=/mnt/db2/8.1/aix5/ese.sbcs
-P
msConfig.wasCdromDir=/mnt/was/was5_aix
-P
msConfig.wasfp1CdromDir=/mnt/was/was5fp1_aix
Alternatively,
you
can
set
up
a
depot.
A
depot
is
a
directory
structure
that
contains
product
images.
For
example,
the
directory
structure
for
a
Windows
system
might
look
like
the
following:
Chapter
2.
Installation
Troubleshooting
11
C:\depot
C:\depot\db2
C:\depot\was5
C:\depot\wasFp1
You
would
then
copy
the
product
images
into
the
corresponding
product
subdirectories
and
copy
the
MS
installation
images
into
the
C:\depot
directory.
To
launch
the
installation,
double-click
the
setup_MS_w32.exe
file.
The
installation
program
performs
required
any
embedded
installations
without
prompting
for
CDs.
The
following
lists
show
the
files
needed
for
the
various
installations.
The
C:\depot
directory
requires
the
following
installation
files:
MS.opt
prereqs.dtd
setup_MS_lin390.cp
MS_db2_embedded_unix.opt
prereqs.xml
setup_MS_sol.bin
MS_db2_embedded_w32.opt
reboot.exe
setup_MS_sol.cp
MsPrereqs.xml
setup_MS.jar
setup_MS_w32.cp
dm_db2_1.ddl
setup_MS_aix.bin
setup_MS_w32.exe
media.inf
setup_MS_aix.cp
startpg.exe
ms.jks
setup_MS_lin.bin
w32util.dll
ms.tar
setup_MS_lin.cp
msg-install.log
setup_MS_lin390.bin
The
C:\depot\db2
directory
requires
the
following
installation
files:
autorun.inf
doc
readme.jp
readme.ru
setup.exe
db2
doc.cmn
readme.kr
readme.tw
db2eseTMTP.rsp
readme.cn
readme.pl
readme.txt
The
C:\depot\was5
directory
requires
the
following
installation
files:
12
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
admin.jar
j2ee.jar
log.jar
utils.jar
bootstrap.jar
jmxc.jar
ras.jar
wasjmx.jar
ffdc.jar
jmxx.jar
sas.jar
wsexception.jar
installService.jar
lmproxy.jar
soap.jar
wssec.jar
The
C:\depot\wasFp1
directory
requires
the
following
installation
files:
autorun.inf
docs
license.txt
nt
readme
readme.html
In
the
C:\depot\wasFp1
directory:
docs
installer.jar
updateSilent.bat.orig
earLauncher
lib
updateWizard.bat
fixpacks
updateSilent.bat
Existing
software
was
not
discovered
during
the
installation
of
IBM
Tivoli
Monitoring
for
Transaction
Performance.
The
installation
program
discovers
existing
software
based
on
the
following
xml
files,
which
define
the
prerequisite
software:
v
MsPrereqs.xml
v
MaPrereqs.xml
v
SnFPrereqs.xml
These
files
are
located
in
the
base
directory
for
that
subproduct
on
the
IBM
Tivoli
Monitoring
for
Transaction
Performance
CDs.
For
example,
here
is
the
segment
for
Solaris
systems
in
the
MsPrereqs.xml:
Checktype="MayExist"
Flag="was_fp1Installed"/>
Checktype="MayExist"
Flag="db2_7Installed"/>
For
the
line
pertaining
to
IBM
WebSphere
Application
Server
discovery,
the
Filename,
if
found,
indicates
the
associated
item
is
installed.
The
flag
was_Installed
is
used
to
indicate
this
is
the
IBM
WebSphere
Application
Server
flag.
If
there
is
a
ContainsString
attribute
(such
as
ContainsString=BASEDIR=),
then
the
file
must
also
contain
this
string
or
the
software
is
considered
to
be
not
installed.
If
the
software
is
installed
but
this
file
is
not
present,
or
if
the
software
is
installed
multiple
times
and
this
file
is
pointing
at
the
wrong
installation,
you
can
create
or
edit
the
MsPrereqs.xml
file
before
installing
IBM
Tivoli
Monitoring
for
Transaction
Performance,
enter
the
string
it
is
searching
for,
and
proceed.
After
the
installation
of
IBM
Tivoli
Monitoring
for
Transaction
Performance
is
complete,
you
can
then
return
the
file
to
its
previous
state.
Here
is
the
file
on
another
system:
bash#
cat
/var/sadm/pkg/WSBAA/pkginfo
#
VPD
created
by
InstallShield
MultiPlatform
Edition
#
Thu
May
22
15:10:43
CDT
2003
ARCH=sparc
BASEDIR=/opt/WebSphere/AppServer
CATEGORY=application
CLASSES=none
DESC=
ISJE_INSTALL_STATUS=3
ISJE_IS_ACTIVE=true
ISJE_IS_PUBLICLY_SHAREABLE=false
ISJE_NAME=IBM
WebSphere
Application
Server
ISJE_PARENTS=WSBAA:5.0.0.0.DSP=:1
ISJE_PRODUCT_NUMBER=5.0.0.0
ISJE_REQUIRED_COUNT=0
ISJE_SOURCES=
ISJE_UID=WSBAA
ISJE_UNINSTALLER="_uninst"
"uninstall.jar"
"uninstall.dat"
""
ISJE_VPD_VERSION=4.5
ISJE_WEB=
NAME=WebSphere
Application
Server
PKG=WSBAA
PKGINST=
WSBAA
VENDOR=
VERSION=5.0.0.0.DSP=
bash#
In
this
case
that
file
must
contain
the
ContainsString
as
well
as
the
base
directory
of
this
IBM
WebSphere
Application
Server
installation.
The
installation
of
IBM
WebSphere
Application
Server
Fix
Pack
1
fails
on
a
UNIX
or
Linux
system
with
the
error
message
BWM83240E.
This
problem
can
be
caused
by
the
presence
of
existing
Java
JDKs
on
the
target
system.
14
IBM
Tivoli
Monitoring
for
Transaction
Performance:
Problem
Determination
Guide
Before
installing
IBM
WebSphere
Application
Server
Fix
Pack
1,
remove
any
existing
JDKs
(except
the
one
located
in
the
IBM
WebSphere
Application
Server
directory)
from
your
system.
Note:
This
applies
only
to
embedd
