VantageView. Installation Guide. Release 12.0

Transcription

1 VantageView Installation Guide Release 12.0

2 Please direct questions about VantageView or comments on this document to: APM Customer Support FrontLine Support Login Page: Copyright 2014 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Disclosure is prohibited without the prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of the user's License Agreement with Compuware Corporation. Documentation may only be reproduced by Licensee for internal use. The content of this document may not be altered, modified or changed without the express written consent of Compuware Corporation. Compuware Corporation may change the content specified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found at Compuware, Vantage, Gomez, Synthetic Monitoring, Network Monitoring, Server Monitoring, VantageView, and FrontLine are trademarks or registered trademarks of Compuware Corporation. 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 2, 2014, 8:22

3 Contents Contents Introduction Who Should Read This Guide Organization of this Guide Related Publications Customer Support Information Information to Provide to Customer Support Documentation Conventions Chapter 1 System Requirements Server Requirements Database Requirements Client Requirements VantageView Co-Location Deployment Guidelines VMware and Virtualization Chapter 2 Installation Prerequisites Installation Restrictions Pre-installation Checklist Server Prerequisites Configuring Permissions for IIS 7.5 or Later Providing Metabase Permissions to the IIS_IUSRS Account Giving File Permissions to IIS_IUSRS on the Mailroot Directory Microsoft Windows Server 2003 Configuration Install IIS in Windows Server Disable Internet Explorer Enhanced Security in Windows Server Install/Allow Web Server Extensions in Windows Server Verify WebDAV Extension Installation in Windows Server Configure Windows Authentication in Windows Server Install SMTP in Windows Server Install SNMP in Windows Server Microsoft Windows Server 2008 Configuration Install IIS in Windows Server Disable Internet Explorer Enhanced Security in Windows Server

4 Contents Install/Allow Web Server Extensions in Windows Server Verify WebDAV Extension Installation in Windows Server Configure Windows Authentication in Windows Server Install SMTP in Windows Server Install SNMP in Windows Server Database Prerequisites Product Suite Prerequisites Chapter 3 Installing VantageView Installation Overview Installation Overview Installation Checklist Installation Procedure Installing VantageView on a 64-bit Operating System Chapter 4 Migrating VantageView Migration Overview Migration Prerequisites Compatible Compuware APM Product Releases Migration Checklist VantageView Data Migration Migrating VantageView to the New Release Verifying Migration Success Post-Migration Notes Chapter 5 Finishing the VantageView Installation Register TeeChart7.ocx on the Client Configuring the VantageView Server Verify Data Location File Permissions for Users Register TeeChart7.ocx on the Server Verify Access for Windows Everyone Group Exclude Files from Anti-Virus Scanning Exclude Files from Anti-Virus Scanning on Compuware APM Products Database Servers Verifying the Success of the VantageView Installation Access VantageView Configure Security Groups in VantageView Configure Database Connections Test Manual Report Publishing Installing the MySQL JDBC driver Implementing Domain-based Database Security in VantageView Chapter 6 Configuration Synthetic Monitoring Configuring a New Synthetic Monitoring Database Connection Modifying an Existing Synthetic Monitoring Database Connection How the Rollup Database Works with Synthetic Monitoring Network Monitoring

5 Contents Network Monitoring Daily Databases Configuring a New Network Monitoring Daily Database Connection Modifying a Network Monitoring Daily Database Connection How the Rollup Database Works with Network Monitoring Network Monitoring Long Term Databases Configuring a Network Monitoring Long Term Database Connection Modifying a Network Monitoring Long Term Database Connection Server Monitoring Server Monitoring Control Servers Configuring a New Control Server Modifying an Existing Control Server Server Monitoring Historical Databases Configuring a New Historical Database Modifying an Existing Historical Database Central Analysis Server Accessing the CAS Report Data Servers Page Adding Report Data Servers Modifying Report Data Servers Deleting Report Data Servers Data Rollup Settings Selecting a Time Zone for Data Rollup Selecting Working Hours for Data Rollup Selecting a Summary Level for Data Rollup Chapter 7 Maintenance Backing Up and Restoring VantageView Moving or Copying VantageView Data to a New Web Server Pointing VantageView to a Different SQL Server Pointing VantageView to a Different Virtual Directory Verifying Compuware Open Server Connection Settings Moving the SQL Server Database Between Platforms Installing Service Packs Uninstalling VantageView Index

6 Contents 6

7 INTRODUCTION Who Should Read This Guide This guide is written for the system administrator, application manager, or any other individual who installs and administers VantageView software. Organization of this Guide The is intended for system administrators or other users who are installing VantageView to work with Compuware APM products. It provides a basic VantageView application and component overview and explains how to install and configure VantageView to use it with the other Compuware APM products. It assumes you are familiar with Windows terminology. This guide contains the following chapters: System Requirements [p. 11] Installing VantageView [p. 35] Finishing the VantageView Installation [p. 55] Migrating VantageView [p. 43] Maintenance [p. 85] Configuration [p. 69] Related Publications The following publications provide information about configuring and using VantageView and related Compuware APM products: VantageView Release Notes Crucial product information and information that was not available at the documentation release date. The most recent version is available on FrontLine, Compuware's Customer Support website, at 7

8 Introduction VantageView Online Help Descriptions of VantageView features and procedures for configuring, maintaining, and using VantageView. The online help is installed with the product and can be accessed by selecting Help from the menu bar. Compuware APM Upgrade and Migration Guide Contains information on migrating VantageView and upgrading/migrating related products to the latest release. VantageView Data Utility Online Help Information for using the Data Utility. PDF files are viewable with Adobe Reader, version 6.0 or later. If you do not have the reader application installed, you can download and install from the Adobe website at Customer Support Information FrontLine Support Website You can access information for Compuware products via our FrontLine support site. You can review frequently asked questions, read or download documentation, access product fixes, or your questions or comments. The first time you access FrontLine, you are required to register and obtain a password. Registration is free. To access FrontLine, log in to Select your product from the Product Support dropdown list. Contacting Customer Support Phone USA and Canada: or All other countries: Contact your local Compuware office. Contact information is available at Web You can report issues via the Report and Track Calls tab on the FrontLine home page. Please report all high-priority issues by phone. [email protected] Mail Customer Support Compuware Corporation One Campus Martius Detroit, MI APM Community You can find product documentation, forums with product experts, product fixes and more information at the Compuware APM Community. You must register and login to access the Community. 8

9 Introduction Corporate Website To access the Compuware website, go to The Compuware site provides a variety of product and support information. Information to Provide to Customer Support Provide Customer Support with as much information as possible about your environment and the circumstances that led to the difficulty. Please be ready to provide: Your client number. This number is assigned to you by Compuware and is recorded on your sales contract. The name, release (version), and build number of the product and its components. This information is displayed when you select the About command from your product's Help menu. The name and release are also on the covers of the product documentation. Environment information, such as the operating system and release (including service pack level) on which the product is installed, memory, hardware/network specifications, and the names and releases of other applications that were running. Problem description, including screen shots. Exact error messages, if any (screen shots recommended). Whether the problem is reproducible. If yes, sequence of steps to reproduce the problem. If not, a description of the actions taken before the problem occurred. A description of the actions that may have been taken to recover from the difficulty, and their results. Log file(s) from the component(s) affected by the problem. Compuware values your comments and suggestions about our products and documentation. Your feedback is very important to us. If you have questions or suggestions for improvement, let us know. Documentation Conventions The following font conventions are used throughout documentation: This font Bold Citation Documentation Conventions [p. 9] Fixed width Fixed width bold Fixed width italic Indicates Terms, commands, and references to names of screen controls and user interface elements. Emphasized text, inline citations, titles of external books or articles. Links to Internet resources and linked references to titles in Compuware documentation. Cited contents of text files, inline examples of code, command line inputs or system outputs. Also file and path names. User input in console commands. Place holders for values of strings, for example as in the command: 9

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

11 CHAPTER 1 System Requirements This chapter describes the VantageView system requirements. VantageView consists of the following components: VantageView server The web server on which you install VantageView. Clients connect to the VantageView instance through the Internet Information Service (IIS). The server also hosts the Compuware Open Server (COS), which handles Alert processing. For more information, see Server Requirements [p. 11]. VantageView database The VantageView SQL Server database stores information used by VantageView. This database can be located on the SQL Server instance that stores your other Compuware APM databases. Subject to expected load factors and machine resource constraints, you can run SQL Server on the same machine as VantageView or on a remote server. For more information, see Database Requirements [p. 13]. Client machine The local machine uses Internet Explorer to view VantageView reports and to manage and configure Server Monitoring servers, all from inside or outside a firewall. For more information, see Client Requirements [p. 14]. Server Requirements There are many different ways to implement the Compuware APM suite. VantageView users, report generation, data mining interfaces, alert process, and alert notifications all cause load on the server. Therefore, consideration must be taken when sizing the server. Compuware recommends that you use servers that can expand to handle increased usage over time. VantageView can co-exist with other Compuware APM products (including the databases). However, Compuware recommends using dedicated servers in a production environment. You can use smaller servers for test or proof-of-concept environments. 11

12 Chapter 1 System Requirements The requirements listed below are for VantageView only. If you install other Compuware APM products or the VantageView database on the same server as VantageView, the listed requirements may be insufficient for the complete installation. For more information, refer to other Compuware APM products system requirements. The following table lists the system requirements for the server on which you install VantageView. Table 1. VantageView Server Requirements Requirement Machine: Specification Minimum: Recommended: Processor Speed 3.0 GHz single core or 2.0 GHz dual core processor Two 3.0 GHz single core or two 2.0 GHz dual core processors or higher. Multiple processors are strongly recommended if SQL Server is installed on the same machine. RAM Disk Space Modem 4 GB 40 GB (Excludes disk space required for the SQL Server application, if the database is installed on the VantageView server. Consult Microsoft documentation for details.) If needed for sending a page Notification. Server-class machine 8 GB (with upgrade capability up to 16 GB) More space may be needed for saving report results or storing large numbers of alerts. Display Operating Systems Super VGA (1024 by 768) or higher resolution video adapter and monitor. Windows Server bit with IIS 6.0 Windows Server 2003 R2 64-bit with IIS 6.0 Windows Server bit or 64-bit with IIS 7.0 and 7.5 Windows Server 2008 R2 64-bit with IIS 7.0 and 7.5 Windows Server 2012 with IIS 7.5, 8.0, and 8.5 Windows Server 2012 R2 with IIS 7.5, 8.0, and 8.5 Server Core installation is not supported. 12

13 Chapter 1 System Requirements Table 1. VantageView Server Requirements (continued) Requirement Specification Database Software (if installed on the VantageView server) Microsoft SQL Server 2005 (32-bit or 64-bit platform) Microsoft SQL Server 2008 (32-bit or 64-bit platform) Microsoft SQL Server 2008 R2 (64-bit platform) Microsoft SQL Server 2012 (64-bit platform) Browsers Microsoft Internet Explorer 7, 8, 9, 10, or 11 (32-bit version) with latest Service Packs Internet Explorer 10 and 11 must run in compatibility mode. Database Requirements If the VantageView database is installed on a machine other than the VantageView server, use the following table to determine the system requirements for the database server. Table 2. VantageView Database Requirements Requirement Machine: Specification Minimum: Recommended: Processor Speed 3.0 GHz single core or 2.0 GHz dual core processor Two 3.0 GHz single core or two 2.0 GHz dual core processors or higher. Multiple processors are strongly recommended if SQL Server is installed on the same machine. Server-class machine RAM 4 GB 8 GB (with upgrade capability up to 16 GB) Disk Space Display Operating Systems 40 GB (Excludes disk space for More space may be needed for databases other than VantageView.) saving report results or storing large numbers of alerts. Super VGA (1024 by 768) or higher resolution video adapter and monitor. Windows Server bit Windows Server 2003 R2 64-bit Windows Server bit or 64-bit Windows Server 2008 R2 64-bit Windows Server 2012 Windows Server 2012 R2 13

14 Chapter 1 System Requirements Table 2. VantageView Database Requirements (continued) Requirement Specification Server Core installation is not supported. For more information, see Microsoft Windows Server 2003 Configuration [p. 25] and Microsoft Windows Server 2008 Configuration [p. 29]. Database Software Microsoft SQL Server 2005 (32-bit or 64-bit platform) Microsoft SQL Server 2008 (32-bit or 64-bit platform) Microsoft SQL Server 2008 R2 (64-bit platform) Microsoft SQL Server 2012 (64-bit platform) Client Requirements The following hardware and software are required on the client machine used for browser access to VantageView. Table 3. Client Machine Hardware and Software System Requirements Requirement Machine: Processor Speed RAM Specification Minimum: 1 GHz 1 GB Recommended: 2 GHz or greater 2 GB Display Browser Super VGA (1024 by 768) or higher resolution video adapter and monitor Microsoft Internet Explorer 7, 8, 9, 10, or 11: 32-bit version, with latest Service Packs Internet Explorer 10 and 11 must run in compatibility mode. For information about operating system support for specific browser versions, refer to Microsoft documentation. VantageView Co-Location Deployment Guidelines Review the information in this section carefully if you plan to install multiple Compuware APM products. Should I install Compuware APM Components on Hardware with the Minimum Specifications? In almost every case where Compuware APM is used in a production mode operation, the answer is No. 14

15 Chapter 1 System Requirements You should use a machine that exceeds the Recommended/Preferred specification where available. If a Recommended/Preferred specification is not listed, then use a machine that greatly exceeds the Minimum specifications. IMPORTANT The Minimum requirement or specification of a Compuware APM component is intended for running that component at a minimum load. If the component is running on a machine with the minimum specification, performance will suffer as the load increases. Additionally, placing multiple Compuware APM components on a single machine places additional strain on the performance capabilities of these components. The Minimum requirement or specification of a Compuware APM component is intended for running that component at a minimum load. If the component is running on a machine with the minimum specification, performance will suffer as the load increases. Additionally, placing multiple Compuware APM components on a single machine places additional strain on the performance capabilities of these components. Co-Location of Compuware APM Components on a Single System When planning the deployment of VantageView, carefully consider how the components are deployed. The deployment of Compuware APM components directly impacts their performance. The Synthetic Monitoring Manager components, such as VantageView, Server Monitoring Control Server, and Synthetic Monitoring Agent Manager are designed and tested together. However, it is intended that such deployments of co-located Compuware APM components only be used in the following scenarios: Small deployments of Compuware APM components. Non-production environments with small loads. IMPORTANT Not all Compuware APM product components support the same platforms so make sure that you review the System Requirements in the Compuware APM product's Installation Guide for the list of supported platforms. Running Compuware APM Components on VMware Instances In addition to considering hardware and the co-location of Compuware APM components, careful consideration is required before deploying Synthetic Monitoring Manager components on VMware instances. When using VMware, there is a significant amount of system resources consumed as part of the VMware overhead. Careful sizing of the VMware systems should ensure that the memory and CPU resources actually available to the VMware instances should far exceed the recommended Compuware APM system specifications/requirements. After monitoring the actual performance of Compuware APM components running on VMware instances, it may be necessary to deploy the components on their own physical systems. 15

16 Chapter 1 System Requirements Recommendation for Production Environments For production deployments, each of the Synthetic Monitoring Manager components (VantageView, Server Monitoring Control Server, and Synthetic Monitoring Agent Manager) must be installed on separate physical machines. Synthetic Monitoring and Server Monitoring Integration Requirements Review the following requirements before installing Server Monitoring with Synthetic Monitoring (or Synthetic Monitoring with Server Monitoring). You can install a Server Monitoring Agent on the Agent Manager machine. You can also install the Agent Manager on a Server Monitoring Agent machine, provided it is a server. Because the Server Monitoring Agent is automatically installed when you install the Synthetic Monitoring Agent, you cannot install a Server Monitoring Agent on a Synthetic Monitoring Agent machine. Likewise, you cannot install a Synthetic Monitoring Agent on a Server Monitoring Agent machine. Because both applications automatically install the Server Monitoring Agent, you cannot install a Synthetic Monitoring Agent on a Server Monitoring Control Server. Likewise, you cannot install the Server Monitoring Control Server on a Synthetic Monitoring Agent. VMware and Virtualization This topic outlines Compuware APM component support for installation and operation on a VMware virtual machine. The decision to use VMware must be approached carefully, and the following capabilities and constraints must be considered during planning and deployment: VMware support is defined as the ability of the Compuware APM product component to install and operate on a VMware virtual machine. A VMware virtual machine must comply with the system requirements for the Compuware APM product component(s) running on it. For large-scale Compuware APM deployments, you must ensure that the virtual machines have sufficient resources, which can exceed stated system requirements due to the volume of data being collected and analyzed. For more information, see the system requirements specifications in the applicable Compuware APM product installation guide. The Compuware APM components support operation on VMware virtual machines only. Other virtual machine mechanisms are not supported. The monitoring of any specific VMware performance metrics is a capability of Server Monitoring. For more information, see the Server Monitoring online help topics that are available within VantageView. Use the following table to determine the support status of each component you intend to deploy on a VMware virtual machine. 16

17 Chapter 1 System Requirements Table 4. Compuware APM support for VMware Product / Component Support Status 1 Business Service Manager Business Service Manager servers Configuration Client Supported Supported Synthetic Monitoring Synthetic Monitoring Manager Synthetic Monitoring Console Parent Agent Manager/Agent Manager Active Agent, Collector Agent, Passive Agent Transaction Trace Analysis within Synthetic Monitoring Agent Scripts: Recorder, Micro Focus QALoad, Micro Focus QARun SQL Server Databases Supported Supported Supported Supported Supported 2 Supported Supported Data Center Real User Monitoring Central Analysis Server Web Client Central Analysis Server/Advanced Diagnostics Server Agentless Monitoring Device Probe Configuration Client Supported Best Effort Supported Supported Transaction Trace Analysis Database Agent Microsoft SQL Server 2005 Express Database Manager Supported Supported 2 Best Effort Best Effort Server Monitoring Control Server, Database Supported 1 2 Each Compuware APM component is assigned a support status, which identifies its compatibility with the VMware guest environment: Supported The component installs and operates in all VMware guest environments, providing that the product component is also compatible with the operating system being run in the guest environment Best Effort Calls to Compuware Customer Support will be investigated however there is no guarantee of results. Not Supported There are known product issues, including the inability to operate or deliver quality results. The VMware guest environment can introduce timing variations that affect the quality of the timing statistics. All other data, such as application identification and usage statistics, should be unaffected. In addition, the monitoring of heavily utilized links is adversely affected by sharing of resources between the virtual machine, the host (physical) machine, and any other virtual machines that are running on the same host machine. 17

18 Chapter 1 System Requirements Table 4. Compuware APM support for VMware (continued) Product / Component Template Manager Agent SNMP Collector Support Status 1 Supported Supported Supported Network Monitoring Interactive Viewer Enterprise Manager, Probe Manager, Independent Manager Probe LAN drivers, WAN drivers Flow Collector Supported Supported Not Supported 2 Supported VantageView Client Web Server Database Supported Supported Supported Compuware DLM Compuware Distributed License Management Supported Each Compuware APM component is assigned a support status, which identifies its compatibility with the VMware guest environment: Supported The component installs and operates in all VMware guest environments, providing that the product component is also compatible with the operating system being run in the guest environment Best Effort Calls to Compuware Customer Support will be investigated however there is no guarantee of results. Not Supported There are known product issues, including the inability to operate or deliver quality results. A licensing override is required to operate the Compuware License Service or a node-locked (single) license inside a VMware guest environment. Contact your Compuware account manager to initiate approval of a licensing override. You will receive the override and implementation instructions via from Compuware World Wide License Management. 18

19 CHAPTER 2 Installation Prerequisites This section describes the prerequisites for installing VantageView: Server Prerequisites [p. 20] Database Prerequisites [p. 32] Product Suite Prerequisites [p. 33] Installation Restrictions The following restrictions apply to all VantageView installations. Workgroups VantageView must be installed on a Windows server that is a member of a domain rather than a workgroup. Basic Authentication Basic authentication for access to the VantageView server is not supported. Instead, VantageView supports the NTLM authentication scheme. Refer to Microsoft s online documentation for information on how to configure IIS to support NTLM authentication. Proxy Servers VantageView does not support client access to the VantageView server through a proxy server. Anti-Virus Scanning VantageView web server The following files, folders (with all subfolders), and file types must be excluded from anti-virus scanning on the VantageView web server: Global.asa,global.asax, and web.config. The entire VantageView Virtual Directory tree. All files in C:\Windows\system32\Inetsrv. 19

20 Chapter 2 Installation Prerequisites Compuware APM database servers The following files, folders (with all subfolders), and file types must be excluded from anti-virus scanning on the database servers of all Compuware APM products: *.ldf *.mdf Pre-installation Checklist Use this checklist to confirm all the prerequisites are met before you install VantageView. Table 5. Pre-installation Checklist Finished Steps Review the VantageView system requirements. For more information, see System Requirements [p. 11]. Make sure the server is configured properly. For more information, see Server Prerequisites [p. 20]. Make sure the database is configured properly. For more information, see Database Prerequisites [p. 32]. Review the Compuware APM product suite prerequisites. For more information, see Product Suite Prerequisites [p. 33]. Review the installation restrictions. For more information, see Installation Restrictions [p. 19]. Server Prerequisites Install and Configure IIS Make sure IIS (Internet Information Services) with Web Server Extensions is installed and configured on the server. VantageView requires that IIS, multiple web server extensions, SMTP, and.net 2.0 are all installed and enabled on the server before starting the VantageView installation. If you have IIS 7.5 or later, the IIS_IUSRS group must have Read permission on the nodes /LM/SmtpSvc and /LM/SmtpSvc/1 and Full Control permission on the mailroot directory. For more information, see Configuring Permissions for IIS 7.5 or Later [p. 23]. Make sure SMTP is enabled on the VantageView web server if notifications or VantageView reports will be sent from this server. Enable.NET 2.0 extensions. VantageView installs.net, but you must enable it in IIS after installation. IIS provides web server functionality required by VantageView for publishing reports. The process for ensuring that IIS is installed and enabling FTP and SMTP depends on the operating system and IIS version. Consult Microsoft s documentation for details. 20

21 Chapter 2 Installation Prerequisites For Windows Server 2008, you must install IIS 7.0 and enable IIS 6 Management Compatibility. For more information, see Install IIS in Windows Server 2003 [p. 25] and Install IIS in Windows Server 2008 [p. 29]. Install and Configure Web Server Extensions Allow the Active Server Pages (ASPs) extension, Server Side Includes (SSIs) extension, and ASP.NET extensions. By default, these extensions are prohibited on Microsoft Windows Allowing these extensions involves modifying the installed Windows components. The procedure varies with the operating system and IIS version. For more information, see Install/Allow Web Server Extensions in Windows Server 2003 [p. 26] and Install/Allow Web Server Extensions in Windows Server 2008 [p. 30]. The VantageView web server is often a primary publishing destination for reports. VantageView relies on WebDAV (Web-based Distributed Authoring and Versioning document-sharing technology by Microsoft) to publish reports. All VantageView publishing destinations must have WebDAV enabled. Consult Microsoft s documentation for details. For more information, see Verify WebDAV Extension Installation in Windows Server 2003 [p. 27] and Verify WebDAV Extension Installation in Windows Server 2008 [p. 31]. Configure SMTP to Send Reports via Verify that the SMTP service is installed and enabled in IIS. Verify that the properties of the Default SMTP Virtual Server (Fully Qualified Domain Name and Smart Host fields) are set up to allow VantageView reports to be sent via . By default, SMTP is not installed in Windows Server For more information, see Install SMTP in Windows Server 2003 [p. 28] and Install SMTP in Windows Server 2008 [p. 32]. To successfully publish on the local machine, write privileges must be granted to the account that runs the w3wp process. By default, this is the network service account. Add the write privileges to the target of the publish operation. The default targets are: SMTP inetpub\mailroot FTP inetpub\ftproot HTTP inetpub\wwwroot Disable Internet Explorer's Enhanced Security Configuration If you are running Microsoft Windows Server 2003 or Windows Server 2008, disable the Windows Component Internet Explorer Enhanced Security Configuration. If enabled, this feature interferes with access to the VantageView web server. For more information, see Disable Internet Explorer Enhanced Security in Windows Server 2003 [p. 26] and Disable Internet Explorer Enhanced Security in Windows Server 2008 [p. 30]. 21

22 Chapter 2 Installation Prerequisites Confirm That the VantageView Host Is a Member of a Windows Domain You must install VantageView on a Windows server that is a member of a domain, not a workgroup. Workgroups are not supported. VantageView establishes security based on Windows domain user accounts. Users that access VantageView are authenticated with their Active Directory account. Depending on the security settings within Internet Explorer, you are either automatically logged in with your current ID, or you are prompted to authenticate. For more information about domains, see Microsoft s documentation. Confirm That Total System Capacity Is Sufficient In most cases, VantageView can be installed on the same machine with other Compuware APM components, such as the Synthetic Monitoring Agent Manager or the Server Monitoring Control Server. However, VantageView performance can be adversely impacted by the workload created by other Compuware APM products, so be sure to provide adequate server capacity to handle the load. Not all Compuware APM product components support the same platforms. Before installing other components, review the system requirements in each product's installation guide for platform support details. Running VantageView on a Windows Server bit Machine You cannot install VantageView on a server configured as a Terminal Service Gateway server. The Feature Remote Procedure Call (RPC) over HTTP Proxy must be disabled. Table 6. Ports Listing VantageView Ports and Protocols Component Default Port Protocol Authentication Required Notes VantageView 80 HTTP Yes VantageView operates on the standard HTTP port 80 by default. If necessary, you can configure it within IIS to operate on a different port. VantageView web server 443 HTTPS Yes HTTPS is supported for accessing the VantageView web server. When it is enabled, all network communication between the client and server is encrypted. HTTPS is strongly recommended for any client connections that are established from outside a network firewall. For more information, consult Microsoft s documentation for installing SSL certificates and HTTPS on your web server. Changepoint Server 90 HTTP Yes Connect to the Changepoint server. 22

23 Chapter 2 Installation Prerequisites Table 6. Ports Listing (continued) Component Default Port Protocol Authentication Required Notes SMTP Server 25 HTTP No Publish reports via . FTP Server 21 HTTP Yes Publish reports via FTP. Agentless Monitoring connection 80 HTTP No Connect to Central Analysis Server. Database access 1433 HTTP Yes Access the SQL Server database. Network Monitoring connection 9003 HTTP No Connect to Network Monitoring Enterprise Manager. Server Monitoring connection 3009 TCP Yes Connect to the Server Monitoring Control Server. Remedy connection User-defined TCP Yes Connect to the Remedy server. COS HTTP No VantageView uses the COS that is automatically installed and configured during the VantageView installation. If you are performing a new installation, the default COS port is on the server. If you are migrating from an earlier release, VantageView retains the previous COS port configuration. For information regarding third-party integration into the COS, refer to the online documentation available on the server where VantageView is installed. On the Windows Start menu, choose Programs Compuware Compuware Open Server. Configuring Permissions for IIS 7.5 or Later In IIS 7.5 or later, the IIS_IUSRS group must have Read permission on the nodes /LM/SmtpSvc and /LM/SmtpSvc/1. The group must also have Full Control permission on the mailroot directory. Procedures for configuring the permissions are provided in the following topics: Providing Metabase Permissions to the IIS_IUSRS Account [p. 23] Giving File Permissions to IIS_IUSRS on the Mailroot Directory [p. 24] Providing Metabase Permissions to the IIS_IUSRS Account 1. Download and install the Internet Information Services (IIS) 6.0 Resource Kit Tools. 23

24 Chapter 2 Installation Prerequisites This resource is available from It includes a Metabase Explorer that works with IIS 6.0, IIS 7.0 and IIS 7.5 with IIS 6 Management Compatibility role services installed. 2. After installation is finished, open the Metabase Explorer tools. In the Windows Start menu, select All Programs IIS Resources Metabase Explorer Metabase Explorer. 3. In the Metabase Explorer, go to the node /LM/SMTPSVC. 4. Right-click the node and select Permissions from the context menu. The Permissions dialog box opens. 5. Click Add to open the Select Users. Computers, Service Accounts, Or Groups dialog box. 6. Click Locations to open the Locations dialog box. Select your local computer, then click OK to close the dialog box and return to the Select Users. Computers, Service Accounts, Or Groups dialog box. 7. In the Enter the object names to select field, type IIS_IUSRS. 8. Click Check Names. When IIS_IUSRS is resolved, click OK to close this dialog box and return to the Permissions dialog box. 9. In the Group or user names list, select IIS_IUSRS. 10. In the permissions list for IIS_IUSRS, ensure that Allow is selected for the Read permission and that no other permissions are assigned. 11. Click OK to save the change and close the Permissions dialog box. In the Properties dialog box, the Permissions for IIS_IUSRS list shows the change you just made. 12. Click OK to close the dialog box. 13. In the Metabase Explorer, go to the node /LM/SMTPSVC/1 and perform Step 4 [p. 24] through Step 12 [p. 24] for the node /LM/SMTPSVC/1. What to Do Next After completing this procedure, assign file permissions to the IIS_IUSRS group on the mailroot directory. Giving File Permissions to IIS_IUSRS on the Mailroot Directory 1. Go to the mailroot directory on your computer. The default location should be C:\inetpub\mailroot. 2. Right-click the mailroot folder and select Properties to open the mailroot Properties dialog box. 3. Select the Security tab, then click Edit to open the Permissions for mailroot dialog box. 4. Click Add to open the Select Users, Computers, Service Accounts, or Groups dialog box. 5. Click Locations to open the Locations dialog box. 24

25 Chapter 2 Installation Prerequisites Select your local computer, then click OK to close this dialog box and return to the Select Users. Computers, Service Accounts, Or Groups dialog box. 6. In the Enter the Object names to select field, type IIS_IUSRS. 7. Click Check Names. When IIS_IUSRS is resolved, click OK to close this dialog box and return to the Permissions for mailroot dialog box. 8. In the Group or user names list, select IIS_IUSRS. 9. In the permissions list for IIS_IUSRS, select Allow for the Full control permission. 10. Click OK to save the change and close the Permissions for mailroot dialog box. In the Properties dialog box, the Permissions for IIS_IUSRS list shows the change you just made. 11. Click OK to close the mailroot Properties dialog box. Microsoft Windows Server 2003 Configuration Before installing VantageView, make the following configuration changes for Microsoft Server 2003: 1. Install Internet Information Services (IIS) 7.0 plus IIS 6 Management Compatibility. For more information, see Install IIS in Windows Server 2003 [p. 25]. 2. Disable Internet Explorer Enhanced Security. For more information, see Disable Internet Explorer Enhanced Security in Windows Server 2003 [p. 26]. 3. Install/allow the following web server extensions: Active Server Pages, ASP.NET, and Service Side Includes (SSI). For more information, see Install/Allow Web Server Extensions in Windows Server 2003 [p. 26]. 4. Install/allow web server extension WebDAV. For more information, see Verify WebDAV Extension Installation in Windows Server 2003 [p. 27]. 5. Enable Windows Authentication. For more information, see Configure Windows Authentication in Windows Server 2003 [p. 28]. 6. If it is required, install SMTP (Simple Message Transfer Protocol). For more information, see Install SMTP in Windows Server 2003 [p. 28]. 7. Install SNMP (Simple Network Management Protocol). For more information, see Install SNMP in Windows Server 2003 [p. 29]. Install IIS in Windows Server 2003 IIS provides web server functionality required by VantageView for publishing reports. Verify that IIS with Web Server Extensions is installed. In Windows Administrative Tools, if IIS is installed, Internet Information Services (IIS) Manager appears in the list. If it is not listed, you need to install it. 1. Open Control Panel (Start Settings Control Panel or Start Control Panel). 2. Select Add/Remove Programs. 25

26 Chapter 2 Installation Prerequisites 3. When the Add or Remove Programs window opens, select Add/Remove Windows Components. The Windows Setup wizard appears and after a few moments the Windows Components Wizard dialog box opens. 4. If not already enabled, enable Application Server. 5. Select Application Server and click Details. 6. Enable Internet Information Services (IIS). Also verify that ASP.NET is enabled. For more information, see Install/Allow Web Server Extensions in Windows Server 2003 [p. 26]. 7. Click OK. 8. Click Next when returned to the Windows Components window. 9. Click Finish when the Completing the Windows Component Wizard window appears. Disable Internet Explorer Enhanced Security in Windows Server 2003 VantageView requires that Internet Explorer Enhanced Security be disabled on Windows Server Open Control Panel (Start Settings Control Panel or Start Control Panel). 2. Select Add/Remove Programs. 3. When the Add or Remove Programs window opens, select Add/Remove Windows Components. The Windows Setup wizard appears and after a few moments the Windows Components Wizard dialog box opens. 4. If necessary, disable Internet Explorer Enhanced Security Configuration. 5. Click Next. 6. Click Finish when the Completing the Windows Component Wizard window appears. Install/Allow Web Server Extensions in Windows Server 2003 VantageView requires that the Active Server Pages (ASPs) extension, Server Side Includes (SSIs) extension, and ASP.NET extension are installed and enabled on Windows Server By default, these extensions are Prohibited on Microsoft Windows Allowing these extensions involves modifying the installed Windows components; the procedure varies with the operating system and IIS version. The VantageView web server is often a primary publishing destination for reports. VantageView relies on WebDAV (Web-based Distributed Authoring and Versioning, document-sharing technology by Microsoft) to publish reports. All VantageView publishing destinations must have WebDAV enabled. Consult Microsoft s documentation for details. 1. Open Control Panel (Start Settings Control Panel or Start Control Panel). 2. Select Add/Remove Programs. 3. When the Add or Remove Programs window opens, select Add/Remove Windows Components. 26

27 Chapter 2 Installation Prerequisites The Windows Setup wizard appears and after a few moments the Windows Components Wizard dialog box opens. 4. The Windows Setup wizard appears and after a few moments the Windows Components Wizard dialog box opens. 5. If not already enabled, enable Application Server. 6. Select Application Server and click Details. The Application Server dialog box appears. 7. In the Subcomponents of Application Server list, enable ASP.NET and Internet Information Services (IIS). 8. Then, select Internet Information Services (IIS) and click Details. 9. In the Internet Information Services (IIS) dialog box, select File Transfer Protocol (FTP) Service, SMTP Service, then select/enableworld Wide Web Service and click Details. 10. In the World Wide Web Service dialog box, enable Active Server Pages, Server Side Includes, and WebDAV Publishing. For more information, see Verify WebDAV Extension Installation in Windows Server 2003 [p. 27]. 11. Click OK and you are returned to the Internet Information Services (IIS) dialog box. Click OK. 12. In the Application Server dialog box, click OK. In the Windows Components window, click Next to begin installation. 13. Click Finish when the Completing the Windows Component Wizard window appears. Verify WebDAV Extension Installation in Windows Server 2003 VantageView relies on WebDAV (Web-based Distributed Authoring and Versioning document-sharing technology by Microsoft) to publish reports. All VantageView publishing destinations must have WebDAV enabled. On Windows Server 2003, verify that WebDAV has been installed: In Administrative Tools, open Internet Information Services (IIS) Manager. Expand the server name, then double-click Web Service Extensions. If WebDAV is installed, it will be listed under the Web Service Extension column. If it is not installed, follow the directions below. 1. Open Control Panel (Start Settings Control Panel or Start Control Panel). 2. Select Add/Remove Programs. 3. When the Add or Remove Programs window opens, select Add/Remove Windows Components. The Windows Setup wizard appears and after a few moments the Windows Components Wizard dialog box opens. 4. If not already enabled, enable Application Server. 5. Select Application Server and click Details. The Application Server dialog box appears. 27

28 Chapter 2 Installation Prerequisites 6. In the Subcomponents of Application Server list, enable Internet Information Services (IIS). 7. Then, select Internet Information Services (IIS) and click Details. 8. Select World Wide Web Service and click Details. 9. In the World Wide Web Service dialog box, enable WebDAV Publishing. In addition to the WebDAV extension, ASP.NET, Active Server Pages, and Server Side Includes are also required, you can enable these at this time, or at a later time. For more information, see Install/Allow Web Server Extensions in Windows Server 2003 [p. 26]. 10. Click OK and you are returned to the Internet Information Services (IIS) dialog box. Click OK. 11. In the Application Server dialog box, click OK. In the Windows Components window, click Next to begin installation. 12. Click Finish when the Completing the Windows Component Wizard window appears. Configure Windows Authentication in Windows Server 2003 Windows authentication must be enabled in Windows Server 2003 before installing VantageView. 1. Open Internet Information Services (IIS) Manager. Select Start Administrative Tools Internet Information Services (IIS) Manager. 2. Right-click Web Sites and select Properties. 3. Select the Directory Security tab. 4. In the Authentication and access control section click Edit. 5. If enabled, disable Enable anonymous access, then enable Integrated Windows authentication. 6. Click OK. Install SMTP in Windows Server Open Control Panel (Start Settings Control Panel or Start Control Panel). 2. Select Add/Remove Programs. 3. When the Add or Remove Programs window opens, select Add/Remove Windows Components. The Windows Setup wizard appears and after a few moments the Windows Components Wizard dialog box opens. 4. Select Application Server. 5. In the Application Server dialog box, select Internet Information Services (IIS) and click Details. 6. In the Internet Information Services (IIS) dialog box, enable SMTP Service and click OK. 7. In the Application Server dialog box, click OK. In the Windows Components window, click Next to begin installation. 8. When the Completing the Windows Components Wizard screen appears, click Finish. 28

29 Chapter 2 Installation Prerequisites Install SNMP in Windows Server Open Control Panel (Start Settings Control Panel or Start Control Panel). 2. Select Add/Remove Programs. 3. When the Add or Remove Programs window opens, select Add/Remove Windows Components. The Windows Setup wizard appears and after a few moments the Windows Components Wizard dialog box opens. 4. Enable Management and Monitoring Tools then click Details. 5. In the Management and Monitoring Tools dialog box, enable Simple Network Management Protocol and click OK. 6. In the Windows Components Wizard dialog box click Next. The Configuring Components window displays showing the progress of the component installation/configuration. 7. When the Completing the Windows Components Wizard screen appears, click Finish. Microsoft Windows Server 2008 Configuration Before installing VantageView requires that you make the following configuration changes for Microsoft Windows Server 2008: Install Internet Information Services (IIS) 7.0 plus IIS 6 Management Compatibility. For more information, see Install IIS in Windows Server 2008 [p. 29]. Disable Internet Explorer Enhanced Security. For more information, see Disable Internet Explorer Enhanced Security in Windows Server 2008 [p. 30]. Install/allow the following web server extensions: Active Server Pages, ASP.NET, and Service Side Includes (SSI). For more information, see Install/Allow Web Server Extensions in Windows Server 2008 [p. 30]. Install/allow web server extension WebDAV. For more information, see Verify WebDAV Extension Installation in Windows Server 2008 [p. 31]. Enable Windows Authentication. For more information, see Configure Windows Authentication in Windows Server 2008 [p. 31]. Install SMTP (Simple Message Transfer Protocol). For more information, see Install SMTP in Windows Server 2008 [p. 32]. Install SNMP (Simple Network Management Protocol). For more information, see Install SNMP in Windows Server 2008 [p. 32]. Install IIS in Windows Server 2008 Make sure IIS (Internet Information Services) with web server extensions is installed. IIS provides web server functionality required by VantageView for publishing reports. The process for ensuring that IIS is installed and enabling SMTP is dependent upon the operating system and IIS version. Consult Microsoft s documentation for details. 29

30 Chapter 2 Installation Prerequisites For Windows Server 2008, you must install IIS 7.0 and enable IIS 6 Management Compatibility. First verify that IIS has not already been installed. 1. From the Administrative Tools menu, open the Server Manager. 2. Select Roles. 3. Click Add Roles. In the Select Server Roles section, if enable Web Server (IIS) is enabled, continue to Step 5 [p. 30], or enable Web Server (IIS) and click Next. 4. Follow the prompts to install IIS In the Server Manager, select Roles Add Role Services. 6. In the Select Role Services section, enable IIS 6 Management Compatibility. This option is located under the heading Management Tools in the list. 7. Click Next. Continue the installation by following the on-screen prompts. 8. Next, install IIS 6 Management Compatibility. 9. From the Administrative Tools menu, open the Server Manager. 10. Click Roles, then select Web Server (IIS). 11. Under Role Service, select Add Role Services. 12. Under Select Role Services, locate and enable IIS 6 Management Compatibility. This option is located under Management Tools in the list. 13. Click Next. 14. Follow the prompts to complete the installation. Disable Internet Explorer Enhanced Security in Windows Server From the Administrative Tools menu, open the Server Manager. 2. In the Server Summary section, in the Security Information section, select Configure IE ESC. 3. In the Internet Explorer Enhanced Security Configuration window, select Off for both Administrators and Users to disable IE Enhanced Security then click OK to save your changes and exit. Install/Allow Web Server Extensions in Windows Server 2008 VantageView requires that the following web server extensions are installed and enabled in Windows Server 2008: Active Server Pages (ASP) Server Side Includes (SSI) ASP.NET 1. From the Administrative Tools menu, open the Server Manager. 2. Under Role Services, locate the web server extensions listed above to see if they have already been installed. 3. If they are not installed, click Add Role Services. 4. In the Select Role Services section, in the Application Development section, enable the following: 30

31 Chapter 2 Installation Prerequisites ASP.NET ASP Server Side Includes During installation, accept the Default installation values for each of these extensions. If you accept the defaults for these extensions, the following extensions are also installation:.net Extensibility ISAPI Extensibility ISAPI Filters 5. Restart IIS after installation. Select Start Run and in the Run dialog box, type iisreset and click OK. Verify WebDAV Extension Installation in Windows Server 2008 The WebDAV extension is not available for Windows Server 2008, but is required for VantageView. Access the following web site, then download and install WebDAV for IIS 7.0: Link to WebDAV Extension for Server In IIS 7.5, WebDAV is available by default. You do not need to download it, but you should verify the installation. To verify that WebDAV has been installed, do the following: 1. From the Administrator Tools menu, open Internet Information Services (IIS) Manager. 2. Select the machine name from the Connections window. 3. If WebDAV has been installed, WebDAV Authoring Rules appears in the right pane. 1. From the Administrator Tools menu, open Internet Information Services (IIS) Manager. 2. Select the machine name from the Connections window. 3. If WebDAV has been installed, WebDAV Authoring Rules appears in the right pane. Configure Windows Authentication in Windows Server 2008 Windows authentication must be enabled in Windows Server 2008 before installing VantageView. 1. From the Administrative Tools menu, open the Server Manager. 2. In the Roles section, select Web Server (IIS). 3. In the Role Services section, select Add Role Services. 4. Scroll to the Select Role Services section and select/enable Windows Authentication. Windows authentication is now enabled. 31

32 Chapter 2 Installation Prerequisites Install SMTP in Windows Server 2008 By default SMTP is not installed and enabled on Windows Server 2008, but required by VantageView. 1. From the Administrative Tools menu, open the Server Manager. 2. In the Features section, select Add Features. 3. In the Select Features window, select/enable SMTP Server. 4. Click Next and accept the installation defaults. Install SNMP in Windows Server 2008 By default, SNMP is not installed on Windows Server 2008, but required by VantageView. 1. From the Administrative Tools menu, open the Server Manager. 2. In the Features section, select Add Features. 3. In the Select Features window, select/enable SNMP Services. 4. Click Next and accept the installation defaults. Database Prerequisites Back up the Current VantageView Database For more information, see Backing Up and Restoring VantageView [p. 85]. Ensure That the SQL Server Database Is Set As Case-insensitive Compuware APM products cannot be installed on a database server that is case-sensitive. A default SQL Server installation is 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 VantageView Database If you are migrating VantageView data and the new VantageView database will be on a different server than the existing VantageView database, then the SQL Server version of the new database must be the same as or later than the SQL Server version of the current location. Verify the SQL Server Agent Settings When the VantageView database is created, SQL Server jobs are installed for maintaining alerts. If you want alerts maintenance to be active, make sure the SQL Server agent service is started and that its Startup Type property is set to Automatic. 32

33 Chapter 2 Installation Prerequisites Product Suite Prerequisites Install Service Packs to companion products Where applicable, check FrontLine ( for any Service Packs that may need to be installed on Compuware APM products before migrating VantageView. For more information, see Installing Service Packs [p. 90]. 33

34 Chapter 2 Installation Prerequisites 34

35 CHAPTER 3 Installing VantageView This chapter describes the procedures for installing VantageView. Before installing VantageView, review the system requirements and installation prerequisites. For more information, see System Requirements [p. 11]. Installation Overview VantageView offers convenient options for installation or migration. If you are installing VantageView for the first time, you can install VantageView automatically with the Server Monitoring or Synthetic Monitoring installations. Refer to the Synthetic Monitoring Installation Guide or the Server Monitoring Installation Guide. You can also install VantageView separately, using the installer provided through the media browser, but in this case you will need to manually configure the other product components for use with VantageView. For more information, see Installation Procedure [p. 38]. VantageView is backward-compatible with specific earlier releases of other Compuware APM products. For more information, see Compatible Compuware APM Product Releases [p. 45]. You can install the new release of VantageView; migrate reports, filters, database connections, server groups, user preferences, alert information, and user IDs from an earlier release; and at a later time, upgrade your other Compuware APM products if they are at a compatible release level. Do the following to install VantageView for the first time: 1. Review the VantageView system requirements to make sure the hardware/software you are using meets the recommended requirements. For more information, see System Requirements [p. 11]. 2. Review the co-location guidelines if you plan to install other Compuware APM products on the same machine as VantageView. For more information, see VantageView Co-Location Deployment Guidelines [p. 14]. If you are installing other VantageView products on the same server, note that not all VantageView product components support the same platforms. Review the system requirements for all co-located products for platform support details. 35

36 Chapter 3 Installing VantageView 3. Make sure the server is configured properly. For more information, see Server Prerequisites [p. 20]. 4. Make sure the database is configured properly. For more information, see Database Prerequisites [p. 32]. 5. Log on to the system as Administrator. If you intend to create the VantageView database using Windows Authentication instead of SQL Server Authentication, you must log on to the system with a domain account that is part of the Administrators group on the VantageView server machine. You can also log on with a local user account that is part of the Administrators group on the VantageView server machine, if SQL Server is installed on the local machine and you will be using the local user account to create the database. 6. Install VantageView. For more information, see Installation Procedure [p. 38]. 7. Finish the VantageView installation as required. For more information, see Finishing the VantageView Installation [p. 55]. Installation Overview VantageView offers convenient options for installation or migration. If you are installing VantageView for the first time, you can install VantageView automatically with the Server Monitoring or Synthetic Monitoring installations. Refer to the Synthetic Monitoring Installation Guide or the Server Monitoring Installation Guide. You can also install VantageView separately, using the installer provided through the media browser, but in this case you will need to manually configure the other product components for use with VantageView. For more information, see Installation Procedure [p. 38]. VantageView is backward-compatible with specific earlier releases of other Compuware APM products. For more information, see Compatible Compuware APM Product Releases [p. 45]. You can install the new release of VantageView; migrate reports, filters, database connections, server groups, user preferences, alert information, and user IDs from an earlier release; and at a later time, upgrade your other Compuware APM products if they are at a compatible release level. Do the following to install VantageView for the first time: 1. Review the VantageView system requirements to make sure the hardware/software you are using meets the recommended requirements. For more information, see System Requirements [p. 11]. 2. Review the co-location guidelines if you plan to install other Compuware APM products on the same machine as VantageView. For more information, see VantageView Co-Location Deployment Guidelines [p. 14]. 36

37 Chapter 3 Installing VantageView If you are installing other VantageView products on the same server, note that not all VantageView product components support the same platforms. Review the system requirements for all co-located products for platform support details. 3. Make sure the server is configured properly. For more information, see Server Prerequisites [p. 20]. 4. Make sure the database is configured properly. For more information, see Database Prerequisites [p. 32]. 5. Log on to the system as Administrator. If you intend to create the VantageView database using Windows Authentication instead of SQL Server Authentication, you must log on to the system with a domain account that is part of the Administrators group on the VantageView server machine. You can also log on with a local user account that is part of the Administrators group on the VantageView server machine, if SQL Server is installed on the local machine and you will be using the local user account to create the database. 6. Install VantageView. For more information, see Installation Procedure [p. 38]. 7. Finish the VantageView installation as required. For more information, see Finishing the VantageView Installation [p. 55]. Installation Checklist Table 7. VantageView Installation Checklist Finished Steps Review the pre-installation requirements. For more information, see Pre-installation Checklist [p. 20]. Install VantageView as directed in the instructions. For more information, see Installation Procedure [p. 38]. After VantageView is installed, finish the installation: Register TeeChart7.ocx on the client. For more information, see Register TeeChart7.ocx on the Client [p. 55]. Configure the VantageView server. Verify the data location file permissions for users. Register TeeChart7.ocx on the server. Verify access for the Windows Everyone Group Exclude particular files and directories from anti-virus scanning on the VantageView server and the other product database servers. For more information, see Configuring the VantageView Server [p. 56]. 37

38 Chapter 3 Installing VantageView Table 7. VantageView Installation Checklist (continued) Finished Steps If you installed a new VantageView installation to use with existing products, re-test the connections to their databases. For more information, see Configure Database Connections [p. 59]. Verify the success of the VantageView installation: Access VantageView. Configure VantageView security groups. Configure the database connections. Test the manual report publishings. Install the MySQL JDBC driver. For more information, see Verifying the Success of the VantageView Installation [p. 58]. If required, set up domain-based security for the VantageView database. For more information, see Implementing Domain-based Database Security in VantageView [p. 60]. During VantageView migration, SQL-account-based authentication defaults are restored. Any previously configured domain-based security settings must be re-applied. Installation Procedure This section does not include the steps to migrate an earlier release of VantageView to a new release. For more information, see Migrating VantageView [p. 43]. 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 Solaris 4. Insert the disc into your computer's DVD drive and wait for the media browser to start. If the media browser does not run automatically, run the setup.exe application on the DVD to start the media browser manually. If you have downloaded the product, go to the equivalent folder in your downloaded copy and run the setup.exe application. 5. Select the Synthetic Monitoring tab, then click VantageView. 38

39 Chapter 3 Installing VantageView The Operating System Updates window appears. The installation process runs an operating system (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. If SQL 2005 Backward Compatibility or Microsoft.NET Framework does not already exist on your system, it will be installed. During the installation, a message may be displayed that the IIS ASP extension is not enabled. Click OK. The IIS ASP extension is one of the web service extensions required for VantageView. For more information, see Server Prerequisites [p. 20]. 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 is enabled, when you click Next, a browser window opens automatically and directs the browser 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 agreed to the terms. 8. When the GNU Lesser General Public License Agreement window appears, click Yes once you have read and agreed to the terms. 9. When the Customer Information window appears, type your User Name and Company Name in the Customer Information window. Click Next. If prompted, select Yes, I want to restart my computer now. Upon reboot, the server automatically restarts the installation application. If the installation does not automatically restart, repeat the tasks performed previously. 10. Click Next in the Choose Destination Location window to accept the default installation location, or click Browse to change the location. The default installation path is C:\Program Files\Compuware\VantageView Click Next in the Choose Data Location window to accept the default data location, or click 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\VantageView However, it is common practice to install the data folder on a separate drive. 39

40 Chapter 3 Installing VantageView CAUTION If your system does not meet the minimum hardware and system requirements, you may receive the warning: At least one Hardware or Software recommendation has failed. Click OK to view the details of the components that passed and failed. Some warnings require you to click Cancel to stop the installation process and upgrade your system to the minimum hardware and software requirements before continuing the installation. 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 the Available Web Sites menu, then, in the Virtual Directory Name field, type the name of the virtual directory and click Next. The virtual directory name must contain only letters, numbers, and hyphens. The default virtual directory name is Vantage. If you are installing a new release of VantageView where an earlier release was installed, this name may already be in use. If it is already in use, the installation prohibits you from using the same name. Choose a different name, such as Vantage In the Select Program Folder window, click Next to accept the default program folder for VantageView You can also select an existing program folder from the Existing Folders 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. If you have multiple instances of SQL Server on the same machine, make sure the instance name is entered as server_name\instance_name. If the full instance name does not appear in the list, you can type it in the field. b. Type the Database Name. The database name must contain only letters, numbers, and hyphens. The default database name is VantageViewDB. Since you are migrating, this name will likely already be in use. If it is already in use, the installation prohibits you from using the same name. Choose a different name, such as VantageViewDB117. c. Select Windows Authentication or SQL Authentication. Click Next. 40

41 Chapter 3 Installing VantageView If selecting SQL Authentication, enter the proper user ID and password to create the database. If selecting Windows Authentication, you must ensure that the user which is currently logged onto the VantageView server has sysadmin rights on the SQL Server. d. The default installation path, database size, and log size are usually sufficient, but you can change them if needed. 15. Click Next. 16. If you are on a server that does not contain an earlier release of VantageView, a prompt appears, asking if you want to migrate an earlier release of VantageView from another machine. Select Yes or No: Yes No If you click Yes you are prompted during the installation for information about where you want to migrate data from. For more information, see Migrating VantageView to the New Release [p. 48]. If you click No, the installation continues. 17. On the next screen, review the current settings. To make changes, click Back. If the settings appear correct, click Next. When you click Next, installation begins. IMPORTANT The installation process may take several minutes. Do not interrupt the installation. 18. Click Finish to close the InstallShield Wizard. If this screen includes a prompt to restart your computer, keep the default selection of Yes to restart. What to Do Next Additional tasks are required after installing VantageView. For more information, see Finishing the VantageView Installation [p. 55]. IMPORTANT If you have installed VantageView on a 64-bit operating system and it does not run properly, you may need to perform additional steps. For more information, see Installing VantageView on a 64-bit Operating System [p. 42]. 41

42 Chapter 3 Installing VantageView Installing VantageView on a 64-bit Operating System IMPORTANT Only use the procedure in this topic if VantageView does not run after installing it on a 64-bit operating system. VantageView is a 32-bit application which requires 32-bit IIS (Internet Information Services) components. VantageView must be installed in an x86 directory, e.g. \Program Files (x86)\. By default, the.net framework installed on the 64-bit operating system is the 64-bit version and does not run 32-bit web sites properly. To use VantageView on a 64-bit operating system, the 32-bit version of the.net Framework will need to be installed and enabled. If a 64-bit web application is currently installed on the web server, VantageView cannot be installed. IIS does not support both 32-bit and 64-bit applications running on the same server. Additionally: You cannot install VantageView on a server configured as a Terminal Service Gateway server. The role Remote Procedure Call (RPC) over HTTP Proxy must be disabled. To enable IIS for 32-bit applications, follow the steps, recommended by Microsoft, below. For more information, visit Microsoft's web site at 1. From the Windows Start menu, select Run, then type cmd in the Run dialog box and then press [Enter] (or click OK). 2. Enable the 32-bit mode. At the command prompt, type cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 and press [Enter]. 3. Install the 32-bit version of ASP.NET 2.0 and install the script maps at the IIS root and under: Type %SYSTEMROOT%\Microsoft.NET\Framework\v \aspnet_regiis.exe -I then press [Enter]. 4. Verify that the status of the ASP.NET version (32-bit) is set to Allowed in the Web service extension list in the Internet Information Services Manager. 42

43 CHAPTER 4 Migrating VantageView This chapter provides information about the migration prerequisites, the migration process, and post-migration information: Migration Overview [p. 43] Migration Checklist [p. 45] Migration Prerequisites [p. 44] Migrating VantageView to the New Release [p. 48] VantageView Data Migration [p. 47] VantageView Release 12.0 can be migrated from Release 10.2 or higher. To migrate from Release 10.2, the latest service pack must be applied. If you migrate VantageView from a release earlier than 11.5, and you have other Compuware APM products, you may not be able to use your current release of the other product(s) with VantageView Release For more information, see Compatible Compuware APM Product Releases [p. 45]. Refer to the Compuware APM Product Migration Guide, available on FrontLine at for guidelines for planning the upgrade/migration process and for crucial information specific to the following scenarios: Your current release is installed on a platform that is not supported for the new release. You have multiple Compuware APM products installed, for example Server Monitoring plus VantageView or Synthetic Monitoring plus VantageView. Migration Overview Before beginning the VantageView migration: Review the system requirements to ensure that the hardware you are using is sufficient to run VantageView. This is especially true if you are running VantageView with other 43

44 Chapter 4 Migrating VantageView Compuware APM product components on the same machine. For more information, see System Requirements [p. 11]. Make sure your current installation is a release that can be migrated to the new release, with service pack applied if necessary. CAUTION Do not uninstall the earlier release of VantageView before migration. If you do, you will lose saved 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 your other 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, see Compatible Compuware APM Product Releases [p. 45]. For more information, see Migration Considerations in the VantageView Release Release Notes. Migration Prerequisites Database Make sure the SQL Server database is set as case-insensitive. VantageView products cannot be installed on a database server that is case-sensitive. A default SQL Server installation is case-insensitive, which means that SQL Server does not differentiate between upperand 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. The database must be SQL Server 2005 or 2008 before migration. If you are migrating VantageView data and the new VantageView database will be on a different server than the existing database, then the SQL Server version of the new database must be the same as or later than the version of the current database. Back up the current database. Compuware recommends that you back up VantageView before migrating. The backup process includes the VantageView database and other VantageView data stored on the server. If you will be migrating VantageView data to a new server, then before you use the VantageView Data Utility, create a folder named Dev97 under the Migrate folder in the current VantageView installation directory. You can move the data manually, instead of using the VantageView Data Utility. 44

45 Chapter 4 Migrating VantageView 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 started and that its Startup Type property is set to Automatic. Service Packs for Companion Products Before migrating VantageView, check FrontLine ( for any service packs that may need to be installed for related products. For more information, see Installing Service Packs [p. 90]. Compatible Compuware APM Product Releases VantageView Release is compatible with specific releases of other Compuware APM products. If the following products are upgraded to at least the minimum supported release, you can migrate VantageView first, and upgrade the other products at your convenience. If you choose not to upgrade unsupported releases of other products, portions of VantageView may not work properly. Reporting and alerts will function correctly with Compuware APM products at the following release levels. Table 8. Supported Releases Compuware APM Product Server Monitoring [ServerVantage] Synthetic Monitoring [ClientVantage, Private Enterprise] ClientVantage (Passive) Network Monitoring [NetworkVantage] Java/.NET Monitoring Data Center Real User Monitoring [Vantage for Real User Monitoring] Supported Releases Release 11.5, 11.7, and 12.0 with latest service pack applied Release 11.7, 12.0, 12.1, and 12.2 with latest service pack applied Release 9.9 with latest service pack applied Release 10.0 with latest service pack applied Release 11.5 with latest service pack applied Release 11.5, 11.6, 11.7, 12.0, 12.1, and 12.2 with latest service pack applied 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 databases created in Microsoft SQL Server. After the VantageView migration, you must re-save all Synthetic Monitoring and Network Monitoring database connections, Network Monitoring Enterprise Managers, and Server Monitoring Control Server connections with the appropriate Alerts Server selected so that VantageView alerts will be properly displayed in VantageView. For more information, see Configuration [p. 69]. Migration Checklist Use this checklist to ensure that all tasks are completed to migrate VantageView successfully. 45

46 Chapter 4 Migrating VantageView Migrate VantageView before migrating other Compuware APM products. In most cases, as long as the companion Compuware APM products are a compatible release, you do not need to migrate them immediately after migrating VantageView. For more information, see Compatible Compuware APM Product Releases [p. 45]. CAUTION Do not uninstall the earlier VantageView release before verifying that the migration is complete and successful. If you do, you will lose saved reports and other VantageView configuration settings. Table 9. VantageView Migration Checklist Finished Steps Confirm that your current installation is a release that can be migrated to the new release, with service pack applied if necessary. For more information, see Installing or Migrating VantageView in the VantageView Release Release Notes. If necessary, apply the latest service pack to your present VantageView release. For more information, see Installing Service Packs [p. 90]. Review the system requirements to ensure that the hardware you are using is sufficient to run VantageView. This is especially important if you are also running other Compuware APM products. For more information, see System Requirements [p. 11]. Review the migration prerequisites. For more information, see Migration Prerequisites [p. 44]. Make sure the SQL Server database server is configured as case-insensitive. The VantageView database cannot be installed if SQL Server is set to case-sensitive. In SQL Server, this setting is called collation. If you are migrating the VantageView data and the database to a new server, make sure that you are migrating the VantageView database to the same version of SQL Server as the earlier release. For more information, see Migration Prerequisites [p. 44]. SQL Server 2000 is no longer supported. You must upgrade to SQL Server 2005 or SQL Server For more information, see Moving the SQL Server Database Between Platforms [p. 88]. Back up the current VantageView database and data files/folders. For more information, see Backing Up and Restoring VantageView [p. 85]. Make sure the SQL Server agent is configured to start automatically after the VantageView database has been migrated. Install a new VantageView environment on the target machine. For more information, see Migrating VantageView to the New Release [p. 48]. Migrate the data from the previous database. For more information, see VantageView Data Migration [p. 47]. 46

47 Chapter 4 Migrating VantageView Table 9. VantageView Migration Checklist (continued) Finished Steps Reconfigure the database authentication, as needed. If you created the VantageView database using Windows Authentication, enable Windows Authentication again after migration. For more information, see Configure Windows Authentication in Windows Server 2003 [p. 28] and Configure Windows Authentication in Windows Server 2008 [p. 31]. During VantageView migration, authentication based on SQL Server accounts is restored to the defaults. Any previously configured domain-based security settings must be reapplied. For more information, see Implementing Domain-based Database Security in VantageView [p. 60]. When VantageView is migrated successfully, reconnect the connections to the Compuware APM product databases. For more information, see Configure Database Connections [p. 59]. VantageView Data Migration To retain existing VantageView reports, do one of the following: Migrate data during installation of the new release. For more information, see Migrating VantageView to the New Release [p. 48]. Use the VantageView Data Utility to migrate prior release data to the Release 12.0 installation. 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 47

48 Chapter 4 Migrating VantageView Migrating VantageView to the New Release Before starting the migration procedure, review the prerequisites. For more information, see Migration Prerequisites [p. 44]. Follow the steps below to migrate VantageView to the new release. CAUTION Do not uninstall the earlier release of VantageView before migrating. If you do, you will lose saved 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 Solaris 4. Insert the disc into your computer's DVD drive and wait for the media browser to start. If the media browser does not run automatically, run the setup.exe application on the DVD to start the media browser manually. If you have downloaded the product, go to the equivalent folder in your downloaded copy and run the setup.exe application. 5. Select the Synthetic Monitoring tab, then click VantageView. The Operating System Updates window appears. The installation process runs an operating system (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. If SQL 2005 Backward Compatibility or Microsoft.NET Framework does not already exist on your system, it will be installed. During the installation, a message may be displayed that the IIS ASP extension is not enabled. Click OK. The IIS ASP extension is one of the web service extensions required for VantageView. For more information, see Server Prerequisites [p. 20]. 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 is enabled, when you click Next, a browser window opens automatically and directs the browser 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 agreed to the terms. 48

49 Chapter 4 Migrating VantageView 8. When the GNU Lesser General Public License Agreement window appears, click Yes once you have read and agreed to the terms. 9. When the Customer Information window appears, type your User Name and Company Name in the Customer Information window. Click Next. If prompted, select Yes, I want to restart my computer now. Upon reboot, the server automatically restarts the installation application. If the installation does not automatically restart, repeat the tasks performed previously. 10. Click Next in the Choose Destination Location window to accept the default installation location, or click Browse to change the location. The default installation path is C:\Program Files\Compuware\VantageView Click Next in the Choose Data Location window to accept the default data location, or click 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\VantageView However, it is common practice to install the data folder on a separate drive. CAUTION If your system does not meet the minimum hardware and system requirements, you may receive the warning: At least one Hardware or Software recommendation has failed. Click OK to view the details of the components that passed and failed. Some warnings require you to click Cancel to stop the installation process and upgrade your system to the minimum hardware and software requirements before continuing the installation. 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 the Available Web Sites menu, then, in the Virtual Directory Name field, type the name of the virtual directory and click Next. The virtual directory name must contain only letters, numbers, and hyphens. The default virtual directory name is Vantage. If you are installing a new release of VantageView where an earlier release was installed, this name may already be in use. If it is already in use, the installation prohibits you from using the same name. Choose a different name, such as Vantage In the Select Program Folder window, click Next to accept the default program folder for VantageView You can also select an existing program folder from the Existing Folders 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. 49

50 Chapter 4 Migrating VantageView If you have multiple instances of SQL Server on the same machine, make sure the instance name is entered as server_name\instance_name. If the full instance name does not appear in the list, you can type it in the field. b. Type the Database Name. The database name must contain only letters, numbers, and hyphens. The default database name is VantageViewDB. Since you are migrating, this name will likely already be in use. If it is already in use, the installation prohibits you from using the same name. Choose a different name, such as VantageViewDB117. c. Select Windows Authentication or SQL Authentication. Click Next. If selecting SQL Authentication, enter the proper user ID and password to create the database. If selecting Windows Authentication, you must ensure that the user which is currently logged onto the VantageView server has sysadmin rights on the SQL Server. d. The default installation path, database size, and log size are usually sufficient, but you can change them if needed. 15. The Migrate previous version? window appears if you are running the installation program on a machine where an earlier release of VantageView is installed. Select either: VantageView 12.0 Select this option to continue to migrate the earlier release to the new release. The installation copies the data to the SQL database. If you select this option, continue to Step 7 [p. 48]. Select 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 machine If 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 the location from which you want to migrate. If you select No a new empty SQL database is created for you to use with VantageView. Click Next. 50

51 Chapter 4 Migrating VantageView 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: Authentication You can use either Windows Authentication or SQL Authentication to migrate the database. If SQL Authentication (default) is enabled, enter the proper User ID and Password for the database. Or select Windows Authentication. Database Instance Select the VantageView database instance. When you run the VantageView Data Utility to migrate data from an earlier release, the Source tab of the Data Utility may be populated with the connection information for the previous release's database. If the Database Instance field of the Source tab contains localhost,1433, you must change that value: If you know the database instance, replace localhost,1433 with the actual instance name. Otherwise, enter (local), including the parentheses, as the database instance. Database Name If the database name is not already displayed, type the name of the database from the earlier VantageView release. By default, the VantageView database is named VantageViewDB. Login Enter the default login for the database if it does not appear automatically. Password Enter the password for the login if it does not appear automatically. Other Complete the following fields: Existing local path on Source SQL Server machine where database backup file is to be placed VantageView requires a valid local path on the SQL Server machine where the database backup will be temporarily placed. You cannot use a UNC path. If the path doesn't exist, you must create one. The temporary backup file will be removed when the migration process has completed. Current location of Source data and web-publish folders The source data folders can be local or remote. If the folder paths are not displayed, click Browse or enter a path to locate the source data and web-publish folders. By default, the location is Documents and Settings\All Users\Application Data\Compuware\VantageView. If the source folders reside on a remote machine, you can enter a valid UNC path. You may first need to authenticate to that location via Windows Explorer for the data utility to see this location as valid. 51

52 Chapter 4 Migrating VantageView Source Virtual Directory name By 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: Authentication You can use either Windows Authentication or SQL Authentication to migrate the database. If SQL Authentication (default) is enabled, enter the proper User ID and Password for the database. Or select Windows Authentication. Database Instance The database instance name. Database Name The database name. Login Specify the login for accessing the VantageView database. Password Enter the password for the SQL login. Other Complete the following field: Existing local path on Target SQL Server machine where database backup file is to be placed: Specify the local path on the target SQL Server machine for the database backup file. The 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 interrupt the installation. 19. Click Finish to close the InstallShield Wizard. Depending on your OS updates, you may be prompted to reboot your computer. What to Do Next Additional steps are required to complete the migration process. For more information, see Finishing the VantageView Installation [p. 55]. Verifying Migration Success Perform the following steps to confirm that migration to the new VantageView release was successful. 52

53 Chapter 4 Migrating VantageView 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 more information, see Configuration [p. 69]. After migration, you must retest the VantageView connection to the Network Monitoring Enterprise Manager. If you use Synthetic Monitoring, the Synthetic Monitoring Agent Manager must be Release 11.5 or later. 53

54 Chapter 4 Migrating VantageView 54

55 CHAPTER 5 Finishing the VantageView Installation This chapter describes the steps necessary for completing the VantageView installation: Register TeeChart7.ocx on the Client [p. 55] Configuring the VantageView Server [p. 56] Post-Migration Notes [p. 53] Verifying the Success of the VantageView Installation [p. 58] The steps below are necessary to complete the VantageView installation after the software is installed. Client machines On each client, to manually install the ActiveX charting component and register TeeChart7.ocx on the client machines. VantageView Server The following tasks are necessary to configure the VantageView server: Verify the data location file permissions for each user. For more information, see Verify Data Location File Permissions for Users [p. 56]. Register TeeChart7.ocx on the server machine. For more information, see Register TeeChart7.ocx on the Server [p. 57]. Verify the access for the Windows Everyone group. For more information, see Verify Access for Windows Everyone Group [p. 57]. Exclude files from anti-virus scanning on the VantageView server. For more information, see Exclude Files from Anti-Virus Scanning [p. 58]. Exclude files from anti-virus scanning on the database servers for other Compuware APM products. For more information, see Exclude Files from Anti-Virus Scanning on Compuware APM Products Database Servers [p. 58]. Register TeeChart7.ocx on the Client If you enabled the use of Client-side Charting ActiveX in Administration>VantageView>Reports>Default Settings, VantageView downloads the 55

56 Chapter 5 Finishing the VantageView Installation ActiveX.cab file and installs it on the client machine. If you choose not to install an ActiveX component, you may clear that option, and VantageView renders the charts on the web server. If you want to manually install the ActiveX charting component on client machines, use the following instructions. To manually register TeeChart7 on client machines: 1. On the VantageView Web Server, locate the file TeeChart7.ocx, located in the Windows System32 directory. 2. Copy the file to the client machine to which you want to install TeeChart7 and place it in the Windows System32 directory; for example, C:\WINXP\system32\. 3. On the client machine, register TeeChart7.ocx using the regsvr32 command. a. From the Windows Start menu, choose Run. b. In the Run field, type regsvr32 "path TeeChart7.ocx" Where path is the fully qualified path of TeeChart7.ocx. For example, regsvr32 "C:\WINXP\system32\TeeChart7.ocx". c. Click OK. A message notifies you that the registration process was successful. d. Click OK to close the message. 4. The file TeeChart7.ocx is now registered on the client machine. Configuring the VantageView Server Configuring the VantageView server involves the following tasks: Verifying the data location file permissions for the users. Registering TeeChart7.ocx on the server. Verifying Access for the Windows Everyone Group. Exclude Files from Anti-Virus Scanning. Exclude Files from Anti-Virus Scanning on Compuware APM Database Servers. Verify Data Location File Permissions for Users For users to successfully access VantageView, the administrator must set Microsoft Windows security permissions. During installation, you were prompted to choose a Data Location. All users who access VantageView must have appropriate permissions for this Data Location and all of its files and subdirectories. To verify data location file permissions for users: 1. Log on as Administrator to the server where VantageView is installed. 2. Using My Computer, navigate to the location specified for the Data Location during the VantageView installation. The default data installation path is C:\Documents and Settings\All User\Application Data\Compuware\VantageView

57 Chapter 5 Finishing the VantageView Installation 3. Right-click the VantageView 12.0 folder and choose Properties. 4. Click the Security tab. 5. Add the appropriate local user(s) or group(s) who require access to VantageView. 6. For each user and group, select the check boxes necessary to allow full permissions: Click the Advanced button. Select Reset permissions on all child objects and enable propagation of inheritable permissions. Click Yes to continue when warned about removing explicitly defined permissions. 7. Click OK. If you receive an error message regarding applying security settings, check to make sure you have ownership of the subfolders and files. To do this, repeat Step 3 [p. 57] and Step 4 [p. 57], click the Advanced button, and then click the Ownership tab. 8. Verify that all subfolders have the same permissions by clicking the Advanced button, highlighting the entry, and then clicking the View/Edit button. 9. In the Permission entry window, in the Apply onto list, select This folder, subfolders and files. Register TeeChart7.ocx on the Server The file TeeChart7.ocx is registered on the server during the installation of VantageView. Should you need to register TeeChart7.ocx on the server again, use the following procedure. To register TeeChart7.ocx on the server: 1. On the VantageView web server, locate the file TeeChart7.ocx, located in the Windows System32 directory. 2. From the Windows Start menu, choose Run. 3. In the Run field, type regsvr32 "path TeeChart7.ocx". Where path is the fully qualified path of TeeChart7.ocx. For example, regsvr32 "C:\WINXP\system32\TeeChart7.ocx". 4. Click OK. A message box appears, notifying you that the registration process was successful. 5. Click OK to close the message box. Teechart7.ocx is now registered on the server. Verify Access for Windows Everyone Group The Everyone Windows group on the VantageView web server must have explicit Execute access in the following folders. Do not assume these permissions are inherited correctly; you must check each folder. C: C:\Windows or \WinNT C:\Windows\System32 or C:\WinNT\System32 57

58 Chapter 5 Finishing the VantageView Installation Exclude Files from Anti-Virus Scanning The following files, folders (with all subfolders), and file types must be excluded from anti-virus scanning on the VantageView web server: Global.asa, global.asax, and Gweb.config. Entire VantageView Virtual Directory tree. C:\Windows\system32\Inetsrv. The default data installation path is C:\Documents and Settings\All Users\Application Data\Compuware\VantageView Exclude Files from Anti-Virus Scanning on Compuware APM Products Database Servers The following files, folders (with all subfolders), and file types should be excluded from anti-virus scanning on the database servers of all Compuware APM products: *.ldf *.mdf Verifying the Success of the VantageView Installation Perform the following tasks to verify that VantageView was installed or migrated successfully. Access VantageView To access VantageView from a client machine: 1. Open Internet Explorer. 2. In the Address field, type where servername is the name of the server on which VantageView is installed, and Vantage is the Virtual Directory Name specified during installation. To access VantageView from the VantageView web server, go to the Start menu and select Programs Compuware VantageView 12.0 VantageView. To display Business Definition tree selections, you must have the ASP.NET web server extension set to Allow. For more information, see Server Prerequisites [p. 20]. Configure Security Groups in VantageView A VantageView user is defined in two locations: within the VantageView database and in the Windows security system. By default, as new users access VantageView, each user is assigned 58

59 Chapter 5 Finishing the VantageView Installation Vantage access rights automatically. However, by modifying security settings in VantageView, you can restrict users to specific areas or specific functions within VantageView. For instructions on how to modify security settings, refer to the VantageView online help. Configure Database Connections VantageView creates reports from data collected by other Compuware APM products. Therefore, to create reports and display alerts, you must first connect to the databases for the other products in VantageView. For more information, see Configuration [p. 69]. When migrating from an earlier release, there are Test and Save requirements. For more information, see Post-Migration Notes [p. 53]. Test Manual Report Publishing To test report ing: 1. Create a VantageView report. See the VantageView online help for details. 2. Click the Publish icon in the upper-right corner of the report view. 3. Select Publish from the selection box. 4. Select the to option, and type your address or that of a known account. 5. Click Send. 6. Check the inbox of the account for successful delivery of the report. See VantageView Report Generator Logs for details, and make sure you followed all the pre- and post-installation instructions in this guide. If you continue to experience problems, contact APM Customer Support for assistance. For more information, see Customer Support Information [p. 8]. Installing the MySQL JDBC driver VantageView does not include the JDBC driver to connect to Java/.NET Monitoring databases stored in MySQL. If you plan to run J2EE reports on your Java/.NET Monitoring database, and the Java/.NET Monitoring database is stored in MySQL, you must add the MySQL Connector (JDBC) driver to VantageView. 1. Locate the MySQL driver on the system running the Java/.NET Monitoring Nucleus Server. Java/.NET Monitoring installation procedures instruct the user to install the MySQL JDBC driver in the VAInstall/jre/lib/ext directory. The file name of the MySQL driver is similar to mysql-connector-java-version-bin.jar, where version is the MySQL version of the driver. 2. Copy the MySQL JDBC driver to the installdrive:\program Files\Compuware\COS\server\cpwr\lib directory. 59

60 Chapter 5 Finishing the VantageView Installation Implementing Domain-based Database Security in VantageView By default, the VantageView web application accesses the VantageView database via the VantageViewUser SQL Server user account. Optionally, you can configure VantageView to access its database via a Windows domain account. Before You Begin To perform this procedure, you must have the following: Administrator access to the VantageView web server and the VantageView database server. A Windows-domain-based account to use for VantageView Web Application VantageView Database authentication. The domain account must be a member of the Windows Administrators security group. This account's password must be set to Never Expire. If the password expires, configuration settings need modification each time it changes, to match the account's new password. When a Windows domain account is used, the identity and credentials are securely passed via the database connection object. No user IDs or passwords are transmitted between the web application and the database. IMPORTANT Configuration steps are IIS version-specific, and some steps vary between IIS versions. The remaining configuration steps are VantageView release-specific. VantageView migrations will undo portions of this configuration. Many of the domain-based security settings must be re-applied after a migration. The following user-defined terms are used in the procedure: [Domain\Account] Domain-based account for VantageView Web Application VantageView Database authentication. [VvDatabase] VantageView database. [VvDatabaseServer] VantageView database server [VvWebSite] VantageView web-site [VvWebSiteServer] VantageView web-site server 60

61 Chapter 5 Finishing the VantageView Installation [VvRelease] VantageView release [VvDir] VantageView installation directory [COSDir] Compuware Open Server (COS) installation directory. Grant permission to [Domain\Account] on [VvDatabaseServer]. 1. From the Windows Start menu, open Control Panel Administrative Tools Local Security Policy. 2. Expand Local Policies, then click User Rights Assignment. 3. Double-click Log on as a service. The Log on as a service Properties dialog box appears. 4. Click Add User or Group. The Select Users, Computers, Service Accounts, or Groups dialog box appears. 5. In the Object names selection field, type [Domain\Account]. 6. Click OK to save the change and close the dialog box. The OK button becomes available when you enter text in the selection field. 7. Click OK to close the Log on as a service Properties dialog box, then close the Local Security Policy window. Leave the Administrative Tools window open. Add [Domain\Account] to the IIS_IUSRS group for [VvDatabaseServer]. In IIS 6.0, the group name is IIS_WPG. 8. Open Administrative Tools Manage Computer. 9. Expand System Tools Local Users and Groups, then click Groups. 10. Double-click IIS_IUSRS (IIS_WPG) to open the IIS_IUSRS Properties (IIS_WPG Properties) window, and make sure [Domain\Account] is a member if the group. If [Domain\Account] is not a member: a. Click Add to display the Select Users, Computers, Service Accounts, or Groups dialog box. b. In the Object names selection field, type [Domain\Account]. c. Click Check Names to validate the name, then click OK to save the change and close the dialog box. These buttons become available when you enter text in the selection field. d. Click OK to close the properties window. Leave the Administrative Tools window open. Grant permissions for [Domain\Account] in [VvDatabase] 11. Open SQL Server Management Studio. 12. Expand [VvDatabaseServer] Security Logins. 61

62 Chapter 5 Finishing the VantageView Installation 13. Verify that the [Domain\Account] login account exists. If it does not exist: a. Right-click Logins and select New Login. The Login - New window appears. b. For the Login name, enter [Domain\Account]. c. For the Default database, select [VvDatabase]. d. Click OK. 14. Assign the sysadmin role to the login account. a. Right-click [Domain\Account] and select Properties. The Login Properties window appears. b. In the left pane, select Server Roles. c. Select sysadmin as the server role. d. Click OK. 15. Select the security settings. a. Expand [VvDatabaseServer] Databases [VvDatabase] Security. b. Right-click Users and select New User. The Database User - New window appears. c. Enter Domain\Account as both the User name and the Login name. d. For the membership role, select Vantage_Admin database. e. Click OK. 16. Exit SQL Server Management Studio. 17. Grant permissions to [Domain\Account] in [VvWebSite], on [VvWebSiteServer]. a. Open a command prompt window and enter the following commands. Enter each command ([c:\]...) as one line. [c:\] iisreset /stop [c:\] cd C:\inetpub\AdminScripts [c:\] cscript adsutil.vbs set W3SVC/1/Root/[VvWebSite]/AspRunOnEndAnonymously FALSE b. After the commands are successfully executed, close the command prompt window. Change the services settings. 18. Open Administrative Tools Services. 19. Stop the VantageView [VvRelease] Service Controller service. 20. Confirm that the VantageView [VvRelease] Print/Publish and Compuware Open Server COS services are stopped. 21. Change the Log On setting for the following services: VantageView [VvRelease] Service Controller VantageView [VvRelease] Print/Publish Synthetic Monitoring Manager Vantage Notification Engine Vantage Rule Engine 62

63 Chapter 5 Finishing the VantageView Installation Compuware Open Server a. Right-click the service and select Properties to display the Properties dialog box. b. Select the Log On tab and click This account. c. In the fields, provide the [Domain\Account] name and the password. d. Click OK to save the change and close the Properties dialog box. Leave the Administrative Tools window open. Complete the instructions appropriate to your IIS version. If you have IIS 7, perform Step 22 [p. 63], then continue with Step 27 [p. 63] If you have IIS 8, perform Step 22 [p. 63], then continue with Step 31 [p. 64] 22. Open Administrative Tools Internet Information Services (IIS) Manager. IIS Change the Application Pools properties. a. Expand Application Pools, then right-click the Vantage[VvRelease] application pool and select Properties to display the Properties dialog box. b. Under Identity, select Configurable. c. In the fields, provide the [Domain\Account] name and the password. d. Click OK to save the change and close the Properties dialog box. 24. Change the Web Sites properties. a. Expand Web Sites Default Web Sites, then right-click [VvWebSite] and select Properties to display the Properties dialog box. b. Select the Virtual Directory tab and click Configuration. c. Select the Mappings tab, and in the Wildcard application maps section, click Insert. d. Click Browse, navigate to [VvDir]\bin\VvIisAuth.dll, and click Open. e. Surround the returned Executable value in double quotes. For example, "C:\Program Files\Compuware\VantageView". f. Clear the checkbox for the Verify that file exists option. g. Click OK until you have closed all dialog boxes and returned to the Internet Information Services (IIS) Manager window. 25. Add a new web service extension. a. In the IIS Manager window, right-click Web Service Extensions and select Add a new Web service extension. b. Select Set extension status to Allowed. c. In the Extension name field, type VvIisAuth[VvRelease]. d. Click Add. e. Click Browse, then navigate to [VvDir]\bin\VvIisAuth.dll, and click Open. f. Click OK until you have closed all dialog boxes, then close the Internet Information Services (IIS) Manager window. 26. Skip the IIS 7 and IIS 8 procedures, and continue with continue with Step 36 [p. 65]. IIS Change the Application Pools properties. 63

64 Chapter 5 Finishing the VantageView Installation a. Expand Application Pools, then right-click the Vantage[VvRelease] application pool and select Properties to display the Properties dialog box. b. Under Identity, select the Identity value, then click the [...] button. c. Select Custom account. d. In the fields, provide the [Domain\Account] name and the appropriate password. e. Click OK until you have closed all dialog boxes. 28. Define the connection. a. In the Connections screen, click [VvWebSiteServer]. b. In the IIS section of the content pane, double-click ISAPI and CGI Restrictions. c. Double-click the row with a Path value that ends with VVIISA~1.DLL. d. In the dialog box that opens, select and copy the ISAPI OR CGI PATH value. e. Click Cancel. f. In the Connections screen, expand Default Web Site and click [VvWebSite]. g. In the IIS section of the content pane, double-click Handler Mappings. h. In the Actions screen, select Add Wildcard Script Map to open the Add Wildcard dialog box. i. Paste the copied Path value into the Executable field. Replace the upper-case.dll with lower-case.dll. j. In the Name field, type VvIisAuth[VvRelease]. k. Click OK. 29. Close the Internet Information Services (IIS) Manager window. 30. Skip the IIS 8 procedure, and continue with continue with Step 36 [p. 65]. IIS Change the Application Pools properties. a. Expand Application Pools, then right-click the Vantage[VvRelease] application pool and select Advanced Settings. b. In the dialog box that opens, under Identity, select the Identity value, then click the [...] button. c. Select Custom account. d. In the fields, provide the [Domain\Account] name and the appropriate password. e. Click OK until you have closed all dialog boxes. 32. Define the connection. a. In the Connections screen, click [VvWebSiteServer]. b. In the IIS section of the content pane, double-click ISAPI and CGI Restrictions. c. Double-click the row with a Path value that ends with VVIISA~1.DLL. d. In the dialog box that opens, select and copy the ISAPI OR CGI PATH value. e. Click Cancel. f. In the Connections screen, expand Default Web Site and click [VvWebSite]. g. In the IIS section of the content pane, double-click Handler Mappings. h. In the Actions screen, select Add Wildcard Script Map to open the Add Wildcard dialog box. i. Paste the copied Path value into the Executable field. Replace the upper-case.dll with lower-case.dll. 64

65 Chapter 5 Finishing the VantageView Installation j. In the Name field, type VvIisAuth[VvRelease]. k. Click OK. 33. Edit the feature permissions. a. Under the Actions panel, select the Edit Feature Permissions action. b. Select all Read Scripts Execute, then click OK. 34. Make sure restrictions are disabled. a. In the Handler Mappings list, select VvIisAuth[VvRelease], then under the Actions panel, click Edit. If the Request Restrictions button is not available, click OK. If the Request Restrictions button is available, disable the restrictions. Clear the check box for Invoke handler only. Set Verbs to All. Set Access to None. b. Click OK to return all the way to the Handler Mappings list. 35. Close the Internet Information Services (IIS) Manager window. Edit the files [VvDir]\vv-options.xml and [COSDir]\server\cpwr\deploy\dmi.war\config\repository.properties. 36. Edit [VvDir]\vv-options.xml. a. Open the file into a text editor. b. Change <web-identity mode="impersonated" account=""/> to <web-identity mode="fixed" account="[domain\account]"/> c. Change <vvdb-connection vvdb-identity-mode="sql"> to <vvdb-connection vvdb-identity-mode="delegated"> d. Save and close the file. 37. Edit [COSDir]\server\cpwr\deploy\dmi.war\config\repository.properties. a. Open the file into a text editor. b. Change the JDBC_USER and JDBC_PASSWORD values to be null, as shown: JDBC_USER= JDBC_PASSWORD= c. Save and close the file, then exit the text editor. Restart IIS and the VantageView services. 38. Restart IIS. 65

66 Chapter 5 Finishing the VantageView Installation Open a command prompt window and execute the following command: [c:\] iisreset /start When the command is successfully executed, close the window. Restart IIS and the VantageView services. 39. Restart the services. a. Open Administrative Tools Services. b. Start VantageView [VvRelease] Service Controller. a. Confirm that the VantageView [VvRelease] Print/Publish and Compuware Open Server services also started. 40. Close Administrative Tools Services. Clear the Internet Explorer cache. 41. Open Internet Explorer. 42. Select Tools Internet Options. The General tab is displayed by default. 43. Under Browsing History, select Delete. The Delete Browsing History dialog box appears. 44. Select Temporary Internet files and Cookies. 45. Click Delete. 46. Click OK or Cancel to close the Internet Options dialog box. What to Do Next Verify that this procedure was performed successfully: 1. Open Internet Explorer and browse to [VvWebSite]. Make sure Internet Explorer is set to Compatibility View mode. The main VantageView page should appear without error. 2. Confirm that the User name displayed near the upper right corner is a user account, not [Domain\Account]. 3. Check the database connections. a. Open the Administration window. b. Open each existing point-product database connection definition, then click Save. c. Close the window. 4. Reset the Purge Settings. a. Open the Management window. b. Select Enterprise Rules Purge Settings. c. In the Purge Settings pane, click the Update button. d. Close the Management window. 66

67 Chapter 5 Finishing the VantageView Installation If a 404 Page Not Found error occurs or the User name is not a user account, review the first section of the procedure, Grant permission to [Domain\Account] on [VvDatabaseServer], and verify that all the settings are properly applied. 67

68 Chapter 5 Finishing the VantageView Installation 68

69 CHAPTER 6 Configuration VantageView provides a reporting portal for the Compuware APM suite of products. You can view the real-time status of clients, servers, and networks in a unified web interface. You can also view reports of end-to-end data. When you install VantageView, you must configure the connection between the web server machine where VantageView resides and the appropriate databases in order to obtain report data from other Compuware APM products. When you migrate VantageView, you might not need to configure the existing connections with other Compuware APM products. VantageView also uses a SQL database. This database stores report configurations, preferences, filters, alerts, and other reporting information. The VantageView database is configured during initial setup and cannot be reconfigured at runtime. You can enable data rollup when configuring the connection between the VantageView web server and the product database. Data rollup enables aggregation (or rollup) of data into product-specific summary levels, thereby improving performance of VantageView reports. See database configuration links above for specific information on enabling data rollup in individual products. For more information, see Data Rollup Settings [p. 83]. If you created a backup of a VantageView product database (Synthetic Monitoring, Network Monitoring, or Server Monitoring database) and attempt to add a connection to that database through a VantageView server that currently has a connection to the original product database, VantageView notifies you that a VantageViewconnection with that product ID already exists. VantageView does not allow the connection to be saved. Synthetic Monitoring Synthetic Monitoring produces diagnostic data that can be displayed in the VantageView interface. 69

70 Chapter 6 Configuration VantageView reports require that a connection exists between the web server machine where VantageView resides and the appropriate Synthetic Monitoring database where data is stored. The Alerts database is not an independent SQL database. The Alerts database consists of several tables in the VantageView database instance. This section contains the following topics: Configuring a New Synthetic Monitoring Database Connection [p. 70] Modifying an Existing Synthetic Monitoring Database Connection [p. 71] How the Rollup Database Works with Synthetic Monitoring [p. 72] Configuring a New Synthetic Monitoring Database Connection 1. From the Administration task pane, open the Client folder. Right-click Databases and select New Database. The Client Database Configuration page appears. If VantageView has been configured to use domain-based security, then the Authentication type option appears. Select either SQL Server Authentication or Windows Authentication. If Windows Authentication is selected, continue to Step 6 [p. 70]. 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. To test the connection, click Test. If the test was successful, a message appears verifying that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name and password, and try again. 7. This step applies only to Synthetic Monitoring Release 9.9: From the Current Event/Alert Server list, select a server to send events/alerts to the VantageView web server. To disable this option, select Do not send to VantageView. If you change any of the above information in SQL Server, modify the database connection and update this information. 70

71 Chapter 6 Configuration 8. The Enable Rollup check box is enabled by default. This allows Synthetic Monitoring data to be summarized as it is collected, and improves report performance. If you do not want to have the data summarized, de-select the Enable Rollup check box. For more information, see How the Rollup Database Works with Synthetic Monitoring [p. 72]. 9. Select the regional Time Zone to use as the basis for the summarized data. For more information, see Selecting a Time Zone for Data Rollup [p. 83]. 10. Select Working hours to segregate the data collected during user-specified hours, such as working hours. The default option is All hours (a 24-hour period from midnight to midnight). For more information, see Selecting Working Hours for Data Rollup [p. 84]. 11. Select the Summary Level for data rollup. The default option is Daily. For more information, see Selecting a Summary Level for Data Rollup [p. 84]. 12. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 13. Click Save. Modifying an Existing Synthetic Monitoring Database Connection 1. From the Administration task pane, expand Client Databases, right-click the name of the database you want to re-configure, and choose Modify. The Client Database Configuration page displays existing configuration parameters. If VantageView has been configured to use domain-based security, then the Authentication type option appears. Select either SQL Server Authentication or Windows Authentication. If Windows Authentication is selected, continue to Step 6 [p. 71]. 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. From the Current Event\Alert Server list, select a server to send alerts to the VantageView web server. To disable this option, select Do not send to VantageView. The port number for the Event\Alert server appears in the Current Event\Alert port box. 71

72 Chapter 6 Configuration If you change any of the above information in SQL Server, modify the database connection and update this information. 7. If you want Synthetic Monitoring data to be summarized as it is collected and demonstrate reported performance, click the Enable Rollup check box. If you do not wish to have the data summarized, deselect the Enable Rollup check box. For more information, see How the Rollup Database Works with Synthetic Monitoring [p. 72]. 8. Select the regional Time Zone to use as the basis for the summarized data. For more information, see Selecting a Time Zone for Data Rollup [p. 83]. 9. Select Working hours to segregate the data collected during user-specified hours, such as working hours. The default option is All hours (a 24-hour period from midnight to midnight). For more information, see Selecting Working Hours for Data Rollup [p. 84]. 10. Select the Summary Level for data rollup. The default option shows both Daily and Hourly. For more information, see Selecting a Summary Level for Data Rollup [p. 84]. 11. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 12. Click Save. How the Rollup Database Works with Synthetic Monitoring Synthetic Monitoring agents collect performance metrics, which are then imported into the Synthetic Monitoring database. Based on selections made during the Synthetic Monitoring database configuration, data may be aggregated into hourly and/or daily (24 hour) summary levels in order to optimize report performance. When configuring a report using the Synthetic Monitoring database, if the selected time range and filters applied do not allow the rollup tables to be used, the report defaults back to the detail tables. The default time period is from midnight to midnight; however, you can also select VantageView Business Hours. When the Daily summary level is used, the report appears in the time zone selected for the rollup. In all other circumstances, the report is presented in the time zone of the client browser. For more information, see Data Rollup Settings [p. 83]. 72

73 Network Monitoring The Network Monitoring reports in VantageView present data from either the Daily database or the Long Term database. This requires that you connect to the Network Monitoring Daily and Long Term databases. Additionally, you can configure a connection with the Network Monitoring Enterprise Manager to view near real-time reports such as the Enterprise Manager Collection Summary Report. For more information, see the VantageView online help. This section contains the following topics: Network Monitoring Daily Database Configuring a New Network Monitoring Daily Database Connection [p. 73] Modifying a Network Monitoring Daily Database Connection [p. 74] How the Rollup Database Works with Network Monitoring [p. 75] Chapter 6 Configuration Network Monitoring Long Term Database Configuring a Network Monitoring Long Term Database Connection [p. 76] Modifying a Network Monitoring Long Term Database Connection [p. 76] Network Monitoring Daily Databases To create Network Monitoring reports, you must first configure the connection between the web server machine where VantageView resides and the appropriate Network Monitoring Daily database where data is stored. The Alerts database is not an independent SQL Server database. This database consists of several tables in the VantageView database instance. The following topics provide an overview of Network Monitoring Daily database connections: Configuring a New Network Monitoring Daily Database Connection [p. 73] Modifying a Network Monitoring Daily Database Connection [p. 74] Configuring a New Network Monitoring Daily Database Connection To configure a new Network Monitoring Daily database connection: 1. Display the Network Daily Database Configuration page. In the Administration task pane, expand Network. Right-click Daily Databases and select New Database. If VantageView has been configured to use domain-based security, the Authentication type option appears. Select either SQL Server Authentication or Windows Authentication. If Windows Authentication is selected, continue to Step 6 [p. 74]. 73

74 Chapter 6 Configuration 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 7. From the Current Event/Alert server list, select a server to send events/alerts to the VantageView web server. To disable this option, select Do not send to VantageView. 8. If you want Network Monitoring data to be summarized as it is collected, click the Enable Rollup option. If you do not wish to have the data summarized, deselect the Enable Rollup option. For more information, see How the Rollup Database Works with Network Monitoring [p. 75]. 9. Select the regional Time Zone to use as the basis for the summarized data. For more information, see Selecting a Time Zone for Data Rollup [p. 83]. 10. Select Working hours to segregate the data collected during user-specified hours, such as working hours. The default option is All hours (a 24-hour period from midnight to midnight). For more information, see Selecting Working Hours for Data Rollup [p. 84]. 11. Click Save. Modifying a Network Monitoring Daily Database Connection To modify an existing Network Daily database connection: 1. Display the Network Daily Database Configuration pane for the connection. In the Administration task pane, expand Network Daily Databases, right-click the name of the database you want to reconfigure, and choose Modify. If VantageView has been configured to use domain-based security, then the Authentication type option appears. Select either SQL Server Authentication or Windows Authentication. If Windows Authentication is selected, continue to Step 6 [p. 75]. 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 74

75 Chapter 6 Configuration 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. From the Current Event\Alert Server list, select a server to send alerts to the VantageView Web server. To disable this option, select Do not send to VantageView. The port number for the Event\Alert server appears in the Current Event\Alert port box. If you change any of the above information in SQL Server, you must modify the database connection and update this information. 7. If you want VantageView data to be summarized as it is collected, click the Enable Rollup check box. If you do not wish to have the data summarized, deselect the Enable Rollup check box. For more information, see How the Rollup Database Works with Network Monitoring [p. 75]. From the Time Zone list, select a time zone in which you want the data aggregated. For more information, see Selecting a Time Zone for Data Rollup [p. 83]. Select a Working hours option for the amount of time you want data to be aggregated. The default option is All hours (a 24-hour period from midnight to midnight). For more information, see Selecting Working Hours for Data Rollup [p. 84]. 8. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 9. Click Save. How the Rollup Database Works with Network Monitoring In the Network Monitoring collection environment, the Network Monitoring agent takes distinct statistics for each day and rolls them up into a single summarized statistic. Based on selections made during the Network Monitoring Daily database configuration, data may be aggregated into daily summary levels in order to optimize report performance. The summaries vary, depending on the type of statistic gathered. When configuring a report using the Network Monitoring Daily database, if the selected time range and filters applied do not allow the rollup tables to be used, the report defaults back to the detail tables. This may occur if the job is still running, or if you have configured a report for less than a 24-hour time period. The default time period is from midnight to midnight; however, you can also select VantageView Business Hours. 75

76 Chapter 6 Configuration Network Monitoring Long Term Databases To create VantageView reports, you must first configure the connection between the web server machine where VantageView resides and the appropriate Network Monitoring Long Term database where data is stored. The Alerts database is not an independent SQL database. This database consists of several tables in the VantageView database instance. The following topics provide an overview of Network Monitoring Long Term database connections: Configuring a Network Monitoring Long Term Database Connection [p. 76] Modifying a Network Monitoring Long Term Database Connection [p. 76] Configuring a Network Monitoring Long Term Database Connection To configure a new Network Monitoring Long Term Database connection: 1. From the Administration task pane, click Network. Right-click Long Term Databases and select New Database. The Network Long Term Database Configuration page appears. If VantageView has been configured to use domain-based security, then the Authentication type option appears. Select either SQL Server Authentication or Windows Authentication. If Windows Authentication is selected, continue to Step 6 [p. 76]. 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 7. Click Save. Modifying a Network Monitoring Long Term Database Connection To modify an existing Network Monitoring Long Term database connection: 76

77 Chapter 6 Configuration 1. From the Administration task pane, expand Network Long Term Databases, right-click the name of the database you want to re-configure, and choose Modify. The Network Long Term Database Configuration page appears with existing configuration parameters. If VantageView has been configured to use domain-based security, then the Authentication type option appears. Select either SQL Server Authentication or Windows Authentication. If Windows Authentication is selected, continue to Step 6 [p. 77]. 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 7. Click Save. Server Monitoring VantageView can display data from the Server Monitoring Control Server and the Server Monitoring Historical Database. These reports show the alerts that have been triggered based on optional filters for a specific time period or monitored component. This section includes the following information: Server Monitoring Control Servers Server Monitoring Control Servers [p. 77] Configuring a New Control Server [p. 78] Modifying an Existing Control Server [p. 79] Server Monitoring Historical Databases Configuring a New Historical Database [p. 80] Modifying an Existing Historical Database [p. 80] Server Monitoring Control Servers To create VantageView reports, you must first configure the connection between the web server machine where VantageView resides and the appropriate Server Monitoring Control Server. When you establish a connection to a Control Server, then you can use this connection to collect data for Alerts, Monitoring, and Reporting. 77

78 Chapter 6 Configuration The Alerts database is not an independent SQL database. This Alerts database consists of several tables in the VantageView database instance. From the Control Server Configuration page you can perform the following tasks: Configuring a New Control Server [p. 78] Modifying an Existing Control Server [p. 79] Follow these guidelines for configuring Server Monitoring Control Server connections: For Server Monitoring to automatically identify new or removed agents for all Server Monitoring Control Server connections, the VantageView Report Generator service must be running. If the service is not running, you must manually re-save the Server Monitoring Control Server connection. If you have used the Agent Console to add or remove an agent station from the database after you have set up the initial database configuration, you may need to re-save the database configuration if the change does not appear in the list of Available agent stations on the report configuration page. If a previously existing agent station no longer exists when the database is re-saved, that agent station is automatically removed from any server group configuration (public or personal) in which it previously existed. Configuring a New Control Server To configure a new Server Monitoring Control Server: 1. From the Administration task pane, expand Server. Right-click Control Servers and choose New Control Server. The Control Server Configuration page appears. If VantageView has been configured to use domain-based security, then the Authentication type option appears. Select either SQL Server Authentication or Windows Authentication. If Windows Authentication is selected, continue to Step 6 [p. 78]. 2. In the Control server name box, type the name of the Server Monitoring Control Server. 3. In the Control server port box, type the port number of the Server Monitoring Control Server (the default is 3009). 4. From the Current Event/Alert server list, select a server to send events/alerts to the VantageView web server. To disable this option, select Do not send to VantageView. If you change any of the above information in SQL Server, you must modify the database connection and update this information. 5. In the Current Event\Alert port box, type the port number of the server. 6. To test the connection, click Test. 78

79 Chapter 6 Configuration If the test was successful, you receive a message verifying that the connection test was successfully completed. The Database information associated with the Control Server appears. If the test was not successful, check your Control Server name and Control Server port. 7. Click Save. Modifying an Existing Control Server To modify an existing Server Monitoring Control Server: 1. From the Administration task pane, expand Server Control Servers. Right-click the name of the control server you want to re-configure, and choose Modify. The Control Server Configuration page appears with existing configuration parameters. 2. In the Control server name box, type the name of the Server Monitoring Control Server (if you want to change this information). 3. In the Control server port box, type the port number of the Server Monitoring Control Server (the default is 3009) (if you want to change this information). 4. The Database server instance box displays the name of the database server connected to the Control Server. 5. The Database name box displays the name of the database connected to the Control Server. 6. The Database user ID box displays the database user ID. 7. The Database password box displays the database password. 8. The Database Type box displays the database type. 9. The Database Version box displays the database version number. 10. The Current Event\Alert Server box displays the VantageView server where alerts for the selected Control Server are sent. Select a Control Server from the list to send alerts to the VantageView web server. 11. The Current Event/Alert port box displays the port number of the server. If you change any of the above information in SQL Server, you must modify the Control Server connection and update this information. 12. To test the connection, click Test. If the test was successful, you receive a message verifying that the connection test was successfully completed. The Database information associated with the Control Server appears. If the test was not successful, check your Control Server name and Control Server port. 13. Click Save. Server Monitoring Historical Databases To create VantageView reports, you must first configure the connection between the web server machine where VantageView resides and the appropriate Server Monitoring historical database 79

80 Chapter 6 Configuration where data is stored. When you establish a connection to a Control Server, then you can use this connection to collect data for Alerts, Monitoring, and Management views. The Alerts database is not an independent SQL database. This database consists of several tables in the VantageView database instance. From this page, you can perform the following tasks: Configuring a New Historical Database [p. 80] Modifying an Existing Historical Database [p. 80] Configuring a New Historical Database To configure a new Server Historical Database: 1. From the Administration tree, click Server. Right-click Historical Databases and choose New Database. The Historical Database Configuration page appears. 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 7. Click Save. If you have used the Agent Console to add or remove an agent station from the database after you have set up the initial database configuration, you may need to re-save the database configuration if the change does not appear in the list of Available agent stations on the report configuration page. If a previously existing agent station no longer exists when the database is re-saved, that agent station is automatically removed from any server group configuration (public or personal) in which it previously existed. Modifying an Existing Historical Database To modify an existing Server Historical Database: 1. From the Administration tree, expand Server Historical Databases and right-click the name of the database you want to reconfigure and choose Modify. 80

81 Chapter 6 Configuration The Historical Database Configuration page appears with existing configuration parameters. 2. In the Database server instance box, type the name of the SQL Server instance containing the database (if you want to change this information). 3. In the Database name box, type the name of the database to point to for the product (if you want to change this information). 4. In the Login name box, type the SQL Server user ID. 5. In the Password box, type the password for the user of the SQL Server database. 6. To test the connection, click Test. If the test was successful, a message verifies that the connection test was successfully completed. The Database Type and the Database Version appear. If the test was not successful, check your database names, login name, and password; then try again. 7. Click Save. If you change any of the database information in SQL Server, you must modify the database connection and update this information. If you have used the Agent Console to add or remove an agent station from the database after you have set up the initial database configuration, you may need to re-save the database configuration if the change does not appear in the list of Available agent stations on the report configuration page. If a previously existing agent station no longer exists when the database is re-saved, that agent station is automatically removed from any server group configuration (public or personal) in which it previously existed. If you need to change this historical connection to a Control Server connection, delete the historical connection and add it as a new Control Server connection. Central Analysis Server The Central Analysis Server (CAS) component of Data Center Real User Monitoring provides real-time access to information about performance and usage of key enterprise applications. It monitors individual users of your business applications, with the purpose of identifying when and where problems occur and how to address them. Unlike some Compuware APM products for which VantageView generates reports from the data in the product s database, CAS reports that are displayed in VantageView are run on the CAS Report Data Server. The Report Data Servers page lets you configure CAS report servers for use as data sources. After you have configured the location of the CAS report server, you can view the CAS interface within the VantageView content pane through the Reports menu and use CAS as a component when configuring a custom report through the Data Mining Interface (DMI). Add the Central Analysis Server information by adding the IP or name of the server, the TCP port (80 by default) and user login information for CAS. Add the Advanced Diagnostics Server 81

82 Chapter 6 Configuration information by adding the IP or name of the server, the TCP port (81 by default) and user login information for the Advanced Diagnostics Server application. For more information about DCRUM components, refer to the documentation available in FrontLine. The following sections contain information about the Central Analysis Server: Accessing the CAS Report Data Servers Page [p. 82] Adding Report Data Servers [p. 82] Modifying Report Data Servers [p. 82] Deleting Report Data Servers [p. 83] Accessing the CAS Report Data Servers Page 1. From the Administration tree, open the Central Analysis Server folder. 2. Click the Servers name. The Report Data Servers page appears. Use this page to add report data servers and to select existing report data servers that you want to modify or delete. If you do not have Administrator privileges, you do not have access to Administration from the VantageView menu. Adding Report Data Servers To add a report data server: 1. From the Administration tree, open the Vantage Analysis Server folder, then click the Servers name. The Report Data Servers page appears. 2. Click Add. The Add Report Data Server page appears. 3. In the Server name/ip address box, type the unique numeric IP address separated by periods (e.g., ). 4. In the Server label box, type the name under which the server is to appear as a data source in DMI and on reports. 5. In the User login box, type the user ID required to access the CAS server. 6. In the User password box, type the password associated with the user ID. 7. In the Retype password box, retype the user password to confirm. 8. Click OK. Modifying Report Data Servers To modify a report data server: 82

83 Chapter 6 Configuration 1. From the Administration tree, open the Vantage Analysis Server folder, then click the Servers name. The Report Data Servers page appears. 2. Click the check box associated with the server you want to modify. 3. Click Modify. The Add Report Data Server page displays. 4. Change the information you want, and then click OK. Deleting Report Data Servers To delete a report data server: 1. From the Administration tree, open the Vantage Analysis Server folder, the click the Servers name. The Report Data Servers page appears. 2. Click the check box associated with the server(s) you want to delete. To select all servers, click Select All. To clear all selected servers, click Deselect All. 3. Click Delete. A confirmation message appears. Click OK to delete the selected server(s); click Cancel to ignore the action. Data Rollup Settings VantageView products collect large amounts of data. At times, the amount of data collected may affect the performance of VantageView reports. Administrators may enable the use of rollup tables and select a rollup time frame when configuring database connections. Data rollup allows information collected to be aggregated into summary levels in order to optimize report performance. Based on selections made during the database configuration, data in the Synthetic Monitoring database and the Network Monitoring Daily database may be rolled up, or aggregated, into summary levels to optimize report performance. The following topics provide an overview of data rollup settings: Selecting a Time Zone for Data Rollup [p. 83] Selecting Working Hours for Data Rollup [p. 84] Selecting a Summary Level for Data Rollup [p. 84] Selecting a Time Zone for Data Rollup To select a time zone for data rollup: 1. Configure a connection to the desired database. For more information, see Configuration [p. 69]. 2. From the Time Zone list, select the Regional Time Zone in which you want the data to be aggregated. 3. Click Save. 83

84 Chapter 6 Configuration If the client browser time zone is different from the time zone selected for the rollup data, you must override the time zone from the report configuration page. Ensuring that the time zone matches the database that invokes the rollup tables results in improved performance. If you change the time zone after the report has been defined and saved, the time zone for the new rollup begins from that point in time with the new parameters, and does not roll up historical data. Selecting Working Hours for Data Rollup To select working hours for data rollup: 1. Configure a connection to the desired database. For more information, see Configuration [p. 69]. 2. Click All hours to select or deselect the option to display data in a single row for a 24-hour period, from midnight to midnight. This is the default option. 3. Click From xxxx to xxxx to select specific start and stop times for a working hours time range. Data will be displayed in two rows: one for the working hours time range and one for the non-working hours time range. 4. Click Save. Selecting a Summary Level for Data Rollup VantageView allows you to select a summary level for data rollup for optimized performance of your VantageView reports. 1. Configure a connection to the desired database. For more information, see Configuration [p. 69]. 2. Enable the Daily check box to select or deselect the option to summarize data for a 24-hour period, from midnight to midnight. 3. Enable the Hourly check box to summarize data by one-hour intervals. If Data Rollup is enabled, you must select at least one Summary Level option. Network Monitoring supports only the daily summary level. 84

85 CHAPTER 7 Maintenance This chapter provides information for maintaining VantageView: Backing Up and Restoring VantageView [p. 85] Moving or Copying VantageView Data to a New Web Server [p. 86] Pointing VantageView to a Different SQL Server [p. 86] Pointing VantageView to a Different Virtual Directory [p. 87] Verifying Compuware Open Server Connection Settings [p. 87] Moving the SQL Server Database Between Platforms [p. 88] Installing Service Packs [p. 90] Uninstalling VantageView [p. 91] Backing Up and Restoring VantageView It is recommended that you back up VantageView before migration and as a part of a regular backup routine. The backup process includes backing up your VantageView SQL Server database and other VantageView data stored on the server. The frequency of your backup depends on the amount of activity in the database. The more activity, the higher the frequency (once or twice daily); the less activity, the lower the frequency (biweekly, weekly, or monthly). CAUTION The backup that you perform includes a database backup of the VantageView database and a file backup of the VantageView data directory. To perform the backup (and any subsequent restoration), you can use the Microsoft SQL utility found in Enterprise Manager, Microsoft SQL Server Management Studio, or a third-party database utility of your choice. See the Microsoft's online help (or the third-party database utility s online help) for more details. 85

86 Chapter 7 Maintenance For the other products such as Synthetic Monitoring, Network Monitoring, or Server Monitoring you must perform a separate backup for each individual database associated with each product. The SQL Server database backup saves the contents of the VantageView database and VantageView configuration settings, including: Data Database connections User IDs (includes User Templates and User Configuration settings) Published reports (and report groups) Published monitoring views Server groups Filters Business Objects and Groups Alerts Console configuration The VantageView database is located in the folder specified during the VantageView installation. The default data installation path is C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data. You must back up other stored data located in the user-defined installation directory, as well as all of its subfolders. The default installation directory is C:\Documents and Settings\All Users\Application Data\Compuware\VantageView It is crucial to the restoration process that you back up everything in the folder and all of its subfolders. Moving or Copying VantageView Data to a New Web Server VantageView stores information in file system files on the VantageView web server. You can migrate VantageView information (data, logs, web-publish, web-temp, etc.) to a new server(for example, because you upgraded your hardware), regardless of whether the earlier VantageView release exists on the local machine. For more information, refer to the online help for the VantageView Data Utility. Pointing VantageView to a Different SQL Server If you have relocated your VantageView database to a different SQL Server machine, you can point VantageView to the new database location. 86

87 Chapter 7 Maintenance If you are migrating VantageView data and the new VantageView database will be on a different server than the existing database, make sure that the SQL Server version of the new server is the same as or later than the SQL Server in the current location. 1. From the Start menu, click Programs Compuware VantageView 12.0, and select VantageView Data Utility. The VantageView Data Utility window appears. 2. From the Select Option window, choose Point VantageView to a different SQL Server. 3. Click Next. The Current area is populated with the current Server Name and Database Name. In the Target area, select a valid Server Name and Database Name that identifies the new location to which the data is to be copied. 4. Click Next. The Summary window appears. Click Proceed. The data is copied to the new location. 5. When finished, click View Log to view any warnings or to read post-installation configuration requirements, or click OK. Pointing VantageView to a Different Virtual Directory To point VantageView to a different virtual directory: IMPORTANT Before running this procedure, you must first rename the original virtual directory in Internet Information Services (IIS) Manager. 1. From the Start menu, select Programs Compuware VantageView 12.0 and select VantageView Data Utility. The VantageView Data Utility window opens. 2. Select the option to Point VantageView to a different virtual directory. 3. Click Next. The window refreshes with the name of the current VantageView virtual directory. Type the new virtual directory name in the text box. 4. Click Next. The Summary window appears. Click Proceed. All VantageView references to the Virtual Directory name are updated. 5. When finished, click Exit to complete the installation. 6. Verify the Compuware Open Server settings, as described in the next section. Verifying Compuware Open Server Connection Settings After pointing VantageView to a different SQL Server instance, you should verify the connection settings for the Compuware Open Server (COS) 1. Locate the file repository.properties in the COS installation. The default location is C:\Program Files\Compuware\COS\server\cpwr\deploy\dmi.war\config\repository.properties. 2. Use a text editor to open the COS file repository.properties. By default, this file is located in C:\Program 87

88 Chapter 7 Maintenance Files\Compuware\COS\server\cpwr\deploy\dmi.war\config\repository.properties. The file s content will be similar to the following example: JDBC_DRIVER=net.sourceforge.jtds.jdbc.Driver JDBC_URL=jdbc:jtds:sqlserver://myserver:1433/VantageViewDB;tds=8.0;lastupdatecount=true; JDBC_USER=VantageView JDBC_PASSWORD=VantageViewPass The line that begins with JDBC_URL tells the COS service where to find the VantageView database. The general form of this line is: JDBC_URL=jdbc:jtds:sqlserver://SERVERNAME:PORT/VVDBNAME;tds=8.0;lastupdatecount=true; 3. In the JDBC_URL line, substitute the network name of your database server for SERVERNAME, the port number of the database instance for PORT, and the VantageView database name for VVDBNAME. If your VantageView database instance is located on the VantageView web server, then replace SERVERNAME with localhost. Otherwise, replace SERVERNAME with the network name or IP address of the SQL Server instance. If your database instance is using the default SQL Server port number, then replace PORT with Otherwise, determine your port number from your SQL Server configuration, and use that value for PORT. Replace VVDBNAME with the name of your VantageView database on the database server. A default installation of VantageView uses VantageViewDB for the database name. If you only changed the server name of your database server, then it is likely that your VantageView database name has not changed. 4. If your database is located in a SQL Server named instance, then append the following additional text to the end of the entire JDBC_URL line, replacing INSTANCENAME with the name of your SQL Server named instance. instance=instancename 5. Save the file and exit the text editor. 6. Restart the Windows service named Compuware Open Server. Moving the SQL Server Database Between Platforms If you move the SQL Server database between platforms, you must also update the VantageView database: 1. Back up the VantageView database in SQL Server. 2. Move the backup file to the machine containing the new SQL Server instance. 3. Restore the backup into the new SQL Server. 4. Set the compatibility level to 90. a. In SQL Server Management Studio (SSMS), expand the SQL Server 2005 instance. b. Expand Databases. c. Right-click the database restored in Step 3 [p. 88] and select Properties. 88

89 Chapter 7 Maintenance d. In the Select a page section of the Database Properties dialog box, click Options. e. From the Compatibility level list, select SQL Server 2005 (90). f. Click OK to save the change and close the dialog box. 5. Create the VantageView login IDs. For this step, you need access to the VantageView installation package or the installation directory of the VantageView Data Utility. If you use the installation package, it should be the same release level as the latest service pack that has been applied to VantageView. a. In SSMS, select File Open File. b. In the Open File dialog box, navigate to the SQL2005 directory of the VantageView Data Utility; the default location is C:\Program Files\Common Files\Compuware\DBInstall\SQLFiles\VantageViewN\sql2005, where N is the release number. c. Select the file Create-VvDb-login.sql. d. Make sure the VantageView database is selected in the available databases list. e. Select Edit Find and Replace Quick Replace. f. Replace all occurrences of #DATABASE# with your VantageView database name. Not every script has these strings to replace. g. To execute the script, select Query Execute. 6. Repeat Step 5 [p. 89] for the following files: Create-VvmDb-login.sql Create-VantageAlerts-login.sql create-maint-dependant-sp.sql Create-Nv-DataSync-SP.sql (if present) 7. Test the connection with the VantageView login ID. a. Open a new query window. b. Make sure the VantageView database is selected in the available databases list. c. Right-click on the query window background. d. Select Connection Change connection. e. In the Connection to Database Engine dialog box, select SQL Server Authentication; enter the login ID VantageView and the VantageView password; the default password is VantageViewPass. f. Click Connect. g. Enter a query and execute it; for example Select * from configuration 8. Repeat Step 7 [p. 89] for these login IDs: CommonAlertsSubscriber default password UncommonlyGoodData 89

90 Chapter 7 Maintenance VVReader default password VPassV_016 (this password cannot be changed). VantageAlerts password strelaegatnav (this password cannot be changed). 9. If you have trouble testing any login ID in Step 7 [p. 89] or Step 8 [p. 89], do the following: a. Open a query window and connect using a login ID with system administrator privileges. b. Make sure the VantageView database is selected in the Available Databases list. c. Execute the following query for the login ID. This SQL Server procedure associates a database user name to a SQL Server login ID. In the query, replace SQL_LOGIN with the SQL Server login ID, and replace DB_USER with the VantageView database user to be associated to the login ID. By default, VantageView database user names are the same as the associated login IDs. 10. Stop IIS. sp_change_users_login Update_One, DB_USER, SQL_LOGIN 11. Use the Services Controller to stop all VantageView services. 12. Make a backup copy of the file vv-options.xml. The default location is C:\Program Files\Compuware\VantageView x.x, where x.x is the current release. 13. Edit the file vv-options.xml to point to the new server and database. 14. On the VantageView machine, edit the ODBC System Data source VantageAlerts to point to the new server and database. 15. Verify the COS connection. In the file C:\Program Files\Compuware\COS\server\cpwr\deploy\dmi.war\config\repository.properties, find the line that begins with JDBC_URL=. Verify the SQL Server name or IP address. The server name could be followed by the port number (i.e. <servername>:<port>) if the database instance is in use. Make sure the port number is correct. Verify the database name. The following example code includes values for JDBC_URL. JDBC_DRIVER=net.sourceforge.jtds.jdbc.Driver JDBC_URL=jdbc:jtds:sqlserver:// /VantageViewDB_154;appName=Vv 12.0-DMI;tds=8.0; lastupdatecount=true JDBC_USER=VantageView JDBC_PASSWORD=VantageViewPass 16. Start IIS. 17. Use the Services Controller to start all VantageView services. Installing Service Packs Between major releases, Compuware provides product fixes in the form of service packs. Service packs are available from the Compuware Customer Support website at For more information, see Customer Support Information [p. 8]. 90

91 Chapter 7 Maintenance Uninstalling VantageView This section describes how to uninstall VantageView from a Windows web server. The removal process may take several minutes. Avoid interrupting this process so that it can completely remove VantageView and all of its components. CAUTION Do not uninstall VantageView without first discussing the issue with a Compuware Customer Support representative unless you are uninstalling subsequent to a successful migration. Uninstalling VantageView in an effort to fix an installation problem may result in loss of reports and other VantageView settings. Uninstalling VantageView also uninstalls the Synthetic Monitoring Manager, which is needed for Synthetic Monitoring. If, after migrating VantageView to a new release, you choose to uninstall the new release, the earlier release of VantageView will no longer function. If you removed an earlier release of VantageView after migrating to a new release, and are now experiencing problems with the new release, do not uninstall the new release. Contact Customer Support. For more information, see Customer Support Information [p. 8]. 1. From the Start menu, select Settings Control Panel and click Add/Remove Programs. 2. Under Currently installed programs, click Compuware VantageView x.x (where x.x represents the release number). 3. Click the Change/Remove button. 4. Select the Remove option, and then click Next. 5. Click OK to confirm that you want to remove the application. 6. Select the server and database you want to remove, and click Next. Optionally, if you have already deleted or plan to delete the VantageView database using other utilities, you may click the Skip button to instruct the wizard to bypass deleting it. If you click the Skip button, the wizard removes all of the VantageView components but does not attempt to delete the VantageView database. 7. Click OK to acknowledge that IIS is to be stopped. Wait until IIS is stopped; this may take a moment. 8. Click Finish to close the InstallShield Wizard. You may be prompted to restart the machine. 9. Close the Add/Remove Programs window. 91

92 Chapter 7 Maintenance 92

93 Index Index 64-bit operating system, installing on 42 A ActiveX charting component 55, 57 client 55 server 57 anti-virus software 19, 58 B backup 85 browser supported versions 14 C Central Analysis Server adding a report data server 82 deleting a report data server 83 modifying a report data server 82 charting component 55, 57 client 55 server 57 checklists 20, 37, 45 installation 37 installation prerequisites 20 migration 45 client machine system requirements 14 Compuware Open Server connections 87 configuration 25 32, 53, 58, 70 71, 73, 76, 78, 80, 82 after migration 53 CAS report data server 82 IIS 25, 29 Windows Server Windows Server configuration (continued) Internet Explorer Enhanced Security 26, 30 Windows Server Windows Server Network Monitoring 73, 76 Daily database connection 73 Long Term database connection 76 security groups 58 Server Monitoring database connection 80 Server MonitoringControl Server connection 78 SMTP 28, 32 Windows Server Windows Server SNMP 29, 32 Windows Server Windows Server Synthetic Monitoring database connection web server extensions 26, 30 Windows Server Windows Server WebDAV 27, 31 Windows Server Windows Server Windows Authentication 28, 31 Windows Server Windows Server Windows Server Windows Server contact information 8 Control Server configuring connection 78 modifying connection 79 Customer Support

94 Index Customer Support (continued) information to provide 9 D data rollup selecting summary level 84 selecting time zone 83 selecting working hours 84 database 13, 19, 44, 53, 70 76, 79 80, 85 backup 85 configuring connections after migration 53 installation restrictions 19 migration prerequisites 44 Network Monitoring Daily database connection 73 Long Term database connection 76 modifying Daily database connection 74 modifying Long Term database connection 76 rollup 75 Server Monitoring configuring connection 80 modifying connection 80 Synthetic Monitoring configuring connection 70 modifying connection 71 rollup 72 system requirements 13 domain-based security 60 G global.asa 19, 58 I IIS IIS_IUSRS IIS installation 25, 29 Windows Server Windows Server installation 19 20, 32 33, 37 38, 42, bit operating system 42 checklist 37 MySQL JDBC driver 59 prerequisites 20, checklist 20 database 32 product suite 33 server 20 procedure 38 installation (continued) restrictions 19 integration 76 77, 79, 81 Central Analysis Server 81 Network Monitoring Long Term database 76 Server Monitoring Control Server 77 Server Monitoring database 79 Internet Explorer Enhanced Security 26, 30 Windows Server Windows Server M migrating VantageView 32, 43 45, 47 48, checklist 45 database connections 53 database prerequisites 32 overview 43 prerequisites 44 procedure 48 report data 47 verifying migration success 52 modifying 79 80, 82 Central Analysis Server report data server 82 Server Monitoring Control Server connection 79 Server Monitoring database connection 80 N Network Monitoring 73 74, 76 configuring Daily database connection 73 configuring Long Term database connection 76 modifying Daily database connection 74 modifying Long Term database connection 76 O online support site 8 opening VantageView 58 operating system supported versions 11, 13 database 13 server 11 P prerequisites 19 20, database 32 installation 19 product suite 33 server 20 product suite compatible releases 45 94

95 Index R reports configuration 59 restoring VantageView 85 rollup database 72, 75 Network Monitoring 75 Synthetic Monitoring 72 S security 58, 60 configuring security groups 58 domain-based 60 server 11, 20 prerequisites 20 system requirements 11 Server Monitoring configuring Control Server connection 78 configuring historical database connection 80 Control Server 77 integrating with VantageView 79 modifying Control Server connection 79 modifying database connection 80 SMTP 28, 32 Windows Server Windows Server SNMP 29, 32 Windows Server Windows Server SQL Server 11, 13, 32, 86 installation prerequisites 32 relocating database 86 supported versions 11, 13 supported environments 16 VMware 16 Synthetic Monitoring configuring database connections 70 modifying database connections 71 system requirements 11, client 14 database 13 server 11 T TeeChart7.ocx 55, 57 client 55 server 57 time zone for data rollup 83 U uninstalling VantageView 91 V verifying successful installation 58 virtual directory, relocating 87 VMware 16 W web server data, moving or copying 86 web server extensions 26, 30 Windows Server Windows Server WebDAV 27, 31 Windows Server Windows Server Windows Authentication 28, 31 Windows Server Windows Server Windows Everyone group 57 Windows Server configuring Windows Authentication 28 disabling Internet Explorer Enhanced Security 26 enabling web server extensions 26 installing IIS 25 installing SMTP 28 installing SNMP 29 verifying WebDAV 27 Windows Server configuring Windows Authentication 31 disabling Internet Explorer Enhanced Security 30 enabling web server extensions 30 installing IIS 29 installing SMTP 32 installing SNMP 32 verifying WebDAV 31 working hours for data rollup 84 95

96 Index 96