Upgrade to AppMon 6.5

Warning

With the Upgrade to 6.3, the domain compuwareapmaas.com was replaced by dynatracesaas.com. If your SaaS instance is still using compuwareapmaas.com make sure to use the dynatracesaas.com domain as the compuwareapmaas.com domain will be de-supported by December 2016.

Dynatrace AppMon 6.5 (Dynatrace AppMon 6.5 Release Notes) has been released on the 26th of September 2016. New AppMon SaaS environments will be automatically provisioned with the latest version of 6.5 - older environments can be migrated on customer request by opening a support ticket and by indicating their desired maintenance window.

Upgrade process

The migration of the server components on the AWS instance is performed by Dynatrace, if you have any collectors and agents connected on your own infrastructure then these will need to be updated manually by the customer. The division of responsibilities will be as such:

Dynatrace:

  • Check Environment Health before update
  • Update AppMon Server and Performance Warehouse to newest version (including installation of the latest public update)
  • If needed a new license will be installed with a possibly remaining UEM volume
  • After the update has been successful, deploy new certificates to the Cloud server and collectors for migrations from version 6.2 or older

Customer:

  • Update clients located on customer infrastructure
  • Update collectors located on customer infrastructure
  • Organize restarts of agents and make a final check

Detailed information about the upgrade can be found in the product documentation: Upgrade and Migration Guide

Dynatrace: Check Environment Health

Before starting the upgrade process, Dynatrace will make a quick assessment on the health of your deployment (including automatic analysis of the support archive).

Dynatrace: update to AppMon Server to 6.5

  • A back-up of the SaaS instance will be triggered
  • The Dynatrace Cloud instance will be upgraded to 6.5 (see Updates & Configuration for more details on the process)
  • The Performance Warehouse will be migrated to 6.5
  • The whole process will take ~ 40 min, during which time the SaaS instance will be offline

The customer will be notified before starting the upgrade and also after the upgrade. In case of issues, the environment can be restored to the previous version within 30 minutes.

Customer: update AppMon Client to 6.5

Any clients that you have installed on your own infrastructure will need to be updated to 6.5 manually. These can be pre-installed in parallel with the 6.5 version. Alternatively you can use the webstart client available on your SaaS server at https://<customerID>.dynatracesaas.com:8021/.

If there are problems with upgrading the client, a separate support ticket needs to be created. Attach any available client log file.

Customer: update Dynatrace Collectors to 6.5

Any collectors that you have installed on your own infrastructure will need to be updated to 6.5 manually. These can be pre-installed in parallel with the 6.5 version as long as they are not switched on before the update of the Server to 6.5.

Once you have received confirmation that your Dynatrace SaaS instance has been upgraded to 6.5, you will need to perform the following steps:

  1. Stop the current collectors
    • You are required to stop your current collectors in order to migrate your current collector settings to the new collectors. Ensure the old collectors are not started automatically with a OS reboot.
      Additional Information: Starting and Stopping Collectors
  2. File Migration
    • Use the migration tool to migrate your on premise collectors.
    • For a full explanation on how to use the migration tool please view the following page: Migration Tool Details
      Example:
      java -jar dynatrace-migration.jar -migration –sourceDTHome "C:\Program Files\dynaTrace\dynaTrace 6.3"  -targetDTHome "C:\Program Files\dynaTrace\dynaTrace 6.5" -migrateInstances defaultCollector
  3. Start the new collectors
    • Once the new collectors have been brought back up, the agents will reconnect automatically and continue sending data to them.
      Additional Information: Starting and Stopping Collectors

If there are problems with upgrading the collector, a separate support ticket needs to be created. Attach any available collector log or command line output while starting the process.

Customer: restart agents

Once your agents are connected to the new collectors, organize to have them restarted, this will allow them to bootstrap to the latest version. For further information, including instructions for agents that require manual updating. Please refer to the following documentation: Agent Upgrades

If there are problems with upgrading the agents, a separate support ticket needs to be created. Any agent log file needs to be attached to this new ticket.

Confirm the operation of the new Dynatrace Server & apply the customization not covered by automation: Final Migration Checks

Optional Dynatrace: deploy certificates

if this has not already been done on your instance during the 6.3 upgrade, the Dynatrace SaaS team will deploy the updated certificates for SSL communication (collector-server) and HTTPS (Dynatrace Web). The certificates will be automatically deployed to the customer Collectors using the Certificate Wizard  (Deploy Certificate). A re-start of the Collectors will be triggered to update the certificates on the Collectors.