IBM DataPower Operations Dashboard v1.0.12.0
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Prepare Pre-Installed Operating System
Non-Appliance Mode Only
The steps below are only applicable for installation in Non-Appliance mode, and should be performed by your Linux administrator.
This video demonstrates how to prepare a RHEL 7.8 operating system for DPOD Non-Appliance mode installation. Use it just as a demonstration, as it is not kept up-to-date with every change in the requirements. When preparing the operating system, you should follow the procedure provided below.
Subject | Action |
---|---|
Supported operating system | Verify that the operation system is supported by DPOD as described in System Requirements. After the server OS is installed, this can be verified using the following command:
|
Resources allocation | Allocate resources according to the chosen architecture type as listed in System Requirements. After the server OS is installed, this can be verified using the following commands:
|
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). Some configurations, such as the Cell environment, require 2 network cards. See Network Preparation for more details. |
Root access | Installation must be performed by a root user. You cannot use sudo instead. However, you may run it after running the command: |
Disks, mount points / file systems and logical volumes | DPOD requires at least 3 disks (LUNs / physical / virtual) for the operating system, for the application and for the data. Some configurations, such as the Cell environment, require additional disks. Please 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 the data disks. Once configured, you may verify there are at least 3 disks using the following command:
Tip: to create the mount points / file systems during RHEL installation:
|
Store service dedicated OS user and group | The Store service requires a dedicated OS user and group to run. Consider executing the following command:
|
OS locale | The supported OS locale is en_US.UTF-8. Check the OS Locale Configuration and change it if necessary. |
Setup DNS | Setup DNS - your network admin may need to assist you with this action. Make sure you can ping to your LDAP, Mail/SMTP Server, NTP Server. |
Using yum on RedHat | For RedHat only:Â Your system might need to be registered and subscribed to the Red Hat Customer Portal to be able to install all prerequisites usingÂ
|
Setup NTP | Setup NTP - it has to be the same one configured in your IBM DataPower Gateways.
|
Setup hosts file | 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:
|
Required RPMs | Verify the existence of the following RPMs from the official RedHat/CentOS yum repositories:
The installation is usually performed by executing yum:
If this command fails to find the packages, you should manually download the RPM files and install them. |
Ensure the httpd service is enabled and started by executing the command:
| |
Optional:Â Install Kibana OSSÂ (please read Kibana access limitations):
| |
Cleanup | In case you are using yum, it is recommended to clean its cache to make sure there is enough space in /var (yum cache can take a lot of the space there). To clean yum cache, execute the command:
|
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. 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 file system
Directory / Mount Point | Disk | Space in Mib | Device Type | File System |
---|---|---|---|---|
biosboot | sys | 2 | Standard Partition | BIOS BOOT |
swap | sys | 8192 | LVM | swap |
/boot | sys | 2048 | Standard Partition | XFS |
/boot/efi | sys | 200 | Standard Partition | EFI System Partition |
/ | sys | 8192 | LVM | XFS |
/var | sys | 8192 | LVM | XFS |
/tmp | sys | 4096 (recommended 16384) | LVM | XFS |
/shared | app | 512 | LVM | XFS |
/app | app | 8192 | LVM | XFS |
/app/tmp | app | 4096 | LVM | XFS |
/installs | app | 11264 | LVM | XFS |
/logs | app | 12,288 | LVM | XFS |
/data | data | As described in Hardware and Software Requirements | LVM | XFS |
Third-Party Software
Third-party software such as antivirus, cybersecurity, monitoring, APM, endpoint protection, backup, etc. might significantly decrease the performance of DPOD and impact its functionality.
In case of functionality or performance issues, try first to disable such software.
During the resolution of issues, DPOD support will ask the customer to disable any 3rd party software in order to isolate the issues and verify their source. Support cannot be provided if the 3rd party tools are not disabled.