Software System Requirements for Aternity on-premise

This section details the minimum software system requirements to install and run the components of Aternity.

Access Aternity Dashboards and Settings

Log 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/), using any of the following Windows supported browsers:

  • Google Chrome version 38 and above.

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

    Note

    Some administration settings screens in Aternity (which use Flex) require the 32-bit version of Chrome or a 32-bit tab in Internet Explorer 11. In Chrome, you must also enable Flash by selecting the web icon in the address bar then selecting to always allow Flash on this site.

    Enable Flash in Chrome to view Aternity settings

Windows Devices (Running Windows Agent)

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

Attribute Requirement

Resource usage

Agent uses:

  • CPU: Total utilization across all cores up to 0.12%.

  • RAM: Up to 225MB physical memory usage. On virtual servers, add 40MB per session.

  • Storage: Around 850MB total (including 740MB for Agent log files. In rare support-led Agent troubleshooting cases, the log files can reach up to 3GB).

  • Bandwidth: Adds up to 0.25 kilobytes per second (KBps) incoming to the device, and up to 0.083KBps reporting data to Aternity.

Operating system

Device must have:

  • Microsoft Windows 10, 8.1, or Windows 7 SP2 Enterprise / Professional 32-bit and 64-bit (32-bit requires Agent 9.0.6 or later).

  • For servers: Windows Server 2008 R2 64-bit and Windows Server 2012 64-bit.

Monitored web applications

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

  • Any Google Chrome browser released in the past two years, with the Aternity Extension for Chrome installed, to monitor web events (WPM) and all browser interaction. Without this, Aternity only monitors clicking a link, back, forward, direct URL, HTTP GET and POST events.

  • Microsoft Internet Explorer v9, 10 or 11.

    Disable IE's compatibility mode to automatically discover web applications. It monitors custom activities even in compatibility mode.

    Select > Internet Options > Advanced > Security, and deselect Enable Enhanced Protection Mode.

  • Firefox version 38 ESR or version 45 ESR.

    For version 45 ESR, contact Customer Services to ensure custom activities are compatible with this version of Firefox, and to add the necessary component to Aternity.

Connectivity

The Agent sends monitoring data to Aternity (IP v4) using HTTPS over port 443.

Microsoft .NET

Device must have Microsoft .NET v3.5 SP1 or later. For added security (TLS 1.2), use .NET version 4.5 or later.

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 environments must be housed in one of the following operating systems:

Attribute Requirement

Operating system

Windows Server 2012 R2, 2012, or 2008 R2.

The Windows Agent monitors virtual devices and/or virtual applications in any of the following environments:

Attribute Requirement

Citrix virtual application servers

Citrix XenApp 6.5, 7.6.

Citrix virtual desktop servers

Citrix XenDesktop 6.5, 7.6.

Citrix XenServer is NOT supported.

VMWare VDI

VDI support is for VMWare ESXi 5.1, 5.5, or 6.0 only. 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.

Mobile Devices (Running a Monitored Mobile App)

To run a monitored app in iOS or Android, the device must have the following operating systems:

Attribute Requirement

iOS operating system

iOS 8 or later (iPhone 4 or earlier cannot run iOS 8).

Android operating system

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

Java Developer Kit

JDK 1.8 or later.

Programming environment

Apple XCode 7.

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.7 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 16 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 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. Users access this server via a browser to configure the system and view the dashboards.

The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Database Server.

Both these servers require the following:

Attribute Requirement

Operating system for Management Server and Data Warehouse Server

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

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 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 2012 R2, 2012, or 2008 R2. Set the date and time formats to Control Panel > Regions > Formats > English (United States).

You can also deploy the Aggregation Server on Linux CentOS 5.8 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 Database Server (Oracle)

The Aternity Database Server is an Oracle database which houses the Aternity system settings and the performance data from the past 1-2 years, aggregated by the Data Warehouse Server.

The only Aternity-specific requirement is the database version itself, which should be installed on any operating system supported by this database.

Attribute Requirement

Oracle version for Aternity Database Server

Aternity 9.x requires that the Aternity Database Server runs either Oracle 11.2.0.4 or 12.1.0.2 (including support for Oracle Data Guard):

  • Oracle Database version 12c Enterprise Edition 64-bit, with patch set 12.1.0.2

  • Oracle Database 11gR2 Enterprise Edition 64-bit with patch set 11.2.0.4

You can download either version of Oracle from the Related Links of the Riverbed support site.

Operating system for Aternity Database Server

(Express setup) Windows Server 64 bit 2012 R2.

(Full setup) Windows Server 64 bit 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 Database Server on Linux CentOS 5.8 or Linux RedHat Fedora.

RAM for Aternity 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.

Hardware

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

Aternity Dashboard Server (Tableau)

The Dashboard Server displays Aternity's intuitive dashboards using Tableau as its engine. It presents the raw data (from the Data Warehouse Server) and the older aggregated data (from the 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 2012 R2 or 2008 R2 Enterprise Edition (with KB2117917). Set the date and time formats to Control Panel > Regions > Formats > English (United States).

Hardware

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

Tableau version for Dashboard Server

Aternity 9.0 and 9.0.1 requires that you update your Dashboard Server to run Tableau Server 9.0.4.

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.