IBM 51 User Manual
Page 26
administrative
console,
security
can
be
disabled
in
this
file
by
changing
the
value
of
the
enabled
parameter
in
the
second
line
from
true
to
false
.
By
default,
<cell>
represents
the
host
name.
Server.xml
This
file
contains
server-specific
configuration
information,
and
is
located
in
the
$WAS_HOME/config/cells/<cell>/nodes/<node>/servers/
server1
directory.
Java.security
This
file
contains
security
properties
used
by
the
java.security
classes.
It
is
located
in
the
$WAS_HOME/java/jre/lib/security
directory.
Sas.client.props
This
file
contains
security
settings
that
indicate
the
Java
Client
how
to
access
secured
applications.
It
is
located
in
the
$WAS_HOME/properties
directory.
4.
Check
the
runtime
WebSphere
Application
Server
log
files
for
errors.
The
logs
are
stored
in
the
following
directory:
v
On
Windows:
%WAS_HOME%\logs\<server-name>
v
On
UNIX:
$WAS_HOME/logs/<server-name>
where
<server-name>
is
by
default
server1
.
The
runtime
WebSphere
Application
Server
log
files
include:
SystemOut.log
This
log
file
contains
messages
generated
when
the
applications
running
inside
the
application
server
are
being
started
or
stopped.
When
startingTivoli
Intelligent
Orchestrator,
use
the
following
command
to
monitor
this
log
file
for
any
problems:
tail
-f
SystemOut.log
SystemErr.log
This
log
file
contains
Java
exceptions
and
stack
traces
caused
by
applications
and
their
applications.
startServer.log
This
log
file
contains
errors
that
occur
during
the
startup
of
the
WebSphere
Application
Server.
Look
for
the
following
output
for
a
successful
startup:
Server
<server-name>
open
for
e-business
.
stopServer.log
This
log
file
contains
errors
that
occur
during
the
shutdown
of
the
WebSphere
Application
Server.
Look
for
the
following
output
for
a
successful
shutdown:
Server
<server-name>
stop
completed
.
5.
Search
the
knowledge
bases
and,
if
necessary,
contact
Support.
For
more
information,
refer
to
Problem
determination
using
SystemOut.log:
The
following
steps
are
required
when
troubleshooting
the
WebSphere
Application
Server
using
SystemOut.log
:
1.
Look
for
any
error
during
the
WebSphere
Application
Server
startup.
v
If
you
see
an
error
before
the
point
where
you
see
...ready
for
e-business
,
check
the
WebSphere
Application
Server
configuration.
14
Tivoli
Intelligent
Orchestrator
Problem
Determination
and
Troubleshooting
Guide