You are on page 1of 42

Real-User Monitoring Data Center

RUM Console Installation Guide


Release 12.0

Please direct questions about Real-User Monitoring Data Center or comments on this document to: APM Customer Support FrontLine Support Login Page: http://go.compuware.com

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

Build: May 17, 2012, 18:21

Contents

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of the Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer Support and Online Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting a Problem on Real-User Monitoring Data Center. . . . . . . . . . . . . . . . . . . Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 Gomez RUM Console Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Installing, Running, and Uninstalling RUM Console Components. . . . Installing RUM Console Server and RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting RUM Console to RUM Console Server . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4 RUM Console Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console Tasks Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console Devices Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console Device Information Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console Capacity Status Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console Sequence Transactions Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console User-Defined Software Services Tab. . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console User Management Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RUM Console Reporting Hierarchy Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5 Using Java Web Start-based RUM Console. . . . . . . . . . . . . . . . . . . . . Launching Java Web Start-based RUM Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launching Java Web Start-based RUM Console from Windows Shortcut. . . . . . . . . . . Managing Java Web Start-based RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling Java Web Startbased RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Java Web Start-based RUM Console Connection Properties. . . . . . . . . . . . . Changing Java Web Start-based RUM Console Connection Properties Remotely. . . . . 5 5 5 5 6 6 8 9 11 15 15 16 17 19 20 20 22 24 24 26 26 26 27 27 28 28 29 30 30

Real-User Monitoring Data Center RUM Console Installation Guide

Contents

Chapter 6 RUM Console Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Standalone RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Java Web Start-based RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup and Recovery Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up RUM Console Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring RUM Console Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying and Fixing User Account Migration Exceptions. . . . . . . . . . . . . . . . . . . . . Appendix A Troubleshooting RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

33 33 34 35 35 35 36 36 37 41

Real-User Monitoring Data Center RUM Console Installation Guide

INTRODUCTION

Who Should Read This Guide


This manual is intended for users of Real-User Monitoring Data Center who want to install RUM Console and RUM Console Server.

Organization of the Guide


This guide is organized as follows: Gomez RUM Console Overview [p. 9] System Requirements [p. 11] Installing, Running, and Uninstalling RUM Console Components [p. 15] RUM Console Navigation [p. 19] Using Java Web Start-based RUM Console [p. 27] RUM Console Upgrades [p. 33]

Related Publications
Documentation for your product is distributed on the product media. For Data Center RUM, it is located in the \Documentation directory. It can also be accessed from the Media Browser. You can also access online documentation for Compuware products via our FrontLine support site at http://go.compuware.com. FrontLine provides fast access to information about your Compuware 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.

Real-User Monitoring Data Center RUM Console Installation Guide

Introduction

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 http://www.adobe.com/downloads/.

Customer Support and Online Information


Corporate Web site To access Compuware's site on the Web, go to http://www.compuware.com. The Compuware site provides a variety of product and support information. FrontLine support Web site You can access online customer support for Compuware products via our FrontLine support site at http://go.compuware.com. FrontLine provides fast access to critical information about your Compuware products. You can read or download documentation, frequently asked questions, and product fixes, or e-mail your questions or comments. The first time you access FrontLine, you are required to register and obtain a password. Registration is free. Contact us The contact information to all local Compuware offices is provided on the http://go.compuware.com Web site. All high-priority issues should be reported by phone.

Reporting a Problem on Real-User Monitoring Data Center


When calling, please provide Customer Support with as much information as possible about your environment and the circumstances that led to the difficulty. You should be ready to provide: Client number: this number is assigned to you by Compuware and is recorded on your sales contract. The version number of the Agentless Monitoring Device (AMD) , the report servers and RUM Console with RUM Console Server. For the report server Use the report server GUI by selecting Help Product Information About, or Tools Diagnostics System Status. For the 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. For the RUM Console and RUM Console Server Use the RUM Console GUI by selecting Help About menu item.

Real-User Monitoring Data Center RUM Console Installation Guide

Introduction

For the TCAM Use the TCAM 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 yes, include a sequence of steps for problem recreation. If 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 difficulty and their results. Debug information for specific components obtained from RUM Console. Information about the RUM Console itself. To export all the information, navigate to Tools Export Diagnostic Information in the RUM Console menu. Information about the report servers. To export the information for a specific ADS or CAS, right-click the device on the Devices tab in the RUM Console and choose Export Diagnostic Information from the context menu. Include Collector 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. Information about the AMD. To export the information for a specific AMD, right-click the device on the Devices tab in the RUM Console 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 TCAM System Event log of the machine where the TCAM is operating.

Real-User Monitoring Data Center RUM Console Installation Guide

Introduction

TCAM logs which by default are stored in C:\ProgramData\Compuware\VTCAM for Windows Server 2008 and C:\Documents and Settings\All Users\Compuware\VTCAM for Windows Server 2003.

NOTE Please compress all the files before sending them to Customer Support. Compuware values your comments and suggestions about the Compuware APM products and documentation. Your feedback is very important to us. If you have questions or suggestions for improvement, please let us know.

Documentation Conventions
The following font conventions are used throughout documentation: This font Bold 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 Compuware documentation. Cited contents of text files, inline examples of code, command line inputs or system outputs. Also file and path names. User input in console commands. Place holders for values of strings, for example as in the command:
cd directory_name

Citation Documentation Conventions [p. 8]


Fixed width

Fixed width bold Fixed width italic

Menu Item

Menu items. Text screen shots.

Screen

Code block

Blocks of code or fragments of text files.

Real-User Monitoring Data Center RUM Console Installation Guide

CHAPTER 1

Gomez RUM Console Overview


Gomez RUM Console consists of two components: RUM Console Server A back-end server application that maintains configuration images and device information, runs tasks related to configuration management, and provides a Web services API for RUM Console to manage configurations. The server is a Windows-based service that can be installed on a machine with Windows 2003 Server or Windows 2008 Server R2 with a network connection to all of the managed devices within the Compuware APM infrastructure. RUM Console A GUI application for configuring report servers and data collectors. With the console, you can create and edit configurations for Compuware APM devices and propagate such configurations to other Compuware APM devices. Both components are required to be installed, but not necessarily on the same machine: you can install the server on a separate machine, in which case the console can connect to the server over HTTPS. NOTE You should use only one installation of RUM Console Server to configure a specific device or group of devices in your Compuware APM infrastructure. If you choose to use more than one instance of RUM Console Server, each server should be used to manage a different group of devices. Otherwise, Compuware APM users working simultaneously on different instances of RUM Console Server could overwrite one another's configurations. Configuring a device with the Guided Configuration perspective is possible only with one RUM Console Server connection at a time; if you try to connect using another RUM Console Server, the Connection status section for the device will show a Could not register manager at agent message for the Guided Configuration and you will not be able to perform any tasks using the Guided Configuration perspective. For more information, see Working with Guided Configuration Perspective in RUM Console in the Real-User Monitoring Data Center Web Application Monitoring User Guide.

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 1 Gomez RUM Console Overview

10

Real-User Monitoring Data Center RUM Console Installation Guide

CHAPTER 2

System Requirements
You can install RUM Console on a Microsoft Windows machine, dedicated or shared with other Data Center RUM components. The requirements listed below are quoted directly from Real-User Monitoring Data Center Hardware Recommendations. Be sure to consult that guide before finalizing your purchase decisions. A report server platform should meet or exceed the following requirements. CPUs At least 2x quad core CPU (or at least 8 cores in total) working with at least 2 GHz clock. In general, performance improves with higher CPU frequencies and core counts. Under testing, the best performance-to-cost ratio was achieved with 12 cores. Operating System For a report server, select a server capable of running one of the following Windows editions with the latest release, service packs, and 5 Client Access Licenses (CALs). 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 Microsoft SQL 2005 Server (64-bit Edition) Standard or Enterprise Microsoft SQL 2008 Server (64-bit Edition) Standard or Enterprise Microsoft SQL 2008 Server R2 (32-bit and 64-bit Edition) Standard or Enterprise

Memory and HDDs The memory and HDD requirements of your report server depend on the functions assigned to that report server. CAS = Central Analysis Server ADS = Advanced Diagnostics Server CAS SQL = the CAS SQL database

Real-User Monitoring Data Center RUM Console Installation Guide

11

Chapter 2 System Requirements

ADS SQL = the ADS SQL database RUM Console Server = the server portion of the RUM Console software

Table 1. Module-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 next table for recommended machine configurations. Module CAS Min. RAM Rec. RAM 24 GB 32 GB Min. HDD 10 GB Can co-exist with CAS SQL, RUM Console Server ADS 24 GB 32 GB 10 GB ADS SQL, RUM Console Server CAS SQL 24 GB 32 GB 8 x 146 GB (in RAID setup) 8 x 146 GB (in RAID setup) 1 GB CAS, RUM Console Server ADS, RUM Console Server CAS, ADS, CAS SQL, ADS SQL

ADS SQL

24 GB

32 GB

RUM Console 2 GB Server

2 GB

Table 2. Illustrative installations This table lists example machine configurations in terms of RAM size, HDD requirements, and module intercompatibility.

NOTE
For each row, the listed amount of RAM should be sufficient for that machine running those modules, but adding more RAM will in many cases result in even better performance. You may find one of the first two configurations below particularly useful. CAS and ADS can never be installed on the same machine.

Modules

RAM

HDD 8 x 146 GB (in RAID setup)

CAS + CAS SQL database + RUM Console 64 GB Server ADS + ADS SQL database + RUM Console Server 64 GB

8 x 146 GB (in RAID setup)

12

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 2 System Requirements Table 2. Illustrative installations (continued) Modules CAS CAS + CAS SQL database ADS ADS + ADS SQL database CAS SQL + RUM Console Server ADS SQL + RUM Console Server RAM 32 GB 64 GB 32 GB 64 GB 32 GB 32 GB HDD 10 GB 8 x 146 GB (in RAID setup) 10 GB 8 x 146 GB (in RAID setup) 8 x 146 GB (in RAID setup) 8 x 146 GB (in RAID setup)

Real-User Monitoring Data Center RUM Console Installation Guide

13

Chapter 2 System Requirements

14

Real-User Monitoring Data Center RUM Console Installation Guide

CHAPTER 3

Installing, Running, and Uninstalling RUM Console Components


To use the RUM Console, you must install it, establish a connection between it and the RUM Console Server, specify a Compuware Security Server to use (or install one locally), and configure some basic settings.

Installing RUM Console Server and RUM Console


1. Select the installation disc that matches your target machine's operating system. 2. DVD1 Windows DVD2 Linux DVD3 AIX HPUX Solaris

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.

Run the RUM Console installation program. If you are viewing the Home tab, click Real User Monitoring Console. If you are viewing the Classic View tab, click Configuration Console for Agentless.

Either selection starts the installation program. 4. 5. 6. On the Introduction screen, read the introduction and then click Next. On the License Agreement screen, indicate that you have read and accepted the license agreement, and then click Next. On the Choose Install Set screen, select the configuration you want to install, and then click Next. Standard Installation installs the console and server software.

Real-User Monitoring Data Center RUM Console Installation Guide

15

Chapter 3 Installing, Running, and Uninstalling RUM Console Components

7. 8. 9.

Console Installation installs only the console software. Custom installs selected items as needed.

If you selected Custom in the previous step, now select the components you want to install and then click Next. On the Choose Install Folder screen, indicate where you want to install the software, and then click Next. On the Security Configuration screen, provide the Compuware Security Server settings you want to use, and then click Next. You can install Compuware Security Server locally during this installation or specify the address and port of a remote Compuware Security Server server to use.

10. On the Pre-Installation Summary screen, review the installation options you have selected, and then click Install. The software you have selected will be installed. This may take some time. 11. On the Install Complete screen, click Done. The location of the installation log is displayed on this screen. Be sure to refer to it if errors occurred during installation.

Connecting RUM Console to RUM Console Server


To use the RUM Console, you must first connect to the RUM Console Server. This process is started automatically when you provide the correct URL and administrative user credentials. It is very important to keep all of the device times synchronized. Ensure that the RUM Console Server is synchronized with RUM Console, and any other report servers and monitoring devices that this RUM Console manages. For more information, see Synchronizing Time Using NTP Server in the Real-User Monitoring Data Center Agentless Monitoring Device Installation Guide and Time Synchronization Between AMD and Server in the Real-User Monitoring Data Center Administration Guide. To connect to RUM Console Server: 1. 2. Double-click the RUM Console icon. Enter the RUM Console Server address in the Address field. Because communication between RUM Console and RUM Console Server occurs over HTTPS, it is important to indicate the protocol and the specific port that will be used. For example:
https://192.168.129.1:4183

where 4183, the specified port number, is the default port for communicating with RUM Console Server. 3. 4. 5. Provide a console user name in a User name field. To log in to RUM Console Server via RUM Console, you must provide your credentials. Enter the password for the user. Click OK to connect to RUM Console Server.

16

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 3 Installing, Running, and Uninstalling RUM Console Components

RUM Console, by default, opens the Guided Configuration perspective. The first time you access the Guided Configuration perspective, you will see the First steps screen. Follow the instructions provided on this screen to configure Compuware APM to monitor your applications. Using the button in the top left part of the screen, you can access the actual Guided Configuration Home page that contains the following sections: Configuration status Shows the number of monitored Web and non-Web software services, the number of imported GPN test definitions, and the number of monitored transactions there are based on the imported GPN tests. It also tells you if there is any configuration draft pending if the connection with an AMD fails. The links embedded in the summary records enable you to perform configuration tasks such as defining a new software service or importing Gomez tests. Web application traffic Indicates whether traffic auto-recording is currently enabled and in progress, and shows the number of traffic traces that were captured manually. Use the embedded links to start a new recording or change recording settings. Data Center RUM status Shows the connection status for AMDs, report servers and Gomez Performance Network. The tooltips show connection details for each device. Application overview Shows the application protocols and servers detected in the traffic monitored by selected or all AMDs. Application traffic categories Shows the most frequently occurring parameters in the traffic monitored by selected or all AMDs. Choosing a parameter can be the starting point for defining a software service, where the selected parameter would be used to filter available servers. Sniffing point diagnostics Shows diagnostic information about the quality of the traffic and whether the mirrored port configuration is correct. When you switch to the Entire Configuration perspective, it includes with the most common views: Tasks, Devices, Transactions, User-Defined Software Services, Reporting Hierarchy and Device Information. Each of these views can be closed, minimized, or attached to a different view panel. To restore all the views to a default configuration, select the menu item Window Restore Defaults. What to Do Next Refer to RUM Console cannot connect RUM Console Server. [p. 38] if you encounter problems in connecting RUM Console to RUM Console Server

Uninstalling RUM Console


Uninstallation of RUM Console can be done via Add or Remove Programs or Programs and Features in Windows Control Panel.

Real-User Monitoring Data Center RUM Console Installation Guide

17

Chapter 3 Installing, Running, and Uninstalling RUM Console Components

To uninstall RUM Console: 1. In Windows system toolbar, click Start and select Control Panel. Depending on the version of your Windows, do one of the following: 2. 3. Double-click Add or Remove Programs Click Uninstall a program in the Programs and Features section

Double-click the RUM Console entry. This will launch the installation program. Select Uninstall Product and proceed with the process of uninstallation.

The installation script will not remove any files or folders created after the initial RUM Console installation.

18

Real-User Monitoring Data Center RUM Console Installation Guide

CHAPTER 4

RUM Console Navigation


RUM Console enables you to view and modify all aspects of system configuration within the Compuware APM infrastructure. You can use the console to define and manage devices, software services, and transactions. While working with these entities through the console, you should be aware that the same entities can often be accessed in different ways, depending on your need. In particular, this applies to software services, which can be managed through devices or independently. RUM Console screens are grouped into two perspectives: Guided Configuration and Entire Configuration. Use the buttons in the top left part of the RUM Console to switch between the perspectives. The most important features of the Guided Configuration perspective include: A step-by-step guide to configuring application traffic monitoring for first-time Compuware APM users. An interface to verify the quality of sniffing points traffic detection. A preview of the captured traffic traces that can help you find the right input data for the software service definitions. A preview of the HTTP, HTTPS, XML, SOAP and SSL (undecrypted) top application traffic categories, which can streamline the configuration process by narrowing down the number of servers available for a software service definition. For example, you can select a number of URLs from the list of the most frequently occurring URLs and then use the selected URLs to filter available servers. A wizard-based process for creating and editing software services, which helps you manage your software services and service rule definitions more effectively. An interface for importing Gomez Performance Network test definitions and integrating performance measurements obtained from the GPN and Data Center RUM.

The main parts of the Entire Configuration perspective include the following: Devices tab Lists report servers and also traffic monitoring devices that can be assigned to report servers. The configurations of these devices can be opened individually, and within each

Real-User Monitoring Data Center RUM Console Installation Guide

19

Chapter 4 RUM Console Navigation

device configuration you can define and configure software services and transactions to be monitored by that device. Sequence Transactions tab It can be used to define transactions for a number of monitoring devices simultaneously. User-Defined Software Services tab Groups together all services from all devices together, where they can be managed, assigned, re-assigned, or moved between devices. If your system configuration consists of only one monitoring device, you may find it more natural to perform most of your software service configuration from within that device configuration. However, if you are using a number of monitoring devices, you may find it useful to create and manage software service definitions under the User-Defined Software Services tab, independently of devices. Reporting Hierarchy tab The Reporting Hierarchy view presents the reporting hierarchy that is specific for a given application and has been imported from an external CSV file and mapped to the Compuware APM reporting hierarchy. Tasks tab The Tasks view presents all available business objects and configuration areas for the RUM Console.

RUM Console Tasks Tab


The Tasks view presents all available business objects and configuration areas for the RUM Console. Objects are grouped into categories: Business objects Devices Sequence Transactions User-defined software services Reporting hierarchy

Configuration User Management This view is a shortcut to the Window Show View menu selections.

RUM Console Devices Tab


The Devices tab on the RUM Console is a part of the Entire Configuration perspective and lists all of the devices within your Compuware APM deployment. Using the console, you can add, edit, and remove device connection configurations for any Compuware APM-supported device or server.

20

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 4 RUM Console Navigation

The Devices pane is arranged in a table and an informational tab. Click the Device Information tab to see details of the device currently selected in the table. RUM Console device types Device types that can appear on the Devices tab include: AMD An Agentless Monitoring Device. In addition to setting up general connection properties, you can also perform in-depth configuration of Global and Monitoring properties. For more information, see Managing Devices in the Real-User Monitoring Data Center Administration Guide and Basic Monitoring Configuration in the Real-User Monitoring Data Center Web Application Monitoring User Guide. Unsupported AMD An Agentless Monitoring Device of a version 11.6 and earlier. You may be able to see some information about such a device in the console, but you cannot use the console to configure it. CAS A Central Analysis Server, which can be administered by assigning, editing, and removing probes in its configuration. You can also enable or disable these probes and mark them to be managed in the console Devices table independently of the defined server connection. RUM Console gives you access to options available on the Master Central Analysis Server in the Settings top menu of the report server. Since the Console already knows the credentials it is able to display configuration screens directly from the report server without the need to log in. Configuration tools open in the lower section of the main screen. ADS An Advanced Diagnostics Server, which can be administered in the console by assigning, editing, and removing probes in its configuration. You can also enable and disable these probes and mark them to be managed in the console Devices table independently of the defined server connection. dynaTrace Server When dynaTrace and Data Center RUM are integrated, you can analyze individual slow pages loads in dynaTrace using data gathered by the Agentless Monitoring Devices leveraging the dynaTrace PurePath technology. This integration makes it possible to navigate from ADS data presented in CAS reports to the associated PurePath data in the dynaTrace Client. To make this work, you must configure the AMD for the ADS to monitor the same HTTP traffic that is generated by business applications being monitored by dynaTrace agents. You need to add dynaTrace Server to the RUM Console devices list as one of the steps necessary to integrate Data Center RUM and dynaTrace. For more information, see Integrating Data Center RUM with dynaTrace in the Real-User Monitoring Data Center Web Application Monitoring User Guide. Java/.NET Monitoring Manager Besides publishing the configuration through COS, you can use RUM Console to publish the global and HTTP related configuration to an individual Java/.NET Monitoring Manager. After a Java/.NET Monitoring Manager is added to the Devices table, the RUM Console

Real-User Monitoring Data Center RUM Console Installation Guide

21

Chapter 4 RUM Console Navigation

publishes all of the AMD device configurations to the Java/.NET Monitoring Manager automatically. Similarly, after the AMD device configuration is altered and a draft configuration is published to the AMD, the console automatically updates the configuration and publishes it to the Java/.NET Monitoring Manager. Flow Collector A legacy Network Monitoring Flow Collector that analyzes the traffic processed by netflow-enabled routers. Cisco NAM Cisco Network Analysis Module (NAM) Traffic Analyzer. Gomez Synthetic Monitoring Private Enterprise Agent Manager A device recognized as Gomez Synthetic Monitoring Private Enterprise Agent Manager via its Web service. This is for informational purposes only; the console only monitors the connection to that device. BSM Connection Manager for Business Service Manager. Adding it as a device to the RUM Console, enables you to assign it to CAS or ADS so that they can receive data imported by its input adapter from Cerner Real-Time Management System (RTMS). WAN A Network Monitoring Probe configured to monitor a WAN link. LAN A Network Monitoring Probe configured to monitor a LAN link. Other A Web server that is not recognized as part of the Compuware APM suite.

RUM Console Device Information Tab


The Device Information tab is a part of the Entire Configuration perspective and presents a brief status view of the selected device. Connection Status Presents information about the current connection status and reports any connection errors (including the response received from a connection query). Health Status Presents information on the health status of individual processes and versions of the selected device. This information is available for AMD-type devices and Central Analysis Server. If you select a Central Analysis Server or AMD, the Health status section of the Device Information tab presents the summary of the Capacity status report: Click the Capacity Status link next to the icon to see a full report. CAS The Memory utilization section shows the percentage of used memory during a predefined period of time, in comparison with the predefined memory threshold. By default, the memory threshold is set to 80%, and if it is exceeded, a memory alert is raised.

22

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 4 RUM Console Navigation

Number of sessions shows how many sessions are stored in the server cache memory. Average data file processing time shows the average data file processing time versus the predefined threshold during the last 24 hours, and whether the long processing time alert was raised. By default, the threshold for data processing time is set to 60% of the monitoring interval. The Nightly tasks execution time section shows how long (on average for a selected period of time) it took to execute three tasks: Daily Report Generation Data aggregation, calculation of trends and baselines, pre-defined DMI reports, and processing other data required for rendering reports. DBDailyMaintenance Data aging, cleaning caches, database daily maintenance of sites, domains, and finding new sites and servers to monitor. RTMDailyDataStore Closing the current day before storing performance data for the start of the next day. Nightly tasks execution time also shows whether the execution time for any of the above tasks exceeded the predefined timeout, raising the long execution time alert.

Business Units shows the number of defined tiers, reporting groups and applications in each reported period. Business Units Associations shows the number of associations between the business units and sessions as defined by a combination client, server and URL.

AMD Memory performance Memory performance indicator expressed as the amount of memory used by AMD data objects. This is equal to the number of object multiplied by the size of the objects. CPU performance CPU performance indicator expressed as CPU usage per thread expressed in percent. Disk performance Disk performance indicator expressed as the percentage of occupied disk space on AMD. Drop performance Drop performance indicator expressed as percentage of dropped packets from received packets. The AMD status information is provided by a Central Analysis Server, therefore you need both AMD and CAS added to your RUM Console and both devices must be connected to each other.

Real-User Monitoring Data Center RUM Console Installation Guide

23

Chapter 4 RUM Console Navigation

For more information, see Capacity Status in the Real-User Monitoring Data Center Administration Guide and AMD Statistics in the Real-User Monitoring Data Center Administration Guide. Configuration Status Presents the Current, Draft, and Pending status of a configuration file. The Current configuration indicates the publishing time and date, while the Draft and Pending configurations indicate whether a draft configuration is present or configuration publishing is pending. Sniffing Point Diagnostics Sniffing Point Diagnostics is a type of hardware state analysis that enables you to perform pre-monitoring tasks without the need to access the AMD terminal.A separate set of statistics is provided for each AMD added to the console. If there are any alarm messages, switch to the Guided Configuration perspective and go to the Sniffing Point Diagnostics section. Statistics and messages shown in this section are taken based on the latest recorded traffic trace. If you have several traces recorded you will always see data for the newest traffic sample. Note that this data is not related to the current state of the AMD and some statistics may be visible even when the device is down. NOTE If a device within your Compuware APM infrastructure is unable to report detailed status information to the manager, some sections may report that the information is unavailable. This does not indicate a problem with a device.

RUM Console Capacity Status Report


The Capacity Status reports for Central Analysis Server and AMD are extensions of the information provided in the Health Status section of the Device Information tab. Click the Capacity Status link next to the icon to see a full report. For more information, see Capacity Status in the Real-User Monitoring Data Center Administration Guide and AMD Statistics in the Real-User Monitoring Data Center Administration Guide.

RUM Console Sequence Transactions Tab


The Sequence Transactions tab in the RUM Console is a part of the Entire Configuration perspective and lists all transactions monitored by AMDs defined in the Devices tab. About transaction monitoring Transactions are sequences of information exchange that represent particular actions or functions performed by a human user or a client program. They are viewed as higher-level units of self-contained functionality and are tied to applications. For example, they may represent the procedure for an online purchase or ticket booking. AMD monitors traffic data and prepares it for transaction monitoring by an ADS and CAS. Some of the relevant configuration and

24

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 4 RUM Console Navigation

processing is performed on the actual RUM Console and some is performed on the AMD. See Configuring AMD to Monitor HTTP-based Transactions in the Real-User Monitoring Data Center Administration Guide and Configuring AMD to Monitor XML-based Transactions in the RUM Console Online Help for information on how to configure and use transaction monitoring on the AMD. ADS can monitor transactions defined as sequences of URLs per user, as sequences of XML transactions, or as sequences of SAP GUI operations. Browsing transactions To browse transactions and examine which group of AMDs monitor a particular transaction, select the Sequence Transactions tab, find the transaction that you want to examine, and expand the list. Sequence Transaction Name The name of a transaction. Application Name The application that includes the listed transaction. Type The protocol used to define the listed transaction: ASYNC-HTTP, CERNER, CERNER-RTMS, HTTP, OF, SAP GUI, SQL or XML. Packaged Applications Whether the listed transaction is a packaged application whose transactions are recognized by the report server automatically. You can expand the transaction list to view the AMDs that monitor this transaction. Right-click transaction to open a menu of transaction-related actions: Add Sequence Transaction Opens the Create Sequence Transaction screen, where you can select the AMD devices that will monitor this new transaction. Delete Sequence Transaction Deletes the selected transactions, updating all affected AMD configurations. NOTE If the transaction being deleted is monitored by more than one AMD, all of the affected AMDs will have a new draft configuration that will have to be published. Open Opens the selected transaction for editing. Clone Creates a clone of the selected transaction and appends an identifier to the cloned transaction name. Copy... Copies the selected transactions to another AMD. While the transactions list is expanded and a specific AMD is selected, the right-click menu options are limited to:

Real-User Monitoring Data Center RUM Console Installation Guide

25

Chapter 4 RUM Console Navigation

Add Sequence Transaction Delete Sequence Transaction Open.

RUM Console User-Defined Software Services Tab


The User-Defined Software Services tab is a part of the Entire Configuration perspective and lists all software services within your Compuware APM deployment. Through the console, you can add, remove, and edit the properties of any software service defined on any of your AMDs. The User-Defined Software Services tab in the main screen of the RUM Console contains information about all user-defined software services created on all devices managed via this console. From here you can manage services, add new ones, delete existing ones, and copy them across AMDs. Note that default software services are specific to a single AMD and cannot be managed centrally. For more information, see Basic Monitoring Configuration in the Real-User Monitoring Data Center Web Application Monitoring User Guide and Managing User-Defined Software Services in the Real-User Monitoring Data Center Cerner Application Monitoring User Guide.

RUM Console User Management Tab


The RUM Console User Management tab is a part of the Entire Configuration perspective and enables you to access Compuware Security Server configuration. Products connect to the Compuware Security Server through the installation process. From the server where CSS was installed, administrators can access CSS from the Start menu, selecting Compuware Common Components Compuware Security. For more information, see User Access and Security Overview in the Real-User Monitoring Data Center Administration Guide.

RUM Console Reporting Hierarchy Tab


The Reporting Hierarchy view presents the reporting hierarchy that is specific for a given application and has been imported from an external CSV file and mapped to the Compuware APM reporting hierarchy. For more information, see Importing the Reporting Hierarchy in RUM Console in the Real-User Monitoring Data Center Administration Guide.

26

Real-User Monitoring Data Center RUM Console Installation Guide

CHAPTER 5

Using Java Web Start-based RUM Console


You can access the RUM Console directly from a Central Analysis Server using Java Web Start, which automatically puts the configuration into the scope of the CAS you are using. There are three ways to launch the Java Web Start-based RUM Console: From a browser. For more information, see Launching Java Web Start-based RUM Console [p. 27]. From Java Application Cache Viewer. For more information, see Managing Java Web Start-based RUM Console [p. 28]. From the Windows shortcut. For more information, see Launching Java Web Start-based RUM Console from Windows Shortcut [p. 28].

To launch Java Web Start-based RUM Console, you need Microsoft Visual C++ 2008 Redistributable Package (x86) installed on your local machine.

Launching Java Web Start-based RUM Console


Access the RUM Console from a Central Analysis Server menu to configure the devices within the scope of the particular CAS. 1. 2. Log in to the Central Analysis Server. In the CAS menu, go to Settings Start RUM Console. Java Web Start-based RUM Console requires Java JRE 6 installed on the desktop. Compuware recommends to use the latest Java JRE 6 update available from the Oracle Web site. Note that Java Web Start-based RUM Console will only run on Windows and a 32-bit JRE. When you launch the Java Web Start-based RUM Console for the first time, or if the application has changed since you last accessed it through Central Analysis Server menu, you have to allow the browser to open the console.jnlp file. The Java Web Start download splash screen appears. Depending on network conditions, this download may take some time. Wait until the download process completes.

Real-User Monitoring Data Center RUM Console Installation Guide

27

Chapter 5 Using Java Web Start-based RUM Console

Refer to Troubleshooting RUM Console [p. 37] if you encounter problems launching the application. 3. Connect to the RUM Console Server. When the application download process completes, the RUM Console opens and attempts to connect to the RUM Console Server using the CAS-provided connection details. When you launch the Java Web Start-based RUM Console for the first time, the RUM Console Server Connection screen appears. The Address field is pre-filled with the CAS-provided RUM Console Server address, however you need to type in the default admin user name and leave the password blank . Click OK to connect to the RUM Console Server. If the connection details are valid, at each consecutive attempt to connect using the same CAS-provided connection details, the user name is also pre-filled. For more information, see Connecting RUM Console to RUM Console Server [p. 16].

Launching Java Web Start-based RUM Console from Windows Shortcut


You can use an automatically created Windows shortcut to launch the RUM Console with the predefined connection details, without the need to open the Central Analysis Server in a browser. To access the shortcut, click the Windows Start button, go to Programs Compuware, and click RUM Console (Web Start). If you open multiple instances of the Java Web Start-based RUM Console, only the most recently accessed application and shortcut are available.

Managing Java Web Start-based RUM Console


Use the Java Application Cache Viewer, part of the Java Web Start software, to manage the Java Web Start-based RUM Console application on your desktop. You can launch Java Application Cache Viewer from the Java Control Panel or by typing javaws -viewer at the command prompt. See Java Web Start documentation for details.

28

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 5 Using Java Web Start-based RUM Console Figure 1. Java Cache Viewer window

You can double-click the application to launch it directly from the Java Cache Viewer window. Note that if you open multiple instances of the Java Web Start-based RUM Console, or if the application has changed since you last accessed it, only the most recently accessed application is available in the Java Cache Viewer.

Uninstalling Java Web Startbased RUM Console


To uninstall the Java Web Startbased RUM Console, use the standard Windows Add or Remove Programs dialog from the Windows Control Panel or use the Java Cache Viewer. If you encounter any problems uninstalling Java Web Startbased RUM Console using the standard Add or Remove Programs dialog from the Windows Control Panel, you should delete the RUM Console application using the Java Application Cache Viewer. 1. 2. 3. Open Java Cache Viewer. For more information, see Managing Java Web Start-based RUM Console [p. 28]. Delete the Java Web Start based RUM Console application. Right-click the RUM Console application and select Delete. Delete all the resources related to the RUM Console. Choose Resources from the Show list at the top of the Java Cache Viewer window and delete all the resources identified by the URL from which you downloaded the RUM Console application.

Real-User Monitoring Data Center RUM Console Installation Guide

29

Chapter 5 Using Java Web Start-based RUM Console

Changing Java Web Start-based RUM Console Connection Properties


When the address or TCP port number of the RUM Console Server changes, you need to enter the new values in the CAS configuration. If you can access the machine where the CAS is installed, this is done by changing configuration details using Windows Control Panel. The address and port number of the Gomez RUM Console are defined during CAS installation or upgrade. When either of the two parameters changes, you can immediately redefine connection properties. To change a previously assigned port number or IP address of theRUM Console Server: 1. On the machine where the CAS or ADS is installed, access Windows Control Panel and open the dialog box for installed software management (for example, Programs and Features). In the list, find the product you want to re-configure, such as Compuware Compuware APM Central Analysis Server ver. 12.0.0 and click Uninstall/Change. A dialog with a set of options opens. Select Change RUM Console Options. The report server service will be stopped and RUM Configuration Connection Properties window opens. Change the IP address or port number as needed. Click Next to confirm modifications to the report server configuration. Finish reconfiguration. After the changes are made, the Change/Remove Summary window will list the changes. Select Start [REPORT_SERVER_TYPE] after the reconfiguration and click Finish to bring the report server online.

2.

3.

4. 5. 6.

To test new settings, start the RUM Console from the CAS menu or Windows menu shortcut. For more information, see Launching Java Web Start-based RUM Console [p. 27] and Launching Java Web Start-based RUM Console from Windows Shortcut [p. 28].

Changing Java Web Start-based RUM Console Connection Properties Remotely


When the address or TCP port number of the RUM Console Server changes, you need to enter the new values in the CAS configuration. If you cannot access the machine where the CAS is installed this is done by changing configuration details in the General Properties Editor. Before You Begin You need administrative rights to perform this task. Log in to the CAS as user with administrative rights and open the Control Panel by typing atscon in your Web browser's Address field:
http://server_IP_address/atscon

30

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 5 Using Java Web Start-based RUM Console

The address and port number of the Gomez RUM Console are defined during the CAS installation or upgrade. When any of the two parameters changes, you can immediately redefine connection properties. 1. 2. In the Control Panel, click General Properties Editor to see configuration properties list. Modify the connection settings. To change the IP address of the RUM Configuration, find CONSOLE_WEBSTART_HOST, type the new address, and then click Set value to save the changes. Leave this empty to use a local installation of the Gomez RUM Console (this is the default). To change the port number of the RUM Configuration, find CONSOLE_WEBSTART_PORT, type the new value, and then click Set value to save the changes. Default value: 4183 To revert changes and return to the default settings, click Restore default for each modified property. You do not need to restart the CAS for the changes to take effect. To test new settings, start the RUM Console from the CAS menu or Windows menu shortcut. For more information, see Launching Java Web Start-based RUM Console [p. 27] and Launching Java Web Start-based RUM Console from Windows Shortcut [p. 28].

Real-User Monitoring Data Center RUM Console Installation Guide

31

Chapter 5 Using Java Web Start-based RUM Console

32

Real-User Monitoring Data Center RUM Console Installation Guide

CHAPTER 6

RUM Console Upgrades


RUM Console should be upgraded to the version corresponding with the other components of Data Center RUM or configuration of important new or enhanced features will not be possible.

Upgrading Standalone RUM Console


Standalone RUM Console means the application that is installed using a regular installation executable, not Java Web Start. You can upgrade RUM Console from a previous version by installing the current version of RUM Console over the existing installation of VCAEUE Console. Before You Begin Before starting an upgrade of RUM Console, be sure that the console client is not running on any user account. If the Windows Task Manager lists a process called cva-client.exe or cva-client.exe *32 but no console is running for the current user, this indicates that another user is running RUM Console. You should log these users out before restarting the upgrade. 1. Select the installation disc that matches your target machine's operating system. 2. DVD1 Windows DVD2 Linux DVD3 AIX HPUX Solaris

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.

Run the RUM Console installation program. Click OK to confirm the upgrade when Existing Product Found On Machine window appears.

Real-User Monitoring Data Center RUM Console Installation Guide

33

Chapter 6 RUM Console Upgrades

The installation program detects the details of your current installation, including product features and installation folder, and attempts to install a new version applying the same options. 4. On the Security Configuration screen, provide the Compuware Security Server settings you want to use, and then click Next. You can install Compuware Security Server locally during this installation or specify the address and port of a remote Compuware Security Server server to use. During the installation and upgrade of the RUM Console, existing user accounts are migrated from the Central Analysis Server database to the Compuware Security Server (CSS), added in release 12.0. If some user accounts did not migrate successfully, a migration record will be created in the CSS database that can be viewed in the RUM Console. For more information, see Identifying and Fixing User Account Migration Exceptions [p. 36]. 5. On the Pre-Installation Summary screen, review the installation options you have selected, and then click Install. The software you have selected will be installed. This may take some time. On the Install Complete screen, click Done. The location of the installation log is displayed on this screen. Be sure to refer to it if errors occurred during installation.

6.

Upgrading Java Web Start-based RUM Console


Some older versions of Java Web Start-based VCAEUE Console are not automatically updated to the new version during upgrade. In such cases, uninstall the previous version. Before You Begin You need a working Central Analysis Server of 12.0 release to launch a new instance of Java Web Start-based RUM Console after uninstalling the previous version. Before starting an upgrade of RUM Console, be sure that the console client is not running on any user account. To upgrade Java Web Start-based VCAEUE Console to RUM Console version 12.0, perform the following steps: 1. Uninstalling Java Web Start-based VCAEUE Console of the previous release. a. Open Java Cache Viewer. For more information, see Managing Java Web Start-based RUM Console [p. 28]. b. Delete Java Web Start based VCAEUE Console application. Right-click the VCAEUE Console application and select Delete. c. Delete all the resources related to the VCAEUE Console. To remove the application completely, delete all the resources related to the VCAEUE Console. Choose Resources from the Show list in the top of the Java Cache Viewer

34

Real-User Monitoring Data Center RUM Console Installation Guide

Chapter 6 RUM Console Upgrades

window and delete all the resources identified by the URL from which you downloaded the VCAEUE Console application. 2. Launching Java Web Start-based RUM Console from Central Analysis Server of 12.0 release. Log in to the Central Analysis Server 12.0 and start Java Web Start-based RUM Console. For more information, see Launching Java Web Start-based RUM Console [p. 27].

Backup and Recovery Procedures


Perform the procedures in this section to save and restore the RUM Console Server database containing the list of users, the Gomez connection settings, and a list of devices that the server manages.

Backing Up RUM Console Server


The RUM Console Server should be backed up manually by copying specific directories to a backup device. Before You Begin The following information is required to back up the RUM Console Server database: Database name. Default: cva Database file location. Default: ..\Compuware\RUM Console\cva\eclipse\workspace\derby\cva 1. 2. 3. Log in as an administrator. Stop the Compuware APM RUM Console service. Copy the ..\Compuware\RUM Console\cva\eclipse\workspace\derby\cva folder to a backup device.

Restoring RUM Console Server


Because AMD configurations are stored on the AMD devices themselves, the data that is required to fully restore the RUM Console Server is the list of users, the Business Service Manager connection settings, a list of devices that the server manages, top application traffic statistics, and span port data. This information is stored in a database that should be available in a backup archive. 1. Install RUM Console using the standard installation procedure. For more information, see Installing RUM Console Server and RUM Console [p. 15]. The installation wizard will create the database structure and a default user account. Stop the Compuware APM RUM Console service.

2.

Real-User Monitoring Data Center RUM Console Installation Guide

35

Chapter 6 RUM Console Upgrades

3. 4. 5. 6.

Delete the contents of the newly installed ..\Compuware\RUM Console\cva\eclipse\workspace\derby\cva directory. Copy the entire ..\Compuware\RUM Console\cva\eclipse\workspace\derby\cva folder from your backup device to its corresponding location on the RUM Console Server. Start the Compuware APM RUM Console service. Connect to the RUM Console Server using RUM Console and examine the configuration, users, device list, and any other properties that you might have set. Assuming that the RUM Console Server is restored properly and the list of devices is recovered, all of the AMD configurations will be read as current configurations. If an AMD configuration is corrupted, an exported configuration could be used as a backup copy and published to that specific AMD. For information on how to export an AMD configuration using the console, see Exporting AMD Configuration in the Real-User Monitoring Data Center Administration Guide.

Restoring RUM Console


To recover the RUM Console, reinstall it. RUM Console is a standalone application that does not store any information within itself. Since it relies on data provided from the RUM Console Server, reinstallation of the console package is sufficient to fully recover the RUM Console. For more information, see Installing, Running, and Uninstalling RUM Console Components [p. 15].

Identifying and Fixing User Account Migration Exceptions


During the installation and upgrade of the RUM Console, existing user accounts are migrated from the Central Analysis Server database to the Compuware Security Server (CSS), added in release 12.0. If some user accounts did not migrate successfully, a migration record will be created in the CSS database that can be viewed in the RUM Console. A typical scenario is that a user or user group already existed in the CSS when the migration occurred. An administrator can identify users or user groups that did not migrate properly, and can rectify the issue if needed in the RUM Console. You can also export a report of migration exceptions. 1. 2. Go to the Guided Configuration perspective and select the User Management task. Select Migration. A list of migration exceptions will be displayed, showing the Principle Name (the user or group that did not migrate) and the reason it did not migrate properly. Click the Show Details icon to display additional information about the user or group that didn't migrate. If needed, manually add the user(s) or group(s) to the CSS. For users, click on the Users link; for groups, the User Group link.

3. 4.

36

Real-User Monitoring Data Center RUM Console Installation Guide

APPENDIX A

Troubleshooting RUM Console


Refer to the information when having problems running both standalone and Java Web Start-based RUM Console. Error Copying the JRE to the destination directory logged during RUM Console upgrade. This message and The process cannot access the file because it is being used by another process in the installation log indicate that RUM Console was running (perhaps on another user's account) when you upgraded the RUM Console installation. RUM Console must be shut down before you can upgrade it. To remedy this issue, shut down RUM Console and then upgrade it. If the Windows Task Manager lists a process called cva-client.exe or cva-client.exe *32 but no console is running for the current user, this indicates that another user is running RUM Console. You should log these users out before restarting the upgrade. The RUM Console uses too much memory. How can I solve the problem? You can control the amount of used memory in several ways: Disable the automatic trace recording in the Guided Configuration perspective. For more information, see Capturing Traffic Traces in the Real-User Monitoring Data Center Web Application Monitoring User Guide. Disable the Guided Configuration connection on some of your AMDs. For more information, see Adding an AMD to the Devices List in the Real-User Monitoring Data Center Web Application Monitoring User Guide. Reset the automatic trace on the Guided Configuration Home page. Use this option carefully, because resetting the trace will cause all the previously gathered statistics to be lost. Restart the Compuware APM RUM Console service using the Windows services.msc utility. 1. 2. 3. Select Start Run. Type the services.msc utility name in the Open box. Click OK.

Real-User Monitoring Data Center RUM Console Installation Guide

37

Appendix A Troubleshooting RUM Console

4.

On the list of the running services, right-click the Compuware APM RUM Console service and select Restart from the context menu.

RUM Console cannot connect RUM Console Server. RUM Console needs to connect to its server components to operate correctly. In vast majority of cases, you will never notice any problems, but in cases when you encounter connectivity issues, the following information will help you troubleshoot the problem.
Table 3. RUM Console connectivity error messages Error message Reason/Meaning

Access denied. Invalid Incorrect password provided for the user. credentials, verify password. Unable to connect to RUM Console Server. Verify connection settings. Unable to connect to RUM Console Server. RUM Console Server is not ready.

RUM Console Server is not responding based on the current connection parameters. Check the connection configuration, that is, RUM Console URL and/or port number.

A corrupted RUM Console database could be one of the causes. You should schedule the RUM Configuration database backup to be able to restore the RUM Console Server functionality in case of the database corruption. Because AMD configurations are stored on the AMD devices themselves, the only data that is required to fully restore the RUM Console Server is the list of users, the devices connection settings, and a list of devices that the server manages. This information is stored in a database that should be available in a backup archive. For more information, see Backing Up RUM Console Server [p. 35] and Restoring RUM Console Server [p. 35].

Authentication error. Connection to Compuware Central Security Server failed.

Compuware Security Server may be down. You cannot authenticate without a working Compuware Security Server.

Java Web Start-based RUM Console will not start and Failed to validate certificate warning appears. Click OK in the bottom of the warning. When the The application's digital signature cannot be verified. warning appears, select Always trust content from this publisher and click Run to start Java Web Start-based RUM Console. Java Web Start-based RUM Console will not start and instead, the system prompts to save or find a program to open the console.jnlp file. The problem is caused by a missing file association for the JNLP files. Navigate to the Microsoft Windows File Types tab in the Folder Options dialog box, click Advanced,

38

Real-User Monitoring Data Center RUM Console Installation Guide

Appendix A Troubleshooting RUM Console

and associate the Launch action for the JNLP files with javaws.exe found in the Java bin directory (such as <install_dir>\bin\javaws.exe). For example:
Figure 2. Associating the JNLP file

An additional instance of Java Web Startbased RUM Console is launched on my desktop after Data Center RUM upgrade. Some older versions of Java Web Start-based VCAEUE Console are not automatically updated to the new version during upgrade. In such cases, uninstall the previous version. For more information, see Uninstalling Java Web Startbased RUM Console [p. 29].

Real-User Monitoring Data Center RUM Console Installation Guide

39

Appendix A Troubleshooting RUM Console

40

Real-User Monitoring Data Center RUM Console Installation Guide

Index

Index

B
backup 35 RUM Console Server 35

M
migrating 33 RUM Console 33 Migration exceptions 36 manually adding to Compuware Security Server 36

C
Compuware APM 19 console 22, 24, 26 See also RUM Console software services 26 users 26 See also RUM Console COS 20 definition 20 RUM Console 20

R
recovery 3536 RUM Console 36 RUM Console Server 35 RUM Console 9, 11, 1516, 1920, 22, 24, 2630, 3437 See also RUM Console backup and recovery 35 capacity status 24 configuring 1516 RUM Console Server - RUM Console connection 16 connecting to server 15 COS 20 Device Information tab 22 Devices tab 20 installing 15 installing server for 15 Java Web Start 2730, 34, 37 recovery 36 Reporting Hierarchy tab 26 RUM Console Server recovery 35 system requirements 11 Tasks tab 20 Transactions tab 24 User-Defined Software Services tab 26 Users tab 26 See also RUM Console RUM Console Server 9, 1516, 35 See also RUM Console Server backing up 35

D
device 1920, 22 adding 19 configuring 19 editing configuration 19 health 22 managing with RUM Console 20 RUM Console tabs 19 status 22

E
Entire Configuration perspective 16

G
Guided Configuration 19

Real-User Monitoring Data Center RUM Console Installation Guide

41

Index
RUM Console Server (continued) configuring 16 RUM Console Server - RUM Console connection 16 installing 15 recovery 35 See also RUM Console Server

T
transaction 19, 24 monitoring 24

U
uninstalling 17 RUM Console 17 upgrading 33 RUM Console 33 standalone RUM Console 33

S
software service 19

42

Real-User Monitoring Data Center RUM Console Installation Guide

You might also like