skip to main content
Corticon Server: Integration & Deployment Guide : Packaging and deploying Decision Services : Using Deployment Descriptors to deploy Decision Services : Structure of a Deployment Descriptor (.cdd) file
 

Try Corticon Now
Structure of a Deployment Descriptor (.cdd) file
The following code segment shows the general pattern of two Decision Services in a CDD file:
<cdd soap_server_binding_url="http://localhost:8850/axis/services/Corticon">
<decisionservice>
<name>[Name1]</name>
<path>[Path1.erf]</path>
<options>
<option name="" value="">
.
.
</options>
</decisionservice>

<decisionservice>
<name>[Name2]</name>
<path>[Path2.eds file]</path>
<options>
<option name="" value="">
.
.
</options>
</decisionservice>

...
</cdd>
Notice that the first decisionservice is a Ruleflow (.erf) file while the second is an unrelated decisionservice that was precompiled from a Ruleflow into a Decision Service (.eds) file. You could add several more decisionservice sections to the CDD file.