Professional Documents
Culture Documents
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.
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
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
INTRODUCTION
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.
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/.
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.
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
Menu Item
Screen
Code block
CHAPTER 1
10
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
11
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
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
CAS + CAS SQL database + RUM Console 64 GB Server ADS + ADS SQL database + RUM Console Server 64 GB
12
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)
13
14
CHAPTER 3
Insert the disc into your computer's DVD drive and wait for the media browser to start. If the media browser does not run automatically, run the setup.exe application on the DVD to start the media browser manually. If you have downloaded the product, go to the equivalent folder in your downloaded copy and run the setup.exe application.
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.
15
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.
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
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
17
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
CHAPTER 4
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
19
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.
Configuration User Management This view is a shortcut to the Window Show View menu selections.
20
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
21
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.
22
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.
23
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.
24
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:
25
26
CHAPTER 5
To launch Java Web Start-based RUM Console, you need Microsoft Visual C++ 2008 Redistributable Package (x86) installed on your local machine.
27
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].
28
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.
29
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].
30
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].
31
32
CHAPTER 6
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.
33
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.
34
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].
2.
35
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.
3. 4.
36
APPENDIX A
37
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].
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
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].
39
40
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
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