Configure the tool

Overview

The config directory contains configuration files for DIH. Some of these files need to be edited. This page provides guidance on which files can be modified to meet your project requirements.

Copy config files

To ensure that your modifications are not overwritten during future DIH updates, copy the following files you are modifying to the config/override subdirectory and make the changes there.

  • config/ria-boot.properties to config/override/ria-boot.properties
  • config/hazelcast.xml to config/override/hazelcast.xml
  • config/hazelcast-client.xml to config/override/hazelcast-client.xml

Configure ria-boot.properties

Configure the following properties in the config/override/ria-boot.properties file.

  • com.ria.core.env.name = <user-defined-name>. This name will be displayed online.
  • com.ria.core.host.address = localhost
  • com.ria.core.host.port = 16080. The 16080 is the HTTP port of the web application.
  • com.ria.core.db.url
  • com.ria.core.db.user
  • com.ria.core.db.password. This is an optional configuration. If property com.ria.core.db.password is specified, the value will be in displayed. If you need the password to be encrypted, add a placeholder value and configure the encryption as described in a following steps.

Encrypt the password

To encrypt the database connection, LDAP, or email server password in the ria-boot.properties file, use the encryption utility by running the command:

bin/encrypt

This command will prompt you to specify the type of password, which can be for the database, LDAP, or email server, and will allow you to set it securely. The ria-boot.properties file will then be updated with the encrypted password.

Configure security

In a new installation, the default configuration includes an admin user ID set ria with the password ria00. This account can be used to log in to the tool for the first time.

In most cases, this security setup is sufficient for the initial installation. If you need to know more, see Configure security.

Configure email

Any JavaMail property that begins with “com.ria.” can be specified in the ria-boot.properties file. These properties allow the email executable to send emails when defined in a task.

At a minimum, you need to specify the email server name but authentication and SSL transport are typically required as well.

Here are some examples from the ria-boot.properties file that can serve as a starting point. Replace user@gmail.com and password with your actual email address and password.

com.ria.mail.debug = false
com.ria.mail.smtp.socketFactory.class = javax.net.ssl.SSLSocketFactory
com.ria.mail.smtp.host = smtp.gmail.com
com.ria.mail.smtp.port = 465
com.ria.mail.smtp.auth = true
com.ria.mail.user = user@gmail.com
com.ria.mail.password = password

Configure Hazelcast

The tool uses Hazelcast IMDG for clustering the runtime server JVMs. Even if only a single JVM is in use, you still need to configure the cluster name and network settings to avoid conflicts with other existing or potential Hazelcast configurations. For more information, see Configure Hazelcast

Create schema objects

The files needed for the initial schema setup are in the tools/dl directory. To create the schema objects, such as tables and views, and to load the initial configuration, run the dataloader init-config.lds script from this directory by executing the following command:

bin/dlload -script lds/init-config.lds