This Corticon upgrade guide describes the preparations and tasks to successfully upgrade an existing deployment of Corticon. Before you start,
  • Always backup all assets and workspaces.
  • If you are unsure how to proceed with an upgrade, consult with Progress Corticon Support or your Progress representative to discuss your migration plan.

Upgrade Considerations

Progress strives to provide backwards compatibility will all new releases but sometimes changes are necessary to reflect new best practices, standards, or capabilities. The probability of non-backwards compatible changes increases the older your current version of Corticon is. When planning a Corticon upgrade, be sure to consider each of the following as part of your upgrade plan:

  • Release—At any time, there are multiple Corticon releases available. These include both LTS (Long Term Support) and non-LTS releases. When planning your upgrade decide if you want to upgrade to an LTS release or if you want access to the latest features available in a non-LTS release. Whichever you choose, be sure to start with the latest update available for that release.
  • Components—Corticon Studio, Corticon Server and Corticon Web Console are provided with the Corticon installation. The Corticon Server and Web Console installation also include a Tomcat distribution which you may be using for deployment. Identify what Corticon components are in use and need to be upgraded.
  • Security—Progress strives to keep Corticon current with all necessary updates to address vulnerabilities reported in third party components. Updating to the most recent release of Corticon will best ensure you have all available security updates. Consult with your IT department to confirm the version of Corticon you are upgrading to meets their mandatory security requirements.
  • Type—Corticon Server may be deployed as a web service, running in an application server, or in-process, running inside a custom application. When deployed as a web service, you need to be aware of any changes to the Corticon REST or SOAP APIs. When deploying as in-process, you need to be aware of any changes to the Corticon Server In-Process API.
  • Clients—When Corticon Server is deployed as a web service, there may be changes to Corticon REST or SOAP APIs which will impact the clients calling Corticon.
  • Platforms—Corticon supports multiple versions of Windows and Linux operating systems, applications servers, databases and Java. The versions you currently use may not be supported by the version of Corticon you are upgrading to. Check the Corticon Supported Platforms Matrix to see if the versions you use are supported by the version you are upgrading to.
  • DevOps—How you build, test and deploy decision services is a critical part of your Corticon deployment. Check to see if any of your current practices need to change as part of your Corticon upgrade or if Corticon has introduced new capabilities which will improve your DevOps practice.
  • Eclipse—Corticon Studio is a set of plug-ins integrated with the Eclipse IDE. The Eclipse version used by Corticon Studio may have changes in the upgrade version of Corticon. If you have added third-party plug-ins to Eclipse, such as for accesses a source control system, check to see if versions of these plug-ins are available for the new version of Eclipse.