1) "Decision Service: <Decision Service Name> is not registered. " error when calling a Decision Service deployed to the Server
Explain the exception/fault "Decision Service: <Decision Service Name> is not registered.".

2) Problem occurred when trying to load .cdd file at : c:/myCDDpath/mycddfile.cdd. Please review log file for detailed Exception!
com.corticon.service.ccserver.exception.CcServerFileOrDirNotFoundException: Could not find a valid EDS located at c:/myEDSpath/myedsfile.eds.

3) Unmanaged Decision Services are not shown via the Web Console

 

 

This exception generally means the Corticon server is unable to find the appropriate Decision Service. Such conditions include the following:

1) Decision service is not properly deployed or is not deployed at all on the Corticon Server
Regenerate the .eds file and deploy it to the Server using .cdd or other deploy techniques.

2) The Decision Service has a different version from the version specified in the request
In this case, a more descriptive message is provided.
(example request)

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"" xmlns:urn="urn:Corticon">
   <soapenv:Header/>
   <soapenv:Body>
      <urn:CorticonRequest decisionServiceName="tutorial_example" decisionServiceTargetVersion="5">
         <urn:WorkDocuments>

(Exception thrown)
com.corticon.service.ccserver.exception.CcServerDecisionServiceNotRegisteredException: Decision Service <tutorial_example> with Version <5> is not currently deployed

To resolve the problem, ensure the version and deployed service match.

3) The server license is not properly populated, or a non-EDC license is used for an EDC Decision Service, or an expired license causes the Decision Service not to be registered.
To resolve the problem, use a valid/appropriate non-expired license.

4) Environment variable CORTICON_HOME is not set
This is important when the Decision Service is deployed to application servers other than the default Tomcat (e.g., A default Tomcat is bundled with  Corticon versions 7.0 and below). The script to start the default Tomcat (e.g., C:\Progress\Corticon 6.3\Server\bin\startServer.bat) sets the CORTICON_HOME environment variable. For other application servers, including non-default user-defined Tomcat application servers, CORTICON_HOME must be explicitly set so that Axis can locate Corticon resources:

set CORTICON_HOME=C:\Program Files\Apache Software Foundation\Tomcat 9.0

5) Stale ServerState.xml file

a. Stop the server.
b. Back up the ServerState.xml.
c. Delete this XML
d. Recompile the Ruleflow to a .eds file and deploy it to the server again.
e. Ensure the Rule Asset URL is mentioned correctly in the CDD file.
f. Ensure the name of the Decision Service in the CDD file is correct
g. Bounce the Server.
h. A new ServerState.xml is populated, capturing the current state of the server.

 

6)  The name of the Decision Service in the SOAP request is different from the name of the Decision Service deployed.
E.g., The name of the Decision Service deployed on the server is Tutorial_Example, while the Decision service name in the SOAP request is TutorialExample or Example_Tutorial.
To resolve this, modify the name of the Decision Service in the SOAP request to match the name of the Decision Service deployed to the server or modify the name of the Decision Service deployed in the server / cdd to match the name in the SOAP request.

7) Mismatch in Corticon Studio and Server versions
Make sure the versions of the Corticon Server and Corticon Studio used are the same.
E.g., User cannot use 5.3.4 Studio to deploy a Decision Service to Corticon Server 5.4.1

8) The Corticon .NET Server is set up incorrectly.
The .dlls and jars are mixed up from the older and newer versions for the Corticon Server for .NET.
Ensure the Corticon .NET Server is set up with IIS correctly.

 

9) Improperly generated WSDL or missing attributes/entities and associations in the WSDL.
Regenerate the WSDL and do not delete essential components from the WSDL.

 

10) The SOAP request to the Decision Service was not in the correct format with the necessary tags.
Ensure the SOAP request is properly formatted to the Decision Service with all the required tags.

 

11) The .eds file is corrupt or invalid.
Check that the .eds file exists in the specified location and check the size of the file to make sure it is adequate.
To resolve the problem, recompile to generate a new .eds file.

 

12) CDD file misconfigurations are causing the Decision Service to not be deployed:

a.  The syntax of the CDD file is invalid. e.g., Missing a / for:

1. <option name="PROPERTY_DATABASE_ACCESS_MODE" value="R" />
2. b. The CDD is pointing to an incorrect datasource.xml file.
3. E.g., pointing to datasource.xml.xml