Quickly Update Aternity Data Warehouse Server on a Dedicated Computer

For medium deployments of Aternity on-premise (more than 30,000 monitored devices), you must have a standalone Aternity Data Warehouse Server.

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.

It constantly aggregates and re-summarizes data in the main database in the background, replacing older, more detailed data with summary data as it ages. Therefore older data typically has limited drill-down capabilities.

You can either setup a Data Warehouse Server as custom or express (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 Aternity Data Warehouse Server for the first time, follow the fresh setup procedure.

Create a standalone Data Warehouse Server for larger deployments

Before you begin

Before upgrading a standalone Data Warehouse Server, 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.

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

    Attribute Requirement


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


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

    Operating system for Management Server and Data Warehouse Server

    Windows Server 64 bit 2019 or 2016.

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

    Also, go to Control Panel > Region > Administrative > Copy settings and copy your current settings to Welcome screen and system accounts. Make sure that Language for non-Unicode programs is set to English (United States).
    Set language regional formats

    Both servers set up and use Apache Tomcat 8.5.75.


    Ensure you have local administrator privileges on this computer.

    Time zone

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

    We recommend that an IT person define a clock synchronization service, like for example NTP, between all Aternity components. This will provide highly accurate timing for all network components and prevent clock drift.


  1. Step 1 Access your standalone Data Warehouse 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 Express (Use 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 express setup
  8. Step 8 Confirm the summary and complete the setup.
  9. Step 9 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running.
  10. Step 10 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).