Scheduler XML Configuration File
The following table defines the Pimsoft.Sigmafine.Scheduler.exe.config configuration file. This file contains the Scheduler general runtime settings that can be edited through a text editor, such as the standard Windows Notepad text editor. The settings in this table are the keys listed inside the \<appSettings> section.
Sigmafine Scheduler XML Configuration file
| Setting | Description |
|---|---|
| AFServer | Name of the AF/Sigmafine Server as registered at AF client side |
| MaxLogFile | The maximum log-file size in Kilobytes.The values must be non-negative integer numbers, greater than 1000. If you are running in debug-trace mode (see Trace item), please specify values greater than 50000. |
| RefreshAF | The Time,,in seconds, Sceduler should wait to refresh the scheduling table.The SF_Scheduler table can be edited while the SF_Scheduler is running, but modifications are taken only every X seconds. This field sets this time-period when refreshing. In order to run properly, please do not specify values lower than 30 seconds. |
| Period | The Number of seconds for threading execution of the analysis. Also referred to as the period of the internal threading system runtime.Please leave the default of 5, unless specified or suggested by a Pimsoft Technical Support Representative. |
| SQLAccessWebApiHost | The URI of the SQL Access RESTful service, according following string: HostName [:IP Port].If the IP Port value is missing, the default https port 443 is used. Whenever this parameter is missing, or it contains an empty host name, Sigmafine Scheduler interprets it as an instruction to integrate the old version of SQL Access according to the next configuration parameter (SQLAccessExe). |
| SQLAccessExe | Complete path for the SQL Access executable.If multiple databases are managed, you will need to configure a set of keys as follows:SQLAccessExe_\<AFDB>Where: \<AFDB> = The name of the AF database from which the SQL Access is configured to publish. |
| AFLogon | Only use this setting if the Scheduler is set to check privileges under SSO/Kerberos deployment scenarios when running.If SSO/Kerberos authentication protocol is enabled, setup this parameter as: DOMAIN\USER\PASSWORDWhen standard NTLM/WIS protocol is used, this setting must be empty. |
| Port | The TCP/IP listening port for Sigmafine Scheduler, often referred to as the listening port for incoming requests.Each instance must have a unique (different) TCP port, otherwise the instances cannot start. |
| Channel | Do not change this value unless Sigmafine Technical Support written indicationThe TCP/IP channel port for the SQL Access Publication Server (i.e., the channel used to listen for SQL Access publication requests). |
| ChannelRecalc | Do not change this value unless Sigmafine Technical Support written indicationThe TCP/IP channel port for the Recalculation Server (i.e., the channel used to listen for Recalculations requests). |
| ChannelExec | Do not change this value unless Sigmafine Technical Support written indicationThe TCP/IP channel port for the Re-Executions Server (i.e., the channel used to listen for Re-Executions requests). |
| InstanceName | The Name of the Sigmafine Scheduler instance used for running multiple instances of the service in parallel. |
| WaitForExit | An Integer value of either 0 or 1:0 instructs Scheduler to run parallel to the SQL ACCESS publications.1 instructs Scheduler to wait for the end of the SQL Access publications. |
| Trace | In set to TRUE, it means to provide the detailed log/tracing feature.If set to FALSE, it means to provide the minimal log/tracing feature (only major errors).CAUTION: Activating this feature causes the creation of a detailed, verbose log that tracks all internal Scheduler operations. If you don't clear out the log often, the file can cause your system to run out of disk space and/or create abnormal file generation inside the Scheduler LOG sub-folder.Each case execution is tracked with a specific external log labeled as:Pimsoft.Sigmafine.Scheduler.Executer.exe.DB.MODEL.ANALYSIS.yyyyMMddHHmmss.logMoreover, Scheduler logs the execution of the case in another separate file for deep debugging of the analysis execution.EXAMPLE:Pimsoft.Sigmafine.Scheduler.Executer.DB.MODEL.AN.20130411231856.log Pimsoft.Sigmafine.Scheduler.Executer.DB.MODEL.AN.20130411231856.log.AFTrace |
Note:
Important Info - Scheduler Configuration Settings file
In case of spaces inside the path, please enclose the full path between double quotes (“”).
EXAMPLE:
“C:\Program Files (x86)\Sigmafine\Scheduler\Pimsoft.Sigmafine.Scheduler.exe”
In case of multiple instances, before starting up the instance, check the configuration file by reviewing the following items (see below). Ensure that different instances do not have the same TCP port and/or the same name, otherwise the instances will not start:
\<add key="Port" value="5470"/>)
\<add key="InstanceName" value="Pimsoft Sigmafine Scheduler"/>
For further details on other application configuration settings and keys, please refers to the Microsoft XML configuration files in the Microsoft .NET Framework documentation.