The compile option compiles a Ruleflow into a Decision Service .eds file that can then be deployed to a Corticon Server through the Web Console, a .cdd file, or other supported tools.

Table 1. usage: corticonManagement --compile
Argument Description
-i,--input file Required. The source Ruleflow .erf file to be compiled.
-o,--output folder Required. Explicit path to the output folder. If the folder does not exist, it is created.
-s,--service name Required. The Decision Service file name. (Do not add the .eds extension, it will be done for you.)
-v, --version The major and minor version for the Decision Service as specified on the Ruleflow is appended to the .eds file name in the output folder as service_vversionMajor_versionMinor.eds.
-e,--edc [R|RW] Required when the Vocabulary has been mapped to a database. Sets the database access mode (read only or read write).
-dj,--dependentjars dependentjar ... Required when using extensions. Explicit paths to JAR files required for this Decision Service, delimited by spaces.
-ij,--includedjars includedjar ... Required when using extensions. Explicit paths to JAR files (that are specified as dependentjars) to include in the generated EDS file, delimited by spaces.
-tle,--toplevelentities EntityName, ...> Optional. List of top level Vocabulary Entity names for the Decision Service, delimited by commas.
Any values that contain spaces must be in quotes. For example: 
-ij "C:\Program Files\myExtensions.jar" "C:\Program Files\myCallouts.jar"
A complete command might look like this: 
corticonManagement 
   --compile
   --input C:\myProject\myRuleflow.erf
   --output C:\myProject\Output
   --service MyDS
   --edc R
   –-version 
   --dependentjars C:\myProject\myExtensions.jar C:\myProject\myCallouts.jar
   --includedjars C:\myProject\myExtensions.jar C:\myProject\myCallouts.jar  
   --toplevelentities Cargo,FlightPlan