Corticon 6.3.5

The 6.3.5 service pack includes critical third-party library updates and important defect fixes to ensure a secure, stable, and fully supported environment, while maintaining platform compatibility. See Issues fixed in Corticon 6.3 for details.

Corticon 6.3.4

Corticon 6.3.4 rolls up the various patch releases for 6.3.3 as well as:
  • Updated Web Console—The Web Console for 6.3.4 introduces the OneWebConsole, on par with the 7.1 Web Console, hardened against many CVEs, and offering new features for deployment visibility and management. The updated Web Console can manage deployed servers and their decision services from version 6.3 and version 7.1. Corticon 6.3.4 and bundle the Web Console from Corticon 7.1. To keep documentation streamlined, all Web Console documentation lives in the 7.1 library—no separate “6.3.4” Web Console guide is available. The benefits are:
    • Updated UI with improved behavior and security
    • Ability to manage all 6.3 and later Corticon Servers from one console. Wherever you see “Web Console” in any 7.1 topic, it applies equally to your 6.3 environment.

    For Corticon 7.1 Web Console documentation, see the 7.1 archive.

    For Corticon 6.3.3 Web Console documentation, see the 6.3 archive item for 6.3.3

  • Web Console Configuration Export and Import–The Web Console uses the Corticon 7.1 Web Console providing the ability to export the Web Console configuration and import it into a separate instance is provided for upgrades or rehosting of the Web Console.
    Note: Do not copy the installed corticon.war file in an attempt an update to a newer version. Use the Web Console's dashboard Administration option to Export Configuration, and then import it into the newer Web Console.
  • Log filter changes—A new filter is available, PAYLOAD, that will put the request payload and the response payload in the log. The filter INVOCATION has been dropped.
  • New server property: Turn off disabling of thread underutilization allocation -- A new server property has been added to control how execution threads are allocated when the Corticon Server is underutilized:
     com.corticon.ccserver.allocation.disable.underutilization.algorithm =false
    See Server Execution Properties "Server Execution Properties" in the Server Guide for details.

Corticon 6.3.3

Corticon 6.3.3 rolls up the various patch releases for 6.3.2 as well as:

  • Corticon Server now enforces version check on EDS deployment—When an EDS is deployed, Corticon Server will inspect the EDS to determine which version of Corticon it was generated with. If this version is not the same major.minor version of Corticon Server, the EDS will not be deployed. Examples:
    • - 6.3.0.0 EDS deployed to 6.3.3.0 Corticon Server: Allowed
    • - 6.1.0.0 EDS deployed to 6.3.3.0 Corticon Server: Disallowed

    Enforcing this version check ensures compatibility between the EDS and Corticon Server. The generated EDS code is dependent on internal Corticon Server APIs which may change across major.minor releases. This could result in an EDS failing to execute despite initially reporting successful deployment.

  • Swagger is optional—Corticon Server no longer bundles Swagger for exploring and testing the Corticon Server REST API. Swagger is now optional and can be added to an instance of Corticon Server. See The REST API Swagger documentation for details. The use of Swagger is best limited to development deployments of Corticon Server. It is typically not needed, or wanted, in production deployments.
  • Tomcat 8.5 not supported—Tomcat 8.5 will reach end-of-life in March 2024. Customers are encouraged to update to Tomcat 9.0 to ensure access to Tomcat security updates. Corticon Server bundles Tomcat 9.0

Corticon 6.3.2

Corticon 6.3.2 rolls up the various patch releases for 6.3.1 as well as:
  • Updates the Corticon Web Console's LDAP authentication to support OpenLDAP—The Web Console supports both Microsoft Active Directory and OpenLDAP.
  • Improved runtime performance of rulesheets—Rulesheets containing filters that use entities not also used in a rule condition or action can expect improved runtime performance.
  • Improved decimal precision comparison in rule tests—Previously, for Decimal data types, the output and expected values might not be flagged as different when they in fact are. As an example, the value 111.100002 would not be flagged as different from 111.100001. These values will now be flagged as differences in rule tests.
  • Logging configurations in Web Console for trace logging are disabled—Modified the default logging configurations of the Web Console database to have trace logging disabled. This is a change from the previous configuration, in which trace logging was enabled by default.

Corticon 6.3.1

Corticon 6.3.1 provides additional functionality to 6.3 with:
  • ADC Insert Primary Key handling—When the primary key of an inserted record is generated by the connected database, Corticon retrieves this generated value and adds it to working memory for that Entity. This will allow follow-up database updates on that Entity to occur, and also allows associated Entities that are dependent on that primary key value to be stored as a foreign key value in the associated Entity.

For more information about ADC writes, see How to configure ADC writes. .

Corticon 6.3

Progress® Corticon® 6.3 includes the following changes and new features:

  • Rule trace viewer—Troubleshooting the execution of rules just got easier. When running Ruletests you now have the option to gather rule trace data. Trace data identifies the sequence of rules triggered and the actions performed. When execution of your Ruletest completes, trace data is displayed in the Rule Trace Viewer where you can see each rule triggered, changes to attribute values and associations, and more. From the Rule Trace Viewer you can easily navigate to the Rulesheet for any rule show in the Rule Trace Viewer. This makes it easy for you to quickly make changes to your rules and see the results in your Ruletests. You no longer need to add rule messages on every rule to trace rule execution. See Trace rule execution .
    Note: See how the rule trace view helped in a large project in the blog Fast Rules Diagnostics and Root Cause Analysis with the New Rule Trace Viewer.
  • Simplified JSON metadata requirements—Some users find that their JSON requests have metadata only at the root, expecting that the decision service can infer the metadata for subordinate levels. That tactic is now supported, although the output provides the metadata at all levels. An example is shown in the Web Console Guide at Simplified JSON in requests .
  • Updated REST Connection driver—The Progress DataDirect Autonomous REST Connector driver has been updated and now supports OAuth2 Authentication and POST requests:
    • REST data source support of OAUTH2—Uses authorization tokens to prove an identity without giving away your password. See Authentication on REST Service connections .
    • REST data source support of POST—A POST request does not include parameters as part of the URL, instead the parameters are data in the request document. Selecting Post parameter type changes how the REST connector makes its requests to the endpoint, so any specified URL parameters may be ignored. See Parameters on REST Service connections .
  • Updated bundles for Eclipse, OpenJDK, Tomcat, and .NET proxy—For details, see Corticon Supported Platforms Matrix .
  • Self-registration update in Web Console—When a Corticon Server self-registers with the Web Console, the Web Console now updates any existing registration for the server by updating the IP address of the registered server. Previously, a new registration would be added resulting in the Web Console having server registrations for both the old and new IP addresses. Updating an existing registration better supports deployments where the IP address of a Corticon Server might change on each restart. The Web Console can then provide continuity of trend data across restarts. See Server registration with Web Console .
  • Corticon deployment on Docker—The popular platform for building, sharing and running applications, Docker, now has detailed download and configuration instructions so that you can quickly deploy Corticon Servers onto Docker images. See How to deploy Corticon on Docker .
Note: Cannot install Studio into an existing Eclipse— Corticon Studio ships with Java 11 or higher, which introduces changes in how JAR files are handled: Java no longer supports the direct addition of custom JARs to the classpath as earlier versions did. As a result, the ability to drop extension JARs into the Eclipse plugin folder is no longer functional. The recommended method for adding extension JARs is in an installed Corticon Studio either:
  • For Eclipse tools, choose Help > Install New Software, and then typically choosing tools at https://marketplace.eclipse.org/ .
  • For your extensions, such as extended operators and service callouts, in a Rule Project, choose Properties > Corticon Extensions.