Scheduler Settings
The component provides options for scheduled events to occur on the server. The table in the right-hand part of the Administration Console displays in the left column the options and in the right one drop-down lists or entry fields for the settings. In the lower part of the table you find brief descriptions of the options (which are displayed when clicking them).
| Option | Description |
|---|---|
| Activate scheduler * | Activates the scheduler. |
| Scheduled server saving * | The server saves data periodically. |
| First save * | First point in time for data storage. |
| Save interval * | Interval for data storage. |
| Scheduled backup of the server * | Server performs periodical backing up of data. |
| Delete content of backup directory * | Delete content of the backup directory.
Caution: If set to Yes, the content of the backup directory is deleted before each backup.
|
| First backup * | First time to back up.
Apart from the time, you can also enter the value Now; the backup runs some minutes after the start of the server. |
| Backup interval * | Interval to back up. |
| Backup path * | Path in the file system to save the backup.
If Backup path is not specified, the files are copied to the BACKUP directory of the database directory. If Backup path is specified, a directory with the name of the database is created in this path. In this directory the directory BACKUP is created. |
| Backup numbering * | Yes: the suffix nnnn is attached to the backup path to keep multiple backup directories. nnnn is the number stored in Back up next number with leading zeros. |
| Next backup number * | The server increases the backup number after every backup, no matter if the backup operation was scheduled or manually started. |
| Maximum backup number * | If the backup number exceeds the specified maximum backup number, the Next backup number is set to 0. If -1 is set, the backup number is unlimited. |
| Check inactive users * | Checks for inactive logged on users. |
| User timeout * | Allowed idle time for inactive users. |
| Process ALEACOMMAND file * | Checks the ALEACOMMAND file every 5 seconds and performs the commands. |
| Run direct importer * | Checks for the IMPORTSTART file every 5 seconds and performs the import. |
| Export AleaLog to relational DB * | Checks for records in ALEALOG.TXT every 10s and transfers them to a relational DB.
Splashing information in ALEALOG.TXT is not written into the relational database. |
| Specify connection string to relational DB * |
Enter the parameters for the connection string. Default: |
| Table name for single cell changes * |
All changes of single cells are exported from AleaLog into this table of the relational DB. Default: Alealog |
| Table name for operations * |
All operations like splashing are exported from AleaLog into this table of the relational DB. Default: AlealogOperations |
| Overwrite 'Definition of the cubes' * | If set to Yes and Export AleaLog is enabled, cell changes of all cubes are written to AleaLog, regardless of the setting 'Definition of the cubes'. |
| LoadFromSource * | Check for relational jobs regularly |
| LoadFromSource polling interval * | Time interval in seconds to check for relational jobs. The valid range is between 1 and 3600 seconds, default value is 60 seconds. |
| Unload idle database * | Removes cubes and dimensions from memory if the database is idle (no user is connected). The objects are saved if necessary before unloading them from memory. |
| Idle time for database unload | Specifies the idle time (no user is connected) of the database (in minutes) before it is unloaded from memory. |
If you change the settings by modifying the ALEA.INI or DB.INI files, or by using a separate window within the MMC, the resulting changes are visible only if you first click another component and then click the changed component again.