You build projects by passing the configuration file for the projects that you want to
build to the Build Command Line.
About this task
The Build Command Line accepts the following optional
parameters:
-help or -h: Prints the usage of the command line, then
exits.-config configuration_file: Specifies the configuration file
and run the build.-verbose or -v: Prints more details in the command logs when
running the build.-version: Prints the Decision Server and Decision Engine versions, then
exits.
Procedure
-
Enter the following command in a command prompt:
java -jar
Build_Command_Line_executable_archive -config
configuration_file
Build_Command_Line_executable_archive is the path to the executable archive in
your installation files and configuration_file is the path to the configuration
file that you wrote.
For example: java -jar rules-compiler/rules-compiler.jar -config
samples/config-files/CustomRuleModel.properties
- Optional: Add the
-verbose or -v parameter
to have a more explicit version of the command logs.
For example: java -jar rules-compiler/rules-compiler.jar -config
samples/config-files/CustomRuleModel.properties -verbose
Results
For each deployment configuration that is referenced by the configuration file, the command
builds a RuleApp as a stand-alone archive in the specified output folder. The name of this file
comes from the RuleApp name specified in the deployment configuration. The build generates
temporary files in a tmp-dsar folder that it creates in your output folder.
This temporary folder is automatically deleted when the build completes.