Non Appliance Mode Only

The steps below are only applicable for installation in Non-Appliance mode, and should be performed by your Linux administrator.

Verify that your operation system is one of the following (x86-64 mode only) as described in system requirements:
- 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
Ensure to select the correct architecture type and that all resources listed in system requirements are made available.
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 IDGs) - see Network requirements

#	Subject	Action	Checked
	Prepare Admin access	Installation must be performed by a root user. You can NOT run it with sudo. You can run it after running the command: su -
	Prepare Store service dedicated OS user and group	The Store service requires a dedicated OS user and group to run. User can use the following command : groupadd storeadms && useradd -g storeadms -md /home/storeadm -s /bin/bash storeadm
	Configure OS locale	The supported OS locale is en_US.UTF-8. Use the following procedure to check the supported 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
		Download the CEF file and transfer it to the /tmp directory 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. Consult your Linux and network admin about the proper way to configure this service. Ensure the NTP RPM is installed. Consider executing the following command: yum install ntp ntpdate <ntp server hostname> systemctl enable ntpd.service systemctl start ntpd.service
		Verify that the /etc/hosts file includes an entry with your server name mapped to your external server IP To find your server name, execute the command: hostname
	Verify all required RPMs are installed	Verify the existence of the following RPMs from the official RedHat/CentOS yum repositories: httpd version 2.4.6-67 and above (together with the following dependencies: mailcap, apr, httpd_tools) mod_ssl curl wget unzip iptables iptables-services bc fontconfig 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. RedHat Only - Execute the following command: subscription-manager repos --enable=rhel-7-server-rh-common-rpms
		Ensure the httpd service is enabled by executing the command: systemctl enable httpd.service
		Ensure the httpd service is started by executing the command: systemctl start httpd.service
		Install mod_proxy_html 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. Download the RPM from: https://artifacts.elastic.co/downloads/kibana/kibana-oss-6.6.1-x86_64.rpm Please follow instructions on https://www.elastic.co/guide/en/kibana/6.6/rpm.html#install-rpm 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	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 :
	Open your firewall to access to DPOD server	To configure your firewall for open access to the DPOD server for 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 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 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

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	Recommended 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 (can be on other fast disk - preferred locally)	LVM	XFS
/data	data	As described in Hardware and Software Requirements minimum of 100GB	LVM	XFS
/boot/efi	data	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.

If you encounter functionality or performance issues, try first to disable these system tools.

Browser not supported