Types of CDA Upgrades

In Place Upgrade

This section describes the process to follow if you want to install a new version of your CDA system directly over the existing version (minor version upgrade).

Requirements

Done	Condition
	No new infrastructure is required. A Single Instance, Active-Active or Active-Passive setup can be used. See: Installation Scenarios for CDA

Before you Start

Done	Task
	Send an e-mail to the relevant teams with the following information: Upgrade window

Upgrade Process

1. Stop the system/remove it from the load balancer. Ensure that no system is running at this point.
2. Perform a backup of the system: database and file system.
3. Upgrade the Release Automation and Automation Engine databases.
4. Upgrade core components:
   1. Automation Engine on existing server; including utilities, database, Automation Engine, Service Manager, Service Manager dialog and CDA plug-in.
   2. Automic Web Interface on new server.
   3. Release Automation on new server.
5. Upgrade DB structures: DBLoad (AE), Data Migrator (CDA).
6. Start the upgraded system and check the log files.
7. Validate the new Automation Engine with the upgraded database.
8. Validate the new Release Automation with the upgraded new database.
9. Install the new AWI Plug-ins (Plugin Manager, Action Builder, Analytics)
10. Install the new CDA Action Packs (includes custom types).
11. Manually migrate objects that cannot be upgraded/migrated automatically.
12. Verify defined CDA entities, properties and deployment workflows.
13. Add the system back to the load balancer – system is running at this point.
14. If applicable perform the binary installation process for all remaining instances: remove from load balancer, install binaries and add to load balancer.
15. (Optionally) upgrade deployment nodes/agents.

Upgrade – Parallel Upgrade

This section describes the process to follow if you want to upgrade your CDA system and keep the old version until you are confident with the new version installed (major version upgrade).

Requirements

Done	Condition
	New infrastructure required. Single Instance, Active-Active or Active-Passive setup. Legacy system will run during upgrade process to keep deployments running. See: Installation Scenarios for CDA

Before you Start

Done	Task
	Send an e-mail to the relevant teams with the following information: Code Freeze Window

Upgrade Process

1. The system does not need to be stopped. However, a code freeze must be set in the legacy system during the upgrade process.
2. Perform a backup of the system: database and file system.
3. Copy the current databases to a new database.
4. Install components:
   1. Automation Engine on new server; including utilities, database, Automation Engine, Service Manager, Service Manager dialog and User Interface.
   2. Automic Web Interface on new server.
   3. Release Automation on new server.
5. Upgrade DB structures: DBLoad (AE), Data Migrator (CDA).
6. Validate the new Automation Engine with the upgraded database.
7. Validate the new Release Automation with the upgraded new database.
8. Install the new AWI Plug-ins (Plugin Manager, Action Builder, Analytics).
9. Upgrade/Install CDA Action Packs (including custom types).
10. Manually migrate objects that cannot be upgraded/migrated automatically.
11. Verify defined CDA entities, properties and deployment workflows.
12. Finish the upgrade. Developers can start developing in the new system.
13. If applicable perform the binary installation process for all remaining instances: remove from load balancer, install binaries and add to load balancer.
14. Optionally, upgrade the deployment nodes.

Parallel Upgrade (Multi Instance)

This section describes the process to follow if you want to upgrade your multi instance CDA system and keep the old version until you are confident with the new version installed (major version upgrade).

Requirements

Done	Condition
	No new infrastructure required. Active-Active or Active-Passive setup required. One instance of legacy system will keep running during upgrade process to keep deployments running. See: Installation Scenarios for CDA

Before you Start

Done	Task
	Send an e-mail to the relevant teams with the following information: Code Freeze Window

Upgrade Process

1. The system does not need to be stopped. However, one instance will be removed from the load balancer. Also a code freeze is needed in the legacy system during the upgrade process
2. Perform a backup of the system: database and file system.
3. Copy the current databases to a new database.
4. Upgrade the Release Automation and Automation Engine databases of the removed instance.
5. Upgrade Components:
   1. Automation Engine on new server; including utilities, database, Automation Engine, Service Manager, Service Manager Dialog and CDA plug-in.
   2. Continuous Delivery Automation on a new server.
   3. Automic Web Interface on new server.
6. Upgrade DB structures: DBLoad (AE), Data Migrator (CDA).
7. Validate the new Automation Engine instance with the upgraded database.
8. Validate the new Release Automation instance with the upgraded new database.
9. Install the new AWI Plug-ins (Plugin Manager, Action Builder, Analytics)
10. Install new CDA Action Packs (including custom types).
11. Manually migrate objects that cannot be upgraded/migrated automatically.
12. Verify defined CDA entities, properties and deployment workflows.
13. Start the system/ add the upgraded instance back to the load balancer. Developers can start developing in the new system.
14. Perform the binary installation process for all remaining instances: remove from load balancer, install binaries and add to load balancer.
15. Upgrade deployment nodes (if requested).