• Decide on the size of your deployment, based on the number of devices to monitor. This directly determines the number of servers you need, and their hardware specifications.

  For example, if the updated requirements for your sizing state you must have a new standalone Aggregation Server, you must use the custom update to remove the legacy embedded Aggregation Server from within the Management Server, then run the setup again on a standalone server to a fresh setup of a new Aggregation Server there.

  

• Aternity 11.x arranges its servers in a slightly different way, with smaller requirements for most legacy components and a new server for Docker components.

• Since all components in v11 reside in the new Docker Components server, several servers for standalone components used in v10 have been removed from v11, such as ETL, standalone Aternity REST API Server and Aternity Data Source for Portal.

• Ensure you have an existing fully functional Aternity 9.x or 10.x before starting your upgrade.

  All devices MUST be reporting to Aternity using Agent 9.x or 11.

• Ensure the servers meet the software system requirements for all components in the solution.

• Choose the network topology of your deployment, based on the location of your monitored devices.

  • Set the firewalls to open the required ports between components, if you plan any of them to be on opposite sides of a firewall.

  • Decide the security, whether you want to encrypt connections between some or all of the Aternity components.

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

• Strengthen robustness by determining the backup strategy and whether to have high availability with redundant servers.

The setup package is for all Aternity servers.

There are also entries in the Useful Links section which are required for database setup.

(For updates from Aternity 10.x only) Perform an upgrade to Vertica 9.1.1. Learn more.

Vertica is a third-party column-store database optimized for large volume data analytics. The Aternity Vertica Database Server stores the performance data in the Vertica format, which is most efficient for displaying in Aternity dashboards. It receives its data from the Aternity Docker Components Server. (If you performed the data migration process, then your Vertica Database Server is already up and running.)

For updates from Aternity 11.0.0 and 11.0.1, data migration is NOT required.

Aternity 11.x requirements for the version of Oracle are the same as Aternity 9 and 10. Therefore it is not necessary to change the Oracle version for this upgrade. In addition, Aternity 11.0.0/11.0.1 support Oracle version 12.2.0.1 and Aternity 11.0.2 supports also Oracle version 18c.

You must run the Aternity Database Verification Utility several times before and after updating the database (learn more).

The verification may return a fatal error if the Aternity schema user does not have the MANAGE SCHEDULER privilege. To resolve, as the database's SYSTEM level user (who created the schema in the Aternity database), connect to Oracle Database and run the command: GRANT MANAGE SCHEDULER TO <db_aternity_user> This is mandatory for upgrading the Aternity Management Server. You can remove this privilege once the upgrade is completed.

Connect to the Aternity ETL Server as a user with root or sudo root privileges. To verify, enter sudo id. Execute the following command to delete all cron jobs:

crontab -r -u <dedicated_linux_user>

Connect to the server as a user with root or sudo root privileges. To verify, enter sudo id. Execute the following command to delete all cron jobs:

crontab -r -u <dedicated_linux_user>

Stop and remove Aternity REST API Server by running the command docker stop AOdata and then docker rm AOdata.

Stop and remove Aternity Data Source for Portal by running the command docker stop AternityDataSource and then docker rm AternityDataSource.

The Dashboard Server displays Aternity's intuitive dashboards using Tableau as its engine.

The Dashboard Gateway acts as the interface between the Dashboard Server and the Aternity Management Server, performing background tasks like preprocessing the data for display in the dashboards, and maintaining logs, audits and cleanup. It must be on the same computer as the Dashboard Server. While it has no user interface of its own, it is crucial to the proper functioning of Aternity.

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).

If you previously had several Aternity components on this server, recheck the sizing, as you may need to create new standalone servers and remove legacy embedded components in this server.

• 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.

For example, if the updated requirements for your sizing state you must have a new standalone Aggregation Server, you must use the custom update to remove the legacy embedded Aggregation Server from within the Management Server, then run the setup again on a standalone server to a fresh setup of a new Aggregation Server there.

The Aternity dashboard layouts contain the names, calculations and layouts of the system's dashboards for this Aternity version.

Select the Gear Icon > License Provisioning > Edit Licenses.

If it displays an existing serial number, select it. Otherwise select Add License. Enter your new number and license volume.

(Optional) Open the System Health dashboard and check the state of all Docker Components.

The System Health dashboard displays the overall topology and health of your Aternity deployment. Learn more.

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.

As your deployment grows in size, add more identical Aggregation Servers (see deployment sizing for details). If your sizing requires that you deploy more than one dedicated Aternity Aggregation Server, you must deploy a third party load balancer (LB). Then configure the Agent for End User Devices of all devices to point to the LB's virtual IP address (learn more). Configure the LB with persistent (sticky) sessions to ensure the Agent maintains its connection with the same server. Aternity also supports sticky sessions when the LB implements stickiness via cookies.

For example, login to Portal and update the base URL to use to access the Aternity Data Source because it now resides on a different host computer.

Configure the SteelCentral Portal™ to connect to your Aternity Data Source to view Aternity data in the Portal alongside data from other products in the SteelCentral Suite.

Aternity on-premise version 11.x update rewrites the OOTB MS Office activities. As a result, if you localized them to your language, once version 11.x is up and running, you need to merge the translations into the updated OOTB MS Office activities. Prior to upgrade, the translated activities were automatically backed up to <Aternity_Home_folder>/monitorsBackup folder in the Management Server. The file name is Export_Microsoft_Monitors_{dd-MMM-yyyy-_HH_mm_ss}.zip where the date changes with the actual date and time of the backup.

Dashboards	Description
Existing dashboards with data from the old version	Following data migration, when you open Aternity version 11.x for the first time, your historical data will show on dashboards.
Existing dashboards without data from the old version	Without data migration, the dashboards that use a new data schema will open empty. They will be fully populated with data in a month after installing Aternity 11.x.
New dashboards that did not exist in old versions at all	New dashboards that did not exist in previous versions initially appear empty and will be fully populated with data in a month as new data flows in from devices.