Installing the Portal on a Linux Server > Task 2: Pre-Installation Configuration (Linux)
Version 10.1.01
Task 2: Pre-Installation Configuration (Linux)
1. Choose a Portal Server. For performance reasons, the APTARE StorageConsole Portal software should not be installed on the same server as the APTARE StorageConsole Data Collectors. If, for some reason, you require both to be on the same server, be sure that both the Portal and Data Collector software do not reside in the same directory on the server. Root privileges are required for the Portal software installation tasks. See also, Portal Installation Memory Requirements.
2. Verify the OS of the Portal Server. Check that the OS is one of the certified operating systems listed in the APTARE StorageConsole Certified Configurations Guide.
Verify that sufficient disk space exists on the designated Portal Server. For the database file systems, the amount specified is the minimum required to create the database. It is recommended that you allocate more than the minimum to accommodate growth.
File System/Directory
Recommended Minimum
Disk Space
12 GiB
5 GiB
15 GiB
Required for database
25 GiB
Required for database
25 GiB
Required for database
35 GiB
Temporary table space
20 GiB
Temporary table space (undo log)
5 GiB
Temporary table space (redo log)
142 GiB
Review third-party software details. See Third-Party Software.
3. If you plan to export or email reports as PDF files, to ensure proper rendering of these output formats, a graphics manager such as X Virtual Frame Buffer (XVFB) is required. Contact your IT organization to configure this capability.
4. Ensure that the libaio package is installed if the Portal Server’s OS is Red Hat Linux. You can check for this package via the rpm –q command as follows. The package on your system should be the following version or greater.
rpm -q libaio
5. Verify that the necessary libraries exist on your system, using the following command:
rpm -q binutils glibc libstdc++ cpp make libaio elfutils-libelf --qf '%{name}.%{arch}\n'|sort
The list of libraries should include:
6. Verify that the bc command is available, as it is required by the database installer.
7. Download the application binaries for both the Oracle Database Installer and the Portal Installer from the APTARE customer portal, if you are installing from an ISO image rather than from a CD. Use the instructions provided in the confirmation of your purchase agreement.
8. Troubleshooting User Account Creation: The Portal installation process will create user accounts for aptare and tomcat. If you are using non-local user management (such as LDAP or NIS) to manage the Linux user accounts, the useradd command may fail to execute successfully. Take the following steps to manually pre-create the required users:
Using your normal process for creating user accounts in LDAP, pre-create the user accounts aptare and tomcat with home directories under /home.
User ID
Primary Group
Supplementary Groups
If you need additional clarification, contact the APTARE Global Support Services for details.
9. Troubleshooting script issues: A known issue associated with Security Enhanced Linux (SELinux) may arise when executing scripts that require Java. This results in a permission denied error message. To resolve this issue, configure SELinux to allow the use of shared libraries with text relocation.
Portal Installation Memory Requirements
For new APTARE StorageConsole 10.x.xx Portal installations, the Oracle database requires a minimum of 4096 MB of memory. Portal installations will fail if sufficient memory resources are not available on the Portal server. Portal upgrades are not impacted by this requirement.
The Portal Installation software checks the following resources:
Total physical memory (physical + virtual) must be greater than 4096 MB. Oracle will fail to start. Add more physical memory to the Portal server. [Windows and Linux OS]
Total temporary file system (tmpfs) memory must be greater than 4096 MB. Oracle will fail to start. Increase the size of tmpfs, typically in /etc/fstab. [Linux OS only]
Shared memory (kernel.shmmax parameter) must be greater than 4096 MB. Oracle will fail to start. Increase the value of the shmmax parameter, typically in /etc/sysctl.conf. After increasing the value for the shmmax parameter, execute: sysctl -p [Linux OS only]