Existing Corticon users advancing to this release will want to know whether their existing products can co-exist with the newer version, as well as any strategies for perpetuating the assets created in their current version.
If you have an existing installation of Corticon products on the target machine, backup all assets and workspaces, and then do the following:
For an upgrade of a 5.3.x, 5.4.x, 5.5.x, or 5.6.x installation to 5.7 - If you are upgrading from 5.3, 5.4, 5.5, or 5.6 installed software on the same machine, 5.7 will install to new location and run independent of the other releases. You must manage any port overloads that might result from running both versions. If you have a load balancing architecture, traffic can be redirected when a new Server version is installed next to a previous version. This architectural setup will incur no down time. A general recommendation should be to leave the previous version untouched until the new version is installed. It is good practice to backup all workspaces before proceeding.
The topic Procedures for upgrading Corticon installations presents a checklist sequence of tips and techniques that will ensure stable, current functionality in upgraded Studios and Servers.
For an upgrade of a 5.2 or earlier version 5 installation to 5.7 - An installed version of Corticon 5.2 or earlier installed on the target machine must be uninstalled, then the appropriate Corticon 5.7 product installed.
We recommend that you consult with Progress Corticon Support or your Progress representative to discuss your migration strategies for existing assets before you take action.
For an upgrade of a 4.3 or earlier installation to 5.7 - Download and install Corticon Studio 5.3.0 or 5.4.0, and then perform the procedures in its Corticon Migration Guide. Once completed, uninstall the 4.3 installation, and install 5.7 where its upgrade utility can bring project assets up to date. We recommend that you consult with Progress Corticon Support or your Progress representative to discuss your migration strategies for existing assets before you take action.
For an upgrade of a 5.3.x, 5.4.x, 5.5.x, or 5.6.x installation to 5.7 - If you are upgrading from 5.3, 5.4, 5.5, or 5.6 installed software on the same machine, 5.7 will install to new location and run independent of the other releases. You must manage any port overloads that might result from running both versions. If you have a load balancing architecture, traffic can be redirected when a new Server version is installed next to a previous version. This architectural setup will incur no down time. A general recommendation should be to leave the previous version untouched until the new version is installed. It is good practice to backup all workspaces before proceeding.