The schema option generates WSDL and XSD schema files from either a Ruleflow (.erf) or Vocabulary (.ecore) file. This is the same functionality that is provided in the Studio Ruleflow and Vocabulary menu commands that export WSDL and export XSD. See How to integrate Corticon Decision Services for more information on service contracts.

Table 1. usage: corticonManagement --schema
Argument Description
-dj,--dependentJars <dependentJar> Add jar files required by this Ruleflow.
-h,--help Print this message.
-i,--input file Required. The source Vocabulary (.ecore) file for a vocabulary-level schema, or Ruleflow (.erf) file for a Decision Service-level schema.
-m,--messagestyle [FLAT|HIER] Optional. Specifies whether the messaging style should be flat, hierarchical. When omitted, defaults to auto-detect where the schema generator determines the best option.
-n,--net name Create a .NET schema.
-o,--output folder Required. Explicit path to the output folder.
-s,--service name Required for a Ruleflow. The name of the Decision Service for the schema.
-t,--type [WSDL|XSD] Required. Type of schema to generate.
-u,--url address Required. Specifies the Server URL to set in the schema document. This URL should match the URL of the Decision Service when deployed so that clients using the schema have the correct server URL to substitute in WSDL schema.

Example usage:

corticonManagement --schema 
                    -i C:\myRuleflow.erf 
                    -t WSDL 
                    -m HIER 
                    -u http://myserver:5555/myservice  
                    -o C:\Output 
                    -s MyDS 
corticonManagement  -s 
                    -i C:\MyVocab.ecore 
                    -t XSD 
                    -u http://myserver:5555/myservice 
                    -o C:\Output