APTARE IT Analytics Installation and Upgrade Guide for Linux
- Install the APTARE IT Analytics Portal on a Linux server
- Introduction
- Portal installation memory requirements
- OVA-based deployment on VMware ESXi
- Installer-based deployment
- Task 1: Portal and database deployment strategies (Linux)
- Task 2: Pre-installation configuration (Linux)
- Task 3: Install Oracle database application binaries (Linux)
- Task 4: Install the Portal application binaries (Linux)
- Task 5: Installing the database schema (Linux)
- Task 6: Start the Portal services (Linux)
- Task 7: Request the license key file (Linux)
- Task 8: Log into the Portal
- Task 9: Install the license key file (Linux)
- Task 10: Performing a cold backup of the database (Linux)
- Recommended database backup process
- Supported third-party and open source products
- Uninstall the APTARE IT Analytics Portal
- Upgrade APTARE IT Analytics Portal on Linux
- Overview
- Upgrade path
- Before upgrading
- Upgrade Oracle database application binaries to 19c (Linux)
- Upgrade APTARE IT Analytics Portal
- Upgrade a shared services environment
- Run the upgrade utility installer (Linux)
- Known issues
- Run the upgrade utility
- After the upgrade
- Upgrade methods to incorporate enterprise objects
- Attribute merging during the Portal upgrade
- Upgrade the Portal with additional licensed modules
- Upgrade scenarios
- Database table creation scripts
- Add additional products
- Enable new features and report templates using the Portal
- Data Collector upgrades
- Troubleshoot - Manual Data Collector upgrades
- Collector updates from the APTARE IT Analytics Portal
- Oracle patches for the database server
- Upgrade and Migrate to a new server
- Upgrade and migrate to a new server
- Install the latest release of APTARE IT Analytics on the new server
- Perform an export of the database on the existing server
- Stop Portal and agent services on the new server
- Drop and re-create the existing portal user on the new server
- Import the database onto the new server
- Start Portal and agent services on the new server
- Download, install, and execute to upgrade the database schema
- Testing
- Update Data Collector binaries (if necessary)
- Upgrade and migrate to a new server
- Portal upgrades (Linux): Tomcat and Apache
Task 2: Pre-installation configuration (Linux)
Choose a Portal Server.
For performance reasons, avoid installing the APTARE IT Analytics Portal software on the same server as the APTARE IT Analytics Data Collectors. Precisely, avoid installing Data Collectors in
/opt/aptare.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. Portal software installation tasks require root privileges.
Verify the OS of the Portal Server. Check that the OS is one of the certified operating systems listed in the 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
Minimum
Disk Space
Notes
/opt
20 GiB
/tmp
10 GiB
Both /tmp and /var/tmp must be writable by the user aptare
/data01
25 GiB
Required for database
/data02
25 GiB
Required for database
/data03
30 GiB
Required for database
/data04
35 GiB
Temporary table space
/data05
20 GiB
Temporary table space (undo log)
/data06
5 GiB
Temporary table space (redo log)
Total
170 GiB
Review third-party software details.
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.
Verify the rpm fontconfig is installed. This is required for the Portal installer. Fontconfig is a library designed to provide system-wide font configuration, customization and application access. If the rpm fontconfig is not installed, exporting reports to XLS and PDF will fail.
Verify that the necessary rpms exist on your system based on the OS.
For RHEL 8 and CENTOS 8, use the following command:
rpm -q perl-TermReadKey perl-Data-Dumper binutils glibc libaio elfutils-libelf perl-Getopt-Long binutils gcc gcc-c++ glibc-devel ksh libaio-devel libgcc libstdc++ libstdc++-devel sysstat psmisc bc make libnsl.x86_64 --qf '%{name}.%{arch}\n'|sortThe command returns:
bc.x86_64 binutils.x86_64 elfutils-libelf.x86_64 gcc-c++.x86_64 gcc.x86_64 glibc-devel.x86_64 glibc.x86_64 ksh.x86_64 libaio-devel.x86_64 libaio.x86_64 libgcc.x86_64 libnsl.x86_64 libstdc++-devel.x86_64 libstdc++.x86_64 make.x86_64 perl-Data-Dumper.x86_64 perl-Getopt-Long.noarch perl-TermReadKey.x86_64 psmisc.x86_64 sysstat.x86_64
For RHEL 7 and CENTOS 7, use the following command:
rpm -q perl-TermReadKey perl-Data-Dumper binutils glibc libaio elfutils-libelf perl-Getopt-Long compat-libcap1 compat-libstdc++-33 gcc gcc-c++ glibc-devel ksh libaio-devel libgcc libstdc++ libstdc++-devel sysstat psmisc bc make --qf '%{name}.%{arch}\n'|sortThe command returns:
bc.x86_64 binutils.x86_64 compat-libcap1.x86_64 compat-libstdc++-33.x86_64 elfutils-libelf.x86_64 gcc-c++.x86_64 gcc.x86_64 glibc-devel.x86_64 glibc.x86_64 ksh.x86_64 libaio-devel.x86_64 libaio.x86_64 libgcc.x86_64 libstdc++-devel.x86_64 libstdc++.x86_64 make.x86_64 perl-Data-Dumper.x86_64 perl-Getopt-Long.noarch perl-TermReadKey.x86_64 psmisc.x86_64 sysstat.x86_64
For SUSE Linux Enterprise, use the following command:
rpm -q bc binutils glibc glibc-devel libcap-ng-utils libcap-ng0 libcap-progs libcap1 libcap2 libelf-devel libgcc_s1 libjpeg-turbo libjpeg62 libjpeg62-turbo libpcap1 libpcre1 libpcre16-0 libpng16-16 libstdc++6 libtiff5 libaio-devel libaio1 make mksh perl-Term-ReadKey pixz rdma-core smartmontools sysstat xz --qf '%{name}.%{arch}\n'|sortThe command returns:
bc.x86_64 binutils.x86_64 glibc-devel.x86_64 glibc.x86_64 libaio-devel.x86_64 libaio1.x86_64 libcap-ng-utils.x86_64 libcap-ng0.x86_64 libcap-progs.x86_64 libcap1.x86_64 libcap2.x86_64 libelf-devel.x86_64 libgcc_s1.x86_64 libjpeg-turbo.x86_64 libjpeg62-turbo.x86_64 libjpeg62.x86_64 libpcap1.x86_64 libpcre1.x86_64 libpcre16-0.x86_64 libpng16-16.x86_64 libstdc++6.x86_64 libtiff5.x86_64 make.x86_64 mksh.x86_64 perl-Term-ReadKey.x86_64 pixz.x86_64 rdma-core.x86_64 smartmontools.x86_64 sysstat.x86_64 xz.x86_64
Verify that the bc command is available, as it is required by the database installer.
Download the application binaries for both the Oracle Database Installer and the Portal Installer from www.veritas.com. Use the instructions provided in the confirmation of your purchase agreement.
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
aptare
aptare
dba
tomcat
tomcat
aptare
Some environments, particularly virtualized ones using automount, will fail to create the home directories when the useradd command is used. In this situation, manually create the /home/aptare and /home/tomcat directories and chown them to aptare and tomcat respectively.
If you need additional clarification, contact the Veritas Support for details.
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.
Download following Oracle patches from www.veritas.com and keep them in a directory on the server where the Oracle Database will be installed.
p31281355_190000_Linux-x86-64.zip
p30565805_198000DBRU_Linux-x86-64.zip
The path for this directory will requested by the Oracle database installer during the installation and upgrade process. The Oracle database installer will install these patches as part of installation or upgrade.