Configure Log Files Utility (ConfigureLog.exe)

The Configure Log Files utility allows you to configure logging at the server level to capture details of deployment, database reorganization, and application transactions. The log types include AB Suite Runtime System.log, Deployment.log, DBReorg.log, and RuntimeAPI log.

This utility is automatically installed with Agile Business Suite Runtime and is located in the AB Suite 7.0 installation directory. You can invoke the utility from the command line to configure or read the log information.

Note: By default, a local administrator can use ConfigureLog.exe. For non-administrative users to access this utility, the users must be a member of the "Runtime Administrators" COM+ role of Runtime Manager application or member of the "AB Suite Runtime Administrators" user group.

To run ConfigureLog.exe from a command line:

Point to the bottom-left corner of the screen to enable the Start icon, right-click Start, and then click Run.
Type cmd in the Run dialog box and press Enter to open a Command Prompt.
In the command prompt, change the working directory to the /bin64 folder of the AB Suite 7.0 installation directory.
```
cd C:\Program Files\Unisys\AB Suite 7.0\Bin64
```
Type "ConfigureLog.exe /?". This displays the complete usage of the utility.

The syntax of Configure Log Files command line utility is

ConfigureLog /C [<SYSTEM|DBREORG|DEPLOYMENT|RUNTIMEAPI>] [/E <true|false>]
[/LL <Debug|Info|Warning|Error>] [/L <location>] [/S <size>]
[/N <number>] [/?]

Parameters

Argument	Description
/C [<SYSTEM\|DBREORG\|DEPLOYMENT\| RUNTIMEAPI>]	Specifies configuring the log information at the server level for the following log types: SYSTEM: The System log file applies to all runtime components. You can specify this option to configure or read the log information of an application transaction. DBREORG: The DBReorg log file is used each time an application is redeployed and the database is reorganized. You can specify this option to configure or read the log error messages during database reorganization. DEPLOYMENT: The Deployment log file is used each time deployment packages are deployed either automatically as part of the build process from Developer, or manually on the Runtime server. RUNTIMEAPI: The RuntimeAPI log file is used to capture the log details of Runtime API operations. By default, the file is stored within the Data folder. *Notes:* This argument is mandatory. Apart from "/C" with option, if you do not pass any other arguments, it displays and lists the information from the log file. This information is read-only. For example: To display the log information that was set previously for the DBReorg log file, type ConfigureLog.exe /C DBREORG
/E <true\|false>	You can set this argument to "true" to enable logging, and vice versa. *Note:* If you set this argument to false, the log level changes to "Disable" and no other log information changes. For example: To enable the DBReorg log file, type ConfigureLog.exe /C DBREORG /E true
/LL Error\|Warning\|Info\|Debug	Specifies the level of logging information to be logged. By default, the log level is Error . The other log levels are Warning, Information, and Debug. For example: To set the log level to "Information" for an enabled log , type ConfigureLog.exe /C SYSTEM /LL INFO
/L <location>	Specifies the location path of the log file. You should specify the absolute file path. The default location is the Data\public\log folder. *Notes:* If you provide empty quotes, "", the location that is already set is considered. If you provide an invalid path, the error message "Unable to create directory. Enter a valid directory name." appears. For example: To modify only the location parameter of the DBReorg log file, type ConfigureLog.exe /C DBREORG /L c:\a1
/S <Size>	Specifies the maximum size of the log file in KB. This parameter value sets the value of the File Size. *Notes:* The default file size displayed is the previous value available from the server. Although, you specify a value for File Size via this parameter, it is modified only at the next start of the server. This specification is applicable only for the "System" log file type. Ensure that you enter a numeric value that is greater than zero and within the range of 1-65,535. For example: To modify only the File Size parameter of System log file, type ConfigureLog.exe /C SYSTEM /S 120
/N <number>	Specifies the number of backup files that can be created once the log file has reached its maximum. *Note:* Ensure that you enter a numeric value that is greater than zero and within the range of 1-65,535. For example: To modify only the number of backups of the Deployment log file, type ConfigureLog.exe /C DEPLOYMENT /N 6
/?	Displays the command line syntax and arguments of the utility. If specified, a usage message appears, and the utility exits without starting the configuring process.

Troubleshooting Error Messages

If you provide incorrect option for an argument, an error message specifying that the argument is invalid along with the argument appears, along with the usage of the utility, for reference.
If you pass an incorrect argument, an error message specifying that the input is invalid appears, along with the argument and the usage of the utility, for reference.
If you do not pass any arguments to the command line utility, an error message specifying that the mandatory argument "/C" is missing appears, along with the usage of the utility, for reference.
If you pass arguments values that are the same as the existing values, the error message "No configuration changes have been made" appears.
If you pass an incorrect value for an argument, an error message specifying that the argument is invalid appears along with the argument and the usage of the utility, for reference
If you try to pass any argument when logging is disabled, a warning message specifying that logging is disabled and suggestion to enable logging to change the property values appears.
If you pass any argument after logging is disabled, a warning message specifying that logging is disabled and suggestion to enable log to configure log files appears.
If you pass valid parameters to run the utility, the message "Completed successfully" appears.
If you pass duplicate arguments, the error message "Encountered duplicate arguments. Please address the duplicates before proceeding" appears.

Examples

The following command configures log information of an application transaction with the log file size as "1000" and number of backup files as "100" for an "Error" log level.
```
ConfigureLog.exe /C System /E true /LL ERROR /L c:\temp /S 1000 /N 100
```
The following command displays the log information of an application transaction that was set in the previous transaction.
```
ConfigureLog.exe /C System
```