skip to main content
Corticon Installation Guide : Procedures for upgrading Corticon installations

Try Corticon Now

Procedures for upgrading Corticon installations

Stepping through tasks that optimize upgrades of Corticon Studios and Servers ensures that your files and assets are synchronized with the updated product. These tasks are a checklist of good practices.
If your upgrade was a minimal step forward, such as a patch (such as >, you should read the patch notes to see if there are tasks to consider. For a Service Pack (such as 5.7.0 > 5.7.1), it is more likely that there are changes in the product that you should handle, even though they might not present problems. For a minor release -- especially a big step (such as 5.5.2 > 5.7.1) -- every one of these tasks should be reviewed, considered, and performed.
Note: Do not copy the .war or .ear files from an older version's installation to a new one.
In the order of action:
*Update Studio installations
*Update the Studio's
*Update eclipse.ini and Java
*Update the Studio license file
*Upgrade assets
*Update desktop shortcut
*Repackage Decision Services
*Undeploy the old Decision Services
*Update Corticon Server and Web Console software
*Update the Server license files
*Update the Server's
*Clear browser caches that use the Web Console
*Update IIS servers and set clienttype to IIS
*Deploy regenerated Decision Services
*Stop load balancers and start the new server
*Setting PAS on Windows to run as a Windows Service


Install Studios

See Installing Corticon Studio

Update the Studio's

Compare the files that are currently in use. Any property adjustments you made in the past, if still valid, should be copied into the newer installation. While a minor release installs into a separate location, a service pack overlays an existing installation and does not touch an existing .

Update eclipse.ini and Java

Some Studio installations benefit from tweaking the eclipse.ini, often for Studio memory settings. If you are pointing to your preferred Java, it might not be optimal.

Update the Studio license file

A major release will likely require a new license file while minor releases typically do not. When you are provided a license for Corticon Studioand Server, you receive a JAR file, CcLicense.jar. Save the file on the target machine or at a location that is network-accessible to the installation. In this example, the license file that both Studio and Server will use is placed at C:\licenses.
To update a Studio license:
1. Select the menu command Window > Preferences.
2. Expand the Progress Corticon group. In the License File entry area, enter or browse to the location of the license JAR:
Click Apply, and then click OK.

Upgrade assets

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

Update desktop shortcut

Make changes to your desktop shortcut if you want your new Studio version to run in a different language.

Repackage Decision Services

Use any of the several techniques in Studio to package projects as Decision Services, and then stage them for deployment on the new server installations.

Other considerations

*If you are advancing from 5.5 to 5.7.1, and using EDC Datasource metadata, regenerate the metadata.
*If you are advancing to 5.7.1, Advanced Data Connectors changed dramatically since its introduction in 5.6.1, the way its used in 5.7.0, and the Datasource configuration file in 5.7.1 to support an independent query database.


Undeploy old Decision Services

Undeploy every EDS on the target servers.

Install new Corticon Server and Web Console software

If you are using load balancers to carry the load during upgrade, take one of its peers offline, and stop it. Run the installers, and then start the new Server.
Note: Other application servers - The .ear and .war files can be downloaded in the package. The unpackaged files are typically installed in the Corticon directory [CORTICON_HOME]\Server\Containers\{EAR/WAR}. Refer to the Progress Software web page Progress Corticon 5.7 - Supported Platforms Matrix to review the currently supported UNIX/Linux platforms and brands of Application Servers. Also see the Corticon KnowledgeBase entry Corticon Server 5.X sample EAR/WAR installation for different Application Servers for detailed instructions on configuring Apache Tomcat, JBoss, WebSphere, WebLogic on all supported platforms.

Update Server licenses

The Server requires you to copy the CcLiense.jar file, and then paste it to replace the existing file, as follows:
*Java server license:
*[CORTICON_HOME]\Server\lib\The license used for Server tasks and operations.
*[CORTICON_WORK_DIR]\Server\pas\server\webapps\axis\WEB-INF\libThe license deployed to the runtime server. If you are managing a default Java server (PAS) from the Web Console, you can perform this task through its Editing Server groups and Servers
*When your installation is from the .ear and .war files for deployment onto other supported platforms and application servers, place the license file adjacent to the Corticon JARs.
*.NET server license :
*[CORTICON_HOME]\Server .NET\samples\lib\The license used by the samples.
*[CORTICON_HOME]\Server .NET\webservice\lib\The license propagated to the IIS location by the install utility..
*The IIS location, typically: C:\inetpub\wwwroot\axis\lib\The license at the IIS location. If you are managing a .NET server from the Web Console, you can perform this task through its Editing Server groups and Servers

Update the Server's

As with Studio, compare and update the files on Java and .NET servers with consideration that many properties are effective only on servers.

Clear browser caches that use the Web Console

For administrators that use the Web Console, have them flush their browser caches.

For .NET servers:

*Install to the IIS - Run install.bat to refresh the IIS server's libraries and samples. Answer Y to all the overwrite choices. Then restart the IIS server.
*Set the Client Type - Change the setting in the file that enables the Studio remote tests and server utilities:
For more information, see Setting the Client Type
*Copy the file from the Corticon server root, paste it into the axis folder at the IIS location, and thereafter apply updates to it there.
For more information, see the Corticon Server: Deploying Web Services with .NET

Deploy the fresh Decision Services

Deploy the newly created Decision Services to the new server.

Stop load balancers and start the new server

Use 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.

Setting PAS on Windows to run as a Windows Service

You can run Corticon Server under Progress App Server as a Windows Service by executing:
[SERVER_WORK_DIR]\pas\server\bin>tcman service Corticon register
Note: Specifying the Corticon Server file locations - At startup, the Windows Service creates CcServerSandbox and logs at [HOME]\pas\Server\bin. That might not be what you want. To position those files at their standard location (or at any preferred location):
1. Stop the running Windows Service.
2. Launch the Corticon Command Prompt.
4. Enter:
tomcat8 //US/Corticon ++JvmOptions="-DCORTICON_SETTING=SER"
tomcat8 //US/Corticon ++JvmOptions="-DCORTICON_WORK_DIR=C://Users//xxxxx//Progress//CorticonWork"
5. Restart the service.
An alternate solution is to add lines to the server's file:
For the logpath, you must use forward slashes as the separator.