Customize your Update of Aternity Data Warehouse Server on a Dedicated Computer

For medium deployments of Aternity on-premise (more than 40,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 express or custom (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 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 Aternity Support Site by selecting Software (size) (learn more).

  • If you are running a version earlier than v9, update to v9 before updating to this version.

  • 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 schema. 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 by removing the previous version of Tableau and then running the setup of the new version. 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

    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 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.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 Custom (Change Existing Settings).
    Important

    Always check the sizing before updating. This version uses different database sizes, dashboard requirements and new servers. Learn more.

    • 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 type of setup
  8. Step 8 Review the existing pathname and select Next.

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

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

  9. Step 9 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
  10. Step 10 Select if you want the incoming connection to the Data Warehouse Server (from the Management Server) to be encrypted with HTTPS.

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

    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.

  11. Step 11 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 (This screenshot displays the default values)
    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, 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.

  12. Step 12 Review the summary, then select Next.
  13. Step 13 Verify the deployment was successful by confirming that the Windows services shows AternityPlatform as running.
  14. Step 14 If you defined the Messaging Broker and/or Raw Data Component to use a secured HTTPS connection and a self-signed SSL certificate when accessing them, then define the identical security settings on the Data Warehouse Server.

    Read here how to configure a secured HTTPS connection, create a truststore, and add your enterprise's certificate to the system's Java keystore file (.jks).