Task Autorun with PAAS
Automatic execution of tasks with PAAS is done for tasks added to Task Autorun in the Administration Panel.
In tasks for execution with PAAS, there must not be any opening of modular forms and dialogues. Processes need to be written for autorun.
 |
Only tasks defined for Autorun with PAAS are executed. |
|
Tasks to run external applications are not executed.
Tasks with the settings ‘At startup’ are not executed.
|
|
Decisions that cannot be processed by automatic procedures can be dealt with by Workflows. |
PAAS links to all PANTHEON databases on the server and queries for tasks with the time scheduled for execution. When finding such a task, PAAS runs PANTHEON that links to the database and executes the task.
After finished execution, PAAS logs the user out of PANTHEON and, without login, keeps the program open for a certain time, waiting for the next claim for task execution. After a certain time, PANTHEON is closed.
This is how tasks are executed without any user intervention.
Pantheon Automation Server - starting check for specific DB at specific time is tied to Autorun feature of Pantheon and Automation Server. At the moment, autorun part of automation server waits for Pantheon support for SQL Server imersonate feature.
Regarding Pantheon Automation Server - starting check for specific DB at specific time PAAS itself works like this:
- PAAS connects directly to SQL Server
- It lists all Pantheon databases (or a subset listed in PAAS.ini)
- It creates separate green thread for every Autorun table found on server
- Tables are checked at regular intervals ("short pooll" method) separately in its own thread
- When time comes for autorun task to run - Pantheon is started
- Autorun task is executed by Pantheon
Pantheon stays active in memory for timeout period (set in PAAS.ini, deault 60min) and waits to run other tasks.
Example:
We have DB1, DB2, DB3; all databases have 10min repeating tasks.
On startup, PAAS will connect to SQL Server and create 3 green threads.
- If all three tasks are run on same time: Three Pantheon instances are created to run 3 tasks
- If one task runs - One Pantheon is started to run one task. Then second task comes for run:
- if Panthon is done with first task - same Pantheon is used to run second task
- If Pantheon is stil busy with first task - another Pantheon instance is created for second task
Related topics:
| Only tasks defined for Autorun with PAAS are executed. |