Installation, Configuration and Operation

Installation on Windows

Unzip the Odilon Server zip file in the directory where you want to install the executables
(data directories are elsewhere, defined in the configuration file: odilon.properties, see below).

Installation on Linux

Untar tar.gz file in the directory where you want to install the executable
(data directories are elsewhere, defined in the configuration file: odilon.properties, see below).

Example:

# To install in /opt
cd /opt
tar xvf odilon-server-0.5-beta.tar.gz

Directories

app/
A self-contained Odilon server.

bin/
Scripts to startup, manage and interact with Odilon instances.

config/
odilon.properties is is Odilon's main configuration file, Other config files (like log4j2.xml for error logging)

examples/
Sample Java classes to create buckets, upload and download files, list objects, and others.

logs/
logs directories

Configuration

Odilon configuration is done in file ./config/odilon.properties
This is where you can set up server url and credentials (url, port, accessKey, SecretKey), and data storage (RAID level, data storage directories), and other parameters

Sample properties file:
odilon.properties

Linux config.sh
The file ./bin/config.sh contains parameters required for Odilon to run

export JAVA_HOME="/usr/lib/jvm/jre" <- the directory where the java jvm 11 (or newer) is
export APP_USER="odilon" <- Linux user that must be used to run odilon
export ODILON_PROPS="
-Xbootclasspath/a:$ODILON_HOME/resources:$ODILON_HOME/config
-Xms4G
-Xmx12G
-Dwork=$ODILON_HOME/tmp/
-Dlog-path=$ODILON_HOME/logs
-Dlog4j.configurationFile=log4j2.xml
-DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
-Djava.net.preferIPv4Stack=true
-Duser.timezone=America/Argentina/Buenos_Aires"
<- standard jvm parameters

Startup and Shutdown

Windows
cd bin/
start.bat to startup the server
stop.bat to shutdown the server

Linux
cd bin/
start.sh to startup the server
shutdown.sh to shutdown the server

After starting the server you can check that it is running normally by opening the page /info in a web browser.
Example: http:/localhost:9200/info

See sample screenshot