Customize your Update of a Standalone Aternity Aggregation Server on a Dedicated Computer

For all deployments (except trial) of Aternity on-premise (more than 1000 monitored devices), you must create one or more standalone Aternity Aggregation Servers.

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.

Aggregation Server collects and consolidates data from monitored devices

As your deployment grows in size, add more identical Aggregation Servers (see deployment sizing for details). If your sizing requires that you deploy more than one dedicated Aternity Aggregation Server, you must deploy a third party load balancer (LB). Then configure the Agent for End User Devices of all devices to point to the LB's virtual IP address (learn more). Configure the LB with persistent (sticky) sessions to ensure the Agent maintains its connection with the same server. Aternity also supports sticky sessions when the LB implements stickiness via cookies.

Deploy a third party load balancer if you have multiple Aggregation Servers

Depending on your topology choices, you can place the standalone Aggregation Server either in the DMZ or the enterprise network (see the Aternity on-premise topologies).

You can either setup an Aggregation Server as express or as custom (which is detailed here).

  • If you are keeping the same topology or security, choose the express update, which keeps your legacy settings in the updated servers.

  • If you are changing your topology or security, choose the custom update.

If you are creating a standalone Aggregation Server for the first time, follow the fresh setup procedure.

Before you begin

Before upgrading one or more standalone Aggregation Servers, you must:

  • Download the latest Aternity on-premise's main setup package from the Riverbed Support Site (learn more).

  • If you are running a version earlier than 11.0.3, first of all update to 11.0.3 before updating to 12.2.

  • Check the correct sizing for your deployment before updating any of your Aternity servers. Learn more.

  • Prepare the Aternity Oracle Database Server for Aternity by verifying its configuration. Learn more.

  • Aternity requires you set up one or more new Vertica Database Servers, depending on the size of your deployment. Learn more. (If you performed the data migration process, then your Vertica Database Server is already up and running.)

  • Update the Dashboard Server if your base version is on-premise 12 or 12.1 (learn more), or Set up a new server on a new host if your base version is 11.0.3 (learn more).

  • On the Dashboard Server, update the Dashboard Gateway component. Learn more.

  • Confirm that a local administrator on the Management Server can connect to the Dashboard Server.

  • Update the Aternity Management Server by running its express setup or custom setup over the previous version.

  • Update the Aternity dashboard layouts from the Management Server. Learn more.

  • (For deployments above 30,000 devices only) Run the express update or the custom update of a standalone Data Warehouse Server on its own computer, or create a new one.

  • Check that your computer conforms to the minimum system requirements:

    Attribute Requirement

    Hardware requirements for Aternity Aggregation Server

    Each Aggregation Server must be at least a Xeon E3 family, 2 cores at 2.4 GHz, hard disk: 30GB (min), RAM: 12GB (min). To determine the number of servers, check the sizing specifications for your deployment.


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

    Operating system for Aternity Aggregation Server

    Windows Server 64 bit 2019 or 2016.

    Set the date and time formats to Control Panel > Region > Formats > English (United States).

    The Aggregation Server sets up and uses Apache Tomcat 8.5.75.

    You can also deploy the Aternity Aggregation Server on Linux CentOS or Linux RedHat Fedora.


    Ensure you have local administrator privileges on this computer.

    As your deployment grows, you add more identical servers with the same hardware and system requirements.


  1. Step 1 Access your standalone Aggregation Server computer.
  2. Step 2 Log in to the computer as a local administrator.

    To verify you are a local administrator on this computer, not a domain administrator, open the System control panel, select Advanced system settings > Computer Name, and confirm the Change button is active.

  3. Step 3 Stop the AternityPlatform service.
    To stop the service, you must sign in to the computer as an administrator, and access the Windows Services screen. If the service does not stop within a minute, go to the Task Manager and select End Task for the Java process running on the machine.
  4. Step 4 Select the Aternity_windows-x64_12.2.0.<build number>.exe setup file, which you downloaded as part of the Aternity on-premise server setup package.

    Copy it to a temporary location on this computer.

  5. Step 5 Right-click the setup and select Run as administrator to begin.
  6. Step 6 (Optional, recommended) Backup your existing server settings, as they may be useful for support and troubleshooting purposes.

    The size of the backup is roughly equal to the size of the deployment, but does not include raw data files and archived reports.

    Backup to a subfolder under updates, like D:\data\Aternity\updates\backup_20160323-182419. We recommend that you use the default folder. Do NOT save the backup in the parent Aternity folder, D:\data\Aternity\.

    Backup the existing settings of the server
  7. Step 7 Select Custom (Change Existing Settings).

    Always check the sizing before updating. This version uses different database sizes, dashboard requirements and new servers. Learn more.

    • If you are keeping the same topology or security, choose the express update, which keeps your legacy settings in the updated servers.

    • If you are changing your topology or security, choose the custom update.

    Select the type of setup
  8. Step 8 Review the existing pathname and select Next.

    The setup displays the settings of the existing deployment on this computer.

    If it reports that the existing setup is corrupted, cancel the update and contact Customer Services.

  9. Step 9 Confirm it selects Aternity Aggregation Server.

    Since this is the same tool as that used for the Management Server, select only this option to ensure it is a standalone server.

    Select the Aternity Aggregation Server to update the standalone server
  10. Step 10 Secure the connection of monitored devices sending performance and device data to this Aggregation Server.
    Secure a single Aggregation Server's connection to monitored devices

    When you roll out the Agent for End User Devices on devices, if you secured the Aggregation Server, you must also configure the Agents to communicate via HTTPS.


    Both the load balancer and the Aggregation Servers should be secured. If you are deploying multiple Aggregation Servers, secure their connection to the load balancer. To secure the devices' performance data uploads, configure HTTPS for the load balancer.

    The setup displays the settings of the existing deployment on this computer.

    Select whether this server receives data encrypted (HTTPS)
    Field Description

    Select HTTPS if you want any connection to this server to be via HTTPS.


    To see the Aternity's system-wide security settings, view the security overview of all components.


    Enter the port required to receive data from the monitored devices. The default for HTTPS is 443.

    Custom keystore

    Enter the pathname of the system's keystore that contains the certificate for verifying Management Server's identity. Additional certificates may interfere with single sign-on processes.

    You must add your enterprise's certificate to the system's Java keystore file (.jks) using Java's keytool utility (see Aternity documentation for creating .jks).

    Custom keystore password

    Enter the password required to access the system's keystore file.

  11. Step 11 Configure the memory allocation according to the size of your deployment, and confirm the timezone of the Aternity servers on this computer.
    Configure the memory allocation and time zone (This screenshot displays the default values)
    Field Description
    Java Virtual Machine memory

    Configure the JVM heap size according to the values listed for the size of your deployment.

    You can tweak this value later on if required.

    Customize Timezone

    Select a time zone, only if you need to override the timezone settings of the operating system.


    The time zones of the Oracle Database Server, Dashboard Server, Management Server, Aggregation Server, and Data Warehouse Server must all be identical.

  12. Step 12 Review the summary, then select Next.
  13. Step 13 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running.
  14. Step 14 Configure a secured HTTPS connection.
    If Messaging Broker and/or Raw Data Component are secured with a self-signed certificate, provide a truststore containing the certificate for the root CA that created that certificate. Place this truststore in the same location, relative to Aternity's home directory (the default on Windows hosts is X:\data\aternity), on the Management Server, Data Warehouse Server, and Aggregation Server. For example, D:\Certificates\aternity_truststore.jks. In the Advanced Settings, provide the path to ..\..\Certificates\aternity_truststore.jks.

    Learn more about how to configure a secured HTTPS connection, how to create a truststore, and how to add your enterprise's certificate to the system's Java keystore file (.jks).