Set Up a New Aternity Data Warehouse Server on a Dedicated Computer

Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices.

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.

Create a standalone Data Warehouse Server for larger deployments

Before you begin

  • Download the latest Aternity on-premise's main setup package from the Aternity Support Site by selecting Software (size) (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.

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

    Attribute Requirement

    Hardware

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

    Network

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

    Both servers set up and use Apache Tomcat 8.5.32.

    Note

    If you set up a trial deployment using VMWare virtual machines, the operating system in the OVA file comes with Windows Server 2012 R2 64 bit.

    Permissions

    Ensure you have local administrator privileges on this computer.

    Time zone

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

Procedure

  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 Select the Aternity_windows-x64.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 Confirm that it selects Aternity Data Warehouse 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 Data Warehouse Server to create a standalone server
  7. Step 7 Select if you want the incoming connection to the Data Warehouse Server (from the Management Server) to be encrypted with HTTPS.
    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 Data Warehouse Server receives its input and sends its output via 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 Confirm the summary and complete the setup.
  12. Step 12 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running.
  13. Step 13 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).