Upgrade Aternity on-premise to 9.0.2 / 9.0.3

Update your Aternity on-premise to version 9.x from v7.1.x or 8.x for a significant step forward in new featuresand resolved issues.

Always check the sizing before ANY update. Even minor Aternity upgrades like from 9.0.1 to 9.0.3 (or 9.0.2) have updated sizing, hence you may need to change your topology and hardware even with the same number of devices.

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 freshly install a new Aggregation Server there.

Uninstall an embedded component during upgrade, then run setup to install it on a standalone server

With larger deployments in Aternity version 9.0.3, deploy a Dashboard Worker Server, which makes dashboard rendering more efficient. You can install the Dashboard Worker Server after completing the upgrade.

Before you begin

Before upgrading Aternity on-premise:

  • You must start with a fully functioning deployment of Aternity on-premise version 7.1.x or later. If you have an older version, first upgrade to version 7.1.x, then deploy this upgrade to Aternity 9.x. Hence your Aternity Dashboard Server should be running Tableau 8.1.x or 8.2.x before the upgrade.

  • Check the correct sizing for your deployment before updating any of your Aternity servers.

  • After the updating from Aternity 7.1.x or 8.x, some dashboards do not retain some of their most recent data:

    • The dashboards with NO legacy data after updating are: My Enterprise, Remote Display, App Analysis, App Errors and All Crashes.

    • The dashboards with only two days of legacy data after update are: Application Status and Troubleshoot Activity.

    • Before and After retains 30 (out of 90) days of legacy data.

    Many dashboards in Aternity v9 have a longer retention. For details, see the new features in v9.

Procedure

  1. Step 1 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
  2. Step 2 Update the Aternity Database Server by verifying and then updating the Oracle database.
    Important

    You MUST run the Aternity Database Verification Utility a week or so before starting your upgrade.

    Aternity 9.x requires that the Aternity Database Server runs either Oracle 11.2.0.4 or 12.1.0.2.

    Use the Aternity Database Verification Utility as part of the database update for Aternity 9.x

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

    1. A week before updating, run the Aternity Database Verification Utility from the Management Server to find any issues with the existing database.

      Fix all the flagged items listed in the reports by updating the settings in your legacy Aternity or by asking a DBA to change the database directly.

    2. Run the utility a second time before updating, to check there are no more actionable changes.

      Tip

      We strongly advise you to submit this report to Customer Services to confirm your database is ready for the update.

    3. Ask your DBA to update Oracle. Aternity 9.x requires that the Aternity Database Server runs either Oracle 11.2.0.4 or 12.1.0.2

      You can download either version of Oracle from the Related Links of the Riverbed support site.

    4. After the database update, run the utility again to check if there are issues with the updated database.

      Implement the required fixes. To resolve an issue from within Aternity's settings, you must first complete all the server updates, then implement those fixes.

    Learn more.

  3. Step 3 Update the Dashboard Server by uninstalling the previous version of Tableau and then running the setup to install the new version.

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

    Update the Dashboard Server component (Tableau Server)
  4. Step 4 (Large deployments only, above 20,000 devices) Add one or more standalone Dashboard Worker Servers by running its setup on a separate dedicated computer for that component.

    Add the number of standalone Dashboard Worker Servers according to the requirements for the size of your deployment.

    The Aternity Dashboard Worker Server accepts much of the intensive processing required to create dashboards, enabling larger Aternity on-premise deployments to display dashboards more efficiently.

    Dashboards in large deployments are more efficient with Dashboard Worker Servers
  5. Step 5 On the Dashboard Server, update the Dashboard Gateway component.

    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.

    Update the Dashboard Gateway on the same computer as the Dashboard Server
  6. Step 6 Update the Aternity Management Server by running its express setup or custom setup over the previous version.

    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.

    Important

    Always check the sizing before ANY update. Even minor Aternity upgrades like from 9.0.1 to 9.0.3 (or 9.0.2) have updated sizing, hence you may need to change your topology and hardware even with the same number of devices.

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

    Uninstall an embedded component during upgrade, then run setup to install it on a standalone server

    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 freshly install a new Aggregation Server there.

    Use the updated sizing to determine whether a component is embedded or standalone
    • (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.

  7. Step 7 Update the Aternity dashboard layouts from the Management Server.

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

    Important

    (Large deployments only) Download the separate dashboard package for large deployments, containing settings and dashboard layouts which are specially performance tuned for large enterprises.

    Add the dashboard layouts ONLY from the Management Server.

    Install the layouts from the Management Server into the Dashboard Server via Dashboard Gateway
  8. Step 8 Update the remaining components of the Aternity deployment.

    If your sizing requires you to update or create a standalone server, run the setup on each standalone computer.

    1. a (For deployments above 5,000 devices only) Run the express update or the custom update of a standalone Aggregation Server on its own computer, or create a new one.

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

      Aggregation Server collects and consolidates data from monitored devices
    2. b (For deployments above 20,000 devices only) Run the express update or the custom update of a standalone Data Warehouse Server on its own computer, or create a new one.

      The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Database Server.

  9. Step 9 To benefit from the full range of features of Aternity v9.x, deploy Agent 9.x on your devices.

    Aternity 9.x is compatible with devices using the legacy Aternity Agent 7.1.x or 8.x. Therefore, Aternity supports a phased upgrade of devices to Agent 9.x. However, using legacy Agents, the dashboards show only activities from managed applications.

    Tip

    If you want persist with older (legacy) versions of Aternity Agent (7.x or 8.x) with Aternity v9, set the system to compatibility mode, by selecting the Gear Icon > Settings > Advanced Settings > webApp > showAgent9Data to No.

    If your legacy Agents communicate over TCP, you must first test then switch from TCP to HTTP(S).

    Install the Agent on desktops and laptops to report their performance to Aternity

    For the best reporting of devices, deploy Agent 9.x, and view the full power of Aternity 9.x:

  10. Step 10 Check that the system's monitor tree is valid for Aternity v9.x, by selecting the Gear Icon > Monitors Validator.

    It creates a report listing the issues it found, organized like the Monitors Settings window, by application name. For details, see Validate Changes to the Monitors Settings (Monitor Tree Compatibility Tester).

    Validate the monitors in the system
    Tip

    If you have custom activities for addons or plugins to a default application (like Microsoft Outlook or IBM Lotus Notes), store those custom activities under the application folder, under its own separate monitor folder.

    Addons and plugins belong under the application's folder

    If your monitors tree includes any customized ‘enabler monitors’, which allow your custom activities to capture events from http, html or Java applications, you must remove the enablers in the upgraded Aternity 9.x, as enabling monitors are built-in by default, under a folder called Aternity Enabler. If you are not sure whether your custom activities include enablers, contact Customer Support.

  11. Step 11 Switch Aternity to display discovered applications and locations automatically.

    (For Agent upgrades only) After you upgraded enough devices with Agent 9.x, switch to the enhanced view of Aternity, including enhanced dashboards, site-based location and automatic user attribute mapping.

    Take full advantage of discovery data
  12. Step 12 If you have a role called Aternity User, you must edit it to ensure it performs correctly in Aternity 9.x.

    Select the Gear Icon > Roles, and add the following privileges under the Dashboards section:

    • View Dashboards

    • Analyze Use Cases

    • Advanced Analytics