Deploy a delivery in online mode¶
An online delivery is deployed into IFS Cloud using the IFS Cloud Installer. The code that is deployed online needs to be online compliant, and a feature activation is required.
Start the IFS Cloud Installer from within the delivery. Note that the IFS Cloud Installer installs parts of a delivery in different steps.
Read and understand the offline delivery mode first, as the following descriptions will be more brief (e.g., all commands are available in Linux).
Online deliveries can be partly managed by the installer, or more manually for greater control if a delivery DevOps pipeline is managing the deliveries. For example, the DB installer steps can be run on the database server to slightly enhance deployment speed. If the actions dbinstallall or dbinstaller and mtinstaller are omitted, the installer will orchestrate both middle-tier and database actions.
Note there is some disk storage considerations to understand associated with online deliveries. Read about it here.
These steps need to be performed in sequence to do a full online delivery.
Apply¶
The apply step can be targeted at different database schemas:
The above implies action=dbinstallall , which includes ICAM schema. Alternatively run only the IFS application schema with action=dbinstaller:
This will deploy all IFS Application database code into a running system. When finished, it will continue to update new or changed data rows to the new version's data structure. A client banner will indicate that installation is active, and parts of the application will be restricted.
The Apply step must be completed before proceeding.
A detailed description of which database objects are deployed during the apply step can be found here.
Precutover1¶
This will prevent new background jobs from starting and set a client banner saying background jobs are postponed until after cutover. More about background job handling can be found here.
Precutover2¶
This will prevent all deferred jobs from starting and set a client banner indicating that the system will soon restart.
Cutover¶
The same can be done manually with:
CMD> .\mtctl.cmd maintenance --mode on -n <namespace>
CMD> .\mtctl.cmd stop -n <namespace>
CMD> .\mtctl.cmd initwait -n <namespace>
CMD> .\installer.cmd --set action=mtinstaller
CMD> .\installer.cmd --set action=dbinstaller --set deployStep=cutover
CMD> .\mtctl.cmd initnowait -n <namespace>
CMD> .\mtctl.cmd maintenance --mode off -n <namespace>
Note: This is an example. If ICAM or other database schemas are used, more DB actions may be required.
During cutover, the middle tier will be stopped and a new version of the middle tier will be initiated but not yet started. Then the database will switch to the new version. Finally, the prepared middle tier connects to the database and fully starts up. All banners will be removed from clients.
Note: Maintenance mode must always be managed manually if used.
Cleanup¶
This will remove obsolete installer objects used during apply, as well as application objects that are obsolete in the newly deployed version.