VantageView. Installation Guide. Release 12.0

(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: http://go.compuware.com

U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation.

This product contains confidential information and trade secrets of Compuware Corporation. Disclosure is prohibited without the prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of the user's License Agreement with Compuware Corporation.

Documentation may only be reproduced by Licensee for internal use. The content of this document may not be altered, modified or changed without the express written consent of Compuware Corporation. Compuware Corporation may change the content specified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found at http://go.compuware.com.

Compuware, 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.

(3)

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

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 VantageView Installation Guide 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 http://go.compuware.com.

(8)

• 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

http://www.adobe.com/.

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 e-mail 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

http://go.compuware.com. Select your product from the Product Support dropdown list.

Contacting Customer Support

Phone

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

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

Web

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

NOTE

Please report all high-priority issues by phone.

Email

[email protected]

Mail

Customer Support Compuware Corporation One Campus Martius Detroit, MI 48226-5099

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.

(9)

Corporate Website

To access the Compuware website, go to http://www.compuware.com. 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:

Indicates This font

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

Bold

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

Citation

Links to Internet resources and linked references to titles in Compuware documentation.

Documentation Conventions [p. 9]

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

Fixed width

User input in console commands.

Fixed width bold

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

Fixed width italic

(10)

Indicates This font

cddirectory_name

Menu items.

Menu ➤ Item

Text screen shots.

Screen

Blocks of code or fragments of text files.

Code block

(11)

C H A P T E R 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.

(12)

NOTE

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

Specification Requirement

Recommended: Minimum:

Machine:

3.0 GHz single core or 2.0 GHz dual core processor

Processor Speed

• 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

8 GB (with upgrade capability up to 16 GB)

4 GB RAM

More space may be needed for saving report results or storing large numbers of alerts.

40 GB (Excludes disk space required for the SQL Server application, if the database is installed on the VantageView Disk Space

server. Consult Microsoft documentation for details.) If needed for sending a page Notification.

Modem

Super VGA (1024 by 768) or higher resolution video adapter and monitor. Display

Windows Server 2003 32-bit with IIS 6.0 Operating Systems

Windows Server 2003 R2 64-bit with IIS 6.0

Windows Server 2008 32-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 NOTE

Server Core installation is not supported. Chapter 1 ∙ System Requirements

(13)

Table 1. VantageView Server Requirements (continued)

Microsoft SQL Server 2005 (32-bit or 64-bit platform) Database Software (if installed

on the VantageView server) _{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)

Microsoft Internet Explorer 7, 8, 9, 10, or 11 (32-bit version) with latest Service Packs

Browsers

NOTE

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

Recommended: Minimum:

Machine:

Two 3.0 GHz single core or two 2.0 GHz dual core processors or higher. 3.0 GHz single core or 2.0 GHz dual

core processor Processor Speed

Multiple processors are strongly recommended if SQL Server is installed on the same machine. Server-class machine

8 GB (with upgrade capability up to 16 GB)

4 GB RAM

More space may be needed for saving report results or storing large numbers of alerts.

40 GB (Excludes disk space for databases other than VantageView.) Disk Space

Super VGA (1024 by 768) or higher resolution video adapter and monitor. Display

Windows Server 2003 32-bit Operating Systems

Windows Server 2003 R2 64-bit Windows Server 2008 32-bit or 64-bit Windows Server 2008 R2 64-bit Windows Server 2012

Windows Server 2012 R2

(14)

Table 2. VantageView Database Requirements (continued)

NOTE

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]. Microsoft SQL Server 2005 (32-bit or 64-bit platform)

Database Software

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

Specification Requirement Recommended: Minimum: Machine: 2 GHz or greater 1 GHz Processor Speed 2 GB 1 GB RAM

Super VGA (1024 by 768) or higher resolution video adapter and monitor Display

Microsoft Internet Explorer 7, 8, 9, 10, or 11: 32-bit version, with latest Service Packs

Browser

NOTE

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.

(15)

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.

(16)

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.

(17)

Table 4. Compuware APM support for VMware

Support Status1 Product / Component

Business Service Manager

Supported Business Service Manager servers

Supported Configuration Client

Synthetic Monitoring

Supported Synthetic Monitoring Manager

Supported Synthetic Monitoring Console

Supported Parent Agent Manager/Agent Manager

Supported Active Agent, Collector Agent, Passive Agent

Supported2 Transaction Trace Analysis within Synthetic Monitoring

Supported Agent Scripts: Recorder, Micro Focus QALoad, Micro Focus QARun

Supported SQL Server Databases

Data Center Real User Monitoring

Supported Central Analysis Server Web Client

Best Effort Central Analysis Server/Advanced Diagnostics Server

Supported Agentless Monitoring Device Probe

Supported Configuration Client

Transaction Trace Analysis

Supported Database

Supported2 Agent

Best Effort Microsoft SQL Server 2005 Express

Best Effort Database Manager

Server Monitoring

Supported Control Server, Database

1

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.

2

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.

(18)

Table 4. Compuware APM support for VMware (continued) Support Status1 Product / Component Supported Template Manager Supported Agent Supported SNMP Collector Network Monitoring Supported Interactive Viewer Supported Enterprise Manager, Probe Manager, Independent Manager

Not Supported2 Probe – LAN drivers, WAN drivers

Supported Flow Collector VantageView Supported Client Supported Web Server Supported Database Compuware DLM Supported3 Compuware Distributed License Management

1

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.

3

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 email from Compuware World Wide License Management.

(19)

C H A P T E R 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.

(20)

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

Steps Finished

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 e-mail 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.

(21)

• 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 2003. 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 E-mail

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 e-mail.

NOTE

By default, SMTP is not installed in Windows Server 2008.

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

(22)

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 2008 64-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.

VantageView Ports and Protocols

Table 6. Ports Listing

Notes Authentication Required Protocol Default Port Component

VantageView operates on the standard HTTP port 80 by default. If necessary, you can Yes

HTTP 80

VantageView

configure it within IIS to operate on a different port.

HTTPS is supported for accessing the VantageView web server. When it is enabled, Yes

HTTPS 443

VantageView web server

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. Connect to the Changepoint server.

Yes HTTP

90 Changepoint Server

(23)

Table 6. Ports Listing (continued) Notes Authentication Required Protocol Default Port Component

Publish reports via email. No

HTTP 25

SMTP Server

Publish reports via FTP. Yes

HTTP 21

FTP Server

Connect to Central Analysis Server. No

HTTP 80

Agentless Monitoring connection

Access the SQL Server database. Yes

HTTP 1433

Database access

Connect to Network Monitoring Enterprise Manager. No HTTP 9003 Network Monitoring connection

Connect to the Server Monitoring Control Server. Yes TCP 3009 Server Monitoring connection

Connect to the Remedy server. Yes

TCP User-defined

Remedy connection

VantageView uses the COS that is

automatically installed and configured during No

HTTP 18080

COS

the VantageView installation. If you are performing a new installation, the default COS port is 18080 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.

(24)

This resource is available from http://go.microsoft.com/fwlink/?LinkId=67351. 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.

(25)

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.

(26)

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

Components.

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

By default, these extensions are Prohibited on Microsoft Windows 2003. 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.

Components.

(27)

4. The Windows Setup wizard appears and after a few moments the Windows Components

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.

Components.

5. Select Application Server and click Details. The Application Server dialog box appears.

(28)

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 2003

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.

(29)

Install SNMP in Windows Server 2003

Components.

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.

(30)

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

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

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 2008

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

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:

(31)

• ASP.NET

• ASP

• Server Side Includes

NOTE

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

NOTE

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.

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.

(32)

Install SMTP in Windows Server 2008

By default SMTP is not installed and enabled on Windows Server 2008, but required by VantageView.

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.

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.

(33)

Product Suite Prerequisites

Install Service Packs to companion products

Where applicable, check FrontLine (http://frontline.compuware.com) 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].

(34)

(35)

C H A P T E R 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].

NOTE

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.

(36)

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.

NOTE

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

(37)

NOTE

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.

NOTE

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

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

(38)

Table 7. VantageView Installation Checklist (continued)

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]. NOTE

During VantageView migration, SQL-account-based authentication defaults are restored. Any previously configured domain-based security settings must be re-applied.

Installation Procedure

NOTE

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.

VantageView. Installation Guide. Release 12.0

VantageView

Installation Guide

Contents

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

Who Should Read This Guide

Organization of this Guide

Related Publications

Customer Support Information

Information to Provide to Customer Support

Documentation Conventions

C H A P T E R 1

System Requirements

Server Requirements

Database Requirements

Client Requirements

VantageView Co-Location Deployment Guidelines

VMware and Virtualization

C H A P T E R 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 2003

Disable Internet Explorer Enhanced Security in Windows Server 2003

Install/Allow Web Server Extensions in Windows Server 2003

Verify WebDAV Extension Installation in Windows Server 2003

Configure Windows Authentication in Windows Server 2003

Install SMTP in Windows Server 2003

Install SNMP in Windows Server 2003

Microsoft Windows Server 2008 Configuration

Install IIS in Windows Server 2008

Disable Internet Explorer Enhanced Security in Windows Server 2008

Install/Allow Web Server Extensions in Windows Server 2008

Verify WebDAV Extension Installation in Windows Server 2008

Configure Windows Authentication in Windows Server 2008

Install SMTP in Windows Server 2008

Install SNMP in Windows Server 2008

Database Prerequisites

Product Suite Prerequisites

C H A P T E R 3

Installing VantageView

Installation Overview

Installation Overview

Installation Checklist

Installation Procedure