To synchronize your files and assets with the updated product, perform the tasks that optimize upgrades of Corticon Studios and Servers. These tasks are a checklist of good practices.

If your upgrade is:

• Hot fix— Provides fixes to one or more customer reported defects. Hot fixes are provided only to the customer which reported a defect. Hot fixes are inclusive of all prior fixes – it will include all fixes from prior hot fixes. When installing a hotfix, review the readme for the release for a summation of defects which are fixed. Upgrading to a new hotfix should be an easy step with no changes in behavior.

Example: Upgrading from 7.0.0.0 to 7.0.0.1

• Service pack— Rolls up all fixed bugs, and is made available to all customers. When installing a service pack, review the readme for the release for a summation of defects which are fixed. Upgrading to a new service pack should be an easy step with no changes in behavior.

Example: Upgrading from 7.0.0.1 to 7.1.0.0

• Major or minor release—Includes new features and may include changes to existing features and supported platforms. Although Progress prioritizes backwards compatibility, upgrading to a new major or minor release may require additional steps. When installing a major or minor release, review the What’s New guide for the release to understand what has changed. Keeping your installation current with new Corticon release will simplify upgrades – the older the release you are upgrading from, the higher likelihood there will be additional steps required to complete the upgrade.

Example: Upgrading from 5.7 to 7.0

IMPORTANT: Corticon Studio and Corticon Server versions must be consistent throughout your infrastructure.

Note: Do not copy a .war file from an older version installation to a new one.

In the order of action:

ON STUDIO MACHINES

ON SERVER MACHINES

ON STUDIO MACHINES

Install Studio

Note: You can keep an installed prior version of Studio for 90 days. See your EULA for information about the "Replaced Product."
For the updated product, proceed with How to install Corticon Studio.

Update the Studio's brms.properties file

Compare the brms.properties file that is currently in use. If any property adjustments you made in the past are still valid, copy them into the newer installation's brms.properties file. While a minor release installs into a separate location, a service pack overlays an existing installation and does not touch an existing brms.properties file.

For information about the brms.properties, see "Studio Properties and settings" in the Rule Modeling Guide and "Server Properties and settings" in the Corticon Server Guide.

Update eclipse.ini and Java

Some Studio installations benefit from tweaking the eclipse.ini, often for Studio "Increase Corticon Studio memory allocation" in the Corticon Installation Guide. If you are pointing to your preferred Java, it might not be optimal.
Note: Do not copy eclipse.ini from an older release. After you do an install, compare your old file to the new one to determine whether any lines are appropriate to migrate.

Update the Studio license file

A major and minor release requires a new license file. When you are provided a license for Corticon Studio and Server, you receive a JAR file, CcLicense.jar. Save the JAR file named CcLicense.jar, which you receive with the Corticon Studio and Server license, on each target machine. To avoid performance issues, Progress strongly recommends that you do not put your Studio license on a network drive, as that may cause network latency issues in Studio due to the frequent check of this license file when rule assets are edited. In this example, the license file that both Studio and Server use is placed at C:\licenses.
To update a Studio license:
  1. Go to Window > Preferences, and expand the Progress Corticon group.
  2. In the License File field, enter or browse the location of the license JAR:


  3. Click Apply, and then click OK.

Upgrade assets

In Studio, be sure to upgrade all project assets. While you upgrade file by file or project by project, the best way is to advance all the assets you might work with in the current release. Then, it is a good practice to run any Ruletest or unit tests to see that the behaviors are as expected.

Note: If you are using a workspace that was used in a previous installation, you might need to refresh the workspace's links to Welcome screen topics. In Studio, click the Home button to refresh the Welcome links.

Update desktop shortcut

If you want to run your new Studio version in a different language, make changes to your desktop shortcut. In essence you are modifying the desktop shortcut to append -nl and the preferred language to the target, for example, -nl ja. For details and examples, see "Set Studio to run in another language" in the Install Guide.

Repackage Decision Services and their Datasource Configuration file

As you cannot deploy the Decision Services until the Servers and Web Console are updated, choose the option Package and save for later deployment so that they are staged with their freshly generated Datasource Configuration file for deployment on the updated Server and Web Console installations .

ON SERVER MACHINES

Undeploy old Decision Services

Undeploy every decision service on the target Servers that were generated using a prior version.

Install Corticon Web Console software

Run the Server download, and choose only Corticon Web Console if you want it to run its corticon.war on a machine that does not collocate with a Corticon Server's axis.war.

After you install servers, you can have the servers register automatically when you install the Corticon Web Console. The properties and instructions you will see Update the Server's brms.properties.

Install Corticon Servers

Note: If you are using load balancers to carry the load during upgrade, take one of its peers offline, and then stop it.
  • Default Tomcat server—When you install Corticon Server or Corticon Web Console, a Tomcat server is installed that is ready to use.
  • .NET server—The Corticon Server installer option for .NET provides the install.bat script that will setup the Corticon application and the axis folder on the .NET IIS server.
    Note: If you are upgrading into an existing Corticon .NET installation, you must stop and remove the current installation:
    1. Backup the axis and Corticon directories under c:/inetpub/wwwroot.
    2. If you have a .NET license, put it aside as it will get added in to the new installation.
    3. Stop the IIS, then click on Sites\Default Web Site, and then right click on any Applications and choose Remove.
    4. In the File Explorer, delete the folders C:\inetpub\wwwroot\axis and C:\inetpub\wwwroot\Corticon.
    5. Close the IIS Manager, and then relaunch it.
    To install Corticon for .NET to the IIS server:
    1. Launch C:\Progress\Corticon 7.x\Server .NET\IIS\install.bat as Administrator. Press Enter to run the script.
    2. After installation, immediately add your authorized .NET license file, CcLicense.jar, to the IIS server's C:/inetpub/wwwroot/Corticon/lib. Without this file the Corticon .NET server will not run.
    3. Start the IIS Manager, and then do the following steps:
      1. Expand Sites and Default Web Site.
      2. Right-click on axis, and then choose Convert to Application. In the dialog, confirm or select Application pool .NET v.4.5 Classic, and then click OK
      3. Right-click on Corticon, and then choose Edit Permissions. In the dialog, click the Security tab. Click Edit, and the choose IIS_IUSRS. Click the Allow - Full control box, as shown:


        Click Apply, then OK to both dialogs.
    4. In a browser, enter http://localhost/axis/corticon/server/ping. The uptime is displayed.
    Note: Multiple applications on one IIS Server—You can have several distinct applications on an IIS server that have separate logs and assets. See Set up Corticon Server for .NET for multiple applications. .

    For more information on Corticon .NET server installation as well .NET deployment security, see "Web services on .NET" in the Corticon Web Services Guide.

  • Other application servers—The Corticon Server .war files can be downloaded in the PROGRESS_CORTICON_7.x_SERVER.zip package. The axis.war or corticon.war file is deployed to the typical deployment directory of the application server. For example:
    • For downloaded Tomcat: [TOMCAT_HOME]\webapps
    • For the default Tomcat in the Corticon installer: [CORTICON_HOME]\Server\tomcat\webapps.
    Note: To review the currently supported UNIX/Linux platforms and brands of application servers, refer to Corticon Supported Platforms Matrix For detailed instructions on configuring Corticon Server on all supported platforms, see the Corticon KnowledgeBase entry Corticon Server WAR installation for different Application Servers .

Update Server licenses

The Server requires you to copy the CcLicense.jar file and then paste it to replace the existing file, as follows:

  • Java Server license:
    • [CORTICON_SERVER_HOME]\Server\lib\—used by sample applications and the Corticon Management Utility.
    • [CORTICON_SERVER_HOME]\Server\tomcat\webapps\corticon\WEB-INF\lib—deployed to the runtime Server. If you are managing a default Java Server from the Corticon Web Console, you can perform this task by referring to "Edit Server groups and Servers" in the Corticon Web Console Guide
    • When you install from the .war file for deployment onto other supported platforms and application servers, place the license file adjacent to the Corticon JARs.
  • .NET Server license:
    Note: You must have a license that enables .NET Server to work with Corticon. See Knowledge Base article: Corticon 6 licensing. The license in the installation where you setup the .NET server does not copy its license file [CORTICON_HOME]\Server .NET\ThirdParty\lib\ to the IIS location.
    Once you have a Corticon 7.0 Server license that supports .NET Server issued to you by Progress, copy the file to C:\inetpub\wwwroot\Corticon\lib\. If you are managing a .NET Server from the Corticon Web Console, you can perform this task by referring to "Edit Server groups and Servers" in the Web Console Guide.

Update the Server's brms.properties

As with Studio, compare and update and tune the brms.properties files on each Java and .NET Server, considering that many properties are effective only on Servers. For more information see "Server properties and settings" in the Server Guide
Note: On .NET Servers, you can copy the brms.properties file from the Corticon Server root, paste it in the Corticon folder in the IIS location, and thereafter apply updates to it.

Corticon Server registration in Corticon Web Console—When new servers want to be managed in the Web Console, you can add properties to the server's brms.properties file that will connect and authenticate on the Web Console, and even put the server into a specified group so that the server automatically gets decision services deployed in the group. For details, see "Server registration with Web Console" in the Server Guide

Clear browser caches that use the Corticon Web Console

For administrators who use the Corticon Web Console, clear the browser caches.

Deploy the fresh Decision Services

Deploy the newly created Decision Services to the new Server. When using CDDs, be aware that you might have two types of data access configuration files. The legacy format used a .properties file while new format is a datasources.xml file.
  • Where you have a legacy .properties file with EDC, use CDD Property : 
    PROPERTY_DATABASE_ACCESS_PROPERTIES_PATH
  • Where you are have a new style .xml file, use CDD Property : 
    PROPERTY_DATASOURCE_CONFIG_FILE_PATH

Stop load balancers and start the new Server

Use Corticon Web Console (or other techniques) to deploy the upgraded EDS files and license to the new Server. Bring the other load balancers down, and then expose the upgraded Server to carry the load. Uninstall old Servers, and then upgrade and provision to be peers.