Configuring Default Properties

Several configurations for Datameer are stored in default.properties.

Edit live.properties instead of default.properties. The settings in the live.properties overwrite settings in default.properties.

Available properties can be seen in the default.properties and moved over to live.properties to be changed there.

Make sure to restart Datameer, using bin/conductor.sh or restarting the client, if you have committed any changes to apply them to your current distribution.

Finding Default Properties

If you already built your own distribution, go to the installation path:

Enter the conf folder.
Search for the default.properties file.
Open it with a text editor.

Make a backup of this file before manually adjusting entries, and fix typos or general errors before saving the file.

Adjustable Options

Find all of the following options within the default.properties file by using cmd+f (Mac) or ctrl +f (Windows) to open the search engine.

Define the deploy(-ment) mode

Datameer deploy modes (separate and unrelated to Hadoop cluster mode):

Trial

File-based database
Example data is injected using a file data store

Live

Metadata store: MySQL
No data is injected

Configuring deploy modes

The deploy mode can be configured in the following ways:

Using Java system property -Ddeploy.mode=local
Using etc/das-env.sh by adding:
```
export DAS_DEPLOY_MODE=local
```
Setting the environment during the start up of the conductor (this way works only if DAS_DEPLOY_MODE isn't set in etc/das-env.sh)
```
DAS_DEPLOY_MODE=local bin/conductor.sh start
```

Configuring DB modes

The metadata store can also be configured independently of the deploy mode in the following ways:

Through Java system property -Ddb.mode=hsql-file|hsql-memory|mysql
Using etc/das-env.sh by adding:
```
export DAS_DB_MODE=hsql-file
```
By setting the environment on start up of the conductor (this method works only if DAS_DB_MODE isn't set in etc/das-env.sh)
```
DAS_DB_MODE=hsql-file bin/conductor.sh start
```

Set up a HSQL or MySQL database

You can manually adjust the settings of a MySQL Database.

name = database name
username
password
host
port

Set a different path for your stored data (das-data)

Don't use a path that depends on the Datameer installation directory. Since the das-data folder is stored inside of your installation directory by default, make a backup of your stored data every time you create a new distribution or upgrade.

To manually type a path to the folder where you want das-data to be stored, change this line:

localfs.root=/[%path%]/datameer/das-data/

The cache is placed under the temp directory. Configure the temp directory with the following property in the live.properties file.

<pre># All Datameer temporary files are written under this directory
localfs.temporary-files=temp</pre>

Define default email and password of internal administrative user account: "admin"

admin.email=admin@localhost
admin.password=admin

Super user setup

You can activate super user accounts in your Datameer distribution. Super user accounts aren't activated by default.

The username and password must not be changed.

Depending on your distribution, you might need to activate a super user account in your trial.properties file as well.

Set up the authentication mechanisms for SSH/SFTP import and export jobs

You can set up the authentication mechanisms for SSH/SFTP import and export jobs. Datameer uses the Jsch library with the following user authentication methods: password, keyboard-interactive, publickey, and gssapi-with-mic.

system.property.jsch.preferred.authentication

Datameer v7