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

For medium or larger deployments of Aternity on-premise (more than 3000 monitored devices), you must create one or more standalone Aternity Aggregation Servers.

An Aggregation Server gathers (aggregates) the data directly from Aternity Agents 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 you deploy more than one dedicated Aternity Aggregation Server, you must deploy a third party load balancer (LB). Then configure the Aternity Agent of all devices to point to the LB's virtual IP address. Configure the LB with persistent (sticky) sessions to ensure the Agent maintains its connection with the same server.

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

  • If you are running a version that predates v7.1.x, update to v7.1.x before updating to v9.x.

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

  • If your legacy Agents communicate over TCP, you must first test then switch from TCP to HTTP(S).

  • Update the Aternity Database Server by verifying and then updating the Oracle database..

  • Update the Dashboard Server by uninstalling the previous version of Tableau and then running the setup to install the new version.

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

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

  • (For deployments above 20,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.


  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 Download the latest version of Aternity on-premise from our website.

    The setup package is for all Aternity servers.

    Download Aternity on-premise from the website
  4. Step 4 Right-click the setup and select Run as administrator to begin.
  5. Step 5 (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 installation, 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
  6. Step 6 Select Custom (Change Existing Settings).

    Always check the sizing before ANY update. Even minor Aternity upgrades like from 9.0.1 to 9.0.3 (or 9.0.2) have updated sizing, hence you may need to change your topology and hardware even with the same number of devices.

    • If you keep 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 installation
  7. Step 7 Review the existing Installation Location and select Next.

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

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

  8. Step 8 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
  9. Step 9 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 Aternity Agent on devices, you must also configure the Agents to send HTTPS.


    If you are deploying multiple Aggregation Servers, there is little to be gained in securing its connection to the load balancer. To secure the devices' performance data uploads, configure HTTPS for the load balancer, NOT the Aggregation Server.

    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 containing your enterprise's certificate.

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

    Custom keystore password

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

  10. Step 10 Configure the memory allocation size of your deployment, and confirm the timezone of the Aternity servers on this computer.
    Configure the memory allocation and time zone
    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 Database Server, Dashboard Server, Management Server, and Data Warehouse Server must all be identical.

    JMS Memory Maximum

    Enter the ActiveMQ JVM heap size according to the value listed for this server for the size of your deployment.

    You can tweak this value later if required.

  11. Step 11 Review the summary, then select Next.
  12. Step 12 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running.