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

Installation in DC RUM 2017

Applies to DC RUM 2017

Follow this procedure for a successful DC RUM 2017 deployment.

  • This help topic is for installing DC RUM 2017.

  • Most of the installation and deployment procedures, with differences as noted, are the same in DC RUM 2017 and Dynatrace NAM 2018, and the two releases share a common basic set of help topics.

    To avoid confusion, be aware of the following product and component name changes that were introduced with Dynatrace NAM 2018:

    DC RUM 2017 and older NAM 2018, NAM 2019
    RUM Console NAM Console
    Central Analysis Server (CAS) NAM Server
    Advanced Diagnostic Server (ADS) Advanced Diagnostics on Demand feature of NAM Server
    Agentless Monitoring Device (AMD) NAM Probe
    You will see these name changes reflected in the help.

1. Learn from others

To learn what to watch for and what to avoid, check out our user forums:

2. Plan your deployment

Decide how your deployment should be implemented, what traffic do you want to monitor, and where you should deploy the hardware. For best monitoring performance, plan for the expected capacity and review hardware requirements.

3. Install your Windows operating systems

Three of the DC RUM components (RUM Console and the CAS and ADS report servers) require Microsoft Windows and SQL server to operate. Make sure you have appropriate licenses for your deployment and install Microsoft Windows for each of the report servers and RUM Consoles you want to run.

Multiple components on one system

There is no need to dedicate a separate Windows machine to the RUM Console. It can coexist on the same Windows machine as a report server. If your deployment involves multiple report servers, one of the report servers can also host the RUM Console.

4. Install RUM Console

A RUM Console installation requires a SQL Server database and a SQL Server database user with certain user rights. If you use a remote database, make sure that you have the database information ready. If you plan to use a local database, make sure that your local security policy permits the installer to set up the database for you.

5. Install report servers

6. (Optional) Install additional report servers

If your deployment plan includes multiple report servers grouped in clusters, install any additional Microsoft Windows and SQL servers.

7. Install Red Hat Enterprise Linux

The AMD monitoring software runs on Red Hat Enterprise Linux. Determine the supported Linux version for your DC RUM deployment, then download and install it. The best installation method, where possible, is to use the kickstart on a machine connected to the internet.

If you are an experienced Linux user, you can install Linux without the kickstart. However, you will then need to do more work (additional configuration and package installation) when you install the AMD monitoring software.

8. Install DC RUM monitoring software

When you are installing the AMD monitoring software, you have a number of installation options. Some parameters are mandatory and affect the deployment (for example, licensing options). Check the installation options and run the installation script.

9. Activate your monitoring software licenses

Every fresh AMD installation includes a 30-day grace license, but it is a good idea to activate the licenses and using the license manager in the RUM Console upload them to the appropriate AMDs.