This article describes the installation steps of ORIGAM Scheduler and its configuration options.
Installation
Simplified installation
Starting with version 2025.8, it is possible to install the scheduler via a Docker container with ORIGAM Server. Simply run the container with the ContainerMode=scheduler environment variable, and the scheduler will run instead of the server. The default value is ContainerMode=server, but with the change described above, it is possible to run the scheduler.
Legacy installation
Use sc.exe utility (see http://support.microsoft.com/kb/251192) to install the OrigamScheduler.exe as a Windows service.
Example
sc create "[ServiceName]" binPath="[PathToServiceDirectory]\OrigamScheduler.exe"
On newer Windows servers add a space after the equal sign to make it work
Example
sc create "[ServiceName]" binPath= "[PathToServiceDirectory]\OrigamScheduler.exe"
| [ServiceName] | Name of your service, e.g. “ORIGAM Scheduler (Production)” |
| binPath | Path to your ORIGAM application folder which includes OrigamScheduler.exe. |
Configuration
It is possible to install several schedulers, each of which will process only a subset of schedules. This way you can scale to multiple servers (or server cores since the schedules are processed in a single thread).
| OrigamSettings/SchedulerFilter | Here you can enter the name of the model folder of Business Logic/Schedules. The scheduler will then process only schedules located in this folder. |
Note
The Scheduler of version 2025.3 and later is a net8.0 application. That means that you can configure it with the standard dotnet config file appsettings.json or env variables. Don’t do it, the only thing read from appsettings.json is the logging level setup and if configured there it will partially override the settings in log4net.config (where you should configure the logging).