| | |
Keyword | Description | Default value |
---|
AccessPort | Network port used. | 4900 |
ActivityStatisticMaxFileSize | Maximum size of the file for activity statistics (MB). This value must be greater than or equal to 1 otherwise no modification is performed. The statistics are saved and reinitialized. | |
ActivityStatisticPath | Path of files for activity statistics. The path is created on the server if it does not exist. The statistics are saved and reinitialized. | |
ActivityStatisticPeriod | Period (in seconds) between each backup of values for the different activity counters. This value must be greater than or equal to 1 otherwise no modification is performed. The statistics are saved and reinitialized. | |
CacheMaxUnusedFiles | Maximum number of unused HFSQL tables that are stored in cache (which means opened) on the server. When this number is reached, the less recent unused table is automatically deleted from the cache. | |
CacheFilesPrefetch | Configures the automatic fill for the cache of tables. The possible values are: - 1: Automatic fill enabled.
- 0: Automatic fill disabled.
| 0, automatic fill of table caches disabled |
DBRootPath | Path of directory containing all databases (which means the data files of different HFSQL Client/Server applications). To specify the directory of Manta service, simply use "%%EXE%%". | "%%EXE%%DB" ("DB" subdirectory of directory of Manta service) |
DaemonUser Linux only | User name that will be used by the server. | "root" |
JNLBackupRootPath | Path of backup directory for the logs. This path is automatically created if it does not exist when restarting the server. | "__JNLBackup" subdirectory of directory containing all the data files |
JNLRootPath | Path of the directory containing all the logs of different HFSQL Client/Server applications (history of write operations performed in the HFSQL files). All the logs will be found in the "__JNL" subdirectory of specified directory. For example, if the specified directory is "C:\Mydir", the logs will be found in the "C:\MyDir\__JNL" directory. We advise you to modify the default path of logs for security reasons. Indeed, if a technical problem occurs on the hard disk containing the data, you will be able to replay the log (saved on another disk) from a backup. To specify the directory of Manta service, simply use "%%EXE%%". | "__JNL" subdirectory of directory containing all data files |
KeepAliveInterval | Maximum time (in seconds) after which, if no communication is established between the server and the client, the server will check the presence of client. | 30 minutes |
KeepAliveTimeOut | Maximum timeout (in seconds) for the server when checking the presence of client. If the client is not found at the end of this timeout, the client is automatically disconnected. | 2 minutes |
KeySearch | Enable the search for keys. The possible values are: - 0: Automatic search for inactive keys,
- 1: Automatic search for active keys.
| 0, automatic search for keys is disabled. |
LoadCoeffCall | Global coefficient for the number of client calls. This value (included between -100 and 100) increases or reduces the coefficient applied to the counter for the client calls to the server.The coefficients are used to modify the importance of each counter in the formula for calculating the load generated by a user on the server. A value equal to 1, 0 or -1 does not modify the coefficient. A value greater than 100 is equivalent to 100. A value less than -100 is equivalent to -100. | |
LoadCoeffDisk | Global coefficient for the number of bytes read or written on disk. This value (included between -100 and 100) increases or reduces the coefficient applied to the counter for the bytes read or written on disk by the server. The coefficients are used to modify the importance of each counter in the formula for calculating the load generated by a user on the server. A value equal to 1, 0 or -1 does not modify the coefficient. A value greater than 100 is equivalent to 100. A value less than -100 is equivalent to -100. | |
LoadCoeffDiskAccess | Global coefficient for the number of accesses to the disk. This value (included between -100 and 100) increases or reduces the coefficient applied to the counter for the number of accesses to the disk. The coefficients are used to modify the importance of each counter in the formula for calculating the load generated by a user on the server. A value equal to 1, 0 or -1 does not modify the coefficient. A value greater than 100 is equivalent to 100. A value less than -100 is equivalent to -100. | |
LoadCoeffRecv | Global coefficient for the number of bytes received on the network. This value (included between -100 and 100) increases or reduces the coefficient applied to the counter for the bytes received by the server. The coefficients are used to modify the importance of each counter in the formula for calculating the load generated by a user on the server. A value equal to 1, 0 or -1 does not modify the coefficient. A value greater than 100 is equivalent to 100. A value less than -100 is equivalent to -100. | |
LoadCoeffSend | Global coefficient for the number of bytes sent over the network. This value (included between -100 and 100) increases or reduces the coefficient applied to the counter for the bytes sent by the server. The coefficients are used to modify the importance of each counter in the formula for calculating the load generated by a user on the server. A value equal to 1, 0 or -1 does not modify the coefficient. A value greater than 100 is equivalent to 100. A value less than -100 is equivalent to -100. | |
LoadEnable | Indicates whether the load balancing is enabled (True) or not (False) | |
LoadMaxWait | Maximum time (in ms) during which a request to the server can be temporarily stopped by the system for load balancing before it is processed. | |
LogConnection | Used to add information to the system log files whenever a client connects to the server. This keyword can be set to 0 (no addition) or 1 (addition allowed). | 0 (no addition) |
MaximumConnectionsNumber | Maximum number of connections allowed per application. This number is determined by the number of applications (processes) with at least one non-super-user connection on the server. For example: - an application that has opened a single connection in super-user mode counts as zero.
- an application that has opened a single connection with a normal user counts as 1.
- an application that has opened two connections of a normal user counts as 1.
- an application that has opened connections as super-user and normal user counts as 1.
If the value of this keyword is 0, there is no limit. | 0, no limit. |
MoreThan2GB | Indicates whether the system files support more than 2 GB. This keyword can be set to 0 (No) or 1 (Yes). | 0 (no) |
NdxCacheSize | Size of the index cache (MB). This size must be greater than 1. Remark: on a 32-bit server, this parameter cannot exceed 1 GB. | |
ServerLogLevels | Defines the elements that must be found in the log file. The possible parameters are "WL" and "PARAM", separated by a comma: - "WL": the calls to the server will be included in the log file.
- "PARAM": the parameters of the calls will be included in the log file.
| No log file will be created |
ServerLogPath | Location of the audit log files of the server (set of operations requested by the client computers to the server). The path is created on the server if it does not exist. | "%%EXE%%\Logs" ("Logs" subdirectory of directory of Manta service) |
ServerLogMaxSize | Maximum size of a log file (in MB). This size must be greater than 1. | 20 MB |
TmpPath | Path of temporary directory. This directory can be used to create temporary files when reindexing large data files for example. | |
WindowsFileCacheSize | Configures the management of Windows disk caches. The possible values are: - -1 for a size that is automatically calculated,
- 0 for an unlimited cache size,
- a positive value is used to define a custom cache size.
Remark: The standard management of Windows disk caches in 64-bit mode (independently from HFSQL) can create memory saturation. This option is used to customize the management of memory caches. | -1 |
WLDebugPort | Port used to debug the stored procedures and the Client/Server triggers. | 27281 |