Table of contents Software System Requirements for Aternity 11 Servers and Devices (Agents) This section details the minimum software system requirements to install and run the components of Aternity. Important Synchronize all Aternity components to have the same date, time AND time zone. Access Aternity Dashboards and Settings Sign in to Aternity by entering the hostname of your on-premise Aternity Management Server (like https://aternity.mycompany.com/) in a Windows browser on a monitor with resolution 1280 x 768 or more. You can view Aternity in: Google Chrome version 42 and above. Microsoft Internet Explorer version 11 and 11 Enterprise Mode, with Compatibility Mode disabled and third-party browser extensions enabled. Note To use Chrome to display some administration screens (which use Flex), perform the procedure explained here to install and use a dedicated desktop application to securely access the Aternity administrative screens. To access this link, you need to sign in to the Aternity Support Site. Learn more. Windows Devices (Running Windows Agent) Each monitored Windows device must have the following minimum system requirements to install the Agent for End User Devices locally: Important Aternity on-premise 12.x requires that devices run Agent for End User Devices 9.0, 9.1.7, 9.2.x, 11.0.x, 12.0.x or Agent 12.1.x. Product Supported Agent for End User Devices Aternity 12.x Agent 9.0, 9.1.7, 9.2.x, 11.0.x, 12.0.x or Agent 12.1.x Aternity 11.x Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0.x Aternity 10.x Agent 9.0.x, 9.1.7, 9.2.5 or 9.2.6. Aternity 9.x Agent 9.0.x ONLY. Attribute Requirement Windows operating system Device must have: (For servers): Windows Server 2016 64-bit, Windows Server 2012 R2 64-bit, or Windows Server 2008 R2 64-bit. (For devices with Agent up to 12.0.x): Microsoft Windows 10, 8.1, or Windows 7 SP1 (with KB3125574) Enterprise / Professional 32-bit and 64-bit (32-bit requires Agent 9.0.6 or later). (For devices with Agent 12.1 or later): Microsoft Windows Server 2016 64-bit, or Microsoft Windows Server 2012 R2 64-bit, or Microsoft Windows 10, or Microsoft Windows 8.1, or Microsoft Windows Server 2008 R2 or later 64-bit (Enterprise / Professional), or Windows 7 SP1 (with KB3125574) or later 64-bit (Enterprise / Professional). Monitored web applications Agent 11.x can monitor a web (cloud) application running in any of the following Windows browsers: Chromium-based Microsoft Edge version 88 and above. Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Without this, Aternity only monitors clicking a link, back, forward, direct URL, HTTP GET and POST events. Monitor only managed applications with custom activities or page load activities (WPM) in Firefox (beta) single process mode versions 38 ESR, 45 ESR or 52 ESR. Contact Customer Services if you have versions 45 ESR or 52 ESR to enable monitoring of custom activities, and to ensure they are compatible with your Firefox. Agent 12.0.x (unlike Agent 11.x) monitors managed applications with custom activities or page load activities (WPM) in Firefox (beta) version 60.4 and above. Connectivity The Agent sends monitoring data to Aternity (including IP v6 for Agent 11 or later) using HTTPS over port 443. Tip Aternity gathers and stores detailed performance data. To view older data, it displays a condensed summary (aggregated data), like an hourly or daily summary. The Agent for End User Devices reports data to Aternity once every minute. If its status becomes disconnected and it cannot send data after trying for five minutes, it locally stores up to 50 minutes of retention data in offline mode, and then sends it when it renews its connection. The device continuously tries to reconnect to Aternity in ever-increasing intervals, after ½ minute, one minute, two minutes, four minutes, eight minutes, 16 minutes, 32 minutes, and if it still fails, the Agent restarts itself and tries again to connect, restarting this cycle again. Resource usage A local Agent in Windows typically uses: CPU: Total utilization across all cores approx. 0.12%. For virtual application servers and MS Terminal Server: typically 5-15%. RAM: Approx. 120MB physical memory (private working set). For virtual application servers and MS Terminal Server, add 40MB per session. Storage: Approx. 110MB, plus Agent log files (10MB to log only errors, or up to 740MB for complete logs). In rare support-led troubleshooting cases, log files can reach up to 3GB. Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity. Microsoft .NET (For Agent for End User Devices 12.0 or earlier) Device must have Microsoft .NET v4.5 SP1 or later to use security (TLS 1.2). (For Agent for End User Devices 12.1 or later) Device must have Microsoft .NET v4.6 SP2 or later to use security (TLS 1.2). Install privileges You must run the Agent setup with administrator privileges on the device. Permissions The Agent must have write access to the registry during the installation and while the Agent is running. The Agent must have permissions to write to the allusersprofile\aternity directory. Global security policies Enable and configure accordingly the Global Security Policies such as GPOs to ensure the Aternity Agent is able to inject into the desired monitored application. Aternity HTML hook is needed to monitor any web based application. If Enable third-party browser extensions is disabled, the hook will be unable to inject. This setting must be enabled or a GPO must be created and/or modified to add our hook to the exclusions. Virtual Windows Devices (Running the Windows Agent) Aternity monitors performance in a wide range of virtual applications and virtual desktops. The virtual servers must be housed in one of the following operating systems: Attribute Requirement Virtual server operating system Windows Server 2016, 2012 R2, 2012, 2008 R2 or 2019. The Windows Agent supports virtual devices and/or virtual applications with any of the following requirements: Attribute Requirement Citrix virtual application servers (Legacy naming up to v7.18) Citrix XenApp 6.5, 7.6, 7.8, 7.15, 7.18 (New naming from v7.19) Citrix Virtual Apps 7.19. Citrix virtual desktop servers (Legacy naming up to v7.18) Citrix XenDesktop 6.5, 7.6, 7.8, 7.15, 7.18 (New naming from v7.19) Citrix Virtual Desktops 7.19 VMWare Enterprise VDI VDI support is for VMWare Horizon View up to 8.0. Aternity does not monitor the ESXi hypervisor. VMWare ThinApp is NOT supported. Microsoft RDC Microsoft Remote Desktop Services 6.1, 8.1, 10.0. Microsoft virtual application servers Microsoft App-V 4.6 SP3, 5.0, 5.1. Azure Windows Virtual Desktop (WVD) Windows 10 Enterprise multi-session or Windows 10 Enterprise Mac Computers (Running the Aternity Agent for Mac) To monitor an Apple Mac with Aternity Agent for Mac, it must have the following minimum system requirements: Attribute Requirement Agent for Mac Supported versions of Agent for Mac: 3.0, 3.1.x, 3.2.x, 3.3, 3.4 Mac operating system macOS 11 (Big Sur) since Agent for Mac 3.4 macOS 10.15 (Catalina) since Agent for Mac 3.3 macOS 10.14 (Mojave) since Agent for Mac 3.1 macOS 10.13 (High Sierra) since Agent for Mac 2.4 macOS 10.12 (Sierra) macOS 10.11 (El Capitan) macOS 10.10 (Yosemite) Processor Mac computer with Intel 64-bit CPU Mac computer with Apple M1 CPU (since Agent for Mac 3.4) Resource usage The Agent for Mac typically uses: CPU: Total utilization across all cores less than 1%. RAM: The Aternity Agent for Mac uses up to 650MB of physical memory. Storage: At least 0.5GB free disk space available. Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity. Monitor web applications Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Mobile Devices (Running a Monitored Mobile App) To run a monitored app, the device must have the following operating systems: Attribute Requirement iOS operating system of monitored device iOS 9 and up to iOS 12. Android operating system of monitored device Android 4.4 and up to Android 9. Embed Mobile Monitoring (Aternity Wrapper and Aternity Mobile SDK) To add monitoring to a mobile app, you must embed Aternity's monitoring into the app itself, before it is encrypted. Before embedding Aternity's monitoring into an iOS mobile app, verify your Mac conforms to the following minimum system requirements (Aternity iOS Wrapper and Aternity iOS Mobile SDK): Attribute Requirement (iOS Wrapper and Aternity iOS SDK) Operating system Mac OS X 10.10 or later. Programming environment Apple XCode 7 or newer. Connectivity Internet access. App resource usage When you add Aternity functionality to an iOS app: Disk storage size increases by 3.3MB. RAM size is an extra 5-10MB. CPU usage rises by 1%. Before embedding Aternity's monitoring into an Android mobile app, verify your device conforms to the following minimum system requirements (Aternity Android Wrapper or Aternity Android Mobile SDK): Attribute Requirement (Android Wrapper and Aternity Android SDK) Operating system Android 4.4 or later. Java Developer Kit JDK 1.8 or later. Programming environment Google Android Studio or a standalone Android SDK. Using the SDK Manager, install the latest Android SDK tools (platform tools and build tools) for SDK Platform API level 19 or newer. Connectivity Internet access. App resource usage When you add Aternity functionality to an Android app: Disk storage barely changes at all. RAM size is an extra 5-10MB. CPU usage rises by 1%. Aternity Oracle Database Server (Oracle) The Aternity Oracle Database Server is an Oracle database which hosts the Aternity system settings, data model and performance data, after the Data Warehouse Server summarized (aggregated) it. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Hard disk for express database setup of the Aternity Oracle Database Server The express database setup requires: System disk (C drive) A logical or physical drive other than the system disk, with the free space required for your deployment size Oracle version for Aternity Oracle Database Server Use Oracle 19.0.0.0 or 18.0.0.0 or 12.2.0.1 or 12.1.0.2 or 11.2.0.4 (including support for Oracle Data Guard), specifically: Oracle Database version 11.2.0.4 Enterprise Edition 64-bit Oracle Database version 12c Enterprise Edition 64-bit, 12.2.0.1 or 12.1.0.2 Oracle Database version 18c Enterprise Edition 64-bit, 18.0.0.0 Oracle Database version 19c Enterprise Edition 64-bit, 19.0.0.0 Note You do not need to update your Oracle if you already have one of these versions. The Oracle license MUST allow for Partitioning, Parallel, and Advanced Compression. However the other licensing features are optional, depending on your enterprise's policy and requirements: (Diagnostics and Tuning Pack and the Active Data Guard). You can download either version of Oracle from the Additional Packages page of the Aternity Support Site. Operating system for Aternity Oracle Database Server (For express database setup) Windows Server 64 bit 2012 R2 or Windows Server 64 bit 2016. (Full setup) Windows Server 64 bit 2016 or 2012 R2. In either case: Set the date and time formats to Control Panel > Regions > Formats > English (United States). (Full setup only) You can also install the Oracle Database Server on Linux CentOS or Linux Red Hat Fedora. RAM for Aternity Oracle Database Server (express setup and full setup) (Express setup) The express database setup automatically detects the RAM and configures the database: For 3-11GB RAM, the database supports up to 100 monitored devices. For more than 11GB RAM, the database supports up to 3000 monitored devices. (Full setup) Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Vertica Database Server Vertica is a third-party column-store database optimized for large volume data analytics. The Aternity Vertica Database Server stores the performance data in the Vertica format, which is most efficient for displaying in Aternity dashboards. It receives its data from the Aternity Docker Components Server. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Operating system for Aternity Vertica Database Server Linux CentOS 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify your version of CentOS, enter cat /etc/centos-release Red Hat Enterprise Linux (RHEL) 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify the RHEL version, enter cat /etc/redhat-release Note If you set up a trial deployment using VMWare virtual machines, the operating system in the OVA file comes with CentOS 7.8. Verify that the disk partition dedicated to the Vertica data folder (Target directory) uses the EXT4 file system. Enter df -Th to verify. If you deploy on virtual machines, you MUST define all resources as dedicated or reserved (Resource Allocation > Reservation). In addition, you can use a Logical Volume Manager (LVM) in Aternity 12 on any hard drive with no restrictions. See Vertica limitations for LVM. Partitions Verify that the disk partition dedicated to the Vertica data folder (Target directory) uses the EXT4 file system. Enter df -Th to verify. Permissions Create the exact same user with the same permissions on each computer. Run the setup as a user with root or sudo root privileges on the computer. To verify, enter sudo id. If you run the setup as a user with sudo permissions that requires a password, setup will prompt you for the password. If the sudo user does not require a password, the setup does not interrupt the process with those prompts. Vertica version for Aternity Vertica Database Server Aternity 12.0 requires that your Vertica Database Server runs HPE Vertica 9.2.1.-11. You can download this with the rest of the Aternity on-premise package. Resource limits for Vertica DBA user The Vertica DBA user must have bash as its shell, and have read, write and execute permissions on its home folder. (For several nodes in a cluster) It must also be able to SSH to other nodes in the cluster. The Vertica DBA user must have an open file limit of 65536 or more. The setup script automatically assigns this setting to the DBA user. You can enter a DBA username, password and group in the parameters file, or keep the name which is predefined (dbadmin), if the username does not exist, the script creates it with these properties. Network Ensure this server has a static IP v4 address, and that you open the required ports. Time zone Synchronize all Aternity components to have the same date, time AND time zone. Aternity Dashboard Server (Tableau) The Dashboard Server displays Aternity's intuitive dashboards using Tableau as its engine. It presents the data from the Aternity Vertica Database Server. The Aternity Dashboard Server is a server running the version of Tableau which is compatible with this version of Aternity. For more information on the requirements of Tableau, see Tableau documentation. Attribute Requirement Operating system for Dashboard Server Use any of the following: Windows Server 2016 64 bit or Windows Server 2012 R2 64 bit (with KB2919355 and KB2999226) (install KB2919355 first, and only then KB2999226) or Set the date and time formats to Control Panel > Regions > Formats > English (United States). Time zone Synchronize all Aternity components to have the same date, time AND time zone. Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Microsoft .NET Ensure this server has Microsoft .NET 3.5 (exactly) required for the database drivers, and .NET 4.5 or later, required for driver setup (both in parallel). To add .NET to a Windows Server, learn more. Tableau version for Dashboard Server Aternity 12.0 requires that your Dashboard Server runs Tableau Server 2019.3.10 (using Tomcat 7.0.91, Apache httpd 2.4.41). Network Ensure this server has a static IP v4 address, and that you open the required ports. Connectivity for Dashboard Server This server must be open for access on port 80 or 443 from the Aternity Management Server and users accessing the Aternity dashboards from their browser. This server requires internet access (port 80) to connect to Tableau's map service to render Aternity's geographic maps correctly. In addition, open port 8000 on the Windows Firewall for Tableau's internal load balancer. Check Tableau's online help for a full list of required open ports. Permissions for Dashboard Server You may need either local or domain administrator privileges on this computer. Verify that the Windows account which is going to set up this server has permission to read, write, list and execute in the Tableau Server setup directory and its sub-folders. Learn more. Aternity Management Server and Aternity Data Warehouse Server The Aternity Management Server acts as Aternity's central server, which manages and integrates all the components. When users access Aternity to view the dashboards or configure it, they access this server via a browser. The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Oracle Database Server and the Aternity Vertica Database Server. Both these servers require the following: Attribute Requirement Operating system for Management Server and Data Warehouse Server Windows Server 64 bit 2016 or 2012 R2 64 bit. Set the date and time formats to Control Panel > Regions > Formats > English (United States). Both servers set up and use Apache Tomcat 8.5.32. Note Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Aggregation Server An Aggregation Server gathers (aggregates) the data directly from Agent for End User Devicess on monitored devices, and passes it on to the Management Server. Attribute Requirement Operating system for Aternity Aggregation Server Windows Server 64 bit 2016 or 2012 R2 64 bit Enterprise Edition. Set the date and time formats to Control Panel > Regions > Formats > English (United States). The Aggregation Server sets up and uses Apache Tomcat 8.5.32. You can also deploy the Aternity Aggregation Server on Linux CentOS or Linux RedHat Fedora. Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Docker Components Server The Aternity Docker Components Server is the on-premise server that hosts all Aternity Docker services which provide multiple different functionalities to Aternity. Most components are mandatory, but you can choose to add or omit some of the optional components and their associated functionality. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Network Ensure this server has a static IP v4 address, and that you open the required ports. Operating system for Aternity Docker Components Server Linux CentOS 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify your version of CentOS, enter cat /etc/centos-release Red Hat Enterprise Linux (RHEL) 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify the RHEL version, enter cat /etc/redhat-release Docker version for Aternity Docker Components Server Aternity does not supply the Docker engine. Customers are responsible for its installation. It is required for the Aternity Docker Components Server, regardless of operating system. On CentOS, Aternity supports Docker for CentOS 17.x or 18.x. Learn more. Use either the Community Edition (CE) or the Enterprise Edition (EE). EE requires subscription, while CE is free. On Red Hat Enterprise Linux (RHEL), Aternity supports Docker 1.13, 17.x, and 18.x, but only 1.13 version is free. RHEL Docker 17.x and 18.x (Enterprise Edition) are only available for RHEL with a paid subscription to Docker. After you set up the Docker engine and run it, you can set up the Docker Components from a Docker image file. If you do not have an internet access, follow the procedure explained here. You can always go to the Docker website to learn more. Permissions (Aternity on-premise 11.0.2) Only users who are defined in the sudoers file can run the setup of Aternity Docker Components Server. Start as a non-root user and follow the setup procedure. At some point, you will be prompted to ask your IT representative to define permissions in the sudoers file. It is possible to run the setup as root user on the computer if this user is defined in the sudoers file as well. (Aternity on-premise 11.0.0 and 11.0.1) Run the setup as a user with root or sudo root privileges on the computer. To verify, enter sudo id. If you run the setup as a user with sudo permissions that requires a password, setup will prompt you for the password. If the sudo user does not require a password, the setup does not interrupt the process with those prompts. Time zone Synchronize all Aternity components to have the same date, time AND time zone. SavePDF Selected topic Selected topic and subtopics All content Related Links
Software System Requirements for Aternity 11 Servers and Devices (Agents) This section details the minimum software system requirements to install and run the components of Aternity. Important Synchronize all Aternity components to have the same date, time AND time zone. Access Aternity Dashboards and Settings Sign in to Aternity by entering the hostname of your on-premise Aternity Management Server (like https://aternity.mycompany.com/) in a Windows browser on a monitor with resolution 1280 x 768 or more. You can view Aternity in: Google Chrome version 42 and above. Microsoft Internet Explorer version 11 and 11 Enterprise Mode, with Compatibility Mode disabled and third-party browser extensions enabled. Note To use Chrome to display some administration screens (which use Flex), perform the procedure explained here to install and use a dedicated desktop application to securely access the Aternity administrative screens. To access this link, you need to sign in to the Aternity Support Site. Learn more. Windows Devices (Running Windows Agent) Each monitored Windows device must have the following minimum system requirements to install the Agent for End User Devices locally: Important Aternity on-premise 12.x requires that devices run Agent for End User Devices 9.0, 9.1.7, 9.2.x, 11.0.x, 12.0.x or Agent 12.1.x. Product Supported Agent for End User Devices Aternity 12.x Agent 9.0, 9.1.7, 9.2.x, 11.0.x, 12.0.x or Agent 12.1.x Aternity 11.x Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0.x Aternity 10.x Agent 9.0.x, 9.1.7, 9.2.5 or 9.2.6. Aternity 9.x Agent 9.0.x ONLY. Attribute Requirement Windows operating system Device must have: (For servers): Windows Server 2016 64-bit, Windows Server 2012 R2 64-bit, or Windows Server 2008 R2 64-bit. (For devices with Agent up to 12.0.x): Microsoft Windows 10, 8.1, or Windows 7 SP1 (with KB3125574) Enterprise / Professional 32-bit and 64-bit (32-bit requires Agent 9.0.6 or later). (For devices with Agent 12.1 or later): Microsoft Windows Server 2016 64-bit, or Microsoft Windows Server 2012 R2 64-bit, or Microsoft Windows 10, or Microsoft Windows 8.1, or Microsoft Windows Server 2008 R2 or later 64-bit (Enterprise / Professional), or Windows 7 SP1 (with KB3125574) or later 64-bit (Enterprise / Professional). Monitored web applications Agent 11.x can monitor a web (cloud) application running in any of the following Windows browsers: Chromium-based Microsoft Edge version 88 and above. Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Without this, Aternity only monitors clicking a link, back, forward, direct URL, HTTP GET and POST events. Monitor only managed applications with custom activities or page load activities (WPM) in Firefox (beta) single process mode versions 38 ESR, 45 ESR or 52 ESR. Contact Customer Services if you have versions 45 ESR or 52 ESR to enable monitoring of custom activities, and to ensure they are compatible with your Firefox. Agent 12.0.x (unlike Agent 11.x) monitors managed applications with custom activities or page load activities (WPM) in Firefox (beta) version 60.4 and above. Connectivity The Agent sends monitoring data to Aternity (including IP v6 for Agent 11 or later) using HTTPS over port 443. Tip Aternity gathers and stores detailed performance data. To view older data, it displays a condensed summary (aggregated data), like an hourly or daily summary. The Agent for End User Devices reports data to Aternity once every minute. If its status becomes disconnected and it cannot send data after trying for five minutes, it locally stores up to 50 minutes of retention data in offline mode, and then sends it when it renews its connection. The device continuously tries to reconnect to Aternity in ever-increasing intervals, after ½ minute, one minute, two minutes, four minutes, eight minutes, 16 minutes, 32 minutes, and if it still fails, the Agent restarts itself and tries again to connect, restarting this cycle again. Resource usage A local Agent in Windows typically uses: CPU: Total utilization across all cores approx. 0.12%. For virtual application servers and MS Terminal Server: typically 5-15%. RAM: Approx. 120MB physical memory (private working set). For virtual application servers and MS Terminal Server, add 40MB per session. Storage: Approx. 110MB, plus Agent log files (10MB to log only errors, or up to 740MB for complete logs). In rare support-led troubleshooting cases, log files can reach up to 3GB. Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity. Microsoft .NET (For Agent for End User Devices 12.0 or earlier) Device must have Microsoft .NET v4.5 SP1 or later to use security (TLS 1.2). (For Agent for End User Devices 12.1 or later) Device must have Microsoft .NET v4.6 SP2 or later to use security (TLS 1.2). Install privileges You must run the Agent setup with administrator privileges on the device. Permissions The Agent must have write access to the registry during the installation and while the Agent is running. The Agent must have permissions to write to the allusersprofile\aternity directory. Global security policies Enable and configure accordingly the Global Security Policies such as GPOs to ensure the Aternity Agent is able to inject into the desired monitored application. Aternity HTML hook is needed to monitor any web based application. If Enable third-party browser extensions is disabled, the hook will be unable to inject. This setting must be enabled or a GPO must be created and/or modified to add our hook to the exclusions. Virtual Windows Devices (Running the Windows Agent) Aternity monitors performance in a wide range of virtual applications and virtual desktops. The virtual servers must be housed in one of the following operating systems: Attribute Requirement Virtual server operating system Windows Server 2016, 2012 R2, 2012, 2008 R2 or 2019. The Windows Agent supports virtual devices and/or virtual applications with any of the following requirements: Attribute Requirement Citrix virtual application servers (Legacy naming up to v7.18) Citrix XenApp 6.5, 7.6, 7.8, 7.15, 7.18 (New naming from v7.19) Citrix Virtual Apps 7.19. Citrix virtual desktop servers (Legacy naming up to v7.18) Citrix XenDesktop 6.5, 7.6, 7.8, 7.15, 7.18 (New naming from v7.19) Citrix Virtual Desktops 7.19 VMWare Enterprise VDI VDI support is for VMWare Horizon View up to 8.0. Aternity does not monitor the ESXi hypervisor. VMWare ThinApp is NOT supported. Microsoft RDC Microsoft Remote Desktop Services 6.1, 8.1, 10.0. Microsoft virtual application servers Microsoft App-V 4.6 SP3, 5.0, 5.1. Azure Windows Virtual Desktop (WVD) Windows 10 Enterprise multi-session or Windows 10 Enterprise Mac Computers (Running the Aternity Agent for Mac) To monitor an Apple Mac with Aternity Agent for Mac, it must have the following minimum system requirements: Attribute Requirement Agent for Mac Supported versions of Agent for Mac: 3.0, 3.1.x, 3.2.x, 3.3, 3.4 Mac operating system macOS 11 (Big Sur) since Agent for Mac 3.4 macOS 10.15 (Catalina) since Agent for Mac 3.3 macOS 10.14 (Mojave) since Agent for Mac 3.1 macOS 10.13 (High Sierra) since Agent for Mac 2.4 macOS 10.12 (Sierra) macOS 10.11 (El Capitan) macOS 10.10 (Yosemite) Processor Mac computer with Intel 64-bit CPU Mac computer with Apple M1 CPU (since Agent for Mac 3.4) Resource usage The Agent for Mac typically uses: CPU: Total utilization across all cores less than 1%. RAM: The Aternity Agent for Mac uses up to 650MB of physical memory. Storage: At least 0.5GB free disk space available. Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity. Monitor web applications Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Mobile Devices (Running a Monitored Mobile App) To run a monitored app, the device must have the following operating systems: Attribute Requirement iOS operating system of monitored device iOS 9 and up to iOS 12. Android operating system of monitored device Android 4.4 and up to Android 9. Embed Mobile Monitoring (Aternity Wrapper and Aternity Mobile SDK) To add monitoring to a mobile app, you must embed Aternity's monitoring into the app itself, before it is encrypted. Before embedding Aternity's monitoring into an iOS mobile app, verify your Mac conforms to the following minimum system requirements (Aternity iOS Wrapper and Aternity iOS Mobile SDK): Attribute Requirement (iOS Wrapper and Aternity iOS SDK) Operating system Mac OS X 10.10 or later. Programming environment Apple XCode 7 or newer. Connectivity Internet access. App resource usage When you add Aternity functionality to an iOS app: Disk storage size increases by 3.3MB. RAM size is an extra 5-10MB. CPU usage rises by 1%. Before embedding Aternity's monitoring into an Android mobile app, verify your device conforms to the following minimum system requirements (Aternity Android Wrapper or Aternity Android Mobile SDK): Attribute Requirement (Android Wrapper and Aternity Android SDK) Operating system Android 4.4 or later. Java Developer Kit JDK 1.8 or later. Programming environment Google Android Studio or a standalone Android SDK. Using the SDK Manager, install the latest Android SDK tools (platform tools and build tools) for SDK Platform API level 19 or newer. Connectivity Internet access. App resource usage When you add Aternity functionality to an Android app: Disk storage barely changes at all. RAM size is an extra 5-10MB. CPU usage rises by 1%. Aternity Oracle Database Server (Oracle) The Aternity Oracle Database Server is an Oracle database which hosts the Aternity system settings, data model and performance data, after the Data Warehouse Server summarized (aggregated) it. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Hard disk for express database setup of the Aternity Oracle Database Server The express database setup requires: System disk (C drive) A logical or physical drive other than the system disk, with the free space required for your deployment size Oracle version for Aternity Oracle Database Server Use Oracle 19.0.0.0 or 18.0.0.0 or 12.2.0.1 or 12.1.0.2 or 11.2.0.4 (including support for Oracle Data Guard), specifically: Oracle Database version 11.2.0.4 Enterprise Edition 64-bit Oracle Database version 12c Enterprise Edition 64-bit, 12.2.0.1 or 12.1.0.2 Oracle Database version 18c Enterprise Edition 64-bit, 18.0.0.0 Oracle Database version 19c Enterprise Edition 64-bit, 19.0.0.0 Note You do not need to update your Oracle if you already have one of these versions. The Oracle license MUST allow for Partitioning, Parallel, and Advanced Compression. However the other licensing features are optional, depending on your enterprise's policy and requirements: (Diagnostics and Tuning Pack and the Active Data Guard). You can download either version of Oracle from the Additional Packages page of the Aternity Support Site. Operating system for Aternity Oracle Database Server (For express database setup) Windows Server 64 bit 2012 R2 or Windows Server 64 bit 2016. (Full setup) Windows Server 64 bit 2016 or 2012 R2. In either case: Set the date and time formats to Control Panel > Regions > Formats > English (United States). (Full setup only) You can also install the Oracle Database Server on Linux CentOS or Linux Red Hat Fedora. RAM for Aternity Oracle Database Server (express setup and full setup) (Express setup) The express database setup automatically detects the RAM and configures the database: For 3-11GB RAM, the database supports up to 100 monitored devices. For more than 11GB RAM, the database supports up to 3000 monitored devices. (Full setup) Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Vertica Database Server Vertica is a third-party column-store database optimized for large volume data analytics. The Aternity Vertica Database Server stores the performance data in the Vertica format, which is most efficient for displaying in Aternity dashboards. It receives its data from the Aternity Docker Components Server. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Operating system for Aternity Vertica Database Server Linux CentOS 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify your version of CentOS, enter cat /etc/centos-release Red Hat Enterprise Linux (RHEL) 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify the RHEL version, enter cat /etc/redhat-release Note If you set up a trial deployment using VMWare virtual machines, the operating system in the OVA file comes with CentOS 7.8. Verify that the disk partition dedicated to the Vertica data folder (Target directory) uses the EXT4 file system. Enter df -Th to verify. If you deploy on virtual machines, you MUST define all resources as dedicated or reserved (Resource Allocation > Reservation). In addition, you can use a Logical Volume Manager (LVM) in Aternity 12 on any hard drive with no restrictions. See Vertica limitations for LVM. Partitions Verify that the disk partition dedicated to the Vertica data folder (Target directory) uses the EXT4 file system. Enter df -Th to verify. Permissions Create the exact same user with the same permissions on each computer. Run the setup as a user with root or sudo root privileges on the computer. To verify, enter sudo id. If you run the setup as a user with sudo permissions that requires a password, setup will prompt you for the password. If the sudo user does not require a password, the setup does not interrupt the process with those prompts. Vertica version for Aternity Vertica Database Server Aternity 12.0 requires that your Vertica Database Server runs HPE Vertica 9.2.1.-11. You can download this with the rest of the Aternity on-premise package. Resource limits for Vertica DBA user The Vertica DBA user must have bash as its shell, and have read, write and execute permissions on its home folder. (For several nodes in a cluster) It must also be able to SSH to other nodes in the cluster. The Vertica DBA user must have an open file limit of 65536 or more. The setup script automatically assigns this setting to the DBA user. You can enter a DBA username, password and group in the parameters file, or keep the name which is predefined (dbadmin), if the username does not exist, the script creates it with these properties. Network Ensure this server has a static IP v4 address, and that you open the required ports. Time zone Synchronize all Aternity components to have the same date, time AND time zone. Aternity Dashboard Server (Tableau) The Dashboard Server displays Aternity's intuitive dashboards using Tableau as its engine. It presents the data from the Aternity Vertica Database Server. The Aternity Dashboard Server is a server running the version of Tableau which is compatible with this version of Aternity. For more information on the requirements of Tableau, see Tableau documentation. Attribute Requirement Operating system for Dashboard Server Use any of the following: Windows Server 2016 64 bit or Windows Server 2012 R2 64 bit (with KB2919355 and KB2999226) (install KB2919355 first, and only then KB2999226) or Set the date and time formats to Control Panel > Regions > Formats > English (United States). Time zone Synchronize all Aternity components to have the same date, time AND time zone. Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Microsoft .NET Ensure this server has Microsoft .NET 3.5 (exactly) required for the database drivers, and .NET 4.5 or later, required for driver setup (both in parallel). To add .NET to a Windows Server, learn more. Tableau version for Dashboard Server Aternity 12.0 requires that your Dashboard Server runs Tableau Server 2019.3.10 (using Tomcat 7.0.91, Apache httpd 2.4.41). Network Ensure this server has a static IP v4 address, and that you open the required ports. Connectivity for Dashboard Server This server must be open for access on port 80 or 443 from the Aternity Management Server and users accessing the Aternity dashboards from their browser. This server requires internet access (port 80) to connect to Tableau's map service to render Aternity's geographic maps correctly. In addition, open port 8000 on the Windows Firewall for Tableau's internal load balancer. Check Tableau's online help for a full list of required open ports. Permissions for Dashboard Server You may need either local or domain administrator privileges on this computer. Verify that the Windows account which is going to set up this server has permission to read, write, list and execute in the Tableau Server setup directory and its sub-folders. Learn more. Aternity Management Server and Aternity Data Warehouse Server The Aternity Management Server acts as Aternity's central server, which manages and integrates all the components. When users access Aternity to view the dashboards or configure it, they access this server via a browser. The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Oracle Database Server and the Aternity Vertica Database Server. Both these servers require the following: Attribute Requirement Operating system for Management Server and Data Warehouse Server Windows Server 64 bit 2016 or 2012 R2 64 bit. Set the date and time formats to Control Panel > Regions > Formats > English (United States). Both servers set up and use Apache Tomcat 8.5.32. Note Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Aggregation Server An Aggregation Server gathers (aggregates) the data directly from Agent for End User Devicess on monitored devices, and passes it on to the Management Server. Attribute Requirement Operating system for Aternity Aggregation Server Windows Server 64 bit 2016 or 2012 R2 64 bit Enterprise Edition. Set the date and time formats to Control Panel > Regions > Formats > English (United States). The Aggregation Server sets up and uses Apache Tomcat 8.5.32. You can also deploy the Aternity Aggregation Server on Linux CentOS or Linux RedHat Fedora. Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Docker Components Server The Aternity Docker Components Server is the on-premise server that hosts all Aternity Docker services which provide multiple different functionalities to Aternity. Most components are mandatory, but you can choose to add or omit some of the optional components and their associated functionality. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Network Ensure this server has a static IP v4 address, and that you open the required ports. Operating system for Aternity Docker Components Server Linux CentOS 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify your version of CentOS, enter cat /etc/centos-release Red Hat Enterprise Linux (RHEL) 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify the RHEL version, enter cat /etc/redhat-release Docker version for Aternity Docker Components Server Aternity does not supply the Docker engine. Customers are responsible for its installation. It is required for the Aternity Docker Components Server, regardless of operating system. On CentOS, Aternity supports Docker for CentOS 17.x or 18.x. Learn more. Use either the Community Edition (CE) or the Enterprise Edition (EE). EE requires subscription, while CE is free. On Red Hat Enterprise Linux (RHEL), Aternity supports Docker 1.13, 17.x, and 18.x, but only 1.13 version is free. RHEL Docker 17.x and 18.x (Enterprise Edition) are only available for RHEL with a paid subscription to Docker. After you set up the Docker engine and run it, you can set up the Docker Components from a Docker image file. If you do not have an internet access, follow the procedure explained here. You can always go to the Docker website to learn more. Permissions (Aternity on-premise 11.0.2) Only users who are defined in the sudoers file can run the setup of Aternity Docker Components Server. Start as a non-root user and follow the setup procedure. At some point, you will be prompted to ask your IT representative to define permissions in the sudoers file. It is possible to run the setup as root user on the computer if this user is defined in the sudoers file as well. (Aternity on-premise 11.0.0 and 11.0.1) Run the setup as a user with root or sudo root privileges on the computer. To verify, enter sudo id. If you run the setup as a user with sudo permissions that requires a password, setup will prompt you for the password. If the sudo user does not require a password, the setup does not interrupt the process with those prompts. Time zone Synchronize all Aternity components to have the same date, time AND time zone.
Software System Requirements for Aternity 11 Servers and Devices (Agents) This section details the minimum software system requirements to install and run the components of Aternity. Important Synchronize all Aternity components to have the same date, time AND time zone. Access Aternity Dashboards and Settings Sign in to Aternity by entering the hostname of your on-premise Aternity Management Server (like https://aternity.mycompany.com/) in a Windows browser on a monitor with resolution 1280 x 768 or more. You can view Aternity in: Google Chrome version 42 and above. Microsoft Internet Explorer version 11 and 11 Enterprise Mode, with Compatibility Mode disabled and third-party browser extensions enabled. Note To use Chrome to display some administration screens (which use Flex), perform the procedure explained here to install and use a dedicated desktop application to securely access the Aternity administrative screens. To access this link, you need to sign in to the Aternity Support Site. Learn more. Windows Devices (Running Windows Agent) Each monitored Windows device must have the following minimum system requirements to install the Agent for End User Devices locally: Important Aternity on-premise 12.x requires that devices run Agent for End User Devices 9.0, 9.1.7, 9.2.x, 11.0.x, 12.0.x or Agent 12.1.x. Product Supported Agent for End User Devices Aternity 12.x Agent 9.0, 9.1.7, 9.2.x, 11.0.x, 12.0.x or Agent 12.1.x Aternity 11.x Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0.x Aternity 10.x Agent 9.0.x, 9.1.7, 9.2.5 or 9.2.6. Aternity 9.x Agent 9.0.x ONLY. Attribute Requirement Windows operating system Device must have: (For servers): Windows Server 2016 64-bit, Windows Server 2012 R2 64-bit, or Windows Server 2008 R2 64-bit. (For devices with Agent up to 12.0.x): Microsoft Windows 10, 8.1, or Windows 7 SP1 (with KB3125574) Enterprise / Professional 32-bit and 64-bit (32-bit requires Agent 9.0.6 or later). (For devices with Agent 12.1 or later): Microsoft Windows Server 2016 64-bit, or Microsoft Windows Server 2012 R2 64-bit, or Microsoft Windows 10, or Microsoft Windows 8.1, or Microsoft Windows Server 2008 R2 or later 64-bit (Enterprise / Professional), or Windows 7 SP1 (with KB3125574) or later 64-bit (Enterprise / Professional). Monitored web applications Agent 11.x can monitor a web (cloud) application running in any of the following Windows browsers: Chromium-based Microsoft Edge version 88 and above. Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Without this, Aternity only monitors clicking a link, back, forward, direct URL, HTTP GET and POST events. Monitor only managed applications with custom activities or page load activities (WPM) in Firefox (beta) single process mode versions 38 ESR, 45 ESR or 52 ESR. Contact Customer Services if you have versions 45 ESR or 52 ESR to enable monitoring of custom activities, and to ensure they are compatible with your Firefox. Agent 12.0.x (unlike Agent 11.x) monitors managed applications with custom activities or page load activities (WPM) in Firefox (beta) version 60.4 and above. Connectivity The Agent sends monitoring data to Aternity (including IP v6 for Agent 11 or later) using HTTPS over port 443. Tip Aternity gathers and stores detailed performance data. To view older data, it displays a condensed summary (aggregated data), like an hourly or daily summary. The Agent for End User Devices reports data to Aternity once every minute. If its status becomes disconnected and it cannot send data after trying for five minutes, it locally stores up to 50 minutes of retention data in offline mode, and then sends it when it renews its connection. The device continuously tries to reconnect to Aternity in ever-increasing intervals, after ½ minute, one minute, two minutes, four minutes, eight minutes, 16 minutes, 32 minutes, and if it still fails, the Agent restarts itself and tries again to connect, restarting this cycle again. Resource usage A local Agent in Windows typically uses: CPU: Total utilization across all cores approx. 0.12%. For virtual application servers and MS Terminal Server: typically 5-15%. RAM: Approx. 120MB physical memory (private working set). For virtual application servers and MS Terminal Server, add 40MB per session. Storage: Approx. 110MB, plus Agent log files (10MB to log only errors, or up to 740MB for complete logs). In rare support-led troubleshooting cases, log files can reach up to 3GB. Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity. Microsoft .NET (For Agent for End User Devices 12.0 or earlier) Device must have Microsoft .NET v4.5 SP1 or later to use security (TLS 1.2). (For Agent for End User Devices 12.1 or later) Device must have Microsoft .NET v4.6 SP2 or later to use security (TLS 1.2). Install privileges You must run the Agent setup with administrator privileges on the device. Permissions The Agent must have write access to the registry during the installation and while the Agent is running. The Agent must have permissions to write to the allusersprofile\aternity directory. Global security policies Enable and configure accordingly the Global Security Policies such as GPOs to ensure the Aternity Agent is able to inject into the desired monitored application. Aternity HTML hook is needed to monitor any web based application. If Enable third-party browser extensions is disabled, the hook will be unable to inject. This setting must be enabled or a GPO must be created and/or modified to add our hook to the exclusions. Virtual Windows Devices (Running the Windows Agent) Aternity monitors performance in a wide range of virtual applications and virtual desktops. The virtual servers must be housed in one of the following operating systems: Attribute Requirement Virtual server operating system Windows Server 2016, 2012 R2, 2012, 2008 R2 or 2019. The Windows Agent supports virtual devices and/or virtual applications with any of the following requirements: Attribute Requirement Citrix virtual application servers (Legacy naming up to v7.18) Citrix XenApp 6.5, 7.6, 7.8, 7.15, 7.18 (New naming from v7.19) Citrix Virtual Apps 7.19. Citrix virtual desktop servers (Legacy naming up to v7.18) Citrix XenDesktop 6.5, 7.6, 7.8, 7.15, 7.18 (New naming from v7.19) Citrix Virtual Desktops 7.19 VMWare Enterprise VDI VDI support is for VMWare Horizon View up to 8.0. Aternity does not monitor the ESXi hypervisor. VMWare ThinApp is NOT supported. Microsoft RDC Microsoft Remote Desktop Services 6.1, 8.1, 10.0. Microsoft virtual application servers Microsoft App-V 4.6 SP3, 5.0, 5.1. Azure Windows Virtual Desktop (WVD) Windows 10 Enterprise multi-session or Windows 10 Enterprise Mac Computers (Running the Aternity Agent for Mac) To monitor an Apple Mac with Aternity Agent for Mac, it must have the following minimum system requirements: Attribute Requirement Agent for Mac Supported versions of Agent for Mac: 3.0, 3.1.x, 3.2.x, 3.3, 3.4 Mac operating system macOS 11 (Big Sur) since Agent for Mac 3.4 macOS 10.15 (Catalina) since Agent for Mac 3.3 macOS 10.14 (Mojave) since Agent for Mac 3.1 macOS 10.13 (High Sierra) since Agent for Mac 2.4 macOS 10.12 (Sierra) macOS 10.11 (El Capitan) macOS 10.10 (Yosemite) Processor Mac computer with Intel 64-bit CPU Mac computer with Apple M1 CPU (since Agent for Mac 3.4) Resource usage The Agent for Mac typically uses: CPU: Total utilization across all cores less than 1%. RAM: The Aternity Agent for Mac uses up to 650MB of physical memory. Storage: At least 0.5GB free disk space available. Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity. Monitor web applications Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Mobile Devices (Running a Monitored Mobile App) To run a monitored app, the device must have the following operating systems: Attribute Requirement iOS operating system of monitored device iOS 9 and up to iOS 12. Android operating system of monitored device Android 4.4 and up to Android 9. Embed Mobile Monitoring (Aternity Wrapper and Aternity Mobile SDK) To add monitoring to a mobile app, you must embed Aternity's monitoring into the app itself, before it is encrypted. Before embedding Aternity's monitoring into an iOS mobile app, verify your Mac conforms to the following minimum system requirements (Aternity iOS Wrapper and Aternity iOS Mobile SDK): Attribute Requirement (iOS Wrapper and Aternity iOS SDK) Operating system Mac OS X 10.10 or later. Programming environment Apple XCode 7 or newer. Connectivity Internet access. App resource usage When you add Aternity functionality to an iOS app: Disk storage size increases by 3.3MB. RAM size is an extra 5-10MB. CPU usage rises by 1%. Before embedding Aternity's monitoring into an Android mobile app, verify your device conforms to the following minimum system requirements (Aternity Android Wrapper or Aternity Android Mobile SDK): Attribute Requirement (Android Wrapper and Aternity Android SDK) Operating system Android 4.4 or later. Java Developer Kit JDK 1.8 or later. Programming environment Google Android Studio or a standalone Android SDK. Using the SDK Manager, install the latest Android SDK tools (platform tools and build tools) for SDK Platform API level 19 or newer. Connectivity Internet access. App resource usage When you add Aternity functionality to an Android app: Disk storage barely changes at all. RAM size is an extra 5-10MB. CPU usage rises by 1%. Aternity Oracle Database Server (Oracle) The Aternity Oracle Database Server is an Oracle database which hosts the Aternity system settings, data model and performance data, after the Data Warehouse Server summarized (aggregated) it. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Hard disk for express database setup of the Aternity Oracle Database Server The express database setup requires: System disk (C drive) A logical or physical drive other than the system disk, with the free space required for your deployment size Oracle version for Aternity Oracle Database Server Use Oracle 19.0.0.0 or 18.0.0.0 or 12.2.0.1 or 12.1.0.2 or 11.2.0.4 (including support for Oracle Data Guard), specifically: Oracle Database version 11.2.0.4 Enterprise Edition 64-bit Oracle Database version 12c Enterprise Edition 64-bit, 12.2.0.1 or 12.1.0.2 Oracle Database version 18c Enterprise Edition 64-bit, 18.0.0.0 Oracle Database version 19c Enterprise Edition 64-bit, 19.0.0.0 Note You do not need to update your Oracle if you already have one of these versions. The Oracle license MUST allow for Partitioning, Parallel, and Advanced Compression. However the other licensing features are optional, depending on your enterprise's policy and requirements: (Diagnostics and Tuning Pack and the Active Data Guard). You can download either version of Oracle from the Additional Packages page of the Aternity Support Site. Operating system for Aternity Oracle Database Server (For express database setup) Windows Server 64 bit 2012 R2 or Windows Server 64 bit 2016. (Full setup) Windows Server 64 bit 2016 or 2012 R2. In either case: Set the date and time formats to Control Panel > Regions > Formats > English (United States). (Full setup only) You can also install the Oracle Database Server on Linux CentOS or Linux Red Hat Fedora. RAM for Aternity Oracle Database Server (express setup and full setup) (Express setup) The express database setup automatically detects the RAM and configures the database: For 3-11GB RAM, the database supports up to 100 monitored devices. For more than 11GB RAM, the database supports up to 3000 monitored devices. (Full setup) Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Vertica Database Server Vertica is a third-party column-store database optimized for large volume data analytics. The Aternity Vertica Database Server stores the performance data in the Vertica format, which is most efficient for displaying in Aternity dashboards. It receives its data from the Aternity Docker Components Server. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Operating system for Aternity Vertica Database Server Linux CentOS 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify your version of CentOS, enter cat /etc/centos-release Red Hat Enterprise Linux (RHEL) 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify the RHEL version, enter cat /etc/redhat-release Note If you set up a trial deployment using VMWare virtual machines, the operating system in the OVA file comes with CentOS 7.8. Verify that the disk partition dedicated to the Vertica data folder (Target directory) uses the EXT4 file system. Enter df -Th to verify. If you deploy on virtual machines, you MUST define all resources as dedicated or reserved (Resource Allocation > Reservation). In addition, you can use a Logical Volume Manager (LVM) in Aternity 12 on any hard drive with no restrictions. See Vertica limitations for LVM. Partitions Verify that the disk partition dedicated to the Vertica data folder (Target directory) uses the EXT4 file system. Enter df -Th to verify. Permissions Create the exact same user with the same permissions on each computer. Run the setup as a user with root or sudo root privileges on the computer. To verify, enter sudo id. If you run the setup as a user with sudo permissions that requires a password, setup will prompt you for the password. If the sudo user does not require a password, the setup does not interrupt the process with those prompts. Vertica version for Aternity Vertica Database Server Aternity 12.0 requires that your Vertica Database Server runs HPE Vertica 9.2.1.-11. You can download this with the rest of the Aternity on-premise package. Resource limits for Vertica DBA user The Vertica DBA user must have bash as its shell, and have read, write and execute permissions on its home folder. (For several nodes in a cluster) It must also be able to SSH to other nodes in the cluster. The Vertica DBA user must have an open file limit of 65536 or more. The setup script automatically assigns this setting to the DBA user. You can enter a DBA username, password and group in the parameters file, or keep the name which is predefined (dbadmin), if the username does not exist, the script creates it with these properties. Network Ensure this server has a static IP v4 address, and that you open the required ports. Time zone Synchronize all Aternity components to have the same date, time AND time zone. Aternity Dashboard Server (Tableau) The Dashboard Server displays Aternity's intuitive dashboards using Tableau as its engine. It presents the data from the Aternity Vertica Database Server. The Aternity Dashboard Server is a server running the version of Tableau which is compatible with this version of Aternity. For more information on the requirements of Tableau, see Tableau documentation. Attribute Requirement Operating system for Dashboard Server Use any of the following: Windows Server 2016 64 bit or Windows Server 2012 R2 64 bit (with KB2919355 and KB2999226) (install KB2919355 first, and only then KB2999226) or Set the date and time formats to Control Panel > Regions > Formats > English (United States). Time zone Synchronize all Aternity components to have the same date, time AND time zone. Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Microsoft .NET Ensure this server has Microsoft .NET 3.5 (exactly) required for the database drivers, and .NET 4.5 or later, required for driver setup (both in parallel). To add .NET to a Windows Server, learn more. Tableau version for Dashboard Server Aternity 12.0 requires that your Dashboard Server runs Tableau Server 2019.3.10 (using Tomcat 7.0.91, Apache httpd 2.4.41). Network Ensure this server has a static IP v4 address, and that you open the required ports. Connectivity for Dashboard Server This server must be open for access on port 80 or 443 from the Aternity Management Server and users accessing the Aternity dashboards from their browser. This server requires internet access (port 80) to connect to Tableau's map service to render Aternity's geographic maps correctly. In addition, open port 8000 on the Windows Firewall for Tableau's internal load balancer. Check Tableau's online help for a full list of required open ports. Permissions for Dashboard Server You may need either local or domain administrator privileges on this computer. Verify that the Windows account which is going to set up this server has permission to read, write, list and execute in the Tableau Server setup directory and its sub-folders. Learn more. Aternity Management Server and Aternity Data Warehouse Server The Aternity Management Server acts as Aternity's central server, which manages and integrates all the components. When users access Aternity to view the dashboards or configure it, they access this server via a browser. The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Oracle Database Server and the Aternity Vertica Database Server. Both these servers require the following: Attribute Requirement Operating system for Management Server and Data Warehouse Server Windows Server 64 bit 2016 or 2012 R2 64 bit. Set the date and time formats to Control Panel > Regions > Formats > English (United States). Both servers set up and use Apache Tomcat 8.5.32. Note Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Aggregation Server An Aggregation Server gathers (aggregates) the data directly from Agent for End User Devicess on monitored devices, and passes it on to the Management Server. Attribute Requirement Operating system for Aternity Aggregation Server Windows Server 64 bit 2016 or 2012 R2 64 bit Enterprise Edition. Set the date and time formats to Control Panel > Regions > Formats > English (United States). The Aggregation Server sets up and uses Apache Tomcat 8.5.32. You can also deploy the Aternity Aggregation Server on Linux CentOS or Linux RedHat Fedora. Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Aternity Docker Components Server The Aternity Docker Components Server is the on-premise server that hosts all Aternity Docker services which provide multiple different functionalities to Aternity. Most components are mandatory, but you can choose to add or omit some of the optional components and their associated functionality. Attribute Requirement Hardware Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size. Network Ensure this server has a static IP v4 address, and that you open the required ports. Operating system for Aternity Docker Components Server Linux CentOS 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify your version of CentOS, enter cat /etc/centos-release Red Hat Enterprise Linux (RHEL) 7.4 or 7.5 or 7.6 or 7.7 or 7.8. To verify the RHEL version, enter cat /etc/redhat-release Docker version for Aternity Docker Components Server Aternity does not supply the Docker engine. Customers are responsible for its installation. It is required for the Aternity Docker Components Server, regardless of operating system. On CentOS, Aternity supports Docker for CentOS 17.x or 18.x. Learn more. Use either the Community Edition (CE) or the Enterprise Edition (EE). EE requires subscription, while CE is free. On Red Hat Enterprise Linux (RHEL), Aternity supports Docker 1.13, 17.x, and 18.x, but only 1.13 version is free. RHEL Docker 17.x and 18.x (Enterprise Edition) are only available for RHEL with a paid subscription to Docker. After you set up the Docker engine and run it, you can set up the Docker Components from a Docker image file. If you do not have an internet access, follow the procedure explained here. You can always go to the Docker website to learn more. Permissions (Aternity on-premise 11.0.2) Only users who are defined in the sudoers file can run the setup of Aternity Docker Components Server. Start as a non-root user and follow the setup procedure. At some point, you will be prompted to ask your IT representative to define permissions in the sudoers file. It is possible to run the setup as root user on the computer if this user is defined in the sudoers file as well. (Aternity on-premise 11.0.0 and 11.0.1) Run the setup as a user with root or sudo root privileges on the computer. To verify, enter sudo id. If you run the setup as a user with sudo permissions that requires a password, setup will prompt you for the password. If the sudo user does not require a password, the setup does not interrupt the process with those prompts. Time zone Synchronize all Aternity components to have the same date, time AND time zone.