Did this article resolve your question/issue?



Everything needed to know about upgrading to Corticon 6.x

« Go Back


TitleEverything needed to know about upgrading to Corticon 6.x
URL Nameeverything-needed-to-know-about-upgrading-to-corticon-6-x
Article Number000203645
EnvironmentProduct: Corticon
Version: 6.x
OS: All supported platforms
Database: All supported databases
Browser: N/A
Application Server: All supported application servers
Question/Problem Description

1) What is the latest production version of Corticon in use?
2) Can existing licenses be used with the new version?
3) How can the setup file/installation be obtained on the ESD download site for the new version?
4) Where is the installation guide for the new version which includes the software/hardware requirements and steps for installation/configuration?
5) What instructions can be used to install the Corticon EAR\WAR file to a java application server?
6) What is the difference between corticon.war and axis.war?
7) Does both the axis.war and corticon.war files need to be deployed to the application server or does only the EAR file need to be deployed in Corticon 6.x?
8) To complete the Corticon application setup, do additional Corticon Server components need to be installed along with axis.war and corticon.war files?
9) If Corticon Server components are installed to a different directory than the application server where folder structure and permissions are different on the machine, will there be any conflicts/issues?
10) For the Corticon Server deployed to an application server, is the install different for stand-alone environments vs clustered environments?
11) Are there different installation steps for a previous version of Corticon versus the 6.x version?  Are there any changes?
12) How can a Decision Service WSDL be viewed in the Corticon 6.x Web Console?
13) Can a meeting be set up while installing Corticon Server components?.

Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Release Availability
  • To determine the latest GA release of Corticon, reference the following: Corticon Release Availability and Retirement Schedule
  • From the available releases in the reference above, it can be determined which releases are Long Term Support (LTS). LTS releases provide the stability of a long-term supported release by including updates/Service Packs that contain cumulative bug fixes. There will be no new features in a Service Pack/Update of an LTS release. It will only contain bug fixes, similar to a fix pack.
  • If a release is a non-LTS release (faster-moving but shorter-lived feature releases for more agility), there will be no Updates/Service Packs for the release and only hot fixes will be available. When a new major release comes out after the non-LTS release, it will be required to upgrade to the new release to receive any new bug fixes.
  • Reference the following for more information about Long Term Support (LTS): Changes to the Corticon Life Cycle Policy
Release Platform Support Release Download License Usage
  • If using Corticon Server for .NET 6.x, a new .NET license will need to be obtained and installed. This new .NET license can be downloaded from the ESD Download site once the Corticon Server for .NET 6.x release is requested and enabled on ESD. Reference the following for more information: Corticon 6.0 and above licensing
  • For Corticon Server for Java 6.x, if currently under maintenance, an existing license can be used or a new license can be downloaded from the ESD Download Site once the 6.x release is enabled on ESD.
  • Reference the following for more information about Corticon Licensing and how to install it: Everything needed to know about Corticon Licensing
Installation and Configuration
Steps for Upgrading Additional information about Installing to a Java Application Server
  • EAR file deployment has been removed in Corticon 6.x.  Therefore, a user only has the war file web service deployment as an option. Reference, Corticon 6.x removed/changed features.
  • When installing to an application server, the axis.war is the Corticon Server web service deployment, and the corticon.war is the Web Console web service deployment.
    • The axis.war file will need to be deployed as this is the Corticon Server.
    • The corticon.war file is the Web Console and it is up to the user whether they would like to use it and, therefore, deploy it to the application server or install it with the Corticon install wizard.
Corticon Server Configuration
  • A user can specify a user-defined Corticon Work Directory for Corticon by setting the CORTICON_WORK_DIR property as a JVM option.
    • For application server deployments, refer to the application server's documentation for how to set JVM options.
    • The CORTICON_WORK_DIR defaults to the application server home directory.
    • If installed using the Corticon installation wizard, the CORTICON_WORK_DIR is installed by default to  C:/users/<install user>/Progress/CorticonWork_<version> 
  • A user can also create a [CORTICON_WORK_DIR]\ file with the following properties to specify a user-defined CcServerSandbox, log files, CDD directory respectfully:
Testing installation
  • Once Corticon is installed, a user can use the following to determine the uptime/get Server Properties of the Server: http://localhost:8850/axis/corticon/server/ping
    If a user is able to get a response from the references above, they can determine if the server is up and running properly.
Rule Compilation and Decision Service Deployment Below are some of the options that can be used to compile/deploy Decision Services. The following can be referenced for adding custom extension JARs or Business Objects during compilation/deployment:  Web Console Management and Monitoring

Corticon Server and Decision Service API Management

Clustering and Load Balancing

  • Reference the application server's documentation in order to determine how to configure a cluster.
  • The Web Console may have limitations with clustering/load balancing. It has an automatic refresh which may render a connection to another server in the cluster causing the login screen to be reloaded after previously logging in. It is not recommended to add the Web Console to a cluster as it should not be needed. A single Web Console instance can be used to manage several Corticon Servers.
  • A generic best practices guide is not available for load balancing and clustering. This is because the choice of clustering or not, using a load balancing or not depends on many factors like size of rules, data, number of decision services, hardware available, number of requests, hardware available (CPU's and RAM ), acceptable response time for a request, etc.
  • For clustering and load balancing requirements specific to a use case and environment, a user must involve Professional Services (a paid engagement). Reference the following for more information about Professional Services: When and how to contact Progress | Corticon professional services team?
Removed/Changed in Corticon 6.x  Assistance while installing Corticon 6.x
  • Support is available to assist with any specific install or upgrade issues/questions. However, it is out-of-scope for support to be present assisting during the entire upgrade. It is recommended to engage Professional Services (When and how to contact Progress | Corticon professional services team?) if someone is needed to be present during the upgrade process.
Last Modified Date12/20/2021 9:58 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.