Can the version of Corticon components differ for integration and deployment of Decision Services? - Progress Community

Loading

Skip to Main Content

Can the version of Corticon components differ for integration and deployment of Decision Services?

Can the version of Corticon Studio, Server and Deployment Console/Multiple Compilation utility differ for integration and deployment of Decision Services?

Nov 8, 2016
Knowledge

Title

Can the version of Corticon components differ for integration and deployment of Decision Services?

URL Name

000056839

Article Number

000174638

Environment

Product: Corticon Version: 5.x and above OS: All supported platforms Browser: N/A Database: All supported databases Application Server: All supported application servers

Question/Problem Description

Can the versions of Corticon Studio, Corticon Server, and Multiple Compilation Utility/Deployment Console differ for the integration and deployment of Decision Services?
Should these Corticon components have the same version?
Can development be done in Corticon Studio 6.1.2 for Corticon Server 6.1.0? Provide specific clarification as to what impact this may pose, if any.
Given 6.1.2 is a patch over 6.1.1, is there any impact to clients staying on 6.1.1 for a short duration after 6.1.2 is applied to build scripts and servers?
Different versions of Corticon are running: 6.1.1 and 6.1.2 after merging teams. Will there be any issues opening assets created 6.1.1 on 6.1.2 and vice versa?
Should the Corticon Server be upgraded to match Corticon Studio version 6.1.2 in all environments?
Is the Dockerfile image from Corticon 7.1.1 backward compatible with Corticon 7.0.0.2 Rule Assets?

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

The same version and same build of Corticon Studio, Corticon Server, and Multiple Compilation Utility/Deployment Console should be used. Corticon components version number should match up even at the hot fix/Service Pack level. Every Corticon Studio in the environment should be at the same level as the Corticon Server. All Rule Assets should be upgraded, recompiled, and redeployed using the same Corticon version installed.

For e.g.

a) Corticon Studio 6.1.3.3 must be used with Corticon Server 6.1.3.3, and the Deployment Console/ Multiple Compilation Utility should also be the same version i.e. 6.1.3.3. The same applies to version 6.1.2. If a Corticon Studio 6.1.1 Rule Asset is opened in Corticon Studio 6.1.2, it will be upgraded to 6.1.2 and cannot be backported.

b) If using the axis.war from Corticon 7.1.1 to deploy to a Docker image, then the Rule Assets will need to be upgraded, compiled, and redeployed with this Corticon 7.1.1 version as well.

Version and build mismatch could lead to errors, incorrect results during execution, and unsuccessful deployment of Decision Services.

It was determined that the Progress Product is functioning as designed.

An enhancement to the product can be requested through the Progress Community via an Ideas submission. Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea.

For detailed information on how to submit an Idea, please refer to Article How to submit an enhancement request for a Progress product?.

Workaround

Notes

Keyword Phrase

Last Modified Date

5/13/2025 9:03 PM

Corticon General Discussions

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Can the version of Corticon components differ for integration and deployment of Decision Services? - Progress Community