Delivery Deployment¶
Service updates and customizations are applied through deliveries. This process is managed in the Build Place Lifecycle Experience, which is the standard approach.
The delivery is downloaded from the LE portal and placed in the deliveries folder, following the folder structure described in the Windows Management Server documentation.
Ensure the delivery is placed at the correct depth in the path structure so the installer inside each delivery can locate files like 'ifscloud-values.yaml' in the 'ifsroot\config' folder. The installer uses relative paths to locate the configuration files.
All types of deliveries have three steps "apply", "cutover" and "cleanup" each with individual logs. Depending on how a delivery is made the steps will be invoked all at once or as separate manual steps.
Deliveries can be deployed in two ways, offline or online. Online is a licensed option. The offline mode will require the system to be down during the entire time the database code is deployed to the database and all "apply", "cutover" and "cleanup" are run in sequence. In online mode the installation is split into different separate steps "apply", "cutover" and "cleanup". Apply can be done while system is up and running and will deploy all database code and changes in the background into a new Oracle Edition. In the cutover the system will be shutdown and the new oracle code and data changes will quickly be switched to be the active version. In the end of cutover the new version of middle tier will be started and connect to the new version of database code. Last a cleanup is performed while the system is up and running, it will remove obsolete db objects used in the apply step and cleanup objects that is obsolete in the new version of IFS Cloud.
Air gap delivery deployments need some additional steps to be performed on a server with internet access first. The deliveries and corresponding artifacts are then moved into the secure air-gapped network. Find the details in "Air gap Considerations" below.