Upgrade considerations

Dynatrace NAM 2018 SP1


Upgrade and installation information

  • As part of configuring an external IdP, you need to export the SSO metadata from the NAM Console and import it into the external IdP configuration. For example, in Using OpenAM as an external IdP , you export the NAM Console metadata in and import it into OpenAM.

    Installing NAM 2018 Service Pack 1 will require you to export and import that metadata once more after you apply the service pack. Without doing so, you will be unable to sign in to the NAM Console through the external IdP. See Using an external identity provider.

Dynatrace NAM 2018


Functional changes

  • NO ADS server. ADS functionality is moved to the NAM server as Advanced Diagnostics on Demand (ADoD) feature and it is enabled by default. See Advanced Diagnostics on Demand.

  • Product rebranding

    DC RUM 2017 May release Dynatrace NAM 2018 release
    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

Upgrade and installation information

  • There is no automatic conversion of ADS reports into ADoD reports. Once upgraded, you can use the diagnostic console command that converts the exiting reports to use ADoD data views or, edit each of your custom ADS-based reports and change the DMI data view for each of them from ADS data views to ADoD data views. See Upgrading DC RUM 2017 with ADS.

  • Starting with Dynatrace NAM 2018 release, all licenses (capacity based and component based) will be handled by the eServices licensing platform. See Licensing.

  • To be authorized by the NAM Console, all users must have access to both the NAM Server public URL and NAM Console public URL.

    Public URLs are required for authorizing users. Users accessing a NAM Server must have access to that NAM Server's public URL and to the NAM Console public URL, because each NAM Server user is transparently redirected to the NAM Console public URL for authentication and then back to the NAM Server public URL.

  • Firewall installation
    The fresh NAM Probe installation includes a system firewall that controls incoming and outgoing network traffic based on configured security rules. The rtmgate listens on TCP port 8443 and UDP port 9093 and, by default, it uses the system firewall to redirect incoming requests on these ports.

    • TCP 443 ► TCP 8443
    • UDP 514 ► UDP 9093

    An upgraded NAM Probe installation that is already using the system firewall will preserve all existing rules and exceptions. The upgrade process will automatically add and map the required communication ports redirections.

DC RUM 2017


Functional changes

  • AMD 2017 available only in high speed architecture. No upgrade path from a Classic AMD - you need to import the configuration to a fresh installed AMD 2017. See Upgrading Classic AMD. If you decide to stay with the classic architecture, you can use the latest release of Classic AMD 12.4 in your 2017 deployment.
  • No CSS in 2017. Users and security are handled by RUM Console. RUM Console installation program imports the users and settings from your current CSS. See Upgrading the RUM Console.
  • AMD network configuration handled by system tools, not rtminst. See Configuring AMD communication interface.

Upgrade and installation information

  • Upgrade possible only from 12.4.x. Recommended upgrade path is 12.4.13 -> 2017. See Upgrade paths.
  • Upgrade.bin, the AMD installation program has now two installation modes, automatic and manual. There's no default option. You must choose one using --automatic or --manual parameters. See Installation and upgrade options.
  • Release 2017 - CAS/ADS database upgrade times

Linux support

  • See list of OS and SQL supported versions.
  • AMD 2017 will only work with Red Hat Enterprise Linux 7.3.
    • If your AMD operates on RHEL 6 you need to migrate to RHEL 7.3 and new AMD architecture. Even though RedHat supports now in-place OS upgrading from RHEL 6 to RHEL 7 this is not supported OS upgrade path by Dynatrace and the only supported OS migration path is the one documented here.
    • If your AMD operates on RHEL 7.2 you need to update RHEL OS to version 7.3 upgrading AMD to 2017 release.
    • If you can't migrate to RHEL 7.3 now you may continue using AMD 12.4 on RHEL 6 with 2017 CAS and ADS until June 30, 2018 (12.4 release end-of support date) but you need to upgrade it to latest available 12.4.x service pack.
  • Starting with the 2017 release, AMD also works with CentOS in releases equivalent to those of Red Hat.
  • Dynatrace does not provide support for the operation and maintenance of your Linux, either Red Hat or CentOS.

Enterprise Synthetic 12.5


Functional changes

No CSS in 12.5. Users and security are handled by RUM Console 2017. RUM Console installation program imports the users and settings from your current CSS. See Upgrading the RUM Console.

Upgrade checklist

Please follow the Release 12.5 Upgrade Checklist.

The 12.5 checklist also includes links to the System Requirements and to upgrading the Framework; follow the Framework Upgrade Checklist.