Mechanisms for controlling trace logs
There are different trace log techniques used, depending on which component is being logged. Tracing can be controlled using the following mechanisms:
- routing file
- Control tracing of the policy server, authorization server, WebSEAL, and runtime components. An affected component must be stopped and restarted for modifications to the routing file to take effect.
- Java properties file
- Control tracing of the IBM Security Verify Access Runtime for Java components.
- trace command
- The server task trace command can be used to dynamically control trace operations for the authorization server and WebSEAL components. This command can also be used to control trace operations for custom C applications that were developed by using the ISAM authorization C APIs.
Parent topic: Trace event logs