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>AllocateTrade</name>
     <path>AllocateTrade.eds</path>
     <options>
        <option name="PROPERTY_AUTO_RELOAD" value="true" />
        <option name="PROPERTY_MAX_POOL_SIZE" value="1" /> 
     </options>
  </decisionservice>
            
  <decisionservice>
      <name>Candidates</name>
      <path>Candidates.eds</path>
      <options>
         <option name="PROPERTY_AUTO_RELOAD" value="true" />
         <option name="PROPERTY_MAX_POOL_SIZE" value="1" />
      </options>
  </decisionservice>
 
</cdd>

For each Decision Service you must specify a name and the EDS file. The options, if any, specified allow you to configure properties of a Decision Services. A CDD file can contain one or more Decision Services.

Note: The path names to the Decision Service (.eds) files can be expressed relative to the location of the Deployment Descriptor file (indicated by the ../ syntax). That's a good practice, as the explicit path on deployment Servers might be different. These paths can be edited if changes are required. If the saved location of the Deployment Descriptor file has its path in common with the location of the Decision Service (.eds) file, then the path is typically expressed in relative terms. If the two locations have no path in common (for example, they are saved to separate machines), then the path must be expressed in absolute terms. UNC paths can also be used to direct Corticon Server to look in remote directories.