Data Center Real User Monitoring

Transcription

1 Data Center Real User Monitoring Central Analysis Server Installation Guide Release 12.3

2 Please direct questions about Central Analysis Server or comments on this document to: Customer Support Copyright 2014 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Disclosure is prohibited without the prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of the user's License Agreement with Compuware Corporation. Documentation may only be reproduced by Licensee for internal use. The content of this document may not be altered, modified or changed without the express written consent of Compuware Corporation. Compuware Corporation may change the content specified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found at Compuware, FrontLine, Network Monitoring, Enterprise Synthetic, Server Monitoring, Dynatrace Network Analyzer, Dynatrace, VantageView, Dynatrace, Real-User Monitoring First Mile, and Dynatrace Performance Network are trademarks or registered trademarks of Compuware Corporation. Cisco is a trademark or registered trademark of Cisco Systems, Inc. Internet Explorer, Outlook, SQL Server, Windows, Windows Server, and Windows Vista are trademarks or registered trademarks of Microsoft Corporation. Firefox is a trademark or registered trademark of Mozilla Foundation. Red Hat and Red Hat Enterprise Linux are trademarks or registered trademarks of Red Hat, Inc. J2EE, Java, and JRE are trademarks or registered trademarks of Oracle Corporation. VMware is a trademark or registered trademark of VMware, Inc. SAP and SAP R/3 are trademarks or registered trademarks of SAP AG. Adobe Reader is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective owners. Local Build: December 8, 2014, 14:52

3 Contents Contents Introduction Who Should Read This Guide Organization of the Guide Related Publications Customer Support Information Component Updates Reporting a Problem Documentation Conventions Chapter 1 Central Analysis Server Overview Supported Browsers and Connectivity Internationalization Support Chapter 2 Planning and Preparation Installation and Upgrade Planning Checklist Compare Release Notes to Goals Obtain Licensing Inventory the Current Deployment Identify Latest Hardware and Software Requirements Estimate the Installation or Upgrade Duration Chapter 3 System Requirements Recommended Platforms for AMDs and Report Servers Recommended Cisco Platforms Recommended Dell Platforms Recommended HP Platforms Report Server General Requirements Recommended Operating System Configuration for Report Servers Microsoft SQL Server Installation Recommendations Central Analysis Server and Network Monitoring Enterprise Manager Installation... Chapter 4 Installing the Report Server Running a CAS Setup Configuring Report Server to Use Private Keys and Certificates

4 Contents Importing CA Certificates Chapter 5 CAS Upgrade Overview Upgrade Workflow Running a CAS Upgrade CAS Smoke Test Migrating 32-bit CAS to 64-bit CAS (Same Platform, Local Database) Migrating 32-bit CAS to 64-bit CAS (Same Platform, Remote Database) Migrating CAS to a New Platform (Local Database) Migrating CAS to a New Platform (Remote Database) Chapter 6 Uninstalling a Report Server Chapter 7 Logging in to the Report Server Chapter 8 CAS Basic Configuration Settings Sites, User Aggregation, and User Tracking Modifying CAS Basic Configuration Settings Enabling User Activity Details and Server Statistics on Demand Configuring Other CAS Settings Chapter 9 Changing Settings Defined During Report Server Installation Migrating User Accounts to CSS Changing Report Server HTTP and SSL Server Settings Changing Report Server Database User Password Changing the RUM Console Connection Information Chapter 10 Licensing Data Center Real User Monitoring Components Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal Dynatrace Enterprise Portal System Requirements Installing the Dynatrace Enterprise Portal on Windows Installing the Dynatrace Enterprise Portal on Solaris Installing the Dynatrace Enterprise Portal on Linux Red Hat Upgrading the Dynatrace Enterprise Portal to Appendix B Report Server Installation and Upgrade Troubleshooting Appendix C Protocols Supported by CAS Appendix D SQL Operations Performed During Report Server Installation or Upgrade Database Creation Creating a Database User Database User Rights Set Memory Size

5 Contents Appendix E Creating CAS Database and Database User with Microsoft SQL Server Management Studio Appendix F Backup and Recovery Procedures Backing Up the Report Server Backing Up MS SQL Server 2005 CAS Databases Backing Up MS SQL Server 2005 ADS Databases Backing Up MS SQL Server 2008 CAS Databases Backing Up MS SQL Server 2008 ADS Databases Backing Up the AMD Configuration Backing Up the RUM Console Database Backing Up CSS Backing Up the Dynatrace Enterprise Portal Disaster Recovery Procedure Restoring an AMD Backup Configuration Restoring CSS Recovering CSS With a Corrupt Database Recovering CSS With an Unavailable Database Restoring Report Server Restoring the RUM Console Database Restoring the RUM Console Restoring the Dynatrace Enterprise Portal Restoring the Portal Due to a Corrupt or Unavailable Database Portal Reinstallation and Restoration Restoring MS SQL Server 2005 Databases Restoring MS SQL Server 2008 Databases Index

6 Contents 6

7 INTRODUCTION Who Should Read This Guide This guide is intended to be used by network engineers and system administrators installing the Central Analysis Server. Organization of the Guide This installation guide is organized as follows: Central Analysis Server Overview [p. 11] Describes the Central Analysis Server release and lists the supported protocols. Planning and Preparation [p. 17] Provides the necessary information for preparing for a new installation or upgrade. System Requirements [p. 21] Describes the minimum hardware and software requirements for Central Analysis Server. Installing the Report Server [p. 31] Describes how to install the Central Analysis Server. CAS Upgrade Overview [p. 41] Describes how to upgrade the Central Analysis Server. Uninstalling a Report Server [p. 55] Describes how to remove the Central Analysis Server. Logging in to the Report Server [p. 57] Describes how to log in to the Central Analysis Server. CAS Basic Configuration Settings [p. 59] Describes how to configure the Central Analysis Server. Changing Settings Defined During Report Server Installation [p. 67] Describes how to update the basic settings that you specified during installation of the Central Analysis Server. Licensing Data Center Real User Monitoring Components [p. 73] Describes the product licensing. 7

8 Introduction Report Server Installation and Upgrade Troubleshooting [p. 85] Describes how to solve installation and upgrade problems. Protocols Supported by CAS [p. 91] Lists protocols supported by CAS. SQL Operations Performed During Report Server Installation or Upgrade [p. 99] Describes the SQL operations that run during the report server installation or upgrade. Creating CAS Database and Database User with Microsoft SQL Server Management Studio [p. 107] Describes how to use Microsoft SQL Server Management Studio to create a CAS database and database user. Related Publications Documentation for your product is distributed on the product media. For Data Center RUM, it is located in the \Documentation directory. It can also be accessed from the Media Browser. Go online ( for fast access to information about your Dynatrace products. You can download documentation and FAQs as well as browse, ask questions and get answers on user forums (requires subscription). The first time you access FrontLine, you are required to register and obtain a password. Registration is free. PDF files can be viewed with Adobe Reader version 7 or later. If you do not have the Reader application installed, you can download the setup file from the Adobe Web site at Customer Support Information Dynatrace Community For product information, go to and click Support. You can review frequently asked questions, access the training resources in the APM University, and post a question or comment to the product forums. You must register and log in to access the Community. Corporate Website To access the corporate website, go to The Dynatrace site provides a variety of product and support information. Component Updates Using the Update Manager tool, you can quickly scan for available updates for all of your installed Data Center RUM components. The update tool can be accessed from the RUM Console by selecting Help Check for Updates. NOTE The Update Manager tool requires that your browser's security settings allow for the execution of Java programs and that the browser is launched from a system with Internet connectivity. 8

9 Introduction The Update Manager tool scans all of the locally installed components as well as the remote components and devices managed by the RUM Console. After the scan, the information displayed includes the name of the component, currently detected version, and current status. If updates are available for any of the components, you can download them directly from our website. A valid account is required to download the updates. Reporting a Problem Use these guidelines when contacting APM Customer Support. When submitting a problem, log on to the Dynatrace Support Portal at click the Open Ticket button and select Data Center Real User Monitoring from the Product list. Refer to the DC RUM FAQ article at to learn know how to provide accurate diagnostics data for your DC RUM components. Most of the required data can be retrieved using RUM Console. Documentation Conventions The following font conventions are used throughout documentation: This font Bold Citation Documentation Conventions [p. 9] Fixed width Fixed width bold Fixed width italic Indicates Terms, commands, and references to names of screen controls and user interface elements. Emphasized text, inline citations, titles of external books or articles. Links to Internet resources and linked references to titles in documentation. Cited contents of text files, inline examples of code, command line inputs or system outputs. Also file and path names. User input in console commands. Place holders for values of strings, for example as in the command: cd directory_name Menu Item Screen Menu items. Text screen shots. Code block Blocks of code or fragments of text files. 9

10 Introduction 10

11 CHAPTER 1 Central Analysis Server Overview The Central Analysis Server provides real-time access to information about performance and usage of key business applications. It monitors user session performance, application performance, and server performance in different configurations, with the purpose of identifying when and where problems occur and how to address them. Analysis options give insight into business application performance on the transaction and operation level. The information is aligned with the business structure of the organization (such as branches, working groups, and business units) and is not dependent on the infrastructure components. It is delivered via comprehensive, interactive, service-oriented reports, and via event-driven alerts that inform you about important events such as performance degradation or traffic pattern anomalies. CAS reports enable you to see a complete view of your application performance. The report structure reflects business organization priorities and allows for quick identification of the root causes of problems. The CAS is equipped with powerful data mining and report building tools for creating new or customized reports quickly and easily. The CAS uses the measurement data provided by the passive network monitoring devices referred to as Agentless Monitoring Devices or Network Monitoring Probes, and by synthetic network monitoring agents referred to as Enterprise Synthetic Agents. In real user monitoring, one or more AMDs or Network Monitoring Probes are attached to the monitored network near the core switch of the data center or near VPN access switches. The AMDs and Network Monitoring Probes collect the data from the monitored network, preprocess it, and deliver it to the report server. Each report server can handle a number of AMDs and Network Monitoring Probes. The report server processes the received data further, stores it in a database, and then generates user-friendly reports. The reports can then be viewed and analyzed regularly or only when a network problem occurs. Smart Packet Capture functionality enables you to analyze and diagnose the cause of a known and observed network problem by examining detailed packet trace data. Once a monitoring system has detected a network problem, the Smart Packet Capture process can then take over to drill down to the root cause of the issue. The CAS provides: Web analysis and reporting Decryption and analysis of HTTPS traffic 11

12 Chapter 1 Central Analysis Server Overview Monitoring of SSL errors Analysis of middleware transactions (XML, SOAP, SAP RFC, and others) Analysis of various database protocols Analysis of the Oracle Forms protocol Analysis of Microsoft Exchange and SMTP protocols Analysis of a selection of SAP protocols Thin client (ICA) protocol analysis VoIP analysis VPN analysis WAN analysis Enterprise applications analysis and reporting Real-time reports, trending reports, and baseline calculations Detection of abnormal application usage and network usage patterns User diagnostics Report access management, publication, and sharing Customizable reports For more information, see Protocols Supported by CAS [p. 91]. Supported Browsers and Connectivity DC RUM users can access the report servers through the supported web browsers. The following browsers are supported: Microsoft Internet Explorer: versions 9, 10 and 11. JavaScript and HTTP 1.1 must be enabled. IMPORTANT When using Internet Explorer, do not use Compatibility View (MSIE 10 and older) or Document Mode emulating previous releases (MSIE 11). To see if the browser is set to Compatibility View or set to Document Mode other than default, press F12 to access MSIE Developer Tools. Data is handled differently in the HTML. Internet Explorer may experience performance degradation when viewing reports that contain many columns or tooltips. Mozilla Firefox: latest stable release. JavaScript, cookies, and HTTP 1.1 must be enabled. Google Chrome: latest stable release. JavaScript and cookies must be enabled. No tablet or smart phone browsers are supported. Before using the report server, you may have to adjust the Java, JavaScript, and HTTP 1.1 settings in your browser. 12

13 Chapter 1 Central Analysis Server Overview NOTE Some configuration screens depend on the web browser running a supported release of the Java plug-in. The Java Web Start-based RUM Console requires JRE installed on the desktop, and it will run only on Windows and a 32-bit JRE. If you use 32-bit and 64-bit browsers interchangeably, you need a Java plug-in for each browser. The Windows 64-bit operating system comes with 32-bit and 64-bit Internet Explorer browsers and the 32-bit version runs as a default. If JavaScript is not enabled, the top menu of the report server will not be visible and you will see the following message instead: This product uses JavaScript. Please make sure JavaScript is enabled in your browser settings. Because of Internet Explorer security policy, you may encounter some issues when executing Java applets. You need to modify the default settings for Internet Explorer 9 to run applets. For more information, see Enabling Java Support in Internet Explorer 9 in the Data Center Real User Monitoring Central Analysis Server User Guide. Adobe Flash Player must be installed on the client machine to enable drilldowns from autodiscovered software services on the CAS to the RUM Console to create user-defined software services. ADS and CAS can be accessed using HTTP or, over secured connections using HTTPS. We recommend secure access with a browser that supports TLS v.1 or 1.1.For more information, see Configuring Report Server to Use Private Keys and Certificates [p. 37]. Enabling JavaScript and Support for HTTP 1.1 in a Browser Internet Explorer To enable JavaScript in Internet Explorer: 1. Select Tools Internet Options from the top menu in your browser. 2. Select the Security tab. 3. Click Custom level to display the Security Settings dialog box. 4. Enable Active scripting in the list of options. To enable HTTP 1.1 in Internet Explorer: 1. Select Tools Internet Options from the top menu in your browser. 2. Select the Advanced tab. 3. Scroll within the Settings list to the section titled HTTP 1.1 settings and ensure that Use HTTP 1.1 is selected. 4. Click OK and restart your browser. To set the browser mode: 1. On the Internet Explorer 10 main menu bar, select Tools F12 developer tools. 13

14 Chapter 1 Central Analysis Server Overview 2. On the F12 developer tools menu bar, select Browser Mode and click a non-compatibility View option. Mozilla Firefox To enable JavaScript in Firefox: 1. Select Tools Options from the top menu in your browser. 2. Select the Content tab. 3. Select Enable JavaScript. To enable HTTP 1.1 in Firefox: 1. Open the browser and, in the address bar, type about:config and press [Enter]. The browser displays a list of current preferences. 2. Scroll to the network.http.version preference and make sure its value is 1.1. If the value is other than 1.1, double-click that row, change the value to 1.1, click OK, and restart your browser. Google Chrome To enable JavaScript in Chrome: 1. Select Settings from the top menu in your browser. 2. Select Show advanced settings. 3. Select the Content settings tab. 4. In the Privacy section, click Content settings. 5. In the Privacy section, select Allow all sites to run JavaScript (recommended). Internationalization Support The Central Analysis Server supports international environments on both ends: report server and client browser. Localized Server Support The user interface of the report server is rendered in the following languages: English Japanese Korean Chinese simplified English is the default language setting. To support other languages, install the required font set for the target language and customize the regional options accordingly. 14

15 Chapter 1 Central Analysis Server Overview Character Encoding Support for Monitored Traffic By default, only UTF-8 encoding is supported and support for other encodings is turned off. Turn UTF-8 off selectively for HTTP processing and XML processing through the configuration options in the RUM Console. Central Analysis Server recognizes the following character encodings: HTTP and XML/SOAP ISO MQ ISO Unicode (UTF-8) UTF-16 (XML/SOAP only) Japanese: EUC-JP, Shift_JIS, Unicode (UTF-8) Korean: EUC-KR, ISO-2022-KR, Unicode (UTF-8) Chinese: Big5, Big5-HKSCS, EUC-TW, GB18030, GB2312, GBK, HZ, ISO-2022-CN, Unicode (UTF-8) Unicode (UTF-8) Database/SQL (Oracle, TDS, DRDA, Informix) UTF-8 (all DB analyzers) UTF-16 (TDS analyzer only) EBCDIC (DRDA analyzer only) DB statements that were not sent in a supported encoding are encoded such that all non-ascii characters are replaced with their hexadecimal value in the form %XX, where X is a hexadecimal digit. SMB and Kerberos Character encoding in monitored traffic does not affect SMB and Kerberos analyzer operations. Jolt Character encoding in monitored traffic does not affect Jolt analyzer operations. Generic TCP Character encoding in monitored traffic does not affect generic TCP analyzer operations. In addition to international character support in monitored traffic, locale-specific characters can also be used in the AMD configuration and in the names defined in the protocols.xml file. If you use locale-specific characters in the configuration files, save the files in UTF-8 encoding. Turning on internationalization support will adversely affect AMD performance. Performance degradation will depend on the nature of the monitored traffic. 15

16 Chapter 1 Central Analysis Server Overview 16

17 CHAPTER 2 Planning and Preparation The installer walks you through the installation process, either for a new installation or a upgrade. In most cases, the process is automatic, but it is recommended that you review this planning section first to ensure the installation or upgrade is complete. Installation and Upgrade Planning Checklist Use this checklist to plan the migration of your CAS installation to release Finished Steps Before upgrading, read the release notes to determine if additional steps are required. For more information, see Compare Release Notes to Goals [p. 18]. Inventory your current product versions, server components, databases, and agents deployed. For more information, see Inventory the Current Deployment [p. 18]. Review the installation guide for the new releases for your products to determine the software and hardware requirements, migration prerequisites, and product dependencies. For more information, see System Requirements [p. 21]. Ensure that you have enough time available to complete the upgrade. For more information, see Estimate the Installation or Upgrade Duration [p. 19]. Verify that you have all of the licenses required for the software. For more information, see Licensing Data Center Real User Monitoring Components [p. 73]. Install the software. For a new installation, see Running a CAS Setup [p. 31]. For an upgrade, see Running a CAS Upgrade [p. 41]. Configure Central Analysis Server. 17

18 Chapter 2 Planning and Preparation Finished Steps CAS Basic Configuration Settings [p. 59] describes CAS basic configuration, that has to be performed before the product can function. Compare Release Notes to Goals Before proceeding with an installation or upgrade, review the Release Notes and product documentation. The Release Notes and other documentation are available in the product distribution and online at Review each product's release notes and other product documentation for major new features added in the release. Check the installation guides for your products for integration dependencies that you need to follow. If you are upgrading, will the important features in your current deployment still work after you install the new software? The Release Notes may list features that have been replaced or dropped from previous releases. If you haven't upgraded your deployment for a few releases, it is likely that some functionality or system requirements have changed. Check the product's Release Notes for the releases you missed to ensure that the functionality you need is still supported, or if it has changed. If the functionality has changed, you can find information in the product documentation on how to configure and use the new replacement feature after migration. Unsupported data or component functionality is not migrated to a newer release. Before upgrading, determine your options for changed or dropped functionality before starting the migration process. Obtain Licensing After you have determined the path to migrate to release 12.3, contact Dynatrace to obtain the necessary licenses for a direct or phased migration. If you are currently up to date with maintenance fees, you can contact Customer Support to obtain licenses for both back and current releases. If your maintenance has expired, contact your Dynatrace sales representative. For more information, see Customer Support Information [p. 8] and Licensing Data Center Real User Monitoring Components [p. 73]. Inventory the Current Deployment When you install or upgrade Dynatrace products, you should start with a careful inventory of what you already have. Determine Current Version and Maintenance Levels If you are upgrading an existing installation, be aware that only certain product releases can migrate directly to the current release. If you have older software installed, you may need to upgrade to an intermediate release first and then upgrade that installation to the current release. If you are upgrading to release 12.3, you should first determine what releases you currently have deployed for all of your Dynatrace components. 18

19 Chapter 2 Planning and Preparation Determine the existing deployment's release number and maintenance level (service packs applied to the release). In the Help About screens, you should see the release number and service pack level, or a release and build number that reflects your latest installation. This information is also provided in product log files. Knowing this information also helps you when discussing installation and upgrade plans with Dynatrace. Diagram Your Installation While you are determining the release levels that your Dynatrace products are on, it is also a good idea to have an inventory of your entire Dynatrace implementation, including the deployed management servers, databases, and agents. The quantity of servers and agents and the platforms they are running on, are factors in planning. A good practice is to create a diagram of your installation so you are aware of all of the components and any access issues that may arise. A deployment diagram is often very helpful in explaining your situation when you need assistance from Customer Support. Identify Latest Hardware and Software Requirements The system requirements for all Dynatrace products evolve as their environments, such operating systems, application servers, and databases evolve. It is therefore possible that your current installation environment will not support the latest release. Check the release 12.3 installation guide for the product solution you use to see whether the components of your current installation environment, such as operating systems, application servers, and databases are still supported. Purchasing and deploying any required new software should be built into the timeline and budget for your migration. You should also check the hardware requirements for each solution used prior to migrating. As Dynatrace improves its monitoring abilities, more disk space and memory may be required to process the additional data. Minimum specifications are provided in the product's installation guide; Dynatrace stresses that you configure your environment using the recommended specifications, if available. Purchasing and deploying new hardware should be built into the timeline and budget for your migration. Estimate the Installation or Upgrade Duration These estimates are guidelines. Your experience may vary based on the server machines you have deployed, network bandwidth, and other factors. After you inventory your current installation, review the following information to estimate the time to migrate your deployment. Each report server (CAS or ADS) must be installed or upgraded by logging into the machine and manually running the installation application. Estimate 0.5 hours for each report server installed. This estimate does not include the database migration estimate (below). If you are upgrading your report server from release 12.0 or later to the current release (12.3), the installer should handle the upgrade automatically. If you are upgrading from an earlier release, you have a longer upgrade path. If upgrading, estimate 3.0 hours to migrate per 100 GB of data in a report server database. (1.5 hours creating the backup and 1.5 hours for database migration). 19

20 Chapter 2 Planning and Preparation 20

21 CHAPTER 3 System Requirements Ensure that your system meets the requirements to run DC RUM components. NOTE Satisfying the minimum requirements may not ensure optimal usability. Choose the most appropriate hardware and system platform to achieve a successful installation. Recommended Platforms for AMDs and Report Servers This section describes the platforms recommended for the AMDs and report servers. IMPORTANT To obtain optimal and reliable performance from your Dynatrace software, we strongly recommend you use the platforms described in this section. Dynatrace makes no predictions or guarantees about the suitability or performance of any other hardware. Customers who purchase other hardware may experience performance or compatibility problems. Tier 1 vs Tier 2 AMD hardware is recommended in two hardware levels: Tier 1 and Tier 2. A Tier 2 platform can host more monitoring interfaces than a Tier 1 platform. The analysis volume and data processing capacity is the same for both tiers. Recommended Cisco Platforms This section describes the recommended platforms from Cisco. 21

22 Chapter 3 System Requirements Cisco Platforms Recommended for AMD Table 1. Cisco Tier 1 AMD Cisco UCS C240 M3 IMPORTANT To maximize performance, open the machine's BIOS configuration and change the CPU performance setting to High Throughput. Recommended Components Platform RAID controller Slots CPUs Memory HDDs Remote Management Power Supply Cisco UCS C240 M3 server LSI 6G MegaRAID i card + battery backup (RAID 0, 1, 5, 6, 10, 50, 60) 1GB cache (5x) PCIe 3.0 slots: (1x) full-height, half-length X16 slot, (1x) full-height, three quarter-length X16 slot, (2x) full-height, half-length x8 PCIe slots, and (1x) half-height, half-length x8 PCIe slot (used for disk controller) (2x) Intel Xeon Processor E5-2690, 8 core (20 MB Cache, 2.90 GHz) 64 GB RAM (DDR MHz RDIMM/PC /Dual Rank Technology: 6G, 15K RPM, SAS or better. Capacity: 600 GB free space or greater. RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. Cisco Integrated Management Controller (2x) 650W power supply Table 2. Cisco Tier 2 AMD Cisco UCS C460 M2 Recommended Components Platform RAID controller Slots CPUs Memory HDDs Remote Management Cisco UCS C460 M2 LSI 6G MegaRAID i card (RAID 0, 1, 5, 6, 10, 60) 512 MB cache 10x PCIe - 1x PCI2.0 (x16) ¾ length, 4x PCI2.0 (x8) ¾ length, 3x PCI2.0 (x4) ½ length, 1x PCI1.0 (x4) ½ length, 1x PCI1.0 (x4) ¾ length (2x) Intel Xeon Processor E (24 MB cache, 2.67 GHz) 64 GB RAM (DDR MHz DRAMs) Technology: 6G, 15K RPM, SAS or better. Capacity: 600 GB free space or greater. RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. Cisco Integrated Management Controller Version: 1.2(1a) 22

23 Chapter 3 System Requirements Table 2. Cisco Tier 2 AMD Cisco UCS C460 M2 (continued) Recommended Components DVD-ROM Power Supply (2x) 850W Power supply Unit for C-SERIES C460 M1 Battery Back-up Cisco Platforms Recommended for Report Servers Table 3. Cisco report server Cisco UCS C240 M3 IMPORTANT To maximize performance, open the machine's BIOS configuration and change the CPU performance setting to High Throughput. Recommended Components Platform RAID controller Slots CPUs Memory HDDs Remote Management Power Supply Cisco UCS C240 M3 server LSI 6G MegaRAID i card + battery backup (RAID 0, 1, 5, 6, 10, 50, 60) 1GB cache (5x) PCIe 3.0 slots: (1x) full-height, half-length X16 slot, (1x) full-height, three quarter-length X16 slot, (2x) full-height, half-length x8 PCIe slots, and (1x) half-height, half-length x8 PCIe slot (used for disk controller) (2x) Intel Xeon Processor E5-2690, 8 core (20 MB Cache, 2.90 GHz) Refer to Report Server General Requirements [p. 26] to select a memory configuration appropriate to your needs. Refer to Report Server General Requirements [p. 26] to select a disk configuration appropriate to your needs. Cisco Integrated Management Controller (2x) 650W power supply Recommended Dell Platforms This section describes the recommended platforms from Dell. Dell Platforms Recommended for AMD Table 4. Dell Tier 1 AMD Dell PowerEdge R720 Recommended Components Platform RAID controller Dell PowerEdge R720 PERC H710P Integrated 23

24 Chapter 3 System Requirements Table 4. Dell Tier 1 AMD Dell PowerEdge R720 (continued) Recommended Components Slots CPUs Memory HDDs Remote Management Power Supply (1x) x16 full-length, full-height, (3x) x8 full-length, full-height, (3x) x8 half-length, half-height (2x) Intel Xeon Processor E5-2690, 8 core (20 MB Cache, 2.90 GHz) 64GB (DDR MHz DRAMs) Technology: 6G, 15K RPM, SAS or better Capacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. idrac7 with Life Cycle controller (2x) 750W power supply Dell Platforms Recommended for Report Servers Table 5. Dell report Server Dell PowerEdge R720 Recommended Components Platform RAID controller Slots CPUs Memory HDDs Remote Management Power Supply Dell PowerEdge R720 PERC H710P Integrated (1x) x16 full-length, full-height, (3x) x8 full-length, full-height, (3x) x8 half-length, half-height (2x) Intel Xeon Processor E5-2690, 8 core (20 MB Cache, 2.90 GHz) Refer to Report Server General Requirements [p. 26] to select a memory configuration appropriate to your needs. Refer to Report Server General Requirements [p. 26] to select a disk configuration appropriate to your needs. idrac7 with Life Cycle controller (2x) 750W power supply Recommended HP Platforms This section describes the recommended platforms from HP. HP Platforms Recommended for AMD Table 6. HP Tier 1 AMD HP DL 380 Gen8 Recommended Components Platform RAID controller HP DL 380 Gen8 HP Smart Array P420 2GB 24

25 Chapter 3 System Requirements Table 6. HP Tier 1 AMD HP DL 380 Gen8 (continued) Recommended Components Slots CPUs Memory HDDs Remote Management Power Supply (1x) full-height, full-length X16 slot, (1x) full-height, half-length X8 slot, (1x) full-height, half-length X4 slot, (1x) full-height, full-length X16 slot, (1x) full-height, half-length X8 slot, (1x) full-height, half-length X8 slot (2x) Intel Xeon Processor E5-2690, 8 core (20 MB Cache, 2.90 GHz) 64GB (DDR MHz DRAMs) Technology: 6G, 15K RPM, SAS or better Capacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. HP ilo (2x) 750W power supply Table 7. HP Tier 2 AMD HP DL 580 G7 Recommended Components Platform RAID controller Slots CPUs Memory HDDs Remote Management Power Supply HP DL 580 G7 Smart Array P410i (2x) full-height full-length x16, (2x) full-height full-length x8, (4x) full-height full-length x4, (2x) full-height full-length PCI-X 64-bit 100MHz (2x) Intel Xeon Processor X7542, 6 core (18 MB Cache, 2.66 GHz) 64GB (DDR MHz DRAMs) Technology: 6G, 15K RPM, SAS or better Capacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. HP ilo (2x) 1200W power supply HP Platforms Recommended for Report Servers Table 8. HP Report Server HP DL 380 Gen8 Recommended Components Platform RAID controller Slots CPUs HP DL 380 Gen8 HP Smart Array P420 2GB (1x) full-height, full-length X16 slot, (1x) full-height, half-length X8 slot, (1x) full-height, half-length X4 slot, (1x) full-height, full-length X16 slot, (1x) full-height, half-length X8 slot, (1x) full-height, half-length X8 slot (2x) Intel Xeon Processor E5-2690, 8 core (20 MB Cache, 2.90 GHz) 25

26 Chapter 3 System Requirements Table 8. HP Report Server HP DL 380 Gen8 (continued) Recommended Components Memory HDDs Remote Management Power Supply Refer to Report Server General Requirements [p. 26] to select a memory configuration appropriate to your needs. Refer to Report Server General Requirements [p. 26] to select a disk configuration appropriate to your needs. HP ilo (2x) 750W power supply Report Server General Requirements A report server platform should meet or exceed the following requirements: CPUs At least 2x quad core CPU (or at least 8 cores in total) working with at least 2 GHz clock. In general, performance improves with higher CPU frequencies and core counts. Under testing, the best performance-to-cost ratio was achieved with 12 cores. Operating System Select a server capable of running one of the following Windows editions with the latest release, service packs, and 5 Client Access Licenses (CALs). Operating System Microsoft Windows 2003 (SP2) Microsoft Windows 2003 R2 Microsoft Windows 2008 Microsoft Windows 2008 R2 Microsoft Windows 2012 Microsoft Windows 2012 R2 Memory-related Requirements Standard Edition 64 bit (x64) for installations up to 32 GB RAM, or Enterprise Edition 64 bit (x64) for installations exceeding 32 GB RAM. Standard Edition or Datacenter Edition for installations up to 4 TB RAM. SQL Server Only Microsoft SQL Server 2005, SQL Server 2008 R2, and SQL Server 2012 are supported. We recommend that you acquire a Microsoft SQL Server Standard Edition license with 5 Server - User Client Access Licenses (CALs). This recommendation is based on the following assumptions: You need a single database user connection to Microsoft SQL Server. Only one server application is connected. All CAS, ADS, and RUM Console users connect through these applications to SQL Server using a web connection (Internet or intranet, depending on the deployment). We assume that you are licensing SQL Server only for this deployment of the Dynatrace software configurations discussed here. If the machine on which you install CAS or ADS also co-hosts other software that uses SQL Server, or if you are connecting CAS or ADS 26

27 Chapter 3 System Requirements to a SQL Server installation deployed on another machine, you may need a different licensing arrangement. Be sure to examine your total configuration (including Dynatrace software and any other software that uses SQL Server) and acquire appropriate SQL Server licensing. In future releases, data from other Dynatrace modules may be co-hosted on the same SQL Server, expanding on the current single database connection. Memory and HDDs The memory and hard disk drive (HDD) requirements of your report server depend on the functions assigned to that report server. The following table lists module system requirements in terms of RAM size (minimum and recommended), HDD requirements (minimum), and module intercompatibility. Note that these numbers are per module. Refer to the next table for recommended machine configurations. In the Min. HDD column, RAID specifications refers to: Technology: 6G, 15K RPM, SAS or better. Capacity: 600 GB free space or greater. RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. Table 9. Component-Specific System Requirements and Recommendations Acronyms used in this table: CAS = Central Analysis Server, ADS = Advanced Diagnostics Server, CAS SQL = the CAS SQL database, ADS SQL = the ADS SQL database, RUM Console Server = the server portion of the RUM Console software, CSS = Central Security Server, and Portal = Dynatrace Enterprise Portal. Module Min. RAM Rec. RAM Min. HDD Can co-exist with CAS 24 GB 32 GB 10 GB CAS SQL, RUM Console Server, CSS, Portal ADS 24 GB 32 GB 10 GB ADS SQL, RUM Console Server, CSS, Portal CAS SQL 24 GB 32 GB See RAID specifications above. CAS, RUM Console Server, CSS, Portal ADS SQL 24 GB 32 GB See RAID specifications above. ADS, RUM Console Server, CSS, Portal RUM Console Server 2 GB 2 GB 1 GB CAS, ADS, CAS SQL, ADS SQL, CSS, Portal CSS 4 GB 4 GB 800 MB CAS, ADS, CAS SQL, ADS SQL, Portal Portal 4 GB 4 GB 10 GB CAS, ADS, CAS SQL, ADS SQL, CSS 27

28 Chapter 3 System Requirements In the table below, you may find one of the first two configurations below particularly useful. For each row, the listed RAM should be sufficient for that machine running those modules, but adding more RAM may improve performance. In the HDD column, RAID specifications refers to: Technology: 6G, 15K RPM, SAS or better. Capacity: 600 GB free space or greater. RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. Table 10. Example Report-Server Machine Configurations NOTE For production environments, we highly recommend that the CAS and ADS be installed on separate servers to ensure a solid level of performance. We support installation of the CAS and ADS on the same server for non-performance testing and demonstration purposes only. Modules RAM HDD CAS + CAS SQL database + RUM Console Server ADS + ADS SQL database + RUM Console Server 64 GB 64 GB See RAID specifications above. See RAID specifications above. CAS CAS + CAS SQL database ADS ADS + ADS SQL database CAS SQL + RUM Console Server ADS SQL + RUM Console Server CAS+ Dynatrace Enterprise Portal 32 GB 64 GB 32 GB 64 GB 32 GB 32 GB 48 GB 10 GB See RAID specifications above. 10 GB See RAID specifications above. See RAID specifications above. See RAID specifications above. See RAID specifications above. Recommended Operating System Configuration for Report Servers Typical preparations for a secure report server deployment require several steps to be performed on the side of the operating system. This section does not include all possible preventive measures; it is intended only to serve as a list of recommended good system administration practices for system hardening. 1. Disable all unnecessary services. Disable all unused system accounts (for example, Guest or SQLDebugger). Disable DCOM. 28

29 Chapter 3 System Requirements Turn off indexing on all volumes (services). Disable network protocols and bindings: SMB NetBios over TCP/IP Disable the following services (if unused): Alerter Application Layer Gateway Service Application Management Automatic updates Background Intelligent Transfer Service (BITS) Computer Browser ClipBook Distributed File System Distributed Link Tracking Client Distributed Link Tracking Server MS Software Shadow copy Provider DNS Server Error Reporting Service File replication Help and support HTTP SSL Human Interface Device Access IAS Jet Database Access IMAPI CD Burning COM Service Indexing Service Intersite Messaging Kerberos Key Distribution Center License Logging Service Messenger Microsoft Search NetMeeting Remote Desktop Sharing Network DDE Network DDE DSDM Network Location Awareness (NLA) Print Spooler Remote Registry Server SNMP Trap Service SQL Server FullText Search TCP/IP NetBIOS Helper Service Telnet Telephony Windows Management Instrumentation Driver Extension 29

30 Chapter 3 System Requirements WMI Performance Adapter Windows Image Acquisition (WIA) 2. Remove all unnecessary executables and registry entries. 3. Apply restrictive permissions to files, services, end points and registry entries. All of these values should be created under the following registry key (if not present already): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters SynAttackProtect, REG_DWORD, 1 EnableDeadGWDetect, REG_DWORD, 0 NoNameReleaseOnDemand, REG_DWORD,1 EnablePMTUDiscovery, REG_DWORD, 0 KeepAliveTime, REG_DWORD (time in milliseconds), EnableICMPRedirect, REG_DWORD, 0 DisableIPSourceRouting, REG_DWORD, 2 TcpMaxConnectResponseRetransmissions, REG_DWORD, 2 TcpMaxDataRetransmissions, REG_DWORD, 3 PerformRouterDiscovery, REG_DWORD, 0 TcpMaxPortsExhausted, REG_DWORD, 5 All values given above are hexadecimal. Microsoft SQL Server Installation Recommendations Be sure that your SQL Server installation is configured for reliable and secure functioning with Central Analysis Server For an instance name, accept the default. For authentication mode, choose mixed. For collation settings, accept the default. Disable error and usage reports. Central Analysis Server and Network Monitoring Enterprise Manager Installation When planning an installation of the CAS and Network Monitoring Enterprise Manager on a single machine, ensure that all hardware and software requirements are met by both components. Also take into consideration any additional factors that may influence the operation of CAS or Network Monitoring, such as service pack installation, upgrade of only one of the two services, performance issues (during data collections performed by Enterprise Manager), and port assignments (for communication with Probes and database server). 30

31 CHAPTER 4 Installing the Report Server Use the Dynatrace suite media browser to locate and start the installation wizard for your report server. Note that no installation actions are performed until all of the installation information has been gathered and you have confirmed that the installation should proceed. IMPORTANT This section describes the basic procedure for upgrading this component. For important additional information concerning backup and recovery procedures, see the component-specific installation guide. Running a CAS Setup You must have administrator privileges to install the CAS. Before You Begin Failover If you are creating a failover installation, do not use this procedure. Instead, see the failover procedures. For more information, see Providing Failover for Report Server in the Data Center Real User Monitoring Advanced Diagnostics Server Installation Guide. Order of Component Installation RUM Console Before installing the CAS, install the RUM Console on the same machine or on another machine with network access to this machine. CSS When you install RUM Console (above), you will have to connect to a local or remote installation of CSS. If you don't already have CSS installed somewhere, you can install it during RUM Console installation. When you install the CAS, if the CAS installer cannot detect a CSS installation on the local machine, you must provide the address of a remote CSS installation before CAS installation can continue. 31

32 Chapter 4 Installing the Report Server Only one installation of CSS is required for all of the DC RUM components. If you have already installed CSS during the installation of any other component, provide the connection details during the CAS installation. Upgrade Considerations If you are upgrading your report server from release 12.0 or later to the current release (12.3), the installer should handle the upgrade automatically. If you are upgrading from an earlier release, you have a longer upgrade path. To install the report server: Locate and Run the Installer 1. Exit all other programs before running the setup program. Some Windows programs, such as anti-virus software, may interfere with the upgrade process. 2. If you have downloaded the full contents of the software installation set or if you are starting from an installation disc: a. Run the setup.exe application. The media browser opens. b. On the Data Center Real User Monitoring tab of the media browser, click Central Analysis Server (CAS). The default installation is for a 64-bit architecture. If you need a 32-bit installation, find the installer in the Central Analysis Server directory of the distribution media and run it directly from the file system. c. Go to Step 4 [p. 32] 3. If you are starting from a product installation file you have downloaded: a. Double-click the product installation file to start the installer. b. Go to Step 4 [p. 32] You can download product installation files and related documentation from You need to register with the site and obtain a login before you can access it. Provide the Configuration Requirements 4. If the detected amount of physical memory (RAM) on the target machine is lower than the recommended amount, a warning message is displayed. You need to install the report server on a machine with at least the minimum RAM as stated in Data Center Real User Monitoring Hardware Recommendations, which you can download from If your machine has insufficient memory, click Cancel to stop the installation and, if possible, upgrade 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. 5. On the Introduction screen, click Next. 32

33 Chapter 4 Installing the Report Server The License Agreement screen is displayed. 6. On the License Agreement screen, read the license, indicate that you accept the terms, and click Next. If you do not accept the terms, you can click Cancel to terminate the installation. 7. On the Installation Folder screen, type or browse for the target installation directory and click Next. NOTE If other DC RUM products are currently active on the target machine, their services are stopped automatically before the CAS is installed. 8. If the Security Configuration screen is displayed, provide all requested CSS connection information. You cannot continue until you provide working CSS connection information. The Host and Port settings describe the CSS connection. Host IP address of the CSS host. Port Port number of the CSS host. Default: 4182 The User name and Password settings are displayed only when upgrading from a release earlier than You need to provide the credentials of a CSS user with administrative privileges when you migrate users from an old installation. User Name Enter the user name for your CSS administrator account. Password Enter the password for your CSS administrator account. 9. If a previous installation has been detected, the Upgrade screen will prompt you for the type of upgrade you want to run (with or without changing the current configuration). If this is an upgrade, not a fresh installation, refer to the upgrade procedure. For more information, see Running a CAS Upgrade [p. 41]. 10. On the Database Configuration Properties screen, indicate whether you want to create a new database or use an existing database. 11. On the Database Connection Properties screen, define the SQL database connection properties. The report server requires a database to store run-time data. Specify: Host[/instance], Port Note that if you are installing the report server and the SQL Server on a single machine, it is required that the service name for SQL Server uses the default name (MSSQLSERVER). If necessary, consult your database administrator to determine the correct values. 33

34 Chapter 4 Installing the Report Server If the database server is on the same machine, you can enter the word localhost in the Host/instance field. For a remote server, set Host/instance to the server name or IP address. Use SSL encryption for SQL Server connection Select or clear this check box to indicate whether SSL should be used in communication between the report server and SQL Server. Database Name Enter the name for the report server database. Database user The default database username can be replaced with a local database server user or a valid domain user. To specify a domain name, use the domain\user format. (This field cannot be edited when you upgrade from older releases). If you are creating a database on Microsoft SQL Server 2008 and plan to use a Windows domain user as the database user, you must enable this account on the SQL Server prior to the report server installation. Password Password for database user specified above. Administrator login, Password The login name and password for the database administrator. If you create the database and database user manually before you install the report server, you can choose not to enter a database password during report server installation. (This may be a security requirement in your computing environment). In this case, leave these fields unchanged. See the report server installation guide for details on manual database administration. Database size The size of the database in gigabytes. Database location The database device location is the physical location of the database on the database server computer. If you selected to upgrade the report server without changing the settings, there are three options for the current 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 of the database configuration settings are lost. 12. If the Database Size screen is displayed, specify the size of the new database and then click Next. 34

35 Chapter 4 Installing the Report Server This screen is displayed if no database of the specified name already exists, or if you have selected to overwrite an existing database. The suggested size displayed on this screen is calculated to leave room for performing a backup of the database on the same disk. 13. If the Database Server Memory screen is displayed, specify the maximum size of the SQL server memory and then click Next. This screen is displayed if a new database is created or if an existing database is overwritten. Note that for the reconfiguration to take effect, SQL Server must be restarted. If you are using a local SQL Server, the installation program offers to restart it automatically. If you have specified a remote SQL Server, you are asked to restart the server manually before attempting to use the database. Select Use all available RAM during database upgrade if you don't need the RAM for other purposes during this upgrade. 14. On the Connectivity Options screen, review the HTTP/HTTPS settings for your report server. 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. Use HTTPS (HTTP over SSL) 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. 15. If the SSL Key Generation Data screen is displayed, specify the encryption key information. You can either automatically generate a key and a certificate, or to use a custom encryption key. To generate the key, provide the required data, which varies depending on whether you selected automatic or custom key generation. The SSL Key Generation Data screen enables you to enter the information required to generate a new key. For a custom encryption key, you can provide only the password; the other fields cannot be edited. 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. 35

36 Chapter 4 Installing the Report Server 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. Address The address. 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. For more information, see Configuring Report Server to Use Private Keys and Certificates [p. 37]. 16. If the SSL Key Security screen is displayed, specify the encryption key security information. Key Password, Confirm Key Password The password associated with the key. Remember the key password Whether to remember the password. TIP For Windows 2008, it is strongly recommended that you select the Remember the key password check box when you install your report server. If you do not do so, you will be asked for that password at every service start. Furthermore, when Interactive Service Detection is disabled you will not see the message at all and will not be able to provide a passphrase for the private SSL key. 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. 17. If the RUM Console Connection screen is displayed (because no local RUM Console installation was detected), enter the address and port of a remote RUM Console installation and then click Next. Note that you can change these settings later. For more information, see Changing the RUM Console Connection Information [p. 70]. 18. On the Documentation page, choose whether and where to install user manuals. You can choose to skip the installation of manuals, or to install them from a directory of your choice. 19. On the Help page, choose whether and where to install online help. 36

37 Chapter 4 Installing the Report Server You can choose to skip the installation of help, or to install it from a directory of your choice. Install the Software 20. 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. 21. Your software is installed. The process of installing and pre-configuring software components and defining your database may take several seconds, minutes, or even hours, depending on the size of the database. A progress box shows the status of the installation action currently in progress. When all of the required actions have been completed, a final post-installation information screen is displayed. 22. On the Installation Summary screen, review the installation summary. Click Show postinstall summary to open a file containing a summary of the installation up to this point. 23. When the installation is complete, indicate whether you want to start the CAS and click Finish. 24. If the Computer Restart screen is displayed, indicate whether you want to restart your computer now and click OK. What to Do Next If you have not already obtained and installed a license, do so now. For more information, see Licensing Data Center Real User Monitoring Components [p. 73]. Configuring Report Server to Use Private Keys and Certificates Set up the report server to use secure connections with users' web browsers and to use automatically generated data or your own keys and certificates. Before You Begin It is recommended that secure access be performed using TLSv1 (TLS version 1), which is more secure than its predecessors. If an older version of the protocol is required, configure it by setting the configuration property, connector.ssl.sslprotocol to SSLv3 or SSLv2. Note that the Apache Tomcat default is all and the acceptable values are SSLv2, SSLv3, TLSv1, and SSLv2+SSLv3. If the connector.ssl.sslprotocol property is left blank, it causes the web browser to negotiate the version of a secure protocol when connecting to the web server. For more information about secure connection configuration in Apache Tomcat, refer to 37

38 Chapter 4 Installing the Report Server The report server implementation of SSL uses OpenSSL, so the encryption, certification, and other operations are handled as they are defined in OpenSSL. The subdirectory tools\openssl of the report server installation directory contains the OpenSSL tool, which can be used for the SSL key and certificate generation, conversions, and management. The report server installation process uses the tools in this directory to generate a self-signed SSL certificate and a key pair for the initial HTTPS server operation. This certificate and the key pair are, by default, stored in the wwwroot/web-inf/ssl subdirectory of the report server installation directory. To change this path, modify the connector.ssl.sslcertificatefile and connector.ssl.sslcertificatekeyfile configuration properties in common.properties. To configure your own encryption keys and register the server in the CA (certificate authority) infrastructure, the common.properties file has to be edited manually. Refer to the Apache Tomcat documentation at All certification procedures, such as certificate request or certificate signing, have to be handled manually by using the OpenSSL utility. For instructions on how to use the OpenSSL utility, refer to The report server can connect to the network via standard HTTP or HTTPS (HTTP over SSL), both of which are supported by the report server installation process, or via other modes that can be configured manually. The connectivity configuration settings are stored in the configuration file common.properties in the config subdirectory of the report server installation directory. The names of the configuration properties in common.properties follow the standard names used for Tomcat and OpenSSL. The format of the file is different, but the names of the configuration parameters are the same. All of the connectivity configuration properties are set by the installation program during report server installation. NOTE Subsequent modifications to connectivity settings are possible but should be performed with great care. These settings require a thorough understanding of web server connector settings and OpenSSL. The simplest procedure for joining the server to the certification infrastructure can be summarized as follows: 1. Generate a private RSA key as described in It is suggested that the password should be encrypted. The report server can ask for the key password every time it starts, or the password can be configured using the report server installation program. 2. Create a certificate request as described in (section 3). 3. Pass the certificate to a certification authority for signing. 4. Set configuration properties. 38

39 Chapter 4 Installing the Report Server Configure the following settings in the common.properties file: Point connector.ssl.certificatefile to the received certificate file. Point connector.ssl.certificatefilekey to the generated key. Point connector.ssl.certificatechainfile to the chain of certificates. 5. Set the key password. If the key was encrypted, use the report server installation program to set the key password. Importing CA Certificates Following an industry standard practice, Dynatrace software installers and device drivers for Microsoft Operating Systems are digitally signed using a commercial Code Signing certificate from a Trusted Certificate Authority (Verisign or Thawte). Code Signing certificates require the use of a primary root and intermediate Certificate Authority (CA) certificate to ensure that signed code is fully trusted by users. As a result, the Dynatrace product installation process requires the presence of a primary root and intermediate CA certificate in the target client or server's local computer certificate store. If not present, the primary root and intermediate CA certificates are downloaded during the installation process using Microsoft's automatic root update mechanism, which requires an Internet connection. For more information about the Windows Root Certificate Program, refer to If the installer does not detect these certificates on the target installation client or server and an internet connection is not available, an Error 1330 message appears indicating an invalid digital signature error has occurred. In this case, you must download and manually install the primary root and intermediate root certificates prior to performing a product installation. To import the required CA certificates, perform the following steps: 1. Log in as an administrator on the target installation client or server. 2. Download the primary root CA certificate. a. Go to: The thawte root certificates page appears. b. Under Root 1 - Primary Root CA, right-click Download Root Now. c. Save the file to the Desktop and change the file name to thawte_primary_root_ca.cer. 3. Import the primary root CA into the certificate store. a. Double-click thawte_primary_root_ca.cer. The Certificate window appears. b. On the General tab, click Install Certificate. The Certificate Import Wizard appears. c. Click Next to continue. d. Select Place all certificates in the following store, and then click Browse. The Select Certificate Store window appears. 39

40 Chapter 4 Installing the Report Server e. Select the Show physical stores check box. f. Select Trusted Root Certification Authorities Local Computer, and then click OK. g. Click Next to continue. Verify that the destination of the certificate is correct. h. Click Finish to complete certificate import. A message indicating that the import was successful appears. 4. Download the intermediate root CA certificate. a. Go to: The Download the Thawte Intermediate and Cross Root CAs for Code Signing certificates page appears. b. In the text box under Code Signing Intermediate CA, save the text to the Desktop in a file named thawte_intermed_root_ca.cer. 5. Import the intermediate root CA into the certificate store. a. Double-click thawte_intermed_root_ca.cer. The Certificate window appears. b. On the General tab, click Install Certificate. The Certificate Import Wizard appears. c. Click Next to continue. d. Select Place all certificates in the following store, and then click Browse. The Select Certificate Store window appears. e. Select the Show physical stores check box. f. Select Intermediate Certification Authorities Local Computer, and then click OK. g. Click Next to continue. Verify that the destination of the certificate is correct. h. Click Finish to complete certificate import. A message indicating that the import was successful appears. 40

41 CHAPTER 5 CAS Upgrade Overview The CAS installation program will detect any older version of the CAS and offer to upgrade it to the current release. Optionally, the upgrade preserves configuration information and traffic monitoring data contained in the CAS database. If you are upgrading your report server from release 12.0 or later to the current release (12.3), the installer should handle the upgrade automatically. If you are upgrading from an earlier release, you have a longer upgrade path. If upgrading from an earlier version, you may need to manually perform some elements of configuration migration. In particular, this applies to the configuration of alerts. IMPORTANT This section describes the basic procedure for upgrading this component. For important additional information concerning backup and recovery procedures, see the component-specific installation guide. Upgrade Workflow Upgrade your components in the recommended order: 1. CSS 2. RUM Console 3. Central Analysis Server 4. Advanced Diagnostics Server 5. Agentless Monitoring Device 6. Dynatrace Enterprise Portal (if used) Running a CAS Upgrade To upgrade an earlier version of CAS to the latest version, fulfill the prerequisites described below, and then run the installer for the latest version of CAS. The installer will detect the earlier software and display your upgrade options. 41

42 Chapter 5 CAS Upgrade Overview Before You Begin Failover If you are creating a failover installation, do not use this procedure. Instead, see the failover procedures. For more information, see Providing Failover for Report Server in the Data Center Real User Monitoring Advanced Diagnostics Server Installation Guide. Migrating CAS from a 32-Bit Version to a 64-Bit Version A direct upgrade from a 32-bit version to a 64-bit version is not supported. If you need to perform such an upgrade: 1. Save your 32-bit configuration settings manually (this pertains only to new server configuration files added after the 32-bit installation). 2. Uninstall the 32-bit version of the product while preserving the database. 3. Install the 64-bit version as a new installation, not an upgrade. 4. Perform a manual migration of configuration settings. Note that settings maintained in the database are migrated with the database. For more information, see Migrating 32-bit CAS to 64-bit CAS (Same Platform, Local Database) [p. 48] and Migrating 32-bit CAS to 64-bit CAS (Same Platform, Remote Database) [p. 49]. Moving CAS to a New Machine To migrate CAS from one platform to another, including the local database: 1. Make backups of your databases and configurations from your old machine. 2. Install the software on the new machine. 3. Restore your databases and configurations on the new machine. For more information, see Migrating CAS to a New Platform (Local Database) [p. 51] and Migrating CAS to a New Platform (Remote Database) [p. 52]. Database Backup Back up the database. For more information, see Backing Up MS SQL Server 2005 CAS Databases [p. 109] and Backing Up MS SQL Server 2008 CAS Databases [p. 111]. Upgrading from Older Releases If you are upgrading your report server from release 12.0 or later to the current release (12.3), the installer should handle the upgrade automatically. If you are upgrading from an earlier release, you have a longer upgrade path. NOTE This software requires integration with CSS. Be sure that your CSS connection is running and reliable throughout report server installation or upgrade. Loss of CSS access during the procedure may cause loss of system integrity. For more information, see After CAS installation or upgrade, access to DMI reports is lost. [p. 85]. To upgrade a CAS installation (to install a newer version over an existing version): 42

43 Chapter 5 CAS Upgrade Overview Locate and Run the Installer 1. Exit all other programs before running the setup program. Some Windows programs, such as anti-virus software, may interfere with the upgrade process. 2. Download the installation package from the Downloads section of the Dynatrace Community. 3. Extract the installation package into a temporary directory. 4. Double-click setup.exe in the installation package to open the installation browser. 5. On the Data Center Real User Monitoring tab, click Central Analysis Server (CAS). The default installation is for a 64-bit architecture. If you need a 32-bit installation, find the installer in the Central Analysis Server directory of the distribution media and run it directly from the file system. IMPORTANT Upgrading from a 32-bit version to a 64-bit version is not supported. For more information, see Migrating 32-bit CAS to 64-bit CAS (Same Platform, Local Database) [p. 48] and Migrating 32-bit CAS to 64-bit CAS (Same Platform, Remote Database) [p. 49]. 6. 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. Provide the Configuration Requirements 7. On the Introduction screen, click Next. The License Agreement screen is displayed. 8. On the License Agreement screen, read the license, indicate that you accept the terms, and click Next. If you do not accept the terms, click Cancel to terminate the installation. 9. If the Security Configuration screen is displayed, provide all requested CSS connection information. You cannot continue until you provide working CSS connection information. The Host and Port settings describe the CSS connection. Host IP address of the CSS host. Port Port number of the CSS host. Default: 4182 The User name and Password settings are displayed only when upgrading from a release earlier than You need to provide the credentials of a CSS user with administrative privileges when you migrate users from an old installation. 43

44 Chapter 5 CAS Upgrade Overview User Name Enter the user name for your CSS administrator account. Password Enter the password for your CSS administrator account. 10. If the Upgrade screen is displayed (because a previous installation has been detected), indicate whether you want to change the current configuration while you upgrade the software. If you choose to upgrade the software without changing the current settings, a minimal sequence of setup screens (Database Connection Properties, Database Server Memory, and Installation Options - Summary), with minimal editing options, are displayed. Review them before upgrading to If you want to change any settings, use the Back button to come back to the Upgrade screen and select the other option. If you choose to change settings and upgrade the software to the new version, the full set of configuration screens as outlined below are displayed to specify new configuration settings and upgrade to release Report Server Settings NOTE 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. 11. On the Installation Folder screen, type or browse for the target installation directory and click Next. NOTE If other Dynatrace products are currently active on the target machine, their services are stopped automatically before CAS is installed. 12. On the Database Configuration Properties screen, indicate whether you want to create a new database or use an existing database. 13. On the Database Connection Properties screen, review the SQL database connection properties and adjust them as needed. Database upgrade options: 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. 44

45 Chapter 5 CAS Upgrade Overview 14. If the Database Server Memory screen is displayed, specify the maximum size of the SQL Server memory and click Next. This screen is displayed if a new database is created or if an existing database is overwritten. Note that for the reconfiguration to take effect, SQL Server must be restarted. If you are using a local SQL Server, the installation program offers to restart it automatically. If you have specified a remote server, you are asked to restart the server manually before attempting to use the database. When you click Next from the Database Server Memory screen, an additional screen prompts you to specify whether to use all available RAM during the database upgrade. Select the check box if you don't need the RAM for other purposes during this upgrade. 15. On the Connectivity Options screen, review the HTTP/HTTPS settings for your report server. 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. Use HTTPS (HTTP over SSL) 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. 16. If the SSL Key Generation Data screen is displayed, specify the encryption key information. You can either automatically generate a key and a certificate, or to use a custom encryption key. To generate the key, provide the required data, which varies depending on whether you selected automatic or custom key generation. The SSL Key Generation Data screen enables you to enter the information required to generate a new key. For a custom encryption key, you can provide only the password; the other fields cannot be edited. 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. 45

46 Chapter 5 CAS Upgrade Overview 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. Address The address. 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. For more information, see Configuring Report Server to Use Private Keys and Certificates [p. 37]. 17. If the SSL Key Security screen is displayed, specify the encryption key security information. Key Password, Confirm Key Password The password associated with the key. Remember the key password Whether to remember the password. TIP For Windows 2008, it is strongly recommended that you select the Remember the key password check box when you install your report server. If you do not do so, you will be asked for that password at every service start. Furthermore, when Interactive Service Detection is disabled you will not see the message at all and will not be able to provide a passphrase for the private SSL key. 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. 18. If the RUM Console Connection screen is displayed (because no local RUM Console installation was detected), enter the address and port of a remote RUM Console installation and then click Next. Note that you can change these settings later. For more information, see Changing the RUM Console Connection Information [p. 70]. 19. On the Documentation page, choose whether and where to install user manuals. You can choose to skip the installation of manuals, or to install them from a directory of your choice. 20. On the Help page, choose whether and where to install online help. 46

47 Chapter 5 CAS Upgrade Overview You can choose to skip the installation of help, or to install it from a directory of your choice. Install the Software 21. 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. 22. 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. 23. Indicate whether you want to start CAS, and then click Finish to exit the installation program. 24. Clear your browser cache. This ensures that your upgraded CAS configuration is displayed correctly. What to Do Next If you have not already obtained and installed a license, do so now. For more information, see Licensing Data Center Real User Monitoring Components [p. 73]. CAS Smoke Test After upgrading the CAS to the latest release, conduct the following validation steps. 1. Review the <CAS_INSTALL_FOLDER>\log\install\Central_Analysis_Server_Install_xx_xx_xxxx_xx_xx_xx.log file to ensure that no errors occurred during migration, especially during the database upgrade. 2. From the CAS main menu, open Tools Diagnostics and view the System Status report. NOTE You should allow at least three hours after the upgrade to allow new data to be processed by the CAS. Review the following sections on the report: License Make sure that licences are valid and available for all decodes you require. Repository Make sure the current status of BULK INSERT is true. Connection with AMDs and Probes Make sure the CAS is able to reach all enabled AMDs and Probes. 47

48 Chapter 5 CAS Upgrade Overview Data processing Check whether there is a delay in data processing (if the CAS was just started, the delay should be decreasing slowly). Database info Maximum possible database size on this machine: Make sure there is enough space on the drive for the database to grow if necessary. Memory section a. Make sure the CAS meets or exceeds minimum memory size requirements. Refer to the Data Center Real User Monitoring Hardware Recommendations. b. Memory caches: make sure New server/url/client/site processing stopped equals false. Server settings Access Settings CAS Server Configuration and review user aggregation, client IP ranges, and site options to make sure settings were preserved. 3. Review CAS reports Check whether historical data is present; access data for previous days, check trends, baselines, reporting groups, applications, and transactions. Migrating 32-bit CAS to 64-bit CAS (Same Platform, Local Database) To migrate from 32-bit to 64-bit on the same platform, you need to make backups of your databases and configurations, then migrate and install the 64-bit software, and then restore your databases and configurations. IMPORTANT For this procedure, it is assumed that your CAS installation uses a local database. If you are using a remote database, see Migrating 32-bit CAS to 64-bit CAS (Same Platform, Remote Database) [p. 49]. Make Backups These steps are not just to make safety copies. You will need these backups to restore your data and configurations after migration. 1. Make a backup of the current CAS database. For more information, see Backing Up MS SQL Server 2005 CAS Databases [p. 109] and Backing Up MS SQL Server 2008 CAS Databases [p. 111]. 2. Make a backup of the current CSS database. For more information, see Backing Up CSS [p. 113]. 3. Make a backup of the RUM Console database. 4. Make a backup of the CAS %programfiles%\cas\config\ directory. Manually copy this folder and its contents to a safe location. 48

49 Chapter 5 CAS Upgrade Overview 5. Make a backup of the CAS %programfiles%\cas\classes\customqueries directory. Manually copy this folder and its contents to a safe location. Migrate and Install the Software 6. Migrate the operating system from 32-bit to 64-bit (assuming 32-bit DC RUM was installed on a 32-bit OS). 7. Install MS SQL server. 8. Install the CSS and RUM Console. Restore the Data and Get the New CAS Installation Running After the target environment is ready, restore your data and bring the CAS back up. 9. Restore the CSS database. For more information, see Restoring CSS [p. 116]. 10. Restore the RUM Console database. For more information, see Restoring the RUM Console Database [p. 119]. 11. Install 64-bit CAS. It is important that you install exactly the same CAS version (and service packs, if they were present) that you had previously. For more information, see Running a CAS Setup [p. 31]. 12. Stop and disable the CAS service. 13. Restore the entire %programfiles%\cas\config\ folder from your backup. Manually copy the backup files you made earlier back to the target installation. 14. Restore the entire %programfiles%\cas\classes\customqueries folder from your backup. Manually copy the backup files you made earlier back to the target installation. 15. Restore the CAS database from backup. 16. Open %programfiles%\cas\config\repository.properties and make sure that the JDBC_URL property is set to localhost and it points to the restored database. Example: JDBC_URL=jdbc:jtds:sqlserver://localhost:1433//CAS;tds=8.0;lastupdatecount=true; 17. Make sure the CSS and RUM Console services are running. 18. Start the CAS service. Migrating 32-bit CAS to 64-bit CAS (Same Platform, Remote Database) To migrate from 32-bit to 64-bit on the same platform, you need to make backups of your databases and configurations, then migrate and install the 64-bit software, and then restore your databases and configurations. 49

50 Chapter 5 CAS Upgrade Overview IMPORTANT For this procedure, it is assumed that your CAS installation uses a remote database. If you are using a local database, see Migrating 32-bit CAS to 64-bit CAS (Same Platform, Local Database) [p. 48]. Make Backups These steps are not just to make safety copies. You will need most of these backups to restore your data and configurations after migration. The SQL database backup is not absolutely necessary when you use a remote database, but it is still a very good idea to make a backup of your important data before you start making major system changes. 1. Make a backup of the current CAS database. For more information, see Backing Up MS SQL Server 2005 CAS Databases [p. 109] and Backing Up MS SQL Server 2008 CAS Databases [p. 111]. 2. Make a backup of the current CSS database. For more information, see Backing Up CSS [p. 113]. 3. Make a backup of the RUM Console database. 4. Make a backup of the CAS %programfiles%\cas\config\ directory. Manually copy this folder and its contents to a safe location. 5. Make a backup of the CAS %programfiles%\cas\classes\customqueries directory. Manually copy this folder and its contents to a safe location. Migrate and Install the Software 6. Migrate the operating system from 32-bit to 64-bit (assuming 32-bit DC RUM was installed on a 32-bit OS). 7. Install the CSS and RUM Console. Restore the Data and Get the New CAS Installation Running After the target environment is ready, restore your data and bring the CAS back up. 8. Restore the CSS database. For more information, see Restoring CSS [p. 116]. 9. Restore the RUM Console database. For more information, see Restoring the RUM Console Database [p. 119]. 10. Install 64-bit CAS. It is important that you install exactly the same CAS version (and service packs, if they were present) that you had previously. For more information, see Running a CAS Setup [p. 31]. 11. Stop and disable the CAS service. 12. Restore the entire %programfiles%\cas\config\ folder from your backup. Manually copy the backup files you made earlier back to the target installation. 50

51 Chapter 5 CAS Upgrade Overview 13. Restore the entire %programfiles%\cas\classes\customqueries folder from your backup. Manually copy the backup files you made earlier back to the target installation. 14. Open %programfiles%\cas\config\repository.properties and make sure that the JDBC_URL property is set to the correct hostname/ip of the remote MS SQL server and that it points to the restored database: JDBC_URL=jdbc:jtds:sqlserver://remote_host:1433//CAS;tds=8.0;lastupdatecount=true;. 15. Make sure the CSS and RUM Console services are running. 16. Start the CAS service. Migrating CAS to a New Platform (Local Database) To migrate the CAS from one platform to another, including the local database, you need to make backups of your databases and configurations from your old machine, then install the software on the new machine, and then restore your databases and configurations on the new machine. IMPORTANT For this procedure, it is assumed that your CAS installation uses a local database. If you are using a remote database, see Migrating CAS to a New Platform (Remote Database) [p. 52]. Make Backups These steps are not just to make safety copies. You will need these backups to restore your data and configurations after migration. 1. Make a backup of the current CAS database. For more information, see Backing Up MS SQL Server 2005 CAS Databases [p. 109] and Backing Up MS SQL Server 2008 CAS Databases [p. 111]. 2. Make a backup of the current CSS database. For more information, see Backing Up CSS [p. 113]. 3. Make a backup of the RUM Console database. 4. Make a backup of the CAS %programfiles%\cas\config\ directory. Manually copy this folder and its contents to a safe location. 5. Make a backup of the CAS %programfiles%\cas\classes\customqueries directory. Manually copy this folder and its contents to a safe location. Migrate and Install the Software 6. Install MS SQL Server on the new server. 7. If the CSS and RUM Console are also moving to the new machine, install them on the new machine now. 8. If the CSS and RUM Console are to remain on the old machine, copy the css.dat file from the old machine to the new machine (by default, this is located in %programdata%\compuware\security Client\). 51

52 Chapter 5 CAS Upgrade Overview 9. Install the CAS on the new machine. It is important that you install exactly the same CAS version (and service packs, if they were present) that you had previously. For more information, see Running a CAS Setup [p. 31]. 10. On the old machine, stop and disable CAS service, SQL Server service, and RUM Console service. The rest of this procedure applies to the new machine. Restore the Data and Get the New CAS Installation Running After the target environment is ready, restore your data and bring the CAS back up. 11. Restore the CSS database. For more information, see Restoring CSS [p. 116]. 12. Restore the RUM Console database. For more information, see Restoring the RUM Console Database [p. 119]. 13. Stop and disable the CAS service. 14. Restore the CAS database from the backup you made earlier. 15. Restore the entire %programfiles%\cas\config\ folder from your backup. Manually copy the backup files you made earlier back to the target installation. 16. Restore the entire %programfiles%\cas\classes\customqueries folder from your backup. Manually copy the backup files you made earlier back to the target installation. 17. Open %programfiles%\cas\config\repository.properties and make sure that the JDBC_URL property is set to localhost and it points to the restored database. Example: JDBC_URL=jdbc:jtds:sqlserver://localhost:1433//CAS;tds=8.0;lastupdatecount=true; 18. Start the CAS service. 19. Add or correct all necessary devices in the RUM Console configuration. If your new CAS is to be the source of time configuration for AMDs, open the configuration of each AMD and set the IP address of the server authorized to set AMD time accordingly. Migrating CAS to a New Platform (Remote Database) To migrate the CAS from one platform to another but using the same remote database, you need to make backups of your databases and configurations from your old machine, then install the software on the new machine, and then restore your databases and configurations on the new machine. IMPORTANT For this procedure, it is assumed that your CAS installation uses a remote database. If you are using a local database, see Migrating CAS to a New Platform (Local Database) [p. 51]. 52

53 Chapter 5 CAS Upgrade Overview Make backups These steps are not just to make safety copies. You will need most of these backups to restore your data and configurations after migration. The SQL database backup is not absolutely necessary when you use a remote database, but it is still a very good idea to make a backup of your important data before you start making major system changes. 1. Make a backup of the current CAS database. For more information, see Backing Up MS SQL Server 2005 CAS Databases [p. 109] and Backing Up MS SQL Server 2008 CAS Databases [p. 111]. 2. Make a backup of the current CSS database. For more information, see Backing Up CSS [p. 113]. 3. Make a backup of the RUM Console database. 4. Make a backup of the CAS %programfiles%\cas\config\ directory. Manually copy this folder and its contents to a safe location. 5. Make a backup of the CAS %programfiles%\cas\classes\customqueries directory. Manually copy this folder and its contents to a safe location. Migrate and Install the Software 6. If the CSS and RUM Console are also moving to the new machine, install them on the new machine now. 7. If the CSS and RUM Console are to remain on the old machine, copy the css.dat file from the old machine to the new machine (by default, this is located in %programdata%\compuware\security Client\). 8. Install the CAS on the new machine. It is important that you install exactly the same CAS version (and service packs, if they were present) that you had previously. For more information, see Running a CAS Setup [p. 31]. During the installation process, make sure that the new CAS does not overwrite the original database. 9. On the old machine, stop and disable CAS service and RUM Console service. The rest of this procedure applies to the new machine. Restore the Data and Get the New CAS Installation Running After the target environment is ready, restore your data and bring the CAS back up. 10. Restore the CSS database. For more information, see Restoring CSS [p. 116]. 11. Restore the RUM Console database. For more information, see Restoring the RUM Console Database [p. 119]. 12. Stop and disable the CAS service. 13. Restore the entire %programfiles%\cas\config\ folder from your backup. Manually copy the backup files you made earlier back to the target installation. 53

54 Chapter 5 CAS Upgrade Overview 14. Restore the entire %programfiles%\cas\classes\customqueries folder from your backup. Manually copy the backup files you made earlier back to the target installation. 15. Start the CAS service. 16. Add or correct all necessary devices in the RUM Console configuration. If your new CAS is to be the source of time configuration for AMDs, open the configuration of each AMD and set the IP address of the server authorized to set AMD time accordingly. 54

55 CHAPTER 6 Uninstalling a Report Server You can uninstall your report server through the Windows Add or Remove Programs control panel. 1. In Windows, open Start Control Panel. 2. Click Uninstall a program. 3. Select Dynatrace Central Analysis Server in the list of installed programs and click Uninstall/Change above the list. Alternative access methods: Double-click the product name. Right-click the product name and select Uninstall/Change. The Welcome screen presents you with options for the installed software. 4. Select the Uninstall option and click Next. 5. If software must be stopped, you will receive a warning; read it and click Next. It may take a few moments to stop the software. 6. Read the summary screen and then click Uninstall. 7. Re-start the system. 8. If you previously installed ADS and CAS on one machine, and you have now uninstalled just one of them, you need to restart the Watchdog Service Windows service manually before the remaining report server can restart. On a machine on which you have installed ADS and CAS, if you uninstall one of those report servers and leave the other one installed, the shared Watchdog Service for both of those report servers is stopped during uninstallation and it is not automatically restarted, which means that the remaining report server will not restart automatically. Find Watchdog Service in the list of Windows services on your machine and restart it manually. What to Do Next Note that report server software uninstallation does not remove or detach the database. If you want to discard the database, you need to do this manually using SQL Server management tools. 55

56 Chapter 6 Uninstalling a Report Server 56

57 CHAPTER 7 Logging in to the Report Server To connect to your report server, enter the server address in your browser. For a new installation, only the system administrator account created during installation is active. Log in with that account name and password. This lets you perform basic configuration tasks such as setting up business units (applications and transactions). You should then define additional users. Access the server as a system administrator only for configuration purposes. For more information, see Adding a User in the Data Center Real User Monitoring Administration Guide. For information on recommended browsers, see Supported Browsers and Connectivity [p. 12]. 57

58 Chapter 7 Logging in to the Report Server 58

59 CHAPTER 8 CAS Basic Configuration Settings When you use the CAS for the first time, you must specify a number of basic configuration options. These options must be configured before the CAS starts to function. Only users with administrative rights can modify the basic configuration settings. Every time the settings are updated on this screen, including the first time the application is run, the report server is restarted. When you click Update, the server is restarted and a message appears on the screen. Return to the CAS home page by clicking Continue. The report server restart can take a while, which may prevent you from quickly accessing the home page. 59

60 Chapter 8 CAS Basic Configuration Settings Figure 1. CAS Configuration Screen To modify settings after the report server is deployed, select Settings Central Analysis Server Server Configuration from the top menu. NOTE You can also modify these settings using the RUM Console. From the console top menu, select Devices and Connections Manage Devices, then choose Open configuration from the context menu for your CAS on the Devices screen. This command opens the configuration screen for a given server. To access settings related to users and sites, select Server Configuration from the menu. Sites, User Aggregation, and User Tracking A site is an organizing concept introduced to help report users identify particular IP networks. In this context, a site is defined as an IP network or a part of a network. A site is defined in one of two ways: Manual sites are specified as explicit IP address ranges. Automatic sites are based on either AS names or CIDR blocks, where a block is defined by an IP address and a network mask. 60

61 Chapter 8 CAS Basic Configuration Settings All client IP addresses that are neither manual nor automatic sites are treated as belonging to the Default site. All server IP addresses that do not fall into any of the manual or automatic site categories are treated as belonging to the Default Data Center site. User aggregation means that users are not recognized individually, but are counted per site. Note that if sites are based on AS names, users can still be aggregated to CIDR blocks within ASes. However, if sites are based on CIDR blocks, users cannot be aggregated to ASes because ASes are higher level aggregates than CIDR blocks. The option Base automatic sites on enables you to select automatic sites based on either ASes or CIDR blocks. You can also opt not to have automatic sites. The option Base user aggregation on enables you to aggregate users to ASes or CIDR blocks, subject to any additional aggregation and user tracking options you may configure. Note that user aggregation is compatible with the way you configure the creation of automatic sites. If automatic sites are based on CIDR blocks, user aggregation can also be based on CIDR blocks, but it cannot be based on ASes, because ASes are not recognized entities. However, if you choose automatic sites based on ASes, you will have the choice of aggregating users to ASes or individual CIDR blocks. Additional user tracking and aggregation options enable you to track or count all or selected IP addresses or user identifiers while aggregating other users. These options may require you to enter IP address ranges consisting of IP addresses separated by hyphens. Both IPv4 and IPv6 address formats are supported. To define a range of IP addresses, you have to specify the starting and ending addresses in the following way: IPv IPv6 2001:0db8:0000:0000:0000:0000:1622:35bd-2001:0db8:0000:0000:0000:0000:1999:35bd An IP address range has to be continuous. Note that you can type an IPv6 address in any of the following ways (they are equivalent): 2001:0db8:0000:0000:0000:0000:1622:35bd 2001:0db8:0:0:0:0:1622:35bd 2001:db8::1622:35bd Modifying CAS Basic Configuration Settings If required, you can make modifications to the CAS settings after the initial configuration. There are two ways to access the basic configuration settings for a selected server: Select Settings Central Analysis Server Server Configuration from the Central Analysis Server menu. From the RUM Console top menu, select Devices and Connections Manage Devices, then choose Open configuration from the context menu for your CAS on the Devices screen. This command opens the configuration screen for a given server. To access settings related to users, and sites, select Server Configuration from the menu. 61

62 Chapter 8 CAS Basic Configuration Settings CAUTION If you change the way automatic sites are defined or if you modify the basic user aggregation options from AS to CIDR or vice versa, the traffic monitoring data currently stored in the report server database will no longer be compatible with the new definitions. In such cases, a warning message will be displayed, giving you the option to abandon the configuration changes or to proceed with or without purging the traffic monitoring information in the database. A purge is recommended, because any attempt to access the old traffic monitoring data while the new site or aggregation definitions are in place produces unpredictable results. After the database is cleared, the data gathered by the AMD is re-read by the report server. Enabling User Activity Details and Server Statistics on Demand The CAS can be configured to bypass the database and store the user activity details and server statistics separately on disk. This option can be used in situations where the user details are not required on a regular basis, but are available for occasional inspection. You can also use this feature to reduce the database size, if it is acceptable that the user details are only available through the drill downs. Before You Begin Consider the issues related to database size and complexity. The User Activity Details and Server Statistics on Demand feature is available in PVU and ISP Extended aggregation modes. Be sure that these are appropriate for your monitoring requirements. For more information, see Resolving CAS Database Sizing Issues in the Data Center Real User Monitoring Capacity Planning and Performance Assessment User Guide. Prepare storage, either a directory on a local drive or a network share, for the data files containing the user activity details and server statistics. To enable User Activity Details and Server Statistics on Demand: 1. Open the Central Analysis Server Configuration screen. Do one of the following: Log on to the CAS as a user with administrative rights. From the CAS top menu, choose Settings Central Analysis Server Server Configuration. Log on to the RUM Console and choose Devices and Connections Manage Devices from the top menu. Then choose Open configuration from the context menu for your CAS on the Devices screen. This command opens the configuration screen for a given server. For basic server settings, choose Server Configuration from the menu. 2. Choose the aggregation mode. 62

63 Chapter 8 CAS Basic Configuration Settings Track user IP addresses (FE mode) FE mode records each client IP address separately (it ignores recognized user names and reports users with IP-address resolution). This mode consumes the most resources and significantly increases the database size. It is good for intranet sites with limited numbers of clients, coming from a limited IP address space of the internal network, and sending no information on actual website user names (no login to the website). Remember: All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services. Track users with identifiers, aggregate other users (ISP mode) In this mode, you track users with defined user names and aggregate other users. The ISP modes record each user name separately. User name recognition from HTTP logins must be enabled on the AMD. ISP mode enables you to count user IP addresses that are aggregated as single users. Remember: All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services. also track IP addresses from selected ranges Record each client IP address separately. also count user IP addresses that are aggregated (ISP Extended mode) Select also count user IP addresses that are aggregated to see the number of unique client IP addresses for user aggregates. Use the ISP mode for websites with required login and limited numbers of website users (for example, e-commerce secure sites). Traffic generated by clients that have not been identified (no user name is available) is aggregated into user-defined sites, AS instances, or CIDR blocks. However, if you specify user IP addresses and select also track IP addresses from selected ranges (ISP Extended mode) you will track users that do not have defined user names. For more information, see Limitations of ISP Mode User Aggregation in the Data Center Real User Monitoring Capacity Planning and Performance Assessment User Guide. Aggregate all users but count distinct user identifiers (PVU mode) In this mode, all clients from the same Autonomous System (AS) or CIDR block or subnet are treated as a single user, but the number of unique, non-aggregated users is also provided (for named users in the default configuration). The PVU mode is appropriate for large and very large Internet-facing websites, when knowledge of the number of unique site visitors is needed. The CAS maintains the top N most active AS instances or CIDR blocks as identified client sites (user substitutes), and it rolls up other clients into a single All Other Clients category. Although users are aggregated, the CAS provides an accurate count of actual unique users of the monitored website. Users are counted before aggregation is applied, and the real user count is provided as a metric on CAS reports. 63

64 Chapter 8 CAS Basic Configuration Settings To count users that do not have defined user names, specify user IP addresses and select also count user IP addresses from selected ranges. Unique users are identified on AMDs based on cookies or HTTP headers that identify users. Remember: All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services. For more information, see Limitations of PVU Mode User Aggregation in the Central Analysis Server Online Help. Aggregate all users (PV mode) In this mode all clients from the same AS or from the same CIDR block are counted as a single user. Use the PV mode for large, Internet-facing websites. The CAS maintains the top N most active AS instances or CIDR blocks as identified client sites (user substitutes), and it rolls up other clients into a single All Other Clients category. 3. Enable access to user activity details and server statistics on demand. In the User activity details and server statistics on demand section, select Enable on-demand access to user activity details and server statistics. 4. Set the storage path. Type the path of the location to store the user activity details data: either a local path, for example Z:\UserDetails; or a network share, for example \\server\userdetails. When you choose to save the user activity details on a network share, ensure that the Central Analysis Server service is run under a common domain user account and that a common user has read and write permissions for the share. NOTE Do not use a mapped network drive to store the data files containing the user activity details. a. In Administrative Tools, select Services. b. Right-click the Central Analysis Server service and open the service's Properties window. Click the Log On tab. In the Log on as section, make sure that This account is selected and that the account name and password are correct and have administrative privileges. 64

65 Chapter 8 CAS Basic Configuration Settings Figure 2. Specifying the Domain Account for the Central Analysis Server Service c. Click OK. d. Restart the service. Right-click the service and select Restart. 5. Set a storage quota. Type the number of days to store the data files of user activity details. 6. Update the configuration. Click Update. Every time the settings are updated on this screen, including the first time the application is run, the report server is restarted. When you click Update, the server is restarted and a message appears on the screen. Return to the CAS home page by clicking Continue. The report server restart can take a while, which may prevent you from quickly accessing the home page. What to Do Next After the server is up and running, ensure that the CAS is saving the data in the location you chose for the data file storage. Configuring Other CAS Settings Procedures for setting all other configuration options supported by the Central Analysis Server are described in Data Center Real User Monitoring System Administration Manual. 65

66 Chapter 8 CAS Basic Configuration Settings The sections referring exclusively to the Central Analysis Server are marked (CAS Only) ; other CAS-applicable material can be found in sections referring to both report servers (CAS and ADS). 66

67 CHAPTER 9 Changing Settings Defined During Report Server Installation You can use the Windows Control Panel to change some of the parameters you set during the initial report server configuration. Note that each of the listed tasks must be performed when the report server is turned off. If the report server is running when you start a task, the setup program will warn you that it needs to shut down that service before you can make a configuration change. Click Next to allow the service to stop so the requested configuration screen can be accessed. Migrating User Accounts to CSS After you have installed a Central Security Server (CSS), you can migrate existing user accounts through the CAS Diagnostics Console. 1. Launch the Diagnostics Console. From the CAS top menu, choose Tools Diagnostics Console. 2. Click the MIGRATE USERS TO CSS command and click Execute. The command is displayed in a text box at the top of the screen. Or, you can type the command, MIGRATE USERS TO CSS, directly into the text box. 3. After the successful migration, the following summary appears: Trying to migrate the following users: principalname: wjj, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: wjj, lastname: wjj, address: principalname: pete, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: pete, lastname: pete, address: principalname: adlex, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: adlex, lastname: adlex, address: principalname: karolina, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: karolina, lastname: karolina, address: principalname: jr, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: jr, lastname: jr, address: principalname: jfw_sec_systemuser, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: jfw_sec_systemuser, lastname: jfw_sec_systemuser, address: principalname: jerry, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: jerry, lastname: jerry, address: principalname: ania, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: ania, lastname: ania, address: principalname: malcolm, description:, rolestoassociateto: ROLE_APM_GUEST, firstname: malcolm, lastname: malcolm, address: 67

68 Chapter 9 Changing Settings Defined During Report Server Installation principalname: superuser, description:, rolestoassociateto: ROLE_APM_SYSTEM_ADMIN, firstname: superuser, lastname: superuser, address: Trying to migrate the following groups: principalname: Administrator; description: ; rolestoassociateto: ROLE_APM_SYSTEM_ADMIN; memberusers: superuser principalname: Custom_Report_User; description: ; rolestoassociateto: ROLE_APM_GUEST; memberusers: wjj,pete,adlex,adminuser,karolina,jr,jfw_sec_systemuser,jerry,ania,malcolm Success! All users from this CAS are present in CSS! Success! All groups from this CAS are present in CSS! 4. Restart the CAS. Changing Report Server HTTP and SSL Server Settings After you have installed the report server, you can change the HTTP and SSL settings through the Windows Add or Remove Programs control panel. 1. In Windows, open Start Control Panel. 2. Click Uninstall a program. 3. Select the report server in the list of installed programs and click Uninstall/Change above the list. Alternative access methods: Double-click the product name. Right-click the product name and select Uninstall/Change. The Welcome screen presents you with options for the installed software. 4. Select Change HTTP and SSL server Settings and click Next. 5. If the software must be stopped before you can reconfigure it, you will receive a warning; read it and click Next. It may take a few moments to stop the software. 6. On the Connectivity Options screen which displays if you selected the check box in the previous step, specify the protocol and port through which your report server is accessible. 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. Use HTTPS (HTTP over SSL) 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. If you select the HTTPS option, the SSL Key Generation Data screen is displayed. 68

69 Chapter 9 Changing Settings Defined During Report Server Installation 7. If the SSL Key Generation Data screen is displayed, specify the encryption key information. You can either automatically generate a key and a certificate, or to use a custom encryption key. To generate the key, provide the required data, which varies depending on whether you selected automatic or custom key generation. The SSL Key Generation Data screen enables you to enter the information required to generate a new key. For a custom encryption key, you can provide only the password; the other fields cannot be edited. 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. Address The address. 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. For more information, see Configuring Report Server to Use Private Keys and Certificates [p. 37]. 8. If the SSL Key Security screen is displayed, specify the encryption key security information. Key Password, Confirm Key Password The password associated with the key. Remember the key password Whether to remember the password. TIP For Windows 2008, it is strongly recommended that you select the Remember the key password check box when you install your report server. If you do not do so, you will be asked for that password at every service start. Furthermore, when Interactive Service Detection is disabled you will not see the message at all and will not be able to provide a passphrase for the private SSL key. 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 69

70 Chapter 9 Changing Settings Defined During Report Server Installation 9. Click Change. 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. Changing Report Server Database User Password After you have installed the report server, you can change the database user password through the Windows Add or Remove Programs control panel. To change the database user password: 1. In Windows, open Start Control Panel. 2. Click Uninstall a program. 3. Select the report server in the list of installed programs and click Uninstall/Change above the list. Alternative access methods: Double-click the product name. Right-click the product name and select Uninstall/Change. The Welcome screen presents you with options for the installed software. 4. Select Change database user password and click Next. 5. If software must be stopped before you can reconfigure it, you will receive a warning; read it and click Next. It may take a few moments to stop the software. 6. On the Database User Password Update screen, type the new password twice. 7. Click Change. Changing the RUM Console Connection Information After you have installed the report server, you can change the RUM Console options through the Windows Add or Remove Programs control panel. 1. In Windows, open Start Control Panel. 2. Click Uninstall a program. 3. Select the report server in the list of installed programs and click Uninstall/Change above the list. Alternative access methods: Double-click the product name. Right-click the product name and select Uninstall/Change. The Welcome screen presents you with options for the installed software. 4. Select Change RUM Console options and click Next. 70

71 Chapter 9 Changing Settings Defined During Report Server Installation 5. If software must be stopped before you can reconfigure it, you will receive a warning; read it and click Next. It may take a few moments to stop the software. 6. Change the RUM Console IP address or port number as needed. 7. Click Next, review the summary, and then click Finish to commit your change. Be sure to indicate whether to start CAS after the reconfiguration. 71

72 Chapter 9 Changing Settings Defined During Report Server Installation 72

73 CHAPTER 10 Licensing Data Center Real User Monitoring Components Component licensing is managed by a system called Distributed License Management (DLM). DLM uses the following components to help manage product licensing: License File DLM authorizes you to use products through a license file, which is a text file that contains information about the component options purchased with the product, including information on the product's features and the number and types of licenses that were purchased. Compuware License Service (cpwr.exe) An application (invoked by the DLM application or executed from the command line) that manages and services requests for product licenses. The Compuware License Service application can be installed on Windows and UNIX platforms. In many cases, you should co-locate the Compuware License Service with the server-based components of one of the Compuware products you are installing. For more information on your licensing options, contact your Dynatrace representative. DC RUM Licensing Options DC RUM is licensing is consumption-based: you purchase a license for the type of analysis monitoring and for the size of your own application environment. You do not have to purchase a license for a base package for the management components. The size of the monitored environment is defined as the number of operating system instances (OSIs) for various types of monitoring analysis available, such as Web, Database, and Exchange. It does not matter how many APM components (AMD, CAS, or ADS) are needed to collect, analyze, and report on the applications being monitored. You can install as many CAS, ADS, and AMD instances as you need to support monitoring for the volume and type of data for the licensed monitored OSIs. You do not have to purchase a license for each one. If one machine hosts multiple types of processes to be monitored, each OSI to be monitored is counted for each monitoring type. For example, if a single OSI hosted an MS SQL database and an Oracle database, two monitoring licenses must be purchased, one for MS SQL and one for Oracle. 73

74 Chapter 10 Licensing Data Center Real User Monitoring Components Consumption-based licensing is, in some cases, supplemented by component-based licensing. This mix of licensing models assures better alignment with some of the deployments, where consumption-based licensing might be difficult to implement because of the very dynamic nature of OSIs to be monitored. For details and clarification, contact your Dynatrace representative. 74

75 APPENDIX A Integrating DC RUM with the Dynatrace Enterprise Portal You can extend DC RUM's reporting capabilities by adding the Dynatrace Enterprise Portal to your implementation. The following is an overview of the initial integration process to get quick value from the Portal: The Portal's Application Health reports are designed specifically to support CAS release Complete your DC RUM 12.3 implementation, or upgrade to 12.3, before integrating with the Portal. Once you have DC RUM at release 12.3, you can install the Portal on the same machine you installed CAS. The system requirements for the Portal are similar to CAS if you have sufficient resources on that machine. For more information, see Installing the Dynatrace Enterprise Portal on Windows [p. 77]. The Portal will integrate with the CSS that was implemented with the DC RUM 12.3 release. You do not have to install a second instance of CSS; during the Portal installation, connect to the existing CSS. The user accounts and user groups you have for DC RUM also will have Portal access. After installing the Portal, the first step is to connect the Portal to your CAS. In the Portal, go to the Report Server Manager to configure your connection. If you installed a previous Portal release, upgrade it to release For more information, see Upgrading the Dynatrace Enterprise Portal to 12.3 [p. 82]. The Enterprise Portal User Guide has more information on creating reports and dashboards to further customize your reporting. The guide is available in the product distribution in the CAS_Documentation\ folder, or installed at <Portal_Home>\Program Files\Compuware\Enterprise Portal\Documentation\. Dynatrace Enterprise Portal System Requirements If you are using the Dynatrace Enterprise Portal with DC RUM, it can be installed on the same server as the Central Analysis Server. For Business Service Management, you can install it with 75

76 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal the BSM server. It also can be installed on its own server for scalability purposes. The following are system requirements for the Dynatrace Enterprise Portal. Server Hardware We recommend any physical or vserver supporting 64-bit Microsoft Windows 2012 or 2008 Server (version R2 recommended), with the following hardware specifications (or equivalent) as a minimum requirement. Table 11. Minimum Hardware Requirements Hardware Component CPU Memory Hard drive Specification 2 x Quad Core Intel Xeon 5450, 3.00-GHz processor, 1333-MHz FSB 4 GB RAM Minimum 10 GB Operating Systems Table 12. Supported 64-bit Operating Systems Operating System Windows 2012 Server 64-bit Windows 2008 Server 64-bit Windows 2008 Server R2 64-bit Windows 2003 Server 64-bit Red Hat Enterprise Linux 4.x, 5.x, 6.x 64-bit Comments The Windows 2012 or 2008 R2 Server are recommended platforms for the Dynatrace Enterprise Portal. All editions. Only supported on certified hardware. Database Table 13. Supported Databases Database Supported Versions Comments Microsoft SQL Server 64-bit R Microsoft SQL Server 2012 or 2008 Enterprise Edition are recommended databases. Oracle 64-bit Oracle Grid 64-bit 10g 10g R2 (10.2) 11g R1 (64-bit) 11g R2 (64-bit) 6.2 Custom table spaces are not supported. 76

77 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal If you need to install SQL Server on a clustered index, after installing the Portal, edit the portal-customizations.properties, located at <Portal_Home>\tomcat\webapps\ROOT\WEB-INF\classes\: jdbc.default.url=jdbc:jtds:sqlserver://clustername:1433/enterpriseportal;instance=instancename Client Client machines accessing the Dynatrace Enterprise Portal should have at least 4 GB RAM for optimum performance. Browsers Table 14. Supported Browsers Browser Mozilla Firefox Microsoft Internet Explorer Chrome Version 9.x and higher 8.0, 9.0, 10.0, 11.0 (use compatibility mode with 11.0) 18 and later. Adobe Flash Player is required. Download from Adobe and install the proper version for your operating system and browser type. To integrate with dynatrace, you must install the 32-bit 1.6 Java JRE for drilldowns to the dynatrace webstart interface. Installing the Dynatrace Enterprise Portal on Windows Before You Begin Review the system requirements to ensure you are installing on a supported system with the required resources. For more information, see Dynatrace Enterprise Portal System Requirements [p. 75]. Ensure that a supported database host is accessible. A database will be created during the installation process, or you can create a database in advance if needed (SQL Server only). Ensure that a CSS is installed and running. 1. Double-click the Dynatrace Enterprise Portal installer executable file to start the installation process. 2. On the Introduction page, review the instructions and then click Next. 3. On the License Agreement page, review the terms of the license, indicate whether you accept the terms of the agreement, and click Next to continue or Cancel to quit. If you do not accept the terms of the agreement, you cannot install the software. 4. On the Installation Folder page, review the destination drive and path, make any necessary changes, and then click Next. 77

78 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal All selected components will be installed in this single location. 5. In the Security Configuration screen, identify where an existing Central Security Server (CSS) is installed, or click Install CSS locally. Enter a user name and password for an administrator account. 6. On the Database Configuration page, review the database type (if available), authentication and connection parameters, make any necessary changes, and then click Next. This information will be used to access your database installation for the Dynatrace Enterprise Portal: Host Name Enter the database host machine. Port The default port is entered automatically. Change the port number if you have a conflict. Windows Authentication Select this option to enable a trusted connection for a remote database. Provide the login information for the account under which the service must run for the trusted connection to be allowed. Trusted Account Enter the account name in the form domain\username. Trusted Password Enter the password for the account. If you select this option, the Database Authentication options are not available. Database Authentication Selected by default, use this option if you do not require a Trusted Connection. Enter the login information: User Name Enter the user name for logging in to the specified database. Password Enter the password for the specified user name. 7. In the Database Name screen, the default database names for the Dynatrace Enterprise Portal and Central Security Server (if installed locally) are displayed. If you want databases with these names to be created, leave the default values and click Next. Optional: If you created databases in advance, enter the database name in the fields provided and click Next. 8. On the Pre-Installation Summary page, review the configuration information carefully to ensure that you have selected the options you want to install. If correct, click Install to begin installation. To make changes, click Previous until you get to the relevant page, change your selection, and then click Next until you return to this page. After you click Install, your selections are installed. 78

79 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal NOTE Depending on the options you chose, this may take considerable time. 9. When the installation is finished, the Install Complete page notifies you of the general installation status. Review the installation status message and click Done to exit the installer. What to Do Next If you are using BSM, deploy the BSM web application for the Portal. To open the Portal, go to Start All Programs Compuware Dynatrace Enterprise Portal After you log in, the Portal home page will open. Configure the Portal to integrate with a report server. For Central Analysis Server, go to Administration Manage Report Server to connect. For BSM, go to Administration Control Panel Integrations. Installing the Dynatrace Enterprise Portal on Solaris Before You Begin Review the system requirements to ensure you are installing on a supported system with the required resources. For more information, see Dynatrace Enterprise Portal System Requirements [p. 75]. Ensure that a supported database host is accessible. A database will be created during the installation process, or you can create a database in advance if needed (SQL Server only). Before beginning installation, make sure you have 4 GB of disk space available in a temporary directory for the installation process, and 4 GB for the installed product. Set the environment variable IATEMPDIR for the temporary directory before you copy files to your system. The user installing and running the Portal should be a non-root user and must have sys rights (be a member of the sys group). To ensure that the ulimit value allows file sizes in excess of the extracted size of install.bin, set fsize=-1 (unlimited file size) before beginning the installation. We recommend installing in console mode. 1. Connect to your installation host with the user name that owns the installation. 2. Create a temporary directory. 3. Copy the installation file (located on DVD 3 of the product distribution, in the Enterprise Portal\ folder) to a temporary directory, give the file executable permissions, and execute. chmod +x install.bin For text-only installation, which prompts for input on the console, use the command./install.bin -i console 4. On the License Agreement screen, review the terms of the license, indicate whether you accept the terms of the agreement. 79

80 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal If you do not accept the terms of the agreement, you cannot install the software. 5. On the Installation Folder page, review the destination drive and path, make any necessary changes, and then click Next. All selected components will be installed in this single location. 6. In the Security Configuration screen, identify where an existing Central Security Server (CSS) is installed, or click Install CSS locally. Enter a user name and password for an administrator account. 7. Configure the database: a. Select the type of database to be used. Oracle is selected by default. b. Enter a database host name. c. Enter a port to be used to connect to the database. Defaults to d. Select whether to use Windows authentication. e. Enter a database user name and password. f. Enter a database name. If you created a database in advance, enter that name in the screen provided. 8. In the Pre-Installation Summary screen, review your selections, then press Enter to install the software. Installation may take several minutes. What to Do Next If you are using BSM, deploy the BSM web application for the Portal. To open the Portal, go to Start All Programs Compuware Dynatrace Enterprise Portal After you log in, the Portal home page will open. Configure the Portal to integrate with a report server. For Central Analysis Server, go to Administration Manage Report Server to connect. For BSM, go to Administration Control Panel Integrations. Installing the Dynatrace Enterprise Portal on Linux Red Hat Before You Begin Review the system requirements to ensure you are installing on a supported system with the required resources. For more information, see Dynatrace Enterprise Portal System Requirements [p. 75]. Ensure that a supported database host is accessible. A database will be created during the installation process, or you can create a database in advance if needed (SQL Server only). Ensure that a CSS is installed and running. 1. Create a temporary directory where you have at least 3 GB to 5 GB of space for the installation process and 3.1 GB for the installed Portal. 2. Set the environment variable IATEMPDIR for that temporary directory. 3. Execute the installation file: install.bin. 80

81 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal 4. On the Introduction page, review the instructions and then click Next. 5. On the License Agreement page, review the terms of the license, indicate whether you accept the terms of the agreement, and click Next to continue or Cancel to quit. If you do not accept the terms of the agreement, you cannot install the software. 6. On the Installation Folder page, review the destination drive and path, make any necessary changes, and then click Next. All selected components will be installed in this single location. 7. In the Security Configuration screen, identify where an existing Central Security Server (CSS) is installed, or click Install CSS locally. Enter a user name and password for an administrator account. 8. In the Database Configuration page, select your database type and enter database connection and authentication information. If you select Oracle: a. Enter a host name and port, if different from the default, and the database instance to use. b. Enter a user name and password for a user authorized to log into the database. c. Click Next. d. Accept the Oracle License Agreement and click Next. If you select SQL Server: a. Enter a host name and port, if different from the default. b. Select a database authentication method: Windows Authentication Select this option to enable a trusted connection for a remote database. Provide the logon information for the account under which the service must run for the trusted connection to be allowed. Trusted Account Enter the account name in the form domain\username. Trusted Password Enter the password for the account. If you select this option, the Database Authentication options are not available. Database Authentication Selected by default, use this option if you are not requiring usage of a Trusted Connection. Enter the login information: c. Click Next. User Name Provide the user name for logging on to the specified database. Password Provide the password for the specified user name. 81

82 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal d. In the Database Name screen, the default database names for the Dynatrace Enterprise Portal and Central Security Server (if installed locally) are displayed. If you want databases with these names to be created, leave the default values and click Next. Optional: If you created databases in advance, enter the database names in the fields provided and click Next. 9. When the installation is finished, the Install Complete page notifies you of the general installation status. Review the installation status message and click Done to exit the installer. What to Do Next If you are using BSM, deploy the BSM web application for the Portal. To open the Portal, go to Start All Programs Compuware Dynatrace Enterprise Portal After you log in, the Portal home page will open. Configure the Portal to integrate with a report server. For Central Analysis Server, go to Administration Manage Report Server to connect. For BSM, go to Administration Control Panel Integrations. Upgrading the Dynatrace Enterprise Portal to 12.3 If you are using Dynatrace Enterprise Portal 12.x, upgrade to release 12.3: 1. Stop the Dynatrace Enterprise Portal service. 2. Install a Portal 12.3 over the existing release. For Windows, the installer is available on DVD 1 at Dynatrace Enterprise Portal\Windows\install.exe. The Linux and Unix installers are on DVD 2 and 3, respectively. After the installation starts, you will see a message that an existing release was found on the machine. Click OK to proceed with the installation. Verify Successful Upgrade Check to see if your custom dashboards and reports are available in the upgraded release. 3. Go to Start All Programs Compuware Dynatrace Enterprise Portal Log in with an administrator's account. 5. If you are using the Portal with DC RUM: Make sure the correct CAS is integrated with the Portal. Only a master CAS should be used. Confirm that the number of applications shown under the Application Health Status report is the same as the number of applications displayed on the CAS report. If you are using the Portal with BSM, confirm that your dashboards exist. Go to Dashboards Manage Pages and see if your dashboards are listed. They will not be operational until you deploy the correct BSM web application. 82

83 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal What to Do Next If you are using BSM, deploy the BSM web application for the Portal. 83

84 Appendix A Integrating DC RUM with the Dynatrace Enterprise Portal 84

85 APPENDIX B Report Server Installation and Upgrade Troubleshooting Issues with installation and upgrade include database connectivity issues, system services startup, and other areas. After CAS installation or upgrade, access to DMI reports is lost. This software requires integration with CSS. Be sure that your CSS connection is running and reliable throughout report server installation or upgrade. Loss of CSS access during the procedure may cause loss of system integrity. Indicators of this situation are The message WARNING: database may not be installed successfully. in the post-installation summary. The log entry java.lang.nullpointerexception at com.compuware. frameworks.security.client.management.impl.managementserviceclient. getallsecurityusers in install.log A symptom of this situation may be loss of DMI report access. To restore DMI report access: 1. Start the CAS with a reliable CSS connection. 2. Log in to the CAS as an administrator. 3. Select Tools Diagnostics Console. 4. In the Command box, type or paste REPORT REREAD and click Execute. 5. Wait for the command to finish execution. This may take some minutes. A message of the form T DMI :09: Loading predefined DMI reports finished. will indicate that the process is complete. If the source of the problem was temporary loss of your CSS connection during report server installation, this command should restore your DMI report access. 85

86 Appendix B Report Server Installation and Upgrade Troubleshooting After the installation, I do not see Advanced Diagnostics Server or Central Analysis Server in the services list. What do I do? If you installed the report server and the SQL Server on a single machine, the service name for SQL Server must be the default name. If the service name used to start SQL Server is not MSSQLSERVER, the installer will not be able to create a service for the report server. Although all necessary files will be successfully installed, you will not be able to start the servers from the services list. Check the log files to see if this is the issue. In default installations, the log files are: <install_dir>\log\install\wdginstallntservice.log <install_dir>\log\install\wdginstallservices.log Open these files and search for the following strings: SQL service MSSQLServer is not found (The specified service does not exist as an installed service. (0x424)) in wdginstallservices.log SQL service (MSSQLServer) is not found (The specified service does not exist as an installed service. (424)) in wdginstallntservice.log. To work around this issue: 1. In Windows, go to Administrative Tools Services. 2. Double-click SQL Server (Instance_Name) (the main SQL Server service) to see the properties. 3. Check the Service Name (not Display Name) for SQL Server on General tab. 4. Open the command prompt and issue the following command: "C:\Program Files\Common Files\Compuware\Watchdog\windowsjre_x64.exe" -install "Vantage Analysis Server" "Vantage Analysis Server" Service name of the SQL Server checked in the step 3 On 32-bit systems, use the "C:\Program Files\Common Files\Compuware\Watchdog\windowsjre.exe" command. 5. Reboot the machine where the report server is installed to apply the changes. 6. After the machine restarts, check whether the Vantage Analysis Server service has been added and starts correctly. What do I do when the services won't start? There could be a number of reasons why the services might not start. The following procedure will help you to determine the most frequent causes of this problem. 1. Inspect the server.log file. The file server.log can be opened by selecting Start Programs Compuware Central Analysis Server Documentation Server log. 2. TCP port availability check. Search server.log for the message Address already in use: JVM_Bind:port_number. If you find a similar message, it means the report server 86

87 Appendix B Report Server Installation and Upgrade Troubleshooting cannot start because the TCP port reserved for the built-in web server is already in use by another software service process. T ADM :45: AAS Platform (build 164) T ADM :45: Vantage Analysis Server (build 152) T ADM :45: RTM Base System (build 156) T ADM :45: RTM GATE (build 149) T ADM :45: ND Core Base System (build 165) T ADM :45: Vantage Analysis Server Service Pack (build 9) java.net.bindexception: Address already in use: JVM_Bind:80 at org.apache.tomcat.util.net.pooltcpendpoint.initendpoint(pooltcpendpoint.java:264) at org.apache.coyote.http11.http11protocol.init(http11protocol.java:137) at org.apache.coyote.tomcat5.coyoteconnector.initialize(coyoteconnector.java:1429) at org.apache.catalina.startup.embedded.start(embedded.java:851) at adlex.delta.tomcat.embedded.tomcatbootstrap.startserver(tomcatbootstrap.java:176) at adlex.delta.server.admin.main(admin.java:243) LifecycleException: Protocol handler initialization failed: java.net.bindexception: Address already in use: JVM_Bind:80 at org.apache.coyote.tomcat5.coyoteconnector.initialize(coyoteconnector.java:1431) at org.apache.catalina.startup.embedded.start(embedded.java:851) at adlex.delta.tomcat.embedded.tomcatbootstrap.startserver(tomcatbootstrap.java:176) at adlex.delta.server.admin.main(admin.java:243) HTTP server not started. Determine the service and terminate it. Use the netstat to list all of the TCP and UDP ports that are currently in use: netstat /a /n This command lists all the active ports and their status, for example: Active Connections Proto Local Address Foreign Address State TCP : :0 LISTENING TCP : :0 LISTENING TCP : :0 LISTENING TCP : :0 LISTENING TCP : :0 LISTENING TCP : :0 LISTENING TCP : :0 LISTENING TCP : :0 LISTENING TCP : :7579 ESTABLISHED TCP : :7578 ESTABLISHED TCP : :0 LISTENING UDP :445 *:* UDP :500 *:* UDP :1025 *:* UDP :1026 *:* UDP :1434 *:* UDP :1464 *:* UDP :3385 *:* UDP :3456 *:* UDP :4500 *:* 3. Database connectivity check. 87

88 Appendix B Report Server Installation and Upgrade Troubleshooting Search server.log for the message No connection to data base. If this message appears in the log, it means the report server could not start due to database connectivity problems. T ADM :19: AAS Platform (build 164) T ADM :19: Vantage Analysis Server (build 152) T ADM :19: RTM Base System (build 156) T ADM :19: RTM GATE (build 149) T ADM :19: ND Core Base System (build 165) T ADM :19: Vantage Analysis Server Service Pack (build 9) T RPT :19: watchdog file created: c:\prj\rtm50\config\nds.sem - Interval 15 min T DB :19: JDBC_DRIVER = net.sourceforge.jtds.jdbc.driver T DB :19: JDBC_URL = jdbc:jtds:sqlserver://localhost:1433/delta;tds=8.0; T DB :19: JDBC_USER = delta E DB :19: Cannot get connection:network error IOException: Connection refused: connect E DB :19: Cannot get connection:network error IOException: Connection refused: connect E DB :21: Cannot get connection:network error IOException: Connection refused: connect T ADM :21: No connection to data base. The error messages prior to the last one indicate the possible reason of the problem. The following table lists the most frequent causes of database connectivity problems. Table 15. Database Connectivity Troubleshooting Actions Message Potential reason Troubleshooting action Cannot get connection:network error IOException: Connection refused: connect Microsoft SQL Server is down. Microsoft SQL Server is not configured to listen on the TCP port though it was listening during the product installation. Start Microsoft SQL Server. Reconfigure Microsoft SQL Server to enable TCP connectivity. Microsoft SQL Server is now Edit the configured to listen on a config\repository.properties different TCP port than it was file to update the TCP/IP during the installation process. settings. Edit the line starting with JDBC_URL=... and enter If a remote Microsoft SQL a correct IP address of the Server was used, it has database server and the TCP changed its IP address or the port on which it listens to configured IP address has been queries. used by a different computer. Cannot get connection:cannot open database requested in login 'vas'. Login fails. Microsoft SQL Server database does not exist. You have to reinstall the product to recreate the database with correct user rights. If you have a database backup copy, you can restore it. 88

89 Appendix B Report Server Installation and Upgrade Troubleshooting Table 15. Database Connectivity Troubleshooting Actions (continued) Message Potential reason Troubleshooting action Cannot get connection:login failed for user 'delta'. The report server cannot authenticate with Microsoft SQL Server. The password of the user delta has been changed. Reset it to the original value. How do I determine the port number for a named instance of the SQL Server? If enabled, the default instance of the SQL Server Database Engine listens on TCP port Named instances of the database engine are configured for dynamic ports. This means they select an available port when the SQL Server service is started. You can determine your SQL Server named instance in several ways; using SQL Server Configuration Manager is one of the simplest ways. In general, you should refer to your SQL Server named instances by name so that you always address the valid instance (the port number may change but the instance name does not). If, during installation of the report server, you are unable to use the instance name and are forced to give a port number, you can check its value: 1. Log in to the system either remotely (via Remote Desktop, for example) or locally. 2. In Windows, go to Programs Microsoft SQL Server <server_version> Configuration Tools and choose SQL Server Configuration Manager. 3. Select Protocols for <instance_name> and then double-click TCP/IP to inspect the instance TCP/IP settings. 4. In the TCP/IP Properties dialog box, on the IP Addresses tab, determine the currently assigned port number. If the TCP Dynamic Ports dialog box contains 0, this indicates that the Database Engine is listening on dynamic ports. The IPAll dialog contains the port number used by the SQL Server named instance you selected. 89

90 Appendix B Report Server Installation and Upgrade Troubleshooting Figure 3. TCP/IP Properties for the SQL Server named instance 5. Click Cancel to close TCP/IP Properties. 6. You can validate port number discovery using the netstat program. Connect to the Database Engine with SQL Server Management Studio from a remote machine. On the machine hosting SQL Server, issue the netstat command and inspect the Local Address and Foreign Address columns. Find a matching pair (or pairs) of addresses that represents your remote connection to the SQL Server. The Local Address column contains the port number associated with the local machine (separated by a colon from the IP address). 90

91 APPENDIX C Protocols Supported by CAS Table 16. Protocols Supported by CAS Analyzer Protocol Version Limitations Example application Cerner over TCP Cerner Cerner 2005, Cerner over TCP 2007 Cerner Millennium Cerner over MQ Cerner over MQ Cerner 2007 MQ: WebSphere 6.0 MQ: WebSphere V7.0 MQ 6.0 Limitations: Traffic for channels with encryption is not monitored. Traffic for channels with header compression is not monitored. MQGET message segmentation is not supported. Additional MQ v7.0 Limitations: For the new v7.0 GET-GET_REPLY operations, only TSH and Message Descriptor headers are processed. No correlation is extracted from the new v7.0 MQ_GET segments. Bytes 8-15 of the TSHM header are not processed. Cerner Millennium Corba Epic Corba Epic over TCP Summer 2010 EpicCare EMR DNS DNS RFC 1035 UDP-based DNS only. 91

92 Appendix C Protocols Supported by CAS Table 16. Protocols Supported by CAS (continued) Analyzer Protocol Version Limitations Example application No support for multi-query requests. DRDA (DB2) DRDA (DB2) DRDA version 2 IBM DB2 Universal Database 8.1 Exchange/RPC over HTTP Exchange/RPC over HTTPS Exchange MS Exchange 2003, 2007, 2010 Encryption at application level is reported as Encrypted transaction. Microsoft Exchange Server 2003 Generic TCP RFC 793 Generic (with transactions) TCP RFC 793 HTTP HTTP 1.1, 1.0 (RFC 2616) Advanced analysis for GET/POST methods by default. For all other methods, such as PUT, every hit is reported separately. These methods require manual configuration change to enable advanced analysis No pipelining. IBM MQ IBM MQ over SSL IBM MQ WebSphere 6.0 MQ 6.0 Limitations: WebSphere WebSphere MQ V7.0 Traffic for channels with encryption is not monitored. Traffic for channels with header compression is not monitored. Traffic between MQ servers, (Manager to Manager) and between MQ clients and MQ MQGET message segmentation is not supported. Additional MQ v7.0 Limitations: servers can be analyzed. Dynamic queue names are recognized. For the new v7.0 GET-GET_REPLY operations, Persistent TCP sessions are supported. only TSH and Message Descriptor headers are processed. No correlation is extracted from the new v7.0 MQ_GET segments. Bytes 8-15 of the TSHM header are not processed. 92

93 Appendix C Protocols Supported by CAS Table 16. Protocols Supported by CAS (continued) Analyzer Protocol Version Limitations Example application ICA (Citrix) Citrix 4 and 4.5 Username extraction and counting is limited to ICA traffic with Basic or None encryption levels. Citrix Metaframe Presentation Server When enhanced encryption is enabled, traffic will be considered an encrypted operation. ICA (Citrix) Citrix 5.0, 6.0 and 6.5 Username extraction and counting is limited to ICA traffic with Basic or None encryption levels. Citrix XenApp When enhanced encryption is enabled, traffic will be considered an encrypted operation. ICMP ICMP RFC 792 Informix Informix IDS 7.31, IDS 9.40 Informix Dynamic Server IP IP RFC 791 Jolt (Tuxedo) Jolt 8.1 BEA Tuxedo Kerberos SMB Microsoft Kerberos 5 All Microsoft Windows systems that use the SMB 1.0 protocol. (Tested on Windows 2000 and Windows XP.) LDAP LDAPS LDAP RFC 4511 Applications using LDAP All Java applications services in which Kerberos using LDAP services encryption is used are not where plain text supported. authentication is used. MySQL MySQL 4.x and 5.x NetFlow NetFlow version 5, version 9, IPFIX Supported excluding flexible NetFlow: You should configure NetFlow to export only a subset of fields and only for ingress traffic. Cisco router Oracle Net8 9i, 10g R1, 10g R2, 11g No support for TDE R1, 11g R2, and 12c R1 encryption. If TDE encryption is enabled, the Oracle 9i, 10g, 11g 93

94 Appendix C Protocols Supported by CAS Table 16. Protocols Supported by CAS (continued) Analyzer Protocol Version Limitations Example application Oracle analyzer stops reporting performance data. Oracle T3/TS3 is not supported. Oracle Forms over HTTP Oracle Forms over TCP Oracle Forms 6i, 9i, 10.1, 11g Oracle Forms 6i Oracle Application Server 9i, 10i, 10g R2, 11g Oracle Forms over SSL SSL support. Oracle Forms over HTTPS RMI BEA T3 JBoss RMI SUN RMI SAP GUI SAP GUI protocol (DIAG) 6.40, 7.10 SAP GUI for Java 7.10rev8, SAP GUI for Windows 7.10, SAP GUI for Windows 7.30, SAP GUI Console, Net weaver Business Client 4.0. SAP GUI over HTTP HTTP 1.1, 1.0 (RFC 2616) Support for SAP 7.01 SP3 and SAP GUI for HTML SAP GUI over HTTPS HTTPS HTTP 1.1 encapsulated Support for SAP 7.01 SP3 in SSL, SSL 3.0, and TLS1.0 (RFC 2246), TLS1.1 (RFC 4346) and TLS1.2 (RFC 5246) SAP GUI for HTML SAP RFC SAP RFC SAP PI, SAP BW, Excel plugin for SAP Siebel HTTP HTTP 1.1, 1.0 (RFC 2616) A special parameter configuration is Siebel CRM SSL support. HTTP 1.1 encapsulated recommended for analyzing in SSL, SSL 3.0, Siebel applications. For TLS1.0 (RFC 2246), more information, see TLS1.1 (RFC 4346) and Global Settings for TLS1.2 (RFC 5246) Recognition and Parsing of URLs in the Data Center Real User Monitoring Web 94

95 Appendix C Protocols Supported by CAS Table 16. Protocols Supported by CAS (continued) Analyzer Protocol Version Limitations Example application Application Monitoring User Guide. SMB SMB SMB 1.0, 2.0 All Microsoft Windows systems that use the SMB protocol. SMTP SMTP, ESMTP RFC 821, RFC1891 Supported commands: HELO/EHLO, MAIL FROM, RCPT TO, DATA, QUIT, RSET, VRFY, HELP, EXPN, NOOP (no support for SEND, SOML, SAML, TURN Multi-part attachments are always saved in one piece (no segmentation is preserved). MS Exchange Server native RPC protocol and POP3 ( download) are not supported. SOAP over HTTP SOAP over HTTPS SOAP SOAP 1.1 and 1.2 Support for Remote Procedures Calls only. Any business application that uses SOAP for data exchange over the network. SSL support. SSL SSL Decrypted HTTPS HTTP 1.1 encapsulated Advanced analysis for in SSL GET/POST methods by SSL 3.0, default. TLS1.0 (RFC 2246) For all other methods, such as PUT, every hit is reported TLS1.1 (RFC 4346) separately. These methods TLS1.2 (RFC 5246) require manual configuration change to enable advanced analysis No pipelining. 56-bit DES is not supported. Only RSA Key Exchange Algorithm is supported. Only a 1024-bit SSL key is supported on CryptoSwift SSL cards. SSL support. 95

96 Appendix C Protocols Supported by CAS Table 16. Protocols Supported by CAS (continued) Analyzer Protocol Version Limitations Example application Open SSL supports 1024-bit, 2048-bit, 4096-bit and 8192-bit keys. ncipher cards support 1024-bit, 2048-bit, 4096-bit and 8192-bit keys. Cavium NITROX XL FIPS cards support 1024-bit and 2048-bit keys. TCP TCP RFC 793 TDS TDS 5.0, 7.0, 8.0 MS SQL Server 7.0, 2000, 2005, 2008, 2008R2, and Sybase 10.0, Sybase Adaptive Server Enterprise (ASE) 15 UDP UDP RFC 768 VoIP RTP, RTCP, SIP, H323 G.726, GSM, G , Conference calls, secure G.729, G.711 (PCMA), protocols, and forked calls G.711(PCMU), G (multiple phones ringing at (ACELP), G the same time) are not (MP-MLQ), LPS supported. The AMD must see both signaling and media on the same AMD. XML XML over SSL XML W3C recommendation 1.0 and 1.1 Encapsulated in TCP, in HTTP, and in HTTPS. SSL support. XML over HTTP XML over HTTPS XML over MQ XML over MQ over SSL XML MQ XML: W3C recommendation 1.0 and 1.1 MQ: WebSphere 6.0 MQ: WebSphere V7.0 XML encapsulated in MQ. MQ 6.0 Limitations: Traffic for channels with encryption is not monitored. Traffic for channels with header compression is not monitored. MQGET message segmentation is not supported. 96

97 Appendix C Protocols Supported by CAS Table 16. Protocols Supported by CAS (continued) Analyzer Protocol Version Limitations Example application Additional MQ v7.0 Limitations: For the new v7.0 GET-GET_REPLY operations, only TSH and Message Descriptor headers are processed. No correlation is extracted from the new v7.0 MQ_GET segments. Bytes 8-15 of the TSHM header are not processed. 97

98 Appendix C Protocols Supported by CAS 98

99 APPENDIX D SQL Operations Performed During Report Server Installation or Upgrade The database installation process has two stages. First, using the SQL Server administrator account, the report server database, database user, and database user rights are set up. Next, using the SQL user account created earlier, the database schema and all necessary tables and indexes are set up and organized. When you are asked for the sa password, this is because the installer needs it to: Obtain SQL Server information Set up databases Set up a database user Grant permissions to the database user Set memory limit During report server installation, none of the existing databases or users is modified. The installer modifies only the Data Center Real User Monitoring database you explicitly specify in the installer dialog. After the report server is installed, you can inspect the SQL scripts that were performed as the sa user. The values you entered in the installer dialogs will be stored in the scripts in the report server's config directory, by default located in the <install_dir>\config\sql\ms\setup path. Example 1. SQL Scripts Stored in the Report Server File System After Installation C20Database.sql C30DomainLogin.sql C30Login.sql C50DomainUserRights.sql C50UserRights.sql SetMaxMemory-curr.sql SetMaxMemory-max.sql SetMaxMemory-recc.sql SetMaxMemory.template 99

100 Appendix D SQL Operations Performed During Report Server Installation or Upgrade After installation, the database owner password is stored by the report server so that important maintenance tasks can be performed. For more information, see Considerations for Report Server Database Migration in the Data Center Real User Monitoring Administration Guide. Non sa-related Part of the Installation After the SQL Server environment is ready, the sa user account is logged out and the user account defined during the installation is logged in to finish the database setup. A log for this part of the database installation is stored in: <install_dir>\log\install\maintaindbtables_stdout.log Database Creation Network Delta, the main report server database, stores all of the data presented by the report server. The script, C20Database.sql, is executed to create the database on SQL Server. The values of the variables set in this script are gathered by the report server installer in the Database Connection Properties, Database Size, and Database Server Memory Setting dialog boxes. The database parameter settings configured by the installer program are: Automatic shrinking is turned off Automatic statistics creation is turned on Checking for out-of-date statistics is turned on Simple Recovery model is turned on SQL_Latin1_General_CP1_CI_AS is used as the SQL collation The variables used in the script are the following: ND_DB_DATABASE The name of the database. Enter the name in the installer in the Database Connection Properties dialog box, in the Name of database box. ND_DB_DATABASE_dat The name of the database file on the SQL Server file system. ND_DB_DEVICE Where the database files are stored. Enter the value as the Database device location. ND_DB_SIZE The size of the database. The recommended size is calculated by the installer, but you can override the calculated value in the Database Size dialog box. ND_DB_DATABASE_log The name of the database log file on the SQL Server file system. The name is the value of the ND_DB_DATABASE variable with _log appended to it. ND_LOG_DEVICE The physical location of the database log file. The location is the same as for the database file. ND_LOG_SIZE The database log size is calculated automatically based on the size of the database. This is typically about 0.25% of the database size. 100

101 Appendix D SQL Operations Performed During Report Server Installation or Upgrade Example 2. C20Database.sql Script if not exists (select * from master.dbo.sysdatabases where name = '$ND_DB_DATABASE') begin CREATE DATABASE $ND_DB_DATABASE ON PRIMARY ( NAME = '$ND_DB_DATABASE_dat', FILENAME = '$ND_DB_DEVICE', SIZE = $ND_DB_SIZE, FILEGROWTH = 10% ) LOG ON ( NAME = '$ND_DB_DATABASE_log', FILENAME = '$ND_LOG_DEVICE', SIZE = $ND_LOG_SIZE ) end GO /* Set database options */ alter database $ND_DB_DATABASE set AUTO_SHRINK OFF GO alter database $ND_DB_DATABASE set AUTO_CREATE_STATISTICS ON GO alter database $ND_DB_DATABASE set AUTO_UPDATE_STATISTICS ON GO alter database $ND_DB_DATABASE set RECOVERY SIMPLE GO alter database $ND_DB_DATABASE COLLATE SQL_Latin1_General_CP1_CI_AS GO CHECKPOINT GO reconfigure with override GO The database remains empty at this point. Tables and other structures are created later, after the sa user logs out and the installer logs in as the default database user to finish setting up the database. Creating a Database User You can select a Windows domain account or a regular database account to create a new database user. For more information, see Running a CAS Setup [p. 31]. Depending on your choice, the installer will execute either C30DomainLogin.sql or C30Login.sql. For more information, see Create a Windows Domain User as a Database User (C30DomainLogin.sql) [p. 101] and Create a Database User (C30Login.sql) [p. 102]. Create a Windows Domain User as a Database User (C30DomainLogin.sql) If you choose a Windows domain user (when you enter a string of the form domain\user in the Name of database user box) as the default report server database user, the installer automatically recognizes this and tries to set up the provided user as the default database user. The domain\user is split into variables ND_DB_DOMAIN and ND_DB_LOGIN. They are used later by a script that sets the domain user rights for the database. For more information, see Database User Rights [p. 102]. 101

102 Appendix D SQL Operations Performed During Report Server Installation or Upgrade Example 3. C30DomainLogin.sql Script USE master GO if not exists (select * from syslogins where name = '$ND_DB_DOMAIN\$ND_DB_LOGIN' ) begin CREATE LOGIN [$ND_DB_DOMAIN\$ND_DB_LOGIN] FROM WINDOWS WITH DEFAULT_DATABASE=[$ND_DB_DATABASE] end GO ALTER LOGIN [$ND_DB_DOMAIN\$ND_DB_LOGIN] WITH DEFAULT_DATABASE = $ND_DB_DATABASE GO Create a Database User (C30Login.sql) The default database user name is entered in the Name of database user box and the password for that user is determined in the Database user password box. The value of ND_DB_LOGIN is substituted by the user name you provided. The user's default database (ND_DB_DATABASE) becomes the database you provided in the installer's Name of database box. Example 4. C30Login.sql Script USE master GO if not exists (select * from syslogins where name = '$ND_DB_LOGIN' ) begin CREATE LOGIN $ND_DB_LOGIN WITH PASSWORD = 'tmppswdch@ngedinnextscript123', DEFAULT_DATABASE = $ND_DB_DATABASE, CHECK_POLICY = OFF end GO ALTER LOGIN $ND_DB_LOGIN WITH DEFAULT_DATABASE = $ND_DB_DATABASE GO The password is set by a procedure that does not log the password or store it in a file on a hard disk. Database User Rights A database user with certain rights is required during the report server installation and operation. These rights can be assigned by executing one of the following SQL scripts. To this end, a database schema is created and then a set of rights is granted to the database user. These rights include: Backing up the database Backing up the database log Connecting to the database Verifying the database state Creating tables, procedures, and functions Executing the select command on tables in which information on tables and indexes is kept Checking whether the database needs defragmenting 102

103 Appendix D SQL Operations Performed During Report Server Installation or Upgrade The database user must be able to verify that the database structure is consistent and that the required tables, columns, and indexes exist. The default database user is also assigned the role of bulkadmin so that records can be inserted into the database in the fastest possible way. Set Domain User Rights The C50DomainUserRights.sql script is executed when the database user was set to be a Windows domain user. Example 5. C50DomainUserRights.sql Script USE $ND_DB_DATABASE GO if db_name()!= '$ND_DB_DATABASE' begin raiserror('error: cannot create login, database ''$ND_DB_DATABASE'' does not exist.',22,127) with log return end GO if not exists (select * from sysusers where name = '$ND_DB_DOMAIN\$ND_DB_LOGIN' and uid < 16382) begin create user [$ND_DB_DOMAIN\$ND_DB_LOGIN] for login [$ND_DB_DOMAIN\$ND_DB_LOGIN] with default_schema = [$ND_DB_DOMAIN\$ND_DB_LOGIN] exec('create schema [$ND_DB_DOMAIN\$ND_DB_LOGIN] authorization [$ND_DB_DOMAIN\$ND_DB_LOGIN]') end GO grant backup database to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant backup log to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant connect to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant create table to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant view database state to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant create procedure to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant create function to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant create view to [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sys.tables TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sys.objects TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sysobjects TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sys.indexes TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sysindexes TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sys.columns TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON syscolumns TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sys.all_columns TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] grant SELECT ON sys.database_principals TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] RECONFIGURE WITH OVERRIDE GO USE master -- Ensure that the report user is allowed to invoke DBCC command. GRANT VIEW SERVER STATE TO [$ND_DB_DOMAIN\$ND_DB_LOGIN] EXEC sp_addsrvrolemember '$ND_DB_DOMAIN\$ND_DB_LOGIN', 'bulkadmin' RECONFIGURE WITH OVERRIDE Set Database User Rights The C50UserRights.sql script is executed when the default database user is set up on the database server directly. 103

104 Appendix D SQL Operations Performed During Report Server Installation or Upgrade Example 6. C50UserRights.sql Script USE $ND_DB_DATABASE GO if db_name()!= '$ND_DB_DATABASE' begin raiserror('error: cannot create login, database ''$ND_DB_DATABASE'' does not exist.',22,127) with log return end GO if not exists (select * from sysusers where name = '$ND_DB_LOGIN' and uid < 16382) begin create user $ND_DB_LOGIN for login $ND_DB_LOGIN with default_schema = $ND_DB_LOGIN exec('create schema $ND_DB_LOGIN authorization $ND_DB_LOGIN') end GO grant backup database to $ND_DB_LOGIN grant backup log to $ND_DB_LOGIN grant connect to $ND_DB_LOGIN grant create table to $ND_DB_LOGIN grant view database state to $ND_DB_LOGIN grant create procedure to $ND_DB_LOGIN grant create function to $ND_DB_LOGIN grant create view to $ND_DB_LOGIN grant SELECT ON sys.tables TO $ND_DB_LOGIN grant SELECT ON sys.objects TO $ND_DB_LOGIN grant SELECT ON sysobjects TO $ND_DB_LOGIN grant SELECT ON sys.indexes TO $ND_DB_LOGIN grant SELECT ON sysindexes TO $ND_DB_LOGIN grant SELECT ON sys.columns TO $ND_DB_LOGIN grant SELECT ON syscolumns TO $ND_DB_LOGIN grant SELECT ON sys.all_columns TO $ND_DB_LOGIN grant SELECT ON sys.database_principals TO $ND_DB_LOGIN RECONFIGURE WITH OVERRIDE GO USE master -- Ensure that the report user is allowed to invoke DBCC command. GRANT VIEW SERVER STATE TO $ND_DB_LOGIN EXEC sp_addsrvrolemember '$ND_DB_LOGIN', 'bulkadmin' RECONFIGURE WITH OVERRIDE Set Memory Size You can define the memory size used by SQL Server during installation. At installation time, the system checks the available amount of memory and recommends a value, and you can use the recommended setting or enter different one. For more information, see Running a CAS Setup [p. 31]. The current setting on SQL Server is saved in the file SetMaxMemory-curr.sql, the memory size is increased to the maximum so that the installer (which is run by the script in file SetMaxMemory-max.sql) has the best conditions to proceed, and then either the memory size is restored (with the use of the file SetMaxMemory-curr.sql) or set to a recommended value with the help of the file SetMaxMemory-recc.sql. 104

105 Appendix D SQL Operations Performed During Report Server Installation or Upgrade Example 7. SetMaxMemory.template Script Template This template is used by the installer to create the SetMaxMemory-curr.sql, SetMaxMemory-max.sql and SetMaxMemory-curr.sql scripts. USE master EXEC sp_configure 'show advanced option', '1' RECONFIGURE WITH OVERRIDE GO EXEC sp_configure 'awe enabled', '1' RECONFIGURE WITH OVERRIDE GO EXEC sp_configure 'min server memory', '0' RECONFIGURE WITH OVERRIDE GO EXEC sp_configure 'max server memory', '$SQL_MAX_MEMORY' RECONFIGURE WITH OVERRIDE GO EXEC sp_configure 'min server memory', '$SQL_MIN_MEMORY' RECONFIGURE WITH OVERRIDE GO 105

106 Appendix D SQL Operations Performed During Report Server Installation or Upgrade 106

107 APPENDIX E Creating CAS Database and Database User with Microsoft SQL Server Management Studio Before installing the report server, your SQL Server administrator can use Microsoft SQL Server Management Studio to create and configure a database and database user for the report server. This may be a security requirement in your computing environment. 1. Create new database using Microsoft SQL Server Management Studio. 2. Set database options. Use the following statements (where $ND_DB_DATABASE is the database name): alter database $ND_DB_DATABASE set AUTO_SHRINK OFF GO alter database $ND_DB_DATABASE set AUTO_CREATE_STATISTICS ON GO alter database $ND_DB_DATABASE set AUTO_UPDATE_STATISTICS ON GO alter database $ND_DB_DATABASE set RECOVERY SIMPLE GO alter database $ND_DB_DATABASE COLLATE SQL_Latin1_General_CP1_CI_AS GO CHECKPOINT GO reconfigure with override GO 3. Create a database user. Use the following statements (where $ND_DB_DATABASE is database name, $ND_DB_LOGIN is the user login, and $ND_DB_PASSWORD is the user password): USE master GO if not exists (select * from syslogins where name = '$ND_DB_LOGIN' ) begin CREATE LOGIN [$ND_DB_LOGIN] WITH PASSWORD = '$ND_DB_PASSWORD', DEFAULT_DATABASE = $ND_DB_DATABASE, CHECK_POLICY = OFF end GO ALTER LOGIN [$ND_DB_LOGIN] WITH DEFAULT_DATABASE = $ND_DB_DATABASE GO 4. Grant rights to the database user. 107

108 Appendix E Creating CAS Database and Database User with Microsoft SQL Server Management Studio Use the following statements (where $ND_DB_DATABASE is the database name and $ND_DB_LOGIN is the user login): USE $ND_DB_DATABASE GO if db_name()!= '$ND_DB_DATABASE' begin raiserror('error: cannot create login, database ''$ND_DB_DATABASE'' does not exist.',22,127) with log return end GO if not exists (select * from sysusers where name = '$ND_DB_LOGIN' and uid < 16382) begin create user [$ND_DB_LOGIN] for login [$ND_DB_LOGIN] with default_schema = [$ND_DB_LOGIN] exec('create schema [$ND_DB_LOGIN] authorization [$ND_DB_LOGIN]') end GO grant backup database to [$ND_DB_LOGIN] grant backup log to [$ND_DB_LOGIN] grant connect to [$ND_DB_LOGIN] grant create table to [$ND_DB_LOGIN] grant view database state to [$ND_DB_LOGIN] grant create procedure to [$ND_DB_LOGIN] grant create function to [$ND_DB_LOGIN] grant create view to [$ND_DB_LOGIN] grant SELECT ON sys.tables TO [$ND_DB_LOGIN] grant SELECT ON sys.objects TO [$ND_DB_LOGIN] grant SELECT ON sysobjects TO [$ND_DB_LOGIN] grant SELECT ON sys.indexes TO [$ND_DB_LOGIN] grant SELECT ON sysindexes TO [$ND_DB_LOGIN] grant SELECT ON sys.columns TO [$ND_DB_LOGIN] grant SELECT ON syscolumns TO [$ND_DB_LOGIN] grant SELECT ON sys.all_columns TO [$ND_DB_LOGIN] grant SELECT ON sys.database_principals TO [$ND_DB_LOGIN] RECONFIGURE WITH OVERRIDE GO USE master -- Ensure that the report user is allowed to invoke DBCC command. GRANT VIEW SERVER STATE TO [$ND_DB_LOGIN] EXEC sp_addsrvrolemember '$ND_DB_LOGIN', 'bulkadmin' RECONFIGURE WITH OVERRIDE What to Do Next After you create the database, be sure to periodically (perhaps daily) maintain it by shrinking the database and log file using SHRINKFILE and SHRINKDATABASE. Refer to the SQL Server documentation for information. 108

109 APPENDIX F Backup and Recovery Procedures There are a number of comprehensive backup and recovery procedures available. These include the backup and recovery procedures for the report server, the RUM Console Server database, and the MS SQL Server 2005 and 2008 databases. There is also a high-level disaster recovery procedure for a basic DC RUM installation available. Backing Up the Report Server To back up a report server, back up the repository, the report configuration, and the user-created custom settings. 1. Perform a manual backup of the Microsoft SQL Server database repository. The directions to follow depend on the version of Microsoft SQL Server that you are using. For more information, see Backing Up MS SQL Server 2005 CAS Databases [p. 109] and Backing Up MS SQL Server 2008 CAS Databases [p. 111]. Store the backup in a safe place. 2. Backup the report server configuration. a. Log in as an administrator. b. Copy all of the files located in the server_installation_dir \config directory to the backup device. 3. Backup the user-created configurations and queries. Copy all of the files located in the server_installation_dir\classes\customqueries directory to the backup device. Backing Up MS SQL Server 2005 CAS Databases Before You Begin Before proceeding with a backup, ensure that there is enough free disk space to accommodate the backup file. The backup file size will be similar in size to the amount of storage used by the database. Verify the amount of available space can in the database properties (Size - Space available). 109

110 Appendix F Backup and Recovery Procedures The report server is Central Analysis Server and the default database name is CAS (or delta in older installations). 1. Stop the report server service. 2. Launch SQL Server Management Studio. From the Start menu, select Start Programs Microsoft SQL Server 2008 SQL Server Management Studio. 3. Log in to the SQL Server Management Studio. A login screen prompts for your user name and password. 4. In the Object Explorer, on the left side of the screen, select Databases CAS. 5. Right-click the report server database and choose Tasks Back Up. 6. On the General page, remove any existing backup destinations by clicking Remove. 7. Click Add to add a new backup destination. 8. Specify the path and name of the file for the database backup and click OK. 9. On the Options page, select Overwrite all existing backup sets. 10. Click OK to start the backup process. The database will now be backed up. 11. After the backup is complete, restart the report server service. Backing Up MS SQL Server 2005 ADS Databases Before You Begin Before proceeding with a backup, ensure that there is enough free disk space to accommodate the backup file. The backup file size will be similar in size to the amount of storage used by the database. Verify the amount of available space in the database properties (Size - Space available). The report server is Advanced Diagnostics Server and the default database name is ADS (or delta in older installations). 1. Stop the report server service. 2. Launch SQL Server Management Studio. From the Start menu, select Start Programs Microsoft SQL Server 2008 SQL Server Management Studio. 3. Log in to the SQL Server Management Studio. A login screen prompts for user name and password. 4. In the Object Explorer, on the left side of the screen, select Databases ADS. 5. Right-click the report server database and choose Tasks Back Up. 6. On the General page, remove any existing backup destinations by clicking Remove. 7. Click Add to add a new backup destination. 8. Specify the path and name of the file for the database backup and click OK. 110

111 Appendix F Backup and Recovery Procedures 9. On the Options page, select Overwrite all existing backup sets. 10. Click OK to start the backup process. The database will now be backed up. 11. After the backup is complete, restart the report server service. Backing Up MS SQL Server 2008 CAS Databases Before You Begin Before proceeding with a backup, ensure there is enough free disk space to accommodate the backup file. The backup file size will be similar in size to the amount of storage used by the database. Verify the amount of available space in the database properties (Size - Space available). The report server is CAS and the default database name is CAS (or delta in older installations). 1. Stop the report server service. 2. Launch SQL Server Management Studio. From the Start menu, select Start Programs Microsoft SQL Server 2008 SQL Server Management Studio. 3. Log in to the SQL Server Management Studio. A login screen prompts for your user name and password. 4. In the Object Explorer, on the left side of the screen, select Databases CAS. 5. Right-click the report server database and choose Tasks Back Up. 6. On the General page, remove any existing backup destinations by clicking Remove. 7. Click Add to add a new backup destination. 8. Specify path and name of the file for the database backup and click OK. 9. On the Options page, select Overwrite all existing backup sets. 10. Click OK to start the backup process. The database will now be backed up. 11. After the backup is complete, restart the report server service. Backing Up MS SQL Server 2008 ADS Databases Before You Begin Before proceeding with a backup, ensure there is enough free disk space to accommodate the backup file. The backup file size will be similar in size to the amount of storage used by the database. Verify the amount of available space in the database properties (Size - Space available). The report server is Advanced Diagnostics Server and the default database name is ADS (or delta in older installations). 1. Stop the report server service. 2. Launch SQL Server Management Studio. 111

112 Appendix F Backup and Recovery Procedures From the Start menu, select Start Programs Microsoft SQL Server 2008 SQL Server Management Studio. 3. Log in to the SQL Server Management Studio. A login screen prompts for your user name and password. 4. In the Object Explorer, on the left side of the screen, select Databases ADS 5. Right-click the report server database and choose Tasks Back Up. 6. On the General page, remove any existing backup destinations by clicking Remove. 7. Click Add to add a new backup destination. 8. Specify the path and the name of the file for the database backup and click OK. 9. On the Options page, select Overwrite all existing backup sets. 10. Click OK to start the backup process. The database will now be backed up. 11. After the backup is complete, restart the report server service. Backing Up the AMD Configuration Make backup copies of the AMD configuration regularly. Note that the configuration can only be restored for the same AMD version. Before You Begin Backing up the current AMD configuration requires: An operating, fully configured AMD device. An external medium or access to another computer that is independent of the AMD device. 1. Log on to the AMD as user root. 2. Stop all of the AMD traffic monitoring services. Use the ndstop command on the Linux command line prompt to stop the traffic monitoring software. 3. Save the existing AMD configuration. To preserve the existing configuration, save the contents of the configuration directory /usr/adlex/config. Use an appropriate method to save this directory to an external medium or another computer. In this example, the tar command is used to archive the configuration directory and the scp command is used to copy the archive to a remote backup machine. tar -czf amd_config.tar.gz /usr/adlex/config/ Next, copy the archive to the remote backup machine: scp amd_config.tar.gz username@backup_machine_ip_address:backup_directory where username is the login name of the user account to use on the remote backup machine, backup_machine_ip_address is the backup machine's IP address, and backup_directory is the directory name where the backup file will be copied to. 112

113 Appendix F Backup and Recovery Procedures IMPORTANT There are several other ways to back up directories. Regardless of the method you choose, be sure to preserve the user rights for the directory and files that are backed up. This is required because the files located in the config directory have different owners. 4. Restart the AMD software using the ndstart command at the command line prompt. Backing Up the RUM Console Database Before You Begin Before proceeding with a backup, ensure that there is enough free disk space to accommodate the backup file. The backup file size will be similar in size to the amount of storage used by the database. In SQL Server Management Studio Object Explorer on the left side of the screen, select Databases cva (default name), right-click cva and choose Properties. See the database size on the General page in the Database section. The default database name is cva. 1. Stop the RUM Console service. Launch the Windows Services and stop the Dynatrace RUM Console service. 2. Log in to the SQL Server Management Studio. A login screen will prompt you for your user name and password 3. Right-click the database and choose Tasks Back Up 4. On the General page, remove any existing backup destinations by clicking Remove. 5. Click Add to add a new backup destination. 6. Specify the path and the backup file name. The default backup file name is cva.bak 7. On the Options page, and elect Overwrite all existing backup sets. 8. Click OK to start the backup process. The database will now be backed up. 9. After the backup is complete, you can start the Dynatrace RUM Console service. Backing Up CSS All data for CSS is contained in its database, so we recommend that you perform regular database backups. If you are using LDAP authentication, there are additional files that also should be backed up if the CSS needs to be restored on a different machine. 1. Using your applicable database procedures, back up the database on a regular basis (nightly, for example). 2. Back up the contents of <install_dir>\common Components\cc\eclipse\workspace\com.compuware.frameworks.security\. 113

114 Appendix F Backup and Recovery Procedures If you are using LDAP authentication, back up this folder after you configure this feature to retain those settings. Backing Up the Dynatrace Enterprise Portal To back up the Portal, back up its database, a properties file and any user-added files and directories. 1. Perform a manual backup of the database, following instructions from your database vendor. 2. Back up the portal-customizations.properties file. The file is located at: <Portal_Home>\tomcat\webapps\ROOT\WEB-INF\classes. This file contains database information for the Portal, along with information on any other properties that were overwritten. 3. Back up any new directories and files that were added or updated by users. These files can be used in a recovery mode by copying them to a new location. Disaster Recovery Procedure This is a high-level recovery procedure for a basic DC RUM installation. It provides an overview of the console, manager, report server, and AMD restoration sequence. Follow the links for details. Most of the devices within DC RUM are configured individually. The sequence of the recovery of each device is not critical, but it can be beneficial to follow this path: 1. Recover and configure the AMD. For more information, see Restoring an AMD Backup Configuration [p. 115]. 2. Recover the Central Security Server. For more information, see Restoring CSS [p. 116]. 3. Recover the report server. For more information, see Restoring Report Server [p. 118]. 4. Recover the database on the report server. Depending on which version of MS SQL Server you are using, refer to Restoring MS SQL Server 2008 Databases [p. 123] or Restoring MS SQL Server 2005 Databases [p. 120] 5. Recover the console database. For more information, see Restoring the RUM Console Database [p. 119]. 6. Recover the console. For more information, see Restoring the RUM Console [p. 119]. 7. If used, recover the Dynatrace Enterprise Portal. For more information, see Restoring the Dynatrace Enterprise Portal [p. 119]. 114

115 Appendix F Backup and Recovery Procedures What to Do Next Optionally, it is possible to recover a specific AMD configuration using a previously exported XML file. For AMDs that require such a recovery, import and publish the configuration using RUM Console. Restoring an AMD Backup Configuration Restore the AMD configuration back up by recreating the archived /usr/adlex/config directory. Note that the configuration can only be restored for the same AMD version. Before You Begin You need: Access to media with the backup or a backup computer used to store the saved configuration. Administrator privileges for the AMD device. Knowledge of how the backup was performed, such as which path was saved. The following example assumes that the configuration directory was archived without including the full path using the tar command. To restore your backup configuration: 1. Log on to the AMD as user root. 2. Stop all of the AMD traffic monitoring services. Use the ndstop command on the Linux command line prompt to stop the traffic monitoring software. 3. Restore the AMD configuration from the archive. Choose the appropriate restoration method, depending on whether you saved the back up to a disc (CD or DVD) or on a remote backup machine. IMPORTANT Regardless of the method used to back up the AMD configuration, be sure to preserve the user rights for the directory and files that you restore. This is required because the files located in the config directory have different owners. If the back up file is on a disc: a. Mount the media drive where the back up is stored. mount /dev/cdrom /mnt If there is no system output, use the mount command to ensure you have access to the backup media. See whether the output includes the path to the media. For example: $ mount /dev/hdc on /mnt type iso9660 (ro) 115

116 Appendix F Backup and Recovery Procedures b. If the backup command included the full path to the config directory, ensure that the working path is a root directory of the AMD device and execute the following command to unpack the archive: cd /usr/adlex/config/ tar -xzvf /mnt/amd_config.tar.gz If the backup file has been created following the procedure in Backing Up the AMD Configuration [p. 112] and is located on a remote backup computer: a. Copy the configuration saved on the backup machine to the system root on the AMD machine. scp username@backup_machine_ip_address:backup_directory amd_config.tar.gz b. Unpack the archive. tar -xzvf amd_config.tar.gz 4. Restart the AMD software using the ndstart command at the command line prompt. Restoring CSS If the CSS goes down for some reason, users will still be able to log into the products for a limited time while issues are investigated. CSS is a standalone application that stores all of its data in a database. For recovery purposes, you can reinstall CSS and reconnect to the existing database. The following recovery procedures cover scenarios when the database is unavailable or corrupt, either of which will make CSS inoperable, even if you have configured CSS for failover. It is important to regularly back up your databases to minimize data loss and system downtime. Recovering CSS With a Corrupt Database If the CSS database content is corrupted and CSS cannot allow user authentication, the preferred recovery method is to restore the latest backup of the SQL Server or Oracle database. Once the database is restored, CSS can be restarted and it will return to normal operation. If the database backup cannot be used (for example, if it also is corrupted), CSS has a second recovery option. The CSS stores data snapshots in the file system as.properties files. Snapshots are triggered when configurations for users, user groups, or role assignments are updated. If there are no configuration changes for 15 minutes, the snapshot of the latest configuration is saved. Up to 20 snapshots will be saved, and older snapshots will be deleted to accommodate newer snapshots. These snapshots can be found in <install_dir>\cc\eclipse\workspace\com.compuware.frameworks.security\archive\. If you have configured CSS for failover, obtain the snapshot from the primary CSS. The snapshot filenames start with compuwaresecurityapplicationdata and contain a timestamp of when they were written and the version of the archiving software. An example of an actual name is: compuwaresecurityapplicationdata_ _v3.0.0.[database 116

117 Appendix F Backup and Recovery Procedures type].properties. The timestamps are not human readable; if you want to know when the snapshot was stored, look at the file's creation date. To restore users, groups and role assignments from a snapshot: 1. Stop the CSS service, including any failover CSS configured. 2. Create a new, empty database. 3. Update the following file with the new database name (unless the database was deleted and recreated): <install_dir>\cc\eclipse\workspace\com.compuware.frameworks.security\ compuwaresecurityjdbcconfiguration.properties. 4. Copy the desired snapshot file and paste it one folder higher at <install_dir>\cc\eclipse\workspace\com.compuware.frameworks.security. 5. Rename the pasted file to compuwaresecurityapplicationdata.properties. 6. Restart the CSS service. 7. If you configured CSS for failover, repeat Step 3 [p. 117] and Step 6 [p. 117] on the failover servers. During initialization, the CSS will create the necessary database tables and populate them with the contents of the promoted snapshot file. Recovering CSS With an Unavailable Database If CSS does not operate because a database server is not available, or if there are no DBA resources available to create a fresh database, a local Derby database can be used temporarily to minimize downtime. In this scenario, if you have configured CSS for failover, you will lose that failover protection until the SQL Server or Oracle database is available again. NOTE Running for extended periods with the temporary Derby database is not recommended because of a lack of automated backup and other management facilities. In particular, the Derby database is susceptible to corruption if the local disk is full. 1. Shut down the CSS service, including any CSS failover servers. 2. Reconfigure CSS to use the local Derby database: a. Back up <install_dir>\cc\eclipse\workspace\com.compuware.frameworks.security\ compuwaresecurityjdbcconfiguration.properties. Rename the file so that it will not be overwritten later in the procedure. b. Rename compuwaresecurityjdbcconfiguration_derby.properties to compuwaresecurityjdbcconfiguration.properties. 3. Pick a configuration snapshot file and promote it. Review Recovering CSS With a Corrupt Database [p. 116] for information on how snapshots are created, where they are located and how they are restored. See Step 4 [p. 117] on where to paste the snapshot file. 4. Restart the CSS service. 117

118 Appendix F Backup and Recovery Procedures The CSS will now be fully operational and users will be able to continue all normal operations, including making changes to users, groups, and roles. The Derby database is named cpwrsecuritydb and is located in <install_dir>\cc\eclipse\workspace. The username and password are both cpwrsecurity. When the Production Database Server is Back Online 5. Create a new CSS database (or clear out the existing database). 6. Restore the backed up default database configuration file renamed in Step 2.a [p. 117]. Rename the file to its original name, compuwaresecurityjdbcconfiguration.properties. 7. Promote the latest configuration snapshot file used in Step 3 [p. 117] 8. Restart the CSS service. CSS will be running with a production database. Restoring Report Server Use the restore procedure for a clean server reinstallation or as a running server reinstallation. The former situation applies, for example, to a total hard drive failure and replacement, while the latter to database corruption or configuration failure. Clean Server Reinstallation To restore a report server by reinstalling the server: 1. Reinstall the operating system including the same updates and patches that were applied to the backed up version. 2. Reinstall the report server software with the database using the identical installation parameters and settings as in the backed up version. 3. Copy the entire contents of the config directory from your backup archive to the corresponding location on a report server. 4. Copy the entire contents of the classes\customqueries from your backup archive to the corresponding location on a report server. 5. Manually restore the MS SQL database. 6. Restart the report server. Running the Server Reinstallation To restore a report server where the operating system or the report server software has not been reinstalled, follow these steps: 1. Log in as a system administrator. 2. Stop the report server engine using the Watchdog service manager. 3. Copy the entire contents of both config and classes\customqueries directories to their corresponding location on a report server overwriting any existing files. 4. Manually restore the MS SQL database. 118

119 Restoring the RUM Console Database NOTE The default database name is cva. Appendix F Backup and Recovery Procedures 1. Stop the RUM Console service. Launch the Windows Services and stop the Dynatrace RUM Console service. 2. Copy the latest version of the backed up database to your local hard drive and, if the backup file is compressed, unpack it. 3. Log in to the SQL Server Management Studio: a login screen will prompt you for your user name and password. 4. In the Object Explorer, on the left side of the screen, select Databases cva database. 5. Right-click the cva database, choose Tasks Restore Database. 6. Select to restore From device. 7. Click... and select the file that holds the cva database backup. In the Restore column on the General page, select the check box beside the name of the file. 8. Switch to Options page, select Overwrite the existing database. Ensure the file name and path is correct. For example:...\mssql\data\cva_log.ldf for the database log file and...\mssql\data\cva.mdf for the database file. Click OK to start the restore process 9. Start the RUM Console service. Launch the Windows Services and start the Dynatrace RUM Console service. Restoring the RUM Console To recover the RUM Console, reinstall it. RUM Console is a standalone application that does not store any information within itself. Because it relies on data provided from the RUM Console Server, reinstalling the console package is sufficient to fully recover the RUM Console. For more information, see Installing, Running, and Uninstalling RUM Console Components in the Data Center Real User Monitoring RUM Console Installation Guide. Restoring the Dynatrace Enterprise Portal In case of a database corruption leading to a Portal failure, you can restore a backed up database and reconfigure the Portal to use the backed up database and other backed up files. For more information, see Restoring the Portal Due to a Corrupt or Unavailable Database [p. 120]. If a Portal failure requires reinstallation, you can use the backed up database and other files to recreate your environment. For more information, see Portal Reinstallation and Restoration [p. 120]. 119

120 Appendix F Backup and Recovery Procedures Restoring the Portal Due to a Corrupt or Unavailable Database 1. Stop the Dynatrace Enterprise Portal service. 2. In your Portal installation, open <Portal_Home>\tomcat\webapps\ROOT\WEB-INF\classes\portal-customizations.properties. 3. Edit the file to point to the most recent backup of the database: a. jdbc.default.url: point to the most recent database backup. b. jdbc.default.username: user name to access the database backup. c. jdbc.default.password: password to access the database backup. d. jdbc.default.encrypted.password=true: password is non-encrypted. 4. Start the Dynatrace Enterprise Portal service. Your Portal should be restore. Portal Reinstallation and Restoration Follow this procedure for reinstalling a new Portal for recovery. 1. Install a new Dynatrace Enterprise Portal. During installation, you will install a new database, but it will be overwritten later. 2. Stop the Dynatrace Enterprise Portal service. 3. Restore the backed up database over the new database created during the new installation. 4. Copy over any added or updated files that were used to customize your original Portal. They should have been backed up as part of the Portal backup procedure. Copy them to the same location as they were initially. For more information, see Backing Up the Dynatrace Enterprise Portal [p. 114]. 5. Start the Dynatrace Enterprise Portal service. Restoring MS SQL Server 2005 Databases NOTE Depending on configuration, the default database name is CAS, ADS, or delta in older installations. 1. Copy the latest version of the backed up database to your local hard drive and if the backup file is compressed, unpack it. 2. Launch SQL Server Management Studio. Select Start Programs Microsoft SQL Server 2005 SQL Server Management Studio. 3. Log in to the SQL Server Management Studio. A login screen prompts for your user name and password. 4. In Object Explorer, on the left side of the screen, select Databases CAS database. 5. Right-click the CAS database and choose Tasks Restore Database. 120

121 Appendix F Backup and Recovery Procedures 6. Select to restore From device. 7. Click... and, in the Restore column on the General page, select the check box next to the name of the CAS database backup file. 8. On the Options page, select Overwrite the existing database and click OK. Ensure the file names and paths are correct. For example: \mssql\data\cas_log.ldf for the database log file and \mssql\data\cas_dat.mdf for the database file. 121

122 Appendix F Backup and Recovery Procedures 9. To activate the restored database, right-click the CAS database, choose New Query from the menu, and type the following script: ALTER AUTHORIZATION ON SCHEMA::delta TO dbo; GO drop user delta go IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N'delta') ALTER LOGIN delta WITH PASSWORD = 'delta', DEFAULT_DATABASE = CAS, CHECK_POLICY = OFF; ELSE CREATE LOGIN delta WITH PASSWORD = 'delta', DEFAULT_DATABASE = CAS, CHECK_POLICY = OFF; GO create USER delta for login delta WITH DEFAULT_SCHEMA = delta; GO ALTER AUTHORIZATION ON SCHEMA::delta TO delta; GO EXEC = = N'bulkadmin' GO grant all to delta RECONFIGURE WITH OVERRIDE go 122

123 Appendix F Backup and Recovery Procedures Select the CAS database from the menu and press [F5] to execute the script. The database is now restored and available. 10. Set Recovery model to Simple. a. Right-click the database and select Properties. b. Select Options. c. Set Recovery model to Simple. d. Click OK. 11. Shrink the log file. a. Right-click the database and select Tasks Shrink Files. b. Set File type to Log. c. Click OK. 12. Start the Central Analysis Server service or the Advanced Diagnostics Server, depending on your installation. Restoring MS SQL Server 2008 Databases NOTE Depending on configuration, the default database name is CAS, ADS, or delta in older installations. 1. Copy the latest version of the backed up database to your local hard drive and if the backup file is compressed, unpack it. 2. Launch SQL Server Management Studio. Select Start Programs Microsoft SQL Server 2008 SQL Server Management Studio 3. Log in to the SQL Server Management Studio. A login screen prompts for your user name and password. 4. In Object Explorer, on the left side of the screen, select Databases CAS database. 5. Right-click the CAS database and choose Tasks Restore Database. 123

124 Appendix F Backup and Recovery Procedures 6. Select to restore From device. 7. Click... and in the Restore column on the General page, select the check box next to the name of the CAS database backup file. 8. On the Options page, select Overwrite the existing database and click OK. Ensure the file names and paths are correct. For example: \mssql\data\cas_log.ldf for the database log file and \mssql\data\cas_dat.mdf for the database file. 124

125 Appendix F Backup and Recovery Procedures 9. To activate the restored database, right-click the CAS database, choose New Query from the menu and type the following script: ALTER AUTHORIZATION ON SCHEMA::delta TO dbo; GO drop user delta go IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N'delta') ALTER LOGIN delta WITH PASSWORD = 'delta', DEFAULT_DATABASE = CAS, CHECK_POLICY = OFF; ELSE CREATE LOGIN delta WITH PASSWORD = 'delta', DEFAULT_DATABASE = CAS, CHECK_POLICY = OFF; GO create USER delta for login delta WITH DEFAULT_SCHEMA = delta; GO ALTER AUTHORIZATION ON SCHEMA::delta TO delta; GO EXEC = = N'bulkadmin' GO grant all to delta RECONFIGURE WITH OVERRIDE go 125

126 Appendix F Backup and Recovery Procedures Select the CAS database from the menu and press [F5] to execute the script. Your database is now restored and available. 10. Set Recovery model to Simple. a. Right-click the database and select Properties. b. Select Options. c. Set Recovery model to Simple. d. Click OK. 11. Shrink the log file. a. Right-click the database and select Tasks Shrink Files. b. Set File type to Log. c. Click OK. 12. Start the Central Analysis Server service or the Advanced Diagnostics Server, depending on your installation. 126

127 Index Index A ADS 21, 26 general requirements 26 recommended platform hardware 21 AMD 21, 115 recommended platform hardware 21 restoring configuration 115 analyzer 91 supported by CAS 91 B backup , 115 AMD configuration 112, 115 Microsoft SQL Server 2005 database ADS 110 CAS 109 Microsoft SQL Server 2008 database 111 ADS 111 CAS 111 Microsoft SQL Server database 113 RUM Console 113 backup procedure 114 Dynatrace Enterprise Portal 114 basic configuration settings 59 browsers 12, 14 configuring 12 localization 14 versions supported 12 C CAS 11, 21, 26, 30, 41, 47 49, 51 52, 61, 67, 70, 91 changing RUM Console options after installation 70 configuration 61 modifying basic settings 61 general requirements 26 migrating 48 49, to 64-bit to new platform migrating CSS users after installation 67 recommended platform hardware 21 supported protocols 91 system requirements 30 upgrade validation 47 upgrading 41 Central Analysis Server, See CAS Cerner 91 certificate 39 installation 39 changing installation settings 67 Cisco 21 recommended platforms 21 component 8 update 8 configuration 12, 37, 112, 115 backing up 112 browser 12 CAS 37 restoring 115 contact information 8 Restoring the Dynatrace Enterprise Portal 120 cpwr.exe 73 CSS 67, 113,

128 Index CSS (continued) database backups 113 migrating users after CAS installation 67 recovery procedure 116 corrupt database 116 recovery process 117 unavailable database server 117 restoring a release 116 Customer Support 8 D Data Center Real User Monitoring upgrade workflow 41 database , 113, , 123 backup in Microsoft SQL Server 113 RUM Console 113 backup in Microsoft SQL Server ADS 110 CAS 109 backup in Microsoft SQL Server ADS 111 CAS 111 restore in Microsoft SQL Server restore in Microsoft SQL Server , 123 database user password 70 changing after CAS installation 70 DB2 (DRDA) 91 CAS 91 DC RUM 21 system requirements 21 decode 91 supported by CAS 91 Dell 23 recommended platforms 23 DLM 73 DNS 91 DRDA (DB2) 91 CAS 91 Dynatrace 114 recovery procedure 114 Dynatrace Enterprise Portal 75, 77, 82, 119 installation 77 integrating with DC RUM 75 recovery procedure 119 system requirements 75 upgrading to latest release 82 Dynatrace Enterprise Portal backup procedure 114 E Epic 91 ESMTP 91 Exchange/RPC 91 G general hardware requirements 26 H HP 24 recommended platforms 24 HTTP 91 HTTP settings 68 changing after CAS installation 68 HTTPS 37 I IBM WebSphere MQ 91 ICA (Citrix) 91 ICMP 91 Informix 91 installation 17 19, 31, 77, 79 CAS 31 Dynatrace Enterprise Portal 77, 80 Dynatrace Enterprise Portal on Solaris 79 planning checklist 17 determining current inventory 18 determining requirements 19 estimating time required 19 identifying goals 18 licensing 18 installation on Linux 80 Dynatrace Enterprise Portal 77, 80 international features support 14 character encoding 14 localized browser 14 localized server 14 IP 91 ISP Extended mode 62 J Jolt 91 K Kerberos

129 Index L licensing 73 localization 14 browser 14 character encoding 14 server 14 logging in to report server 57 M Microsoft SQL Server 30, , 104, 107, 113 database backup 113 RUM Console 113 installation 30, , 104 manual database creation 107 Microsoft SQL Server , 120 database backup ADS 110 CAS 109 database restore 120 Microsoft SQL Server , 119, 123 database backup 111 ADS 111 CAS 111 database restore 119, 123 migrating 41, 48 49, CAS 41, 48 49, to 64-bit to new platform N NetFlow 91 O online support site 8 Oracle 91 P platforms 21, recommended 21, Cisco 21 Dell 23 HP 24 protocol 91 protocol (continued) analyzer 91 supported by CAS 91 PVU mode 62 R recovery 119 RUM Console 119 recovery procedure 119 Dynatrace Enterprise Portal 119 report server 12, 21, 26, 37, 85, 109 backup 109 communication over HTTPS 37 general requirements 26 recommended platform hardware 21 secure communication 37 supported browsers 12 troubleshooting 85 restore 115, , 123 AMD configuration 115 Microsoft SQL Server 2005 database 120 Microsoft SQL Server 2008 database 119, 123 Restoring 120 Dynatrace Enterprise Portal 120 RUM Console 26, 70, 119 changing options after CASinstallation 70 recovery 119 S SAP GUI 91 SAP RFC 91 scalability 62 ISP Extended mode 62 PVU mode 62 server 39 security 39 certificate 39 site 60 configuration 60 sizing 62 ISP Extended mode 62 PVU mode 62 SMB 91 SMTP 91 SOAP 91 SSL

130 Index SSL Server settings 68 changing after CAS installation 68 system requirement 12 supported browsers 12 system requirements 21, 28, 30 CAS 30 recommended operating system configuration 28 System requirements 75 Dynatrace Enterprise Portal 75 T TCP 91 TDS 91 Thawte 39 certificate 39 Tier 1 hardware 21, Cisco 21 Dell 23 HP 24 Tier 2 hardware 21, 24 Cisco 21 HP 24 troubleshooting 85 installation and upgrade 85 U UDP 91 uninstalling report server 55 update 8 component 8 update (continued) product 8 upgrade 17 19, 41 ADS 41 AMD 41 CAS 41 CSS 41 Data Center Real User Monitoring 41 planning checklist 17 determining current inventory 18 determining requirements 19 estimating time required 19 identifying goals 18 licensing 18 RUM Console 41 upgrading 41, CAS 41, to 64-bit Upgrading 82 Dynatrace Enterprise Portal 82 user 60 aggregation 60 tracking 60 User activity details on demand 62 user aggregation V VoIP 91 X XML