Previous Topic: Instance SettingsNext Topic: Watchdog Settings

CA RiskMinder UNIX Installation Guide › Configuration Files and Options › INI Files › arcotcommon.ini › Changing Server Startup Logging Parameters

Changing Server Startup Logging Parameters

If you want to change the logging parameters that you see when RiskMinder Server or Case Management Queuing Server starts up, then:

  1. Navigate to the conf directory in ARCOT_HOME.
  2. Open arcotcommon.ini in a text editor of your choice.
  3. (For RiskMinder Server) Add the following section at the end of the file: 
    [arcot/riskfort/startup]
LogFile=
LogFileSize=10485760
BackupLogFileDir=
LogLevel=
LogTimeGMT=0

    The following table explains these parameters.

Parameter

Default

Description

LogFile

 

The file path to the default directory and the file name of the log file.

 

Note: This path is relative to ARCOT_HOME (<install_location>/arcot/).

LogFileSize

10485760

The maximum number of bytes the log file can contain. When a log file reaches this size, a new file is started and the old file is moved to the location specified for BackupLogFileDir.

BackupLogFileDir

 

The location of the directory where backup log files are maintained, after the current file exceeds LogFileSize bytes.

 

Note: This path is relative to ARCOT_HOME (<install_location>/arcot/).

LogLevel

 

The default logging level for the server, unless an override is specified.

 

The possible values are:

  • 0: FATAL
  • 1: WARNING
  • 2: INFO
  • 3: DETAIL

LogTimeGMT

0

The parameter which indicates the time zone of the time stamp in the log files.

 

The possible values are:

  • 0: Local Time
  • 1: GMT
  1. (For Case Management Queuing Server) Add the following section at the end of the file: 
    [arcot/riskfortcasemgmtserver/startup]
LogFile=
LogFileSize=10485760
BackupLogFileDir=
LogLevel=
LogTimeGMT=0

    The table in the previous step explains these parameters.

  2. Set the required values for the parameters that you want to change.
  3. Save and close the file.
  4. Restart RiskMinder Server.
  5. Restart Case Management server.