Directory server, Runtime logs for prerequisites, Websphere application server – IBM 51 User Manual
Page 64: Runtime, Logs, Prerequisites, Websphere, Application, Server
Directory
Server
The
log
files
for
the
IBM
Tivoli
Directory
Server
are:
v
ldap.stderr
v
ldap.stdout
v
ldapinst.log
Runtime
logs
for
prerequisites
For
additional
information
on
errors
that
do
not
pertain
to
Tivoli
Intelligent
Orchestrator,
you
might
want
to
consult
the
error
and
trace
logs
for
the
middleware
prerequisites.
The
names
and
the
locations
of
these
log
files
are
provided
below.
WebSphere
Application
Server
The
runtime
WebSphere
Application
Server
logs
are
located
in
the
%WAS_HOME%\logs
and
the
%WAS_HOME%\logs\server1
directories,
where
%WAS_HOME%
is
the
WebSphere
Application
Server
home
directory.
The
runtime
transaction
logs
for
WebSphere
Application
Server
are
stored
in
the
%WAS_HOME%\tranlog
directory.
The
default
value
for
%WAS_HOME%
is:
Windows
C:\Program
Files\WebSphere\AppServer
AIX
/usr/WebSphere/AppServer
Linux
and
Solaris
/opt/WebSphere/AppServer
Check
the
following
log
files
for
errors:
v
SystemOut.log
v
startServer.log
v
stopServer.log
v
SystemErr.log
SystemOut.log
This
is
the
log
file
for
WebSphere
output.
It
contains
messages
that
are
generated
when
the
applications
running
inside
the
WebSphere
Application
Server
are
being
started
or
stopped.
You
might
want
to
refer
to
this
file
when
WebSphere
does
not
start.
The
log
file
is
located
in
the
%WAS_HOME%\logs\server1
directory
on
Windows
systems
($WAS_HOME/logs/server1
on
UNIX
or
Linux).
After
the
Tivoli
Intelligent
Orchestrator
is
successfully
started,
use
the
tail
-f
SystemOut.log
command
to
monitor
this
log
file
for
any
problems
that
might
occur.
startServer.log
This
is
the
log
file
for
the
startup
of
the
WebSphere
Application
Server,
located
in
the
%WAS_HOME%\logs\server1
directory
on
Windows
systems
($WAS_HOME/logs/server1
on
UNIX
or
Linux).
Look
for
open
for
e-business
for
a
successful
startup
of
the
WebSphere
Application
Server.
stopServer.log
This
is
the
log
file
for
the
shutdown
of
the
WebSphere
Application
Server.
52
Tivoli
Intelligent
Orchestrator
Problem
Determination
and
Troubleshooting
Guide