IBM Verify Identity Governance operational logs

Operational log files contain information about processing activities. These activities are associated with the communication between the Verify Identity Governance Server and other applications.

The following section describes:

• Message, security, and trace logs. Use these logs to troubleshoot errors that occur during IVIG operations.
• Logging options. You can set logging options for all IVIG logs. You can also set options for each type of logging activity.

Default location of operational logs

The operational log files are in subdirectories of the TIVOLI_COMMON_DIRECTORY/CTGIM directory. The default location of the log files depends on the operating system.

Microsoft Windows systems

C:\Program Files\IBM\tivo..\..\common\CTGIM\logs

UNIX and Linux® systems

/opt/IBM/tivo../../common/CTGIM/logs

You can change the default location of the log files during the initial installation and configuration. After installation and configuration, you can edit the enRoleLogging.properties file to change the location. The default location of the enRoleLogging.properties file depends on the operating system.

Microsoft Windows systems

C:\Program Files\IBM\isim\data

UNIX and Linux systems

/opt/IBM/isim/data

IBM Verify Identity Governance logging properties describes the general logging options and the options for each type of logging activity.

You can configure different options to manage the quantity and size of the log files.

Management of size and number of files

You can configure the size and number of log files in the enRoleLogging.properties file. The handler.file.maxFileSize property changes the size of all files. The handler.file.log_type.maxFiles property sets the number of files that are maintained for each type of log before discarding records.

After a set of log files reaches the specified capacity for a single file, the newest data replaces the oldest log data. To maintain a longer activity history, you can specify the number of multiple log files to keep before data is discarded. The following algorithm manages the number of log files:

1. If the log_type.log file reaches 100 KB, the data is moved to the log_type1.log file.
2. If the size of log_type.log reaches 100 KB again
   • The Data from log_type1.log is moved to log_type2.log
   • The Data from log_type.log is moved to log_type1.log
3. The next time log_type.log reaches a size of 100 KB, step 2 is repeated until the maximum number of specified files is reached. If the maximum file limit is reached before the last set of data is moved, the data from log_typeX.log is discarded.