Configuration Overview

Some of the configuration of the WebScheduler is made by editing text based configuration files. A user must not be logged into the WebScheduler whilst changes are being made to these files. Some of the files have an XML structure but they can all be edited with a simple text editor such as Notepad.

c:\inetpub\<SV Website>\WebScheduler\Web.config

Settings specific to the appearance of the WebScheduler web portal. For example first day of the week.

c:\inetpub\<SV Website>\ScheduleData\App_Data\SchedulesAccess.dat

Allocation of WebScheduler rights to PcVue Users.

c:\inetpub\<SV Website>\ScheduleData\BIN\ScheduleData.Drivers.CronDat.dll.config

Configuration required to use PcVue built-in Scheduler.

Where <SV Website> is the name corresponding to the IIS web site you have deployed with the Web Deployment Console.

The Web Scheduler functionality changed substantially with version 11.0 of PcVue.

• Prior to version 11.0, the Web Scheduler was able to manage and run its own Schedules.
• From version 11.0, onwards the Web Scheduler is purely a tool for managing PcVue built-in schedules and those found in BACnet Schedule and Calendar objects.

Changes to the configuration of BACnet Schedules, Calendars and Enumerated Associated Labels in version 11.2 of PcVue.

• Prior to version 11.2, configuration was by editing the file Schedules.dat.
• From version 11.2 onwards, Schedules.dat is no longer used. BACnet Schedules, Calendars and Enumerated Associated Labels are configured using the Application Explorer.

How Web Scheduler user access is controlled:

• The WebScheduler controls user access to BACnet Schedule and Calendar objects based on "Timetables" privileges as defined in the connected user's profile. The file SchedulesAccess.dat is ignored.

• The WebScheduler controls user access to built-in Cron scheduler based on privileges defined in the file SchedulesAccess.dat.