Data Center Real User Monitoring

Transcription

1 Data enter Real User Monitoring Advanced Diagnostics Server Installation Guide Release

2 Please direct questions about Advanced Diagnostics Server or comments on this document to: APM ustomer Support FrontLine Support Login Page: opyright 2012 ompuware orporation. All rights reserved. Unpublished rights reserved under the opyright 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 ompuware orporation license agreement and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (OT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. ompuware orporation. This product contains confidential information and trade secrets of ompuware orporation. Disclosure is prohibited without the prior express written permission of ompuware orporation. Use of this product is subject to the terms and conditions of the user's License Agreement with ompuware orporation. 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 ompuware orporation. ompuware orporation may change the content specified herein at any time, with or without notice. All current ompuware orporation product documentation can be found at 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. Build: January 3, 2013, 23:48

3 ontents ontents Introduction Who Should Read This Guide Organization of the Guide Related Publications Accessing ustomer Support Reporting a Problem Documentation onventions hapter 1 Advanced Diagnostics Server Overview Supported Browsers and onnectivity Internationalization Support hapter 2 Planning and Preparation Installation and Upgrade Planning hecklist ompare Release Notes to Goals Obtain Licensing Inventory the urrent Deployment Identify Latest Hardware and Software Requirements Estimate the Installation or Upgrade Duration hapter 3 System Requirements Recommended Hardware for AMDs and Report Servers Report Server Requirements Recommended Operating System onfiguration for Report Servers Microsoft SQL Server 2005 Setup Recommendations SQL Server 2005 Installation SQL Server 2005 onfiguration hapter 4 Installing Advanced Diagnostics Server onfiguring Report Server to Use Private Keys and ertificates Importing A ertificates hapter 5 ADS Upgrade Overview Running an Advanced Diagnostics Server Upgrade

4 ontents Migrating 32-bit ADS to 64-bit ADS Backing Up MS SQL Server 2005 ADS Databases Backing Up MS SQL Server 2008 ADS Databases hapter 6 Uninstalling the Report Server hapter 7 Logging in to the Report Server hapter 8 ADS Basic onfiguration Settings Modifying ADS Basic onfiguration Settings ADS Scalability-Related onfiguration Properties onfiguring Other ADS Settings hapter 9 hanging ADS Settings Defined During Installation hanging the HTTP and SSL Server Settings on ADS hanging the Database User Password on ADS hapter 10 Licensing Data enter Real User Monitoring omponents Appendix A ompuware Security Server Management Install the ompuware Security Server (SS) Moving the Location of the Security Server Appendix B Integrating DRUM with the Enterprise Portal Installing the Enterprise Portal Appendix Providing Failover for Report Server Failover lustering on Windows Server Failover lustering Prerequisites Failover lustering Installation Process Running a Report Server Setup on a Failover Node hanging Default Report Server Service Settings on a Failover Node Defining High Availability for Report Server Service Migrating Existing Report Server Installation to Provide High Availability Using lustering Feature Migrating Report Server Failover luster to Provide High Availability Using lustering Feature Starting, Stopping, and Accessing Report Server Working in Failover luster..... Appendix D Report Server Installation and Upgrade Troubleshooting Appendix E Protocols Supported by ADS Appendix F SQL Operations Performed During Report Server Installation or Upgrade Database reation reating a Database User Database User Rights Set Memory Size

5 ontents Appendix G reating ADS Database and Database User with Microsoft SQL Server Management Studio Index

6 ontents 6

7 INTRODUTION Who Should Read This Guide This guide is intended to be used by network engineers and system administrators installing the Advanced Diagnostics Server. Organization of the Guide This installation guide is organized as follows: Advanced Diagnostics Server Overview [p. 13] - Describes the Advanced Diagnostics Server release and lists the supported protocols. Planning and Preparation [p. 19] - Offers planning and preparation guidance you should review before starting software installation or upgrade. System Requirements [p. 23] - Describes the minimum hardware and software requirements for Advanced Diagnostics Server. Installing Advanced Diagnostics Server [p. 39] - Describes how to install the Advanced Diagnostics Server. Upgrading entral Analysis Server in the Data enter Real User Monitoring entral Analysis Server Installation Guide - Describes how to upgrade the Advanced Diagnostics Server. Uninstalling the Report Server [p. 53] - Describes how to remove the Advanced Diagnostics Server. Logging in to the Report Server [p. 55] - Describes how to log in to the Advanced Diagnostics Server. ADS Basic onfiguration Settings [p. 57] - Describes how to configure the Advanced Diagnostics Server. hanging ADS Settings Defined During Installation [p. 63] - Describes how to later change basic settings that you specified during installation of the Advanced Diagnostics Server. 7

8 Introduction Licensing Data enter Real User Monitoring omponents [p. 67] - Describes product licensing. Report Server Installation and Upgrade Troubleshooting [p. 107] - Describes how to solve installation and upgrade problems. Protocols Supported by ADS [p. 113] - Lists protocols supported by ADS. SQL Operations Performed During Report Server Installation or Upgrade [p. 117] - Describes SQL operations that run during report server installation or upgrade. reating ADS Database and Database User with Microsoft SQL Server Management Studio [p. 125] - Describes how to use Microsoft SQL Server Management Studio to create a ADS database and database user. Related Publications Documentation for your product is distributed on the product media. For DRUM, it is located in the \Documentation directory. It can also be accessed from the Media Browser. You can also access online documentation for ompuware products via our FrontLine support site at FrontLine provides fast access to information about your ompuware 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 Accessing ustomer Support orporate Web Site To access ompuware's site on the Web, go to The ompuware site provides a variety of product and support information. FrontLine Support Web Site You can access online customer support for ompuware products via our FrontLine support site at FrontLine provides fast access to critical information about your ompuware products. You can read or download documentation, frequently asked questions, and product fixes, or your questions or comments. The first time you access FrontLine, you are required to register and obtain a password. Registration is free. ontact Us The contact information to all local ompuware offices is provided on the Web site. All high-priority issues should be reported by phone. 8

9 Reporting a Problem When contacting APM ustomer Support, please provide as much information as possible about your environment and the circumstances that led to the difficulty. You should be ready to provide: lient number. This number is assigned to you by ompuware and is recorded on your sales contract. The version number of the AMD, report servers, and RUM onsole with RUM onsole Server. Report Server Use the report server GUI by selecting Help Product Information About, or Tools Diagnostics System Status. AMD Scroll down to the Testing AMD section. At the bottom of the diagnostic data paragraph, look for Version ND-RTM v. ndw.ww.x.y.zz. RUM onsole and RUM onsole Server Use the RUM onsole GUI by selecting Help About menu item. TAM Use the TAM GUI by selecting Help About menu item. Environment information, such as the operating system and release (including service pack level) on which the product (AMD, report server) is installed, memory, hardware/network specifications, and the names and releases of other applications that were running. Problem description, including screen captures. Exact error messages, if any (screen captures recommended). Whether or not the problem is reproducible. If it is, include a sequence of steps for problem recreation. If it is not, include a description of the actions taken before the problem occurred. A description of the actions that may have been taken to recover from the problem, and their results. Debug information for specific components obtained from RUM onsole. Information about the RUM onsole itself. To export all the information, navigate to Tools Export Diagnostic Information in the RUM onsole menu. Information about the report servers. To export the information for a specific ADS or AS, right-click the device on the Devices tab in the RUM onsole and choose Export Diagnostic Information from the context menu. Include ollector Diag Option to include diagnostic information on data collectors attached to the report server. Save as Destination path and filename for the diagnostic package file. Introduction 9

10 Introduction Information about the AMD. To export the information for a specific AMD, right-click the device on the Devices tab in the RUM onsole and choose Export Diagnostic Information from the context menu. Include Data Files Option to include fragments of traffic data. Time range Time range of the monitoring data to be included with the diagnostics. Data File Filter (RegEx) Regular expression filter for monitoring data files generated during the defined time range. Save as Destination path and filename for the diagnostic package file. Information from the TAM System Event log of the machine where the TAM is operating. TAM logs which by default are stored in :\ProgramData\ompuware\VTAM for Windows Server 2008 and :\Documents and Settings\All Users\ompuware\VTAM for Windows Server NOTE Please compress all the files before sending them to ustomer Support. ompuware values your comments and suggestions about the ompuware APM products and documentation. Your feedback is very important to us. If you have questions or suggestions for improvement, please let us know. Documentation onventions The following font conventions are used throughout documentation: This font Bold itation Documentation onventions [p. 10] 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 ompuware documentation. ited 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: 10

11 Introduction This font Indicates cd directory_name Menu Item Screen Menu items. Text screen shots. ode block Blocks of code or fragments of text files. 11

12 Introduction 12

13 HAPTER 1 Advanced Diagnostics Server Overview Advanced Diagnostics Server (ADS) performs detailed analysis of key transactional application protocols and delivers definite answers to individual user problems regarding performance and errors of business-critical front-end and back-end applications. The sub-millisecond accuracy of ADS measurements enables precise identification of faulty components and operations. ADS analyzes the following transactional application protocols: HTTP/HTTPS Oracle Forms SAP Oracle MS SQL Sybase DB2 SOAP XML ADS also supports sequential transaction monitoring with exact measurements of the transaction sequence path, inter-step timings, and execution flow, and in this way helps you troubleshoot business processes supported by monitored applications. Performance, usage, and errors for each application user are mapped to the transactions executed through the Web site interaction. ADS builds an analytical model of Web site performance to find systemic problems that cause the HTTP/S-based application performance degradation. Systemic problem occurrences, reasons, and effects are quantified and assigned to the network, server, client delays or content design domains. Quantification of the effect and severity in simple terms (the number of slow page loads due to a particular domain failure) helps to focus efforts on addressing the most severe Web site problems. ADS provides you with: Detailed analysis of every application user, including every single operation and sub-operation (for example, HTTP page and page component) requested by the user, down to insight into the complete HTTP request header, request content, and response header. 13

14 hapter 1 Advanced Diagnostics Server Overview Problem-solving reports for Web sites that find systemic problems caused by HTTP-based application performance degradation (slow page loads are categorized due to the page size, page design, client link speed, or server issues). Detailed reporting on users' request attributes and response messages communicated to the user through HTML pages - so-called soft errors such as information on a requested product that is out of stock or the inability to process a reservation because a partner site did not respond. Transaction troubleshooting with insight into the exact sequence of steps taken by the user and with a drilldown to individual step execution flow and performance influencers. Integration with entral Analysis Server (AS) reporting, extending AS report workflow with detailed reporting on key application protocols. At the same time, the ADS is capable of filtering out all but the most critical operations, transactions, and users, so the ompuware APM database is not overloaded with unnecessary details. Supported Browsers and onnectivity DRUM users can access report servers through supported Web browsers. The following browsers are supported: Microsoft Internet Explorer version 7 9, with JavaScript and HTTP 1.1 settings enabled. Note that due to a different handling of the data within the HTML, Microsoft Internet Explorer may experience degradation in performance while viewing reports containing a large number of columns or reports containing a large number of tooltips. Mozilla Firefox, starting from version 3.5 to the most recent one, with JavaScript, cookie support, and HTTP 1.1 enabled. Before you start using the report server, it may be necessary to adjust Java, JavaScript, and HTTP 1.1 settings in your browser. 14

15 hapter 1 Advanced Diagnostics Server Overview NOTE Some configuration screens require a Web browser with Java plug-in version update 11 or later. If you use 32-bit and 64-bit browsers interchangeably, you need a Java plug-in for each browser. Remember that the Windows 64-bit operating system comes with 32-bit and 64-bit Internet Explorer (IE) browsers and that the 32-bit version runs as a default. Java Web Start-based RUM onsole requires Java JRE 6 installed on the desktop. ompuware recommends to use the latest Java JRE 6 update available from the Oracle Web site. Note that Java Web Start-based RUM onsole will only run on Windows and a 32-bit JRE. In Java plug-in version 1.5, TLS is turned off by default. This may cause some applets not to work in your Web browser. You must turn on TLS in the Java 1.5 ontrol Panel to have full access to all report server features. For more information, see How to enable TLS 1.0 for Java 1.5 plug-in [p. 16]. Without JavaScript 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. Due to Internet Explorer security policy, you may encounter some issues when executing Java applets. You need to modify the default settings for IE 9 to run applets. For more information, see Enabling Java Support in Internet Explorer 9 in the Data enter Real User Monitoring Administration Guide. ADS and AS can be accessed using HTTP or, over secured connections, using HTTPS. We recommend secure access with a browser that supports TLS v.1. Using older versions of the protocol, such as SSL 2 or SSL 3, is not recommended but can be configured. For more information, see onfiguring Report Server to Use Private Keys and ertificates [p. 39]. How to enable JavaScript and support for HTTP 1.1 in your browser Internet Explorer To enable JavaScript: 1. Select Tools Internet Options from the top menu in your browser and click the Security tab. 2. lick ustom level and enable Active scripting on the list of options. To enable HTTP 1.1: 1. Select Tools Internet Options from the top menu in your browser and click the Advanced tab. 2. Scroll within the Settings list to the section titled HTTP 1.1 settings and ensure that the Use HTTP 1.1 box is selected. 3. lick OK and restart your browser. 15

16 hapter 1 Advanced Diagnostics Server Overview Mozilla Firefox To enable JavaScript: 1. Select Tools Options from the top menu in your browser and click the ontent tab. 2. Select the Enable JavaScript box. To enable HTTP 1.1: 1. Open the browser and, in the address bar, type about:config and press [Enter]. The browser will display a list of current preferences. 2. Scroll to the network.http.version preference and ensure 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. How to enable TLS 1.0 for Java 1.5 plug-in The TLS for Java plug-in is turned on in Java ontrol Panel, in the Security settings of the Advanced tab. 1. Access the Java ontrol Panel in one of the following ways: Windows control panel: In Windows, click Start Settings ontrol Panel and select Java to open Java ontrol Panel. Note that Java ontrol Panel opens for the default Java installation, which may not be correct for the plug-in that you are trying to modify. Java installation directory: Navigate to the bin directory where the Java version you intend to modify is installed (for example <install_dir>\jre1.5.0_11\bin). lick the file javacpl.exe to activate the configuration tool. Java platform icon in system tray: Right-click the icon and choose Open ontrol Panel from the menu. 2. In the Java ontrol Panel, click the Advanced tab and expand the Security tree to display the Use TLS 1.0 check box. 3. Select the Use TLS 1.0 check box. 4. lick OK. Internationalization Support Advanced Diagnostics 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 16

17 hapter 1 Advanced Diagnostics Server Overview Japanese Korean hinese simplified For English, which is the default language setting, there is no need for additional configuration of the operating system or browser. To enable support for other languages, install the required font set for the target language and customize the regional options accordingly. haracter encoding support for monitored traffic By default, only UTF-8 encoding is supported and support for other encodings is turned off. It can be turned on selectively for HTTP processing and XML processing with the configuration options in the RUM onsole. Advanced Diagnostics Server recognizes the following character encodings: HTTP and XML/SOAP ISO MQ ISO Unicode (UTF-8) UTF-16 (XML/SOAP only) Japanese: EU-JP, Shift_JIS, Unicode (UTF-8) Korean: EU-KR, ISO-2022-KR, Unicode (UTF-8) hinese: Big5, Big5-HKSS, EU-TW, GB18030, GB2312, GBK, HZ, ISO-2022-N, Unicode (UTF-8) Unicode (UTF-8) Database/SQL (Oracle, TDS, DRDA, Informix) UTF-8 (all DB analyzers) UTF-16 (TDS analyzer only) EBDI (DRDA analyzer only) DB statements that were not sent in a supported encoding are encoded such that all non-asii characters are replaced with their hexadecimal value in the form %XX, where X is a hexadecimal digit. SMB and Kerberos haracter encoding in monitored traffic does not affect SMB and Kerberos analyzer operations. Jolt and FIX haracter encoding in monitored traffic does not affect Jolt and FIX analyzer operations. Generic TP haracter encoding in monitored traffic does not affect generic TP analyzer operations. As a consequence of allowing international character support in monitored traffic, locale-specific characters can also be used in AMD configuration and in names defined in the protocols.xml 17

18 hapter 1 Advanced Diagnostics Server Overview file. If locale-specific characters are used in the configuration files, the files should be saved in UTF-8 encoding. Turning on internationalization support will adversely affect AMD performance. Performance degradation will depend on the nature of the monitored traffic. 18

19 HAPTER 2 Planning and Preparation Whether you are creating a fresh software installation or upgrading an existing installation, the installer will walk you through the installation process. In many scenarios the process will be fully automatic, but you should always review this planning section first to be sure you create a complete and robust installation. Installation and Upgrade Planning hecklist Use this checklist to plan the migration of your ADS installation to release Finished Steps Read the release notes to be sure the installation or upgrade will meet your goals. For more information, see ompare Release Notes to Goals [p. 20]. Inventory your current product versions, server components, databases, and agents deployed. For more information, see Inventory the urrent Deployment [p. 20]. Review the installation guide for the new releases for your products to determine software and hardware requirements, migration prerequisites, and product dependencies. For more information, see System Requirements [p. 23]. Schedule your time. For more information, see Estimate the Installation or Upgrade Duration [p. 21]. Verify that you have licenses for the software. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Install the software. For a fresh install, see Running an Advanced Diagnostics Server Setup in the Data enter Real User Monitoring entral Analysis Server Installation Guide. 19

20 hapter 2 Planning and Preparation Finished Steps For an upgrade, see Running a entral Analysis Server Upgrade in the Data enter Real User Monitoring entral Analysis Server Installation Guide. onfigure Advanced Diagnostics Server. ADS Basic onfiguration Settings [p. 57] describes ADS basic configuration, which has to be performed before the product can function. ompare Release Notes to Goals Whether you are creating a fresh installation or upgrading an existing installation, be sure that you know where you are going. The Release Notes and other documentation are available in the product distribution and online at on the product Documentation page. Review each product's Release Notes and product documentation for major new features added in the release. heck the installation guides for your products for integration dependencies that you need to follow. If you are upgrading, will important features in your current deployment still work after you install the new software? The Release Notes may list features replaced or dropped from previous releases. If you haven't upgraded your deployment over a few releases, it is likely that some functionality or system requirements have changed. heck 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 should be able to find information in the product documentation on how to configure and use the new replacement feature after migration. You should not expect unsupported data or component functionality to be migrated to a newer release. You should determine your options for changed or dropped functionality before starting the migration process. Obtain Licensing After you have a clear migration path to release 12.0, contact ompuware to obtain the necessary licenses for a direct or phased migration. If you are currently up to date with maintenance fees, you can contact ustomer Support to obtain licenses for both back and current releases. If your maintenance has expired, contact your ompuware sales representative. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Inventory the urrent Deployment When you install or upgrade ompuware APM products, you should start with a careful inventory of what you already have. 20

21 hapter 2 Planning and Preparation Determine urrent 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.0, you should first determine what releases you currently have deployed for all of your ompuware APM components. 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 will also help you in discussing installation and upgrade plans with ompuware. Diagram Your Installation While you are determining what release levels your ompuware APM products are on, it is also a good idea to have an inventory of your entire ompuware APM implementation, including deployed management servers, databases, and agents. The quantity of servers and agents, and the platforms they are running on, will be factors in planning. A good practice is to create a diagram of your installation so you are aware of all components and any access issues that may arise. A deployment diagram is often very helpful in explaining your situation when you need assistance from ustomer Support. Identify Latest Hardware and Software Requirements System requirements for all ompuware APM products have evolve as their environments (operating systems, application servers, databases, etc.) evolve. It is therefore possible that your current installation environment will not support the latest release. heck the release 12.0 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 hardware requirements for each solution used prior to migrating. As ompuware APM grows its monitoring abilities, more disk space and memory may be required to process additional data. Minimum specifications are provided in the product's installation guide; ompuware 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 this table to estimate the time to migrate your deployment. Each report server (entral Analysis Server or Advanced Diagnostics Server) must be installed or upgraded by logging into the machine and manually running the installation 21

22 hapter 2 Planning and Preparation 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 (or higher), 11.6.x, or 11.7.x to the current release (12.0), the installer should handle the upgrade automatically. If you are upgrading from an earlier release, you should first upgrade that installation to one of these releases and then use the release 12.0 installer to upgrade to the current release. (This will at least double your upgrade time.) 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). 22

23 HAPTER 3 System Requirements Ensure that your system meets the requirements to run DRUM components. NOTE Satisfying the minimum requirements may not ensure the usability level you require. hoose the most appropriate hardware and system platform to achieve the best performance and optimal operation of your installation. Recommended Hardware for AMDs and Report Servers This section describes the platforms and cards we recommend for AMDs and report servers. IMPORTANT To obtain optimal and reliable performance from your ompuware APM software, ompuware strongly recommends that you use the platforms and cards described in this section. We make no predictions or guarantees about the suitability or performance of any other hardware. ustomers who purchase other hardware may experience performance or compatibility problems. ompuware and isco ompuware is a isco Solutions Technology Integrator and isco Developer Network Solution Provider. ompuware integrates its Application Performance Monitoring solutions with the isco Data enter Business Advantage, WAN Optimization and Application Acceleration, and Network Management and Automation solutions. ompuware leverages these integrations to enable customers to create unique and enhanced application performance management (APM) solutions optimized with isco Solutions to transform their businesses. The ompuware APM standardizes on the isco US hardware, which becomes the "gold standard" for developing and running all data center monitoring components. As part of this partnership, ompuware will OEM and sell US 210 and 460 high performance servers as the preferred integrated platform for the ompuware APM. 23

24 hapter 3 System Requirements 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. AMD recommended configurations Table 1. isco Tier 1 AMD isco US 210 M2 IMPORTANT To maximize performance, open the machine's BIOS configuration and change the PU performance setting to High Throughput. Recommended omponents Platform RAID controller Riser card Slots PUs Memory HDDs Remote Management DVD-ROM Power Supply isco US 210 M2 server LSI 6G MegaRAID i card (RAID 0, 1, 5, 6, 10, 60) 512 MB cache (5x) PIe 2.0 slots: (2x) full-height, full-length and (3x) full-height, half-length x8 PIe slots, all with x16 connectors (2x) Intel Xeon Processor X5670 (12 MB ache, 2.93 GHz) 64 GB RAM (DDR MHz DRAMs) Technology: 6G, 15K RPM, SAS or better apacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. isco Integrated Management ontroller Version: 1.2(1a) Required for installation of operating system and application software. DVD-RW Drive for US 210 M2 Rack Servers 650W power supply, w / added 5A Standby for US 200 for 210 Battery Back-up 24

25 hapter 3 System Requirements Table 2. isco Tier 1 AMD isco US 240 M3 IMPORTANT To maximize performance, open the machine's BIOS configuration and change the PU performance setting to High Throughput. Recommended omponents Platform RAID controller Riser card Slots PUs Memory HDDs Remote Management Power Supply isco US 240 M3 server LSI 6G MegaRAID i card + battery backup (RAID 0, 1, 5, 6, 10, 50, 60) 1GB cache (5x) PIe 3.0 slots: (1x) full-height, half-length X16 slot, (1x) full-height, three quarter-length X16 slot, (2x) full-height, half-length x8 PIe slots, and (1x) half-height, half-length x8 PIe slot (used for disk controller) (2x) Intel Xeon Processor E5-2690, 8 core (20 MB ache, 2.90 GHz) 64 GB RAM (DDR MHz RDIMM/P /Dual Rank Technology: 6G, 15K RPM, SAS or better apacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. isco Integrated Management ontroller (2x) 650W power supply Table 3. isco Tier 2 AMD isco US 460 M2 Recommended omponents Platform RAID controller Riser card Slots PUs Memory isco US 460 M2 LSI 6G MegaRAID i card (RAID 0, 1, 5, 6, 10, 60) 512 MB cache 10x PIe - 1x PI2.0 (x16) ¾ length, 4x PI2.0 (x8) ¾ length, 3x PI2.0 (x4) ½ length, 1x PI1.0 (x4) ½ length, 1x PI1.0 (x4) ¾ length (2x) Intel Xeon Processor E (24 MB cache, 2.67 GHz) 64 GB RAM (DDR MHz DRAMs) 25

26 hapter 3 System Requirements Table 3. isco Tier 2 AMD isco US 460 M2 (continued) Recommended omponents HDDs Remote Management DVD-ROM Power Supply Technology: 6G, 15K RPM, SAS or better apacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. isco Integrated Management ontroller Version: 1.2(1a) (2x) 850W Power supply Unit for -SERIES 460 M1 Battery Back-up Report server recommended configuration Table 4. isco report server isco US 210 M2 Recommended omponents Platform RAID controller Riser card Slots PUs Memory HDDs Remote Management DVD-ROM Power Supply isco US 210 M2 server LSI 6G MegaRAID i card (RAID 0, 1, 5, 6, 10, 60) 512 MB cache (5x) PIe 2.0 Slots: (2x) full-height, full-length and (3x) full-height, half-length x8 PIe slots, all with x16 connectors (2x) Intel Xeon Processor X5670 (12 MB ache, 2.93 GHz) Please refer to Report Server Requirements [p. 31] to select a memory configuration appropriate to your needs. Please refer to Report Server Requirements [p. 31] to select a disk configuration appropriate to your needs. isco Integrated Management ontroller Version: 1.2(1a) Required for installation of operating system and application software. DVD-RW Drive for US 210 M2 Rack Servers 650W power supply, w / added 5A Standby for US 200 for 210 Battery Back-up 26

27 hapter 3 System Requirements Table 5. isco report server isco US 240 M3 IMPORTANT To maximize performance, open the machine's BIOS configuration and change the PU performance setting to High Throughput. Recommended omponents Platform RAID controller Riser card Slots PUs Memory HDDs Remote Management Power Supply isco US 240 M3 server LSI 6G MegaRAID i card + battery backup (RAID 0, 1, 5, 6, 10, 50, 60) 1GB cache (5x) PIe 3.0 slots: (1x) full-height, half-length X16 slot, (1x) full-height, three quarter-length X16 slot, (2x) full-height, half-length x8 PIe slots, and (1x) half-height, half-length x8 PIe slot (used for disk controller) (2x) Intel Xeon Processor E5-2690, 8 core (20 MB ache, 2.90 GHz) Please refer to Report Server Requirements [p. 31] to select a memory configuration appropriate to your needs. Please refer to Report Server Requirements [p. 31] to select a disk configuration appropriate to your needs. isco Integrated Management ontroller (2x) 650W power supply ompatible network cards Use these tables to select NIs and SSL cards for the AMD on recommended platforms. These tables do not apply to report server platforms. 27

28 hapter 3 System Requirements Table 6. NI Support Matrix - 10 GbE = ustom Driver, N = Native Driver, NS = Not Supported Model Part isco 210 M2 Broadcom NetExtreme II N2XX-ABPI02 10 Gigabit AT2 E10G1AT2 X520-LR1 E10G41BFLR X520-SR2 E10G42BFSR 10 Gigabit FX SR Dual Port 1 EXPX9502AFXSR 10 Gigabit FX LR 1 EXPX9501AFXLR 1 ard has been EOL'ed by the manufacturer. 240 M3 460 M1 460 M2 HP DL380 G7 DL380p Gen8 DL580 G7 Dell R710 R720 R900 Minimum Version DRUM 12.0 RHEL 5 or 6 (64 bit) DRUM RHEL 5.5 DRUM RHEL 5.5 DRUM RHEL 5.5 DRUM 10.3 RHEL 5.1 DRUM RHEL

29 hapter 3 System Requirements Table 7. NI Support Matrix - 1 GbE = ustom Driver, N = Native Driver, NS = Not Supported, FT = Field Tested Model Part isco 210 M2 240 M3 460 M1 460 M2 Intel E1G44ETG1P20 N2XX-AIPI02 Broadcom NetExtreme II 5709 Quad Port N2XX-ABPI03 NS Broadcom NetExtreme II 5709 Quad Port N2XX-ABPI03-M3 NS NS N S Pro/1000 PF Quad Port 1 EXPI9404PF NS NS NS NS Pro/1000 PF Dual Port EXPI9402PF Pro/1000 PT Dual Port EXPI9402PT Pro/1000 PT Low Profile Quad Port EXPI9404PTL NS Gigabit ET2 Quad Port E1G44ET2 NS NS HP DL380 G7 DL380p Gen8 DL580 G7 BL460c G7 Dell R710 R720 R900 Minimum Version DRUM 12.0 RHEL 5 or 6 (64 bit) DRUM 12.0 RHEL 5 or 6 (64 bit) DRUM 10.0 SP2 DRUM 10.0 SP1 DRUM 10.0 SP1 DRUM 10.0 SP2 DRUM 12.0 RHEL 5 or 6 (64 bit) 29

30 hapter 3 System Requirements Table 7. NI Support Matrix - 1 GbE (continued) Model Part Gigabit ET Dual Port E1G42ET I340-F4 E1G44HF Gigabit EF Dual Port E1G42EF Pro/1000 MF LX Single Port 1 PWLA8490LX Pro/1000 MF Dual Port PWLA8492MF Pro/1000 MT Dual Port PWLA8492MT Pro/1000 GT Quad Port PWLA8494GT N364m B21 isco 210 M2 NS NS NS NS 240 M3 NS NS NS NS 460 M1 NS NS NS NS 460 M2 NS NS NS NS NS HP DL380 G7 NS NS NS NS DL380p Gen8 DL580 G7 NS NS NS NS BL460c G7, FT Dell R710 R720 R900 Minimum Version DRUM 12.0 RHEL 5 or 6 (64 bit) DRUM 12.0 RHEL 5 or 6 (64 bit) DRUM 12.0 RHEL 5 or 6 (64 bit) DRUM 5.1 DRUM 5.1 DRUM 5.1 DRUM 10.0 SP1 30

31 Table 8. Recommended SSL card configuration for the AMD on recommended platforms Part Number N4033E-6K0 N3023E-6K0 Description and Important Notes nipher nshield 6000e F3, FIPS SSL accelerator card (RoHS)6. Type: low profile and regular slots. In a isco US 210, you must use the standard (full) height bevel option. nipher nshield 6000e F2, FIPS SSL accelerator card (RoHS)6. Type: low profile and regular slots. This card is stocked by and available directly from ompuware. In a isco US 210, you must use the standard (full) height bevel option. Report Server Requirements A report server platform should meet or exceed the following requirements: PUs At least 2x quad core PU (or at least 8 cores in total) working with at least 2 GHz clock. In general, performance improves with higher PU frequencies and core counts. In ompuware's testing, the best performance-to-cost ratio is 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 five lient Access Licenses (ALs). Windows Server Standard Edition is appropriate for installations up to 32 GB RAM; Enterprise Edition is appropriate for installations exceeding 32 GB RAM. Microsoft Windows 2008 R2 (64-bit) Standard or Enterprise Edition (depending on the server memory size) Microsoft Windows 2008 (64-bit) Standard or Enterprise Edition (depending on the server memory size) SQL Server Only Microsoft SQL Server 2005 and SQL Server 2008 are supported. ompuware recommends that you acquire a Microsoft SQL Server Standard Edition license with 5 Server - User lient Access Licenses (ALs). 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 AS, ADS, and RUM onsole users connect through these applications to SQL Server using a web connection (Internet or intranet, depending on the deployment). In other words, ompuware assumes that you are licensing SQL Server only for this deployment of the ompuware software configurations discussed here. If the machine on which you install AS or ADS also co-hosts other software that uses SQL Server, or if you are connecting AS or ADS to a SQL Server installation deployed on another machine, you may need a different licensing arrangement. Examine your total configuration 31

32 hapter 3 System Requirements (including ompuware software and any other software that uses SQL Server) and acquire SQL Server licensing that meets your overall needs. The current need for a single database connection may be expanded in future releases, with other ompuware modules' data being co-hosted by the same SQL Server. Memory and HDDs The memory and hard disk drive (HDD) requirements of your report server depend on the functions assigned to that report server. AS = entral Analysis Server ADS = Advanced Diagnostics Server AS SQL = the AS SQL database ADS SQL = the ADS SQL database RUM onsole Server = the server portion of the RUM onsole software SS = ompuware Security Server Table 9. omponent-specific System Requirements and Recommendations This 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 following table for recommended machine configurations. In the Min. HDD column, RAID specifications refers to: Technology: 6G, 15K RPM, SAS or better apacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. Module Min. RAM Rec. RAM Min. HDD an co-exist with AS 24 GB 32 GB 10 GB AS SQL, RUM onsole Server ADS 24 GB 32 GB 10 GB ADS SQL, RUM onsole Server AS SQL 24 GB 32 GB See RAID specifications above. AS, RUM onsole Server ADS SQL 24 GB 32 GB See RAID specifications above. ADS, RUM onsole Server RUM onsole Server 2 GB 2 GB 1 GB AS, ADS, AS SQL, ADS SQL 32

33 hapter 3 System Requirements Table 9. omponent-specific System Requirements and Recommendations (continued) Module Min. RAM Rec. RAM Min. HDD an co-exist with SS 4 GB 4 GB 800 MB AS, ADS, AS SQL, ADS SQL Table 10. Example Report-server Machine onfigurations 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 in many cases will improve performance. Also, keep in mind that the AS and ADS can never be installed on the same machine. In the HDD column, RAID specifications refers to: Technology: 6G, 15K RPM, SAS or better apacity: 600 GB free space or greater RAID level: Fastest write performance with a customer-accepted level of data protection. RAID 10 recommended. Modules AS + AS SQL database + RUM onsole Server ADS + ADS SQL database + RUM onsole Server AS AS + AS SQL database ADS ADS + ADS SQL database AS SQL + RUM onsole Server ADS SQL + RUM onsole Server RAM 64 GB 64 GB 32 GB 64 GB 32 GB 64 GB 32 GB 32 GB HDD See RAID specifications above. See RAID specifications above. 10 GB See RAID specifications above. 10 GB See RAID specifications above. See RAID specifications above. See RAID specifications above. Recommended Operating System onfiguration for Report Servers Typical preparations for a secure report server deployment require several steps to be performed on the side of the operating system. 33

34 hapter 3 System Requirements 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 DOM. Turn off indexing on all volumes (services). Disable network protocols and bindings: SMB NetBios over TP/IP Disable the following services (if unused): Alerter Application Layer Gateway Service Application Management Automatic updates Background Intelligent Transfer Service (BITS) omputer Browser lipbook Distributed File System Distributed Link Tracking lient 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 D Burning OM Service Indexing Service Intersite Messaging Kerberos Key Distribution enter License Logging Service Messenger Microsoft Search NetMeeting Remote Desktop Sharing Network DDE Network DDE DSDM Network Location Awareness (NLA) Print Spooler Remote Registry Server 34

35 hapter 3 System Requirements SNMP Trap Service SQL Server FullText Search TP/IP NetBIOS Helper Service Telnet Telephony Windows Management Instrumentation Driver Extension 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_LOAL_MAHINE\SYSTEM\urrentontrolSet\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), EnableIMPRedirect, REG_DWORD, 0 DisableIPSourceRouting, REG_DWORD, 2 TcpMaxonnectResponseRetransmissions, REG_DWORD, 2 TcpMaxDataRetransmissions, REG_DWORD, 3 PerformRouterDiscovery, REG_DWORD, 0 TcpMaxPortsExhausted, REG_DWORD, 5 All values given above are hexadecimal. Microsoft SQL Server 2005 Setup Recommendations The following sections provide a brief description of SQL Server 2005 setup for reliable and secure functioning with Advanced Diagnostics Server. NOTE Most of the recommendations listed here may have already been applied if the Agentless Monitoring Device was purchased as a turnkey solution. If only a ompuware software solution was chosen, some of the steps may not be applicable. For more information, see Purchase Options in the Data enter Real User Monitoring Getting Started. The changes must be applied with caution so as not to affect the operation of the SQL Server or Advanced Diagnostics Server. SQL Server 2005 Installation Perform this procedure only if you use SQL Server 2005 as a back end for entral Analysis Server. Prior to SQL Server installation, ensure the following services are enabled (set the start to automatic) and started: OM+ System Application Distributed Transaction oordinator 35

36 hapter 3 System Requirements Then perform the following: 1. Start the installation of SQL Server Select the Server components, tools, Books Online, and samples install option. 2. onfigure installation options. System configuration check may display several warnings about components needed only for Reporting Services. Because Reporting Services are not installed, the following warnings should not cause any problems with SQL Server 2005: IIS Feature Requirement ASP.NET Version Registration Requirement 3. hoose components to install. Select the following components: SQL Server Database Services Workstation components, Books Online, and development tools 4. hoose the instance name. Since it is permissible to use one of many MS SQL Server instances, you are permitted to use any name meaningful to you for each of the instances. 5. Define Service Account. Select Use the built-in system account with Local System as an option. 6. Select the authentication mode. hoose Mixed mode, set sa password to adlex. 7. Define collation settings. Leave default ollation selection: Dictionary order, case insensitive, for use with 1252 haracter set. 8. Disable Error and usage Report Settings. Do not send any data outside your network, clear all options. SQL Server 2005 onfiguration Perform this procedure only if you use SQL Server 2005 as a back end for entral Analysis Server. After installing SQL Server 2005, perform the following configuration steps: 1. reate a new default database file location. Set the directory e:\mssql\data as Database default locations (for Data and Log). 2. Move the tempdb database to the new location. a. Open SQL Server Management Studio and connect to local database with administrative privileges (sa or local machine administrator). In Object Explorer, expand Databases System databases, right-click tempdb, and choose New Query. b. Execute the following query: ALTER DATABASE tempdb MODIFY FILE ( NAME = tempdev, FILENAME = 'e:\mssql\data\tempdb.mdf' ) 36

37 hapter 3 System Requirements ALTER DATABASE tempdb MODIFY FILE ( NAME = templog, FILENAME = 'e:\mssql\data\templog.ldf' ) c. Stop the SQL Server service. d. Move tempdb.mdf and tempdb.ldf from :\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data to e:\mssql\data e. Start the SQL Server Service. f. To verify changes in the database, execute the following query: SELET name, physical_name AS urrentlocation, state_desc FROM sys.master_files WHERE database_id = DB_ID(N'tempdb'); A summary table like the following should appear: Name urrentlocation state_desc tempdev E:\mssql\data\tempdb.mdf ONLINE templog E:\mssql\data\templog.ldf ONLINE g. lose SQL Server Management Studio. 3. Turn off ustomer Experience Improvement Program. 37

38 hapter 3 System Requirements 38

39 HAPTER 4 Installing Advanced Diagnostics Server Use the ompuware APM 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. AUTION When installing or upgrading the ADS, keep in mind that its configuration has to be synchronized with the AS, because the ADS uses configuration settings from the AS. As a consequence, if you had different configuration settings for the ADS and the AS, the ADS settings will be overridden by the AS settings. This is because the AS is the primary reporting engine and the whole configuration for Data enter Real User Monitoring is maintained by the RUM onsole (RUM onsole). An ADS can exist with a AS only in a server farm, where the master server (AS) populates its configuration to all slaves (ADSes or ASes). onfiguring Report Server to Use Private Keys and ertificates You can set up your 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. Use of older versions of the protocol can be configured by setting the configuration property connector.ssl.sslprotocol to SSLv3 or SSLv2, as required. Note that Apache Tomcat default is all, with other acceptable values being SSLv2, SSLv3, TLSv1, and SSLv2+SSLv3. Leaving the connector.ssl.sslprotocol parameter empty causes the Web browser negotiate the version of a secure protocol when connecting to the Web server. For more information on secure connection configuration in Apache Tomcat, refer to 39

40 hapter 4 Installing Advanced Diagnostics Server The report server implementation of SSL uses OpenSSL. This means that encryption, certification, and other operations are handled as defined in OpenSSL. The subdirectory tools\openssl of the report server installation directory contains the OpenSSL tool, which can be used for 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 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.sslertificatefile and connector.ssl.sslertificatekeyfile configuration properties in common.properties. To configure your own encryption keys and register the server in the A (certificate authority) infrastructure, the common.properties file has to be edited manually. Refer to the Apache Tomcat documentation: 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. reate a certificate request as described in (section 3). 3. Pass the certificate to a certification authority for signing. 4. Set configuration properties. 40

41 hapter 4 Installing Advanced Diagnostics Server onfigure the following settings in the common.properties file: Point connector.ssl.ertificatefile to the received certificate file. Point connector.ssl.ertificatefilekey to the generated key. Point connector.ssl.ertificatehainfile 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 A ertificates Following an industry standard practice, ompuware's software installers and device drivers for Microsoft Operating Systems are digitally signed using a commercial ode Signing certificate from a Trusted ertificate Authority (Verisign or Thawte). ode Signing certificates require the use of a primary root and intermediate ertificate Authority (A) certificate to ensure that signed code is fully trusted by users. As a result, ompuware's product installation process requires the presence of a primary root and intermediate A certificate in the target client or server's local computer certificate store. If not present, the primary root and intermediate A 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 ertificate 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 ompuware product installation. To import the required A certificates, perform the following steps: 1. Log in as an administrator on the target installation client or server. 2. Download the primary root A certificate. a. Go to: The thawte root certificates page appears. b. Under Root 1 - Primary Root A, right-click Download Root Now. c. Save the file to the Desktop and change the file name to thawte_primary_root_a.cer. 3. Import the primary root A into the certificate store. a. Double-click thawte_primary_root_a.cer. The ertificate window appears. b. On the General tab, click Install ertificate. The ertificate Import Wizard appears. c. lick Next to continue. d. Select Place all certificates in the following store, and then click Browse. The Select ertificate Store window appears. 41

42 hapter 4 Installing Advanced Diagnostics Server e. Select the Show physical stores check box. f. Select Trusted Root ertification Authorities Local omputer, and then click OK. g. lick Next to continue. Verify that the destination of the certificate is correct. h. lick Finish to complete certificate import. A message indicating that the import was successful appears. 4. Download the intermediate root A certificate. a. Go to: The Download the Thawte Intermediate and ross Root As for ode Signing certificates page appears. b. In the text box under ode Signing Intermediate A, save the text to the Desktop in a file named thawte_intermed_root_a.cer. 5. Import the intermediate root A into the certificate store. a. Double-click thawte_intermed_root_a.cer. The ertificate window appears. b. On the General tab, click Install ertificate. The ertificate Import Wizard appears. c. lick Next to continue. d. Select Place all certificates in the following store, and then click Browse. The Select ertificate Store window appears. e. Select the Show physical stores check box. f. Select Intermediate ertification Authorities Local omputer, and then click OK. g. lick Next to continue. Verify that the destination of the certificate is correct. h. lick Finish to complete certificate import. A message indicating that the import was successful appears. 42

43 HAPTER 5 ADS Upgrade Overview The Advanced Diagnostics Server installation program will detect older versions of the product and offer to upgrade them to the current release, optionally preserving configuration information and traffic monitoring data contained in the Advanced Diagnostics Server database. If you are upgrading your report server from release (or higher), 11.6.x, or 11.7.x to the current release (12.0), the installer should handle the upgrade automatically. If you are upgrading from an earlier release, you should first upgrade that installation to one of these releases and then use the release 12.0 installer to upgrade to the current release. (This will at least double your upgrade time.) If upgrading from an earlier version, some elements of configuration migration may have to be performed manually. This applies, in particular, to the configuration of alerts. AUTION When installing or upgrading the ADS, keep in mind that its configuration has to be synchronized with the AS, because the ADS uses configuration settings from the AS. As a consequence, if you had different configuration settings for the ADS and the AS, the ADS settings will be overridden by the AS settings. This is because the AS is the primary reporting engine and the whole configuration for Data enter Real User Monitoring is maintained by the RUM onsole (RUM onsole). An ADS can exist with a AS only in a server farm, where the master server (AS) populates its configuration to all slaves (ADSes or ASes). Running an Advanced Diagnostics Server Upgrade To upgrade an older version of Advanced Diagnostics Server to the latest version, fulfill the prerequisites and then run the installer for the latest version of ADS. The installer will detect the earlier software and display your upgrade options. 43

44 hapter 5 ADS 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 [p. 77]. Migrating from a 32-bit version to a 64-bit version Direct upgrade from a 32-bit version to a 64-bit version is not supported. If you need to perform such an upgrade, you must save your 32-bit configuration settings manually (this pertains only to new server configuration files added after the 32-bit installation) and uninstall the 32-bit version of the product, while preserving the database. You should then install the 64-bit version as a new installation, not an upgrade, and perform a manual migration of configuration settings. Note that those settings that are maintained in the database will be migrated together with the database. For more information, see Migrating 32-bit ADS to 64-bit ADS [p. 49]. SQL Server restart If you specify a new maximum size for your SQL Server memory, SQL Server must be restarted. If you are using a local SQL Server installation, 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. Database backup Back up the database. For more information, see Backing Up MS SQL Server 2005 AS Databases in the Data enter Real User Monitoring Administration Guide and Backing Up MS SQL Server 2008 AS Databases in the Data enter Real User Monitoring Administration Guide. Upgrading from older releases If you are upgrading your report server from release (or higher), 11.6.x, or 11.7.x to the current release (12.0), the installer should handle the upgrade automatically. If you are upgrading from an earlier release, you should first upgrade that installation to one of these releases and then use the release 12.0 installer to upgrade to the current release. (This will at least double your upgrade time.) NOTE This software requires integration with ompuware Security Server (SS). Be sure that your SS connection is up and reliable throughout report server installation or upgrade. Loss of SS access during the procedure may cause loss of system integrity. To upgrade ADS (to install a newer version over an existing version): 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. Select the installation disc that matches your target machine's operating system. DVD1 Windows DVD2 Linux 44

45 hapter 5 ADS Upgrade Overview DVD3 AIX HPUX Solaris 3. Insert the disc into your computer's DVD drive and wait for the media browser to start. If the media browser does not run automatically, run the setup.exe application on the DVD to start the media browser manually. If you have downloaded the product, go to the equivalent folder in your downloaded copy and run the setup.exe application. 4. On the Data enter Real User Monitoring tab, click Advanced Diagnostics Server (ADS). The default installation is for a 64-bit architecture. If you need a 32-bit installation, find the installer in the ADS directory of the distribution media and run it directly from the file system. IMPORTANT As noted above, upgrade from a 32-bit version to a 64-bit version is not supported. For more information, see Migrating 32-bit ADS to 64-bit ADS [p. 49]. 5. If an earlier release is detected, click Install to install the service pack. IMPORTANT The default installation is for a 64-bit architecture. If you need a 32-bit installation, find the installer in the ADS directory of the distribution media and run it directly from the file system. To upgrade from , you need to exit this installer and run the SP installer directly. The SP installer is located in the SP subdirectory of the ADS directory on the installation media. 6. If the detected amount of physical memory (RAM) on the target machine is lower than the recommended amount, you will see a warning message. lick ancel to abort the installation and perhaps 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. 7. On the Welcome 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, you can click ancel to terminate the installation. 9. If the Security and Reporting Settings screen is displayed, provide all requested ompuware Security Server connection information. You cannot continue until you provide working SS connection information. The Host and Port settings describe the SS connection. Host IP address of the SS host. 45

46 hapter 5 ADS Upgrade Overview Port Port number of the SS host. Default: 4182 The User name and Password settings are displayed only when upgrading from a release prior to You need to provide the credentials of a SS user with administrative privileges when you migrate users from an old installation. User Name Enter the user name for your SS account. Default: adminuser Password Enter the password for your SS account. Default: adminpw 10. If the Product Setup 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 to release 12.0 without changing the current settings, a minimal sequence of setup screens (Database onnection Properties, Database Server Memory, and Installation Options - Summary) with minimal editing options will be displayed for you to review before you start an upgrade to 12.0 without editing the current configuration settings. If you change your mind about any settings, use the Back button to come back to the Product Setup screen and select the other option. If you choose to change settings and upgrade the software to release 12.0, the full set of configuration screens as outlined below will be displayed for you to specify new configuration settings and upgrade to release Report server settings The full set of configuration screens are outlined below. If you chose to upgrade your software without changing settings, most of these screens will not be displayed. 11. On the Installation Folder screen, type or browse for the target installation directory and click Next. NOTE If other ompuware APM products are currently active on the target machine, their services are stopped automatically before ADS is installed. 12. On the Database onnection Properties screen, define the SQL database connection properties. If you chose to upgrade the report server without changing the settings, you have three options for what to do with the current database: 46

47 hapter 5 ADS Upgrade Overview 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. Reset database (retain configuration) This option deletes all traffic monitoring data but preserves database configuration settings. Upgrade This option preserves all traffic monitoring data and database configuration settings. If you chose to upgrade the report server and change the settings, a pop-up window will prompt you to choose whether to Recreate the database (and delete all of your existing data) or Upgrade the existing database (and preserve the data). 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, the 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, you are presented an additional screen on which to specify whether to use all available RAM during database upgrade. Select the check box if you don't need the RAM for other purposes during this upgrade. 14. On the HTTP onnection Info screen, review the HTTP/HTTPS settings and choose whether to open the onnectivity and Security Options screen to edit these settings. 15. On the onnectivity and Security Options screen (displayed if you selected the check box in the previous step), specify the port number on which your report server should be accessible. Host name The host name under which your report server will be recognized is shown on the screen for your information. You will view your reports by accessing this host in your browser. Use HTTP on port The host name should be followed by the port number, if the port number is not 80. Note that this number will be incremented if the default port is unavailable. Use HTTPS (HTTP over SSL) on port If you need to transfer or display the reports securely across the network, you can also specify the HTTPS port number. 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. Note that this number will be incremented if the default port is unavailable. If you select the HTTPS option, the SSL Key Generation Data screen will be displayed. 47

48 hapter 5 ADS Upgrade Overview 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 chose automatic or custom key generation. The SSL Key Generation Data screen enables you to type in the information required to generate a new key. For a custom encryption key, you will have to provide only the password; the other fields will be grayed out. hoosing a custom encryption key requires configuring the server manually, which involves copying both the key and the certificate to the proper directory and modifying the common.properties file. For more information, see onfiguring Report Server to Use Private Keys and ertificates [p. 39]. NOTE If you do not select the Remember the key password check box, you can instead supply the key password on system start-up, 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. 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. Also, remember that not providing a password means that the key will not be encrypted. 17. Review the summary of installation choices. Before the actual upgrade commences, a summary screen displays all of the choices you have made. Review them carefully and, if you need to change any of them, use the Back button to retrace your steps to the appropriate configuration screen. 18. lick Install to commence the actual process of upgrading and pre-configuring software components and defining your database. The amount of time this takes depends on the size of the database and may be anything 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 have been completed, a final post-upgrade information screen is displayed. 19. On the Installation Summary screen, review the installation summary. If you prefer, you can click Show postinstall summary to open a file containing the installation summary. 20. Indicate whether you want to start ADS and then click Finish to exit the installation program. What to Do Next If you have not already obtained and installed a license, do so now. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. 48

49 hapter 5 ADS Upgrade Overview Migrating 32-bit ADS to 64-bit ADS Migrating a 32-bit version of the Advanced Diagnostics Server to a 64-bit version requires some manual configuration. Before You Begin This procedure migrates a 32-bit ADS installation to 64-bit ADS installation within the current release number (12.0). If your 32-bit ADS and database installation is not current (is older than release 12.0), you first need to upgrade your installation to the 32-bit version of the release 12.0 software, and only then can you apply the following migration instructions to migrate it from a 32-bit report server installation to 64-bit report server installation. For more information, see Running a entral Analysis Server Upgrade in the Data enter Real User Monitoring entral Analysis Server Installation Guide. If your 32-bit ADS and database installation is current (is release 12.0), the procedure that follows will enable you to migrate it to a 64-bit release 12.0 installation. You will need to know the administrative user sa database password and the path to the database. Upgrading to a 64-bit version of the ADS requires uninstalling the current 32-bit version and installing the 64-bit version. This process requires a manual transfer of custom settings from one version to the other. The majority of report server configurations and settings are stored in the attached database. Only the configuration files that were created after the default installation need to be transferred manually. These include customer-specific configuration files located in <install_dir>\config folder and custom SQL scripts that are located in the <install_dir>\config\sql\ms\def folder. To migrate a 32-bit instance of the ADS to the 64-bit architecture, perform the following steps: 1. Back up the ADS database. For more information, see Backing Up MS SQL Server 2005 AS Databases in the Data enter Real User Monitoring Administration Guide and Backing Up MS SQL Server 2008 AS Databases in the Data enter Real User Monitoring Administration Guide. 2. reate a temporary repository folder and back up the ADS configuration. Navigate to :\<install_dir>\config and copy all the files and subdirectories to the backup folder. 3. Uninstall the current 32-bit version using Add or Remove Programs in the Start Settings ontrol Panel. 4. Install the ADS 64-bit version using the same installation procedures and information used for the 32-bit version. IMPORTANT When the Database onnection Properties screen is displayed, if you receive a warning message that the database already exists, be sure to click Upgrade or your existing database will be overwritten with an empty database. 49

50 hapter 5 ADS Upgrade Overview 5. Examine and compare the <install_dir>\config\sql\ms\def folder contents with the repository and copy the missing SQL scripts from the repository into the new installation. 6. Examine and compare the <install_dir>\config\locations-*.config folder contents with the repository and copy the modified files from the repository into the new installation. 7. Examine and compare the <install_dir>\config\reporting-groups-*.config folder contents with the repository and copy the modified files from the repository into the new installation. The new 64-bit installation will now contain the configuration read from the upgraded database and all of the custom alert and SQL scripts created in the 32-bit version. What to Do Next Be sure to confirm that the new installation contains the proper settings before removing the temporary repository. Backing Up MS SQL Server 2005 ADS Databases Before You Begin Before proceeding with a backup you need to 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. This can be checked in properties of database (Size - Space available). Your report server is Advanced Diagnostics Server and the default database name is ADS (or delta in older installations). 1. Stop service for the report server. 2. Launch SQL Server Management Studio. From the Start menu, select Start Programs Microsoft SQL Server 2005 SQL Server Management Studio. 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, navigate to 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 the Remove button. 7. lick Add to add a new backup destination. 8. Specify the path and name of the file that will hold the database backup and click OK. 9. Navigate to the Options page and select Overwrite all existing backup sets. 10. lick OK to start the backup process. The database will now be backed up. 11. After the backup is complete, you can restart service for the report server. 50

51 hapter 5 ADS Upgrade Overview 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. This can be checked in properties of the database (Size - Space available). Your report server is Advanced Diagnostics Server and the default database name is ADS (or delta in older installations). 1. Stop service for the report server. 2. 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 will prompt you for your user name and password 4. In the Object Explorer, on the left side of the screen, navigate to 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 the Remove button. 7. lick Add to add a new backup destination. 8. Specify path and name of the file that will hold the database backup and click OK. 9. Navigate to the Options page and select Overwrite all existing backup sets. 10. lick OK to start the backup process. The database will now be backed up. 11. After the backup is complete, you can restart service for the report server. 51

52 hapter 5 ADS Upgrade Overview 52

53 HAPTER 6 Uninstalling the Report Server You can uninstall ADS through the Windows Add or Remove Programs control panel. To uninstall your ADS: 1. In Windows, open Start ontrol Panel. 2. lick Uninstall a program. 3. Select ompuware Advanced Diagnostics Server in the list of installed programs and click Uninstall/hange above the list. Alternative access methods: Double-click the product name. Right-click the product name and select Uninstall/hange. 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. On the Uninstall Options - Summary screen, click Uninstall. 7. Re-start the system. 8. If you previously installed ADS and AS 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 AS, 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. 53

54 hapter 6 Uninstalling the Report Server 54

55 HAPTER 7 Logging in to the Report Server To connect to your report server, enter the server address in your browser. After the initial installation, only the adminuser account is active and requires its default password adminpw. This lets you perform basic configuration tasks such as setting up business units (applications and transactions). You should configure your own adminuser password as one of the first actions you perform on the server. You should then define additional users. Access the server as an administrator only for configuration purposes. For more information, see Adding a User in the Data enter Real User Monitoring Administration Guide. For information on recommended browsers, see Supported Browsers and onnectivity [p. 14]. 55

56 hapter 7 Logging in to the Report Server 56

57 HAPTER 8 ADS Basic onfiguration Settings When you use the Advanced Diagnostics Server (ADS) for the first time, you are asked to specify basic configuration options that must be specified before the ADS starts to function. You must have administrative privileges to make these settings. ADS can be configured in two modes referred to as small Web site and large Web site. The choice of model impacts on how quickly your database will grow and thus how quickly it will affect report performance. The difference from the reporting point of view is mostly in greater availability of low-level hit details data (used mostly to compose load sequence charts) in the small web site mode. In the large web site mode, these details are accessible for shorter retention times and it takes longer to display them. However, this allows us to store five times more pages in the ADS database. TIP You should use the large web site model when page load volume is high and if your main objective is to use fault domain isolation or sequence transaction reporting. However, do NOT use this mode even if the page load volume is high if your main objective is to have fast hit-level detail reports for more than the last few hours. You should also consider introducing data filtering to further limit the analyzed data to only those transactions and URLs which are most significant. Figure 1. ADS scalability settings screen 57

58 hapter 8 ADS Basic onfiguration Settings Small Web site If your main requirement is to have a troubleshooting server with all-details drill-down reports from AS (especially drill-down reports from single user activity reports to load sequence charts) you can find that the data availability limitations or report performance are unacceptable in the large website mode. Using this scalability mode, the ADS records each individual page and each individual page hit in the database, so hit-level information can be used for planning purposes and historical analysis. A disadvantage of this solution is that the hit-level database affects the whole ADS database size. Additionally, since report response time influences ADS capacity, the capacity drops down and it is affected by the response time of hit-level reports. In practice, it means about 2M pages (approximately 10M hits) per day. When you select Small Web site, you can collect details about a small number of page loads per day: approximately 2 million on Tier 1 equipment. Page Elements When you select Small Web site, Page Elements are stored in a database. 2 Page Headers By default, page headers are stored on the AMD. To store all page headers in the database, select Store page headers in DB. This will increase the size of the database (approximately 6 to 7 times larger than the original size). NOTE Storing page headers on the AMD introduces certain limitations to the Page Elements data view. If header data is stored on the AMD, and if you use page header-related dimensions in your report, you also have to apply an Operation ID or Hit ID filter in this report. Page header-related dimensions include Request header, Request parameters (from URL), POST data, POST data (raw) and Request cookie in the HTTP request section, and Response header, Response cookie in HTTP response section. The data daily storage default limit for a small Web site is 2 million pages per day. By default, data is still written to the database if the daily storage limit is exceeded, and only an alert is issued. However, this behavior, as well as the limit itself, can be changed by a user with administrative privileges. For more information, see ADS Scalability-Related onfiguration Properties [p. 60].. Large Web site The large web site mode is worth considering if your main requirement in having ADS installed is not to access low level granularity data per every hit, but you are mostly interested in sequence transactions or fault domain isolation. Using this scalability mode, the ADS does not record 2 For XML and SOAP, Page Elements data is identical to Page Analysis data, so, to avoid unnecessarily keeping the duplicates in the database, a VDATA_FILTER_XMLSOAP filter is set to true by default. Keeping this filter set to true saves disk space but, because the XML and SOAP entries are filtered out, it makes reporting on the Page Elements level (elements or headers) impossible. To change the value of VDATA_FILTER_XMLSOAP property in userpropertiesadmin, type in the Web browser's Address bar and press [Enter], change the filter's property value, and click Set value to accept the change. To access this screen, you need to have administrative privileges for the report server. 58

59 hapter 8 ADS Basic onfiguration Settings per-http-hit information, which reduces the volume of information kept in the SQL database to about 10M page loads per day. Keeping only per-page data, however, results in limited access to the HTTP hit information. Whenever you request information on the analyzed page loads, the data is read directly from AMDs. This option makes it possible to view load sequence charts for an individual page load, but does not allow for aggregation of the information for more than one page load. When you select Large Web site, you can collect aggregated information about a large number of page loads per day, approximately 10 million on Tier 1 equipment. The efficiency of Tier 2 is from 30% to 50% higher than that of Tier 1. The data daily storage default limit for a large Web site is 10 million pages per day. By default, data is still written to the database if the daily storage limit is exceeded, and only an alert is issued. However, this behavior, as well as the limit itself, can be changed by a user with administrative privileges. For more information, see ADS Scalability-Related onfiguration Properties [p. 60]. Page Elements The Page Elements data view is limited in its report generation capability by the fact that traffic monitoring data is stored on the AMDs and not in the report server's database. 2 Page Headers Page header data is stored on the AMDs. (This is mandatory for large Web sites.) NOTE Because of Page Elements view limitations resulting from storing page headers on the AMD, if you use page header-related dimensions on a report, you must also filter report data by Operation ID. Page header-related dimensions include including Request header, Request parameters (from URL), POST data, POST data (raw) and Request cookie in the HTTP request section, and Response header, Response cookie in HTTP response section. If no page header-related dimensions are used, you can choose to filter the report either by Operation ID or, provided the report interval limit is equal to or less than one hour, by User name. Data aggregation performed for large Web site mode does not affect the accuracy of the predefined reports, but it may influence reports you create using the DMI report generation tool. The following ADS reports are not available in large Web site mode: Page Design Problem Overview Largest Page Elements Most Popular Page Elements The following ADS reports are unavailable when accessed from AS: Load Sequence Stepchart HTTP Response by Page Element 59

60 hapter 8 ADS Basic onfiguration Settings Modifying ADS Basic onfiguration Settings After the ADS has been accessed for the first time and configured, the basic configuration screen does not appear automatically when the server is started, but you can open it as needed through menu option Settings Advanced Diagnostics Server Scalability Settings. AUTION Selecting the Store page headers in DB check box under Small Web site will increase the size of the database required for data storage. If database size is of concern, it is best to leave this setting as default (not selected). The scalability settings do not affect historical data, and you do not need to purge the report server database when changing the scalability settings. However, note that the collected data can vary depending on the scalability configuration. For example, in the large Web site mode, client IP addresses and user names are not stored. This means that if you change the settings to the small Web site mode, this information will not appear on the reports covering older data, that is, the period of time when large Web site was selected. ADS Scalability-Related onfiguration Properties If you have administrative privileges, you can modify the default configurations described in ADS Basic onfiguration Settings [p. 57] using options on the User Properties screen. Note that because there are no specific issues related to database complexity, the most important sizing parameter for ADS is the number of operations per day such as the number of page loads per day. Note at the same time that because it is mainly the small database size that ensures good system response time and performance the theoretical limit of the number of operations stored by ADS can be exceeded, if you are willing to accept some degradation of system performance and bigger database size. If this is indeed acceptable, you can reconfigure ADS and increase the limit by a small fraction, after which you should verify that the effects of this on system performance are not too great. To access this screen, in the Web browser's Address bar, type: onfigurable properties include: FDI_SAVE_ONLY_SLOW_PAGES When this is set to TRUE, the server will store only slow pages in the database. FV_THR_SMALL_SITE Determines the daily storage limit for small Web site mode, which by default is 2 million pages per day. FV_THR_LARGE_SITE Determines the daily storage limit for large Web site mode, which by default is 10 million pages per day. FV_THR_APPLY_PAGES_LIMIT When this is set to 1, data is not written to the database if the daily storage limit is exceeded. 60

61 hapter 8 ADS Basic onfiguration Settings FDI_ADD_LIENT_TO_AGGR When this is set to TRUE, client information (client IP, user name, tier client IP) is added to aggregation. Figure 2. Warning message showing exceeded limits for the number of processed operations onfiguring Other ADS Settings For details on how to set all of the other configuration options supported by the Advanced Diagnostics Server (ADS), please refer to Data enter Real User Monitoring System Administration Manual. Sections referring exclusively to Advanced Diagnostics Server are marked (ADS Only) ; sections referring to all of the Data enter Real User Monitoring report servers, including Advanced Diagnostics Server, have no applicability annotations in titles. 61

62 hapter 8 ADS Basic onfiguration Settings 62

63 HAPTER 9 hanging ADS Settings Defined During Installation You can use the Windows ontrol Panel to change some of the parameters you set during ADS configuration. Note that each of the listed tasks must be performed when the ADS is turned off. If the ADS is running when you start a task, the setup program will warn you that it needs to shut down ADS service before you can make a configuration change. lick Next to allow the service to stop so the requested configuration screen can be accessed. hanging the HTTP and SSL Server Settings on ADS After you have installed the ADS, you can change the HTTP and SSL settings through the Windows Add or Remove Programs control panel. 1. In Windows, open Start ontrol Panel. 2. lick Uninstall a program. 3. Select ompuware Advanced Diagnostics Server in the list of installed programs and click Uninstall/hange above the list. Alternative access methods: Double-click the product name. Right-click the product name and select Uninstall/hange. The Welcome screen presents you with options for the installed software. 4. Select hange HTTP and SSL server Settings 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 onnectivity and Security Options screen (displayed if you selected the check box in the previous step), specify the port number on which your report server should be accessible. 63

64 hapter 9 hanging ADS Settings Defined During Installation Host name The host name under which your report server will be recognized is shown on the screen for your information. You will view your reports by accessing this host in your browser. Use HTTP on port The host name should be followed by the port number, if the port number is not 80. Note that this number will be incremented if the default port is unavailable. Use HTTPS (HTTP over SSL) on port If you need to transfer or display the reports securely across the network, you can also specify the HTTPS port number. 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. Note that this number will be incremented if the default port is unavailable. If you select the HTTPS option, the SSL Key Generation Data screen will be displayed. 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 chose automatic or custom key generation. The SSL Key Generation Data screen enables you to type in the information required to generate a new key. For a custom encryption key, you will have to provide only the password; the other fields will be grayed out. hoosing a custom encryption key requires configuring the server manually, which involves copying both the key and the certificate to the proper directory and modifying the common.properties file. For more information, see onfiguring Report Server to Use Private Keys and ertificates [p. 39]. NOTE If you do not select the Remember the key password check box, you can instead supply the key password on system start-up, 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. 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. Also, remember that not providing a password means that the key will not be encrypted. 8. lick hange. 64

65 hanging the Database User Password on ADS After you have installed the ADS, 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 ontrol Panel. 2. lick Uninstall a program. 3. Select ompuware Advanced Diagnostics Server in the list of installed programs and click Uninstall/hange above the list. Alternative access methods: Double-click the product name. Right-click the product name and select Uninstall/hange. The Welcome screen presents you with options for the installed software. 4. Select hange 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. lick hange. hapter 9 hanging ADS Settings Defined During Installation 65

66 hapter 9 hanging ADS Settings Defined During Installation 66

67 HAPTER 10 Licensing Data enter Real User Monitoring omponents ompuware APM component licensing is managed by a system called ompuware Distributed License Management (DLM). DLM uses the following components to help manage product licensing: License File DLM authorizes you to use ompuware 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. ompuware License Service (cpwr.exe) An application (invoked by the DLM application or executed from the command line) that manages and services requests for the licenses of your ompuware products. The ompuware License Service application can be installed on Windows and UNIX platforms. In many cases, you should co-locate the ompuware License Service with the server-based components of one of the ompuware products you are installing. License types DLM offers several different types of licenses as described in the table below. Each ompuware product may support different combinations of these license types. Table 11. DLM license types License type Trial License Description A trial license ships with some ompuware products. This license type lets you evaluate the product. The default evaluation period is 30 days, after which time the trial license expires. Obtained by... Installing the product. 67

68 hapter 10 Licensing Data enter Real User Monitoring omponents Table 11. DLM license types (continued) License type Temporary License Description A temporary license has a fixed expiration date from the time that it is installed on your system. You must run the DLM to install this license type. Obtained by... Requesting the license from ompuware, not shipped with the product. Permanent Node-Locked License A client-based single-user license that does not have an expiration date. A Node-Locked license is identified by the HOSTID keyword in the license file and must always run on the same machine (same node, and hence the license is node-locked ) as it was originally installed. If you use a Permanent Node-Locked License and you change workstations or NI cards, you must contact ompuware to obtain a new Permanent Node-Locked License for the new hardware. Running the DLM to determine your node identifier and providing the information to ompuware. ompuware will you a license file based on the node identifier. ompuware APM licenses will only recognize the first NI address identified during system startup. If you have a multi-homed system, you will need to obtain a license based on your disk serial number. Permanent oncurrent (Floating) License Borrowed License A license arrangement under which you can purchase a specific number of licenses without assigning them to a particular workstation. When all available licenses are checked out from the License Manager, no additional users can run the product until a license is checked back in. This type of license has a license file with SERVER and DAEMON lines. A license that the user checks out of the borrow proxy server and later checks back in. This enables the user to detach from the network and still use the ompuware product. Running the DLM on the server for the License Manager to obtain the node identifier and providing the information to ompuware. The License Manager software and the license files must be installed on the server. Use the DLM from the client machines to connect them to the License Manager. License must be requested from ompuware. Requires the Borrow License lient application to be installed in the same directory as the DLM. 68

69 APPENDIX A ompuware Security Server Management Every report server (AS or ADS) and RUM onsole installation must be integrated with a ompuware Security Server (SS). Install the ompuware Security Server (SS) Before You Begin System requirements for a standalone implementation: 64-bit Windows 2008 server is the recommended operating system. You can also install on 64-bit Solaris 9.x or above or 64-bit Red Hat Enterprise 4.x or above. At least 4 GB RAM. At least 800 MB hard disk space. You must have a SQL Server or Oracle database host available prior to installing. If creating the database in advance, configure 2 GB for initial size, with autogrowth of 200 MB for data and 200 MB for log. A ompuware Security Server (SS) is required for a Data enter Real User Monitoring or Business Service Manager implementation. If you have both products, you only need one SS do not install a second version. It is recommended that you install the SS as part of a server component installation, but if needed, you can perform a standalone installation. The SS is a critical component and should be installed on a high-availability server. For DRUM, it is recommended that you install SS on the same server as the entral Analysis Server. For BSM, you should install the SS on the same server as the Service Model Server. 1. Select the installation disc that matches your target machine's operating system. DVD1 Windows DVD2 Linux DVD3 AIX HPUX Solaris 2. Insert the disc into your computer's DVD drive and wait for the media browser to start. 69

70 Appendix A ompuware Security Server Management If the media browser does not run automatically, run the setup.exe application on the DVD to start the media browser manually. If you have downloaded the product, go to the equivalent folder in your downloaded copy and run the setup.exe application. 3. Go the Utilities tab and click ompuware ommon omponents. The installer will prepare to install files. 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 ancel 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 Administator Account page, enter the user name and password for a system administrator account to use with SS and the integrating products. 8. In the Security Database onfiguration screen, enter information to create a database, or identify an existing SS database: Host Name Specify the database host machine. Port The default port is entered automatically. hange the port number if you have a conflict. 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 onnection. Enter the login information: User Name Provide the user name for logging on to the specified database. Password Provide the password for the specified user name. lick Next to proceed. 9. In the Database Name screen, the default SS database name is displayed. You can change the name, or enter the name of an existing database if created in advance. lick Next. 70

71 Appendix A ompuware Security Server Management 10. On the Pre-Installation Summary page, review the configuration information carefully to ensure that you have selected the options you want to install and, if everything is correct, click Install to begin installation. If you need 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. NOTE Depending on the options you chose, this may take considerable time. 11. When the installation is finished, the Install omplete page will notify you of the general installation status. Review the installation status message and click Done to exit the installer. What to Do Next To access the SS interface, go to Start button and select All Programs ompuware ommon omponents ompuware Security. For more information, see User Access and Security Overview in the Data enter Real User Monitoring Administration Guide. Moving the Location of the Security Server After an initial installation of the ompuware Security Server (SS), you can relocate it to another location if needed. Only an experienced system administrator should perform this procedure, as errors could prevent users from accessing the system. If the initial SS was already configured, and contained data, ompuware recommends that you retain the existing SS database and connect to it during the installation of a new SS. 1. Install a new SS, using either the standalone SS installer, or as part of a new product installation. For more information, see Install the ompuware Security Server (SS) [p. 69]. 2. Stop the services of all components integrated with the initial SS implementation (for example, RUM onsole, AS, Enterprise Portal). 3. On those systems, navigate to the css.dat file. On Windows 7\2008 servers, you can find css.dat in the ProgramData\ompuware\Security lient\ folder. 4. Open the file with a text editor. 5. Edit <csshost> and <cssport> parameters to reflect the location and port for the new SS installed in Step 1 [p. 71]. Save the file. 6. Start the services on those machines. 71

72 Appendix A ompuware Security Server Management 72

73 APPENDIX B Integrating DRUM with the Enterprise Portal You can extend your reporting capabilities by adding the Enterprise Portal to your DRUM implementation. The following is an overview of the integration process to get quick value from the Portal: The Portal's new Application Health reports are designed specifically to support entral Analysis Server (AS) release 12.0 and later. omplete your DRUM 12.0 implementation, or upgrade to 12.0, before integrating with the Portal. Once you have DRUM at release 12.0, you can install the Portal on the same machine you installed AS. The system requirements for the Portal are similar to AS if you have sufficient resources on that machine. For more information, see Installing the Enterprise Portal [p. 74]. NOTE If you have a previous release of Business Service Manager, and plan on upgrading the dashboards to the Enterprise Portal, you should install the Portal on the same machine as the BSM release 11.5 or 11.7 dashboards to migrate dashboards and user accounts to the new release. See the Business Service Manager Installation Guide for migration instructions. The Portal will integrate with the ompuware Security Server that was implemented with the DRUM 12.0 release. You do not have to install a second instance of SS; during the Portal installation, connect to the existing SS. The user accounts and user groups you have for DRUM also will have Portal access. After installing the Portal, the first step is to connect the Portal to your AS. In the Portal, go to the Report Server Manager to configure your connection. 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 Docs\ folder, or installed at Portal_Home\Program Files\ompuware\Enterprise Portal\Documentation\. 73

74 Appendix B Integrating DRUM with the Enterprise Portal Installing the Enterprise Portal Before You Begin Ensure that you have a database host available, or a supported database already available. 1. Select the installation disc that matches your target machine's operating system. DVD1 Windows DVD2 Linux DVD3 AIX HPUX Solaris 2. Insert the disc into your computer's DVD drive and wait for the media browser to start. If the media browser does not run automatically, run the setup.exe application on the DVD to start the media browser manually. If you have downloaded the product, go to the equivalent folder in your downloaded copy and run the setup.exe application. 3. On the Real User Monitoring tab, select Enterprise Portal. The installation program will prepare to install. 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 ancel 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 onfiguration screen, identify where an existing ompuware Security Server (SS) is installed, or click Install SS locally. Enter a user name and password for an administrator account. 8. On the Database onfiguration 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 Enterprise Portal: Host Name Specify the database host machine. Port The default port is entered automatically. hange the port number if you have a conflict. 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. 74

75 Appendix B Integrating DRUM with the Enterprise Portal 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 onnection. Enter the login information: User Name Provide the user name for logging on to the specified database. Password Provide the password for the specified user name. 9. In the Database Name screen, the default database names for the Enterprise Portal and ompuware 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. 10. On the Pre-Installation Summary page, review the configuration information carefully to ensure that you have selected the options you want to install and, if everything is correct, click Install to begin installation. If you need 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. NOTE Depending on the options you chose, this may take considerable time. 11. When the installation is finished, the Install omplete page will notify you of the general installation status. Review the installation status message and click Done to exit the installer. What to Do Next To open the Portal, go to Start All Programs ompuware Enterprise Portal After you log in, the Portal home page will open. You will need to configure a report server. For entral Analysis Server, go to Administration Manage Report Server to connect. For BSM, go to Administration ontrol Panel Integrations. 75

76 Appendix B Integrating DRUM with the Enterprise Portal 76

77 APPENDIX Providing Failover for Report Server You can provide high availability and backup of reports using two solutions: a Data enter Real User Monitoring built-in or Windows Server feature. The choice of the failover mechanism depends on whether you already have an existing Data enter Real User Monitoring setup, what hardware and software platforms are deployed in your data center. Figure 3. Decision making on the choice of failover solution Start Deploy Windows Server 2008 Yes New installation? No Operating system? Microsoft lustering Feature Operating system? Windows Server 2003 AS server cluster Process complete Windows Server 2008 AS server cluster supported up to 12.0 Do you have required hardware for Microsoft lustering Feature No AS server cluster Process complete AS server cluster supported up to 12.0 Yes Microsoft lustering Feature Process complete It is recommended that for all new Data enter Real User Monitoring installations you use Windows Server 2008 lustering Feature. If you are upgrading older versions of failover clusters 77

78 Appendix Providing Failover for Report Server either consider migration to the operating system based solution or continue using the AS-based server cluster. Failover lustering on Windows Server 2008 Failover lustering Feature is built in Windows Server Enterprise or Datacenter editions. You can use this operating system built-in mechanism provided by Microsoft to ascertain high availability and backup for entral Analysis Server or Advanced Diagnostics Server. This is the recommended scenario when you need a stand by server to provide instant disaster counteraction. How the failover cluster works Two hosts working in the cluster provide report redundancy based on a single report server database. Once the main cluster machine fails the other instantly takes over. Each of the report server installations use shared configuration and logs. Which host in the cluster is currently operational is transparent to the report user or configuration tools. Both machines, and thus report servers, are available with the same network address. 78

79 Appendix Providing Failover for Report Server Figure 4. Failover lustering structure Network Primary AMD Secondary AMD Shared storage (cluster witness disk) Shared storage (AS installation) Shared storage (SQL Server installation) SQL Server A SQL Server B AS A AS B RUM onsole User ommunication flow: Primary Failover Heartbeat 79

80 Appendix Providing Failover for Report Server What to do next To learn about prerequisites for setting up a failover cluster, see Failover lustering Prerequisites [p. 80]. To learn how to install report server within the cluster, see Failover lustering Installation Process [p. 81]. To learn how to migrate existing report server installation to failover cluster, see Migrating Existing Report Server Installation to Provide High Availability Using lustering Feature [p. 96]. To learn how to migrate an older version of report server failover cluster to Windows based solution, see Migrating Report Server Failover luster to Provide High Availability Using lustering Feature [p. 100]. Failover lustering Prerequisites Before you start setting up a high availability environment providing reports ensure the operating system for the report server supports all required features, your hardware is compliant to the clustering conditions, you have the right type of storage for installation and can provide remote database back-end for the report server. For the list of detailed hardware and software requirements refer to Failover luster Requirements ( To be able to deploy failover configuration for the report server you need to satisfy at least the following conditions: Two separate machines to host report server installation. It is highly recommended to use machines matching configuration and components. Each machine needs at least two separate network connections: for data exchange and server status checking (known as heartbeat). Ensure you have sufficient number of licenses for operating system variant supporting failover clustering. The Failover lustering feature is included only in Windows Server 2008 R2 Enterprise and Windows Server 2008 R2 Datacenter. The servers for a failover cluster must run the same version of Windows Server 2008 (including patches and service packs) also matching hardware version (64-bit). Servers working as cluster nodes need to be part of the same Active Directory domain. lustering feature does not work outside domain. The suggested role is member server. Shared storage to be used by all machines working in a cluster. The number of disks you need depends whether you also deploy SQL Server in a clustering environment. When you want only report server high availability the number of shared disks is two. When you want report server and SQL server high availability the number of shared disks is three. Ensure each server working as cluster node has the same drive letter assigned to the storage. Ensure you have sufficient permissions to administer the cluster. You must be logged on to the domain with an account that has administrator rights and permissions on all servers in the cluster. You do not need a domain administrator account, but the account must be in the Administrators group on each individual server within the cluster. 80

81 Appendix Providing Failover for Report Server External software like ompuware Security Server or RUM onsole must be installed on machines working outside the cluster configuration. Failover lustering Installation Process The cluster is installed on two machines referred as Node A and Node B. Preliminary tasks 1. Verify prerequisites for building a failover cluster. For more information, see Failover lustering Prerequisites [p. 80]. 2. Ensure each of the hosts designed to work as cluster nodes belongs to the same Active Directory domain. 3. Select Active Directory domain user to be used as cluster user. Ensure the user is added to the Administrators group on each node of the cluster. 4. Use domain account to login into nodes A and B Setting up failover cluster 5. Enable Failover lustering feature on all hosts working within the cluster and perform other clustering-related steps. Go to Server Manager to find tools necessary for performing the following steps. a. Install Failover lustering feature. For more information, see Install the Failover lustering Feature ( b. onnect storage and networks for the cluster. For more information, see Prepare Hardware Before Validating a Failover luster ( c. Validate configuration. For more information, see Validate a New or Existing Failover luster ( d. reate a cluster. For more information, see reate a New Failover luster ( Ensure to include all servers designated to be cluster nodes (Node A and Node B) when performing the Select servers step. Setting up SQL Server Before you begin actual installation and setup of nodes hosting report server installation you must prepare SQL Server to store report server's runtime data. It is not recommended that a standalone SQL Server be installed on one of the cluster nodes. hoose either a remote SQL Server installation to store report server database or deploy SQL Server failover cluster using nodes A and B or remote failover cluster. 6. Optional: Install SQL Server cluster on nodes A and B. 81

82 Appendix Providing Failover for Report Server For more information, see Getting Started with SQL Server 2008 R2 Failover lustering ( SQL Server vendor offers two solutions: Integrated failover cluster install with Add Node and Advanced/Enterprise installation. hoose the most suitable solution for you and proceed according to SQL Server manual. If you decide to implement this solution note the failover cluster client access point name and address. This information is required later as the report server installation step. Ensure also that the databases are set to be located on the external storage shared by SQL Server cluster nodes. This location will also need to be provided during AS or ADS installation. Setting up report server on Node A The following steps need to be performed on both machines Node A and Node B as a sequence. Simultaneous installations are not possible since each process depends on the software being installed on a shared storage and shared database access. 7. Install the report server on Node A choosing the remote storage as installation home. For more information, see Running a Report Server Setup on a Failover Node [p. 83]. Note that you should perform installations on each node sequentially in the order suggested. This will ensure report server files and database coherence. To preserve data, always instruct the installer to upgrade an existing report server database. 8. hange default settings for report server services. The system services supporting report server operation are controlled by the Server luster Manager. For more information, see hanging Default Report Server Service Settings on a Failover Node [p. 89]. 9. Verify newly installed report server operation. Try logging to the report server as user with administrative rights to see if it is up and running. Do not change any settings yet. 10. onfigure Distributed License Management on Node A. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Ensure the license file is located on the shared storage where report server files are located so that each running report server instance can access the licenses without blocking the cluster operation. 11. Stop cluster service on Node A. Use Failover luster Manager to stop the service on a selected node. Expand Nodes, right-click the node you want to stop and click Stop luster Service in the More Actions submenu. As a result Node B will be able to access shared storage and the cluster service will be started. Setting up Node B 12. Install the report server on Node B choosing the remote storage as installation home. For more information, see Running a Report Server Setup on a Failover Node [p. 83]. 82

83 Appendix Providing Failover for Report Server To preserve data always instruct the installer to upgrade an existing report server database. 13. hange default settings for report server services. The system services supporting report server operation are controlled by the Server luster Manager. For more information, see hanging Default Report Server Service Settings on a Failover Node [p. 89]. 14. Verify newly installed report server operation. Try logging to the report server as user with administrative rights to see if it is up and running. Do not change any settings yet. 15. onfigure Distributed License Management on Node B. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Ensure the license file is located on the shared storage where report server files are located so that each running report server instance can access the licenses without blocking the cluster operation. 16. Stop the report server on Node B. Finishing failover cluster configuration 17. Ensure failover services is running on both nodes. Use Failover luster Manager to start the service on a selected node. Expand Nodes, right-click the node you want to start and click Start luster Service in the More Actions submenu. 18. onfigure AS or ADS service for high availability For more information, see Defining High Availability for Report Server Service [p. 90]. onfiguring Data enter Real User Monitoring 19. Add the report server to the RUM onsole. To add the report server use the IP address assigned to the client access point. To find out the address of the failover cluster, see Step 8 [p. 95]. What to Do Next After confirming the report server works and adding it to the RUM onsole you can proceed with other deployment tasks like adding AMDs to the server and other configuration tasks. Running a Report Server Setup on a Failover Node Before You Begin SQL Server Restart If you specify a new maximum size for your SQL Server memory, SQL Server must be restarted. If you are using a local SQL Server installation, 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. 83

84 Appendix Providing Failover for Report Server Order of omponent Installation RUM onsole Before installing ADS or AS, you should install RUM onsole on another machine with network access to this machine. ompuware Security Server When you install RUM onsole (above), you will have to connect to a local or remote installation of ompuware Security Server (SS). If you don't already have SS installed somewhere, you can install it during RUM onsole installation. When you install ADS or AS, if the report server installer cannot detect a SS installation on the local machine, you must provide the address of a remote SS installation before the ADS or AS installation can continue. You should have only one installation of SS for all DRUM components. If you have already installed SS during installation of any other component, just provide connection details during report server installation. NOTE This software requires integration with ompuware Security Server (SS). Be sure that your SS connection is up and reliable throughout report server installation or upgrade. Loss of SS access during the procedure may cause loss of system integrity. To install the report server: 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. Select the appropriate installation disc for the target machine: DVD1 Windows. 3. Insert the disc into your computer's DVD drive and wait for the media browser to start. If the media browser does not run automatically, run the setup.exe application on the DVD to start the media browser manually. If you have downloaded the product, go to the equivalent folder in your downloaded copy and run the setup.exe application. 4. If you want to integrate Advanced Diagnostics Server or entral Analysis Server with the Enterprise Portal (Portal), install the Portal first. The Enterprise Portal installer is available on the same installation media as the report server installer. 5. On the Data enter Real User Monitoring tab, click Advanced Diagnostics Server (ADS) or entral Analysis Server (AS). The default installation is for a 64-bit architecture. If you need a 32-bit installation, find the installer in the ADS or entral Analysis Server directory of the distribution media and run it directly from the file system. 6. If the detected amount of physical memory (RAM) on the target machine is lower than the recommended amount, a warning message is displayed. 84

85 Appendix Providing Failover for Report Server To function properly, the report server should be installed on a machine with at least the minimum RAM as stated in Recommended Hardware onfigurations. For details, see lick ancel to abort the installation and perhaps 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. 7. On the Welcome 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, you can click ancel to terminate the installation. 9. If the Security and Reporting Settings screen is displayed, provide all requested ompuware Security Server connection information. You cannot continue until you provide working SS connection information. The Host and Port settings describe the SS connection. Host IP address of the SS host. Port Port number of the SS host. Default: 4182 The User name and Password settings are displayed only when upgrading from a release prior to You need to provide the credentials of a SS user with administrative privileges when you migrate users from an old installation. User Name Enter the user name for your SS account. Default: adminuser Password Enter the password for your SS account. Default: adminpw IMPORTANT ompuware Security Server connection details are kept outside the shared storage, therefore you need to maintain that information separately on each node remembering to always synchronize it. After the product is installed it is impossible to modify SS connection details. 10. If the Product Setup screen is displayed (because a previous installation has been detected), abort installer, remove the existing installation and restart the installer. 11. On the Installation Folder screen, type or browse for the target installation directory and click Next. 85

86 Appendix Providing Failover for Report Server Ensure to direct the installer to the remote storage that will be later used by each node within the failover cluster. 12. On the Database onnection Properties screen, define the SQL database connection properties. If this is installation on Node B, that covers report server installation folder created during installation on Node A, the database connection details are already provided on this screen. Verify if these values are identical as the ones provided during report server installation on Node A. Ensure the database location is correct. The report server requires a database to store run-time data. You need to specify: Database administrator login, Database administrator 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. Server [\instance :port] Provide connection details for the remote SQL Server. If you are running an SQL Server cluster set Server to the client access point for the SQL Server failover cluster (not the node name or address). If you are running a remote or standalone SQL Server installation set Server to the server name or IP address. To specify a port other than the default (1433), set Server to the server name followed by a colon followed by the port number. For example: myservername:1434 To specify a SQL database instance to which you want to connect, set Server to the server name followed by a backslash followed by the instance name. For example: myservername\myinstancename You may need to consult your database administrator to determine the correct values. Database device location The database device location is the physical location of the database on the database server computer. You can browse for a file path. If you are running SQL Server cluster make sure to provide the path that leads to the remote storage location defined in cluster configuration. Name of database Enter the name you want to give to your report server database. Name of 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.) 86

87 Appendix Providing Failover for Report Server If you are going to create a database on Microsoft SQL Server 2008 and want 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. Database user password Password for database user specified above. onfirm user password Password for database user specified above. (Same as Database user password.) Use SSL Select or clear the Use SSL check box to indicate whether SSL should be used in communication with a report server. 13. If you have entered the path and name of an existing database, when you click Next from the Database onnection Properties screen you are presented with buttons for specifying what to do with the current database: Upgrade the existing database (and preserve the data) or Recreate the database (and delete all of your existing data). IMPORTANT To preserve data, always instruct the installer to upgrade an existing report server database. 14. If the Database Size screen is displayed, specify the size of the new database and then click Next. 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. 15. 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, the 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, you are presented an additional screen on which to specify whether to use all available RAM during database upgrade. Select the check box if you don't need the RAM for other purposes during this upgrade. 16. On the HTTP onnection Info screen, review the HTTP/HTTPS settings and choose whether to open the onnectivity and Security Options screen to edit these settings. Select the Launch advance panel option to open the onnectivity and Security Options screen, where you can specify the port number on which your report server should be accessible. 17. On the onnectivity and Security Options screen (displayed if you selected the check box in the previous step), specify the port number on which your report server should be accessible. 87

88 Appendix Providing Failover for Report Server Host name The host name under which your report server will be recognized is shown on the screen for your information. You will view your reports by accessing this host in your browser. Use HTTP on port The host name should be followed by the port number, if the port number is not 80. Note that this number will be incremented if the default port is unavailable. Use HTTPS (HTTP over SSL) on port If you need to transfer or display the reports securely across the network, you can also specify the HTTPS port number. 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. Note that this number will be incremented if the default port is unavailable. If you select the HTTPS option, the SSL Key Generation Data screen will be displayed. 18. 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 chose automatic or custom key generation. The SSL Key Generation Data screen enables you to type in the information required to generate a new key. For a custom encryption key, you will have to provide only the password; the other fields will be grayed out. hoosing a custom encryption key requires configuring the server manually, which involves copying both the key and the certificate to the proper directory and modifying the common.properties file. For more information, see onfiguring Report Server to Use Private Keys and ertificates [p. 39]. NOTE If you do not select the Remember the key password check box, you can instead supply the key password on system start-up, 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. 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. Also, remember that not providing a password means that the key will not be encrypted. 19. Review the summary of your installation choices and, if you are satisfied with them, click Install. If you need to change anything, use the Back button to retrace your steps to the appropriate configuration screen. 88

89 Appendix Providing Failover for Report Server 20. Your report server 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. 21. On the Installation Summary screen, review the installation summary. lick Show postinstall summary if you want to open a file containing a summary of the installation up to this point. 22. Perform post-installation actions. Depending on the operating system you are using, you may be asked at this stage whether you want to start ADS or AS. Ensure the check box provided is selected and click Finish. IMPORTANT In some circumstances, this screen displays a ontinue button rather than a Finish button. lick ontinue and follow the onscreen instructions to finish the installation. What to Do Next The system services supporting report server operation are controlled by the Server luster Manager. You must change the default settings for report services to run as Active Directory domain user. For more information, see hanging Default Report Server Service Settings on a Failover Node [p. 89]. If you have not already obtained and installed a license, do so now. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Ensure the license file is located on the shared storage where report server files are located so that each running report server instance can access the licenses without blocking the cluster operation. hanging Default Report Server Service Settings on a Failover Node Installations of AS or ADS in failover cluster do not use default settings for stopping and starting the report servers. You need to adjust server services to manual start and the Watchdog service to never restart the report server. It is also necessary to define the user account that the service can use to log on. To modify service settings for report servers: 1. Log on to the cluster node using user account belonging to the Administrators group. 2. Open the Services management tool. 3. Select the report server service and display its properties. If you are configuring high availability for AS reports, select entral Analysis Server service. 89

90 Appendix Providing Failover for Report Server If you are configuring high availability for ADS reports, select Advanced Diagnostics Server. 4. Set Startup type to Manual. 5. Specify the user account that the service can use to log on. On the Log On tab select This account and enter credentials for the domain user. 6. lick OK to confirm the changes. Defining High Availability for Report Server Service entral Analysis Server or Advanced Diagnostics Server starts working within failover cluster after you define high availability for the report server service. Use cluster wizard to achieve this goal. The tool allows you to select report server service, assign storage to the failover service and set the access name you will use to access the reports. After the wizard steps are completed the report server starts working within failover cluster. Before You Begin For general information on adding services to failover configuration, see onfiguring a Service or Application for High Availability ( To configure high availability of the report server application: 1. In the Failover luster Manager navigate to your main cluster screen to display onfigure add-in. 2. lick onfigure a Service or Application. High Availability Wizard opens, click Next to proceed. 90

91 Appendix Providing Failover for Report Server Figure 5. High Availability Wizard 3. On the Select Service or Application screen select Generic Service and click Next to proceed. Figure 6. Selecting service type 91

92 Appendix Providing Failover for Report Server 4. From the list of available services select your report server service. If you are configuring high availability for AS reports, select entral Analysis Server service. If you are configuring high availability for ADS reports, select Advanced Diagnostics Server. Figure 7. Selecting report server service 5. Define lient Access Point. In the Name field enter the name that will be used by anyone who wants to access the reports. The name provided must be a valid DNS name and comply with NetBios standard (no more than 15 characters). This is the name visible to other Data enter Real User Monitoring components (for example RUM onsole or other report servers). lick Next to proceed. 92

93 Appendix Providing Failover for Report Server Figure 8. Defining client access point 6. Select storage that will always be available to the currently operating cluster node. Select the disk that contains AS or ADS installation directory. Figure 9. Selecting remote storage 93

94 Appendix Providing Failover for Report Server 7. omplete high availability service setting. You do not need to replicate registry settings across nodes, skip Replicate Registry Settings, click Next to see confirmation screen. Figure 10. onfirmation screen for service high availability shown before settings are deployed After the confirmation screen is displayed click Next to finalize configuring a service for high availability. lick Finish to exit wizard. 94

95 Appendix Providing Failover for Report Server Figure 11. The last step in High Availability Wizard The report server is now working in high availability mode. 8. Find out the address of the failover cluster. To be able to access reports you must communicate with the report server using the address or name of the service automatically set at the service configuration time. You can access AS or ADS reports using client access point name that was set at the stage of configuring service high availability. You can also use IP address assigned to the application by the cluster manager. In Server Manager go to Features Failover luster Manager Your_luster_Name Services and applications Your_client_access_point_name to find IP address. 95

96 Appendix Providing Failover for Report Server Figure 12. Details for high availability entral Analysis Server Migrating Existing Report Server Installation to Provide High Availability Using lustering Feature You can designate an existing report server (AS or ADS) to work in a failover cluster configuration where two independent hosts share report server installation, configuration and logs. To do that you will have to stop the running server, de-install it and perform installation using a shared external storage. Each machine working within failover cluster hosting report server needs to be prepared in the same manner. The following procedure presents steps necessary for transforming a standalone report server to a replicated setup providing high availability of reports. The base assumption in this procedure is that the currently used machine becomes one of the cluster members. This, however, is not required, you do not have to include the existing machine in the cluster. Each of the two hosts working within the cluster is going to be further on referred to as Node A and Node B. Note that for the time of installation and migration access to the reports will not be possible. To deploy report server using lustering Feature: Preliminary tasks 1. Verify prerequisites for building a failover cluster. For more information, see Failover lustering Prerequisites [p. 80]. 2. Ensure each of the hosts designed to work as cluster nodes belongs to the same Active Directory domain. 3. Select Active Directory domain user to be used as cluster user. Ensure the user is added to the Administrators group on each node of the cluster. 4. Use domain account to login into nodes A and B 96

97 Appendix Providing Failover for Report Server Preserving database and important settings 5. Stop the report server. For more information, see Starting, Stopping, and Accessing Your Report Server in the Data enter Real User Monitoring Administration Guide. 6. Required: Perform report server backup. For more information, see Backing Up Report Server in the Data enter Real User Monitoring Administration Guide. 7. Required: Perform report server database backup. If you deployed SQL Server 2008 to store report server run-time data, see Backing Up MS SQL Server 2008 AS Databases in the Data enter Real User Monitoring Administration Guide. If you deployed SQL Server 2005 to store report server run-time data, see Backing Up MS SQL Server 2005 AS Databases in the Data enter Real User Monitoring Administration Guide. Discarding old setup 8. Required: Uninstall the report server software. You must perform this step if you are transforming the machine currently hosting report server installation into a cluster node. The existing data files and configuration need to be reinstalled on shared disk. For more information, see Uninstalling the Report Server [p. 53]. Setting up failover cluster 9. Enable Failover lustering feature on all hosts working within the cluster and perform other clustering-related steps. Go to Server Manager to find tools necessary for performing the following steps. a. Install Failover lustering feature. For more information, see Install the Failover lustering Feature ( b. onnect storage and networks for the cluster. For more information, see Prepare Hardware Before Validating a Failover luster ( c. Validate configuration. For more information, see Validate a New or Existing Failover luster ( d. reate a cluster. For more information, see reate a New Failover luster ( Ensure to include all servers designated to be cluster nodes (Node A and Node B) when performing the Select servers step. 97

98 Appendix Providing Failover for Report Server Setting up SQL Server Before you begin actual installation and setup of nodes hosting report server installation you must prepare SQL Server to store report server's runtime data. It is not recommended that a standalone SQL Server be installed on one of the cluster nodes. hoose either a remote SQL Server installation to store report server database or deploy SQL Server failover cluster using nodes A and B or remote failover cluster. 10. Optional: Install SQL Server cluster on nodes A and B. For more information, see Getting Started with SQL Server 2008 R2 Failover lustering ( SQL Server vendor offers two solutions: Integrated failover cluster install with Add Node and Advanced/Enterprise installation. hoose the most suitable solution for you and proceed according to SQL Server manual. If you decide to implement this solution note the failover cluster client access point name and address. This information is required later as the report server installation step. Ensure also that the databases are set to be located on the external storage shared by SQL Server cluster nodes. This location will also need to be provided during AS or ADS installation. 11. Optional: Migrate database to a remote SQL Server. You must perform this step if you have previously run SQL Server and report server on a single machine. The backed up report server database must be moved to a remote SQL Server or to the SQL Server cluster. For more information, see Backup and Recovery Procedures in the Data enter Real User Monitoring Administration Guide and Report Server Database Management in the Data enter Real User Monitoring Administration Guide. Setting up Node A The following steps need to be performed on both machines Node A and Node B as a sequence. Simultaneous installations are not possible since each process depends on the software being installed on a shared storage and shared database access. To preserve data, always instruct the installer to upgrade an existing report server database. Ensure to enter the migrated database details when installing the report server. 12. Install the report server on Node A choosing the remote storage as installation home. For more information, see Running a Report Server Setup on a Failover Node [p. 83]. Note that you should perform installations on each node sequentially in the order suggested. This will ensure report server files and database coherence. To preserve data, always instruct the installer to upgrade an existing report server database. 13. hange default settings for report server services. The system services supporting report server operation are controlled by the Server luster Manager. For more information, see hanging Default Report Server Service Settings on a Failover Node [p. 89]. 14. onfigure Distributed License Management on Node A. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. 98

99 Appendix Providing Failover for Report Server Ensure the license file is located on the shared storage where report server files are located so that each running report server instance can access the licenses without blocking the cluster operation. 15. Verify newly installed report server operation. Try logging to the report server as user with administrative rights to see if it is up and running. Do not change any settings yet. 16. Stop cluster service on Node A. Use Failover luster Manager to stop the service on a selected node. Expand Nodes, right-click the node you want to stop and click Stop luster Service in the More Actions submenu. As a result Node B will be able to access shared storage and the cluster service will be started. Setting up Node B 17. Install the report server on Node B choosing the remote storage as installation home. For more information, see Running a Report Server Setup on a Failover Node [p. 83]. To preserve data always instruct the installer to upgrade an existing report server database. 18. hange default settings for report server services. The system services supporting report server operation are controlled by the Server luster Manager. For more information, see hanging Default Report Server Service Settings on a Failover Node [p. 89]. 19. onfigure Distributed License Management on Node B. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Ensure the license file is located on the shared storage where report server files are located so that each running report server instance can access the licenses without blocking the cluster operation. 20. Stop the report server on Node B. 21. Using previously prepared backup restore the report server overriding default settings from fresh installation. For more information, see Restoring Report Server in the Data enter Real User Monitoring Administration Guide. 22. Start the report server service. 23. Verify newly installed report server operation. Try logging to the report server as user with administrative rights to see if it is up and running. Do not change any settings yet. 24. Stop the report server on Node B. Finishing failover cluster configuration 25. Ensure failover services is running on both nodes. 99

100 Appendix Providing Failover for Report Server Use Failover luster Manager to start the service on a selected node. Expand Nodes, right-click the node you want to start and click Start luster Service in the More Actions submenu. 26. onfigure AS or ADS service for high availability For more information, see Defining High Availability for Report Server Service [p. 90]. onfiguring Data enter Real User Monitoring 27. Add the report server to the RUM onsole. To add the report server use the IP address assigned to the client access point. To find out the address of the failover cluster, see Step 8 [p. 95]. What to Do Next After confirming the report server works and adding it to the RUM onsole you can proceed with other deployment tasks like adding AMDs to the server and other configuration tasks. Migrating Report Server Failover luster to Provide High Availability Using lustering Feature You can designate an existing report server failover cluster using deprecated mechanism built in entral Analysis Server to work in a failover cluster configuration using Windows Server built-in lustering Feature. To do that you will have to destroy the existing cluster, upgrade master server, perform a full backup (database and configuration) and perform installation using a shared external storage. Each machine working within failover cluster hosting report server needs to be prepared in the same manner. The following procedure presents steps necessary for transforming an older installation (for example, 11.7) of report server failover cluster to a solution using lustering Feature of Windows Server The base assumption in this procedure is that the currently used machines become nodes in the failover cluster. This, however, is not required, you do not have to include the existing machines in the cluster. Use the master server as the base of upgrade and backup. Each of the two hosts working within the cluster is going to be further on referred to as Node A and Node B In the case of this migration procedure we assume that the former master server becomes Node A and the former slave server becomes Node B. All backup procedures need to be performed on the machine where the master server is installed. Note that for the time of installation and migration access to the reports will not be possible. Preliminary tasks 1. Verify prerequisites for building a failover cluster. For more information, see Failover lustering Prerequisites [p. 80]. 2. Ensure each of the hosts designed to work as cluster nodes belongs to the same Active Directory domain. 3. Select Active Directory domain user to be used as cluster user. Ensure the user is added to the Administrators group on each node of the cluster. 4. Use domain account to login into nodes A and B 100

101 Appendix Providing Failover for Report Server Preserving database and important settings 5. Destroy server cluster. For more information, see Deleting a Failover Server in the Data enter Real User Monitoring Administration Guide. 6. Perform master AS upgrade to release For more information, see Upgrading entral Analysis Server in the Data enter Real User Monitoring entral Analysis Server Installation Guide. 7. Stop report servers. Stop the master and the slave server. Starting, Stopping, and Accessing Your Report Server in the Data enter Real User Monitoring Administration Guide 8. Required: Perform master server database backup. If you deployed SQL Server 2008 to store report server run-time data, see Backing Up MS SQL Server 2008 AS Databases in the Data enter Real User Monitoring Administration Guide. If you deployed SQL Server 2005 to store report server run-time data, see Backing Up MS SQL Server 2005 AS Databases in the Data enter Real User Monitoring Administration Guide. 9. Required: Perform master server backup. For more information, see Backing Up Report Server in the Data enter Real User Monitoring Administration Guide. Discarding old setup 10. Required: Uninstall the report server software on both hosts, the master and the slave. You must perform this step if you are transforming the machine currently hosting report server installation into a cluster node. The existing data files and configuration need to be reinstalled on shared disk. For more information, see Uninstalling the Report Server [p. 53]. Setting up failover cluster 11. Enable Failover lustering feature on all hosts working within the cluster and perform other clustering-related steps. Go to Server Manager to find tools necessary for performing the following steps. a. Install Failover lustering feature. For more information, see Install the Failover lustering Feature ( b. onnect storage and networks for the cluster. For more information, see Prepare Hardware Before Validating a Failover luster ( c. Validate configuration. For more information, see Validate a New or Existing Failover luster ( 101

102 Appendix Providing Failover for Report Server d. reate a cluster. For more information, see reate a New Failover luster ( Ensure to include all servers designated to be cluster nodes (Node A and Node B) when performing the Select servers step. Setting up SQL Server Before you begin actual installation and setup of nodes hosting report server installation you must prepare SQL Server to store report server's runtime data. It is not recommended that a standalone SQL Server be installed on one of the cluster nodes. hoose either a remote SQL Server installation to store report server database or deploy SQL Server failover cluster using nodes A and B or remote failover cluster. 12. Optional: Install SQL Server cluster on nodes A and B. For more information, see Getting Started with SQL Server 2008 R2 Failover lustering ( SQL Server vendor offers two solutions: Integrated failover cluster install with Add Node and Advanced/Enterprise installation. hoose the most suitable solution for you and proceed according to SQL Server manual. If you decide to implement this solution note the failover cluster client access point name and address. This information is required later as the report server installation step. Ensure also that the databases are set to be located on the external storage shared by SQL Server cluster nodes. This location will also need to be provided during AS or ADS installation. 13. Optional: Migrate the backed up master AS database to a remote SQL Server. You must perform this step if you have previously run SQL Server and report server on a single machine. The backed up report server database must be moved to a remote SQL Server or to the SQL Server cluster. For more information, see Backup and Recovery Procedures in the Data enter Real User Monitoring Administration Guide and Report Server Database Management in the Data enter Real User Monitoring Administration Guide. Setting up Node A The following steps need to be performed on both machines Node A and Node B as a sequence. Simultaneous installations are not possible since each process depends on the software being installed on a shared storage and shared database access. To preserve data, always instruct the installer to upgrade an existing report server database. Ensure to enter the migrated database details when installing the report server. 14. Install the report server on Node A choosing the remote storage as installation home. For more information, see Running a Report Server Setup on a Failover Node [p. 83]. Note that you should perform installations on each node sequentially in the order suggested. This will ensure report server files and database coherence. To preserve data, always instruct the installer to upgrade an existing report server database. 15. hange default settings for report server services. 102

103 Appendix Providing Failover for Report Server The system services supporting report server operation are controlled by the Server luster Manager. For more information, see hanging Default Report Server Service Settings on a Failover Node [p. 89]. 16. onfigure Distributed License Management on Node A. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Ensure the license file is located on the shared storage where report server files are located so that each running report server instance can access the licenses without blocking the cluster operation. 17. Verify newly installed report server operation. Try logging to the report server as user with administrative rights to see if it is up and running. Do not change any settings yet. 18. Stop cluster service on Node A. Use Failover luster Manager to stop the service on a selected node. Expand Nodes, right-click the node you want to stop and click Stop luster Service in the More Actions submenu. As a result Node B will be able to access shared storage and the cluster service will be started. Setting up Node B 19. Install the report server on Node B choosing the remote storage as installation home. For more information, see Running a Report Server Setup on a Failover Node [p. 83]. To preserve data always instruct the installer to upgrade an existing report server database. 20. hange default settings for report server services. The system services supporting report server operation are controlled by the Server luster Manager. For more information, see hanging Default Report Server Service Settings on a Failover Node [p. 89]. 21. onfigure Distributed License Management on Node B. For more information, see Licensing Data enter Real User Monitoring omponents [p. 67]. Ensure the license file is located on the shared storage where report server files are located so that each running report server instance can access the licenses without blocking the cluster operation. 22. Stop the report server on Node B. 23. Using previously prepared backup restore the report server overriding default settings from fresh installation. For more information, see Restoring Report Server in the Data enter Real User Monitoring Administration Guide. 24. Start the report server service. 25. Verify newly installed report server operation. 103

104 Appendix Providing Failover for Report Server Try logging to the report server as user with administrative rights to see if it is up and running. Do not change any settings yet. 26. Stop the report server on Node B. Finishing failover cluster configuration 27. Ensure failover services is running on both nodes. Use Failover luster Manager to start the service on a selected node. Expand Nodes, right-click the node you want to start and click Start luster Service in the More Actions submenu. 28. onfigure AS or ADS service for high availability For more information, see Defining High Availability for Report Server Service [p. 90]. onfiguring Data enter Real User Monitoring 29. Add the report server to the RUM onsole. To add the report server use the IP address assigned to the client access point. To find out the address of the failover cluster, see Step 8 [p. 95]. What to Do Next After confirming the report server works and adding it to the RUM onsole you can proceed with other deployment tasks like adding AMDs to the server and other configuration tasks. Starting, Stopping, and Accessing Report Server Working in Failover luster Report server working in a failover cluster is accessed with the address or name set during cluster configuration. Starting and stopping is controlled by Failover luster Manager. Accessing the report server The report server is accessed through a Web browser. Open the following URL: or access point:port where, client_access_point is the name that you set during configuration of report server service for high availability, :port is optional if the server is not installed on port 80 for HTTP or 443 for HTTPS, accordingly. Starting and stopping the report server The report server working in a cluster should be started and stopped using Failover luster Manager. 104

105 Appendix Providing Failover for Report Server In Failover luster Manager expand your cluster and go to Services and applications. Right-click the name of your report server service and select: Bring this service or application online to start report server. Take this service or application offline to stop report server. You should not use Services tool on chose nodes as this effects in report server services being moved to another node. Figure 13. Selecting to stop report server Figure 14. Failover luster Manager showing stopped report server 105