Logi Info includes the Logi Scheduler, which allows Logi applications to be run by administrators on a scheduled basis. Scheduling features can also be embedded in reports, allowing runtime scheduling by end users.
The following topics discuss the Logi Scheduler:
- Logi Scheduler Terminology
- Deployment for Windows
- Deployment for Java
- Configuring Scheduler Communications
- Schedule Task Databases
- Multiple Scheduler Instances
- Quick and Easy Report Scheduling
About The Logi Scheduler
In simple terms, the Logi Scheduler is a proprietary service that runs "in the background" as either a Windows Service or a Linux/UNIX daemon. It maintains its own database of scheduled events and runs them at the desired times and intervals. The Scheduler service has no user interface of its own, but is instead directed to create, maintain, and delete scheduled events by other applications through an application interface.
This service is configured to start up automatically when its host server is started and therefore runs without user intervention. From a performance perspective, it consumes very few resources on the server and spends most of its time idling.
When the Scheduler "runs" an event from its database, it does so by opening a new web server session and calling a specific task in a Logi Info Processdefinition. That process task can then run reports, send emails, etc. - any of the usual task-driven activities.
The Scheduler service release and its corresponding Logi Info release are
This topic concerns itself primarily with the preliminaries: understanding the Scheduler service and installing it. A sister topic, Using Logi Scheduler, is also available with more detailed information about how to configure the Scheduler and work with it from within a Logi application.
In addition, there are two sample scheduling applications available from DevNet that can be downloaded and examined for a better understanding of the elements that support the Scheduler. One of these, Scheduler Console, in the General category, is designed for administering the Scheduler on your server; this is the primary tool we provide for this purpose. The other sample application is an example of a report that allows end users to schedule reports at runtime.