Set Up a New 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 Devices 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).

Before you begin

Before creating a standalone Aggregation Server, you must:

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

  • Complete setting up the Aternity Oracle Database Server.

  • Complete setting up one or more Aternity Vertica Database Servers.

  • Complete setting up the Aternity Dashboard Server and the set up of the Dashboard Gateway.

  • Complete setting up the Aternity Management Server.

  • Complete the setup (publishing) of the Aternity dashboard layouts.

  • (Optional) Complete setting up a dedicated Aternity Data Warehouse Server computer.

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

    Network

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

    The Aggregation Server sets up and uses Apache Tomcat 8.5.69.

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

    Permissions

    Ensure you have local administrator privileges on this computer.

    Timezone

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

  • 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 Select the Aternity_windows-x64_12.1.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.

  4. Step 4 Right-click the setup and select Run as administrator to begin.
  5. Step 5 Select Next and enter the path to the setup directory on a local, non-system drive.

    This reduces the risk of the server application competing with the operating system for disk space.

    Select the location of the Management Server files
  6. Step 6 Select Aternity Aggregation Server.

    Since this is the same tool as that used for the Management Server, select only Aternity Aggregation Server as this is a standalone server.

    Select the Aternity Aggregation Server to create a standalone server
  7. Step 7 (Single standalone server only) 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.

    Tip

    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.

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

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

    Tip

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

    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.
  8. Step 8 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.

    Important

    The time zones of the Oracle Database Server, Dashboard Server, Management Server, Data Warehouse Server and Aggregation Server must all be identical.
  9. Step 9 Review the summary, then select Next.
  10. Step 10 Define this server's connection to the Management Server.

    The Aggregation Server must pass on its output to components in the Management Server.

    Point to the Management Server
    Field Description
    Management Server Hostname / IP Address

    Enter the hostname or IP which is the listening address you defined when creating the Management Server.
    Management Server Port

    Enter the port number which it uses for HTTP or HTTPS access, defined when creating the Management Server.
    Use SSL Transport

    Select if you defined the Management Server to use secure HTTPS when accessing it.
  11. Step 11 If this is a fresh install, select A new Aggregation Server.
    Define whether this is a clean setup
  12. Step 12 Define the properties of this new standalone Aggregation Server.
    Define the properties of a new Aggregation Server
    Field Description
    Aggregation Server unique profile name

    Enter an internal name for this server, to be used by the Agent for End User Devices on a monitored device to specify this Aggregation Server by name.
    Device Types

    Select whether this Aggregation Server accepts connections from mobile, Mac and Windows monitored devices, or just Windows devices.
  13. Step 13 Confirm the summary and complete the setup.
  14. Step 14 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running.
  15. Step 15 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).