IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

The
FILE
syntax
for
the
NOTICE
message
controls
log
roll
over
and
file
recycling:
FILE.max_files.max_records
The
max_files
value
specifies
the
number
of
files
that
are
used.
The
max_records
value
specifies
the
maximum
number
of
entries
per
file.
In
the
default
example
above,
FILE.10.100
means
there
are
10
files
created,
each
with
a
maximum
of
100
entries.
The
files
are
named:
notice.log.1
notice.log.2
.
.
.
notice.log.10
The
messages
″wrap
around″
to
the
first
file
after
the
last
file
has
reached
its
limit
or
when
the
server
is
stopped
and
restarted.
When
a
log
file
is
reused,
the
existing
records
are
written
over
(erased).
In
some
cases,
when
files
are
created
in
the
background
by
WebSEAL,
the
files
can
be
owned
by
root.
To
ensure
that
WebSEAL
can
write
messages
to
the
these
log
files,
you
can
optionally
specify
file
permissions,
owner
and
group.
In
the
following
example,
the
optional
arguments
that
accomplish
this
are
″:666:ivmgr:ivmgr″:
ERROR:STDERR:-;FILE:/var/pdweb/log/msg_error.log:666:ivmgr:ivmgr
Note:
For
more
information
on
routing
file
configuration
options,
review
the
routing
file
template
that
is
distributed
with
WebSEAL.
For
more
information
on
Tivoli
Access
Manager
support
for
serviceability
messages,
see
the
IBM
Tivoli
Access
Manager
for
e-business
Problem
Determination
Guide.
Serviceability
messages
in
UTF-8
format
WebSEAL
produces
serviceability
messages
using
UTF-8
encoding.
When
the
operating
system
uses
a
non-UTF-8
local
code
page,
WebSEAL
automatically
converts
serviceability
messages
to
a
data
format
to
match
the
non-UTF-8
local
code
page.
In
some
cases,
the
conversion
from
UTF-8
to
non-UTF-8
encoding
can
result
in
data
loss.
For
this
reason,
it
is
recommended
that
the
WebSEAL
process
run
in
a
locale
environment
that
uses
UTF-8
encoded
code
pages.
It
is
possible
to
obtain
UTF-8
logs
when
running
in
a
non-UTF-8
locale.
Use
the
UTF8FILE
type
in
the
routing
file.
For
example,
ERROR:UTF8FILE:/var/pdweb/log/msg__error.log
For
more
information,
see
the
routing
file
template
that
is
distributed
with
WebSEAL:
Note
that
when
data
loss
occurs,
the
routing
file
entry
contains
a
series
of
question
marks
(????)
at
the
location
where
data
conversion
was
problematic.
For
more
information,
see
“Multi-locale
support
with
UTF-8”
on
page
44.
Chapter
4.
Serviceability
and
logging
97