Admin Scheduler

The Global Scheduler window allows the Project Administrator to set-up and manages schedule extract commands. It is possible to set repeat schedules that run at key points of the day. Schedules can be set-up to update the parent or child (make changes made in the Master or Extract viewable in the parent or child), or to transfer items to the parent or child (relocate the claim to the child or parent so that it can be modified at the remote location).

Schedules are local to the location where the Project Administrator is configuring the schedules. Therefore a Project Administrator can set-up schedules between itself and any other location.

The Global Scheduler window is used to create new schedules and display, modify and delete existing schedules. From the Admin Tool select Data > Global Scheduler.

Schedules are stored in an SQL Database on an SQL Server, when the Project Administrator clicks on the Global Scheduler menu option a request to the SQL Service is made. If the SQL Service is not running an error dialogue message will be displayed:

Assuming that the Service is running and the Global Schedule has been configured the existing schedules are then populated in the Global Scheduler window.

From the AVEVA Administration main menu bar, select Data > Global Scheduler to display the Global Scheduler window.

The Global Scheduler window is based on a table and allows the Project Administrator to create and modify scheduled extract commands that can be executed on a regular basis.

The schedules table is used to display and modify schedules. Each row on the table represents a (separate) schedule. Each column on the table represents a field that can be set on the schedule.

The columns\schedule fields include: Schedule Name, Location, To, Transfer, Recurrence, Start Time Repeat and Enabled.

The table is populated with existing (previously saved) schedules on opening the Global Scheduler window. Existing schedules are displayed in the grid in chronological order according to their start time. If there are no existing schedules the schedules table is empty.

The Project Administrator can quickly and easily set up schedules. Click + to add a new schedule (will add a new row to grid) or click - to delete existing schedules.

The Schedule Name is automatically populated, but can be changed. The Schedule Names are descriptive only and can be duplicates (since it is used for display purposes only and each schedule has its own internal identifier). For a newly created schedule, the schedule name is set by default to New Schedule. The selection of the Location and the To columns are important to setting up the schedule. It is expected that the Project Administrators will set up the schedule with an idea on what schedule is required, to where and when. Options available for the Location and the To column drop-downs are only populated with options that are available in the project. By default the scheduled Location is set to Required for a new schedule. The Location column drop-down is only populated with locations that share distributed single extract below a master will be available in the Location List. The To option only reflects the Parent or Child if there is a Master or child available remotely. By default the scheduled To option is set to Required for a new schedule.

The Transfer column determines if the schedule should update the remote Master or Child with changes made locally, equivalent of doing an EXTRACT FLUSH or REFRESH (option unchecked) or if it should relocate items so that they can be modified remotely (option checked). The later will change the claim to be located at the remote location.

The Recurrence column allows the Project Administrator to select what days the schedule should run on. Select the drop-down menu to display two columns (Recurs On and Day).

To set the schedule to run on a particular day set the Recur On check box on the same row as the particular day. Setting the schedule to run on a particular day will cause the schedule to run on that day every week at the specified start time.

The schedule can run on one or more days of the week. For each day the schedule is set to run an abbreviation (of the name of that day) is added to the Recurrence cell on main Global Scheduler table. Each abbreviation remains in the cell when the drop down menu is closed. If the schedule is not set to run on at least one day the schedule is invalid and cannot run and a warning symbol is displayed in the (blank) recurrence cell.

To set the schedule to run every day of the week the user can check the check box on the left hand side of the Recurs On header to select all the days.

The Start Time is entered by hand and defines the first time the schedule is run on the days as defined on the Recurrence column. The start time cell is masked and only accepts a 24 hour time (format).

Note:
All schedules will run until midnight.

The Repeat column allows the user to define the time intervals between each execution of the schedules:

The time is the time interval until the next time the schedule should run, so selecting 30 mins will mean that the schedule will run every half an hour from the Start time (assuming that the day matched the recurrence). Selecting Never makes the schedule a one off operation. In this case the schedule will run once, at the start time, on the days defined by the recurrence.

To define which Databases the schedule applies to, the Project Administrator can select from a list.

Click on the hyper link Select in the Databases column to display the Database Configuration window.

The Database Configuration window allows the Project Administrator to add or remove databases in to or out of the schedule as predefined by the Select hyperlink. Databases not in the schedule appear in the left column, whereas databases in the schedule appear in the right. The buttons in the middle allow the Project Administrator to move databases between the Scheduled and non-scheduled boxes.

The Controlled Extract Workflow only supports extract families with a single Extract below a Master. When using the Database Configuration window, only extract hierarchies supporting this are displayed in the available database lists. However, it is possible to create a third extract below a Master or Extract which will invalidate the schedule. As the scheduler maintains an independent list of schedules, this results in an invalid extract hierarchy in the scheduled Extract list. If the user wants to create an extract hierarchy with more than one extract then any Master or Extract databases must be removed from the scheduler.

The Database Configuration window is only populated with extract hierarchies that are applicable to the Location and the To options on the Global Scheduler window. So if Location is set to Cambridge, and To is set to PARENT the Database Configuration window will only display Master databases that have extracts primary at the current location and masters primary at Cambridge.

The de-allocated databases will not be removed from the schedules. The purpose of this allows Project Administrators to do housekeeping operations such as re-config, merge and clear extracts without worrying about having to reset the Master Databases at the satellites. The Project Administrators can bring the Database back to the hub, undertake maintenance, then reallocate the Database back to the satellite.

If the Location is set to Cambridge, but To is set to CHILD the Database Configuration window will only display Extract databases that are primary Cambridge and Masters that are primary at the current location.

Note:
Only available in Model, so only databases that are of type DESI will only be displayed in the Database Configuration window.

The Enable column allows the schedule to be enabled or disabled. Select the check box to allow certain schedules to be disabled if required by the Project Administrator.

Reasons for disabling the schedule:

• Maybe the schedules have been set up, but the location has not been activated yet.

• There are house-keeping operations being undertaken that affect databases at either location, so the Project Administrator wants to temporarily stop schedules from running.

When the Project Administrator has set-up and configured all schedule details the schedules are committed to the scheduler once the Project Administrator clicks Apply (the OK and + button are temporarily disabled and prevents the user from re-sending the same data while the previous action is pending) and OK.

Note:
The Global Scheduler takes time to initiate the call to the Global Daemon, before the issued commands appear on the Transaction window, refer to Viewing Command Transactions for further information.

It is possible for all the schedules to be configured before the Project Administrator clicks OK or Apply, or clicked between schedule configurations. Click OK or Apply will send a request to the Global Manager Service that will store the schedules in a SQL database for the scheduler to activate; this is a client - server request that requires the service to be up. The service will report an error if it is not possible to contact the service, or there is an internal error.

The Global Scheduler window validates input as data is entered and will not let the schedule be created if either the Location or the To option is not set.

Schedules that have been previously stored in the scheduler, but have become invalid due to project topology changes are highlighted. The conflicting cell is highlighted with a cross icon. In the example below the schedule has become invalid because the location Leeds has been deleted. It is safe to have invalid schedules held within the scheduler as these will fail gracefully.

Fields that are not complete are highlighted with warning icons, as below.

It is not possible to navigate away from the row until both the Location and To have been set; however it is possible to delete the row.