Executing the installer

The installer is completely driven by the DOIM CLI (see also doim.sh reference). Hence, it must be run from the Control Node in the DOIM_HOME/bin directory.

Step 1 - Interactively collecting user input

This step interactively collects user input and stores it as a response file that will then used to generate the initial DMCFG.

Most of the interactive questions are a one-to-one mapping of the variables reported in Domain Master Configuration Reference. The text of each question reports the corresponding DMCFG variable name, so you can quickly look them up on the provided reference page.

You will be asked to create an Ansible Vault password that you will then provide each time passwords are handled by the DOIM CLI. This password is critical for DOIM and must be handled as such.

To launch the interactive phase, run this command:

doim.sh rspfile-create

This command simply stores the collected input without installing anything anywhere, and generates the initial DMCFG, locally storing it on the Control Node.

Step 2 - Installing the product code and deploying the initial DMCFG on managed nodes

The installation of the product code and the deployment of the initial DMCFG on managed nodes is done by running this command:

doim.sh domain-install

At the end of the command execution, which can take a while (depending on the number of managed nodes and on network/storage speed), the product and the initial DMCFG will be available on each managed node. The product, however, will remain in a shutdown state.

Step 3 - Installing product licenses

Any license key files obtained from Primeur must be stored in DOIM_HOME/licenses. Once they are available in this location you can deploy them all to managed nodes by running this command:

doim.sh license-install