Running Doradus Standalone

Java 1.8 is required to run Doradus. The easiest way to run Doradus is as a stand-alone application using its embedded Jetty server. If you build Doradus using Maven, from the directory {doradus_home}/doradus-jetty use a command such as the following

java -cp ./target/classes:./target/dependency/* com.dell.doradus.core.DoradusServer

If you compiled Doradus with Ant, use a command such as the following:

java -cp ./lib/*:../doradus-server/config:../doradus-server/lib/* com.dell.doradus.core.DoradusServer

Parameters are passed to Doradus as follows:

•

Configurable parameters are defined in the file doradus.yaml. In Github, it resides in the folder doradus-server/src/main/resources. During builds, this file is copied to the folder doradus-server/target/classes (Maven) or doradus-server/config (Ant). This appropriate folder should be in your classpath. You can specify an alternate location with the following Java parameter:

-Ddoradus.config=file:/Doradus/my-doradus.yaml

•	Logging options are defined in the file log4j.properties, which resides in the same folder as doradus.yaml. Specify an alternate location with the parameter:

-Dlog4j.configuration=file:/Doradus/mylog4j.properties

•	Most doradus.yaml parameters can be overridden in command line arguments by prepending a "-" to the parameter name. For example, to override restport, add the command line argument:

-restport 5711

List-valued parameter values should be separated with commas and no spaces. Example:

-tls_cipher_suites TLS_ECDH_RSA_WITH_AES_128_CBC_SHA,TLS_ECDH_RSA_WITH_AES_256_CBC_SHA

•	Instead of modifying doradus.yaml or passing command line arguments, you can place all your non-default configuration parameters in their own file and specify the file’s location with a single command-line argument -param_override_filename. Example:

-param_override_filename /Users/Me/myoverrides.yaml