RUMDC_RUMConsoleInstall

Real-User Monitoring – Data CenterRUM ConsoleInstallation Guide

Release 11.7.0

http://www.gomez.com/

Please direct questions about Real-User Monitoring – Data Center or comments on this document to:

APM Customer SupportFrontLine Support Login Page:

http://go.compuware.com

Copyright © 2011 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of theUnited States.

U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth inCompuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS252.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 withoutthe prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of theuser'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, modifiedor changed without the express written consent of Compuware Corporation. Compuware Corporation may change the contentspecified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found athttp://go.compuware.com.

Compuware, FrontLine, Network Monitoring, Private Enterprise, Server Monitoring, Transaction Trace Analysis, Gomez, Vantagefor Java and .NET Monitoring, VantageView, Gomez, Real-User Monitoring – First Mile, and Gomez Performance Network aretrademarks 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 trademarksof 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: November 18, 2011, 11:06



Contents

5Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Who Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Organization of the Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Customer Support and Online Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Reporting a Problem on Real-User Monitoring – Data Center. . . . . . . . . . . . . . . . . . .8Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9Chapter 1 ∙ Gomez RUM Console – Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . .

11Chapter 2 ∙ System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13Chapter 3 ∙ Installing, Running, and Uninstalling RUM Console Components. . . .13Installing RUM Console Server and RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . .14Connecting RUM Console to RUM Console Server . . . . . . . . . . . . . . . . . . . . . . . . . .15Uninstalling RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17Chapter 4 ∙ RUM Console Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18RUM Console Tasks Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18RUM Console Devices Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20RUM Console Device Information Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22RUM Console Capacity Status Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22RUM Console Transactions Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24RUM Console User-Defined Software Services Tab. . . . . . . . . . . . . . . . . . . . . . . . . .24RUM Console Users Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25RUM Console – Reporting Hierarchy Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27Chapter 5 ∙ Using Java Web Start-based RUM Console. . . . . . . . . . . . . . . . . . . . .27Launching Java Web Start-based RUM Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Launching Java Web Start-based RUM Console from Windows Shortcut. . . . . . . . . . .28Managing Java Web Start-based RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Uninstalling Java Web Start based RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . .30Changing Java Web Start-based RUM Console Connection Properties. . . . . . . . . . . . .31Changing Java Web Start-based RUM Console Connection Properties Remotely. . . . .

3Real-User Monitoring – Data Center RUM Console Installation Guide

Contents

33Chapter 6 ∙ RUM Console Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Upgrading Standalone RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Upgrading Java Web Start-based RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Backup and Recovery Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Backing Up RUM Console Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Restoring RUM Console Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Restoring RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

37Appendix A ∙ Troubleshooting RUM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

41Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Real-User Monitoring – Data Center RUM Console Installation Guide4

Contents

I N T R O D U C T I O N

Who Should Read This GuideThis manual is intended for users of Real-User Monitoring – Data Center who want to installRUM Console and RUM Console Server.

Organization of the GuideThis guide is organized as follows:

• Gomez RUM Console – Overview [p. 9]

• System Requirements [p. 11]

• Installing, Running, and Uninstalling RUM Console Components [p. 13]

• RUM Console Navigation [p. 17]

• Using Java Web Start-based RUM Console [p. 27]

• RUM Console Upgrades [p. 33]

Related PublicationsDocumentation for your product is distributed on the product media. For Data Center RUM, itis 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 supportsite at http://go.compuware.com. FrontLine provides fast access to information about yourCompuware products. You can download documentation and FAQs as well as browse, askquestions and get answers on user forums (requires subscription). The first time you accessFrontLine, 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 Readerapplication installed, you can download the setup file from the Adobe Web site athttp://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 Compuwaresite provides a variety of product and support information.

FrontLine support Web site

You can access online customer support for Compuware products via our FrontLine supportsite at http://go.compuware.com. FrontLine provides fast access to critical information aboutyour 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 thehttp://go.compuware.com Web site.All high-priority issues should be reported by phone.

Reporting a Problem on Real-User Monitoring – DataCenter

When calling, please provide Customer Support with as much information as possible aboutyour 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 salescontract.

• The version number of the Agentless Monitoring Device (AMD) , the report servers andRUM Console with RUM Console Server.

For the report serverUse the report server GUI by selecting Help ➤ Product Information ➤ About, orTools ➤ Diagnostics ➤ System Status.

For the AMDScroll down to the Testing AMD section. At the bottom of the diagnostic dataparagraph, look for Version ND-RTM v. ndw.ww.x.y.zz.

For the RUM Console and RUM Console ServerUse the RUM Console GUI by selecting Help ➤ About menu item.


Introduction

http://www.adobe.com/downloads/

http://www.compuware.com



For the TCAMUse the TCAM GUI by selecting Help ➤ About menu item.

• Environment information, such as the operating system and release (including service packlevel) on which the product (AMD, report server) is installed, memory, hardware/networkspecifications, and the names and releases of other applications that were running.Problem description, including screenshots.

• Exact error messages, if any (screenshots recommended).

• Whether or not the problem is reproducible. If yes, include a sequence of steps for problemrecreation. 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 andtheir results.

• Debug information as follows:

Information from the report server◦ Log files from http://report_server_IP/root/log/ and watchdog.log from

the C:\Program Files\Common Files\Compuware\Watchdog directory.

◦ Configuration file: http://report_server_IP/ExportConfig

◦ Screenshots of the problem.

Information from the AMDLog files from /var/log/adlex/: rtm.log, rtm.log.1, rtm_perf.log,rtm_perf.log.1.

Information from the RUM Console◦ The installation log file, other log files and the version file.

To export all the information, navigate to Tools ➤ Diagnostic InformationExport in the RUM Console menu.

◦ The configuration information for the selected report servers.To export the information for a specific ADS or CAS, right-click the device onthe Devices tab in the RUM Console and choose Diagnostic Information Exportfrom the context menu.

Information from the TCAMSystem Event log of the machine where the TCAM is operating.

NOTEPlease compress all the files before sending them to Customer Support.

Compuware values your comments and suggestions about the Gomez products anddocumentation. Your feedback is very important to us. If you have questions or suggestions forimprovement, please let us know.


Introduction

Documentation ConventionsThe following font conventions are used throughout documentation:

IndicatesThis font

Terms, commands, and references to names of screen controls and userinterface elements.

Bold

Emphasized, text, inline citations, titles of external books or articles.Citation

Links to Internet resources and linked references to titles in Compuwaredocumentation.

DocumentationConventions [p. 8]

Cited contents of text files, inline examples of code, command line inputs orsystem outputs. Also file and path names.

Fixed width

User input in console commands.Fixed width bold

Place holders for values of strings, for example as in the command:Fixed width italic

cd directory_name

Menu items.Menu ➤ Item

Text screen shots.Screen

Blocks of code or fragments of text files.Code block


Introduction

C H A P T E R 1

Gomez RUM Console – Overview

Gomez RUM Console consists of two components:

RUM Console ServerA back-end server application that maintains configuration images and device information,runs tasks related to configuration management, and provides a Web services API forRUM Console to manage configurations. The server is a Windows-based service that canbe installed on a machine with Windows 2003 Server or Windows 2008 Server R2 witha network connection to all of the managed devices within the Gomez infrastructure.

RUM ConsoleA GUI application for configuring report servers and data collectors. With the console,you can create and edit configurations for Gomez devices and propagate such configurationsto other Gomez devices.

Both components are required to be installed, but not necessarily on the same machine: you caninstall the server on a separate machine, in which case the console can connect to the serverover HTTPS.

NOTE

• You should use only one installation of RUM Console Server to configure a specific deviceor group of devices in your Gomez infrastructure. If you choose to use more than oneinstance of RUM Console Server, each server should be used to manage a different groupof devices. Otherwise, Gomez users working simultaneously on different instances of RUMConsole Server could overwrite one another's configurations.

• Configuring a device with the Guided Configuration perspective is possible only withone RUM Console Server connection at a time; if you try to connect using another RUMConsole Server, the Connection status section for the device will show a Could notregister manager at agent message for the Guided Configuration and you will notbe able to perform any tasks using the Guided Configuration perspective. For moreinformation, see Working with Guided Configuration Perspective in RUM Console in theRUM Console – Online Help.



Chapter 1 ∙ Gomez RUM Console – Overview

C H A P T E R 2

System Requirements

You can install RUM Console on a Microsoft Windows machine, dedicated or shared with otherData Center RUM components.A RUM Console platform should meet or exceed the following requirements.

RUM Console Server.Operating System

Windows 2003 Server/ Windows 2008 Server R2Java

Proper version bundled with the installation.CPUs

Quad-core class.Memory

8 GB RAM, minimum. 1.5 GB free memory for Gomez RUM Console service (2.5GB recommended).In case of large setups (70 or more devices added to the RUM Console), Compuwarerecommends to modify the memory setting for the Gomez RUM Console service.In such case, edit the wrapper.conf file from ..\Compuware\RUMConsole\cva\eclipse\configuration and change the propertywrapper.java.maxmemory=1024

towrapper.java.maxmemory=2048

RUM Console (standalone console software installation without server)Operating System

2003 Server/ Windows 2008 Server R2 and Windows XP/Vista/Windows 7Java

Proper version bundled with the installation.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 theOracle Web site. Note that Java Web Start-based RUM Console will only run onWindows and a 32-bit JRE.


http://www.oracle.com/technetwork/java/javase/downloads/index.html

CPUsDual-core class.

Memory4 GB RAM, at least 1 GB free memory.

RUM Console Server is very often installed with other Data Center RUM components on thesame machine. Particular sets of components installed on one machine require specific systemparameters. For more information, see General Hardware Requirements in the Real-UserMonitoring - Data Center – Hardware Recommendations.


Chapter 2 ∙ System Requirements

C H A P T E R 3

Installing, Running, and Uninstalling RUM ConsoleComponents

To use the RUM Console, you must install it, establish a connection between it and the RUMConsole Server, and configure some basic settings.

Installing RUM Console Server and RUM Console1. Select the appropriate installation disc for the target machine.

• 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 theDVD to start the media browser manually.

3. The media browser opens to the Components/Upgrades tab.The media browser has two tabs:

Components/UpgradesThe options on this tab are for creating fresh software installations or upgradingexisting installations.There are two views of this tab:

HomeThis view shows all of the Gomez On-Premises installation and upgrade optionsavailable on this disc.

Classic ViewThis view shows exactly the same installation and upgrade options, but it refersto them by their old product names. You may find this useful as you upgradeolder installations.


UtilitiesThe options on this tab are for upgrading other software to use in conjunction withyour Gomez On-Premises software.

4. Run the RUM Console installation program.• On the Home tab, click Real User Monitoring Console, or

• On the Classic View tab, click Configuration Console for Agentless.

Either selection starts the installation program.

5. On the Introduction screen, read the introduction and then click Next.6. On the License Agreement screen, indicate that you have read and accepted the license

agreement, and then click Next.7. 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.

• Console Installation – installs only the console software.

• Custom – installs selected items as needed.

8. If you selected Custom in the previous step, now select the components you want to installand then click Next.

9. On the Choose Install Folder screen, indicate where you want to install the software, andthen click Next.

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.

Connecting RUM Console to RUM Console ServerTo use the RUM Console, you must first connect to the RUM Console Server. This process isstarted automatically when you provide with the correct URL and administrative user credentials.It is very important to keep all of the device times synchronized. Ensure that the RUM ConsoleServer is synchronized with RUM Console, and any other report servers and monitoring devicesthat this RUM Console manages. For more information, see Synchronizing Time Using NTPServer in the Real-User Monitoring - Data Center – Agentless Monitoring Device – InstallationGuide and Time Synchronization Between AMD and Server in the Real-User Monitoring - DataCenter – Administration Guide.To connect to RUM Console Server:

1. Double-click the RUM Console icon.2. Enter the RUM Console Server address in the Address field.

Because communication between RUM Console and RUM Console Server occurs overHTTPS, it is important to indicate the protocol and the specific port that will be used. Forexample:


Chapter 3 ∙ Installing, Running, and Uninstalling RUM Console Components

https://192.168.129.1:4183

where 4183, the specified port number, is the default port for communicating with RUMConsole Server.

3. 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.

4. Enter the password for the user.5. Click OK to connect to RUM Console Server.

RUM Console, by default, opens the Entire Configuration perspective with the most commonviews: Tasks, Devices, Transactions, User-Defined Software Services, Reporting Hierarchyand Device Information. Each of these views can be closed, minimized, or attached to a differentview panel. To restore all the views to a default configuration, select the menu item Window ➤Restore Defaults.Refer to RUM Console cannot connect RUM Console Server. [p. 38] if you encounter problemsin connecting RUM Console to RUM Console Server

Uninstalling RUM ConsoleUninstallation of RUM Console can be done via Add or Remove Programs or Programs andFeatures in Windows Control Panel.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:• Double-click Add or Remove Programs

• Click Uninstall a program in the Programs and Features section

2. Double-click the RUM Console entry.This will launch the installation program.

3. 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 Consoleinstallation.



C H A P T E R 4

RUM Console Navigation

RUM Console enables you to view and modify all aspects of system configuration within theGomez 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 entitiescan often be accessed in different ways, depending on your need. In particular, this applies tosoftware services, which can be managed through devices or independently.RUM Console screens are grouped into two perspectives: Guided Configuration and EntireConfiguration. Use the buttons in the top left part of the RUM Console to switch between theperspectives.The most important features of the Guided Configuration perspective include:

• A step-by-step guide to configuring application traffic monitoring for first-time Gomezusers.

• 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 thesoftware service definitions.

• A preview of the HTTP, HTTPS, XML, SOAP and SSL (undecrypted) top applicationtraffic categories, which can streamline the configuration process by narrowing down thenumber of servers available for a software service definition. For example, you can selecta number of URLs from the list of the most frequently occurring URLs and then use theselected URLs to filter available servers.

• A wizard-based process for creating and editing software services, which helps you manageyour software services and service rule definitions more effectively.

• An interface for importing Gomez Performance Network test definitions and integratingperformance measurements obtained from the GPN and Data Center RUM.

The main parts of the Entire Configuration perspective include the following:

Devices tabLists report servers and also traffic monitoring devices that can be assigned to reportservers. The configurations of these devices can be opened individually, and within each


device configuration you can define and configure software services and transactions tobe monitored by that device.

Transactions tabIt can be used to define transactions for a number of monitoring devices simultaneously.

User-Defined Software Services tabGroups 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 morenatural to perform most of your software service configuration from within that deviceconfiguration. However, if you are using a number of monitoring devices, you may findit useful to create and manage software service definitions under the User-DefinedSoftware Services tab, independently of devices.

Reporting Hierarchy tabThe Reporting Hierarchy view presents the reporting hierarchy that is specific for agiven application and has been imported from an external CSV file and mapped to theGomez reporting hierarchy.

Tasks tabThe Tasks view presents all available business objects and configuration areas for theRUM Console.

RUM Console Tasks TabThe Tasks view presents all available business objects and configuration areas for the RUMConsole.Objects are grouped into categories:

Business objects• Devices

• User-defined software services

• Transactions

• Reporting hierarchy

Configuration• Users

This view is a shortcut to the Window ➤ Show View menu selections.

RUM Console Devices TabThe Devices tab on the RUM Console is a part of the Entire Configuration perspective andlists all of the devices within your Gomez deployment. Using the console, you can add, edit,and remove device connection configurations for any Gomez-supported device or server.The Devices pane is arranged in a table and an informational tab. Click the Device Informationtab to see details of the device currently selected in the table.


Chapter 4 ∙ RUM Console Navigation

RUM Console device types

Device types that can appear on the Devices tab include:

AMDAn Agentless Monitoring Device. In addition to setting up general connection properties,you can also perform in-depth configuration of Global and Monitoring properties. Formore information, see Managing Devices in the Real-User Monitoring - Data Center –Administration Guide and Basic Monitoring Configuration in the RUM Console – OnlineHelp.

Unsupported AMDAn Agentless Monitoring Device of a version 11.5 and earlier. You may be able to seesome information about such a device in the console, but you cannot use the console toconfigure it.

CASA Central Analysis Server, which can be administered by assigning, editing, and removingprobes in its configuration. You can also enable or disable these probes and mark themto 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 Serverin the Settings top menu of the report server. Since the Console already knows superusercredentials it is able to display configuration screens directly from the report server withoutthe need to log in. Configuration tools open in the lower section of the main screen.

ADSAn 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 theseprobes and mark them to be managed in the console Devices table independently of thedefined server connection.

Java/.NET Monitoring ManagerBesides publishing the configuration through COS, you can use RUM Console to publishthe 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 Consolepublishes all of the AMD device configurations to the Java/.NET Monitoring Managerautomatically. Similarly, after the AMD device configuration is altered and a draftconfiguration is published to the AMD, the console automatically updates the configurationand publishes it to the Java/.NET Monitoring Manager.

Flow CollectorA legacy Network Monitoring Flow Collector that analyzes the traffic processed bynetflow-enabled routers.

Cisco NAMCisco Network Analysis Module (NAM) Traffic Analyzer.

Gomez Synthetic Monitoring – Private Enterprise Agent ManagerA device recognized as Gomez Synthetic Monitoring – Private Enterprise Agent Managervia its Web service. This is for informational purposes only; the console only monitorsthe connection to that device.



GFM ApplianceFirst Mile Appliance is a performance data collection service that is used to measure yourHTTP and HTTPS based application performance within your infrastructure.First MileAppliance uses a device called the GFM Appliance to feed the Gomez PerformanceNetwork with data collected during monitoring your web servers. Along with your existingGomez Platform service, GFM Appliance gathers information on both sides of the firewallin order to generate a comprehensive view of your application performance.

TFPTransaction Following Processor, software that gathers data from AMDs, correlates it fortransaction following, and sends it to a CAS.

BSMConnection Manager for Business Service Manager. Adding it as a device to the RUMConsole, enables you to assign it to CAS or ADS so that they can receive data importedby its input adapter from Cerner Real-Time Management System (RTMS).

WANA Network Monitoring Probe configured to monitor a WAN link.

LANA Network Monitoring Probe configured to monitor a LAN link.

OtherA Web server that is not recognized as part of the Gomez suite.

RUM Console Device Information TabThe Device Information tab is a part of the Entire Configuration perspective and presents abrief status view of the selected device.

Connection StatusPresents information about the current connection status and reports any connection errors(including the response received from a connection query).

Health StatusPresents information on the health status of individual processes and versions of theselected device. This information is available for AMD-type devices and Central AnalysisServer.If you select a Central Analysis Server or AMD, the Health status section of the DeviceInformation tab presents the summary of the Capacity status report: Click the CapacityStatus 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 memorythreshold. By default, the memory threshold is set to 80%, and if it is exceeded,a memory alert is raised.

• Number of sessions shows how many sessions are stored in the server cachememory.



• Average data file processing time shows the average data file processing timeversus the predefined threshold during the last 24 hours, and whether the longprocessing time alert was raised. By default, the threshold for data processingtime is set to 60% of the monitoring interval.

• The Nightly tasks execution time section shows how long (on average for aselected period of time) it took to execute three tasks:

Daily Report GenerationData aggregation, calculation of trends and baselines, pre-defined DMIreports, and processing other data required for rendering reports.

DBDailyMaintenanceData aging, cleaning caches, database daily maintenance of sites, domains,and finding new sites and servers to monitor.

RTMDailyDataStoreClosing the current day before storing performance data for the start ofthe next day.

Nightly tasks execution time also shows whether the execution time for anyof the above tasks exceeded the predefined timeout, raising the long executiontime alert.

• Business Units shows the number of defined tiers, reporting groups andapplications in each reported period.

• Business Units Associations shows the number of associations between thebusiness units and sessions as defined by a combination client, server and URL.

AMDMemory performance

Memory performance indicator expressed as the amount of memory used byAMD data objects. This is equal to the number of object multiplied by the sizeof the objects.

CPU performanceCPU performance indicator expressed as CPU usage per thread expressed inpercent.

Disk performanceDisk performance indicator expressed as the percentage of occupied disk spaceon AMD.

Drop performanceDrop performance indicator expressed as percentage of dropped packets fromreceived packets.

The AMD status information is provided by a Central Analysis Server, therefore you needboth AMD and CAS added to your RUM Console and both devices must be connectedto each other.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 StatusPresents the Current, Draft, and Pending status of a configuration file. The Currentconfiguration indicates the publishing time and date, while the Draft and Pendingconfigurations indicate whether a draft configuration is present or configuration publishingis pending.

Sniffing Point DiagnosticsSniffing Point Diagnostics is a type of hardware state analysis that enables you to performpre-monitoring tasks without the need to access the AMD terminal.A separate set ofstatistics 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 Diagnosticssection.Statistics and messages shown in this section are taken based on the latest recorded traffictrace. If you have several traces recorded you will always see data for the newest trafficsample. Note that this data is not related to the current state of the AMD and some statisticsmay be visible even when the device is down.

NOTEIf a device within your Gomez infrastructure is unable to report detailed status information tothe manager, some sections may report that the information is unavailable. This does not indicatea problem with a device.

RUM Console Capacity Status ReportThe Capacity Status reports for Central Analysis Server and AMD are extensions of theinformation 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 andAMD Statistics in the Real-User Monitoring - Data Center – Administration Guide.

RUM Console Transactions TabThe Transactions tab in the RUM Console is a part of the Entire Configuration perspectiveand 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 functionsperformed by a human user or a client program. They are viewed as higher-level units ofself-contained functionality and are tied to applications. For example, they may represent theprocedure for an online purchase or ticket booking. AMD monitors traffic data and prepares itfor transaction monitoring by an ADS and CAS. Some of the relevant configuration andprocessing is performed on the actual RUM Console and some is performed on the AMD. SeeConfiguring AMD to Monitor HTTP-based Transactions in the RUM Console – Online Help



and Configuring AMD to Monitor XML-based Transactions in the RUM Console – Online Helpfor 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 XMLtransactions, or as sequences of SAP GUI operations.

Browsing transactions

To browse transactions and examine which group of AMDs monitor a particular transaction,select the Transactions tab, find the transaction that you want to examine, and expand the list.

Transaction NameThe name of a transaction.

Application NameThe application that includes the listed transaction.

TypeThe protocol used to define the listed transaction: ASYNC-HTTP, CERNER, CERNER-RTMS,HTTP, OF, SAP GUI, SQL or XML.

Packaged ApplicationsWhether the listed transaction is a packaged application whose transactions are recognizedby the report server automatically.

You can expand the transaction list to view the AMDs that monitor this transaction.Right-click to open a menu of transaction-related actions:

Add TransactionOpens the Create Transaction screen, where you can select the AMD devices that willmonitor this new transaction.

Delete TransactionDeletes the selected transactions, updating all affected AMD configurations.

NOTEIf the transaction being deleted is monitored by more than one AMD, all of the affectedAMDs will have a new draft configuration that will have to be published.

OpenOpens the selected transaction for editing.

CloneCreates a clone of the selected transaction and appends an identifier to the clonedtransaction name.

Copy...Copies the selected transactions to another AMD.

While the transactions list is expanded and a specific AMD is selected, the right-click menuoptions are limited to:

• Add Transaction

• Delete Transaction

• Open.



RUM Console User-Defined Software Services TabThe User-Defined Software Services tab is a part of the Entire Configuration perspectiveand lists all software services within your Gomez deployment. Through the console, you canadd, 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 containsinformation about all user-defined software services created on all devices managed via thisconsole. From here you can manage services, add new ones, delete existing ones, and copythem across AMDs. Note that default software services are specific to a single AMD and cannotbe managed centrally.For more information, see Basic Monitoring Configuration in the RUM Console – Online Helpand Managing User-Defined Software Services in the RUM Console – Online Help.

RUM Console Users TabThe RUM Console Users tab is a part of the Entire Configuration perspective and enablesyou to manage all user accounts for a console.The Users tab, which appears in the lower pane of the console when you click Users, listsconsole users.

NOTEThe default admin account cannot be removed or renamed. The only permissible actions onthat account are password creation and password change.

Right-click to open a menu of user-related command options:

Add a new userRight-click in the Users table and select Add a new user to open the Add New Userwindow, or alternatively, click the icon located to the right of the Users tab.Type the new user's User ID, type the user's password in Password, and Confirmpassword, and then click OK to add that user.

Edit userRight-click a user and select Edit user to open the Edit User window for the selecteduser. To change the selected user's password, type the current password, type the newpassword twice, and then click OK to change that user's password.You cannot change the user ID displayed here, but, to the same effect, you can delete anunwanted user ID and add a user ID with the name you want to use.

Delete userRight-click a user and select Delete user to open the Delete Confirmation message box,and then click OK to delete the selected user.



RUM Console – Reporting Hierarchy TabThe Reporting Hierarchy view presents the reporting hierarchy that is specific for a givenapplication and has been imported from an external CSV file and mapped to the Gomez reportinghierarchy.For more information, see Importing the Reporting Hierarchy in RUM Console in the Real-UserMonitoring - Data Center – Administration Guide.



C H A P T E R 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 WebStart-based RUM Console [p. 28].

• From the Windows shortcut. For more information, see Launching Java Web Start-basedRUM Console from Windows Shortcut [p. 28].

Launching Java Web Start-based RUM ConsoleAccess the RUM Console from a Central Analysis Server menu to configure the devices withinthe scope of the particular CAS.

1. Log in to the Central Analysis Server.

2. 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 OracleWeb site. Note that Java Web Start-based RUM Console will only run on Windows and a32-bit JRE.When you launch the Java Web Start-based RUM Console for the first time, or if theapplication 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 downloadsplash screen appears.Depending on network conditions, this download may take some time. Wait until thedownload process completes.Refer to Troubleshooting RUM Console [p. 37] if you encounter problems launching theapplication.


http://www.oracle.com/technetwork/java/javase/downloads/index.html

3. Connect to the RUM Console Server.When the application download process completes, the RUM Console opens and attemptsto 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 RUMConsole Server Connection screen appears. The Address field is pre-filled with theCAS-provided RUM Console Server address, however you need to type in the defaultadmin user name and leave the password blank . Click OK to connect to the RUM ConsoleServer.If the connection details are valid, at each consecutive attempt to connect using the sameCAS-provided connection details, the user name is also pre-filled. For more information,see Connecting RUM Console to RUM Console Server [p. 14].

Launching Java Web Start-based RUM Console fromWindows Shortcut

You can use an automatically created Windows shortcut to launch the RUM Console with thepredefined 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, andclick RUM Console (Web Start).If you open multiple instances of the Java Web Start-based RUM Console, only the most recentlyaccessed application and shortcut are available.

Managing Java Web Start-based RUM ConsoleUse the Java Application Cache Viewer, part of the Java Web Start software, to manage theJava 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.


Chapter 5 ∙ Using Java Web Start-based RUM Console

http://www.java.com/en/download/faq/java_webstart.xml

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 theapplication has changed since you last accessed it, only the most recently accessed applicationis available in the Java Cache Viewer.

Uninstalling Java Web Start based RUM ConsoleYou can uninstall the Java Web Start-based RUM Console by using the standard Add or RemovePrograms dialog from the Windows Control Panel or by using Java Cache Viewer.If you encounter any problems uninstalling Java Web Start based RUM Console using thestandard Add or Remove Programs dialog from the Windows Control Panel, you shoulddelete the RUM Console application using the Java Application Cache Viewer.

1. Open Java Cache Viewer.For more information, see Managing Java Web Start-based RUM Console [p. 28].

2. Delete Java Web Start based RUM Console application.Right-click the RUM Console application and select Delete.

3. Delete all the resources related to the RUM Console.To remove the application completely, delete all the resources related to the RUM Console.Choose Resources from the Show list in the top of the Java Cache Viewer window anddelete all the resources identified by the URL from which you downloaded the RUMConsole application.



Changing Java Web Start-based RUM ConsoleConnection Properties

When the address or TCP port number of the RUM Console Server changes, you need to enterthe new values in the CAS configuration. If you can access the machine where the CAS isinstalled, 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 installationor upgrade. When either of the two parameters changes, you can immediately redefine connectionproperties. To change a previously assigned port number or IP address of theRUM ConsoleServer:

1. On the machine where the CAS or ADS is installed, access Windows Control Panel andopen the dialog box for installed software management (for example, Programs andFeatures).

2. In the list, find the product you want to re-configure, such as Compuware Gomez CentralAnalysis Server ver. 11.7.0 and click Uninstall/Change.A dialog with a set of options opens.

3. Select Change RUM Console Options.The report server service will be stopped and RUM Configuration Connection Propertieswindow opens.

4. Apply the requested changes.• If you installed the RUM Configuration with default settings and on the same machine

where you are installing the CAS, leave the options unchanged and click Next toproceed with installation.

• For remote RUM Configuration installation, clear Local RUM Configurationinstallation and type the IP address of the host where the RUM Console Server isrunning.

5. Click Next to confirm modifications to the report server configuration.6. 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 bringthe report server online.

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] andLaunching Java Web Start-based RUM Console from Windows Shortcut [p. 28].



Changing Java Web Start-based RUM ConsoleConnection Properties Remotely

When the address or TCP port number of the RUM Console Server changes, you need to enterthe new values in the CAS configuration. If you cannot access the machine where the CAS isinstalled this is done by changing configuration details in the General Properties Editor.

Prerequisites

You need administrative rights to perform this task. Log in to the CAS as superuser and openthe Control Panel by typing atscon in your Web browser's Address field:http://server_IP_address/atscon

The address and port number of the Gomez RUM Console are defined during the CASinstallation or upgrade. When any of the two parameters changes, you can immediately redefineconnection properties.

1. In the Control Panel, click General Properties Editor to see configuration properties list.2. 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 thedefault).

• 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 modifiedproperty. 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] andLaunching Java Web Start-based RUM Console from Windows Shortcut [p. 28].



C H A P T E R 6

RUM Console Upgrades

RUM Console should be upgraded to the version corresponding with the other components ofData Center RUM, otherwise configuration of important new or enhanced features will notpossible.

Upgrading Standalone RUM ConsoleStandalone RUM Console means the application, which is installed using a regular installationexecutable, not Java Web Start. You can upgrade RUM Console from a previous version byinstalling the current version of RUM Console over the existing installation of VCAEUE Console.

Prerequisites

Before starting an upgrade of RUM Console, be sure that the console client is not running onany user account.

1. Select the appropriate installation disc for the target machine.

• 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 theDVD to start the media browser manually.

3. The media browser opens to the Components/Upgrades tab.The media browser has two tabs:

Components/UpgradesThe options on this tab are for creating fresh software installations or upgradingexisting installations.There are two views of this tab:


HomeThis view shows all of the Gomez On-Premises installation and upgrade optionsavailable on this disc.

Classic ViewThis view shows exactly the same installation and upgrade options, but it refersto them by their old product names. You may find this useful as you upgradeolder installations.

UtilitiesThe options on this tab are for upgrading other software to use in conjunction withyour Gomez On-Premises software.

4. Run the RUM Console installation program.Click OK to confirm the upgrade when Existing Product Found On Machine windowappears.The installation program detects the details of your current installation, including productfeatures and installation folder, and attempts to install a new version applying the sameoptions.

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.

6. On the Install Complete screen, click Done.

Upgrading Java Web Start-based RUM ConsoleIn the 11.7 release, RUM Console can only communicate with the RUM Console Server overHTTPS. If your existing installation of Java Web Start-based VCAEUE Console of a previousrelease communicated with a VCAEUE Server over HTTP, it will not automatically update tothe new version. In such case, you have to uninstall the previous version.

Prerequisites

You need a working Central Analysis Server of 11.7 release to launch a new instance of JavaWeb 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 onany user account.

To upgrade Java Web Start-based VCAEUE Console to RUM Console version 11.7, performthe 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.


Chapter 6 ∙ RUM Console Upgrades

c. Delete all the resources related to the VCAEUE Console.To remove the application completely, delete all the resources related to the VCAEUEConsole. Choose Resources from the Show list in the top of the Java Cache Viewerwindow and delete all the resources identified by the URL from which you downloadedthe VCAEUE Console application.

2. Launching Java Web Start-based RUM Console from Central Analysis Server of 11.7release.Log in to the Central Analysis Server 11.7 and start Java Web Start-based RUM Console.For more information, see Launching Java Web Start-based RUM Console [p. 27].

Backup and Recovery ProceduresPerform the procedures below to save and restore theRUM Console Server database containingis the list of users, the Gomez connection settings, and a list of devices that the server manages.

Backing Up RUM Console ServerThe RUM Console Server should be backed up manually by copying specific directories to abackup device.

Prerequisites

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

To back up the RUM Console Server database:

1. Log in as an administrator.2. Stop the Gomez RUM Console service.3. Copy the ..\Compuware\RUM Console\cva\eclipse\workspace\derby\cva folder

to a backup device.

Restoring RUM Console ServerBecause AMD configurations are stored on the AMD devices themselves, the data that is requiredto fully restore the RUM Console Server is the list of users, the Business Service Managerconnection settings, a list of devices that the server manages, top application traffic statisticsand span port data. This information is stored in a database that should be available in a backuparchive.

1. Install RUM Console using the standard installation procedure. For more information, seeInstalling RUM Console Server and RUM Console [p. 13].



The installation wizard will create the database structure and a default user account.

2. Stop the Gomez RUM Console service.3. Delete the contents of fresh installed ..\Compuware\RUM

Console\cva\eclipse\workspace\derby\cva directory.4. 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.5. Start the Gomez RUM Console service.6. 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 isrecovered, all of the AMD configurations will be read as current configurations. If an AMDconfiguration is corrupted, an exported configuration could be used as a backup copy andpublished to that specific AMD. For information on how to export an AMD configurationusing the console, see Exporting AMD Configuration in the Real-User Monitoring - DataCenter – Administration Guide.

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



A P P E N D I X A

Troubleshooting RUM Console

Refer to the information when having problems running both standalone and Java WebStart-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 anotherprocess” in the installation log indicate that RUM Console was running (perhaps on anotheruser's account) when you upgraded the RUM Console installation. RUM Console mustbe 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 runningRUM 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. Formore information, see Capturing Traffic Traces in the RUM Console – Online Help.

• Disable the Guided Configuration connection on some of your AMDs. For moreinformation, 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 optioncarefully, because resetting the trace will cause all the previously gathered statisticsto be lost.

• Restart the Gomez RUM Console service using the Windows services.msc utility.

1. Select Start ➤ Run.

2. Type the services.msc utility name in the Open box.

3. Click OK.

4. On the list of the running services, right-click the Gomez RUM Console serviceand 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 vastmajority of cases, you will never notice any problems, but in cases when you encounterconnectivity issues, the following information will help you troubleshoot the problem.

Table 1. RUM Console connectivity error messages

Reason/MeaningError message

The user account does not exist.Unable to connect to

RUM Console Server.

Verify user name.

Incorrect password provided for the user.Unable to connect to

RUM Console Server.

Verify password.

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

Unable to connect to

RUM Console Server.

Verify connection

settings.

A corrupted RUM Console database could be one of the causes.You should schedule the RUM Configuration database backup to

Unable to connect to

RUM Console Server.

be able to restore the RUM Console Server functionality in caseRUM Console Server is

not ready. of the database corruption. Because AMD configurations are storedon the AMD devices themselves, the only data that is required tofully restore the RUM Console Server is the list of users, thedevices connection settings, and a list of devices that the servermanages. This information is stored in a database that should beavailable in a backup archive.For more information, see Backing Up RUM Console Server[p. 35] and Restoring RUM Console Server [p. 35].

Java Web Start-based RUM Console will not start and Failed to validate certificate warningappears.

In such case, click OK in the bottom of the warning. When The application's digitalsignature cannot be verified. warning appears, select Always trust content from thispublisher 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 tosave or find a program to open the console.jnlp file.

The problem is caused by a missing file association for the JNLP files. In such case,navigate to the MS Windows File Types tab in the Folder Options dialog, click Advancedand associate the Launch action for the JNLP files with javaws.exe found in the Javabin directory, for example C:\Program Files\java\jre6\bin\javaws.exe. See theexample association below:


Appendix A ∙ Troubleshooting RUM Console

Figure 2. Associating the JNLP file

An additional instance of Java Web Start-based RUM Console is launched on my desktopafter Data Center RUM upgrade to the 11.7 release.

In the 11.7 release, RUM Console can only communicate with the RUM Console Serverover HTTPS. If your existing installation of Java Web Start-based VCAEUE Console ofa previous release communicated with a VCAEUE Server over HTTP, it will notautomatically update to the new version. In such case, you have to uninstall the previousversion. For more information, see Uninstalling Java Web Start based RUM Console[p. 29].



Index

Bbackup

35RUM Console Server 35

Cconsole 20, 22, 24

See also RUM Consolesoftware services 24users 24

See also RUM ConsoleCOS

18definition 18RUM Console 18

Ddevice

17–18, 20adding 17configuring 17editing configuration 17health 20managing with RUM Console 18RUM Console tabs 17status 20

EEntire Configuration perspective 14

GGomez 17Guided Configuration 17

Mmigrating

33RUM Console 33

Rrecovery

35–36RUM Console 36RUM Console Server 35

RUM Console 9, 11, 13–14, 17–18, 20, 22, 24–25, 27–31, 34–37

See also RUM Consolebackup and recovery 35capacity status 22configuring

13–14RUM Console Server - RUM Console connection 14

connecting to server 13COS 18Device Information tab 20Devices tab 18installing 13installing server for 13Java Web Start 27–31, 34, 37recovery 36Reporting Hierarchy tab 25RUM Console Server recovery 35system requirements 11Tasks tab 18Transactions tab 22User-Defined Software Services tab 24Users tab 24

See also RUM ConsoleRUM Console Server 9, 13–14, 35

See also RUM Console Serverbacking up 35configuring

14


Index

RUM Console Server (continued)configuring (continued)

RUM Console Server - RUM Console connection 14installing 13recovery 35

See also RUM Console Server

Ssoftware service 17

Ttransaction

17, 22monitoring 22

Uuninstalling

15RUM Console 15

upgrading33

RUM Console 33standalone RUM Console 33


Index

RUMDC_RUMConsoleInstall

Documents

Transcript of RUMDC_RUMConsoleInstall