Configuring System Critical Logs

This procedure describes how you manage the process of storing system critical logs in the database using the J2EE Engine Visual Administrator. If the cluster element on which such logs are configured collapses as a result of a critical process, you can then remotely monitor what happened using the logs that were written to the database.

The database is common for all cluster elements, so if it collapses, then no cluster will be available. That is, this type of log helps you to find the critical situations that occurred on an arbitrary cluster element no matter whether it is running or not.

1. Choose Log Manager → Properties tab
2. Select the DatabaseLogs_Enabled property and enter Yes or No to enable or disable the events being stored in the database.

   This property has a global impact, that is, if set to Yes , you can change its value on a log controller level through the Log Configurator Service GUI.

3. Select the DatabaseLogs_InitAttempts property and specify the number of attempts that the system will make to connect to the database.
4. Select the DatabaseLogs_AttemptsTimeout property and specify the timeout between the attempts to connect to the database. The timeout is specified in seconds.
5. Select the DatabaseLogs_Severity property and specify the severity level above or equal to which the logs are written in the database. The available values are - All , Debug , Path , Info , Warning , Error , Fatal , and None .
   Note

   It is not recommended to specify a value different from FATAL .

6. Select the DatabaseLogs_DaysToKeep property and specify the number of days one log record is kept in the database. After the specified time interval the logs are automatically deleted.