Feedback
Did this article resolve your question/issue?

   

Article

Upgrading to Corticon 5.7 and above for .NET

« Go Back

Information

 
TitleUpgrading to Corticon 5.7 and above for .NET
URL Nameupgrading-to-corticon-5-7-for-net
Article Number000111960
EnvironmentProduct: Corticon Server for .NET
Version: 5.7.x and above
OS: Windows
Database: N/A
Browser: N/A
Application Server: IIS
Question/Problem Description
What are the steps to upgrade to Corticon Server for .NET  5.7 and above?

Is "update projects" needed for upgrading from Corticon Server from a previous .NET to Corticon Server for .NET 5.7 and above? 

Will any of the existing rule sheets (.ers), test sheets (.ert), vocabulary (.ecore) or ruleflow (.erf) objects need to change (or go through some sort of upgrade) due to the upgrade from a previous Corticon Server for .NET to Corticon Server for .NET 5.7 and above?

Before running the install.bat, do the existing folder contents need to be deleted first?  Should the C:\inetpub\wwwroot\axis directory be completely removed?

How to upgrade Corticon Server for .NET that is being deployed as part of a Web Services application?

 
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Steps to upgrade to Corticon Server for .NET 5.7 and above:

1) Stop IIS

2) Back up the current IIS axis directories to save the config and CDD directories for reference.

3) Delete the current IIS axis directories (e.g. C:\inetpub\wwwroot\axis)

4) Install Corticon Server for .NET 5.7 or above

5) Reference the following for setting up Corticon Server for .NET with IIS: 
IIS 8.0 and 8.5 (Supported with Corticon Server for .NET 5.7 up to 6.1):
Progress Article  Steps to set up IIS 8.0 and 8.5 on Windows Server 2012 R1 and R2 for Corticon .NET Server 5.x (embedded video)
IIS 10 (Supported with Corticon Server for .NET 5.7 and above):
Progress Article Steps to set up IIS 10 on Windows Server 2019,2016 or Windows 10 for Corticon Server for .NET
i.  Execute [CORTICON_HOME(typically C:\Progress\Corticon 6.3)]\Server .NET\IIS\install.bat to copy the Corticon Server files to the IIS application physical path, keeping the default path: C:\inetpub\wwwroot\axis

ii. Change the permissions of the C:\inetpub\wwroot folder and subfolders so that users can read/write to it.

6) Update the evaluation license file with the permanent license:
Progress Article  How to obtain the permanent license file for Corticon Server and Studio and verify that they are applied?
 
8) For Studio 5.7.x, change the setting in the brms.properties file that enables the Corticon Studio remote tests and server utilities:
com.corticon.studio.client.soap.clienttype=IIS
Reference the following Progress Article  Where is the brms.properties file located in Corticon Studio?  for information on the brms.properties file.

9) Add properties from the previous version that have been set at a value other than the default to the properties files located in C:\Inetpub\wwwroot\axis\brms.properties.
For example, if loglevel was modified to ERROR in the previous version's  C:\Inetpub\wwwroot\axis\conf\CcCommon.properties, this will need to be set in the 5.7 and above brms.properties file that the user creates: C:\Inetpub\wwwroot\axis\brms.properties

10) Restart IIS

11) Make sure the .NET v4.5 Classic Application Pool that the axis application is running under is started.

12) Upgrade all the rule assets and test them to ensure they behave as they did in the previous version.
Upgrade Corticon Assets:
Progress Article  Is there a utility to auto upgrade assets when migrating from one version of Corticon to another higher version ? 

13) Compile and Deploy with Corticon Server for .NET 5.7 and above and ensure that the behavior is the same as the previous version
https://docs.progress.com/bundle/corticon-deployment/page/How-to-package-and-deploy-Decision-Services.html?labelkey=product_corticon

14) Ping the Corticon Server to make sure it is up and running properly by using the following URL:
http://localhost/Axis/corticon/server/ping


Steps to upgrade when Corticon Server for .NET 5.7 and above is deployed as part of a Web Services application:

1) Install Studio and the Corticon Server for .NET 5.7 or above.

2) Upgrade the rule assets to 5.7 or above and regenerate the eds files with Corticon 5.7 or above 
Upgrade Corticon Assets:
Progress Article   Is there a utility to auto upgrade assets when migrating from one version of Corticon to another higher version ?

3) Build a new copy of the web service application using the Corticon 5.7 or above files and publish the web service application to IIS

 
Workaround
Notes
References to Other Documentation:
Progress Information Hub > Corticon Installation > How to prepare for a Corticon installation > If you are upgrading Corticon > Procedures for upgrading Corticon installations
https://docs.progress.com/bundle/corticon-install/page/Procedures-for-upgrading-Corticon-installations.html

Progress Article(s):
Corticon 6.x removed/changed features

 
Last Modified Date4/20/2022 7:49 PM
Attachment 
Files
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.