Note | ||
---|---|---|
| ||
The steps below are only applicable for installation in Non-Appliance mode, and should be performed by your Linux administrator. |
Tip |
---|
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 |
The 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 |
Info |
---|
Tuning requirement - define 3 Disks with LVM and with size and mount points as defined below |
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. |
The minimum file system sizes for the different installation types are described in table 2 below.
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:
|
|
|
|
|
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:
| |
OS locale | The supported OS locale is en_US.UTF-8. |
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:
- Has at least 1GB of free space
- Is NOT one of these folders: /app, /logs, /data, /shared, /installs
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>
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. 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: |
|
|
- This RPM is not always accessible from existing repositories. Try first to install it by executing the command: yum install mod_proxy_html
If you get the error "No package mod_proxy_html available. Error: Nothing to do", you will need to download the RPM yourself, using one of the following methods:- Method 1 - download the RPM
- Find your httpd version by executing the command: rpm -qa | grep httpd
- The system will print something resembling httpd-2.4.6-67.el7_2.4.x86_64. This is the mod_proxy version you need to download.
- For RedHat only - Download the mod_proxy with the correct version from the following url:
https://access.redhat.com/downloads/content/mod_proxy_html/2.4.6-45.el7/x86_64/f21541eb/package (change the version part of the URL to match the httpd version you found above). Use wget or any other mechanism to download, and ensure to place the RPM inside the /tmp directory of the pre-installed OS server. - Install the RPM by executing the command: rpm -Uvh mod_proxy_html-2.4.6-67.el7_2.4.x86_64.rpm (Note: your version may vary, as described above)
- Method 2 - add a repository and install it from the repository using the commands (For RedHat only)
subscription-manager repos --enable=rhel-7-server-optional-rpms
yum install mod_proxy_html
- Method 1 - download the RPM
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
| |
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:
|
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 |
Table 2 - Prepare your file system
Disk
Standard Edition - Minimal/Low/Medium/High
free space in Mib
Device Type
200 | Standard Partition | EFI System Partition |
/ | sys |
8192 | LVM |
XFS | |
/var | sys |
8192 | LVM | XFS |
/tmp | sys |
4096 (recommended 16384) | LVM |
2048
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 |
200
(for UEFI installations for GPT partition)
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.
...
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 these system toolssuch 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.