Use this topic to enable the trace specification to indicate
tracing at the required level.
About this task
The Java Authorization Contract for
Containers (JACC) for Tivoli® Access Manager provider
messages are logged to the configured trace output location, and messages
are written to standard out
SystemOut.log file. When trace
is enabled, all logging, both trace and messaging, is sent to the
trace.log file.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
What to do next
The trace specification now indicates that tracing is enabled
at the required level. Save the configuration and restart the server
for the changes to take effect.