Software System Requirements for Aternity 10 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 SteelCentral Aternityâ„¢ from within a web browser, by entering the hostname of your on-premise Aternity Management Server (like https://aternity.mycompany.com/), on a monitor resolution of at least 1280 x 768, using any of the following Windows supported browsers:

  • Google Chrome version 42 and above.

  • Microsoft Internet Explorer version 11 and 11 Enterprise Mode, with Compatibility Mode disabled.

    Note

    To use Chrome to display some administration screens (which use Flex), you must enable Flash by selecting the web icon in the address bar then select to always allow Flash on this site.

    Enable Flash in Chrome to view Aternity administration screens

Windows Devices (Running Windows Agent)

Each monitored Windows device must have the following minimum system requirements to install the Aternity Agent locally:

Important

Aternity on-premise 10 requires that devices ONLY run Aternity Agent 9.0.x, 9.1.7 or 9.2.5.

Product Supported Aternity Agent
Aternity 10.x

Aternity Agent 9.0.x, 9.1.7 or 9.2.5 ONLY.

Aternity 9.x

Aternity Agent 9.0.x ONLY.

Attribute Requirement

Windows operating system

Device must have:

  • 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 servers: Windows Server 2016, Windows Server 2012 64-bit, and Windows Server 2008 R2 64-bit.

Monitored web applications

Agent 9.x can monitor a web (cloud) application running in any of the following Windows browsers:

  • 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 any web application in Microsoft Internet Explorer v9, 10 or 11. For legacy until Agent 9.2.3, monitor discovered web apps by disabling IE's compatibility mode (learn more).

  • 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.

Connectivity

The Agent sends monitoring data to Aternity (including IP v6 for Agent 10 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 Aternity Agent 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.

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

Device must have Microsoft .NET v4.5 SP1 or later to use security (TLS 1.2).

Install privileges

You must run the Agent setup with administrator privileges on the device.

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, or 2008 R2.

The Windows Agent supports virtual devices and/or virtual applications with any of the following requirements:

Attribute Requirement

Citrix virtual application servers

Citrix XenApp 6.5, 7.6, 7.8, 7.15.

Citrix virtual desktop servers

Citrix XenDesktop 6.5, 7.6, 7.15.

VMWare Enterprise VDI

VDI support is for VMWare Horizon View 6.x and 7.x up to 7.2 (certified support for version 6.2). 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.

Mac Computers (Running the Aternity Agent for Mac beta)

To monitor an Apple Mac with Aternity Agent for Mac, it must have the following minimum system requirements:

Attribute Requirement

Mac operating system

macOS 10.14 (since version 3.1), macOS 10.13 (High Sierra) (since version 2.4), macOS 10.12 (Sierra), OS X 10.11 (El Capitan), or OS X 10.10 (Yosemite)

Processor

Mac computer with Intel 64-bit CPU.

Disk space

At least 0.5GB free disk space available.

RAM

The Aternity Agent for Mac uses less than 100MB RAM.

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 10 or later.

Android operating system of monitored device

Android 4.4 or later.

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.

Java Developer Kit

JDK 1.8 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 Mac 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

Mac OS X 10.10 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.

In addition, check the ports which you must open on this server (learn more).

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

For Aternity 10.x, use Oracle 12.1.0.2 or 11.2.0.4 (including support for Oracle Data Guard), specifically:

  • Aternity 10.x requires Oracle Database version 12c Enterprise Edition 64-bit, 12.1.0.2 or Oracle Database 11gR2 Enterprise Edition 64-bit with patch set 11.2.0.4.

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 Related Links of the Riverbed support site.

Operating system for Aternity Oracle Database Server

(For express database setup) Windows Server 64 bit 2012 R2.

(Full setup) Windows Server 64 bit 2016 (for Aternity 10.0.1 only), 2012 R2 or 2008 R2 Enterprise Edition.

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 5.8 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:

(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

The Aternity Vertica Database Server stores the performance data from the past 31 days in the Vertica format, which is most efficient for displaying in Aternity dashboards. It receives its data from the Aternity ETL Server, which translates performance data from the Aternity Oracle Database Server to this 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.

In addition, check the ports which you must open on this server (learn more).

Operating system for Aternity Vertica Database Server

  • Linux CentOS 7.3 - 7.5. To verify your version of CentOS, enter cat /etc/centos-release

  • (Aternity 10.0.1) Red Hat Enterprise Linux (RHEL) 7.4 or 7.5.

    (Aternity 10.0) Red Hat Enterprise Linux (RHEL) 7.4.

    To verify the RHEL version, enter cat /etc/redhat-release

Verify that the disk partition 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, if you want to use a Logical Volume Manager (LVM), you can use it in Aternity 10.0 on any partition other than the one used for the data and catalog folders. Vertica 8.0.1 in Aternity 10.0 does not support LVM for the partition where the data and catalog folders are stored. See Vertica limitations. However, in Aternity 10.0.1 with Vertica 8.1.1 it is possible to use any partition for LVM, including the one where the data and catalog folders are stored.

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 10.0.1 requires that your Vertica Database Server runs HPE Vertica 8.1.1 (for Aternity 10.0 it is Vertica 8.0.1). 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

Windows Server 64 bit 2016 (for Aternity 10.0.1 only), or 2012 R2, or 2008 R2 Enterprise Edition (with KB2117917). 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.

In addition, check the ports which you must open on this server (learn more).

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 10.0 requires that your Dashboard Server runs Tableau Server 9.3.3 (using Tomcat 7.0.64). Aternity 10.0.1 runs Tableau Server 9.3.22 (using Tomcat 7.0.82).

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

Ensure you have local administrator privileges on this computer.

Verify the Local Service account of Windows 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 the system's central server, which manages and integrates all the system components. When users access Aternity to view the dashboards or configure the system, 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.

Both these servers require the following:

Attribute Requirement

Operating system for Management Server and Data Warehouse Server

Windows Server 64 bit 2016 (for Aternity 10.0.1 only), 2012 R2, 2012, or 2008 R2. Set the date and time formats to Control Panel > Regions > Formats > English (United States).

Both servers set up and use Apache Tomcat 8.5.14.

Hardware

Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size.

In addition, check the ports which you must open on this server (learn more).

Aternity Aggregation Server

An Aggregation Server gathers (aggregates) the data directly from Aternity Agents on monitored devices, and passes it on to the Management Server.

Attribute Requirement

Operating system for Aternity Aggregation Server

Windows Server 64 bit 2016 (for Aternity 10.0.1 only), 2012 R2 or 2008 R2 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.14.

Hardware

Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size.

In addition, check the ports which you must open on this server (learn more).

Aternity ETL Server

The Aternity ETL Server is a component of Aternity on-premise, which aggregates and converts performance data from the Aternity Oracle Database Server to the Vertica database format, and sends it to the Vertica Database 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.

In addition, check the ports which you must open on this server (learn more).

Network

Ensure this server has a static IP v4 address, and that you open the required ports.

Operating system for Aternity ETL Server

  • Linux CentOS 7.3 - 7.5. To verify your version of CentOS, enter cat /etc/centos-release For the kernel version, enter uname -r and see the first two numbers.

  • (Aternity 10.0.1) Red Hat Enterprise Linux (RHEL) 7.4 or 7.5.

    (Aternity 10.0) Red Hat Enterprise Linux (RHEL) 7.4.

    To verify the RHEL version, enter cat /etc/redhat-release

Virtual memory settings for Aternity ETL Server

Verify that your system has a swap file of at least 6GB which is active, by entering free -m.

To create a 6GB swap file and enable it, enter the following commands, one line at a time. For RHEL, enter:

dd if=/dev/zero of=/swapfile bs=1024 count=65536
mkswap /swapfile
swapon /swapfile

For CentOS systems, enter:

fallocate -l 6G /swapfile
mkswap /swapfile
swapon /swapfile

To set the swap file as permanent, edit the system partition settings in /etc/fstab in a plain text editor such as vim, and add the following line at the end of the file:

/swapfile   swap    swap    defaults    0 0

Then save and exit the text editor. The system enables the new swap file when you restart the server.

Chrony

The ETL Server setup script automatically uses a utility called Chrony, which comes with CentOS 7, to synchronize time and time zones between the Aternity components.

Important

Synchronize all Aternity components to have the same date, time AND time zone.

Confirm the system runs the Chrony utility, by entering systemctl status -l chronyd

If your system does not have Chrony, search for Chrony, download the version for CentOS 7, and enable it by entering yum install chrony.

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.

Resource limits for ETL Server

The user that runs the ETL Server must have an open file limit of 65536 or more.

Set the number by editing the system's resource limits in etc/security/limits.conf in a plain text editor like vim, and add the following line at the end of the file:

etl_username -     nofile  65536
If the username is root, enter
root -     nofile  65536

Now enter ulimit -n to verify the limit.

Then save and exit the editor.

Aternity Data Source for Portal and/or Aternity REST API Server

The Aternity REST API Server is a component in Aternity on-premise which allows authorized users to send REST API queries to directly extract and analyze Aternity's data without accessing Aternity's dashboards. You can combine the data with other data sources if needed, or transform it as required, then view it in Microsoft Excel, Power BI, or your own data application.

The Aternity REST API Server is a component in Aternity on-premise which allows authorized users to send REST API queries to directly extract and analyze Aternity's data without accessing Aternity's dashboards. You can combine the data with other data sources if needed, or transform it as required, then view it in Microsoft Excel, Power BI, or your own data application.

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.

In addition, check the ports which you must open on this server (learn more).

Network

Ensure this server has a static IP v4 address, and that you open the required ports.

Operating system for Aternity REST API Server or Aternity Data Source for Portal

  • Linux CentOS 7.3 - 7.5 + kernel update version 4.2 or later. To verify your version of CentOS, enter cat /etc/centos-release.

  • (Aternity 10.0.1) Red Hat Enterprise Linux (RHEL) 7.4 or 7.5.

    (Aternity 10.0) Red Hat Enterprise Linux (RHEL) 7.4.

    To verify the RHEL version, enter cat /etc/redhat-release

  • Linux Ubuntu 16.04 (Xenial) LTS (long term support). To verify the Ubuntu version, enter cat /etc/*release

It must have Python 2.7 or later.

Docker for Aternity REST API Server or Aternity Data Source for Portal

Aternity REST API Server or Aternity Data Source must use Docker for Ubuntu or Docker for CentOS (Docker 17.0.3 or 17.06). Learn more. For Red Hat Enterprise Linux (RHEL), use the Docker which comes with RHEL (Docker 1.12 or 1.13).

After you set up the Docker engine, you can set up the Aternity REST API Server or Aternity Data Source for Portal from a Docker image file.

Permissions

Run the setup as a user with root or sudo root privileges on the computer. To verify, enter sudo id.

Time zone

Synchronize all Aternity components to have the same date, time AND time zone.