This section summarizes the features that are no longer supported and no longer documented as of Progress® Corticon® 6.0.0:

  • Deployment of Ruleflows - Corticon Server no longer supports deployment of ERF files, only compiled EDS files can be deployed. Previously you could deploy Ruleflows and associated assets to Corticon Server so that the Server would compile the assets into runnable Decision Services. That was a performance hit every time that Decision Service was loaded and could lead to error situations in production if the Decision Service failed to compile. You can generate EDS files with Corticon Studio, Corticon command line utilities, or Corticon ant macros. If deploying ERF files with Corticon Deployment Descriptors (CDD files), you will need to modify these to deploy EDS files. Eliminating ERF deployment helps enforce Continuous Integration/Continuous Deployment (CI/CD) best practices by encouraging the deployment of fully compiled and tested Decision Services. See the topics How to package and deploy Decision Services
  • Corticon Deployment Console - The Corticon Deployment Console bundled with Corticon Server provided a GUI mechanism for creating CDD files, compiling Decision Services, and generating WSDL files for Decision Services. These tasks can each be performed in other ways.
    If you have been using the Deployment Console, its functionality is available as:
    • Command line interface for creating CDD files - The CDD file format is a simple text file manifest describing a Decision Service. The most common practice is to copy a sample CDD file bundled with Corticon, and then make modifications to it in a text editor. The new corticonmanagement command -cdd as described in Create a CDD file enables all the CDD options for a single Decision Service deployment description file in one command.
    • Compile Decision Services - Multiple techniques in the Deployment guide perform compilation:
      • Using Studio to compile and deploy Decision Services
      • Automating packaging and testing of Decision Services
      • Using Server API to compile and deploy Decision Services
    • WSDLs are now generated from the Vocabulary and Ruleflow editors - WSDL is bundled with a Decision Service on compilation. The WSDL for a Decision Service can be accessed via the Corticon Web Console or the Corticon Server REST API. To create WSDL, see Generate service contracts in Corticon Studio .
  • Download of Decision Services - Corticon Studio no longer allows download of Decision Services. As rule assets can no longer be staged for compilation on the server, the best practice for managing your rule assets is to store them from Studio in a source code control system such as Git. Corticon Studio now includes plugins for using Git with your rule projects.
  • SOAP Management API (except execution)- Corticon Studio no longer provides SOAP API to deploy or manage Decision Services. You will need to migrate to using the equivalent REST APIs. Note that the ability to execute a Decision Service with a SOAP request will not be removed – only the management APIs are affected. Corticon Server’s REST APIs are accessible via Swagger on your deployed Corticon Server at http://localhost:8850/axis/swagger (use your appropriate host name and port number ).
  • Java Server Console was previously removed from the Corticon Server install and documentation but was available in the server.zip download. It is no longer available. The Server Console has been replaced with the Corticon Web Console..
  • EAR file deployment - Corticon Server no longer includes the CcServer.ear file as an option for deploying to an application server. Use the Corticon Server axis.war file for deployment to an application server. The CcServer.ear file was not included with the Corticon Server install. It was available only in the server.zip distribution.
  • Enterprise JavaBeans deployment - With the removal of CcServer.ear, Corticon Server no longer provides support for EJB deployment.
  • .NET Business Objects - Corticon no longer supports the use of .NET business objects for executing Decision Services in-process. The use of business objects for runtime execution was primarily done for performance. For performance critical in-process deployments, you should pass JSON to Corticon, not business objects. The performance of JSON is superior to that of business objects. If you have been using .NET business objects, contact your Progress representative for guidance in migration strategies.
  • Option useForQueryService in datasource.xml - The useForQueryService option in a datasource.xml file for identifying the datasource to use for ADC queries has been removed. In its place, add a Query datasource to your Corticon vocabulary to identify the source of ADC and Batch queries. See Define and import queries for ADC
  • EDC database.properties file - The option to specify EDC properties via a database.properties file has been removed. In its place, use a datasource.xml file. The datasource.xml file can define properties for multiple datasources. See Export the Datasource Configuration file for more information.
  • Passing REST API arguments in HTTP Header - The Corticon Server REST API no longer supports passing arguments in the HTTP header. This mechanism did not fully support localization. In its place, pass arguments as query String parameters.
  • Rule Execution Recording Service - The Corticon Server rule execution recording service has been removed. In support of this, the Corticon Studio Project > Create Execution Recording Schema menu option has been removed. Similar functionality can be achieved using Corticon’s ADC. Contact your Progress representative for guidance in migration strategies.
  • WebConsole Monitoring of In-Process Corticon Servers - The Corticon Server no longer provides an option to run an in-process Tomcat server for use when using Corticon in-process. This change results in in-process Corticon Servers not being monitorable with the Corticon Web Console. To monitor an in-process Corticon Server with the Web Console, your container application will need to proxy the Corticon REST API to the Corticon Server. Contact your Progress representative for guidance in migration strategies.
  • ICcServer API Changes - Previously deprecated methods in the ICcServer API have been removed. In addition, methods present for support of the Java Server Console have been removed. Users running Corticon in-process may need to use alternate method signatures with 6.0. See the latest Corticon Server JavaDoc for current API methods.
  • Sample Extended Operators - The SeMath and RandomGenerator extended operators have been removed.