Perform the following steps to deploy DPOD on a pre-installed CentOS / RHEL.

Prerequisites

• Make sure to follow Operating System Requirements for Non-Appliance Mode.

Obtain the Software

1. Download the CEF file from Passport Advantage (file name is DPOD_NonAppliance_<VERSION>.cef).

2. Download the activation key file from Passport Advantage (file name is DPOD-full-version-activation-key-<KEY-VERSION>.zip or DPOD-api-calls-activation-key-<KEY-VERSION>.zip).
   The activation key file is a password-protected zip file. Do not try to unzip the activation key zip file.

Execute the CEF File

• The CEF file may be executed from any directory that meets the following requirements (e.g.: /tmp):

  • The directory has at least 1GB of free space after the CEF file is copied into it.

  • The directory is NOT mounted with noexec flag (e.g.: in /etc/fstab).

  • The directory is NOT one of the following: /app, /logs, /data, /shared, /installs.

• Download the CEF (Compressed Executable Format) file and copy it to the chosen directory.

• Consider the following parameters when executing the CEF file:

  • By default, CEF file content is extracted to /tmp directory. To change the destination directory, use the option --dest-dir <directory>.

  • By default, the installation will verify that the server has at least 3 disks. If you plan to use the Minimal deployment profile with only 1 disk, use the option --poc.

• Execute the following commands:

  cd <CEF_DIRECTORY> chmod 755 <CEF_FILE> ./<CEF_FILE>

The Installation Process

1. The CEF installer displays a series of questions, requiring you to verify that your machine and operating system meet the installation prerequisites.

2. Once you answer Yes to all questions, the installer will verify the system meets all prerequisites.
   Critical compatibility checks must be satisfied in order to install the system, while other informational compatibility checks will make sure the operating system is optimized and will notify if changes are recommended to be made.
   Please take time to review the results of these checks after installation, and perform applicable optimizations. The compatibility checks report can be found in /installs/logs/appliance_checks-<date time>.log.

3. Next, you can change the time and date settings.

4. Choose an environment name for this DPOD installation. Each DPOD installation must have a unique 4-character environment name.
   If you are installing a second DPOD machine that will be used as the standby machine in a DR Active/Standby scenario, the environment name must be identical to the environment name of the active DPOD installation.

   If you are installing DPOD as part of a Cell environment, the environment name must be identical between the Cell Manager and all Cell Members.

5. Choose whether you use SSD storage. This will help optimizing the performance.

6. Configure the Store Service dedicated user (default is storeadm).

7. (Optional) If the server has 2 NICs, you will need to specify the IP address that will be used for the UI Console.

8. Accept or decline the EULA.

9. Choose the deployment profile. Ensure your machine has enough resources for the chosen profile, or the installation might abort.

10. The installation will commence. The process takes 5-15 minutes, and when it ends the installer displays a message indicating whether the process was successful or not, alongside the name of the installation log file.

Post Installation

Once the installation is complete, it is recommended to let DPOD optimize the operating system parameters to ensure performance by executing the script below.
Please review the script before executing it and make sure the OS parameters values match your organization's policy.