more quick actions
minimize quick actions
12.0
1
Posts
1
Users
0
Likes
28
Views
Topic starter
Hi,
Now than we are 2 months away from the v12 general availability, this post is probably the last in the series...
One change that is worth being aware of in v12 is related to setting up the WebScheduler for built-in Cron timetables.
Up until now, the server component behind the WebScheduler (the ScheduleData server) needed to access the Cron.dat configuration file directly via the filesystem. Because the ScheduleData server is run on the Web server computer, this direct access to a PcVue configuration file was preventing us from cleanly separating the web back end and the web server. In v12, no choice, it was a strategic goal to make that segmentation possible.
So we did it.
As of v12, the WebScheduler gets built-in Cron timetables through the Property server, the interface (on the web back end side) used by all of our web services to browse, retrieve or write PcVue items (variables, alarms, historical data, BACnet Schedule & Calendar...).
As a consequence:
- You no longer need to change the ACL of the project so that the IIS users can access the Cron.dat file
- You no longer need to manually set the filepath of the Cron.dat in the WebScheduler's Cron driver config file.
You can also simplify the script we used to give to customers. But do not forget that, upon changes, the Cron.dat still need to be distributed across stations (if need be). This is another story, for a next version...
Regards
Posted : 14/06/2019 7:01 pm