Set Up a New Aternity Management Server

The Aternity Management Server acts as Aternity's central server, which manages and integrates all the components. When users access Aternity to view the dashboards or configure it, they access this server via a browser.

You can add more components on the Management Server computer for smaller deployments:

Add more components on the same Management Server computer

Before you begin

Before creating the Management Server:

  • Download the latest Aternity on-premise's main setup package from the Riverbed support site by selecting Software (size) (learn more).

  • To setup the Aternity Management Server, you must register with Aternity's online activation form. Enter your contact details and serial number to send an activation key to your email (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.

  • Make sure the hardware and operating system of the Aternity Management Server conform to the following 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.

    Time zone

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

    Permissions

    Ensure you have local administrator privileges on this computer.

Procedure

  1. Step 1 Access the Aternity Management 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 Locate 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 In the Welcome screen, click Next.
  6. Step 6 In the License Agreement screen, select I agree to continue.
  7. Step 7 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 Aternity Management Server files
  8. Step 8 Select the Aternity Management Server to add to this computer.

    You can add more components on the Management Server computer for smaller deployments:

    Select the Aternity servers to add on this computer
    • (Up to 1000 devices) The Management Server computer has ALL the following: Oracle Database Server, Data Warehouse Server, and Aggregation Server, all on the same computer.

    • (Less than 20,000 devices) The Oracle Database Server is standalone. The Management Server computer has ALL the following: the Data Warehouse Server, and Aggregation Server.

    • (Less than 40,000 devices) The standalone servers are: Oracle Database Server and Aggregation Server. The Management Server computer has the Data Warehouse Server.

    • (Above 40,000 devices) The standalone servers are: Oracle Database Server, Management Server, Data Warehouse Server and Aggregation Server.

  9. Step 9 To setup the Aternity Management Server, you must register with Aternity's online activation form. Enter your contact details and serial number to send an activation key to your email (learn more).

    Aternity requires a live email address for every production deployment of Aternity on-premise, to properly honor our commitments of royalty payments to vendors of third party software.

    Go to https://activation.aternity.com.

    When completed, Aternity sends the activation key to your email.

    Retrieve an activation key to continue the setup
    Field Description
    Company Name

    Enter the name of your enterprise which purchased Aternity.

    Contact Email / Confirm Email

    Enter your work email address which you can access. Aternity sends the activation key to this address.

    Important:

    You must check the inbox of this account for the activation key. You cannot continue setup without this key.

    Serial Number for your Aternity Purchase

    Enter the exact serial number of the latest Aternity purchase.

    Environment Type

    Define the purpose of your system, for identification purposes only. If you are not sure, select Unknown.

    Release

    Select the version Aternity which you want to activate.

  10. Step 10 Enter the activation key which you received via email from the online activation form.
    Tip:

    Copy all characters in the key, including the 'equals' (=) signs at the end.

    Enter the activation key
  11. Step 11 Enter the listening address (FQDN recommended) when other components connect to this computer.
    Select the Management Server address
    Field Description
    Hostname

    Enter the listening address to which other components connect to the Management Server. Select the FQDN (recommended), hostname or IP v4 address from the drop-down list, or enter it manually.

    For example, when the Aggregation Server sends data to the Management Server, it must send to this address.

    It displays several entries if this computer has more than one network card (NIC) or several virtual IPs.

    External URL

    Enter the complete URL (including protocol) which users must use in a browser to access Aternity. For example, https://aternity.company.com

    Tip:

    If you made a mistake in this field, use the Configuration Tool to change it later.

  12. Step 12 (Only for small deployments, if the Aternity Aggregation Server is also on this computer) Define the properties of this Aggregation Server.
    Select the device types which may connect to Aternity
    Field Description
    Device Types

    Select whether this Aggregation Server accepts connections from mobile, Mac and Windows monitored devices, or just Windows devices. Typically, you would use the default All devices setting.

  13. Step 13 Select the size of your deployment as the number of devices you expect to monitor.

    This defines the storage and memory settings for the Oracle Database Server and the Data Warehouse Server. A smaller deployment saves storage and memory space, while a larger size improves performance.

    Learn more.

    Select your deployment size
  14. Step 14 Configure the connection of the Management Server with the Oracle Database Server, and automatically initialize the database by creating its schema.
    Note:

    If you choose to automatically create the schema in the Aternity database, you must provide the database's SYSTEM level user and password.

    Typically you enter details in the Connection tab, but if you have a custom database connection URL, use the Advanced Properties tab.

    Configure the Management Server's connection with the Oracle Database Server
    Field Description
    Database Server hostname/IP address

    Enter the FQDN, hostname (recommended) or IP address of the Oracle Database Server.

    Database Service Name

    Enter the Oracle database service name (usually Aternity). This is the alias to the instance of the Aternity database.

    Database Port

    Enter the port required to access the Oracle Database Server (default is 1521).

    Create Database Schema

    Select to automatically generate the schemas required for the Aternity database:

    Aternity database schemas
    • ATERNITY schema: This is the name of the business data schema, which stores the performance measurements and device data over the past year or two, along with contextual data, like device details and user details.

    • GR schema: This is the name of the system settings schema, which stores Aternity's system settings.

    For example, select this if you created the database using the express setup of the Aternity Oracle Database.

    Deselect this to skip the automatic creation of schemas. For example, if your DBA has already created the schemas in the database in a custom setup, or if your security policy prevents you from knowing the Oracle SYSTEM username/password, or running it from a setup in this way. If so, contact customer services to receive a script which your DBA can run to create these schemas in a secure way.

    Username and Password

    (If you selected Create Database Schema): Enter the username and password required to create the database schema.

    Use the Advanced Properties if you have a custom database connection URL. This overrides any settings in the Connection tab.

    Configure your Oracle database connection URL
    Field Description
    Customize URL

    Select to enter your own custom connection string to the database. Ask your DBA if you have a custom database implementation which requires a custom URL.

    Tip:

    If you have Oracle RAC (Real Application Clusters) deployed, configure the connection string of Aternity's database service to use only a one single instance in the cluster. You can configure the failover option to use another server if required.

    Therefore Aternity does NOT support RAC's load balancing and high availability features. We recommend you contact Customer Services to discuss your overall DR / high availability architecture.

    Custom Database URL

    Enter the custom database connection URL, such as (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))(CONNECT_DATA=(SERVER = DEDICATED)(SERVICE_NAME = ATERNITY)))

  15. Step 15 Configure the connection of the Management Server to the Vertica Database Server, and automatically initialize the database by creating its schema.
    Configure your Vertica database connection URL
    Field Description
    Vertica Server hostname/IP address

    Enter the hostname, IP address, or DNS name of the Vertica Database Server. For a Vertica cluster, enter the hostname, IP address, or DNS name of any one of the cluster servers.

    Vertica Database Name

    Enter the name of the Vertica database, which is set during the Vertica Database Server setup.

    Vertica Port

    Enter port 5433 to access the Vertica Database Server.

    Username and Password

    Enter Vertica's system-level (DBADMIN) username and password, which allows the creation of the Vertica Aternity schema user.

  16. Step 16 Define the names of the two schemas in the Aternity database, and their passwords.

    If you deselected the Create database schema field because your DBA already received a script from our Customer Services, ask your DBA for the name and password of each schema.

    Enter the names and passwords of the two schemas in the Oracle database
    Field Description
    Platform Database Credentials

    Enter a name for the business data schema (sometimes, Aternity), and its password.

    This is the name of the business data schema, which stores the performance measurements and device data over the past year or two, along with contextual data, like device details and user details.

    Tip:

    It automatically creates the same schema name in the Vertica database.

    Configuration Database Credentials

    Enter a name for the system settings schema (sometimes, GR), and its password.

    This is the name of the system settings schema, which stores Aternity's system settings.

  17. Step 17 Confirm the names of the tablespaces in the Aternity database.

    In nearly every case, your Aternity database should use the default tablespace names. Only use different names if your DBA is required (by enterprise policy) to change them when setting up the Aternity database.

    Use the default Aternity database tablespaces
    Field Description
    DATA Tablespace Name

    This is the default tablespace for the ATERNITY and GR schemas.

    This tablespace has the default name ATERNITY_DATA.

    DATA INDEX Tablespace Name

    This tablespace stores the Aternity indexes.

    This tablespace has the default name ATERNITY_IDX.

    HISTORICAL DATA Tablespace Name

    This tablespace stores the Aternity historical performance and device data.

    This tablespace has the default name ATERNITY_HD.

    HISTORICAL DATA INDEX Tablespace Name

    This tablespace stores the indexes for Aternity's historical performance and device data.

    This tablespace has the default name ATERNITY_HD_IDX.

    LOB Tablespace Name

    This tablespace stores large objects (BLOB/CLOB).

    This tablespace has the default name LOB_LARGE.

    TEMP Tablespace Name

    This is the default temporary tablespace.

    This tablespace has the default name TEMP.

  18. Step 18 Configure the security for any connection to this server.

    Configure HTTPS if:

    • You want people to view Aternity's dashboards via HTTPS (like https://aternity.mycompany.com),

    • (Smaller deployments only) You want monitored devices to connect via HTTPS.

    • (Larger deployments only) You want the Aggregation Server to connect to this server via HTTPS.

    Secure access to the Management Server
    Tip:

    For secure HTTPS (SSL) web access to Aternity, you must secure both the Aternity Management Server and the Aternity Dashboard Server.

    Select to access Aternity via HTTP or 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 Management Server listening port. Aternity users view dashboards, and components communicate with the Management Server, using this port.

    In small, ‘all-in-one’ deployments, this defines the port for Agent for End User Devicess which report data to Aternity. In large deployments, other Aternity components must connect to this server though this port.

    The default for HTTP is 80 and for HTTPS, 443.

    Custom keystore

    Enter the pathname of the system's keystore containing only the certificate that verifies your company's identity. Additional certificates may interfere with single signon processes.

    You must add your enterprise's certificate to the system's Java keystore file (.jks) using Java's keytool utility (see Oracle's keytool documentation).

    Custom keystore password

    Enter the password required to access the system's keystore file.

    If you use the sample keystore file which Aternity provides, it creates a certificate warning on the browser every time you access Aternity via HTTPS, since this is not a properly signed certificate. You can obtain a signed certificate from your own internal Enterprise Certificate Authority (CA).

  19. Step 19 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, 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.

  20. Step 20 (Optional) Personalize the Aternity sign in screen.
    Optionally add a logo to the Aternity sign in screen
    Field Description
    Use Custom Logo

    Select to enter your own logo.

    Local File

    Enter the pathname to the PNG or JPG logo file stored locally on this computer.

    Remote URL

    Enter the web URL to the PNG or JPG logo file stored on the internet.

  21. Step 21 Confirm the summary and complete the setup.
  22. Step 22 Make sure that Start AternityPlatform service is not selected, and then select Finish.

    Only start the AternityPlatform service after you set up or update dashboard layouts, to avoid generating unnecessary errors in the setup log files.

    Do not start the AternityPlatform service
  23. Step 23 Open a browser and sign in to Aternity.
  24. Step 24 Log in with the default credentials.

    If you are an administrator logging in for the first time on a newly installed Aternity on-premise system, use the default username administrator and default password Q!w2e3r4. Then we recommend you immediately change the password for this account (learn more).

  25. Step 25 Register the Management Server so we can identify your server if you ever send log files to Customer Support in the future.
    Register the Management Server
    Field Description
    Account name

    Enter your company's full name or an abbreviation.

    Contact name

    Enter the name of someone responsible for Aternity in your enterprise.

    Contact email

    Enter the email of someone responsible for Aternity in your enterprise.

    System type

    Define the purpose of your system, for identification purposes only. If you are not sure, select Unknown.

    Note:

    In Air-gapped networks after installation you can skip the registration page and turn it off underthe Gear Icon > Settings > Account > Registered.

    .
  26. Step 26 Troubleshoot problems by searching for error in any of the following log files:
    • Database logs in <aternity_home>\updates\logs\aternity.log.

    • Setup logs in <aternity_home>\.install4j\installation.log, or if you canceled before the end, find the temporary log in %TEMP%. Ignore the following errors:

      [ERROR] com.install4j.runtime.beans.actions.services.StopServiceAction [ID 11701]: ServiceException{errorCode=5001}

      com.install4j.runtime.beans.actions.registry.ReadRegistryValueAction [ID 3387]: Execute action not successful after 0 ms

      [ERROR] com.install4j.runtime.beans.actions.files.DeleteFileAction [ID 10587]: Execute action not successful after XXX ms