...
The JOC Cockpit Resources / Calendars view has import and export functions to allow reliable Calendar deployment, for example, from a source, such as an Integrations System (Int.) to target, such as a Production System (Prod.).
...
- Export of the Calendar from the Int. JOC Cockpit to the Int. file system, where the Calendar will be saved as a JSON file.
- Transfer of the JSON calendar file to the Production file system.
- Import of the JSON calendar file to the Production JOC Cockpit with automatic integration into the Production JOC Cockpit Daily Plan.
- Manual Updating of the Daily Plan will be Required in particular situations.
Details of the deployment procedure will depend on two factors:
...
- whether a Calendar is to be deployed on the Prod. system for the first time or whether an existing Calendar on the Prod system is to be updated
...
- .
Note that Calendars are always exported with usage and folder information - i.e.:
- With with information about the Orders or stand-alone Jobs which the Calender has been assigned to and the Run-time information (Period and Restrictions).
- With with the Calendar Path parameter ...
.Status colour Yellow title Add Summary
If a Order or stand-alone Job is found on the target system with the same Path parameter (i.e. name and directory) as an Order or standalone Job on the source system which the Calender has been assigned to then the Calendar and Run-time information can be assigned to the Order or stand-alone Job on the target system.
"New" Deployment of a Calendar
Consider the situation where a new Calendar has been tested and is now to be deployed to a production environment. Status
...
.
...
Example Configuration
The following configuration will be used to demonstrate deployment of "new" Calendars:
...