Compuware APM Product Upgrade and Migration ... - … this document, upgrade is the ... product...

Compuware APMProduct Upgrade and MigrationInstallation Guide

Release 12.2

http://www.compuware.com/

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

APM Customer SupportFrontLine Support Login Page:

http://go.compuware.com

Copyright © 2014 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, Compuware APM, Data Center Real User Monitoring, Synthetic Monitoring, Network Monitoring, Server Monitoring,VantageView, and FrontLine are trademarks or registered trademarks of Compuware Corporation.

Micro Focus QALoad and all other Micro Focus brand and product names are trademarks or registered trademarks of MicroFocus or its subsidiaries in the UK and other countries.

Adobe® Reader® is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries.

All other company and product names are trademarks or registered trademarks of their respective owners.

Local Build: January 8, 2014, 11:22



Contents

7Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Organization of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10Customer Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13Chapter 1 ∙ Planning Your Upgrade or Migration to Release 12.2 . . . . . . . . . . . . .13Use the APM Community for Upgrade and Migration Guidance . . . . . . . . . . . . . . . . .13Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Identify Goals of the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Inventory Your Current Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Check Hardware and Software Requirements for the New Release . . . . . . . . . . . . . . .15Supported Releases for Direct Upgrade or Migration . . . . . . . . . . . . . . . . . . . . . . . . .16Product Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21Chapter 2 ∙ Upgrading Data Center Real User Monitoring . . . . . . . . . . . . . . . . . .21Upgrade Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Upgrade Paths for Earlier DC RUM Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Upgrading to CSS 12.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23RUM Console Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Upgrading a Standalone RUM Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Upgrading the Java Web Start-based RUM Console . . . . . . . . . . . . . . . . . . . . . . . .26CAS Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Running a CAS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32CAS Smoke Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33CSS Upgrade Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33ADS Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Running an ADS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39ADS Smoke Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Upgrading AMD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3Compuware APM Product Upgrade and Migration Installation Guide

Contents

40Upgrading the AMD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42AMD Smoke Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Adding Missing Software After Red Hat Enterprise Linux 6 Kickstart Installation . .

47Chapter 3 ∙ Upgrading the Enterprise Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Upgrading the Enterprise Portal to 12.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Deploy BSM Dashboards in the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51Chapter 4 ∙ Migrating BSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Migration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Migration Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Install the Service Model Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Migrate the Service Model Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Run the Server Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Migrate Additional Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Edit EUE Adaptor Configuration (Migrating from Releases Prior to 12.1) . . . . . . . .58Optional: Import Previous Release's Service Model Configuration Data . . . . . . . . . .58Migrate the Event Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

61Chapter 5 ∙ Migrating VantageView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Migration Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Compatible Compuware APM Product Releases . . . . . . . . . . . . . . . . . . . . . . . . . .63Migration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65VantageView Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Migrating VantageView to the New Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Verifying Migration Success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Post-Migration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

73Chapter 6 ∙ Upgrading to Synthetic Monitoring Release 12.2 . . . . . . . . . . . . . . . . .73Release 12.2 Upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Upgrade Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Upgrading to Synthetic Monitoring Release 12.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Agent Automatic Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Applying an Automatic Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Viewing the Status of an Automatic Software Update . . . . . . . . . . . . . . . . . . . . . . .81Manually Upgrading an Agent to Release 12.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Upgrading a Remote Version of the Synthetic Monitoring Console . . . . . . . . . . . . . . .82Verifying the Success of the Upgrade/Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

84Updating Registration for Agent-Initiated Agents with Secure Communication AfterUpgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

84Upgrading the Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Framework Upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Importing the Upgrade Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87Deploying the Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

91Chapter 7 ∙ Migrating Server Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91Migration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Compuware APM Product Upgrade and Migration Installation Guide4

Contents

92Migration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Migration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Determining the Server Monitoring Agent Release . . . . . . . . . . . . . . . . . . . . . . . . .94Performing the Server Monitoring Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Migrating Server Monitoring Databases with the Database Utility . . . . . . . . . . . . . . . .95Database Migration Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96Upgrading SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96Migration Verification Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Deploying Patches to Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Estimating UNIX Agent Update Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Migrating a UNIX Agent from 32-Bit to 64-Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

101Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Contents


Contents

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

The purpose of this guide is to provide instructions for upgrading or migrating multipleCompuware APM products to Release 12.2. Also refer to product documentation and releasenotes for system requirements, known issues or less-common upgrade procedures.Since some APM products are dependent on at least one other product, it is important to migratethe products in a specific order.

How Terms are Used in this Guide

MigrationIn this document, migration is the process of upgrading an existing release of a productor product component to a new release and transferring the associated data to the newrelease. You will migrate from your existing releases of BSM, Synthetic Monitoring,Server Monitoring, and VantageView to the latest release.

UpgradeIn this document, upgrade is the process of moving the current software release of aproduct or product component to a new release without the need to transfer the associateddata to the new release. You will upgrade DC RUM components, CSS, and EnterprisePortal from eligible releases.

AcronymsTable 1. Acronym Definitions

DefinitionAcronym

Advanced Diagnostics ServerADS

Agentless Monitoring DeviceAMD

Compuware's Application Performance Management product suiteAPM

Autonomous SystemAS

Autonomous System NumberASN


Table 1. Acronym Definitions (continued)

DefinitionAcronym

Broadband Agentless Monitoring DeviceB-AMD

Business Service ManagementBSM

Central Analysis ServerCAS

Console Basic AnalyzerCBA

Classless Inter-Domain RoutingCIDR

Compuware Open ServerCOS

Compuware Security ServerCSS

Comma Separated ValuesCSV

Deep Application Transaction ManagementDATM

Data Center Real User MonitoringDC RUM

Distributed License ManagementDLM

Data Mining InterfaceDMI

End User ExperienceEUE

Network Delta AccessNDA

Page View UsersPVU

Real User MonitoringRUM

Serial Attached SCSISAS

Subscriber IntelligenceSI

Switched Port AnalyzerSPAN

Thin Client Analysis ModuleTCAM

Transaction Trace AnalysisTTA

VLAN Access Control ListVACL

Windows Internet Name ServiceWINS

Who Should Read This GuideThis guide is intended for use for those responsible for upgrading and migrating CompuwareAPM products to release 12.2. Upgrading and migrating requires product knowledge, as wellas experience with database administration.

Organization of This GuideThis guide contains the following chapters:

• Planning Your Upgrade or Migration to Release 12.2 [p. 13]


Introduction

• Instructions for upgrading or migrating the following products:

◦ Upgrading Data Center Real User Monitoring [p. 21]

◦ Upgrading the Enterprise Portal [p. 47]

◦ Migrating BSM [p. 51]

◦ Migrating VantageView [p. 61]

◦ Upgrading to Synthetic Monitoring Release 12.2 [p. 73]

◦ Migrating Server Monitoring [p. 91]

Related PublicationsThe following documents provide system requirements and additional installation andmigration/upgrade information. In addition to the documentation listed for each product, eachproduct features an extensive help system that is installed with the product.

BSMThe product documents listed below are available to provide additional directions forinstalling, migrating, and configuring BSM.

• Business Service Management Release Notes (ReleaseNotes.html).

• Business Service Management Installation Guide (BSM_Installation.pdf).

• Business Service Management Administration Guide (BSM_Admin.pdf) – Reviewthis guide to learn how to configure CSS for user management.

These guides are installed with the product, or available on the installation media in theBusiness Service Management\Documentation folder.

DC RUMThere are several components to install for DC RUM and they are described in thefollowing documents:

• Hardware Recommendations (DCRUM_HardwareRecommendations.pdf) – Reviewthis guide for system requirements for DC RUM components.

• Capacity Planning and Performance Assessment User Guide(DCRUM_CapacityPlanningUserGuide.pdf) – Review this guide to help determinethe system capacity requirements for new installations of DC RUM, or installationof additional features. It also describes how to assess the performance of currentinstallations.

• Agentless Monitoring Device Installation Guide (DCRUM_AMDInstall.pdf).

• Central Analysis Server Installation Guide (DCRUM_CASInstall.pdf).

• Advanced Diagnostics Server Installation Guide (DCRUM_ADSInstall.pdf).

• RUM Console Installation Guide (DCRUM_RUMConsoleInstall.pdf).

• Data Center Real User Monitoring System Administration Guide (DCRUM_Admin.pdf)– Review this guide to learn how to configure CSS for user management.

• Data Center Real User Monitoring Getting Started Guide (DCRUM_GetStarted.pdf).


Introduction

Documentation is installed with the product, or available on the installation media in the\Central Analysis Server\CAS_Documentation folder.

dynaTraceGo to the APM Community for documentation on upgrading to the latest release.

Server Monitoring• Server Monitoring Installation Guide (SM_Installation.pdf)

This guide is available on the installation media in the \Server Monitoring\Docs folder.Synthetic Monitoring

• Synthetic Monitoring Installation Guide (SYM_Install.pdf).

This guide is available on the installation media in the \Synthetic Monitoring\Docsfolder.

VantageView• VantageView Installation Guide (VV_Installation.pdf).

This guide is available on the installation media in the \VantageView\Docs folder.Distributed Licensing Management

• Distributed License Management Installation Guide (Compuware LicensingGuide.pdf).

This guide is available on the installation media in the \cpwr\cwlm\ folder.

Customer Support Information

FrontLine Support Website

You can access information for Compuware products via our FrontLine support site. You canreview frequently asked questions, read or download documentation, access product fixes, ore-mail your questions or comments. The first time you access FrontLine, you are required toregister and obtain a password. Registration is free. To access FrontLine, log in tohttp://go.compuware.com. Select your product from the Product Support dropdown list.

Contacting Customer Support

Phone• USA and Canada: 1-800-538-7822 or 1-313-227-5444.

• All other countries: Contact your local Compuware office. Contact information isavailable at http://go.compuware.com.

WebYou can report issues via the Report and Track Calls tab on the FrontLine home page.

NOTEPlease report all high-priority issues by phone.


Introduction

https://apmcommunity.compuware.com/community/display/APMDOC/APM+Documentation



APM CommunityYou can find product documentation, forums with product experts, product fixes and moreinformation at the Compuware APM Community. You must register and login to accessthe Community.

[email protected]

MailCustomer SupportCompuware CorporationOne Campus MartiusDetroit, MI 48226-5099

Corporate Website

To access the Compuware website, go to http://www.compuware.com. The Compuware siteprovides a variety of product and support information.

Conventions Used in This GuideBelow is a list of the conventions used in this document.

IndicatesFont Used

Terms, commands, and references to names of screen controls and userinterface options, such as menu items.

Bold

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

Blue

Cited contents of text files, examples of code, command line inputs, or systemoutputs. Also file and path names.

Fixed width

Place holders for values of strings, for example as in the command:cd directory_name

Fixed width italic

Menu items.Menu ➤ Item


Introduction

https://apmcommunity.compuware.com/community/display/PUB/Community+Home

mailto:[email protected]

http://www.compuware.com

http://www.compuware.com


Introduction

C H A P T E R 1

Planning Your Upgrade or Migration to Release12.2

Careful planning of your upgrade or migration to release 12.2 can help you determine the tasksrequired to successfully upgrade. Compuware Customer Support reports that many issues canbe avoided by understanding your upgrade or migration path(s), completing all tasks asdocumented, and verifying success at multiple stages.This chapter outlines the steps you should take to plan your upgrade project. It has two checklists— one for planning the project, the second for executing the upgrades.

Use the APM Community for Upgrade and MigrationGuidance

The APM Community's Upgrade and Migration Center has a number of resources to help youplan your upgrade or migration project:

• Product demonstrations, Technical Talks, release notes and product documentation.

• Questionnaires and planning templates to help you plan the upgrade project. Thequestionnaire will help you create an inventory of your current deployment so that youhave a baseline from which to plan. Hardware recommendations are available so that youcan assess resources you'll need for the new release.

• Migration and upgrade forums moderated by Compuware APM experts.

Planning ChecklistUse this checklist to plan the upgrade or migration of your products to release 12.2.

Table 2. Migration Planning Checklist

StepsFinished

Identify Goals of the Upgrade [p. 14].

Create an inventory of your current product versions, server components, databasesand deployed agents.


https://apmcommunity.compuware.com/community/pages/viewpage.action?pageId=103318366

Table 2. Migration Planning Checklist (continued)

StepsFinished

For more information, see Inventory Your Current Deployment [p. 14].

Review the installation guide for the new releases for your products to determinesoftware and hardware requirements, upgrade or migration prerequisites, andproduct dependencies.For more information, see Check Hardware and Software Requirements for theNew Release [p. 15].

Determine your path to release 12.2.For more information, see Supported Releases for Direct Upgrade or Migration[p. 15] and Product Backward Compatibility [p. 16].

Begin your upgrade project.Use the Upgrade Checklist [p. 18] as a guide for executing multi-product upgradesand migrations.

Identify Goals of the UpgradeAn important planning consideration is whether you will upgrade all of your APM products ora subset. To help determine your upgrade goals, review each product's Release Notes and productdocumentation for major new features in the release. It may also list features that were replacedor dropped from previous releases, so you should make sure that the features in your currentdeployment will work in 12.2 as it did in the previous release. The installation guide for yourproduct(s) will contain integration dependencies that should be followed. The Release Notesand documentation are available in the product distribution media, or at the APM CommunityDocumentation page.If you haven't upgraded your deployment for a few releases, it is likely that some functionalityor system requirements have changed. Check the product's Release Notes for the releases youmissed to ensure that the functionality you need is still supported, or if it has changed. If thefunctionality has changed, you should be able to find information in the documentation on howto configure and use the new replacement feature after migration.Do not expect that unsupported data or component functionality will be migrated or upgradedto a newer release. You should determine your options for changed or dropped functionalitybefore starting the upgrade process.

Inventory Your Current DeploymentTo successfully upgrade or migrate your environment to release 12.2, first determine whatrelease(s) you currently have deployed for all of your Compuware APM components. In release12.1 DC RUM added its Update Manager, which will quickly produce a report on all DC RUMcomponents and determine if service packs or new releases are available for download. If yourRUM Console server has internet access, go to the console's Help menu and select Check forUpdates. If you don't have internet access from that machine, go to FrontLine to connect toyour RUM Console server and launch the Update Manager.


Chapter 1 ∙ Planning Your Upgrade or Migration to Release 12.2

https://apmcommunity.compuware.com/community/display/APMDOC/APM+Documentation

http://go.compuware.com/default.aspx?rurl=http://frontline.compuware.com//products/A8/updatemanager.aspx

Only certain product releases can upgrade or migrate directly to release 12.2, so determine ifyou can upgrade directly, or if you need to first get to a minimum supported release that allowsa direct upgrade or migration. For more information, see Supported Releases for Direct Upgradeor Migration [p. 15].Determine both the release number and the maintenance level of each component, because it isimportant to apply the latest service packs to releases before upgrades. In the Help ➤ Aboutscreens, you can find the release number and service pack level, or a release and build numberthat reflects your latest installation. This information is also provided in product log files, or inthe case of BSM, in the version.xml file in the BSM_HOME\ folder. Knowing this informationwill also help you in discussing potential migration plans with Compuware.

Inventory Server Components, Databases and Agents

While determining the release levels of your products, it is also a good idea to create an inventoryof your entire Compuware APM implementation, for example, deployed management servers,databases, and agents. The quantity of servers and agents, and the platforms they are runningon, will be factors in planning the migration of these components.A good practice is to create a diagram of the installation so you are aware of all componentsand any access issues that may arise. A deployment diagram could be helpful if you needassistance from Customer Support.

Check Hardware and Software Requirements for theNew Release

System requirements for Compuware APM products have evolved with releases of new operatingsystems, application servers and databases. What currently works in your deployed environmentmay not support a 12.2 implementation. Check the release 12.2 installation guide for yourproducts to see if the currently deployed operating systems, application servers, and databasesare still supported. Purchasing and deploying new software should be built into the timeline forupgrade or migration.You should also review the DC RUM Hardware Recommendations and the Capacity Planningand Performance Assessment User Guide. As Compuware APM grows its monitoring capabilities,more disk space and memory may be required to process additional data. Minimum specificationsare provided in the product's installation guide. Compuware stresses that you configure yourenvironment using the recommended specifications, if available. Purchasing and deploying newhardware should be built into the timeline for your migration.

Supported Releases for Direct Upgrade or MigrationThe following table shows product releases that can upgrade and migrate directly to the latestrelease.

Refer toReleases Eligible forUpgrade to LatestRelease

Product

Migrating BSM [p. 51]12.0.2 and laterBSM



Refer toReleases Eligible forUpgrade to LatestRelease

Product

Upgrading Data Center Real User Monitoring[p. 21] and Upgrade Paths for Earlier DC RUMReleases [p. 21]

12.0 and laterDC RUM

Migrating Server Monitoring [p. 91]10.2 (must be on latestservice pack) and later

Server Monitoring

Upgrading to Synthetic Monitoring Release 12.2[p. 73]

10.2 (must be on latestservice pack) and later

Synthetic Monitoring

Migrating VantageView [p. 61]10.2 (must be on latestservice pack only for10.2) and later

VantageView

If you are running an older product release that does not have a direct upgrade or migration pathto release 12.2, you must first get to the minimum release that supports a direct upgrade ormigration to release 12.2. Once this intermediate upgrade is successful, proceed with the nextupgrade to release 12.2. Documentation is available on how to migrate from back releases to aminimum release for a direction migration to 12.2. Go to the Documentation page on the APMCommunity to find documentation for back releases.

NOTEIt is likely that you are running several integrated products — a reporting component likeVantageView along with a monitoring solution like Server Monitoring or Synthetic Monitoring.With these integrated monitoring and reporting solutions, you must maintain the integratedproducts in supported and compatible releases throughout the migration process. Failure to doso will impact the availability of monitoring operations. For more information, see ProductBackward Compatibility [p. 16].

Product Backward CompatibilitySome Compuware APM products are backward-compatible with other products and components,so you don't have to upgrade all components immediately to start getting value from newfunctionality.

NOTEIf you are migrating VantageView from 10.2 to 12.0, you must also migrate Synthetic Monitoringand Server Monitoring to release 12.0. For more information, see Compatibility with PreviousReleases [p. 74].If you are using Synthetic Monitoring with a scripting framework, you should contact your localCustomer Support office to determine compatibility with the current release. In addition, wheninstalling or upgrading the Synthetic Monitoring agents, the Micro Focus QALoad Player isautomatically installed. You would then have to upgrade the Micro Focus QALoad Workbenchto match the new version.



https://community.compuwareapm.com/community/display/PUB/Community+Home

https://community.compuwareapm.com/community/display/PUB/Community+Home

The following sections detail the backward compatibility with other product components orreleases:

DC RUM 12.2 Backward Compatibility

Supported VersionsComponent

CAS • AMD 12.0 and later

• RUM Console 12.2 (no backward compatiblity)

• Enterprise Portal 12.1

No backward compatibility.AMD

RUM Console • CAS 12.0 and later

• AMD 12.0 and later

CAS 12.2 only — no backward compatibility.ADS

11.5.3 and laterBSM

11.5 and laterSynthetic Monitoring

Enterprise Portal 12.2 Backward Compatibility

Supported VersionsProduct Integration

12.0.2 and later.BSM

NOTEYou must deploy the BSM web application for theback release you are using, and apply the latestservice pack. For more information, see DeployBSM Dashboards in the Portal [p. 48].

12.1CAS

CSS 12.2 Backward Compatibility

Supported VersionsProduct Integration

12.1 and 12.0 (Synthetic Monitoring 12.1 only).All supported components.

VantageView 12.0 Backward Compatibility

Supported VersionsIntegration

Control Server 11.5 and 11.7Server Monitoring

Agent Manager 11.7Synthetic Monitoring

Release 10.0Network Monitoring



Supported VersionsIntegration

Release 11.5, 11.6, and 11.7DC RUM

Server Monitoring 12.0 Backward Compatibility


11.5 and 11.7 agentsControl Server

Synthetic Monitoring 12.2 Backward Compatibility


11.7 agentsAgent Manager

12.0VantageView

BSM 12.2 Backward Compatibility

VersionsProduct Integrations

11.7 and laterDC RUM (CAS)

11.5 and laterServer Monitoring

Upgrade ChecklistUse this checklist to organize your upgrade or migration to the latest release. This checklist isdesigned for customers who have their Compuware APM products at releases that support adirect upgrade to release 12.2. If your implementation includes releases that do not support adirect upgrade, you should upgrade those to an interim release that supports a direct upgrade,and then proceed with this sequence of steps. If you do not use a product mentioned in thechecklist, skip that step and proceed to the next product task.

Table 3. Upgrade Checklist

Upgrade or Migration TaskFinished?

Apply latest service pack(s), if needed, to your current APM environment.Go to http://frontline.compuware.com and check the Fixes/Downloads page foryour product to see if service packs are available.

Back up your current APM environment, including databases.

If you are on release 12.x, upgrade the CSS to 12.2.

Upgrade the DC RUM RUM Console to release 12.2. For more information, seeUpgrading Data Center Real User Monitoring [p. 21] and RUM Console Upgrades[p. 23].

Verify that the RUM Console upgraded successfully.



http://frontline.compuware.com

Table 3. Upgrade Checklist (continued)


Upgrade CAS and ADS to release 12.2.For more information, see CAS Upgrade Overview [p. 26] and ADS UpgradeOverview [p. 33].Following installation, determine if service packs are available for thosecomponents and apply them.

Verify that the CAS and ADS upgraded successfully. For more information, seeCAS Smoke Test [p. 32] and ADS Smoke Test [p. 39].

Upgrade the DC RUM AMD to 12.2.Following installation, determine if service packs are available for thosecomponents and apply them.For more information, see Upgrading AMD Software [p. 40].

Verify that the AMD upgraded successfully. For more information, see AMDSmoke Test [p. 42].

If you are using the Enterprise Portal 12.x with DC RUM or BSM, upgrade it to12.2. For more information, see Upgrading the Enterprise Portal to 12.2 [p. 47].

If you are using BSM, deploy the BSM web application with the Portal. For moreinformation, see Deploy BSM Dashboards in the Portal [p. 48].

If your Service Model is on 12.0 or later, install BSM 12.2 and migrate yourService Model server data to the new release. For more information, see Installthe Service Model Components [p. 53].

Verify that your Service Model is unchanged from the previous release and thedashboards appear as expected in the Portal.

If you use VantageView, migrate it to release 12.0.Following installation, determine if service packs are available for thosecomponents and apply them.For more information, see Migrating VantageView [p. 61].

Verify that VantageView migrated and upgraded successfully.For more information, see Verifying Migration Success [p. 70].

Upgrade Synthetic Monitoring to release 12.2.Following installation, determine if service packs are available for thosecomponents and apply them.

Verify that Synthetic Monitoring upgraded successfully. For more information,see Verifying the Success of the Upgrade/Migration [p. 82].

Upgrade Server Monitoring to release 12.0.Following installation, determine if service packs are available for thosecomponents and apply them.For more information, see Migrating Server Monitoring [p. 91].



Table 3. Upgrade Checklist (continued)


Verify that Server Monitoring upgraded successfully. For more information, seeMigration Verification Checklist [p. 96].



C H A P T E R 2

Upgrading Data Center Real User Monitoring

This chapter describes how to upgrade DC RUM to Release 12.2. It does not include informationon backing up and restoring your configurations and data; troubleshooting information; ordescribe less-common procedures such as how to upgrade from a 32-bit system to a 64-bitsystem. For such details, please refer to the installation guides for the DC RUM components.

Upgrade WorkflowUpgrade your components in the recommended order:

1. CSS2. RUM Console3. Central Analysis Server4. Advanced Diagnostics Server5. Agentless Monitoring Device6. Enterprise Portal (if used)

Upgrade Paths for Earlier DC RUM ReleasesReleases prior to 12.0 cannot be upgraded directly to the current release (12.2). If your currentDC RUM release is earlier than 12.0, you need to follow an incremental upgrade path to get tothe current release. See the table below for all supported upgrade paths.

Table 4. Migration Paths for Older Releases

Upgrade path is:Your current installation

10.2 1. Upgrade your current installation to 10.3

2. Upgrade from 10.3 to 11.1





Table 4. Migration Paths for Older Releases (continued)

Upgrade path is:Your current installation

10.3 1. Upgrade your current installation to 11.111.0 2. Upgrade from 11.1 to 11.7



11.1 1. Upgrade your current installation to 11.7



11.5 1. Upgrade your current installation to 11.5.211.5.1 2. Upgrade from 11.5.2 to 12.0


11.5.2 1. Upgrade your current installation to 12.011.6 2. Upgrade from 12.0 to 12.211.711.7.1

Upgrade your current installation directly to 12.212.012.0.112.0.212.112.1.1

NOTEIf you are upgrading the Vantage Analysis Server (VAS, now known as the CAS) and AdvancedWeb Diagnostic Server (AWDS, now known as the ADS) from release 11.0 or earlier, you needto upgrade the Distributed License Management application to 4.3.25 and then 4.5.2. You shouldperform these upgrades prior to upgrading the VAS and ADS.

Upgrading to CSS 12.2To upgrade your Compuware APM release to 12.2, CSS must also be on 12.2.To upgrade an existing CSS:

1. Stop the Compuware Common Components service.2. Install CSS 12.2 over the existing release. For Windows, the installer is available in the

product distribution on DVD 1 at Common Components\install.exe. The Linux andUnix installers are on DVD 2 and 3, respectively.


Chapter 2 ∙ Upgrading Data Center Real User Monitoring

After you start the installation, you will see a message that an existing release was foundon the machine. Click OK to proceed with the installation.

3. After installing, verify that CSS is running, that your users and user groups are retained,and that the authentication method (local or LDAP) is configured.

RUM Console UpgradesThe version of the RUM Console must be the same version as the other components of DCRUM or the configuration of any new or enhanced features is not possible.

IMPORTANTThis section describes the basic procedure for upgrading this component. For important additionalinformation concerning backup and recovery procedures, see the component-specific installationguide.

Upgrading a Standalone RUM ConsoleA standalone RUM Console refers to the application that is installed using a regular installationexecutable, not the Java Web Start. You can upgrade the RUM Console from a previous versionby installing the current version of the RUM Console over the existing installation.

Before You Begin

Before starting an upgrade of the RUM Console, ensure that the console client is not runningon any user account.If the Windows Task Manager lists a process called cva-client.exe or cva-client.exe*32, but no console is running for the current user, this indicates that another user is runningthe RUM Console. Log these users out before restarting the upgrade.

1. Select the installation disc that matches your target machine's operating system:

• DVD1 Windows

• DVD2 Linux

• DVD3 AIX HPUX

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.If you downloaded the product, go to the equivalent folder in your downloaded copy andrun the setup.exe application.

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



The installation program detects the details of your current installation, including the productfeatures and installation folder, and attempts to install a new version applying the sameoptions.

4. If the Security Configuration screen is displayed, provide the CSS settings you want touse and click Next.You can install CSS locally during this installation or specify the address and port of aremote CSS server to use.

5. If you are upgrading from release 12.0 to release 12.2, on the RUM Console DatabaseConfiguration screen, define the SQL database connection properties and decide whetherto use the existing database or create a new one.If you are upgrading from release 12.1 to release 12.2, go to Step 6 [p. 25].a. Define the SQL database connection properties.

The RUM Console requires a database to store run-time data. You need to specify:

Host[\instance], PortYou may need to consult your database administrator to determine the correctvalues.

• If the database server is on the same machine, you can enter localhost inthe Host[\instance] field.

• For a remote server, set Host[\instance] to the server name or IP address.

Database NameEnter the name you want to give to your RUM Console database, or the nameof the existing database if it was prepared earlier.

Use SSL encryptionSelect or clear the Use SSL check box to indicate whether to use SSLcommunications with a report server.

b. Decide whether to create a new or use an existing database.c. Provide the database details.

If you decide to create a new database, choose the authentication method and providethe administrator and database user name and password.

Administrator login, PasswordThe login name and password for the database administrator. Note that in caseof Windows authentication, you will have to provide a trusted account name inthe domain\user format.

Database userThe default database user name can be a valid domain user. To specify a domainname, use the domain\user format.When you create a new database, make sure that you provide a non-existingdatabase user name. To make sure the user does not exist in the Microsoft SQLServer, log in to Microsoft SQL Server Management Studio and navigate toSecurity ➤ Logins to see the list of defined users.

PasswordPassword for database user specified above.



6. On the Pre-Installation Summary screen, review the installation options that you selectedand click Install.The selected software will be installed. This may take some time.

7. On the Install Complete screen, click Done.The location of the installation log is displayed on this screen. Refer to it if errors occurredduring installation.

What to Do Next

If you would like to upgrade your SAP hierarchy definitions to the new simplified version, youmust manually import the new hierarchy file.

Upgrading the Java Web Start-based RUM ConsoleSome older versions of the DC RUM Java Web Start-based VCAEUE Console are notautomatically updated to the new version during an upgrade. In such cases, uninstall the previousversion before installing 12.2.

Before You Begin

You need a working CAS 12.2 release to launch a new instance of the Java Web Start-basedRUM Console after uninstalling the previous version.Before starting an upgrade of the RUM Console, ensure that the console client is not runningon any user account.

To upgrade the Java Web Start-based VCAEUE Console to RUM Console version 12.2, performthe following steps:

1. Uninstall your earlier release of the Java Web Start-based VCAEUE Console.a. Open the Java Cache Viewer.

For more information, see Managing Java Web Start-based RUM Console in the DataCenter Real User Monitoring RUM Console Installation Guide.

b. Delete the Java Web Start-based VCAEUE Console application.Right-click the VCAEUE Console application and select Delete.

c. Delete all the resources related to the VCAEUE Console.To remove the application completely, delete all the resources related to the 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. Launch the Java Web Start-based RUM Console from the CAS 12.2 release.Log on to CAS 12.2 and start Java Web Start-based RUM Console. For more information,see Launching Java Web Start-based RUM Console in the Data Center Real UserMonitoring RUM Console Installation Guide.



CAS Upgrade OverviewThe CAS installation program will detect any older version of the CAS and offer to upgrade itto the current release. Optionally, the upgrade preserves configuration information and trafficmonitoring data contained in the CAS database.If you are upgrading your report server from release 12.0 or later to the current release (12.2),the installer should handle the upgrade automatically. If you are upgrading from an earlierrelease, you have a longer upgrade path. For more information, see Upgrade Paths for EarlierDC RUM Releases [p. 21].If upgrading from an earlier version, you may need to manually perform some elements ofconfiguration migration. In particular, this applies to the configuration of alerts.


Running a CAS UpgradeTo upgrade an earlier version of CAS to the latest version, fulfill the prerequisites describedbelow, and then run the installer for the latest version of CAS. The installer will detect the earliersoftware and display your upgrade options.

Before You Begin

FailoverIf you are creating a failover installation, do not use this procedure. Instead, see the failoverprocedures. For more information, see Providing Failover for Report Server in the DataCenter Real User Monitoring Administration Guide.

Migrating CAS from a 32-Bit Version to a 64-Bit VersionA direct upgrade from a 32-bit version to a 64-bit version is not supported. If you need toperform such an upgrade:

1. Save your 32-bit configuration settings manually (this pertains only to new serverconfiguration files added after the 32-bit installation).

2. Uninstall the 32-bit version of the product while preserving the database.

3. Install the 64-bit version as a new installation, not an upgrade.

4. Perform a manual migration of configuration settings.

Note that settings maintained in the database are migrated with the database. For moreinformation, see Migrating 32-bit CAS to 64-bit CAS (Same Platform, Local Database)in the Data Center Real User Monitoring Central Analysis Server Installation Guide andMigrating 32-bit CAS to 64-bit CAS (Same Platform, Remote Database) in the Data CenterReal User Monitoring Central Analysis Server Installation Guide.

Moving CAS to a New MachineTo migrate CAS from one platform to another, including the local database:



1. Make backups of your databases and configurations from your old machine.

2. Install the software on the new machine.

3. Restore your databases and configurations on the new machine.

For more information, see Migrating CAS to a New Platform (Local Database) in theData Center Real User Monitoring Central Analysis Server Installation Guide andMigrating CAS to a New Platform (Remote Database) in the Data Center Real UserMonitoring Central Analysis Server Installation Guide.

Database BackupBack up the database. For more information, see Backing Up MS SQL Server 2005 CASDatabases in the Data Center Real User Monitoring Administration Guide and BackingUp MS SQL Server 2008 CAS Databases in the Data Center Real User MonitoringAdministration Guide.

Upgrading from Older ReleasesIf you are upgrading your report server from release 12.0 or later to the current release(12.2), the installer should handle the upgrade automatically. If you are upgrading froman earlier release, you have a longer upgrade path. For more information, see UpgradePaths for Earlier DC RUM Releases [p. 21].

To upgrade a CAS installation (to install a newer version over an existing version):

Locate and Run the Installer

1. Exit all other programs before running the setup program.Some Windows programs, such as anti-virus software, may interfere with the upgradeprocess.


• DVD1 Windows

• DVD2 Linux

• DVD3 AIX HPUX


4. On the Data Center Real User Monitoring tab, click Central Analysis Server (CAS).The default installation is for a 64-bit architecture. If you need a 32-bit installation, findthe installer in the Central Analysis Server directory of the distribution media and run itdirectly from the file system.



IMPORTANTUpgrading from a 32-bit version to a 64-bit version is not supported. For more information,see Migrating 32-bit CAS to 64-bit CAS (Same Platform, Local Database) in the DataCenter Real User Monitoring Central Analysis Server Installation Guide and Migrating32-bit CAS to 64-bit CAS (Same Platform, Remote Database) in the Data Center Real UserMonitoring Central Analysis Server Installation Guide.

5. If the detected amount of physical memory (RAM) on the target machine is lower than therecommended amount, a warning message is displayed.Click Cancel to abort the installation and consider upgrading the machine's RAM beforerestarting the installation process, or click Next (not recommended) to continue thisinstallation with less than the recommended amount of RAM.

Provide the Configuration Requirements

6. On the Introduction screen, click Next.The License Agreement screen is displayed.

7. On the License Agreement screen, read the license, indicate that you accept the terms, andclick Next.If you do not accept the terms, click Cancel to terminate the installation.

8. If the Security Configuration screen is displayed, provide all requested CSS connectioninformation.You cannot continue until you provide working CSS connection information. The Hostand Port settings describe the CSS connection.

HostIP address of the CSS host.

PortPort number of the CSS host.

Default: 4182

The User name and Password settings are displayed only when upgrading from a releaseearlier than 12.0. You need to provide the credentials of a CSS user with administrativeprivileges when you migrate users from an old installation.

User NameEnter the user name for your CSS administrator account.

PasswordEnter the password for your CSS administrator account.

9. If the Upgrade screen is displayed (because a previous installation has been detected),indicate whether you want to change the current configuration while you upgrade thesoftware.If you choose to upgrade the software without changing the current settings, a minimalsequence of setup screens (Database Connection Properties, Database Server Memory,and Installation Options - Summary), with minimal editing options, are displayed. Review



them before upgrading to 12.2. If you want to change any settings, use the Back button tocome back to the Upgrade screen and select the other option.If you choose to change settings and upgrade the software to the new version, the full setof configuration screens as outlined below are displayed to specify new configurationsettings and upgrade to release 12.2.

Report Server Settings

NOTEThe full set of configuration screens are outlined below. If you selected to upgrade your softwarewithout changing settings, most of these screens are not displayed.

10. On the Installation Folder screen, type or browse for the target installation directory andclick Next.

NOTEIf other Compuware APM products are currently active on the target machine, their servicesare stopped automatically before CAS is installed.

11. On the Database Configuration Properties screen, indicate whether you want to createa new database or use an existing database.

12. On the Database Connection Properties screen, review the SQL database connectionproperties and adjust them as needed.Database upgrade options:

Upgrade DatabaseThis option preserves all traffic monitoring data and database configuration settings.

Reset DatabaseThis option deletes all traffic monitoring data but preserves database configurationsettings.

Recreate DatabaseThis option deletes the database and creates a new database of the same name. Allthe traffic monitoring data contained in the database and all database configurationsettings are lost.

13. If the Database Server Memory screen is displayed, specify the maximum size of theSQL Server memory and click Next.This screen is displayed if a new database is created or if an existing database is overwritten.Note that for the reconfiguration to take effect, SQL Server must be restarted. If you areusing a local SQL Server, the installation program offers to restart it automatically. If youhave specified a remote server, you are asked to restart the server manually before attemptingto use the database.When you click Next from the Database Server Memory screen, an additional screenprompts you to specify whether to use all available RAM during the database upgrade.Select the check box if you don't need the RAM for other purposes during this upgrade.



14. On the Connectivity Options screen, review the HTTP/HTTPS settings for your reportserver.

Use HTTPWhether to use HTTP to transfer and display reports.

HTTP Port NumberThis number is incremented if the default port (80) is unavailable.

Use HTTPS (HTTP over SSL)Whether to use HTTPS to transfer and display reports.

HTTPS Port NumberWhen accessing the reports on a port other than 443, remember to supply the selectedport number together with the host name in your browser. This number is incrementedif the default port is unavailable.

Generate key and certification, Use custom key and certificateIf you choose to generate a key and certification, you will need to provide informationfor it on the next screen.

15. If the SSL Key Generation Data screen is displayed, specify the encryption keyinformation.You can either automatically generate a key and a certificate, or to use a custom encryptionkey. To generate the key, provide the required data, which varies depending on whetheryou selected automatic or custom key generation. The SSL Key Generation Data screenenables you to enter the information required to generate a new key. For a custom encryptionkey, you can provide only the password; the other fields cannot be edited.

CountryThe standard abbreviation for your country. Select one from the list of approvedcountry codes.

LocalityUsually your city. Use a full name such as “Los Angeles,” not an abbreviation.

State or ProvinceYour administrative region within your country. Use a full name such as “California,”not an abbreviation.

Organization NameUsually a company name. Use the full legal company or personal name as registeredin your locality.

Organization UnitThe company division or branch (such as Accounting or Marketing) to which thecertificate was issued.

Common/Host NameThe host.

Email AddressThe email address.

Choosing a custom encryption key requires that you configure the server manually. Thisprocess involves copying both the key and the certificate to the proper directory andmodifying the common.properties file. For more information, see Configuring Report



Server to Use Private Keys and Certificates in the Data Center Real User MonitoringAdministration Guide.

16. If the SSL Key Security screen is displayed, specify the encryption key security information.

Key Password, Confirm Key PasswordThe password associated with the key.

Remember the key passwordWhether to remember the password.

TIPFor Windows 2008, it is strongly recommended that you select the Remember thekey password check box when you install your report server. If you do not do so,you will be asked for that password at every service start. Furthermore, whenInteractive Service Detection is disabled you will not see the message at all and willnot be able to provide a passphrase for the private SSL key.

If you do not select the Remember the key password check box, you can insteadsupply the key password at system startup, but only if you are directly connected tothe server. Remember that the dialog box for entering the password will not appearif you are connected to the server using a remote terminal.Also, remember that if you do not provide a password the key will not be encrypted.

17. If the RUM Console Connection screen is displayed (because no local RUM Consoleinstallation was detected), enter the address and port of a remote RUM Console installationand then click Next.Note that you can change these settings later. For more information, see Changing the RUMConsole Connection Information in the Data Center Real User Monitoring Central AnalysisServer Installation Guide.

18. On the Documentation page, choose whether and where to install user manuals.You can choose to skip the installation of manuals, or to install them from a directory ofyour choice.

19. On the Help page, choose whether and where to install online help.You can choose to skip the installation of help, or to install it from a directory of yourchoice.

Install the Software

20. On the Pre-Installation Summary page, review the summary of your installation choicesand click Install.To change the settings, click Back to return to the appropriate configuration screen.The amount of time this takes depends on the size of the database and may take betweenseveral seconds and, for large databases, several hours. A progress box shows the status ofthe installation action currently in progress. When all of the required actions are completed,a final post-upgrade information screen is displayed.

21. On the Installation Summary screen, review the installation summary.



If you prefer, you can click Show postinstall summary to open a file that contains theinstallation summary.

22. Indicate whether you want to start CAS, and then click Finish to exit the installationprogram.

23. Clear your browser cache.This ensures that your upgraded CAS configuration is displayed correctly.

What to Do Next

If you have not already obtained and installed a license, do so now. For more information, seeLicensing Data Center Real User Monitoring Components in the Data Center Real UserMonitoring Administration Guide.

CAS Smoke TestAfter upgrading the CAS to the latest release, conduct the following validation steps.

1. Review the<CAS_INSTALL_FOLDER>\log\install\Central_Analysis_Server_Install_xx_xx_xxxx_xx_xx_xx.log

file to ensure that no errors occurred during migration, especially during the databaseupgrade.

2. From the CAS main menu, open Tools ➤ Diagnostics and view the System Status report.

NOTEYou should allow at least three hours after the upgrade to allow new data to be processedby the CAS.

Review the following sections on the report:

LicenseMake sure that licences are valid and available for all decodes you require.

RepositoryMake sure the current status of BULK INSERT is true.

Connection with AMDs and ProbesMake sure the CAS is able to reach all enabled AMDs and Probes.

Data processingCheck whether there is a delay in data processing (if the CAS was just started, thedelay should be decreasing slowly).

Database info“Free space among allocated space cumulated with space allowed to be allocated.”Make sure there is enough space on the drive for the database to grow if necessary.

Memory sectiona. Make sure the CAS meets or exceeds minimum memory size requirements. Refer

to the Data Center Real User Monitoring Hardware Recommendations.

b. Memory caches: make sure New server/url/client/site processing stoppedequals false.



Server settingsAccess Settings ➤ CAS ➤ Server Configuration and review user aggregation,client IP ranges, and site options to make sure settings were preserved.

3. Review CAS reportsCheck whether historical data is present; access data for previous days, check trends,baselines, reporting groups, applications, and transactions.

CSS Upgrade ValidationAfter upgrading CAS and CSS to the latest release, conduct the following validation steps toensure product security is working properly.

1. Create a new user in the CSS with a non-administrator role.Log in to the CAS with these user credentials.

2. Import specific LDAP groups and LDAP users.3. Manually re-establish LDAP connectivity.

Note the LDAP parameters from the current installation or work with your LDAPadministrator to get the correct connection details.

ADS Upgrade OverviewThe ADS installation program will detect any older version of ADS and offer to upgrade to thecurrent release. Optionally, the upgrade preserves the configuration information and trafficmonitoring data contained in the ADS database.If you are upgrading your report server from release 12.0 or later to the current release (12.2),the installer should handle the upgrade automatically. If you are upgrading from an earlierrelease, you have a longer upgrade path. For more information, see Upgrade Paths for EarlierDC RUM Releases [p. 21].If upgrading from an earlier version, you may need to manually perform some elements ofconfiguration migration. In particular, this applies to the configuration of alerts.

CAUTIONWhen installing or upgrading the ADS, keep in mind that its configuration has to be synchronizedwith the CAS, because the ADS uses configuration settings from the CAS. As a consequence,if you had different configuration settings for the ADS and the CAS, the ADS settings will beoverridden by the CAS settings.The CAS is the primary reporting engine and the whole configuration for DC RUM is maintainedby the RUM Console. An ADS can exist with a CAS only in a server farm, where the masterserver (a CAS) populates its configuration to all slaves (other ADS or CAS report servers).




Running an ADS UpgradeTo upgrade an older version of ADS to the latest version, fulfill the prerequisites describedbelow, and then run the installer for the latest version of ADS. The installer will detect the earliersoftware and display your upgrade options.

Before You Begin

FailoverIf you are creating a failover installation, do not use this procedure. Instead, see the failoverprocedures. For more information, see Providing Failover for Report Server in the DataCenter Real User Monitoring Administration Guide.

Migrating ADS from a 32-Bit Version to a 64-Bit VersionA direct upgrade from a 32-bit version to a 64-bit version is not supported. If you need toperform such an upgrade:

1. Save your 32-bit configuration settings manually (this pertains only to new serverconfiguration files added after the 32-bit installation).

2. Uninstall the 32-bit version of the product while preserving the database.

3. Install the 64-bit version as a new installation, not an upgrade.

4. Perform a manual migration of configuration settings. Note that those settings thatare maintained in the database are migrated with the database.

For more information, see Migrating 32-bit ADS to 64-bit ADS (Same Platform, LocalDatabase) in the Data Center Real User Monitoring Advanced Diagnostics ServerInstallation Guide and Migrating 32-bit ADS to 64-bit ADS (Same Platform, RemoteDatabase) in the Data Center Real User Monitoring Advanced Diagnostics ServerInstallation Guide.

Moving ADS to a New MachineTo migrate the ADS from one platform to another, including the local database, first makebackups of your databases and configurations from your old machine, install the softwareon the new machine, and then restore your databases and configurations on the newmachine. For more information, see Migrating ADS to a New Platform (Local Database)in the Data Center Real User Monitoring Advanced Diagnostics Server Installation Guideand Migrating ADS to a New Platform (Remote Database) in the Data Center Real UserMonitoring Advanced Diagnostics Server Installation Guide.

Database BackupBack up the database before starting the upgrade. For more information, see Backing UpMS SQL Server 2005 CAS Databases in the Data Center Real User MonitoringAdministration Guide and Backing Up MS SQL Server 2008 CAS Databases in the DataCenter Real User Monitoring Administration Guide.

Upgrading from older releasesIf you are upgrading your report server from release 12.0 or later to the current release(12.2), the installer should handle the upgrade automatically. If you are upgrading froman earlier release, you have a longer upgrade path. For more information, see UpgradePaths for Earlier DC RUM Releases [p. 21].



To upgrade ADS (to install a newer version over an existing version):

Locate and Run the Installer

1. Exit all other programs before running the setup program.Some Windows programs, such as anti-virus software, may interfere with the upgradeprocess.


• DVD1 Windows

• DVD2 Linux

• DVD3 AIX HPUX


4. On the Data Center Real User Monitoring tab, click Advanced Diagnostics Server (ADS).The default installation is for a 64-bit architecture. If you need a 32-bit installation, findthe installer in the ADS directory of the distribution media and run it directly from the filesystem.

IMPORTANTUpgrading from a 32-bit version to a 64-bit version is not supported.

5. If the detected amount of physical memory (RAM) on the target machine is lower than therecommended amount, a warning message is displayed.Click Cancel to abort the installation and consider upgrading the machine's RAM beforerestarting the installation process, or click Next (not recommended) to continue thisinstallation with less than the recommended amount of RAM.


6. On the Introduction screen, click Next.The License Agreement screen is displayed.

7. On the License Agreement screen, read the license, indicate that you accept the terms, andclick Next.If you do not accept the terms, click Cancel to terminate the installation.

8. If the Security Configuration screen is displayed, provide all requested CSS connectioninformation.You cannot continue until you provide working CSS connection information. The Hostand Port settings describe the CSS connection.

HostIP address of the CSS host.



PortPort number of the CSS host.

Default: 4182

The User name and Password settings are displayed only when upgrading from a releaseearlier than 12.0. You need to provide the credentials of a CSS user with administrativeprivileges when you migrate users from an old installation.

User NameEnter the user name for your CSS administrator account.

PasswordEnter the password for your CSS administrator account.

9. If the Upgrade screen is displayed (because a previous installation has been detected),indicate whether you want to change the current configuration while you upgrade thesoftware.If you choose to upgrade the software without changing the current settings, a minimalsequence of setup screens with minimal editing options are displayed. Review them beforeupgrading to 12.2. If you want to change any settings, use the Back button to come backto the Product Setup screen and select the other option.If you choose to change settings and upgrade the software to release 12.2, the full set ofconfiguration screens as outlined below will be displayed so you can specify newconfiguration settings and upgrade to release 12.2.


The full set of configuration screens are outlined below. If you chose to upgrade your softwarewithout changing settings, most of these screens are not displayed.

10. On the Installation Folder screen, enter or browse for the target installation directory andclick Next.

NOTEIf other Compuware APM products are active on the target machine, their services arestopped automatically before ADS is installed.

11. On the Database Configuration Properties screen, indicate whether you want to createa new database or use an existing database.

12. On the Database Connection Properties screen, define the SQL database connectionproperties.Database upgrade options:

Upgrade DatabaseThis option preserves all traffic monitoring data and database configuration settings.

Reset DatabaseThis option deletes all traffic monitoring data but preserves database configurationsettings.



Recreate DatabaseThis option deletes the database and creates a new database of the same name. Allthe traffic monitoring data contained in the database and all database configurationsettings are lost.

13. If the Database Server Memory screen is displayed, specify the maximum size of theSQL Server memory and then click Next.This screen is displayed if a new database is created or if an existing database is overwritten.Note that for the reconfiguration to take effect, SQL Server must be restarted. If you areusing a local SQL Server, the installation program offers to restart it automatically. If youhave specified a remote server, you are asked to restart the server manually before attemptingto use the database.When you click Next from the Database Server Memory screen, you are presented anadditional screen to specify whether to use all available RAM during the database upgrade.Select the check box if you don't need the RAM for other purposes during this upgrade.

14. On the Connectivity Options screen, review the HTTP/HTTPS settings for your reportserver.

Use HTTPWhether to use HTTP to transfer and display reports.

HTTP Port NumberThis number is incremented if the default port (80) is unavailable.

Use HTTPS (HTTP over SSL)Whether to use HTTPS to transfer and display reports.

HTTPS Port NumberWhen accessing the reports on a port other than 443, remember to supply the selectedport number together with the host name in your browser. This number is incrementedif the default port is unavailable.

Generate key and certification, Use custom key and certificateIf you choose to generate a key and certification, you will need to provide informationfor it on the next screen.

15. If the SSL Key Generation Data screen is displayed, specify the encryption keyinformation.You can either automatically generate a key and a certificate, or to use a custom encryptionkey. To generate the key, provide the required data, which varies depending on whetheryou selected automatic or custom key generation. The SSL Key Generation Data screenenables you to enter the information required to generate a new key. For a custom encryptionkey, you can provide only the password; the other fields cannot be edited.

CountryThe standard abbreviation for your country. Select one from the list of approvedcountry codes.

LocalityUsually your city. Use a full name such as “Los Angeles,” not an abbreviation.



State or ProvinceYour administrative region within your country. Use a full name such as “California,”not an abbreviation.

Organization NameUsually a company name. Use the full legal company or personal name as registeredin your locality.

Organization UnitThe company division or branch (such as Accounting or Marketing) to which thecertificate was issued.

Common/Host NameThe host.

Email AddressThe email address.

Choosing a custom encryption key requires that you configure the server manually. Thisprocess involves copying both the key and the certificate to the proper directory andmodifying the common.properties file. For more information, see Configuring ReportServer to Use Private Keys and Certificates in the Data Center Real User MonitoringAdministration Guide.

16. If the SSL Key Security screen is displayed, specify the encryption key security information.

Key Password, Confirm Key PasswordThe password associated with the key.

Remember the key passwordWhether to remember the password.

TIPFor Windows 2008, it is strongly recommended that you select the Remember thekey password check box when you install your report server. If you do not do so,you will be asked for that password at every service start. Furthermore, whenInteractive Service Detection is disabled you will not see the message at all and willnot be able to provide a passphrase for the private SSL key.

If you do not select the Remember the key password check box, you can insteadsupply the key password at system startup, but only if you are directly connected tothe server. Remember that the dialog box for entering the password will not appearif you are connected to the server using a remote terminal.Also, remember that if you do not provide a password the key will not be encrypted.

17. On the Documentation page, choose whether and where to install user manuals.You can choose to skip the installation of manuals, or to install them from a directory ofyour choice.

18. On the Help page, choose whether and where to install online help.You can choose to skip the installation of help, or to install it from a directory of yourchoice.



Install the Software

19. On the Pre-Installation Summary page, review the summary of your installation choicesand click Install.To change the settings, click Back to return to the appropriate configuration screen.The amount of time this takes depends on the size of the database and may take betweenseveral seconds and, for large databases, several hours. A progress box shows the status ofthe installation action currently in progress. When all of the required actions are completed,a final post-upgrade information screen is displayed.

20. On the Installation Summary screen, review the installation summary.If you prefer, you can click Show postinstall summary to open a file that contains theinstallation summary.

21. Indicate whether you want to start ADS, and then click Finish to exit the installationprogram.

What to Do Next

When upgrading from a version earlier than 12.1, you must switch to the new root cause discoverymode. On the upgraded ADS, in Control Panel, select Advanced Properties Editor and changethe SIMPLE_ROOT_CAUSE property value to 1. For compatibility reasons, the upgrade does notenable the new algorithm automatically. Note that the new root cause classification mode doesnot affect historical data, which is always shown according to the previously performedcategorization. After SIMPLE_ROOT_CAUSE is enabled, the ADS classifies all of the data reachingthe server using the enhanced algorithm.If you have not already obtained and installed a license, do so now. For more information, seeLicensing Data Center Real User Monitoring Components in the Data Center Real UserMonitoring Administration Guide.

ADS Smoke TestAfter upgrading the ADS to the latest release, conduct the following validation steps.

1. Review the<ADS_INSTALL_FOLDER>\log\install\Advanced_Diagnostics_Server_Install_xx_xx_xxxx_xx_xx_xx.log

file.Ensure that no errors occurred during migration, especially during the database upgrade.

2. From the ADS main menu, open Tools ➤ Diagnostics and view the System Status report.Perform basic validation of the ADS after migration

NOTEYou should allow at least three hours after the upgrade to allow new data to be processedby the ADS.

Review the following sections on the report:

LicenseMake sure that the licenses are valid and available for all of the decodes you require.



RepositoryMake sure the current status of BULK INSERT is true.

Connection with AMDs and ProbesMake sure the ADS is able to reach all enabled AMDs and Probes.

Data processingCheck whether there is a delay in data processing (if the AMD was just started, thedelay should be decreasing slowly).

Database info“Free space among allocated space cumulated with space allowed to be allocated”:Make sure there is enough space on the drive for the database to grow if necessary.

Memory sectionMake sure the ADS meets or exceeds minimum memory size requirements. Refer tothe Data Center Real User Monitoring Hardware Recommendations.

Small/large modeReview the Operation Data Limit to verify that the default threshold (for operations)was not exceeded.

3. Review the CAS-to-ADS drill downDrill down from the CAS to an ADS report to ensure that the link to page elements isworking and that ADS data is being collected.

Upgrading AMD SoftwareTo upgrade an existing installation of AMD software and preserve the AMD configurationsettings, run the upgrade file in the software distribution as described in the following procedure.To upgrade both the AMD software and the underlying operating system, you must first upgradethe AMD software running on the old operating system. This upgrade process allows you tosave the AMD configuration in a format that can later be restored on the upgraded system. Referto the Data Center Real User Monitoring Agentless Monitoring Device Installation Guide forcomplete instructions on upgrading the operating system.

Upgrading the AMD SoftwareUpgrade the AMD software using the upgrade packages provided by Compuware.

1. Log on to the AMD as root user.2. Mount the latest AMD upgrade disc, typically Compuware APM DVD 2.

Insert the AMD upgrade disc into your DVD drive and mount the drive with the command:mount /dev/cdrom /mnt

If you are working with a different installation, your device mount location may be different.In such cases, you can skip to Step 4 [p. 41].For more information, see Operating System Related Issues in the Data Center Real UserMonitoring Agentless Monitoring Device Installation Guide.

3. Go to the upgrade directory.Change your current working directory to AMD on the DVD drive with the command:



cd /mnt/AMD

4. Select the upgrade file.For more information, see AMD Software Installation and Upgrade Script in the DataCenter Real User Monitoring Agentless Monitoring Device Installation Guide.

5. Test the system readiness for the AMD software installation.Run the selected upgrade file with the --test-system parameter. For example:./upgrade-amd-amdos6-x86_64-ndw-12-02-00-2119-b001.bin --test-systemA summary is displayed after tests are run. If a message indicates that no issues were found,proceed to the next step. Otherwise follow the instructions on the screen. You may beprompted to either install missing software or to disable services that affect the AMD'sperformance. For more information, see Preparing the Operating System for AMD SoftwareInstallation in the Data Center Real User Monitoring Agentless Monitoring DeviceInstallation Guide.

Example 1. System Output on a System Ready for AMD Software Installation

[root@vantageamd cdrom]# ./upgrade-amd-amdos5-x86_64-ndw-12-02-00-1234-b001.bin

--test-system

AMD Installation and Upgrade Utility, Copyright (C) 2005-2013 Compuware Corp.

Installation version: AMD 12.02.00.1234 with OpenSSL support

Installation architecture: x86_64

Installation type: Upgrading AMD 12.02.00.1012 with OpenSSL support

Installation started on: Wed Apr 4 12:31:51 CEST 2013

No missing dependencies, it is OK to install AMD software

6. Run the selected upgrade file in the installation directory.At the command line prompt, type:./file_name

where file_name is the name of the correct upgrade file.Before the AMD software is installed, a script is run to check whether all softwaredependencies are resolved. If any auxiliary packages are missing, the process stops and themissing package names are listed. If this occurs, use your Red Hat subscription repositoryor the system installation media to install the required packages. Note that the AMDinstallation scripts list only the packages on which the software is directly dependent. Thelisted packages may have further dependencies that also need to be resolved and are pulledin automatically by package management software such as yum. In special cases, you canuse additional parameters for the upgrade command to help you automate necessary systemupgrade steps. For more information, see AMD Software Dependencies and Conflicts inthe Data Center Real User Monitoring Agentless Monitoring Device Installation Guide.

IMPORTANTAn updated Linux kernel may be installed as an effect of a software compatibility check.If this happens, a system restart is necessary so that the proper kernel version is in use. Formore information, see Resolving Linux Kernel-Related Compatibility Issues in the DataCenter Real User Monitoring Agentless Monitoring Device Installation Guide.



If the installation script discovers that, after setup, the available disk space is below theminimum space required, a message is displayed. If this happens, you must make a suitableamount of free disk space available before continuing.

Example 2. Warning Messages on System with Insufficient Amount of Free Disk Space

Warning: Insufficient free disk space available.

/usr/adlex/rtm/bin requires at least 2GB

/var/log/adlex requires at least 1GB

/var/spool/adlex/rtm requires at least 10GB

7. Optional: Select the correct SSL engine (applies to nCipher support only).Because of hardware constraints, the installation procedure performed by the upgrade filemay not be able to detect the exact type of the nCipher accelerator card (nShield or nFast),and it configures the AMD for nShield. If the card installed is not nShield, you mustmanually modify the appropriate AMD configuration property after the upgrade file isexecuted. To do this, open the /usr/adlex/config/rtm.config configuration file andfind the ssl.engine property, which defaults tossl.engine=nshield

If the installed card is nFast, change the setting from nShield to nfast.

8. Reboot the AMD to complete the upgrade.

After the AMD is restarted, you can use the ndstat command to view the installed packagesand their versions.

Example 3. Example of ndstat Output After the Upgrade

[root@vantageamd ~]# ndstat

=== Installed packages

adlexrtm-ndw.12.1.0.791-1.el5.x86_64

java-1.6.0-sun-1.6.0.14-1jpp

adlexv2page-12.1.0-24.el5.x86_64

adlexpage2trans-12.1.0-7.el5.x86_64

rtmperf-12.1.0-1.el5.x86_64

adlexsnmp-12.0.0-6.el5.x86_64

libadlexpcap-1.1-12.el5.x86_64

adlexcron-1.0.8-1.el5.noarch

tomcat-amd-12.0.0-10.el5.x86_64

cpwrdlm-4.5.0-16.2.el5.x86_64

rtmgate-12.1.0-28.el5.x86_64

avagt-12.1.0-213.el5.i386

cba-12.1.0-791.el5.x86_64

cba-agent-12.1.0-35.el5.x86_64

nfc-12.1.0-791.el5.x86_64

Installation type: rtm

AMD Smoke TestAfter upgrading the AMD to the latest release, perform the following validation steps.

1. Review the AMD install log file, /var/log/adlex/upgrade.bin.log, to ensure that noerrors occurred during the AMD upgrade.

2. Verify the basic AMD configuration.Run rtminst and verify that the AMD configuration is correct (sniffing ports setup, memorylimits) – review options 2, 3 & 4 in rtminst.



3. Verify the Compuware user account.Make sure that the Compuware user account exists in Linux. If it does not, re-runupgrade.bin with the --force switch to re-create this account and set the required fileand folder ownership to this user for proper AMD operation

4. Use the custom drivers rather than native drivers if possible.Review the list of sniffing NICs and check whether only custom-driver-supported NICscan be used for traffic sniffing purposes.

5. Perform sniffing port diagnostics.Use the RUM Console (Guided Configuration) to record a trace file for analysis. Examinethe Sessions section in detail.

6. Perform SSL diagnostics.Use the RUM Console (Guided Configuration) to record a trace file for analysis. Examinethe SSL Diagnostics section in detail. Remember to log in (authenticated user) to the SSLcard if the AMD was rebooted after upgrade.

7. Verify the time synchronizationExamine the /var/log/adlex/rtmgate.log file to make sure the AMD clock issynchronized with at least one CAS (the main server to which this AMD is attached), orverify that NTP-based time synchronization is enabled instead and is working properly.

8. Perform an AMD resources check.On the CAS, access the AMD Statistics reports to review the following:

• AMD Packet Processing Statistics – compare number of received packets before andafter the migration. Check for any anomalies such as a significantly increased ordecreased number of packets received by AMD

• AMD CPU Statistics

• AMD Capacity Status – focus on the memory usage.

9. Check for AMD restarts.Check the rtm.log for unexpected AMD restarts (there should be none).

Adding Missing Software After Red Hat Enterprise Linux 6Kickstart Installation

After Red Hat Enterprise Linux 6 is installed using the kickstart method provided by Compuware,you need to add several packages to be ready for the AMD software installation. The packagesmust be installed manually or from the Red Hat Network using an Internet connection. You canuse the AMD software installation script as an aid for installing the missing packages.

Before You Begin

Register your system and enable subscriptions. Refer to Red Hat Enterprise Linux 6 DeploymentGuide (http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/) to find a suitable solution for “Product Subscriptions and EntitlementsManagement.” If your AMD has no Internet connection, you will need to perform registration



http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/




on another machine and download the packages to a location that can be accessed from theAMD.To install the required software, you must enable the following repositories on the Red HatNetwork website:RHEL Workstation Optional or RHEL Server OptionalRHEL Workstation Supplementary or RHEL Server supplementaryChoose a server or workstation repository to match your installed operating system variant.

To display the list of packages that are required by the AMD software but not installed in thesystem, run the installation script with --list-missing-deps parameter. For example:./upgrade-amd-amdos6-x86_64-ndw-12-02-00-1234-b001.bin --list-missing-deps

The packages required for AMD software installation and not included in the base workstationor server repository include:

• perl-XML-Simple available from RHEL Workstation Optional or RHEL ServerOptional repository.

• xerces-c available from RHEL Workstation Optional or RHEL Server Optionalrepository.

• java-1.6.0-sun available from RHEL Workstation Supplementary or RHEL Serversupplementary repository.

Install from Red Hat Network

Install the missing packages directly from the Red Hat Network if your AMD has an Internetconnection.

• Change the working directory to the location where the upgrade.bin is placed.

Install from Local Repository

• Perform a manual installation of the missing packages from a locally created repository ifthe AMD has no Internet connection.To run this procedure successfully, you must install createrepo using the Red HatEnterprise Linux installation disc or online repository. For example: yum installcreaterepo.1. Navigate to the location where the upgrade.bin is placed and run the script with the

--list-missing-deps parameter.2. Collect all of the indicated packages and prepare them for copying.

Use the installation media or official Red Hat repositories as the source for the packages.

NOTEIf your AMD's Linux was installed without using the kickstart script and you do nothave access to the network, you must create a local repository that contains the packagesfrom all of the Linux distribution DVDs. The missing packages that are listed usingthe --list-missing-deps parameter have additional dependencies located throughoutthe Linux distribution set.



3. Use an SFTP client (for example, WinSCP) to log in to the AMD.4. Copy the necessary packages to the directory of your choice on the AMD. For example:

/tmp/amdrepo.5. Log in to the system as root.6. Navigate to the directory where the packages are located and run the createrepo

command. For example:createrepo /tmp/amdrepo

7. Navigate to the location where upgrade.bin is placed and run the script with the--install-deps-from-url parameter. For example:./upgrade-amd-amdos6-x86_64-ndw-12-02-00-1234-b001.bin

--install-deps-from-url file:///tmp/amdrepo

As a result, the AMD software dependencies and other auxiliary packages are installedfrom the custom repository.

What to Do Next

After the missing packages are installed, you can perform the regular AMD software installationprocedure. For more information, see Installing the AMD Software in the Data Center RealUser Monitoring Agentless Monitoring Device Installation Guide.



C H A P T E R 3

Upgrading the Enterprise Portal

The Enterprise Portal was introduced in release 12.0 as a common reporting component for DCRUM and BSM. If you implemented the 12.x Portal, upgrade it to release 12.2. For moreinformation, see Upgrading the Enterprise Portal to 12.2 [p. 47].After upgrading the Portal, if you use BSM, you will need to deploy the applicable BSMdashboards. For more information, see Deploy BSM Dashboards in the Portal [p. 48].

Upgrading the Enterprise Portal to 12.2If you are using Enterprise Portal 12.x, upgrade to release 12.2:

1. Stop the Enterprise Portal service.2. Install a Portal 12.2 over the existing release. For Windows, the installer is available on

DVD 1 at Enterprise Portal\Windows\install.exe. The Linux and Unix installersare on DVD 2 and 3, respectively.After the installation starts, you will see a message that an existing release was found onthe machine. Click OK to proceed with the installation.

Verify Successful Upgrade

Check to see if your custom dashboards and reports are available in the upgraded release.

3. Go to Start ➤ All Programs ➤ Compuware ➤ Enterprise Portal 12.2.4. Log in with an administrator's account.5. If you are using the Portal with DC RUM:

• Make sure the correct CAS is integrated with the Portal. Only a master CAS shouldbe used.

• Confirm that the number of applications shown under the Application Health Statusreport is the same as the number of applications displayed on the CAS report.

If you are using the Portal with BSM, confirm that your dashboards exist. Go toDashboards ➤ Manage Pages and see if your dashboards are listed. They will not beoperational until you deploy the correct BSM web application.


What to Do Next

If you are using BSM, deploy the BSM web application for the Portal.

Deploy BSM Dashboards in the PortalBSM 12.2 dashboards are available in the product distribution as a zip file. Extract the zip fileto the Enterprise Portal installation directory to enable the default BSM dashboards for the BSMrelease you are going to use.

NOTEIf you have upgraded the Portal, but want to stay on an older BSM release (12.0 or 12.1), youneed to apply the latest service pack for that release, and deploy the proper web application tomatch your release. Go to FrontLine to download back-release web applications.

Do not create a separate directory for the contents of the BSM zip file. Extract it to the EnterprisePortal base installation directory. The files are automatically distributed to the appropriatesub-directories.

1. Download BSMWeb.zip from Business Service Manager\EntPortalWebApp on DVD1. This file contains the BSM dashboard web application.

2. Stop the Enterprise Portal service.3. Delete the following folders:

a. <install>\tomcat\webapps\cwinfocenter

b. <install>\tomcat\work\Catalina\localhost\cwinfocenter

NOTEIf you previously deployed a version of BSMWeb[version].zip and are deploying a newversion, also delete the folder <install>\tomcat\webapps\centauri.

4. Extract the contents of BSMWeb[version].zip to the Enterprise Portal base installationdirectory making sure to overwrite files and merge folders.Click Yes to overwrite or merge the contents, if prompted.After you extract BSMWeb.zip to the base install directory, verify the following files areincluded:

• Several files in the <Portal_Home>\deploy folder.

• Two new war files (centauri.war and cwinfocenter.war) in<Portal_Home>\tomcat\webapps folder.

• The bsmWebVersion.xml file in the <Portal_Home> folder.

5. Restart the Enterprise Portal service.The BSM dashboard web application is now deployed.

6. Configure BSM by clicking Control Panel from the main menu.

a. Click Integrations ➤ BSM Server Lines ➤ Enable Business Service Management.b. Click Apply.


Chapter 3 ∙ Upgrading the Enterprise Portal

http://frontline.compuware.com/

7. Click Control Panel ➤ Server Administration ➤ Actions ➤ Reindex all searchindexes ➤ Execute.

If you are not upgrading your BSM deployment, check to see if your dashboards are workingas expected. If you are upgrading BSM, see the migration instructions that follow. For moreinformation, see Migrating BSM [p. 51].

NOTEIf you want to use a BSM server with the same host and port as the previous release, manuallycopy Main ServletProperties.xml from the backed up files after the BSM web applicationis deployed. An alternative is to reconnect your integration between the Portal and BSM.



C H A P T E R 4

Migrating BSM

NOTEBefore migrating to the new release, contact Compuware Customer Support to assess yourmigration scenario, especially if BSM is currently deployed under any of the following conditions:

• Using release 11.7 or earlier.

• Using custom dashboard layouts and portlets.

For more information, see Customer Support Information [p. 10].

You can migrate 12.0 or later Service Model data, dashboards, and reports to release 12.2.Following is an overview of common migration scenarios.The 12.2 Enterprise Portal is backward-compatible with BSM 11.7 or later, if the latest servicepack is applied and the correct BSM web application is deployed. You may choose to upgradethe Portal to 12.2 for use with DC RUM, and keep BSM at a supported back release. For moreinformation, see Deploy BSM Dashboards in the Portal [p. 48].

Migrating BSM from 12.x Following a DC RUM Upgrade to 12.2

If you upgraded the Enterprise Portal with DC RUM 12.2:

1. Deploy the 12.2 BSM web application for the Portal. For more information, see DeployBSM Dashboards in the Portal [p. 48].If you did not upgrade the Portal with DC RUM 12.2, upgrade it first to 12.2 beforedeploying the BSM web application. For more information, see Upgrading the EnterprisePortal to 12.2 [p. 47].

2. Install the Service Model Components [p. 53].

3. Migrate the Service Model Database [p. 55] and refer to the Migration Checklist [p. 52]for other tasks that are required to migrate your Service Model.


Migrating BSM from 12.x (without Upgrading DC RUM)

1. Upgrade the CSS and Enterprise Portal to 12.2. For more information, see Upgrading toCSS 12.2 [p. 22] and Upgrading the Enterprise Portal to 12.2 [p. 47].

2. Deploy the 12.2 BSM web application for the Portal. For more information, see DeployBSM Dashboards in the Portal [p. 48].

3. Install the Service Model Components [p. 53].

4. Migrate the Service Model Database [p. 55] and refer to the Migration Checklist [p. 52]for other tasks that are required to migrate your Service Model.

Migration ChecklistUse the following checklist to plan and execute your migration to the latest release.

TaskCompleted

Contact Customer Support to assess your migration scenario.

Review the system requirements for the new release to determine if your environmentsupports a new installation. Note that you cannot install BSM release 12.2 on 32-bitoperating systems. For more information, see System Requirements in the BusinessService Management Installation Guide.

Review the migration prerequisites to ensure you are ready to install the new releaseand migrate data to it.

Make a backup of your current environment, including databases. Export the ServiceModel configuration data using the Configuration Management wizard.

Deploy BSM Dashboards in the Portal [p. 48]

Install the BSM Service Model components on the same machine as the existing release.For more information, see Install the Service Model Components [p. 53].

Migrate the Service Model Database [p. 55]

Run the Server Migration Utility [p. 56]

Migrate Additional Files [p. 57]

Edit EUE Adaptor Configuration (Migrating from Releases Prior to 12.1) [p. 58]

Migrate the Event Console Configuration [p. 58]

Determine if your Service Model migrated properly. Check to see if you have the samenumber of services in your model, and if the service states are as expected. Poll theconnections and see if the service states are as expected.

Do a final validation of the dashboards using the upgraded Service Model.

Uninstall the previous release.


Chapter 4 ∙ Migrating BSM

Migration PrerequisitesBefore migrating to release 12.2, do the following:

• Ensure that the server hardware, operating systems and application servers meet or exceedthe recommended system requirements for the new installation. For more information, seeSystem Requirements in the Business Service Management Installation Guide.

• Ensure you have at least 3 GB to 5 GB of temporary disk space for the installer processand 3 GB of space for the installed BSM. You must also have established your databasehostname with login information.

• Upgrade the CSS and Portal to release 12.2 and deploy the 12.2 version of the BSM webapplication. For more information, see Upgrading to CSS 12.2 [p. 22] and Upgrading theEnterprise Portal [p. 47].

• Make a backup copy of the existing database before beginning a migration or upgrade. Youwill restore the backed up Service Model database over the new Service Model databasecreated with release 12.2.

• As a precaution, use the Support Utility to back up critical Service Model Server files. Formore information, see Backing Up the Service Model Server in the Business ServiceManagement Administration Guide.

• As a precaution, export your Service Model configuration files, using the ConfigurationManagement wizard. Importing the configuration data after upgrading to the new releasemay solve some migration issues. For more information, see Configuration ManagementWizard - Export Configuration Action in the Business Service Management AdministrationGuide.

• Optional: BSM 12.2 provides optimized calculation of metric statistics based on hourlyaggregations. Calculate hourly statistics before starting the database migration so you cantake advantage of these optimizations, ensure data validity for metrics for services withaggregated metric profiles, and prevent the migration of potentially large amounts of rawmetric data. This can be done by scheduling a statistics job for services of interest for therequired time periods and schedule priorities.

• Deactivate connections for any adaptors that are deployed.

Install the Service Model ComponentsIf you have successfully upgraded the CSS and Portal to 12.2, install the Service Modelcomponents.


• DVD1 Windows

• DVD2 Linux

• DVD3 AIX HPUX

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.If you downloaded the product, go to the equivalent folder in your downloaded copy andrun the setup.exe application.

3. In the Compuware APM installation browser, go to the Additional Products tab and clickBusiness Service Manager to open the installation wizard.A window displays the progress for extracting the installer. Preparing to install may takeseveral minutes.

4. On the Introduction page, review the instructions and then click Next.5. On the License Agreement page, review the terms of the license, indicate whether you

accept the terms of the agreement, and click Next to continue or Cancel to quit.If you do not accept the terms of the agreement, you cannot install the software.

6. On the Installation Folder page, review the destination drive and path, make any necessarychanges, and then click Next.All selected components will be installed in this single location.

7. In the Installation Type screen, select either Client and Server applications (mostcommon) or Connection Manager Server and click Next.When selecting Client and Server applications, you have the option to install only theclient or Service Model Server. By default, both are selected.

8. In the Database Configuration screen, select the database type to be used for BusinessService Manager (SQL Server or Oracle), and enter the following:

9. In the Database Name screen, the default database name for BSM is displayed. If youwant a database with this name to be created, leave the default values and click Next.You will later overwrite this database with the backed up database from the previous release.

10. The Business Service Management - Port Configuration screen displays available portsselected for BSM components. Click Next to continue with these selections.After installing the product, you can change the port settings from the Configuration Client'smain menu. Go to Windows ➤ Preferences ➤ Server Configuration.

11. In the Business Service Management - Memory Configuration screen, JVM memorysettings are displayed by default. The initial memory displayed is half of the availablememory detected on the system. You can change the initial memory as needed. Click Nextto proceed.

12. On the Pre-Installation Summary page, review the configuration information carefullyto ensure that you have selected the options you want to install. If correct, click Install tobegin installation.To make changes, click Previous until you get to the relevant page, change your selection,and then click Next until you return to this page.After you click Install, your selections are installed.

NOTEDepending on the options you chose, this may take considerable time.



13. When the installation is finished, the Install Complete page notifies you of the generalinstallation status. Review the installation status message and click Done to exit the installer.

What to Do Next

After all components are installed, migrate the Service Model data to the new release.

Migrate the Service Model DatabaseYou will need to install the new release of the Enterprise Portal and BSM before migrating data.For more information, see Migration Checklist [p. 52].

CAUTIONIf errors occur during database migration, you will not be able to continue with this process.Restore the database, and contact Compuware Customer Support for assistance. For moreinformation, see Customer Support Information [p. 10].

1. If necessary, stop the Enterprise Portal and Service Model services on the previousrelease, and the Compuware Service Model 12.2 service on the new release.

2. Restore the Service Model database backed up from the previous release, overwriting thenew 12.2 Service Model database.If you used the default database name during the 12.2 BSM installation process, a newdatabase named BSM was created.

3. Navigate to the BSM_HOME/server/misc/migration/database folder and execute theapplicable database migration command that matches your migration scenario (from 12.0or 12.1).The following dialog box is displayed:

4. Enter information for the new BSM database and click Migrate. Note the following:



• The User Name must have the authority to create, delete, and modify tables in thedatabase.

• If you use raw metric data for charts in the dashboards, and want to retain those rawmetrics in the new release, set a retention period in the Days to Keep Raw MetricData field. Enter a value that reflects how far back you may need to request raw metricdata. The default is 90 days.

• If your database is Oracle, assign the necessary permissions for this BSM release.

◦ ALTER ANY INDEX

◦ ALTER ANY SEQUENCE

◦ ALTER ANY TABLE

◦ ALTER ANY TRIGGER

◦ CREATE ANY INDEX

◦ CREATE ANY SEQUENCE

◦ CREATE ANY PROCEDURE

◦ CREATE SESSION

◦ CREATE TABLE

◦ CREATE TRIGGER

◦ CREATE VIEW

◦ UNLIMITED TABLESPACE

What to Do Next

Run the Server Migration utility.

Run the Server Migration UtilityThe installation for the new release includes a utility for migrating the earlier version of theService Model Server.

Before You Begin

Stop the Compuware Service Model 12.2 service.

1. Navigate to the server migration folder.On the machine where BSM release 12.2 is installed, open a command window, thennavigate to the folder: BSM_HOME/server/misc/migration/server/.

2. Execute MigrateServer.bat.Run the batch file as an administrator. If User Account Control is enabled, you must runthe batch file from a command prompt.

3. Specify the earlier release that you have installed.You can migrate to release 12.2 from release 12.0 or later.



4. Specify the source directory.When prompted, enter the full path for <BSM_HOME> for the previous release.

5. Specify the target directory.When prompted, enter the full path for <BSM_HOME_12.2> for the new release.

After you specify the locations of the previous and new releases, the utility does the following:

1. Stops the Release 12.2 service if necessary.

2. Backs up the files required for migration in both the source and target directories.

3. Copies the following files from the source directory to the target directory:

• Connection Manager configuration file: ConnectionManager.xml

• Adaptor Message Translator configuration files: *_MessageTranslator.xml

• Service Templates configuration file: ServiceTemplates.xml

• Database Filter Message Translator: DatabaseFilterMT.xml

• User Database configuration file: UserDatabase.xml

Migrate Additional FilesManually copy any custom and third-party files, such as customized adaptors and JavaScriptlibraries, that were used with the previous release but are not included in the new defaultinstallation.If you used third-party libraries with the previous release, copy the files to the correspondinglocation in the new release. For more information, see Checking Directory Contents in theBusiness Service Management Installation Guide.

What to Do Next

Some files from the previous release cannot be copied into the new release, because overwritingthe new file would destroy required information that was not contained in the previous release.If you customized any of the following files, you must manually edit the files in the new release:

• All BSM_HOME/server/bin/*.properties files

• Out of Order processing configuration found inBSM_HOME/server/config/HistoricalDataImport.xml

• BSM_HOME/server/config/Navigator.Client.xml

Compare the old and new files, and edit the new file as needed to match the customizedinformation in the previous release.

CAUTIONBe careful not to delete any content, or alter the content other than the custom configurations.



Edit EUE Adaptor Configuration (Migrating from Releases Priorto 12.1)

If you are migrating from a BSM release prior to 12.1, perform the following procedure.

1. Restart the Compuware Service Model 12.2 service.It may take some additional time for the server to start as it completes the migration process.

2. Open the BSM client. In the Connection Configuration view, select the End UserExperience adaptor, and click the Configure button.

3. Verify that the message translator is configured correctly. Select the filter of theSys_GenerateParameterId rule and confirm that the expression contains only double-equalsigns like this:((VantageDataCollector=="COS") || (EventType=="DataException"))

4. If it has a single equal symbol, edit the expression.5. Edit the SetParameterId action.

In the bottom third of the script, replace:if (Site != null)

paramId += _Result.getProperty("LocationId") +" Loc/";

withif (Site != null && Site != "*" && Site != "" && Site != "All Other")

paramId += _Result.getProperty("LocationId") +" Loc/";

6. Save your changes.

Optional: Import Previous Release's Service Model ConfigurationData

If you have errors in your migration, one remedy would be to import the Service Modelconfiguration data from the previous release that was exported prior to upgrading. For moreinformation, see Configuration Management Wizard - Import Configuration Action in theBusiness Service Management Administration Guide. If you have any errors, contact CustomerSupport to assess your situation.

Migrate the Event Console ConfigurationMigrate the Event Console configuration by copying the configuration details from the previousrelease to the new release.

1. Open both the previous release of the Event Console and the new release.2. Open the Preferences windows.

Select Edit ➤ Preferences in each to open the Preferences window for the Event Consolein both releases.

3. In the Main node, copy the values for all the fields from the previous release to the newrelease.

4. Skip the Visible Columns node.



The Visible Columns node cannot be migrated because the columns are only visible afternew events are received. When new events that contain different parameters are receivedin the new Event Console, you can then choose columns as needed.

5. Set the colors in the new release.

a. In the Event Colors node, change the colors for test and backgrounds to the same asthe previous release.

b. In the Color Rules node, add the color rules from the previous release.

6. In the Actions node, add the actions from the previous release.

7. In the Timers node, copy the script from previous release to new release, and then set theInterval value.

8. In the Advanced Filters node, add custom filters one-by-one.You cannot copy the entire expression at once; you must add the sub-expressions one-by-one.

9. In the Misc node, copy the values.



C H A P T E R 5

Migrating VantageView

This chapter provides information about the migration prerequisites, the migration process, andpost-migration information:

• Migration Overview [p. 61]

• Migration Checklist [p. 63]

• Migration Prerequisites [p. 62]

• Migrating VantageView to the New Release [p. 65]

• VantageView Data Migration [p. 65]

VantageView Release 12.0 can be upgraded from Release 10.2 or higher. To upgrade fromRelease 10.2, the latest service pack must be applied.If you migrate VantageView from a release earlier than 11.5, and you have other CompuwareAPM products, you may not be able to use your current release of the other product(s) withVantageView Release 12.0. For more information, see Compatible Compuware APM ProductReleases [p. 62].

Migration OverviewBefore beginning the VantageView migration:

• Review the system requirements to ensure that the hardware you are using is sufficient torun VantageView. This is especially true if you are running VantageView with otherCompuware APM product components on the same machine. For more information, seeSystem Requirements in the VantageView Installation Guide.

• Make sure your current installation is a release that can be migrated to the new release,with service pack applied if necessary.

CAUTIONDo not uninstall the earlier release of VantageView before migration. If you do, you will losesaved reports and other VantageView settings.

Complete these tasks to migrate from an earlier VantageView release.


1. Install a new VantageView environment.

2. Migrate the data from the earlier release to the new VantageView.

3. In the new VantageView, select Administration and re-save existing database connections.

4. If necessary, upgrade your other Compuware APM products that use VantageView. If yourother products are at the minimum supported release level for the new VantageView release,you can upgrade those products later at your convenience. For more information, seeCompatible Compuware APM Product Releases [p. 62].

Migration Prerequisites

Database

• Make sure the SQL Server database is set as case-Insensitive. VantageView products cannotbe installed on a database server that is case-sensitive. A default SQL Server installationis case-insensitive, which means that SQL Server does not differentiate between upper-and lower-case characters. In SQL Server, this setting is called collation.

• Verify the version of the SQL Server database. SQL Server 2000 is not supported. Thedatabase must be SQL Server 2005 or 2008 before migration.If you are migrating VantageView data and the new VantageView database will be on adifferent server than the existing database, then the SQL Server version of the new databasemust be the same as or later than the version of the current database.

• Back up the current database. Compuware recommends that you back up VantageViewbefore migrating. The backup process includes the VantageView database and otherVantageView data stored on the server.

• If you will be migrating VantageView data to a new server, then before you use theVantageView Data Utility, create a folder named Dev97 under the Migrate folder in thecurrent VantageView installation directory.You can move the data manually, instead of using the VantageView Data Utility.

SQL Server Agent Service

When the VantageView database is created, SQL Server jobs are installed for maintaining alerts.If you want alert maintenance to be active, make sure the SQL Server Agent service is startedand that its Startup Type property is set to Automatic.

Service Packs for Companion Products

Before migrating VantageView, check FrontLine (http://frontline.compuware.com) for anyservice packs that may need to be installed for related products. For more information, seeInstalling Service Packs in the VantageView Installation Guide.

Compatible Compuware APM Product ReleasesVantageView Release 12.0.4 is compatible with specific releases of other Compuware APMproducts. If the following products are upgraded to at least the minimum supported release, you


Chapter 5 ∙ Migrating VantageView

http://frontline.compuware.com

can migrate VantageView first, and upgrade the other products at your convenience. If youchoose not to upgrade unsupported releases of other products, portions of VantageView maynot work properly. Reporting and alerts will function correctly with Compuware APM productsat the following release levels.

Table 5. Supported Releases

Supported ReleasesCompuware APM Product

Release 11.5, 11.7, and 12.0 with latest service packapplied

Server Monitoring [ServerVantage]

Release 11.7, 12.0, 12.1, and 12.2 with latest servicepack applied

Synthetic Monitoring [ClientVantage, PrivateEnterprise]

Release 9.9 with latest service pack appliedClientVantage (Passive)

Release 10.0 with latest service pack appliedNetwork Monitoring [NetworkVantage]

Release 11.5 with latest service pack appliedJava/.NET Monitoring

Release 11.5, 11.6, 11.7, 12.0, 12.1, and 12.2 withlatest service pack applied

Data Center Real User Monitoring [Vantage forReal User Monitoring]

For product-specific information refer to the Compuware APM Upgrade and Migration Guide.Refer to the Database Utility online help for more information about working with databasescreated in Microsoft SQL Server.After the VantageView migration, you must re-save all Synthetic Monitoring and NetworkMonitoring database connections, Network Monitoring Enterprise Managers, and ServerMonitoring Control Server connections with the appropriate Alerts Server selected so thatVantageView alerts will be properly displayed in VantageView. For more information, seeConfiguration in the VantageView Installation Guide.

Migration ChecklistUse this checklist to ensure that all tasks are completed to migrate VantageView successfully.Migrate VantageView before migrating other Compuware APM products. In most cases, aslong as the companion Compuware APM products are a compatible release, you do not needto migrate them immediately after migrating VantageView. For more information, see CompatibleCompuware APM Product Releases [p. 62].

CAUTIONDo not uninstall the earlier VantageView release before verifying that the migration is completeand successful. If you do, you will lose saved reports and other VantageView configurationsettings.



Table 6. VantageView Migration Checklist

StepsFinished

Confirm that your current installation is a release that can be migrated to the new release,with service pack applied if necessary.

If necessary, apply the latest service pack to your present VantageView release. For moreinformation, see Installing Service Packs in the VantageView Installation Guide.

Review the system requirements to ensure that the hardware you are using is sufficient torun VantageView. This is especially important if you are also running other CompuwareAPM products. For more information, see System Requirements in the VantageViewInstallation Guide.

Review the migration prerequisites. For more information, see Migration Prerequisites[p. 62].

Make sure the SQL Server database server is configured as case-insensitive. TheVantageView database cannot be installed if SQL Server is set to case-sensitive. In SQLServer, this setting is called collation.

If you are migrating the VantageView data and the database to a new server, make surethat you are migrating the VantageView database to the same version of SQL Server as theearlier release. For more information, see Migration Prerequisites [p. 62].

NOTESQL Server 2000 is no longer supported. You must upgrade to SQL Server 2005 or SQLServer 2008. For more information, see Moving the SQL Server Database Between Platformsin the VantageView Installation Guide.

Back up the current VantageView database and data files/folders. For more information,see Backing Up and Restoring VantageView in the VantageView Installation Guide.

Make sure the SQL Server agent is configured to start automatically after the VantageViewdatabase has been migrated.

Install a new VantageView environment on the target machine. For more information, seeMigrating VantageView to the New Release [p. 65].

Migrate the data from the previous database. For more information, see VantageView DataMigration [p. 65].

Reconfigure the database authentication, as needed.

• If you created the VantageView database using Windows Authentication, enableWindows Authentication again after migration. For more information, see ConfigureWindows Authentication in Windows Server 2003 in the VantageView InstallationGuide and Configure Windows Authentication in Windows Server 2008 in theVantageView Installation Guide.

• During VantageView migration, authentication based on SQL Server accounts isrestored to the defaults. Any previously configured domain-based security settingsmust be reapplied. For more information, see Implementing Domain-based DatabaseSecurity in VantageView in the VantageView Installation Guide.



Table 6. VantageView Migration Checklist (continued)

StepsFinished

When VantageView is migrated successfully, reconnect the connections to the CompuwareAPM product databases. For more information, see Configure Database Connections inthe VantageView Installation Guide.

VantageView Data MigrationTo retain existing VantageView reports, do one of the following:

• Migrate data during installation of the new release. For more information, see MigratingVantageView to the New Release [p. 65].

• Use the VantageView Data Utility to migrate prior release data to the Release 12.0installation.

The migration process migrates the following VantageView items:

• Reports

• Filters

• Database connections

• Server groups

• User preferences

• User IDs

• Alert data

• Visualizer diagrams

The following are not migrated:

• Custom code

• Custom style sheet

• Custom banner logo.xml

• Custom icons

• Custom sounds

Migrating VantageView to the New ReleaseBefore starting the migration procedure, review the prerequisites. For more information, seeMigration Prerequisites [p. 62].Follow the steps below to migrate VantageView to the new release.

CAUTIONDo not uninstall the earlier release of VantageView before migrating. If you do, you will losesaved reports and other VantageView settings.



1. Verify that your system meets the minimum hardware and software requirements.2. Log on to the Windows server using an ID with administrator privileges.3. Select the installation disc that matches your target machine's operating system:

• DVD1 Windows

• DVD2 Linux

• DVD3 AIX HPUX


5. Select the Synthetic Monitoring tab, then click VantageView.The Operating System Updates window appears. The installation process runs an operatingsystem (OS) update check, then lists the OS update items that will be installed. Click Next.The installation script may prompt you to restart the system after update items are installed.The installation will continue automatically after the restart is completed.

NOTE

• If SQL 2005 Backward Compatibility or Microsoft .NET Framework does not alreadyexist on your system, it will be installed.

• During the installation, a message may be displayed that the IIS ASP extension is notenabled. Click OK. The IIS ASP extension is one of the web service extensions requiredfor VantageView. For more information, see Server Prerequisites in the VantageViewInstallation Guide.

6. When the operating system updates have been installed, the VantageView Setup starts.When the Welcome to the InstallShield Wizard for VantageView appears, click Next.If the option Visit Compuware FrontLine for Product News and Technical Alerts isenabled, when you click Next, a browser window opens automatically and directs thebrowser to FrontLine so you can log in and check for the latest service packs or information.

7. When the License Agreement window appears, click Yes once you have read and agreedto the terms.

8. When the GNU Lesser General Public License Agreement window appears, click Yesonce you have read and agreed to the terms.

9. When the Customer Information window appears, type your User Name and CompanyName in the Customer Information window. Click Next.If prompted, select Yes, I want to restart my computer now. Upon reboot, the serverautomatically restarts the installation application. If the installation does not automaticallyrestart, repeat the tasks performed previously.

10. Click Next in the Choose Destination Location window to accept the default installationlocation, or click Browse to change the location.



The default installation path is C:\Program Files\Compuware\VantageView 12.0.

11. Click Next in the Choose Data Location window to accept the default data location, orclick Browse to change the location.The default data installation path, depending on your Windows version, is specified:C:\Documents and Settings\All Users\Application

Data\Compuware\VantageView 12.0 or C:\ProgramData\Compuware\VantageView12.0. However, it is common practice to install the data folder on a separate drive.

CAUTIONIf your system does not meet the minimum hardware and system requirements, you mayreceive the warning: At least one Hardware or Software recommendation hasfailed. Click OK to view the details of the components that passed and failed. Somewarnings require you to click Cancel to stop the installation process and upgrade yoursystem to the minimum hardware and software requirements before continuing theinstallation. Click Cancel to stop the installation, or Next to continue.The most common warnings are for SMTP, because SMTP is often prohibited on servers.

12. Select the web site where you want to install the VantageView application from theAvailable Web Sites menu, then, in the Virtual Directory Name field, type the name ofthe virtual directory and click Next.

NOTEThe virtual directory name must contain only letters, numbers, and hyphens. The defaultvirtual directory name is Vantage. If you are installing a new release of VantageViewwhere an earlier release was installed, this name may already be in use. If it is already inuse, the installation prohibits you from using the same name. Choose a different name,such as Vantage120.

13. In the Select Program Folder window, click Next to accept the default program folder forVantageView 12.0. You can also select an existing program folder from the ExistingFolders list, or type the name of a new program folder.

14. In the Create VantageView Database window, configure the database details.You must have system administrator permissions to create the database.a. Select the server from the Server Name menu, or type the name of the server.

NOTEIf you have multiple instances of SQL Server on the same machine, make sure theinstance name is entered as server_name\instance_name. If the full instance namedoes not appear in the list, you can type it in the field.

b. Type the Database Name.



NOTEThe database name must contain only letters, numbers, and hyphens. The defaultdatabase name is VantageViewDB. Since you are migrating, this name will likelyalready be in use. If it is already in use, the installation prohibits you from using thesame name. Choose a different name, such as VantageViewDB117.

c. Select Windows Authentication or SQL Authentication. Click Next.

NOTEIf selecting SQL Authentication, enter the proper user ID and password to create thedatabase. If selecting Windows Authentication, you must ensure that the user whichis currently logged onto the VantageView server has sysadmin rights on the SQLServer.

d. The default installation path, database size, and log size are usually sufficient, but youcan change them if needed.

15. The Migrate previous version? window appears if you are running the installation programon a machine where an earlier release of VantageView is installed. Select either:

VantageView 12.0Select this option to continue to migrate the earlier release to the new release. Theinstallation copies the data to the SQL database. If you select this option, continue toStep 7 [p. 66].

NOTESelect this option only if the previous release of VantageView is Release 10.2 or later.If you are running a release prior to Release 10.2, it must be migrated to Release 10.2,with the latest service pack, before you proceed with the migration.

Skip migration on local machineIf you select this option, the following message appears:Is there an earlier version of VantageView on another machine you

would like to migrate? If you select yes you will be prompted for

more information after the files transfer.

If you select Yes, you are prompted during the migration for information about thelocation from which you want to migrate. If you select No a new empty SQL databaseis created for you to use with VantageView. Click Next.

16. If you selected to migrate, you are prompted to specify the target and source database,directories, and virtual directory.a. On the Source tab, enter the following information for the source database:

AuthenticationYou can use either Windows Authentication or SQL Authentication to migratethe database. If SQL Authentication (default) is enabled, enter the proper UserID and Password for the database. Or select Windows Authentication.



Database InstanceSelect the VantageView database instance.

NOTEWhen you run the VantageView Data Utility to migrate data from an earlierrelease, the Source tab of the Data Utility may be populated with the connectioninformation for the previous release's database. If the Database Instance fieldof the Source tab contains localhost,1433, you must change that value:

• If you know the database instance, replace localhost,1433 with the actualinstance name.

• Otherwise, enter (local), including the parentheses, as the database instance.

Database NameIf the database name is not already displayed, type the name of the database fromthe earlier VantageView release. By default, the VantageView database is namedVantageViewDB.

LoginEnter the default login for the database if it does not appear automatically.

PasswordEnter the password for the login if it does not appear automatically.

OtherComplete the following fields:

Existing local path on Source SQL Server machine where database backupfile is to be placed

VantageView requires a valid local path on the SQL Server machine wherethe database backup will be temporarily placed. You cannot use a UNCpath. If the path doesn't exist, you must create one. The temporary backupfile will be removed when the migration process has completed.

Current location of Source data and web-publish foldersThe source data folders can be local or remote. If the folder paths are notdisplayed, click Browse or enter a path to locate the source data andweb-publish folders. By default, the location is Documents andSettings\All Users\Application Data\Compuware\VantageView.If the source folders reside on a remote machine, you can enter a valid UNCpath. You may first need to authenticate to that location via WindowsExplorer for the data utility to see this location as valid.

Source Virtual Directory nameBy default, the virtual directory name is Vantage. If this was changed,enter the name in this field.

b. On the Target tab, enter the following information for the target database:



AuthenticationYou can use either Windows Authentication or SQL Authentication to migratethe database. If SQL Authentication (default) is enabled, enter the proper UserID and Password for the database. Or select Windows Authentication.

Database InstanceThe database instance name.

Database NameThe database name.

LoginSpecify the login for accessing the VantageView database.

PasswordEnter the password for the SQL login.

OtherComplete the following field:

Existing local path on Target SQL Server machine where database backupfile is to be placed:

Specify the local path on the target SQL Server machine for the databasebackup file.

NOTEThe Source and Target Authentication methods are not required to be the same.

c. Click Next.

17. The Start Copying Files window appears and allows you to review the current settings.If the settings are correct, click Next to start copying files. To make changes, click Back.

18. Wait while the installation progresses. This could take several minutes. Do not interruptthe installation.

19. Click Finish to close the InstallShield Wizard. Depending on your OS updates, you maybe prompted to reboot your computer.

What to Do Next

Additional steps are required to complete the migration process. For more information, seeFinishing the VantageView Installation in the VantageView Installation Guide.

Verifying Migration SuccessPerform the following steps to confirm that migration to the new VantageView release wassuccessful.

1. Open Internet Explorer and navigate to the VantageView home page.2. Test the connections to the monitoring product databases.3. Test execution of saved or new reports, dashboards, and monitoring views.4. Make sure alerts are being received.



Post-Migration Notes• After migration, you must Test and Save all Synthetic Monitoring and Network Monitoring

database connections and all Server Monitoring Control Server connections. For moreinformation, see Configuration in the VantageView Installation Guide.

• After migration, you must retest the VantageView connection to the Network MonitoringEnterprise Manager.

• If you use Synthetic Monitoring, the Synthetic Monitoring Agent Manager must be Release11.7 or later.



C H A P T E R 6

Upgrading to Synthetic Monitoring Release 12.2

The following Synthetic Monitoring releases are eligible for upgrade to Release 12.2:

• Release 12.1

• Release 12.0

• Release 11.7

• Release 11.5

• Release 11.1

• Release 11.0

• Release 10.2 (must be on the latest service pack)

When upgrading to Synthetic Monitoring Release 12.2, it is important that the upgrade procedureis performed in the order that the steps are presented.

Release 12.2 Upgrade ChecklistUse the following checklist to keep track of your progress.

StepsFinished

Review the system requirements before starting the upgrade. For more information,see System Requirements in the Synthetic Monitoring Installation Guide.

NOTEIf you are upgrading from Release 10.2 and are using SQL Server 2000, you mustfirst upgrade to a supported version of SQL Server.

Review the upgrade recommendations. For more information, see UpgradeRecommendations [p. 74].

Upgrade to the 12.0.4 version of VantageView. For more information, see Upgradingto Synthetic Monitoring Release 12.2 [p. 77].


StepsFinished

If you are using Micro Focus QALoad, you must uninstall Micro Focus QALoadWorkbench before you upgrade Synthetic Monitoring.To uninstall Micro Focus QALoad, see the section Removing a Product in the MicroFocus QALoad Installation and Configuration Guide.

NOTEOne exception to this requirement is when you upgrade to Micro Focus QALoadRelease 5.9 immediately prior to upgrading Synthetic Monitoring. In this case, youdo not have to uninstall Micro Focus QALoad Release 5.9.Micro Focus QALoad Release 5.9 is included on the Compuware APM installationmedia.

Upgrade the Synthetic Monitoring Agent Manager to Release 12.2. For moreinformation, see Upgrading to Synthetic Monitoring Release 12.2 [p. 77].

Upgrade the Agents to Release 12.2. For more information, see Upgrading toSynthetic Monitoring Release 12.2 [p. 77].

Manually upgrade the Agents that were not upgraded automatically. For moreinformation, see Manually Upgrading an Agent to Release 12.2 [p. 81].

If you are upgrading Agent-initiated Agents with secure communication or with acustom port, re-register them with the Agent Manager after the upgrade is complete.For more information, see Updating Registration for Agent-Initiated Agents withSecure Communication After Upgrade [p. 84].

If you use the Synthetic Monitoring Scripting Framework, you must upgrade to thelatest release of the Framework. For more information, see Upgrading theFramework [p. 84].

Verify that the upgrade was successful. For more information, see Verifying theSuccess of the Upgrade/Migration [p. 82].

Upgrade RecommendationsIMPORTANTBefore upgrading, review the Synthetic Monitoring Release Notes for the latest productinformation. The release notes can be found on the Compuware APM Release 12.2 installationmedia in the Synthetic Monitoring folder or on FrontLine, Compuware's Customer Supportwebsite at http://go.compuware.com.

Compatibility with Previous Releases

• If you are upgrading to the 12.0.4 version of VantageView, you must upgrade the AgentManager and all Agents to Release 12.2 before publishing any configuration changes.


Chapter 6 ∙ Upgrading to Synthetic Monitoring Release 12.2


• The 12.2 Synthetic Monitoring Manager is backward compatible with a 12.1 Agent Managerand Agent. Consequently, if you are upgrading from VantageView 12.0.2 to VantageView12.0.4 (which installs a 12.2 Synthetic Monitoring Manager), you do not need to immediatelyupgrade the Agent Manager and Agents.

• The 12.2 Agent Manager is backward compatible with 12.1 Agents. However, 12.1 Agentsdo not support new features added in Release 12.2. Agents at Release 12.0 or earlier arenot supported.

Best Practices for Upgrading Compuware APM Products

When upgrading your Compuware APM products and migrating the data, Compuware requiresthat you migrate VantageView before migrating the other Compuware APM products (SyntheticMonitoring, Network Monitoring, and Server Monitoring).VantageView provides enhanced data migration with backward compatibility to aid with multipleproduct migrations. VantageView is compatible with other Compuware APM products onemajor release backward. This allows you to install and migrate VantageView first, and thenupgrade individual Compuware APM products later.

IMPORTANTAfter upgrading VantageView, test the connection to the Synthetic Monitoring database.

Upgrading TestPartner to Agent Recorder

Starting with Synthetic Monitoring Release 12.0, if a TestPartner release later than 6.0 is detectedon an Agent machine, the Synthetic Monitoring Agent installation program uninstalls TestPartner,and then installs the Agent Recorder, a rebranded version of TestPartner that is now the defaultscripting tool of Synthetic Monitoring.

IMPORTANTAfter upgrading a TestPartner 6.0 or 6.1 Release, you must run the Agent Recorder DBMaintenance utility to update the TestPartner database version. For more information, refer tothe Updating a Database Version topic in the Agent Recorder Help.

If you are upgrading an Agent machine on which a TestPartner 6.0 or earlier release is installed,contact Customer Support.

Permissions Required for Performing the Upgrade

To upgrade or migrate Synthetic Monitoring components, you must be logged on with localadministrator privileges. To migrate data from the database, you must log in as a databaseadministrator.

Uninstall Micro Focus QALoad Workbench Before Upgrading to Release 12.2

Uninstall the Micro Focus QALoad Workbench on machines where it is installed beforeupgrading to 12.2. If the Micro Focus QALoad Workbench is installed when the Agent isupgraded, the upgrade will fail.



VantageView Requirement After Migration

After completing the Synthetic Monitoring migration to Release 12.2, in VantageView, youmust re-save the Synthetic Monitoring database connection.

Upgrading the Synthetic Monitoring Scripting Framework

If you are using the Synthetic Monitoring Scripting Framework and have upgraded SyntheticMonitoring, you must upgrade to the latest release of the Framework. An upgraded Frameworkensures you have access to new functions and support for new features introduced in the currentversion of Synthetic Monitoring. For more information, see Upgrading the Framework [p. 84].

Upgrading SQL Server

SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 are supportedin Release 12.2.

NOTESQL Server 2000 is no longer supported and must be upgraded to a supported SQL Serverversion prior to upgrading Synthetic Monitoring.

If you choose to upgrade from an earlier version of SQL Server to a supported SQL Serverversion, you may upgrade before or after the Synthetic Monitoring upgrade.

Synthetic Monitoring Database Recovery Model Update

In Release 11.5 and later, during installation, Synthetic Monitoring uses the simple recoverymodel for the database. The simple recovery model automatically reclaims log space to keepspace requirements small, essentially eliminating the need to manage the transaction log space.This model does not provide any log backups, so for work loss consideration, it is important tounderstand that any changes made since the last backup are unprotected. You can only recoverto the end of the last backup.In Synthetic Monitoring releases prior to 11.5, the full recovery model was selected by default.If you are upgrading to Release 12.2, your recovery model setting is retained after you completethe upgrade to Release 12.2.If, in the prior release, the recovery model was manually changed to simple, the same settingis retained after the upgrade.

NOTEIf necessary, you can change the recovery model to full. The full recovery model produces atransaction log which, in some cases, uses a large portion of available disk space. If thetransaction log grows large enough to consume a large amount of disk space, you can usetransaction log truncation to free space in the logical log for reuse by the transaction log. Visitthe Microsoft MSDN website for more information about Transaction Log Truncation.

For additional information about SQL Server database recovery models, refer to the topicRecovery Models and Transaction Log Management on the Microsoft MSDN website.



If you are concerned about recovering data with the simple recovery model, you can also createa backup plan for the Synthetic Monitoring database in Microsoft SQL Server ManagementStudio. For more information, refer to the topic Backup Under the Simple Recovery Model onthe Microsoft MSDN website.

Upgrading to Synthetic Monitoring Release 12.2

Before You Begin

• Make sure to review the issues and considerations before starting the upgrade. For moreinformation, see Upgrade Recommendations [p. 74].

• Before upgrading, in SQL Server, make sure to allow the execute permission on the systemstored procedure sp_xml_preparedocument to allow processing of the .xml files. Thisstored procedure also requires membership in the public role. For more information, seehttp://msdn.microsoft.com/en-us/library/ms187367.aspx.

1. Migrate to the 12.0.4 version of VantageView.During the VantageView migration, a 12.2 version of the Synthetic Monitoring Managerand Synthetic Monitoring Console is installed.Once you have migrated VantageView, test the connection to the Synthetic Monitoringdatabase in VantageView, and then save the connection.Directions for migrating VantageView can be found in the Migrating VantageView chapterof the VantageView Installation Guide.

2. Before upgrading Synthetic Monitoring, make sure that you have additional disk space atthe current data location. If you retain the Network Packet Capture reports, you may requiresubstantially more disk space than is stated in the system requirements.

3. Upgrade the Synthetic Monitoring Agent Manager to Release 12.2.During this upgrade, the Agent Manager and the Synthetic Monitoring database are upgraded,unless you choose to skip the database migration temporarily.a. Uninstall Micro Focus QALoad Workbench from machines where it is used with

Synthetic Monitoring.If Micro Focus QALoad Workbench is not removed before upgrading, the message AQALoad Workbench product version mismatch has been found on this

machine. Remove this product before installing a Synthetic Monitoring

Agent appears and the upgrade terminates.If this message appears, uninstall Micro Focus QALoad Workbench from the machine,then restart the Synthetic Monitoring upgrade.

b. Backup the Synthetic Monitoring and Transaction Trace Analysis databases beforeupgrading to 12.2.

c. Insert the Compuware APM installation media into the drive. The Compuware menuappears. If the Compuware APM installation window does not display, double-clicksetup.exe in the root directory of the installation media.

d. Select the Synthetic Monitoring tab.



http://msdn.microsoft.com/en-us/library/ms187367.aspx

e. Select Synthetic Monitoring Agent Manager.If you do not have the required version of the operating system files, the CompuwareAPM Operating System Updates window appears, listing the operating systemupdates that will be installed. Click Next and restart the machine if requested.

f. Click Next at the Welcome to the Upgrade for Synthetic Monitoring screen.g. At the Migration/Update of Synthetic Monitoring Database screen, enter the

information for the Synthetic Monitoring database and click Next or click Skip if youwant to migrate the database later.You can select either Windows Authorization or SQL Authorization to upgrade thedatabase. If you specify Windows Authorization, include the domain name, ifnecessary. Enter the user name and password and click Next to continue.

h. At the Migration/Update of the Transaction Trace Analysis Database screen, enterthe information for the Transaction Trace Analysis database and click Next.

i. When the Ready to Upgrade the Program window, click Upgrade to continue theupgrade.

j. Once the upgrade is complete, click Finish.

4. After the Synthetic Monitoring database is migrated, in VantageView, save the databaseconnection.

5. If you skipped migrating the database during the Agent Manager migration, you mustmigrate your database (using the APM Database Utility), and then connect the database tothe Synthetic Monitoring Console to avoid losing Agent data.

6. Upgrade the Agents to Release 12.2.In most cases, you can automatically upgrade the Agents directly from the Agent Managerafter it has been upgraded, provided Micro Focus QALoad Workbench has already beenremoved from Agent machines where it is used with Synthetic Monitoring.

IMPORTANTIn order to automatically update an Agent, the option Enable automatic software updatesmust be enabled. This applies to those Agents that have been configured with the defaultAgent Manager-initiated communication. For more information, see Agent AutomaticSoftware Updates [p. 79].Additionally, when upgrading from all releases earlier than 11.7, you must first install anew Compuware certificate in the Windows Trusted Publishers certificate store. Thecertificate file Compuware.cer is located in the following folder on the Compuware APMinstallation media: Transaction Trace\Transaction Trace Analysis AgentInstaller\Compuware.cer.For more information about the Trusted Publishers certificate store, refer tohttp://msdn.microsoft.com/en-us/library/windows/hardware/ff553504%28v=VS.85%29.aspx.For more information about using the Windows command-line certificate installation tool,refer to http://msdn.microsoft.com/en-us/library/windows/hardware/ff543411(v=VS.85).aspx.

a. Open the Synthetic Monitoring Console and access the Agent Manager’s content pane.



http://msdn.microsoft.com/en-us/library/windows/hardware/ff553504%28v=VS.85%29.aspx

http://msdn.microsoft.com/en-us/library/windows/hardware/ff553504%28v=VS.85%29.aspx

http://msdn.microsoft.com/en-us/library/windows/hardware/ff543411(v=VS.85).aspx

b. Right-click the Agent Manager and click Apply Agent Software Update. The softwareis automatically updated on the Agent machines that have the option Enable automaticsoftware updates enabled.

TIPYou can configure the Active Agents content pane to display columns that describethe status of the software update. For more information, see Viewing the Status of anAutomatic Software Update [p. 80].

c. Click Publish Configuration to apply the upgrade to the Agents. The upgrade isapplied and, if necessary, the Agent machine is rebooted.

d. If necessary, manually upgrade Synthetic Monitoring Agents that were not automaticallyupgraded from the Agent Manager. For more information, see Manually Upgradingan Agent to Release 12.2 [p. 81].

7. After the upgrade has completed, re-install Micro Focus QALoad Workbench wherenecessary.

8. Verify that the components of Synthetic Monitoring have been upgraded successfully. Formore information, see Verifying the Success of the Upgrade/Migration [p. 82].

What to Do Next

• If you use the Import/Export transactions and Agents feature, change the version number(CVVersion) in each of the import files to 12.2 before you import again.

NOTEImporting from a pre-11.5 Release export file is not supported.

• If you use the Synthetic Monitoring Scripting Framework, additional steps may be requiredto complete the migration/upgrade process. For more information, see Upgrading theFramework [p. 84].

Agent Automatic Software UpdatesThere are two methods for upgrading an Agent to a major release or service pack:

Manually upgrade each AgentAfter upgrading the Agent Manager, manually install the latest release or service pack oneach Agent machine.

Enable and apply an automatic software updateDuring an upgrade of the Agent Manager, the requisite Agent upgrade files are installedon the Agent Manager. Consequently, you can deploy and install the upgrade from theSynthetic Monitoring Console by enabling the automatic software update feature on eachAgent, and then applying the update on all designated Agent machines.



Applying an Automatic Software Update1. On each Agent that you want to update automatically, select the Enable automatic software

updates option.

2. Install the new release or service pack on the Agent Manager, or if you have installed Parentand Child Agent Managers, install it first on the Parent Agent Manager, and then on eachChild Agent Manager.

3. After the new release or service pack has been installed on the Agent Manager right-clickthe Agent Manager and select Apply Agent Software Update.An informational message box appears stating that software updates will be applied thenext time you publish.

4. Apply the upgrade on the Agents by selecting File ➤ Publish Configuration.The Publish Report windows appears and displays the result of the upgrade. During theupgrade, the new release or service pack is deployed and installed on each Agent. Afterthe publishing job finishes, the Agent is restarted to complete the software update.

TIPTo view more specific details about the software update, you can configure the ActiveAgents content pane to display columns that describe the status of the software update. Formore information, see Viewing the Status of an Automatic Software Update [p. 80].

Viewing the Status of an Automatic Software UpdateDuring an automatic software upgrade and upon its completion, you can view the status of theupgrade in the Active Agents content pane, as described in the following steps.

1. In the Navigation pane of the Synthetic Monitoring Console, choose Agent Management ➤Active Agents.The Active Agents content pane appears.

2. Click the Field Chooser button ( ) located in the upper left of the Active Agent contentpane.

3. Select the following columns:• Update Request Time

• Update Status

• Update Status Time

During and after the automatic software update, the previously selected columns display specificinformation about the status of the update, such as the success or failure of the update, any errorsthat may have occurred, and the date and time the update started and completed.

NOTEFor 12.0 Agents, information appears in the Update Status and Update Status Time columnsonly after the update on the Agent has completed.



Manually Upgrading an Agent to Release 12.2

Before You Begin

To upgrade or migrate Synthetic Monitoring components, you must be logged on with localadministrator privileges.

Follow these directions to manually upgrade an existing Synthetic Monitoring Agent insteadof using the automatic upgrade feature.

1. First, if Micro Focus QALoad Workbench is installed on the Agent, remove it beforeperforming the upgrade. If you attempt to upgrade the Agent without removing Micro FocusQALoad first, the message A QALoad Workbench product version mismatch hasbeen found on this machine. Remove this product before installing a

Synthetic Monitoring Agent appears and the upgrade terminates. Remove Micro FocusQALoad then restart the upgrade program.

2. Insert the Compuware APM Windows installation media into the drive. The CompuwareAPM Setup menu automatically appears. If not, double-click setup.exe in the rootdirectory of the installation media.

3. Click Synthetic Monitoring Agent.The Compuware APM OS Update Setup begins. If operating system updates are required,the Compuware APM Operating System Updates screen displays a list of the operatingsystems updates that will be installed. Click Next and restart the machine if requested.The Welcome to the Upgrade for Synthetic Monitoring Agent screen appears.

4. Click Next.The Ready to Upgrade screen appears.

5. Review your upgrade selections and click Upgrade.The Installing Synthetic Monitoring Agent screen appears showing the installation status.

6. When the InstallShield Wizard Completed window appears, click Finish.7. If you are prompted to restart the computer, click Yes.8. Verify that the Agent upgraded successfully. For more information, see Verifying the

Success of the Upgrade/Migration [p. 82].

Upgrading a Remote Version of the SyntheticMonitoring Console

Before You Begin

To install Synthetic Monitoring components you must be logged on with local administratorprivileges.



IMPORTANTA remote version of the Synthetic Monitoring Console installed on a separate machine fromthe Synthetic Monitoring Manager must be at the same release as Synthetic Monitoring Manager.

To upgrade a remote version of the Synthetic Monitoring Console to the current release, performthe following steps:

1. Install the current release of VantageView.

NOTEThe VantageView installation also installs Synthetic Monitoring Manager. For moreinformation, refer to the VantageView Installation Guide.

2. Start the remote Synthetic Monitoring Console that you want to upgrade.The Connect to Synthetic Monitoring Manager appears.

3. Click Connect.An informational message box asks you to upgrade the version of the remote SyntheticMonitoring Console.

4. Click Yes.The dialog box closes and the remote version of the Synthetic Monitoring Console isupgraded.

5. Click Connect again.

Verifying the Success of the Upgrade/MigrationMake sure each of the following components has been successfully upgraded/migrated to thenew release.

Synthetic Monitoring Manager

On the machine where the Synthetic Monitoring Manager is installed, access Programs andFeatures and verify that Compuware Synthetic Monitoring Manager 12.2 and the build numberappears.You can also check the release and build number of the Synthetic Monitoring Console installedwith the Synthetic Monitoring Manager. Open the Synthetic Monitoring Console. Select Help ➤About, and then verify the release number is 12.2.

Remote Synthetic Monitoring Console

Open the Synthetic Monitoring Console. Select Help ➤ About, and then verify the releasenumber is 12.2.

Agent Managers

On the Agent Manager machine, access Programs and Features and verify that CompuwareSynthetic Monitoring 12.2 and the build number appears.



Additionally, you can double-click the Synthetic Monitoring Agent icon in the system tray toverify the correct release and build.

Synthetic Monitoring Database

On the machine where the Synthetic Monitoring database has been installed, verify that thedatabase is successfully migrated by running the following query in SQL Server ManagementStudio:Use <your Synthetic Monitoring DB name>

Go

Select DBVersion, DBPatch, DBActualPatch From Configuration

Go

NOTESpecify the name of your database in the Use statement. The default database names dependon the release from which you are upgrading:

DB Table NameRelease

SyntheticMonitoring12.1 and later

PrivateEnterprise11.7, 12.0

ClientVantage11.5 and earlier

Once the query has completed, verify the following values appear on the Results tab:

• DBVersion = 12.02

• DBPatch = 00

• DBActualPatch = 00

Agents

Verify that the Agent(s) is upgraded successfully by using one of the following methods:

• On the Agent machine, access Programs and Features and verify that CompuwareSynthetic Monitoring 12.2 and the build number appears.

• Double-click the Synthetic Monitoring Agent icon in the system tray and verify the correctrelease and build.

• You can also verify the Agent's release number in the Synthetic Monitoring Console. Waitapproximately ten minutes after the upgrade completes. In the Synthetic Monitoring Console,select Agent Management ➤ Agents. Make sure that the Agent's release number has beenupdated.



VantageView Database

On the machine where the VantageView database is installed, verify that the VantageViewdatabase has been successfully migrated by running the following SQL query in SQL ServerManagement Studio:Use VantageViewDB

Go

Select DBVersion, DBPatch From Configuration

Go

Once the query has completed, verify the following values appear on the Results tab:

• DBVersion = 12.00

• DBPatch = 14

Updating Registration for Agent-Initiated Agents withSecure Communication After Upgrade

An Agent-initiated Agent is an Agent configured to initiate communication with the AgentManager, instead of using the default Agent Manager-initiated communication.After manually upgrading an Agent-initiated Agent configured with secure communication,you must manually re-register the Agent with the Agent Manager by following these steps.

1. On the Agent machine, stop all Synthetic Monitoring services.2. Using a plain text editor such as Notepad, open the AgentRegister.xml file located in

installdrive:\Program Files\Compuware\Synthetic

Monitoring\Agent\Config\fxsrvaccws.The contents of this file are similar to the example shown below. The port you will changeis highlighted:<AgentRegister><EnableSecureCommunication><![CDATA[true]]></EnableSecureCommunication>

<Name><![CDATA[AA104]]</Name><Owner><MachineName><![CDATA[AM112]]></MachineName>

<Port>####</Port></Owner></AgentRegister>

3. Change the Agent Manager's port number to 9015 (the default secure communication portnumber). Save the changes and exit the file.9015 is the Agent Manager default secure port number. If you manually changed thisnumber, use that number instead. You can view the port number in the Agent Managerconfiguration in the Synthetic Monitoring Console.

4. Restart the Synthetic Monitoring services.

Upgrading the FrameworkIf you are using the Synthetic Monitoring Scripting Framework and have upgraded SyntheticMonitoring, an upgrade to the latest release of the Framework is recommended. An upgradedFramework ensures you have access to any new changes in the Framework and support for newfeatures introduced in the current version of Synthetic Monitoring.



NOTEIf you do not upgrade the Framework, the following status message appears when you run atest script: Current Framework version <12.x>. An update is available forRecorder version <12.x>. Review installation instructions. Defaulting to

a wait time of 30".

Framework Upgrade ChecklistThe Framework upgrade process includes the steps listed in the following table.

Table 7. Framework Upgrade Checklist

StepsCompleted

Make a backup of the Agent Recorder database on the Master Scripting Agent fromwhich you will deploy the updated database to all Agent machines.

Import the Framework upgrade files into the Agent Recorder database. For moreinformation, see Importing the Upgrade Files [p. 85].

Deploy the upgraded Agent Recorder database to all Agent machines. For moreinformation, see Deploying the Framework [p. 87].

Importing the Upgrade FilesThe following Framework upgrade files are copied to the Agent Manager machine during aSynthetic Monitoring installation or when applying a Synthetic Monitoring Service Pack:

FrameworkUpdates.XMLThis is an exported Agent Recorder file that contains the internal Framework scripts,modules, screen events, image maps, and object maps that are necessary for the upgrade.

UserModifiableFunctions.XMLThis is an exported Agent Recorder file that contains a current version of Agent RecorderCVFW_User_Modifiable_Functions module. This module provides template functionsthat you can modify to support your environment. If you have previously edited thismodule, you must copy your changes out of the module prior to import, and then manuallymerge them back in after importing UserModifiableFunctions.XML. If you did notedit this module, you should still perform an import of this file to ensure you have thecorrect version available.

NOTEAs an alternative to importing UserModifiableFunctions.XML, a text file version(UserModifiableFunctions.txt) is available. To use this version, copy the contentsof the file and manually merge them with your custom changes in the existingCVFW_User_Modifiable_Functions module.



IMPORTANTThe Framework upgrade files do not contain required Agent Recorder settings which aremaintained in the Framework Agent Recorder database. Consequently, these files should onlybe used to upgrade an existing Framework Agent Recorder database. Do not use these files toinstall the Framework in a new Framework installation scenario.

Import Framework Updates

Perform the following steps to import all Framework updates with the exception of theCVFW_User_Modifiable_Functions module updates, which are imported in a separateprocedure.

1. Copy the Framework upgrade files from the following location in the Agent Managerinstallation folder to any location on the Master Scripting Agent machine:C:\Program Files\Compuware\Synthetic

Monitoring\Samples\ScriptingFramework\

2. On the Master Scripting Agent, start Agent Recorder.

3. Choose File ➤ Import Assets.The Agent Recorder Asset Import Wizard appears.

4. Click Next.The Import File name or Directory page appears.

5. Select Import assets from a single file, browse to FrameworkUpdates.XML, and thenclick Next.The Items to Import page appears.

6. Select Import all assets, and then click OK.The Conflict Resolution page appears.

7. Accept the default resolution, and then click Next.The Start Importing Assets page appears.

8. Click Next and Finish to start the import process.

Import CVFW_User_Modifiable_Functions Module Updates

If you did not previously modify the CVFW_User_Modifiable_Functions module, use theAgent Recorder Import wizard to import the current version of the file. If you made changes tothe CVFW_User_Modifiable_Functions module that you do not want to overwrite, performthe following steps:

9. Copy your changes out of the CVFW_User_Modifiable_Functions module.10. Use the Agent Recorder Import wizard described in the previous steps to import

UserModifiableFunctions.XML.11. Paste your changes back into the newly imported CVFW_User_Modifiable_Functions

module.



TIPYou can create a shared module to store your own functions, and then reference them inthe CVFW_User_Modifiable_Functions module. Additionally, you can log what functionsyou changed at the top of the module to quickly identify what you need to modify.

Verify That the Agent Recorder Framework Is Configured

12. Start the Agent Recorder and open the Test scripts window of the Asset Browser. In theDescription field for each Framework test script, you should see the current version of theFramework listed.

What to Do Next

Deploy the updated Agent Recorder database to the remaining Agents in your environment.For more information, see Deploying the Framework [p. 87].

Deploying the Framework

Before You Begin

• In the Synthetic Monitoring Console, add all Agents on which to deploy the database.

• Configure the Agent Recorder database and Framework configuration file on the MasterScripting Agent before deploying these assets to all other Agents.

• On all Agent machines, close Agent Recorder.

The recommended deployment process for distributing the Framework Agent Recorder databaseon the Master Scripting Agent to all other Agent machines requires the use of the SyntheticMonitoring script publishing utility. This utility allows you to selectively choose which Agentsto update.

NOTEAlthough it is not recommended, this version of the Framework continues to support the use ofa shared folder to distribute Framework assets, as directed in previous versions of the Framework.

Deploy the Agent Recorder Database

1. On the Master Scripting Agent, start the Synthetic Monitoring Console.2. Select Scripts from the Navigation pane, then select Script Publishing.3. Right-click in the Script Publishing grid, and then select Add.

The Publish Scripts dialog box appears.



Figure 4. Publish Scripts Dialog Box - Agent Recorder

4. In the Publish Scripts dialog box, type the name of the definition in the Name field.5. From the Scripting tool/Data list, select Agent Recorder.6. From the Data source list, select TestPartner.7. In the Master database box, click Browse, and then select the TestPartner.mdb file in

the following location:C:\ProgramData\Documents\Compuware\Recorder\DB\TestPartner.mdb

NOTEFor some operating systems, the Documents folder is hidden. In this instance, click Browse,and then type C:\ProgramData\Documents\Compuware\Recorder\DB\ in the Addressbar of the Open dialog box. Next, select TestPartner.mdb, and then click Open.

8. From the Schedule time list, select the timing of when you want to publish.9. Select the Agents on which to deploy the database.10. Optionally, select the Publish configuration now check box to immediately publish to all

selected Agents.11. Click Schedule.

The database file is compressed and, if you enabled Publish configuration now, thecompressed file is published immediately to the Agent(s), along with any other pendingconfiguration changes. The status of the publish appears in the Publish Report. window,as shown below.



Figure 5. Publish Report

After running the publish scripts utility, the Status column displays Successful to indicatethe database was deployed as intended.

12. Close the Publish Report window.

Deploy the Agent Recorder Configuration File

13. Right-click in the Script Publishing grid, and then select Add.The Publish Scripts dialog box appears.

Figure 6. Publish Scripts Dialog Box - UserData

14. In the Name field, type the name of the definition.15. From the Scripting tool/Data list, select UserData.



16. In the User data file box, click Browse, and then select the CVFW.zip file in the followinglocation:C:\ProgramData\Compuware\ClientVantage\Data\work\Data\UserData

NOTEOn Windows XP machines: C:\Documents and Settings\All Users\ApplicationData\Compuware\ClientVantage\Data\work\Data\UserData

17. From the Schedule time list, select the timing of when you want to publish.18. Select the Agents on which to deploy the configuration file.19. Optionally, select the Publish configuration now check box to immediately publish to all

selected Agents.20. Click Schedule.

If you enabled Publish configuration now, the configuration file is published immediatelyto the Agent(s), along with any other pending configuration changes.

Verify the Deployment of the Database and Configuration File

21. On any Agent machine on which you deployed the database and configuration file, startAgent Recorder and open the Test scripts window of the Asset Browser.A list of default Framework test scripts that start with the prefix CVFW_ and ZZ_ shouldappear. In the Description field of the ZZ_Release_History test script, you should seethe current version of the Framework listed.

22. To verify that the configuration file was deployed successfully, run the CVFW_Maintenancescript and verify that your settings appear on the various tabs of the Configuration window.Alternatively, on an Agent machine, you can open the folderC:\ProgramData\Compuware\ClientVantage\Data\work\Data\UserData, and verifythe modified date of the CVFW.ini file matches the time the file was published.



C H A P T E R 7

Migrating Server Monitoring

You can upgrade Server Monitoring to Release 12.0 from Release 10.2 and up, after applyingthe latest service pack.In this document, upgrade is the process of installing a new release after a previous release hasbeen installed. Migration is the process of transferring the data from the previous release to thenew release.Upgrading to the new release usually includes migration. The time required for migrationdepends on the size and content of the database. The migration process can be time consuming.

Migration Guidelines

Compatibility with Earlier Releases

Although you can migrate to Release 12.0 from earlier releases back to 10.2, components thatare not yet migrated may not be compatible with the new release.The Server Monitoring Control Server supports existing agents for two releases back from thenew release.VantageView is compatible with Server Monitoring for two releases back from the new release.This enables you to migrate VantageView first, and then migrate Server Monitoring later. Formore information, refer to Compatible Compuware APM Product Releases in the VantageViewInstallation Guide.You can continue to run earlier releases of VantageView in support of earlier releases ofCompuware APM products until you migrate them to the latest release.

CAUTIONAfter migrating VantageView and Server Monitoring, do not try to modify a Server Monitoringtask using an earlier release of VantageView.

Compuware Open Server

The default Compuware Open Server (COS) port is 18080. If your current release used a differentport for COS, that COS port configuration setting is retained.


UNIX .tar Files

In Release 12.0, UNIX .tar files are not automatically loaded onto the Control Server for useby the Agent Upgrade feature. You must manually copy the agent .tar files from the appropriateDVD to the Control Server.

Table 8. File Locations

File LocationPlatform

DVD 2, SV_Unix_Agents folderLinux

DVD 3, SV_Unix_Agents folderAIX, HPUX, and Solaris

Copy the appropriate .tar file for your agent to the Update folder in the Server Monitoring(or ServerVantage, for Release 11.5 and earlier) installation directory.After the files are copied into the Update directory, the upgrade appears as available on theVantageView Administration ➤ Server ➤ Control Server ➤ control-server ➤ AgentUpgrades page. For more information, refer to the online help for the Agent Upgrade page.

Migration ChecklistReview the following checklist before migrating Server Monitoring. When you perform themigration, use the checklist to make sure you have completed all requirements and tasks.

Table 9. Migration Checklist

StepsFinished

Review the system requirements to verify that you have all of the appropriate hardwareand software configurations to migrate successfully.

Review the licensing information for any changes that may have been implemented forlicensing.

Before beginning the migration, verify that your tasks are running correctly. If any tasksare running with an exception or error, determine why. This information aids in yourpost-migration verification. For more information, see Migration Checklist [p. 92].

Perform procedures as needed for the migration requirements. For more information, seeMigration Requirements [p. 93].

Perform the migration. For more information, see Performing the Server MonitoringMigration [p. 94].

If you plan to keep your existing database data, migrate the database. For more information,see Migrating Server Monitoring Databases with the Database Utility [p. 95].

Migrate your agent stations.

Upgrade the SNMP Collector.

Verify that migration was successful. For more information, see Migration VerificationChecklist [p. 96].


Chapter 7 ∙ Migrating Server Monitoring

Migration RequirementsCheck the Server Monitoring Release Notes for the most recent information. The most up-to-dateversion of the Release Notes is available on FrontLine at http://go.compuware.com.The migration procedure is the same for any supported release.Before beginning migration:

• Verify that the target workstations meet the hardware and software requirements for thenew release.

• Verify the backward compatibility of your agents. Agents are supported for two releasesback. For more information, see Determining the Server Monitoring Agent Release [p. 93].

Before migrating the database, consider the following:

• If you are performing a migration or you want to save the historical data, you must migratethe database.

• If you have existing templates that use the same name as templates that are installed withthe new release, the existing templates are renamed by appending _1, _2, etc. If the templatename exceeds the maximum length allowed, the last characters of the template name arechanged.

• If you deleted a Compuware-supplied template and renamed custom templates with thesame name, these templates are replaced with the new Compuware-supplied templates.

• Make sure you have double the amount of the database size available on your hard diskbefore you begin the migration process. If you do not have the required space, the migrationwill fail.

• If you plan to use VantageView to view databases prior to Release 12.0, refer to theVantageView Installation Guide for database requirements.

CAUTIONBefore you migrate the database, back up the database using Microsoft SQL Server backup.

To set up a remote database for your Control Server, refer to the online help for the DatabaseUtility.

Determining the Server Monitoring Agent Release

VantageView Agent Report Page

You can use the Agent Report page in VantageView to determine an agent's release.

1. In VantageView, click Administration to open the Administration page.

2. In the Administration tree, expand Server ➤ Control Servers ➤ control_server.

3. Click Agent Status to display the Agent Report page for the selected Control Server.




The Agent Build Number column provides the release number and build number for eachagent. For example, 12.00.00.806 indicates that the agent is Release 12.0 with no servicepack applied, build 806.You can also use the procedures described below to determine the release for an agent.

Windows Agent

Use the Reconfigure Agent console to determine the release of your Windows agent:

1. Open Reconfigure Agent by choosing Start ➤ All Programs ➤ Compuware ➤ ServerMonitoring ➤ Reconfigure Agent.

2. Select Help ➤ About to display the release and build number of the Server MonitoringWindows agent.

UNIX Agent

Navigate to the /etc folder of the install directory ($SVHOME) to determine the release of yourUNIX agent:

1. Change to the $SVHOME /etc subfolder of the UNIX agent and look for the release.dfile, which contains the release of the Server Monitoring UNIX Agent. .

2. Open this file in a text editor to review its contents.

Performing the Server Monitoring Migration1. Log on to the server with local administrator permissions.2. Select the installation disc that matches your target machine's operating system:

• DVD1 Windows

• DVD2 Linux

• DVD3 AIX HPUX


4. Select the Additional Products tab.5. Under Server Monitoring, select the component you want to migrate

Links are included for the Control Server and Agent (including 64 Bit and Itanium 64Bit).

NOTEFor information on VantageView migration, refer to the chapter Migrating VantageViewin the VantageView Installation Guide.



The installation wizard opens. Follow the prompts to complete the migration.

What to Do Next

Continue as needed with the migration tasks described below. After you complete all migrationtasks, validate that migration was successful. For more information, see Migration VerificationChecklist [p. 96].

Migrating Server Monitoring Databases with theDatabase Utility

If your database migration fails, after you have corrected the issue (for example, you may needto provide more disk space), use the Database Utility to migrate your database. You can accessthe utility from the Compuware APM installation media, or from the Windows Start menu.For more information, refer to the Database Utility online help.

CAUTIONMigrating the database may take several hours, depending on the size of the database and thesystem performance. Typically, migrating a 0.5 GB database on a 3-GHz workstation requiresapproximately 30 minutes to complete.

The maintenance job logs are automatically created and stored in the database. Run theExtractMaintenanceLogs.bat utility to extract and delete these logs from the specifieddatabase.The Server Monitoring database requires Microsoft SQL Server 2005 or 2008, with mixed-modeauthentication enabled.

Database Migration RecoveryIMPORTANTThe Database Migration Recovery feature is available only when migrating from the latestservice pack of Release 11.7. Check FrontLine for the latest service pack and apply that servicepack before migrating your database. If you experience a migration problem when migratingfrom an earlier release, you must correct the problem, restore the original backup, and thenrestart the full migration for your backup database.

The Database Migration Recovery feature enables you to restart the migration process from thepoint of failure without having to restore the original database from backup. This feature canrecognize and recover from the following types of failures:

• Exceeding available disk space (Server Monitoring database, temporary database, masterdatabase, etc.).

• Exceeding time limits for a full migration.

• SQL Server/Windows failure (such as power failure).



With these failures, the migration stops while you troubleshoot and fix the problem. Then youcan resume the migration from the point of failure.The Database Migration Recovery recovers from the listed types of migration failures. It doesnot assist in recovery from other types of migration failures or from exceeding time limits fora single SQL Server batch job. In these cases, contact APM Customer Support for assistancein resolving the problem. To continue monitoring while the problem is resolved, restore theoriginal release of Server Monitoring and its database. After the problem is resolved, you canstart migration with your current unmigrated version of the database. This ensures the completemigration of new data points, events, and current tasks.

Upgrading SNMP CollectorThe SNMP Collector is upgraded by installing the new release.Upgrade VantageView and Server Monitoring first, and then upgrade the SNMP Collector.Both Server Monitoring and VantageView must be upgraded for Release 12.0 of SNMP Collectorto function properly.VantageView Release 12.0 supports the SNMP Collector from two releases back, allowing youto gradually upgrade them.

Migration Verification ChecklistUse this checklist to verify the success of your Server Monitoring migration.

Table 10. Migration Verification Checklist

StepsFinished

Parse the migration log to verify that no errors occurred during the migration.

Re-save the Control Server connection in VantageView.

Verify that the upload setting has remained the same, if it was changed from the defaultbefore migration.

Verify that the watchdog setting has the same value.

Verify that the email settings have remained the same.

Verify that the failover email address has remained the same.

Verify that the notification port has remained the same.

Verify that the TCP/IP ports have remained the same.

Verify that the configured database maintenance has remained the same.

Create a new task and validate that it functions properly, including notifications.

Create a server metric report to verify that it works.

Create a DMI report to verify that it works.



Table 10. Migration Verification Checklist (continued)

StepsFinished

Verify that tasks created before migration are still running without issues and are generatingnotifications.

Deploying Patches to AgentsServer Monitoring enables efficient deployment of patches to agents. The Server MonitoringControl Server can push patches to agents.

Before You Begin

Make sure the owner of Server Monitoring processes has permission to execute the -showrev-p- command.In Release 12.0, UNIX .tar files are not automatically loaded onto the Control Server for useby the Agent Upgrade feature. You must manually copy the agent .tar files from the appropriateDVD to the Control Server. For more information, see UNIX .tar Files [p. 92].Make sure sufficient disk space is available for temporary files that are created during thedeployment. For more information, see Estimating UNIX Agent Update Disk Space [p. 97].

A patch may consist of:

• One or more executable, library, or configuration files. These generally replace the versionalready in the agent. They may also be new files.

• A Patch Description File. This file tells the Control Server and agent about the patch.

Server Monitoring agent patches are deployed through VantageView.

1. From the VantageView menu bar, choose Administration and navigate to Server ➤Control Servers.

2. Select and expand the appropriate Control Server.3. Click Agent Upgrades to display the Agent Upgrades page.

This page enables both upgrades and deployment of patches.

4. Select the appropriate upgrade or patch from the menu.A description of the selected item appears below the patch, along with a list of agentseligible to receive the selected upgrade or patch. Changing the selection changes the list ofagents to match the new selection.

5. To schedule an agent for the selected upgrade or patch, select the agent's check box.6. When all desired agents are selected, click Upgrade.

Estimating UNIX Agent Update Disk SpaceDuring an update or patch deployment, the script for the Server Monitoring UNIX agent createsa backup of the current agent in /tmp by default, and then performs the update.



If the update fails, the script uses the backup to roll the agent back. If the update is successful,it deletes the backup from /tmp.The following tables list the sizes for all supported UNIX agents in Server Monitoring. The sizelisted in the Agent Size (KB) column is the size of the agent's installation image in kilobytes.The /tmp Estimate (KB) column doubles the initial size to take into account logs, additionalagent features installed, and other data generated when the agent runs for a length of time. The/tmp partition should have at least this estimated space free before the auto-upgrade process isstarted. The /tmp Estimate (MB) column lists the /tmp Estimate (KB) size converted tomegabytes.

NOTEThe /tmp free space is an estimate. It may not be enough space if the agent has been runningin debug mode (saving logs) for an extended period of time. A good rule of thumb is to makesure there is 500 MB of free space available on /tmp. This disk space will be enough for all butthe largest agents; for example, the hpux64 agent requires approximately 1 GB.

Table 11. 32-Bit Agent Updates and Patches

/tmp Estimate (MB)/tmp Estimate (KB)Agent Size (KB)Agent TypeFree SpaceFree SpaceInitial Image

300305584152792aix_agt

460470394235197hpux_agt

11011145455727linux_ia32 (Itanium)

10510659253296solaris-x86

145227198113599solaris_agt

Table 12. 64-Bit Agent Updates and Patches

/tmp Estimate (MB)/tmp Estimate (KB)Agent Size (KB)Agent TypeFree SpaceFree SpaceInitial Image

306312378156189aix64_agt

478488766244383hpia64 (Itanium)

10351058966529483hpux64

10911141455707linux_ia64 (Itanium)

464709223546linux_ppc64 (PowerPC)

686941234746linux_s390x

818248641243linux-x86_64

524536450268225solaris64

314320684160342solaris-x86_64



Migrating a UNIX Agent from 32-Bit to 64-BitPerform this procedure only if you are currently running a 32-bit agent on a 64-bit Linux, AIX,or Solaris machine, and you want to take advantage of the 64-bit features.

1. Copy the 64-bit agent files install, sizes.d, and the appropriate 64-bit agent TAR.Z filefrom the SV_Unix_Agents folder on the installation media to a work area on your machine.

2. Install these files over the existing 32-bit agent.

After you migrate an agent that is monitoring Oracle, DB2, or WebLogic from 32-bit to 64-bit,you must reconfigure the agent.



Index

AActive Agent

77, 82manual upgrade 77upgrade 77verify the upgrade 82

ADS33, 39

upgrade validation 39upgrading 33

agent93, 97, 99

backward compatibility 93deploying patches 97migration 93release number 93UNIX

99migrating from 32-bit to 64-bit 99

Agent73, 79–81, 84

Agent-initiated Agent 84apply software updates on the Agent 80manual upgrade 81re-register Agent-initiated Agent 84software updates 79–80upgrade 73, 81upgrade, manual

84Release 12.0 to 12.2 84Release 12.1 to 12.2 84

Agent Manager73, 77, 80, 82

enable80

software updates 80update software 80upgrade 73, 77verify the upgrade 82

AMD40, 42

AMD (continued)software

40upgrading 40

upgrade validation 42upgrading 40

APM Community13

Migration Center 13Apply software updates 80audience 8Automatic software updates 79–80

Bbackup

61, 91Server Monitoring 91VantageView 61

Best practices74

upgrading Compuware APM products 74

CCAS

26, 32upgrade validation 32upgrading 26

checklist13

migration of products 13Checklist

73upgrade 73

checklists63, 92, 96

migration 63, 92verifying migration 96

Compuware Open Server migration 91


Index

configuration71

after migration 71contact information 10contents of this guide 8conventions 11CSS

7, 33migrating Business Service Management and Data CenterReal User Monitoring existing users 7upgrade validation 33

CSSupgrade 22Custom ports

84Agent-initiated Agent 84

Customer Support 10customized files

57migrating to new release 57

DData Center Real User Monitoring

9documentation 9

Data Center Real User Monitoring upgrade workflow 21database

55, 61–62, 71, 91, 93, 95configuring connections after migration 71migration

55, 61, 91, 93, 95Server Monitoring 91VantageView 61

migration prerequisites 62migration recovery 95

Database74, 82

database recovery model 74Synthetic Monitoring

82verify migration 82

upgrade SQL Server 74VantageView

82verify migration 82

DC RUM21

upgrade paths from older releases 21definition

7migrate/migration 7upgrade 7

Deploying87

Framework 87deploying BSM web application 48directions

61, 91migration

61, 91Server Monitoring 91

directions (continued)migration (continued)

VantageView 61documentation

7, 9introduction 7

EEnable

80software updates

80automatic software updates 80

Enterprise Portal47

upgrading 47upgrading to latest release 47

Event Console migration 58Executing migration checklist 18

FFramework

84–85, 87deploying 87upgrade 84upgrade checklist 85upgrade files 85

Hhardware and software requirements 15Help

9product documentation 9

Iinstallation

9documentation 9

Installation81

component81

Synthetic Monitoring Console 81intended audience 8

Llicensing

9documentation 9

MMicro Focus QALoad

77, 81


Index

Micro Focus QALoad (continued)uninstall Workbench 77, 81

Migratiion verification58

BSM 58migrating

23, 26, 33, 40ADS 33AMD 40CAS 26RUM Console 23

migrating VantageView61–63, 65, 70–71

checklist 63database connections 71overview 61prerequisites 62procedure 65report data 65verifying migration success 70

migration9, 51, 53, 55–58, 61, 91–96

Business Service Management9

documentation 9checklist 92configuration 56Data Center Real User Monitoring

9documentation 9

database 55database recovery 95Database Utility 95documentation

9Business Service Management 9Server Monitoring 9Synthetic Monitoring 9VantageView 9

Event Console 58existing users to Compuware Security Server 51files from previous release 57guidelines 91installing Service Model components 53overview 51, 91prerequisites 53procedure 94recovery

61, 91Server Monitoring 91VantageView 61

requirements 93server 56Server Monitoring

9, 91directions 91documentation 9

SNMP Collector 96SQL Server 2000

91Server Monitoring 91

migration (continued)Synthetic Monitoring

9documentation 9

to Enterprise Portal 51VantageView

9, 61documentation 9

verification checklist 96Migration

13–14determine currently installed product 14overview 13

Migration checklist 52Migration paths

15planning 15

Monitoring74

passive monitoring 74

Oonline support site 10Operating system update 81organization of this guide 8

PPassive monitoring 74patches

97deploying to agents 97UNIX agent temporary disk space 97

Permissions74

upgrade 74Product acronyms 7product backward compatibility 16product migration checklist 13product suite compatible releases 62Publish

80automatic software updates 80

Rrecover

61, 91migration

91Server Monitoring 91

VantageView 61Register

84update Agent registration 84

RUM Console25

Java Web Start 25


Index

SServer Monitoring

9, 91database

91migration 91

documentation 9migration

91database recovery 91

Service Model58

importing after migration 58Service Model Server

56migration 56

Service packs80

automatic updates 80Settings

80Enable automatic software updates

80overview 80

SNMP Collector96

upgrade 96software dependencies 43Software updates

80Automatic Software Updates 80

SQL Server73–74, 95

200073–74

upgrade 732005 742008 74migration recovery 95requirements 74upgrade 74

Supported73

releases for upgrade73

12.0 7312.1 73

Synthetic Monitoring Console81–82

installation 81verify the upgrade 82

Synthetic Monitoring Manager82

verify the upgrade 82

Uuninstall

61VantageView 61

UNIX agent97, 99

migrating from 32-bit to 64-bit 99temporary disk space for update or patch deployment 97

Update80

Automatic software updates 80upgrade

21, 84, 91ADS 21AMD 21CAS 21CSS 21Data Center Real User Monitoring 21Framework 84RUM Console 21Server Monitoring agents 91

Upgrade73–74, 77, 80–82

Agent 81applying service packs 80best practices 74checklist 73database 74Microsoft SQL Server 2000 73permissions 74recommendations 74Release 12.0 to 12.2 73, 77Release 12.1 to 12.2 73, 77, 82SQL Server 74verify the upgrade 82

Upgrade checklist85

Framework 85Upgrade files

85Framework 85

Upgrade goals14

identify 14upgrading

21–23, 26, 33–34, 40ADS 33–34AMD

40software 40

CAS 26CSS 22DC RUM

21upgrade paths 21

RUM Console 23standalone RUM Console 23

Upgrading47

Enterprise Portal 47upgrading a release

51overview 51


Index

VVantageView

9, 61, 77, 82database

61migration 61

documentation 9

VantageView (continued)migration

61database recovery 61directions 61

uninstall 61upgrade 77, 82


Index


Index

Compuware APM Product Upgrade and Migration ... - … this document, upgrade is the ... product...

Documents

Transcript of Compuware APM Product Upgrade and Migration ... - … this document, upgrade is the ... product...