Scheduler Help 
Scheduler Help
Contents : Show
Pegasus Scheduler requires a number of pre-requisite components to be installed and settings configured on the server before the Scheduler is installed, as follows:
Microsoft SQL Server or SQL Server Express
Microsoft SQL Server or SQL Server Express is required to store the Pegasus Scheduler database. The Scheduler Service needs to connect to the SQL Server to access its database. Additionally, if Opera 3 SQL is used, then the Scheduler Service will need to access the company databases.
SQL Server Management Studio
The required settings depend on whether Pegasus scheduler is using either:
Windows Authentication mode - where the Windows User account is used to connect to SQL Server, or
SQL Server Authentication mode - where a SQL Server login name and password are used to connect to SQL Server.
Windows Authentication mode
The Scheduler Service runs as the Local System account in Microsoft Windows. This Windows account is listed as NT AUTHORITY\SYSTEM in SQL Server. This login must be granted the dbcreator server role. If a standalone SQL server is being used then the SYSTEM account on the Opera 3 server must be added to SQL Server logins. To add a computer you must use a login name of “domain/computer$”, e.g. CORPDOMAIN/SERVER2$.
SQL Server Authentication mode
Do not use the 'sa' Login for the Scheduler as this account has very broad permissions. Add a new Login using SQL Server authentication and grant it the dbcreator Server Role. Password expiration should be turned off.
Opera 3 SQL Databases
If you are running Opera 3 SQL, then the Scheduler Service running on the Opera 3 server will need access to the company databases. Opera 3 SQL company databases are located on the Opera 3 server. The Scheduler Service runs as the Local System account in Windows. This Windows account is listed as NT AUTHORITY\SYSTEM in SQL Server. This Login must be allowed to access the SQL Databases.
Firewall Settings TCP ports
You must consider firewall settings for SQL Server and Scheduler.
TCP ports
Set these ports in the incoming rules:
On the SQL Server allow TCP port 1433 in the incoming rules
On the Scheduler server, allow TCP port 51920 in the incoming rules
On the mail server, allow TCP port 25 in the incoming rules (port 25 is the default - change as required if the mail server uses a different port number). The mail server may need to open up the Simple Mail Transfer Protocol (SMTP) port if it has not previously been used, or if it was previously used, but was restricted to certain machines.
SMTP Email Server
In order to configure the mail server settings in Pegasus Scheduler after the installation, you will first need to find out the appropriate SMTP settings in order to communicate with the mail server. The mail server may need configuring to allow emails to be sent to it from the Scheduler server. Instructions for this vary based on the type and version of the Mail Server software, so we cannot give exact instructions here.
Permissions for the Opera 3 data folder
The Scheduler Service account requires read-write permission for the Opera 3 data folder (the 'Opera 3 Server Dynamic' network share).
The Pegasus Scheduler solution comprises a number of different components that are written using the Microsoft .NET 4 framework and are installed on either the Opera 3 Client or the Opera 3 Server computers.
Component |
Description |
Installed on ... |
|---|---|---|
Task Scheduler Editor |
This is where the tasks are created and updated. |
Opera 3 Client |
Task Schedule Runner |
This refers to the Task Scheduler Editor to see whether tasks need to be run, and updates history files with information about the task. |
Opera 3 Server |
Task Runner |
This component performs the task on the data, for example by running the Update Data Structures (UDS) command. |
Opera 3 Server |
Once a task is set up in the Task Schedule Editor, the following things happen:
A task is also set up in Windows Task Scheduler that includes the day/s and time that the task will be run along with the selected Windows user account.
At the required time Windows Task Scheduler communicates with the Task Schedule Runner.
The Task Schedule Runner then reads the tasks in the Task Schedule Editor.
The Task Schedule Editor communicates with the Task Runner which runs the task and updates the data.
The Scheduler Windows service uses the 'Local System Account' Windows user. This is automatically set for you when Pegasus Scheduler is installed.
Important: Permissions are not set up automatically for you; you need to set them up manually in Windows.
The Local System Account must have necessary permissions to the following:
Full permissions to the network share name on the Opera 3 server called 'O3 Server XXX Dynamic' (where XXX is either VFP or SQL).
Full permissions to the Opera 3 SQL databases (Opera 3 SQL only).
If a repeat invoicing task has been set up from the Repeat Invoice command in the Sales Order Processing or Invoicing applications and it has been set up to print to a specified printer, that printer must have been set up by a Windows user at the Opera 3 server.
Tip: If the Opera 3 data is not located on the Opera 3 server, it may be desirable to run the Scheduler Service as a different Windows account. This can be done by changing the service settings in Computer Management. The account settings for the service will have to be reapplied every time the Scheduler Service is upgraded.
Tip: Checking the installed version number: On the Task Schedule Editor form, click the mouse right-click button and select About. The version and build date are displayed on the form displayed.