Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Upgrading CAS or ADS from 12.4 to 2017

The installation wizard walks you through all steps in the correct order.


All DC RUM components need to be authenticated within a particular deployment. This authentication was performed via an internal user. Starting with DC RUM 2017, authentication is performed via internally generated tokens. Because the RUM Console contains token generating and authentication functionality, make sure that you first upgrade the RUM Console.

Exit all other programs before running the setup program.
Some Windows programs, such as anti-virus software, may interfere with the upgrade process.

If other Dynatrace products are currently active on the target machine, their services are stopped automatically before CAS or ADS is installed.

Double-click the setup file.
Depending on your release the file name should be similar to CAS_setupAMD64.exe .

If the detected amount of physical memory (RAM) on the target machine is lower than the recommended amount, a warning message is displayed.
Click Cancel to abort the installation and consider upgrading the machine's RAM before restarting the installation process, or click Next (not recommended) to continue this installation with less than the recommended amount of RAM.

On the License Agreement screen, indicate that you have read and accepted the license agreement and click Next.

The installer will guide you through the upgrade of the RUM Console. Click Next to advance the wizard.
The full set of configuration screens are outlined below. If you selected to upgrade your software without changing settings, most of these screens are not displayed.

Upgrade panel

  • Upgrade the application without changing the settings.
    The database information used during the upgrade is obtained from the previous installation of the report server.
  • Reinstall application and change settings for the new version.
    You will have to provide the database, user and connection properties for the upgrade.

Database configuration properties

  • Create new database
    You will need to provide SQL connection data and SQL Server administrator login credentials to create a new database and new database user.
  • Use existing database
    You will need to provide SQL Server connection data.
    You can also set additional database options regarding the existing database (upgrade, reset or recreate).

Database connection properties for existing database

Provide the host (including the port), the instance and the name of the new database to be created.

  • Authentication
    Provide the administrator account information. This user can be a direct database user, or a windows user with permissions to administer the database.
  • Database User
    Enter information for the database user that is used accessing the database. Mark the Create database user and Use database administrator account if you want to create a new user for accessing the database.
  • Upgrade Database
    This option preserves all traffic monitoring data and database configuration settings.
  • Reset Database
    This option deletes all traffic monitoring data but preserves database configuration settings.
  • Recreate Database
    This option deletes the database and creates a new database of the same name. All the traffic monitoring data contained in the database and all database configuration settings are lost.

Database connection properties for new database

Provide the host (including the port), the instance and the name of the new database to be created.

  • Authentication
    Provide the administrator account information. This user can be a direct database user, or a windows user with permissions to administer the database.
  • Database User
    Enter information for the new user that will be created specifically for accessing the new database.
  • Database size [GB]
    You can indicate the size of the database that will be created. If you use a remote SQL Server, or a default SQL Server location on another disk partition, ensure that the database size does not exceed the available disk space.

RUM Console connection

The report servers are administered by the RUM Console. Since the DC RUM deployment upgrade requires the RUM Console to be upgraded first, you should have the upgraded RUM Console address available.

  • RUM Console URL:
    Enter the address of the upgraded RUM Console including the network port used for component communication (default port: 4183).
  • Enter token
    DC RUM components use API tokens for secure internal communication. If you already have the token or you want to generate it now, select this option and enter the token. For more information, see API tokens.
  • Get token automatically
    You can have the DC RUM system administrator get a token automatically. Select this option and provide the DC RUM System Administrator credentials.

Incorrect RUM Console connection properties
You will receive this error if your RUM Console information is incorrect (the address, the system admin user name or password), or the RUM Console version you are using is not compatible with the current installation. Tokens are compatible with NAM 2017 releases and newer.

Connectivity Options

Define the client connectivity options to the report server. This is where you configure how the user will access the report server and its reports.

Use HTTP Whether to use HTTP to transfer and display reports.

  • HTTP Port
    This number is incremented if the default port (80) is unavailable.
  • Use HTTP for communication Use HTTP to transfer and display reports.
  • Redirect HTTP to HTTPS only When an attempt is made to connect to this report server using HTTP, automatically redirect that connection to HTTPS.

When accessing the reports on a port other than 443, remember to supply the selected port number together with the host name in your browser. This number is incremented if the default port is unavailable.

  • Generate key and certification On the SSL Key Generation Data screen you will have to enter the information required to generate a new key.
  • Use custom key and certificate
    For a custom encryption key, you can provide only the password; the other fields cannot be edited. Choosing a custom encryption key requires that you configure the server manually. This process involves copying both the key and the certificate to the proper directory and modifying the common.properties file.

SSL key generation data

The SSL Key Generation Data screen enables you to enter the information required to generate a new key.

  • Country
    The standard abbreviation for your country. Select one from the list of approved country codes.
  • Locality
    Usually your city. Use a full name such as “Los Angeles,” not an abbreviation.
  • State or Province
    Your administrative region within your country. Use a full name such as “California,” not an abbreviation.
  • Organization Name
    Usually a company name. Use the full legal company or personal name as registered in your locality.
  • Organization Unit
    The company division or branch (such as Accounting or Marketing) to which the certificate was issued.
  • Common/Host Name
    The host.
  • Email Address
    The email address.

SSL key security

Specify the encryption key security information.

  • Key Password The password associated with the key.
  • Confirm Key Password
    The password associated with the key.
  • Remember the key password
    Whether to remember the password.

If you do not select the Remember the key password check box, you can instead supply the key password at system startup, but only if you are directly connected to the server. Remember that the dialog box for entering the password will not appear if you are connected to the server using a remote terminal.

Also, remember that if you do not provide a password the key will not be encrypted.

On the Pre-Installation Summary page, review the summary of your installation choices and click Install.
To change the settings, click Back to return to the appropriate configuration screen.
The amount of time this takes depends on the size of the database and may take between several seconds and, for large databases, several hours. A progress box shows the status of the installation action currently in progress. When all of the required actions are completed, a final post-upgrade information screen is displayed.

On the Installation Summary screen, review the installation summary.
If you prefer, you can click Show postinstall summary to open a file that contains the installation summary.

Indicate whether you want to start CAS, and then click Finish to exit the installation program.

Clear your browser cache.
This ensures that your upgraded CAS configuration is displayed correctly.