A Corticon implementation has several dimensions. Here are some general aspects to upgrades:

  • Release: Major, minor, service pack, hotfix—To get the best of Corticon features, install the latest version. All your development installations must be at the same major.minor release. The Corticon Web Console can manage multiple releases where each server has consistent Decision Service versions. More than one major.minor Studio release can co-exist on one machine but you should strive to get upgrades and fallback positions finished, and then uninstall the older version. A patch and a hotfix can always overlay existing installations.
  • Components: Studio, Server, clientApps—Corticon's installers provide the complete Eclipse development environment and the complete deployment environment. Client Applications are provided strictly as samples. Customers are responsible for their apps, which typically do not need upgrades.
    Note: WebConsoleThe Corticon Web Console is a separate installer, and uses specific Java and Tomcat versions. The Web Console and a Server cannot be collocated.
  • Platform: Windows (Java), Windows/IIS(.NET), Linux(Java), AppServer-WAR(Java)—The typical installation is on Windows with the Tomcat appserver. The utilities that transform a Java Server to .NET Server and then deploy to an IIS server are provided. Linux and App Server WAR installations are produced in every release so that they stay in sync with other installations.
  • Eclipse and Java: Provider/version from/to—The Eclipse and Java version/provider are installed with the product. See the Supported platforms page.
  • Deployment strategy:CDD, EDS—While the historic technique was to move all the rule assets to the server for compilation and deployment, due to security considerations, now version 6.x does not support server-side compilation. As such, CDDs are listings of EDS files in contrast with directly deploying an EDS.
  • Type: Web Services, In-Process—Business planning determines which strategy is better. Both are offered and the techniques for successful deployment on either are documented. Note however that strategies for widely dispersed in-process servers can create slowdowns when upgrades are offered.