Set up Trial POC for Aternity on-premise 12 with VMWare Images (OVA files)

Set up a trial POC of Aternity on-premise using VMWare virtual machines using OVA image files for each of the three servers. An OVA image file contains both the operating system and Aternity server setups required for a POC.


Use OVA image files ONLY in the trial POC demo deployment of Aternity on-premise, and not in production. Using OVA image files in production will prevent you from updating your deployment to a new version.


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

We strongly recommend that you do NOT change the time zone in OVA image files.

The operating system in each OVA file comes with security updates up to September 2020. We recommend you update to the latest security patches for the same version of that OS in each OVA.

Set up trial POC for Aternity on-premise on VMs with OVA image files

This procedure uses VMWare's vSphere to deploy the virtual machines.

Before you begin

You must be familiar with VMWare vSphere and vCenter.

This procedure assumes you already have a vCenter server with a resource pool for VMs, and access to a vSphere client.

Allocate the virtual machines with the dedicated resources as detailed in the trial sized hardware requirements.


  1. Step 1 To download the three virtual machine image files (.ova), contact Customer Services.

    An OVA file contains an entire disk image, including both the operating system and Aternity server setups required for a POC (learn more).

    In addition to the three image files, you download a credentials text file with user names and passwords you need for login to each server.

    Field Description


    This is the VM image file which contains Windows Server 2012 running the Aternity Management Server computer for trial deployments.

    It also contains the Aternity Oracle Database Server, the Aternity Data Warehouse Server and the Aternity Aggregation Server.


    This is the VM image file which contains Windows Server 2012 running the Aternity Dashboard Server computer for trial deployments.

    It also contains the Aternity Dashboard Gateway Server and the Aternity dashboard layouts.


    This is the VM image file which contains CentOS Linux 7.6 running the Aternity Vertica Database Server computer for trial deployments.

    It also includes the Aternity Docker Components Server.


    This is the text file with user names and passwords for each server. Refer to this file when you need to log in.

  2. Step 2 If using VMWare 6.5, skip step 2 and continue to step 3. If using VMWare 5.5, unpack each image file (.ova) to its own folder (right-click on the .ova and select Extract Here).
    Once unpacked, you have several different files in each folder:
    1. .ovf file
    2. .vmdk file(s)
    3. .mf file

    Delete the .mf file from all three folders.

  3. Step 3 Open the VMWare vSphere client.
  4. Step 4 Select File > Deploy OVF Template and do the following:
    • If using VMWare 6.5, select the ova image file to deploy

    • If using VMware 5.5, select the .ovf file to deploy

    Select Next to review the details, then select Next.

    Open the image file for this VM
  5. Step 5 Assign the VM's internal vSphere name and location within vSphere's window.
    Add VM metadata to vSphere
    Field Description

    Enter the logical name for this VM which appears in the vSphere tree.

    Itinerary Location

    Enter the location of this VM in the vSphere tree.

  6. Step 6 Assign the CPU and disk resources for this virtual machine.

    The virtual machine (and therefore its host or cluster) must have the resources available as per the requirements for trial/POC deployments.

    Assign the virtual host or cluster which runs the VM
    Field Description

    Select the host or cluster of hosts which you want to assign as the resource pool for this VM.

    Destination Storage

    Select the disk storage allocation for this virtual machine.

    Disk Format

    Select the method your VM allocates disk storage.

    Choose the method according to your enterprise provisioning policy. We recommend selecting Disk Format > Thin Provision if available.

  7. Step 7 Deploy all three virtual machines on the same network (recommended) or on networks where they can reach each other.

    Select Next then Finish to deploy. Perform the above steps for each of the image files.

    Deploy the VM to a network which ensures it can reach the other two VMs
  8. Step 8 Switch on each VM and update ALL the network settings for each VM to match your enterprise's environment.

    Edit the network settings as follows:

    • For Windows Server 2012 virtual machines, sign in as user administrator with the password specified in the credentials.txt file, then select Start > Run and enter ncpa.cpl. Find your active network configuration, then select Properties > Internet Protocol version 4 (TCP/IPv4).

    • For Linux virtual machines, sign in as user root with the password specified in the credentials.txt file, then edit ifcfg-ens160 in /etc/sysconfig/network-scripts with a plain text editor.

    Change VM network settings to fit your enterprise
    Field Description
    DNS1 / DNS2 Preferred DNS server / Alternate DNS server

    Enter the IP v4 address of the enterprise DNS server which would hold the entries for these three VMs: aternity-mgmt, aternity-tabl, and aternity-vertica.


    (Linux only) Replace the predefined value of this field ( with the domain suffix which your enterprise needs to resolve a hostname like aternity-vertica to

    (Windows only) Select Advanced > Advanced TCP/IP Settings > DNS > Append these DNS suffixes (in order) > Add, then enter the domain suffix which you need to resolve a hostname like aternity-mgmt to

    Add DNS suffix in Windows
    NETMASK / GATEWAY / Subnet mask / Default gateway

    Enter the remaining network settings of this VM which fit your enterprise's address policy.

    IPADDR / IP Address

    Enter the IP v4 address of this VM which fits your enterprise's address policy.

    Ensure the VM is connected in vSphere.

  9. Step 9 Restart the network service of the Aternity Vertica Database Server for the new network settings to take effect.

    Enter service network restart

  10. Step 10 Create DNS entries in your enterprise DNS server for the three virtual machines, and map them to the IP v4 addresses which you assigned.

    Create entries for aternity-mgmt, aternity-tabl, and aternity-vertica in your DNS.

  11. Step 11 Sign in to the Tableau Services Manager with the Windows host administrator user on that device.
  12. Step 12 Activate Tableau.

    Enter Aternity's license key for Tableau: TS1E-AFF9-2A60-C12B-CBF5, and select Activate License.

    Activate Tableau

    After activation, it may take a few minutes for the server to reach the running state. Server may show state as degraded during startup.

    The URL address of the TSM web UI is http://<machine_hostname>:8850. Port 8850 is used by default for Tableau administration and configuration. In case you want to access the TSM from a different device, the port 8850 should be open on the device where Tableau was deployed. Learn more.

  13. Step 13 Register Tableau.
  14. Step 14 If this computer is not connected to the Internet, perform an offline activation. Learn more.
    Contact Customer Services to get the key for the offline activation.

    An offline process (VM migration) may deactivate a valid license. To prevent Tableau license deactivation, verify that either Tableau virtual machine has a Static Mac address or VMotion is disabled on that virtual machine. Follow VMWare documentation to configure Tableau VM Mac address to Static.

  15. Step 15 Verify the setup succeeded, by checking the status of the system on the Tableau top bar: verify it is RUNNING.
    Verify the Tableau is running

    If after several minutes it still remains in degraded or stopped state, restart the server.

  16. Step 16 Restart the AternityTableauGateway service.
  17. Step 17 Access the aternity-vertica server as a user with root or sudo root privileges on the computer. To verify, enter sudo id.
  18. Step 18 Verify the setup by confirming that Vertica is running.
    1. a Switch to the Vertica database administrator user, like dbadmin, by entering su - dbadmin.
    2. b Run the Vertica administration tool by entering admintools.
      Vertica's database administrator tools
    3. c Select the first option View database cluster state.

      Confirm the State is UP.

      Verify the database is running

      If the database is not up, return to the main menu and select 3 to start the database.

  19. Step 19 Access the Aternity Management Server computer.
  20. Step 20 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.

  21. Step 21 Restart the AternityPlatform service.

    Wait until the service returns to the Running status. 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, and then start the AternityPlatform service.

  22. Step 22 Verify you can access Aternity by going to http://aternity-mgmt.

    If the Login screen does not appear, wait 2-3 minutes, as it is possible that the server is still starting up.

  23. Step 23 Access the aternity-vertica server as user aternity, navigate to /aternity-docker-components and run the command ./aternity-docker-admin install

    Ignore validation errors regarding hardware requirements.

  24. Step 24 Access Aternity by going to http://aternity-mgmt.

    Sign in with username administrator and with the password specified in the credentials.txt file. This trial deployment is not configured with secure communication (HTTPS).

    There are some browser settings which must be in place to access Aternity (Learn more).

  25. Step 25 Go to the Gear Icon > System Health, and verify that all components are in the running state.