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: These messages are sent
to CTRACE. CTRACE can write them to a CTRACE dataset, memory buffer,
and/or the SYSPRINT data set for the region's started task.
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 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.