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.
Note: Starting with this release, Service Packs and patches will roll up into the latest installer. That means that a downloaded 5.6 installer will install fresh components at the current release level or update existing 5.6 installations with the latest updates.
If you have an existing installation of Corticon products on the target machine, do the following:
For an upgrade of a 5.3.x, 5.4.x, or 5.5.x installation to 5.6.x - If you are upgrading from 5.3, 5.4, or 5.5 installed software on the same machine, 5.6.x 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.
For an upgrade of a 5.2 or earlier version 5 installation to 5.6.x - An installed version of Corticon 5.2 or earlier installed on the target machine must be uninstalled, then the appropriate Corticon 5.6 product installed.
You might want to 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.6.x - An installed version of Corticon 4.3 or earlier installed on the target machine must take an intermediate step of upgrading its assets to at least 5.3, and then uninstalled. To accomplish this, you must 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.6.x where its upgrade utility can bring project assets up to date. You might want to 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, or 5.5.x installation to 5.6.x - If you are upgrading from 5.3, 5.4, or 5.5 installed software on the same machine, 5.6.x 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.