Note | |
---|---|
title | Non-Appliance Mode OnlyThe steps below are only applicable for installation in Non-Appliance mode, and should be performed by your Linux your Linux administrator. |
...
- Red Hat Enterprise Linux Server release 7.2, 7.4, 7.5 or 7.6 (7.3 is not supported)
- CentOS version 7.2 / 7.4 / 7.6
...
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 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:
| ||
Resources allocation | Allocate resources according to the chosen architecture type as listed in Hardware and Software Requirements. After the server OS is installed, this can be verified using the following commands:
| ||
Network requirements | Ensure you have at least one network |
...
interface installed and configured with full access to network services, such as DNS and NTP |
...
Prepare Admin access
. | |
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.
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. |
Download the CEF file and transfer it to the /tmp directory on the pre-installed OS server.
Check the OS Locale Configuration and change it if necessary. |
Prepare your 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
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 | erify 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 |
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
|
RedHat Only - Execute the following command: subscription-manager repos --enable=rhel-7-server-rh-common-rpms
The following RPMs are recommended for system maintenance and troubleshooting, but are optional: telnet client, net-tools, iftop, tcpdump | ||
Ensure the |
|
Ensure the httpd service is started by executing the command: systemctl start httpd.service
- 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
- 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 (RedHat Only)
subscription-manager repos --enable=rhel-7-server-optional-rpms
yum 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.
| |
Optional: Install Kibana OSS (please read Kibana access limitations):
|
|
Table 2 - Prepare your file system
Recommended
Disk
Standard Edition - Minimal/Low/Medium/High
free space in Mib
Device
Type
File
System
Configure kibana (kibana.yml):
- server.port: 5601
- server.host: "montier-es-http"
- server.basePath: "/op/kibana"
- elasticsearch.hosts: "http://montier-es-http:9200"
- elasticsearch.shardTimeout: 300000
Prepare disk, mount points / file systems and logical volume
Info |
---|
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 following 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.
This can be done during RHEL installation by choosing Installation Destination option. You will then need to select all Local Standard drives and choose option "I will configure partitioning" under the "Other Storage Options" section.
You should follow table 2 and add all mount points with required definitions using the "+" button.
to create a volume group (sys, app, data) open the "Volume Group" list box and choose "create new volume group ..."
This way you can partition your 3 (logical) drive exactly as stated in table 2.
The minimum file system sizes for the different installation types are described in table 2 below
After configuring the required mount points you can use the command "df -h" to make sure all free space requirements are met.
Your mount point configuration should resemble the following :
To configure your firewall for open access to the DPOD server for port 443, execute the following commands:
Note |
---|
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
If, for any reason, you need to remove this access (close the port) - execute the following commands:firewall-cmd --zone=public --remove-port=443/tcp --permanent
firewall-cmd --reload
iptables-save | grep 443
Note |
---|
You should open port access for the DNS Server, your DataPower devices, your SMTP server and others as described in firewall rules. Please assist your network admin and Linux admin to enable access on these ports. |
Table 1 - Prepare your disk and mount points
...
...
Disk Name
...
| |||
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 |
(recommended 16384) | LVM | XFS |
/ |
2048
Standard
Partition
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 |
For UEFI installations for GPT partition
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.
...
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 toolsto 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.