In Linux OS start the task scheduler from the command line by executing the command:
DISPLAY=:987 ./Scheduler [-<Parameters>]
Features of starting task scheduler in Linux OSIn Windows OS start the task scheduler from the command line by executing the command:
Scheduler.exe [-<Parameters>]
Task scheduler of Foresight Analytics Platform can be started manually from the command line with specified parameters.
IMPORTANT. Task scheduler and BI server are recommended to be started on different servers.
The task scheduler with specified parameters is created after creating a configuration file and differs depending on the operation system in use.
In Linux OS start the task scheduler from the command line by executing the command:
DISPLAY=:987 ./Scheduler [-<Parameters>]
In Windows OS start the task scheduler from the command line by executing the command:
Scheduler.exe [-<Parameters>]
IMPORTANT. When starting several task schedulers in different computers or virtual machines make sure that the scheduled tasks container is set up to start only in one task scheduler. If startup settings for several containers are specified in the same task scheduler, these containers should be started in one database.
Task scheduler startup parameters differ depending on the selected operating system.
The following parameters are used in Linux OS:
-d. Indicates whether the file is started as a service. Specify the absolute path to scheduler.xml. For example:
DISPLAY=:987 ./Scheduler -d /opt/foresight/fp10.x-biserver/bin/scheduler.xml
-p. The parameters for setting a custom folder, in which a pid file should be created. Specify the required path to the pid file. If the parameter is not set, it is created in the /var/run folder. The parameter is used only with the -d parameter. For example:
DISPLAY=:987 ./Scheduler -p /var/tmp -d /opt/foresight/fp10.x-biserver/bin/scheduler.xml
-x. Indicates whether scheduler debug info output redirection is disabled. The parameter can be used only with the -d parameter. Debug info will be written by default to the /var/log/syslog file. If the -x parameter is set, the standard output stream is used that is determined by scheduler startup option:
Startup from console - the console is used as the standard output stream.
Startup of the systemd initialization system service - the /var/log/syslog file or the file redetermined using the StandardOutput parameter is used as the standard output stream.
DISPLAY=:987 ./Scheduler -dx /opt/foresight/fp10.x-biserver/bin/scheduler.xml
The following parameters are used in Windows OS:
Instance. Start a task scheduler instance with the specified settings file.
The task scheduler's configuration file is named Scheduler.xml by default. If it is necessary to start the task scheduler with another configuration file, execute the following command:
Scheduler.exe –Instance <name>
where "name" is a configuration file name specified without the extension "xml". For example:
Scheduler.exe -Instance Test
After this command is executed, a task scheduler instance starts that is set up to use the Test.xml configuration file.
Silent. Do not notify about an already started task scheduler with the specified settings.
To start the task scheduler without notifying about an error of an already started task scheduler, use the Silent parameter. For example:
Scheduler.exe -Instance Test -Silent
After this command is executed the scheduler starts using the settings stored in the Test.xml file. If the task scheduler using these settings is already started, a new instance of task scheduler is not started, and error message is not displayed.
MultipleInstances. Disabling the blocking of starting several instances of task scheduler configured to the same configuration file. It is relevant only for server operating systems.
To start the instance of the task scheduler within the current server operating system, if the process has been already started within some other parallel session, use the MultipleInstances parameter. For example:
Scheduler.exe -Instance Test –MultipleInstances
After this command is executed, a task scheduler instance starts that is set up to use the Test.xml configuration file. If this command is executed again, another task scheduler instance can be started.
These parameters can be used together.
See also:
Starting Tasks for Execution | Creating a Configuration File