Set Up a New Aternity Management Server

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

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

Add more components on the same Management Server PC
  • (Trial demo deployments less than 66 devices) The Management Server PC can also have the Database Server, Analytics Server, Data Warehouse Server, and Aggregation Server, all on the same PC.

  • (Small deployments less than 5,000 devices) The Database Server is standalone. The Management Server PC has ALL the following: the Analytics Server, Data Warehouse Server, and Aggregation Server.

  • (Mid-sized deployments less than 20,000 devices) The standalone servers are: Database Server and Aggregation Server. The Management Server PC has ALL the following: Analytics Server and Data Warehouse Server.

  • (Larger deployments above 20,000 devices) The standalone servers are: Database Server, Data Warehouse Server and Aggregation Server. The Management Server PC should only have the Analytics Server.

Before you begin

Before creating the Management Server:

  • Complete deployment of the Aternity Database Server.

    • (Non-DBAs) Use the express database setup for small deployments up to 3000 devices.

    • (DBAs only) Use the custom database setup for larger deployments or to integrate any sized database properly into your enterprise.

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

  • Make sure the hardware and operating system of the Aternity Management Server conform to the following requirements:

    Attribute Requirement

    Operating system for Management Server and Data Warehouse Server

    Windows Server 64 bit 2012 R2, 2012, or 2008 R2. Set the date and time formats to Control Panel > Regions > Formats > English (United States).

    Hardware

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

    Permissions

    Ensure you have local administrator privileges on this computer.

Procedure

  1. Step 1 Access the Aternity Management Server PC.
  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 Download the latest version of Aternity on-premise from our website.

    The setup package is for all Aternity servers.

    Download Aternity on-premise from the website
  4. Step 4 Right-click the setup and select Run as administrator to begin.
  5. Step 5 Select Next and enter the pathname of 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 the Aternity Management Server and the Aternity Analytics Server to add to this computer.

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

    Select the Aternity servers to add on this computer
    • (Trial demo deployments less than 66 devices) The Management Server PC can also have the Database Server, Analytics Server, Data Warehouse Server, and Aggregation Server, all on the same PC.

    • (Small deployments less than 5,000 devices) The Database Server is standalone. The Management Server PC has ALL the following: the Analytics Server, Data Warehouse Server, and Aggregation Server.

    • (Mid-sized deployments less than 20,000 devices) The standalone servers are: Database Server and Aggregation Server. The Management Server PC has ALL the following: Analytics Server and Data Warehouse Server.

    • (Larger deployments above 20,000 devices) The standalone servers are: Database Server, Data Warehouse Server and Aggregation Server. The Management Server PC should only have the Analytics Server.

    Add more components on the same Management Server PC
  7. Step 7 Enter the hostname of this computer.
    Select the Management Server address
    Field Description
    Hostname

    Select the hostname or IP address from the drop-down list, or enter it manually. This is the listening address when other components connect to the Management Server.

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

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

  8. Step 8 (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 and Windows monitored devices, or just Windows devices. Typically, you would use the default All devices setting.

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

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

    Select your deployment size
  10. Step 10 Configure the connection of the Management Server with the Database Server (the Oracle database), 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 Database Server
    Field Description
    Database Server hostname/IP address

    Enter the hostname, IP address, or DNS name of the Database Server.

    Database Service Name

    Enter the 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 Database Server (default is 1521).

    Create Database Schema

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

    Aternity database schemas
    • he 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.

    • he 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 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 custom 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. Contact Aternity customer service team before implementing connection strings with any RAC elements or other advanced features.

    Custom Database URL

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

  11. Step 11 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 database schemas
    Field Description
    Platform Database Credentials

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

    This field is for 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.

    Configuration Database Credentials

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

    This field is for the system settings schema, which stores Aternity's system settings.

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

  13. Step 13 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 port that Aternity uses to communicate with the Management Server.

    In small, ‘all-in-one’ deployments, this defines the port for Aternity Agents 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 your enterprise's certificate.

    You must add your 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 should purchase your own certificate signed by a certification authority.

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

  15. Step 15 (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.

  16. Step 16 Confirm the summary and complete the setup.
  17. Step 17 Select Start AternityPlatform service and select Finish.
    Start the service of the Management Server

    The AternityPlatform service is the Management Server. You can verify it is running in the Windows Task Manager.

    Tip:

    If the setup completes but the AternityPlatform service did not start, verify you have local administrator privileges on the computer.

  18. Step 18 Open a browser and sign in to Aternity.
  19. Step 19 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.

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