Non Appliance Mode Only
The steps below are only applicable for installation in Non-Appliance mode, and should be performed by your Linux administrator.
| Subject | Action |
|---|---|
| Supported operating system | Verify that your operation system is one of the supported operating systems described in System Requirements. |
| Resources allocation | Ensure to select the correct architecture type and that all resources listed in System Requirements are made available. |
| Network card | Ensure you have at least one network card installed and configured with full access to network services such as DNS and NTP (the same as your Gateways) - see Network Preparation. |
Root access | Installation must be performed by a root user. You can NOT run it with sudo. However, you may run it after running the command: su - |
Disks, mount points / file systems and logical volumes | Tuning requirement - define 3 Disks with LVM and with size and mount points as defined below For both Production and Non Production installations, the Standard Edition requires 3 disks (LUNs / physical / virtual) to support throughput. You will need to allocate the mount points / file systems on the different disks as described in table 1 below. It is strongly recommended to use logical volume manager (LVM) - particularly for data disks. The minimum file system sizes for the different installation types are described in table 2 below. To create the mount points / file systems during RHEL installation:
After configuring the required mount points / file systems you can use the command "df -h" to make sure all free space requirements are met. |
| Store service dedicated OS user and group | The Store service requires a dedicated OS user and group to run. Consider executing the following command: groupadd storeadms && useradd -g storeadms -md /home/storeadm -s /bin/bash storeadm |
| OS locale | The supported OS locale is en_US.UTF-8. Use the following procedure to check the OS Locale Configuration and change it if necessary. |
Installation file and environment | Ensure your /tmp directory has at least 1GB of free space Installation from a different directory is possible. If you opt to run the install from a directory other than /tmp, ensure that this directory:
Download the CEF file and transfer it to the installation directory (e.g. /tmp) on the pre-installed OS server. Execute the following command from the pre-installed OS server terminal: chmod 755 ./<File Name> |
Setup your network (consult your network admin) | Setup DNS - your network admin may need to assist you with this action. |
Setup NTP - it has to be the same used for your IBM DataPower Gateways.
| |
Verify that the /etc/hosts file includes an entry with your server name mapped to your external server IP. To find your server name, you may execute the command: hostname | |
Required RPMs | Verify the existence of the following RPMs from the official RedHat/CentOS yum repositories:
The installation is usually performed by executing: yum install httpd mod_ssl curl wget unzip iptables iptables-services bc fontconfig If this command can not find the package on account of it not being included in the repository, you will need to add the containing repository or manually download the RPMs files and install them. |
Ensure the httpd service is enabled and started by executing the command: systemctl enable httpd.service && systemctl start httpd.service | |
Install mod_proxy_html:
| |
OPTIONAL: Install Kibana OSS (kibana-oss-6.6.1) This RPM is required only if you would like to manually query the Big Data store:
Configure Kibana (edit kibana.yml):
| |
| Firewall access to DPOD server | To configure your firewall to allow access to DPOD server at port 443, execute the following commands: These commands may not be applicable if your system has no builtin firewall. firewall-cmd --zone=public --add-port=443/tcp --permanent firewall-cmd --reload iptables-save | grep 443
firewall-cmd --zone=public --remove-port=443/tcp --permanent firewall-cmd --reload iptables-save | grep 443 You should open port access for the DNS Server, your DataPower Gateways, your SMTP server and others as described in Firewall Requirements. Please assist your network admin and Linux admin to enable access on these ports. |
Table 1 - Prepare your disk and mount points
File system / Mount point | Disk Name |
|---|---|
| / | sys |
| /var | sys |
| /tmp | sys |
| /boot | sys |
| swap | sys |
| /logs | app |
| /data | data |
| /shared | app |
| /app | app |
| /app/tmp | app |
| /installs | app |
Table 2 - Prepare your file system
| Directory / Mount Point | Disk | Standard Edition - Minimal/Low/Medium/High free space in Mib | Device Type | File System |
|---|---|---|---|---|
| / | sys | 4096 | LVM | XFS |
| swap | sys | 8192 | swap | XFS |
| /var | sys | 4096 | LVM | XFS |
| /tmp | sys | 2048 (recommended 16384) | LVM | XFS |
| /boot | sys | 2048 | Standard Partition | XFS |
| /shared | app | 512 | LVM | XFS |
| /app | app | 8192 | LVM | XFS |
| /app/tmp | app | 4096 | LVM | XFS |
| /installs | app | 8192 | LVM | XFS |
| /logs | app | 12,288 | LVM | XFS |
| /data | data | As described in Hardware and Software Requirements | LVM | XFS |
| /boot/efi | data | 200 | Standard Partition | EFI System Partition |
Installation Compatibility Checks
There are two types of checks: Critical and Informational.
The critical checks are mandatory in order to install the system. The informational checks are highly recommended for system optimization.
Please take time to review the results of these checks after installation, and perform all applicable optimizations. The compatibility checks report can be found in /installs/logs/appliance_checks-<date time>.log
Supported programs
The only supported programs for installation on the DPOD server are infrastructure / system tools like Antivirus agents, Monitor Agents, Backup Agents etc.
Note that these system tools may affect DPOD's functionality and performance.
If you encounter functionality or performance issues, try first to disable these system tools.