IBM DataPower Operations Dashboard v1.0.16.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 operating system is supported by DPOD as described in Hardware and Software Requirements. After the server OS is installed, this can be verified using the following command: cat /etc/redhat-release |
Resources allocation | Allocate resources according to the chosen deployment profile as listed in Hardware and Software Requirements. After the server OS is installed, this can be verified using the following commands: free -h
lscpu |
Network requirements | Ensure you have at least one network interface installed and configured with full access to network services, such as DNS and NTP. |
Root access | The installation must be performed by a root user. You cannot use sudo instead. |
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. lsblk 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. |
SELinux configuration | Changes in SELinux configuration might be needed. If SELinux is enforced on the DPOD server, please review possible required configuration changes. |
Setup DNS | Setup DNS - your network admin may need to assist you with this action. |
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 |
Required RPMs | Verify the existence of the following RPMs from the official RedHat/CentOS yum repositories:
The installation is usually performed by executing The following RPMs are recommended for system maintenance and troubleshooting, but are optional: telnet client, net-tools, iftop, tcpdump |
Ensure the | |
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: |
Table 1 - File Systems / Mount Points
File System / Mount Point | Disk | Space in Mib | Device Type | File System |
---|---|---|---|---|
biosboot | sys (sda) | 2 | Standard Partition | BIOS BOOT |
swap | sys (sda) | 8192 | LVM | swap |
/boot | sys (sda) | 2048 | Standard Partition | XFS |
/boot/efi | sys (sda) | 200 | Standard Partition | EFI System Partition |
/ | sys (sda) | 8192 | LVM | XFS |
/var | sys (sda) | 8192 | LVM | XFS |
/tmp | sys (sda) | 4096 | LVM | XFS |
/shared | app (sdb) | 512 | LVM | XFS |
/app | app (sdb) | 8192 | LVM | XFS |
/app/tmp | app (sdb) | 4096 | LVM | XFS |
/installs | app (sdb) | 11264 | LVM | XFS |
/logs | app (sdb) | 12,288 | LVM | XFS |
/data | data (sdc) | As described in Hardware and Software Requirements or according to the sizing spreadsheet in case one was provided by DPOD support team. Minimum of 100GB. | LVM | XFS |
[Required only for cell members] | Dedicated 6 or 9 disks | Only for cell members, according to the sizing spreadsheet provided by DPOD support team. See Setup a Cell Environment for information about these disks/mount points. | 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.