DPOD’s appliance installation is packaged as an ISO file, in order to support installation on both physical and virtual servers. It includes two steps:

1. The operating system installation (a Rocky Linux operating system), which is pre-loaded in the ISO file and is managed by DPOD.

2. The DPOD application deployment.

Prerequisites

• Allocate CPU and RAM according to the chosen deployment profile as listed in Hardware and Software Requirements.

• DPOD requires 3 disks (LUNs / physical / virtual):

  • 1 disk for the operating system

  • 1 disk for the application and logs

  • At least 1 disk for the data

  The sizes of the disks are described in Hardware and Software Requirements.

Obtain the Software and the Activation Key

1. Download the ISO file and its md5 checksum file from Passport Advantage (file name is DPOD_Appliance_<VERSION>.iso).
   Verify the ISO file integrity by calculating its md5 checksum and comparing it to the downloaded md5 checksum file.

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):

   1. The activation key is included in the download assembly for the program you purchased. In Passport Advantage, make sure to select version “1.0.x” (and not the specific DPOD version).
      For the full version, please apply the activation key found in eAssembly "IBM DataPower Operations Dashboard V1.0.x Full Version Activation eAssembly" (G071VEN/M088JEN).
      For the API calls version, please apply the activation key found in eAssembly "IBM DataPower Operations Dashboard V1.0.x API Calls Version Activation eAssembly" (G071TEN/M088HEN).

   2. The activation key file is a password-protected zip file. Do not try to unzip the activation key zip file.

Deploy the Operating System

Launching the Installation

1. Set the DPOD ISO file as your virtual/physical server's DVD.

2. Make sure the server boots using the UEFI firmware (and not the Legacy boot).

3. Make sure the DVD is configured correctly in the server’s boot order.

4. Power on the virtual/physical server.

5. On the OS launch screen, choose “Install DPOD Appliance - Standard” to start the automatic OS installation for the Standard Edition:

   Open

   

6. The required packages will now be installed. Wait for the installation to complete before proceeding (this should take a few minutes).

Network Configuration

When the OS installation completes, you will be presented with the Network Configuration screen, used to provide DPOD with the network information it requires.

1. Enter the host name, e.g.: dpod-server (you may add the host name to your organization's DNS).

2. Enter the IPv4 address, e.g.: 192.168.65.170

3. Enter the network netmask, e.g.: 255.255.255.0

4. Enter the default gateway: e.g.: 192.168.65.2

5. Enter primary and secondary DNS server IP addresses.

6. When the network data entry process is complete, DPOD echoes it back on the screen for verification:

   Open

   

   Enter “y” to confirm the network details as entered or “n” to re-enter the information.

Setting Passwords

The installation will prompt for passwords for the following users:

1. dpodadm - an administrative user used to log in to the server via SSH, and has permission to use sudo.

2. root - the root user (which is denied from connecting via SSH).

OS Installation Finalization

When you've completed all the steps above, before you press ENTER to restart the machine, you should disable/eject your DVD from the virtual/physical server to make sure the installation is not launched again after the restart. Press ENTER and wait for the server to restart.

Application Deployment

1. Log in to the DPOD's server console with the user dpodadm (e.g.: using SSH, VMware console, a KVM switch, or the physical server console).

2. Run the following command to launch the DPOD application deployment:

   sudo /opt/APPL-setup

3. Follow the instructions and provide any required information (such as environment name, time zone, etc.):

4. Do not interrupt the software update process after you confirmed it and the background process has started.
   If SSH connection is lost during upgrade, the upgrade will still continue. Reconnect to the server and check the log files for the process status and outcome.