Logging
All trusted requests (both Trusted and TrustedWithDomain
) can be logged to rolling log files in a directory of your choice.
The current log file is named Trusted.log
. When it reaches the maximum size (size
), it is closed and renamed Trusted
1.log
, and a new Trusted.log
is started. When the number of logs exceeds the maximum (n
), log entries roll over to reuse the oldest log file.
To activate logging, add the following line to the access control file:
<LogService>
-log_dir<logDir>
-log_max_size<size>
-log_max_num<n>
where:
Option |
Description |
|
The directory where the log file is saved. Make sure this directory exists before you activate logging. |
|
The maximum size of the rolling log file in KB. The suffix |
|
The maximum number of rolling log files. |
Example Log File Entries
This is an example log entry for an authorized request:
Tue Dec 31 11:14:13 EST 2002: Trusted operation: userID=HAWK-TRUSTDMN\hawkuser, node=hawkuser-DT:none:default, microagent=COM.TIBCO.hawk.microagent.SysInfo, method= getOperatingSystem.
This is an example of an entry for an unauthorized request:
Tue Dec 31 11:19:54 EST 2002: Trusted operation: userID= HAWK-TRUSTDMN\hawkuser, node=hawkuser-DT:none:default, microagent= COM.TIBCO.hawk.microagent.Repository, method= getRBMap - permission denied.