Chapter 6. Auditing and troubleshooting 221
the installation of these servers. During the installation of the Tivoli Access
Manager servers, the installation logs capture all messages for that specific
installation. When using the installation wizard, each server has its own log file.
When using a native installation, the installation uses its
operating-system-specific logs.
For diagnostics, you define which message events and which trace events to
capture. These events can help you troubleshoot problems. To configure
diagnostic events, you define statements in the server-specific routing files. Each
server has an associated routing file. The statements in these routing files are for
both message events and trace events. You define the statements for message
events by severity level. You define the statements for trace events by trace level
and optionally by component. This guide contains information about the
message and trace events.
6.3.1 Routing files
Routing files are ASCII files that you can use to customize the logging of
message and trace events for C-language-based servers, daemons, and other
C language programs and applications. The contents of routing files allow you to
control the following aspects of event logging:
򐂰 Whether to enable logging for specific event classes
򐂰 Where to direct the output for each event class
򐂰 How many log files to use for each event class
򐂰 How large each log file can be for each event class
Every Access Manager component has its own name for the routing file, and all
routing files are placed by default under:
<TAM_install_root>/etc/routing
Format of routing files
Each routing file contains entries that control the logging of message events and
trace events. However, the format of these entries differs by event type.
򐂰 Message events
severity:destination:location [[;destination:location]...]
[;GOESTO:{other_severity | other_component}]
򐂰 Trace events
component:subcomponent.level[[,subcomponent.level]...]
:destination:location [[;destination:location]...] [;GOESTO:{other_severity
| other_component}]
222 Certification Study Guide: IBM Tivoli Access Manager for e-business 6.0
The parameters in these entries have the following meanings:
component:subcomponent.level[[,subcomponent.level]...]
Specifies the component, subcomponents, and reporting levels of trace events to
log. For trace events only.
򐂰 For the component portion, you can specify an asterisk (*) to log trace data for
all components.
򐂰 For the subcomponent portion, you can specify an asterisk (*) to log trace
data for all subcomponents of the specified component.
򐂰 For the level portion, specify the reporting level to log. This value is a number
between 1 and 9. A level of 1 indicates the least amount of details, and a level
of 9 indicates the greatest amount of details.
destination
Specifies where to log the events. For each destination, you need to specify a
location. When specifying multiple destination-location pairs, separate each pair
with a semicolon (;). The following destinations are valid:
DISCARD Discards the events.
FILE Writes the events as ASCII text in the current code page
and locale to the specified location. When using this
destination, you must specify a location for the file.
Optionally, you can follow the FILE destination by a period
and two numbers that are separated by a period (for
example, FILE.10.100). The first value indicates the
number of files to use. The second value indicates the
number of events each file can contain. If you do not
specify these values, there is only one log file that grows
without limit. The average size of an ASCII event is 200
bytes. Because the maximum size of a log file is 2 GB, the
maximum number of events should be limited to
approximately 10,000,000 events.
STDERR Writes the events as ASCII text in the current code page
and locale to the standard error device.
STDOUT Writes the events as ASCII text in the current code page
and locale to the standard output device.
TEXTFILE Same a FILE.
UTF8FILE It has similar behavior to FILE, but it writes the events as
UTF-8 text to the specified location. The average size of a
UTF-8 event is also 200 bytes. When the operating
system does not use a UTF-8 code page, the conversion
to UTF-8 can result in data loss. When data loss occurs,

Get Certification Study Guide: IBM Tivoli Access Manager for e-business 6.0 now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.