Overview of Corticon upgrades

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, Corticon Web Console, and Corticon Utilities are setup with the separate installers. Java and an appserver are not included in Corticon download packages. 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.

What changed in 7.3.0

The minor release 7.3 further protects installations from vulnerabilities and adds:

• New version of the Web Console–The Web Console that has been the standard as the Corticon OneWebConsole from 6.3.4 through 7.2 has been upgraded to improve performance and to harden it against vulnerabilities.
  Note: To upgrade from an earlier version, export its Web Console configuration, and then import it into a 7.1.3 instance of the Web Console. The import will overwrite the existing configuration. Do not copy the installed corticon.war file in an attempt an update to a newer version. Use the Web Console's dashboard Administration option to Export Configuration. After installing and configuring the 7.1.3 Web Console, start it, and then choose Import Configuration. Refer to the Corticon Web Console Installation guideCorticon Web Console Installation guide.
• Swagger is no longer supported—The Swagger install bundle and the configuration information have been removed as well as the samples that show use of Swagger.

What changed in 7.2.0

The minor release 7.2 further protects installations from vulnerabilities and adds:

• Web Console stands alone—The version 7.1 of the Web Console provides support for multiple versions of deployed servers. It has its own installation bundle and install doc. As it uses different Java and Tomcat from newer releases, you can longer collocate a server and a Web Console on the same app server. You can however have two app severs and two Javas on one machine to support servers and to support Web Console.
• Swagger is no longer supported—The Swagger install bundle and the configuration information have been removed as well as the samples that show use of Swagger.

What changed in 7.1.1

The service pack release 7.1.1 extends AI development, and provides some customer-requested features, such as a new utility for Custom Reporting, an updated REST Datasource, and improved JSON Support in Tester.