Difference between revisions of "Running the Scheduling Service in non-Service mode"
(Created page with "The XLCubed Scheduling Service can be run in non-service mode if necessary. This can be helpful when you need to run schedules for multiple websites, or where i...") |
(→See Also: branched scheduling for file-based and sql repositories) |
||
| Line 7: | Line 7: | ||
==See Also== | ==See Also== | ||
| − | * [[Scheduling]] | + | * [[Scheduling with the File-based Repository]] |
| + | * [[Scheduling with the SQL Repository]] | ||
* [[Scheduling Installation]] | * [[Scheduling Installation]] | ||
| + | |||
| + | [[Category:Scheduling]] | ||
Revision as of 12:54, 11 November 2015
The XLCubed Scheduling Service can be run in non-service mode if necessary. This can be helpful when you need to run schedules for multiple websites, or where it better suits your infrastructure. The schedules can be sent manually or timed using Windows Task Scheduler or similar.
After setting up the scheduler in the normal way (see this page for more instructions), you will need to run the executable with a special command-line parameter in order to check for new schedules to run:
C:\Inetpub\wwwroot\XLCubedWeb\Scheduler\XLCubed.Scheduling.Service.exe /RUNPENDING
Note that as with the standard Scheduling Service, the user running the schedules must have sufficient permissions to all the relevant folders, databases and cubes.
