Calendar Management - Calendar Deployment

Introduction

The JOC Cockpit Resources / Calendars view has import and export functions to allow reliable Calendar deployment, for example, from an Integrations System (Int.) to a Production System (Prod.).

In general, such a deployment will involve 3 steps:

1. Export of the Calendar from the Int. JOC Cockpit to the Int. file system, where the Calendar will be saved as a JSON file.
2. Transfer of the JSON calendar file to the Production file system.
3. Import of the JSON calendar file to the Production JOC Cockpit with automatic integration into the Production JOC Cockpit Daily Plan.

Details of the deployment procedure will depend on two factors:

1. 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.
2. Whether a Calendar is to be deployed on its own or whether it is to be deployed with the Orders from the Int. system which have been configured to use the Calender.

Note that Calendars are always exported with usage information - i.e. with information about the Orders which the Calender has been assigned to and the Run-time information (Period and Restrictions).

Deployment of a "New" Calendar

Consider the situation where a new Calendar has been tested and is now to be deployed to a production environment.

• The new Calendar can have a
• on the Int. system has the same Path parameter as will be required on the Prod. system.

Deployment of a Calendar Update

Consider the situation where a Calendar is already in use in a production environment and requires to be updated.

A typical scenario would be where the Calender is to be extended for a further year and the holidays for that year added.