IBM DataPower Operations Dashboard v1.0.20.x

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Appliance Server Installation

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

  1. Operating System installation (a CentOS operating system that is pre-loaded in the ISO file and is managed by DPOD).

  2. Software deployment

You MUST NOT add or install any packages / RPMs on the operating system that is managed by DPOD (for example, do not use yum install).
You MUST NOT update the CentOS version or any other component within DPOD using external repositories (for example, do not use yum update).
The only supported way to upgrade the platform and/or components is by applying a product Fix Pack.

Obtain the Software

  1. Download the ISO file from Passport Advantage (file name is DPOD_Appliance_<VERSION>.iso).

  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.

OS Deployment

Prerequisites

  1. The server needs to have 3 disks, as documented in Hardware and Software Requirements.

Initial Installation

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

  2. Make sure the server is using the Legacy BIOS and not UEFI, as currently the ISO file does not support UEFI.

  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 Appliance” to start the automatic OS installation for Standard Edition (the Developer Edition should have a slightly different launch screen stating this is the Developer Edition):

  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 DPOD's host name, e.g. dpod25min (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 (not mandatory)

  6. When the network data entry process is complete, DPOD echoes it back on the screen for verification and displays an 'Is this correct [y/n]' prompt.
    Enter “y” to confirm network details as entered or “n” to re-enter the information.

Setting Passwords

Set passwords for the users:

  1. Change DPOD's OS administrative user (productadm) password:

  2. Change root user passwor:

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 in the virtual or physical server so the installation is not launched again after the restart.

Press ENTER and wait for the server to restart.

Software Deployment

  1. Log in to the DPOD's server console with the user root (e.g.: using VMware console, a KVM switch, or the physical server console).
    Do not use SSH to connect to the DPOD server, as for security reasons, SSH sessions are limited to 300 seconds and your session might time out during installation. If you must use SSH, you can configure the timeout limit by following the steps in SSH Session to DPOD Disconnects Often.

  2. run lsblk and make sure the three required disks were mounted, and are in the correct order (OS, Install and Data disks, as explained on Hardware and Software Requirements).
    Run the installApp command to start the product installation:

    installApp
  3. Adjust the date, time and time zone if required:


    If you choose to change the current time zone configuration, you will be prompted for time zone selection. Select your country's region and country.
    DPOD will suggest a time zone based on your country selection, and display an 'Is the above information OK?' prompt. You may confirm the time zone configured by choosing 1 for “yes” or 2 for “no”.

  4. On the next screen you may configure the NTP (Network Time Protocol) servers DPOD will use. Keeping the internal clocks of DPOD and the monitored appliances in sync is important - as DPOD reports the time as logged by the devices themselves.
    Enter the NTP servers information.
    After you finish entering the NTP data, DPOD echoes it back on the screen for verification and displays an 'Is this correct [y/n]' prompt.
    Enter “y” to confirm NTP details as entered or “n” to re-enter the information.

  5. Choose an environment name for this DPOD installation, each DPOD installation must have a unique 4-character environment name.

  6. Choose whether you use SSD storage

  7. Read the End User License Agreement (EULA) and if you accept the term please press 1 to accept it. You may also press 0 to decline the agreement and abort the installation.

  8. On the following screen, choose the deployment profile that fits your requirements (see Hardware and Software Requirements page):
    Note that the list might change, and the options available to you may not match those shown above.
    t

  9. Wait for the installation to finish.
    Any errors will be logged to the installation log file, displayed at the end of the installation process.
    The /installs/logs directory contains detailed install logs for each component.

  10. After displaying the messages "Stopping/Starting ...",  the installation will work in silent mode - without any further messages for ~ 5 minutes, this is a normal behavior.
    When the installation is completed, you should see the following output:
    r in screenshot

  11. Login again as root or just use the su - command.



 

Copyright © 2015 MonTier Software (2015) Ltd.