Quickly Update an 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. If you are creating a standalone Aggregation Server for the first time and not as an upgrade, follow the procedure for a fresh setup.

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.

You can either setup an Aggregation Server as custom or as express (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.

  • Check your PC 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: 8GB (min)

    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.

    Permissions

    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.

Procedure

  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 Express (Use Existing Settings).
    Important

    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 Confirm the summary and complete the setup.
  8. Step 8 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running.
  9. Step 9 Review the settings from the existing server, and select Install to start the update.

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