Vantage Analysis Server Installation Guide

Transcription

Vantage Analysis Server
Installation Guide
11.6
Please direct questions about Vantage Analysis Server or comments on this document to:
Compuware Customer Support
Compuware Corporation
Customer Support Hotline
1-800-538-7822
FrontLine Support Login Page:
http://go.compuware.com
For telephone numbers in other geographies, see the list of worldwide Support Offices at http://go.compuware.com.
Access is limited to authorized users. Use of this product is subject to the terms and conditions of the user’s License Agreement
with Compuware Corporation. Documentation may be reproduced by Licensee for internal use only. All copies are subject to the
terms of this License Agreement. Licensee agrees to provide technical or procedural methods to prevent use of the Software and
its documentation by anyone other than Licensee.
Copyright © 2011 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the
United States.
U.S. GOVERNMENT RIGHTS—Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth
in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS
252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.
Compuware Corporation.
This product contains confidential information and trade secrets of Compuware Corporation. Use, disclosure, or reproduction is
prohibited without the prior express written permission of Compuware Corporation. Access is limited to authorized users. Use
of this product is subject to the terms and conditions of the user’s License Agreement with Compuware Corporation.
ApplicationVantage, ClientVantage, Compuware, FrontLine, NetworkVantage, ServerVantage, Vantage, Vantage for Java and
.NET Monitoring, VantageView, Gomez, First Mile, and Gomez Private Network are trademarks or registered trademarks of
Compuware Corporation.
Cisco is a trademark or registered trademark of Cisco Systems, Inc.
Internet Explorer, Outlook, SQL Server, Windows, Windows Server, and Windows Vista are trademarks or registered trademarks
of Microsoft Corporation.
Firefox is a trademark or registered trademark of Mozilla Foundation.
Red Hat and Red Hat Enterprise Linux are trademarks or registered trademarks of Red Hat, Inc.
J2EE, Java, and JRE are trademarks or registered trademarks of Oracle Corporation.
VMware is a trademark or registered trademark of VMware, Inc.
Adobe® Reader® is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries.
All other company and product names are trademarks or registered trademarks of their respective owners.
Build: June 10, 2011, 11:45
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Who Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Organization of the Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product Documentation Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer Support and Online Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting a Problem on Vantage for Real User Monitoring. . . . . . . . . . . . . . . . . . . . .
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
6
7
7
9
Chapter 1 ∙ Vantage Analysis Server Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . .
VAS Product Release Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Browsers and Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internationalization Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
12
13
15
Chapter 2 ∙ Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
Chapter 3 ∙ System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommended Hardware Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommended Software Platform for Report Servers. . . . . . . . . . . . . . . . . . . . . . . . .
Recommended Operating System Configuration for Report Servers. . . . . . . . . . . . . . .
Microsoft SQL Server 2005 Setup Recommendations. . . . . . . . . . . . . . . . . . . . . . . . .
SQL Server 2005 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SQL Server 2005 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Vantage Analysis Server and NetworkVantage Enterprise Manager Installation . . . . . .
19
19
20
20
22
22
23
24
Chapter 4 ∙ Installing Vantage Analysis Server. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Vantage Suite Media Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Report Server to Use Private Keys and Certificates. . . . . . . . . . . . . . .
25
25
26
33
Chapter 5 ∙ Upgrading Vantage Analysis Server. . . . . . . . . . . . . . . . . . . . . . . . . . .
Navigating the Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing a Report Server Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating the Report Server to 64-bit Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
35
35
41
3
Contents
4
Chapter 6 ∙ Logging in to the Report Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
Chapter 7 ∙ VAS Basic Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VAS Personality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sites, User Aggregation, and User Tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying VAS Basic Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Other VAS Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
47
49
49
50
Chapter 8 ∙ Changing Report Server Settings Defined During Installation. . . . . . .
Changing Connectivity and Security Settings for the Report Server. . . . . . . . . . . . . . .
Changing Report Server Database User Password. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Java Web Start-based VCAEUE Console Connection Properties. . . . . . . . . .
51
53
55
55
Chapter 9 ∙ Licensing Vantage for Real User Monitoring Components. . . . . . . . . .
Licensing Report Server Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Licensed Features Supported by VAS, ADS, and AMD . . . . . . . . . . . . . . . . . . . . . . .
57
58
59
Appendix A ∙ Report Server Installation and Upgrade Troubleshooting. . . . . . . . .
61
Appendix B ∙ Protocols Supported by VAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
Appendix C ∙ SQL Operations Performed During Report Server Installation or
Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Database User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database User Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Memory Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
74
75
76
78
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
INTRODUCTION
Who Should Read This Guide
This guide is intended to be used by network engineers and system administrators installing the
Vantage Analysis Server.
Organization of the Guide
The Installation Guide of Vantage Analysis Server is organized as follows:
•
Vantage Analysis Server Overview [p. 11] - Describes the Vantage Analysis Server release
and lists the supported protocols.
•
Installation Checklist [p. 17] - Specifies how to install, license, and configure Vantage
Analysis Server, with references to details in other sections of this document as required.
•
System Requirements [p. 19] - Describes the minimum hardware and software requirements
for Vantage Analysis Server.
•
Installing Vantage Analysis Server [p. 25] - Describes how to install the Vantage Analysis
Server.
•
Upgrading Vantage Analysis Server [p. 35] - Describes how to upgrade the Vantage
Analysis Server.
•
VAS Basic Configuration Settings [p. 47] - Describes how to configure the Vantage
Analysis Server.
•
Licensing Vantage for Real User Monitoring Components [p. 57] - Describes product
licensing.
•
Protocols Supported by VAS [p. 67] - Lists protocols supported by VAS.
5
Introduction
Product Documentation Library
The following publications offer information on using and configuring Vantage Analysis Server.
Vantage for Real User Monitoring Release Notes
Summarizes new product features, known issues, and limitations, and lists last-minute
information not included in other publications related to the product.
Distributed License Management - License Installation Guide
Describes how to install and administer Compuware product licensing components.
Vantage for Real User Monitoring Getting Started Guide
Introduces product components, release information, system requirements, licensing
information, and performance estimates.
Describes how to install the report server.
Vantage Agentless Monitoring Device Installation and Configuration Guide
Describes how to install the Agentless Monitoring Device, which collects data for the
Vantage Analysis Server and Advanced Diagnostics Server.
Vantage for Real User Monitoring System Administration Guide
Describes how to configure and administer Vantage for Real User Monitoring.
Vantage Analysis Server on-line help
Provides on-line procedures and information to help you use the product.
Vantage Analysis Server User Guide
Guides you through the features of the report server. It describes each top-level report and
many lower-level reports, shows you how to interpret the reports, how to identify problems
and how to optimize your network and site operation.
Web Application Monitoring Guide
Explains how to configure Web application monitoring with the Web Monitoring
Configuration perspective in Vantage Configuration for Agentless End-User Experience
- Console.
Vantage for Real User Monitoring Web Services - Getting Started Guide for Developers
Provides data structure definitions and usage examples for RUM Web service developers.
WAN Optimization in Vantage Getting Started Guide
Introduces the WAN optimization concept within Vantage. It describes how to properly
configure Vantage and accurately monitor your optimized WAN environment using the
AMD and the report server.
PDF files can be viewed with Adobe Reader, version 7 or later. If you do not have the Reader
application installed, you can download the setup file from the Adobe Web site at
http://www.adobe.com/downloads/.
6
Introduction
Customer Support and Online Information
Corporate Web site
To access Compuware's site on the Web, go to http://www.compuware.com. The Compuware
site provides a variety of product and support information.
FrontLine support Web site
You can access online customer support for Compuware products via our FrontLine support
site at http://go.compuware.com. FrontLine provides fast access to critical information about
your Compuware products. You can read or download documentation, frequently asked questions,
and product fixes, or e-mail your questions or comments. The first time you access FrontLine,
you are required to register and obtain a password. Registration is free.
Contact us
The contact information to all local Compuware offices is provided on the
http://go.compuware.com Web site.
All high-priority issues should be reported by phone.
Reporting a Problem on Vantage for Real User
Monitoring
When calling, please provide Customer Support with as much information as possible about
your environment and the circumstances that led to the difficulty.
You should be ready to provide:
•
Client number: this number is assigned to you by Compuware and is recorded on your sales
contract.
•
The version number of the Agentless Monitoring Device (AMD) , the report servers and
VCAEUE Console with VCAEUE Server.
For the report server
Use the report server GUI by selecting Help ➤ Product Information ➤ About, or
Tools ➤ Diagnostics ➤ System Status.
For the AMD
Scroll down to the Testing AMD section. At the bottom of the diagnostic data
paragraph, look for Version ND-RTM v. ndw.ww.x.y.zz.
For the VCAEUE Console and VCAEUE Server
Use the VCAEUE Console GUI by selecting Help ➤ About menu item.
For the VTCAM
Use the VTCAM GUI by selecting Help ➤ About menu item.
7
Introduction
•
Environment information, such as the operating system and release (including service pack
level) on which the product (AMD, report server) is installed, memory, hardware/network
specifications, and the names and releases of other applications that were running.
Problem description, including screenshots.
•
Exact error messages, if any (screenshots recommended).
•
Whether or not the problem is reproducible. If yes, include a sequence of steps for problem
recreation. If not, include a description of the actions taken before the problem occurred.
•
A description of the actions that may have been taken to recover from the difficulty and
their results.
•
Debug information as follows:
Information from the report server
◦ Log files from http://report_server_IP/root/log/ and watchdog.log from
the C:\Program Files\Common Files\Compuware\Watchdog directory.
◦
Configuration file: http://report_server_IP/ExportConfig
◦
Screenshots of the problem.
Information from the AMD
Log files from /var/log/adlex/: rtm.log, rtm.log.1, rtm_perf.log,
rtm_perf.log.1.
Information from the VCAEUE Server
◦ Log files from ..\Program Files\Compuware\
Vantage_Configuration_For_Agentless_EUE\cva\log
◦
directory.
All files from ..\Program Files\Compuware\
Vantage_Configuration_For_Agentless_EUE\platform3.0\InstallLogs
◦
All *.log files from ..\Documents and Settings\All Users\Application
Data\Compuware\<Service Name>\workspace\log\kernel where <Service
Name> is Microsoft Windows Service Name associated with VCAEUE Server. By
default it is Agentless Platform 1
◦
Version file (version.xml) located in ..\Program
Files\Compuware\Vantage_Configuration_For_Agentless_EUE\
◦
Version file (version.xml) located in ..\Program Files\Compuware\
Vantage_Configuration_For_Agentless_EUE\cva\eclipse
Information from the VCAEUE Console
The installation log file:
Vantage_Configuration_for_Agentless_End-User_Experience_11.6_InstallLog.log
location:
..\Program Files\Compuware\Vantage_Configuration_For_Agentless_EUE
log files located in the following directory of your VCAEUE Console installation:
..\Program
Files\Compuware\Vantage_Configuration_For_Agentless_EUE\eclipse\log
8
Introduction
and version file (version.xml) located in ..\Program
Files\Compuware\Vantage_Configuration_For_Agentless_EUE\ and in ..\Program
Files\Compuware\Vantage_Configuration_For_Agentless_EUE\cva\eclipse.
Information from the VTCAM
System Event log of the machine where the VTCAM is operating.
NOTE
Please compress all the files before sending them to Customer Support.
Compuware values your comments and suggestions about the Vantage products and
documentation. Your feedback is very important to us. If you have questions or suggestions for
improvement, please let us know.
Conventions
The following font conventions are used throughout documentation:
This font
Indicates
Bold
Terms, commands, and references to names of screen controls and user
interface elements.
Conventions [p. 9]
Links to Internet resources and linked references to titles in Compuware
documentation.
Fixed width
Cited contents of text files, examples of code, command line inputs or system
outputs. Also file and path names.
Fixed width bold
User input in console commands.
Fixed width italic
Place holders for values of strings, for example as in the command:
cd directory_name
Menu ➤ Item
Menu items.
9
Introduction
10
CHAPTER 1
Vantage Analysis Server Overview
The Vantage Analysis Server (VAS) provides real-time access to information about performance
and usage of key business applications. It monitors user session performance, application
performance, and server performance in different configurations, with the purpose of identifying
when and where problems occur and how to address them.
Analysis options give insight into business application performance on the transaction and
operation level. The information is aligned with the business structure of the organization (such
as branches, working groups, and business units) and is not dependent on the infrastructure
components. It is delivered via comprehensive, interactive, service-oriented reports, and via
event-driven alarms that inform you about important events such as performance degradation
or traffic pattern anomalies.
VAS reports are organized as a comprehensive set of scorecards, dashboard reports, and detailed
drilldown reports tied to the scorecards. The report structure reflects business organization
priorities and allows for quick determination of the root causes of problems. The VAS is also
equipped with powerful data mining and report building tools for creating new or customized
reports quickly and easily.
The VAS uses measurement data provided by passive network monitoring devices referred to
as Agentless Monitoring Devices (AMDs) or NetworkVantage Probes, and by active network
monitoring agents referred to as ClientVantage Active Agents. The VAS also can read data
from the Cisco Network Analysis Module (NAM).
In real user monitoring, one or more AMDs, NetworkVantage Probes, or NAMs are attached
to the monitored network near the core switch of the data center or near VPN access switches.
The AMDs and NetworkVantage Probes collect data from the monitored network, preprocess
it, and deliver it to the report server. Each report server can handle a number of AMDs and
NetworkVantage Probes. The report server processes the received data further, stores it in a
database, and then generates user-friendly reports. Reports can then be viewed and analyzed
regularly or only when a network problem occurs.
The VAS provides:
•
Web analysis and reporting
•
Analysis of Oracle, DB2, MS SQL, Sybase, and Informix protocols
•
Analysis of the Oracle Forms protocol
11
Chapter 1 ∙ Vantage Analysis Server Overview
•
Analysis of the Jolt (Tuxedo) protocol
•
Analysis of MS Exchange protocol
•
Analysis of XML-based transactions
•
Analysis of SOAP-based transactions
•
Analysis of SAP GUI protocol
•
Thin client protocol analysis
•
VoIP analysis
•
VPN analysis
•
WAN analysis
•
IBM MQ protocol analysis
•
Enterprise applications analysis and reporting
•
Real-time reports, trending reports, baseline calculations
•
Event alarms
•
Detection of abnormal application usage and network usage patterns
•
User diagnostics
•
Customizable reports
•
Report access management and report publication/sharing
•
Decryption and analysis of HTTPS traffic
•
Monitoring of SSL errors
VAS Product Release Information
The report server is composed of several software modules, each of which may have a different
version number. This table lists component module versions for the current and preceding
releases of the report server.
Table 1. Component module versions based on preceding and current release report server
Module name
11.1.0
11.5
11.6.0
Vantage Analysis Server
11.1.0
11.5
11.6.0
DMI
11.1.0
11.5
11.6.0
RTM
Base System
11.1.0
11.5
11.6.0
RTM
Gate
11.1.0
11.5
11.6.0
11.1.0
11.5
11.6.0
ND
12
Module version number in report server version
Core Base System
Supported Browsers and Connectivity
Vantage for Real User Monitoring users can access report servers through supported Web
browsers.
The following browsers are supported:
•
Microsoft Internet Explorer version 7.0 or 8.0, with JavaScript and HTTP 1.1 settings
enabled.
Note that due to a different handling of the data within the HTML, Microsoft Internet
Explorer may experience degradation in performance while viewing reports containing a
large number of columns or reports containing a large number of tooltips.
•
Mozilla Firefox version 3.5 or 3.6, with JavaScript, cookie support, and HTTP 1.1 enabled.
Before you start using the report server, it may be necessary to adjust JavaScript and HTTP 1.1
settings in your browser.
NOTE
•
Some configuration screens require a Web browser with Java plug-in version 1.5.0.9 update
11 or later.
•
If you use 32-bit and 64-bit browsers interchangeably, you need a Java plug-in for each
browser. Remember that the Windows 64-bit operating system comes with 32-bit and 64-bit
Internet Explorer (IE) browsers and that the 32-bit version runs as a default.
•
Java Web Start-based VCAEUE Console requires the Java Web Start that is included in
JRE 1.4.2 or higher as part of the JRE software. Note that Java Web Start-based VCAEUE
Console will only run on Windows and a 32-bit JRE.
•
In Java plug-in version 1.5, TLS is turned off by default. This may cause some applets not
to work in your Web browser. You must turn on TLS in the Java 1.5 Control Panel to have
full access to all report server features. For more information, see How to enable TLS 1.0
for Java 1.5 plug-in [p. 14].
•
Without JavaScript enabled, the top menu of the report server will not be visible and you
will see the following message instead: This product uses JavaScript. Please make
sure JavaScript is enabled in your browser settings.
The Advanced Diagnostics Server and Vantage Analysis Server can be accessed using HTTP
or, over secured connections, using HTTPS. We recommend secure access with a browser that
supports TLS v.1. Using older versions of the protocol, such as SSL 2 or SSL 3, is not
recommended but can be configured. For more information, see Configuring the Report Server
to Use Private Keys and Certificates [p. 33].
How to enable JavaScript and support for HTTP 1.1 in your browser
Internet Explorer
To enable JavaScript:
13
1.
Select Tools ➤ Internet Options from the top menu in your browser and click the
Security tab.
2.
Click Custom level and enable Active scripting on the list of options.
To enable HTTP 1.1:
1.
Select Tools ➤ Internet Options from the top menu in your browser and click the
Advanced tab.
2.
Scroll within the Settings list to the section titled HTTP 1.1 settings and ensure that
the Use HTTP 1.1 check box is selected.
3.
Click OK and restart your browser.
Mozilla Firefox
To enable JavaScript:
1.
Select Tools ➤ Options from the top menu in your browser and click the Content
tab.
2.
Select the Enable JavaScript check box.
To enable HTTP 1.1:
1.
Open the browser and, in the address bar, type about:config and press [Enter].
The browser will display a list of current preferences.
2.
Scroll to the network.http.version preference and ensure its value is 1.1. If the value
is other than 1.1, double-click that row, change the value to 1.1, click OK, and restart
your browser.
How to enable TLS 1.0 for Java 1.5 plug-in
The TLS for Java plug-in is turned on in Java Control Panel, in the Security settings of the
Advanced tab.
1.
Access the Java Control Panel in one of the following ways:
•
Windows control panel:
In Windows, click Start ➤ Settings ➤ Control Panel and select Java to open Java
Control Panel. Note that Java Control Panel opens for the default Java installation,
which may not be correct for the plug-in that you are trying to modify.
•
Java installation directory:
Navigate to the bin directory where the Java version you intend to modify is installed
(for example C:\Program Files\Java\jre1.5.0_11\bin). Click the file javacpl.exe
to activate the configuration tool.
•
Java platform icon in system tray:
Right-click the icon and choose Open Control Panel from the menu.
2.
14
In the Java Control Panel, click the Advanced tab and expand the Security tree to display
the Use TLS 1.0 check box.
3.
Select the Use TLS 1.0 check box.
4.
Click OK.
Internationalization Support
Vantage Analysis Server supports international environments on both ends: report server and
client browser.
Localized server support
The user interface of the report server is rendered in the following languages:
•
English
•
Japanese
•
Korean
•
Chinese simplified
•
Chinese traditional
For English, which is the default language setting, there is no need for additional configuration
of the operating system or browser. To enable support for other languages, install the required
font set for the target language and customize the regional options accordingly.
Character encoding support for monitored traffic
Vantage Analysis Server recognizes the following character encodings:
HTTP and XML/SOAP
• ISO-8859-1
•
ISO-8859-2
•
Unicode (UTF-8)
•
UTF-16 (XML/SOAP only)
•
Japanese: EUC-JP, Shift_JIS, Unicode (UTF-8)
•
Korean: EUC-KR, ISO-2022-KR, Unicode (UTF-8)
•
Chinese: Big5, Big5-HKSCS, EUC-TW, GB18030, GB2312, GBK, HZ,
ISO-2022-CN, Unicode (UTF-8)
MQ
Unicode (UTF-8)
Database/SQL (Oracle, TDS, DRDA, Informix)
• UTF-8 (all DB analyzers)
•
UTF-16 (TDS analyzer only)
•
EBCDIC (DRDA analyzer only)
15
DB statements that were not sent in a supported encoding are encoded such that all
non-ASCII characters are replaced with their hexadecimal value in the form %XX, where
X is a hexadecimal digit.
SMB and Kerberos
Character encoding in monitored traffic does not affect SMB and Kerberos analyzer
operations.
Jolt and FIX
Character encoding in monitored traffic does not affect Jolt and FIX analyzer operations.
Generic TCP
Character encoding in monitored traffic does not affect generic TCP analyzer operations.
16
CHAPTER 2
Installation Checklist
Installation actions should be performed in this order. Follow the links for details on performing
individual steps.
1.
Verify hardware and software suitability.
See System Requirements [p. 19] to ensure the hardware and software requirements are
met.
2.
Obtain a license for your Vantage Analysis Server installation.
For more information, see Licensing Vantage for Real User Monitoring Components [p. 57].
3.
Install Vantage Analysis Server.
For new installation, see Installing Vantage Analysis Server [p. 25], for upgrade procedures,
see Upgrading Vantage Analysis Server [p. 35].
4.
Configure the Vantage Analysis Server.
VAS Basic Configuration Settings [p. 47] describes VAS basic configuration, which has
to be performed before the product can function.
For details on how to set all of the other configuration options supported by Vantage
Analysis Server, please refer to Vantage for Real User Monitoring System Administration
Guide.
17
Chapter 2 ∙ Installation Checklist
18
CHAPTER 3
System Requirements
Ensure that your system meets the requirements to run Vantage for Real User Monitoring
components.
NOTE
Satisfying the minimum requirements may not ensure the usability level you require. Choose
the most appropriate hardware and system platform to achieve the best performance and optimal
operation of your installation.
Recommended Hardware Platforms
Recommended hardware comes in two tiers. This table lists platforms supported for each tier.
Although Tier 1 and Tier 2 platforms have similar performance characteristics, Tier 2 hardware
platforms have been designed to analyze much greater traffic data volumes and to operate with
a higher number of network interfaces, and Tier 2 hardware architecture employs system models
that support greater traffic analysis and storage capabilities.
Table 2. Supported hardware platforms
Product
AMD
Report Server
Tier 1
Tier 2
Dell, HP, IBM
HP, Sun, IBM
Dell, HP, IBM, Sun
For details on Tier 1 and Tier 2 hardware configurations, see Recommended Hardware
Configurations.
19
Chapter 3 ∙ System Requirements
Recommended Software Platform for Report Servers
The following software platform components are recommended for Vantage for Real User
Monitoring report servers.
Microsoft Windows Server
One of the following editions:
•
Microsoft Windows Server 2003 (64-bit Edition) with the latest release, service packs,
and five Client Access Licenses (CALs).
•
Microsoft Windows Server 2008 (64-bit Edition) with the latest release, service packs,
and five Client Access Licenses (CALs). Windows Server 2008 is the report server
default platform.
Microsoft SQL Server
One of the following editions:
•
Microsoft SQL Server 2005 (64-bit Edition).
•
Microsoft SQL Server 2008 (64-bit Edition).
•
Microsoft SQL Server 2008 R2 (32-bit and 64-bit Edition).
The recommended versions are: Standard and Enterprise.
Other software
• Adobe Reader, version 7.0.5 or later.
•
PuTTY (Telnet/SSH utility), version 0.58 or later.
•
WinSCP (Windows secure file copy utility), version 3.8.3 or later.
The recommended minimum screen resolution on the report server machine is 1024x768, with
at least 16-bit color mode.
Recommended Operating System Configuration for
Report Servers
Typical preparations for a secure report server deployment require several steps to be performed
on the side of the operating system.
This section does not include all possible preventive measures; it is intended only to serve as a
list of recommended good system administration practices for system hardening.
1.
Disable all unnecessary services.
•
Disable all unused system accounts (for example, Guest or SQLDebugger).
•
Disable DCOM.
•
Turn off indexing on all volumes (services).
•
Disable network protocols and bindings:
SMB
20
NetBios over TCP/IP
•
Disable the following services (if unused):
Alerter
Application Layer Gateway Service
Application Management
Automatic updates
Background Intelligent Transfer Service (BITS)
Computer Browser
ClipBook
Distributed File System
Distributed Link Tracking Client
Distributed Link Tracking Server
MS Software Shadow copy Provider
DNS Server
Error Reporting Service
File replication
Help and support
HTTP SSL
Human Interface Device Access
IAS Jet Database Access
IMAPI CD Burning COM Service
Indexing Service
Intersite Messaging
Kerberos Key Distribution Center
License Logging Service
Messenger
Microsoft Search
NetMeeting Remote Desktop Sharing
Network DDE
Network DDE DSDM
Network Location Awareness (NLA)
Print Spooler
Remote Registry
Server
SNMP Trap Service
SQL Server FullText Search
TCP/IP NetBIOS Helper Service
Telnet
Telephony
Windows Management Instrumentation Driver Extension
WMI Performance Adapter
Windows Image Acquisition (WIA)
2.
Remove all unnecessary executables and registry entries.
21
3.
Apply restrictive permissions to files, services, end points and registry entries.
All of these values should be created under the following registry key (if not present already):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
SynAttackProtect, REG_DWORD, 1
EnableDeadGWDetect, REG_DWORD, 0
NoNameReleaseOnDemand, REG_DWORD,1
EnablePMTUDiscovery, REG_DWORD, 0
KeepAliveTime, REG_DWORD (time in milliseconds), 300000
EnableICMPRedirect, REG_DWORD, 0
DisableIPSourceRouting, REG_DWORD, 2
TcpMaxConnectResponseRetransmissions, REG_DWORD, 2
TcpMaxDataRetransmissions, REG_DWORD, 3
PerformRouterDiscovery, REG_DWORD, 0
TcpMaxPortsExhausted, REG_DWORD, 5
All values given above are hexadecimal.
Microsoft SQL Server 2005 Setup Recommendations
The following sections provide a brief description of SQL Server 2005 setup for reliable and
secure functioning with Vantage Analysis Server.
NOTE
Most of the recommendations listed here may have already been applied if the Agentless
Monitoring Device was purchased as a turnkey solution. If only a Compuware software solution
was chosen, some of the steps may not be applicable. For more information, see Purchase
Options in the Vantage for Real User Monitoring – Getting Started Guide.
The changes must be applied with caution so as not to affect the operation of the SQL Server
or Vantage Analysis Server.
SQL Server 2005 Installation
Perform this procedure only if you use SQL Server 2005 as a back end for the Vantage Analysis
Server.
Prior to SQL Server installation, ensure the following services are enabled (set the start to
automatic) and started:
•
COM+ System Application
•
Distributed Transaction Coordinator
Then perform the following:
1.
Start the installation of SQL Server 2005.
Select the Server components, tools, Books Online, and samples install option.
2.
Configure installation options.
System configuration check may display several warnings about components needed only
for Reporting Services. Because Reporting Services are not installed, the following warnings
should not cause any problems with SQL Server 2005:
•
22
IIS Feature Requirement
•
3.
ASP.NET Version Registration Requirement
Choose components to install.
Select the following components:
4.
•
SQL Server Database Services
•
Workstation components, Books Online, and development tools
Choose the instance name.
Since it is permissible to use one of many MS SQL Server instances, you are permitted to
use any name meaningful to you for each of the instances.
5.
Define Service Account.
Select Use the built-in system account with Local System as an option.
6.
Select the authentication mode.
Choose Mixed mode, set sa password to adlex.
7.
Define collation settings.
Leave default Collation selection: Dictionary order, case insensitive, for use with 1252
Character set.
8.
Disable Error and usage Report Settings.
Do not send any data outside your network, clear all options.
SQL Server 2005 Configuration
Perform this procedure only if you use SQL Server 2005 as a back end for the Vantage Analysis
Server.
After installing SQL Server 2005, perform the following configuration steps:
1.
Create a new default database file location.
Set the directory e:\mssql\data as Database default locations (for Data and Log).
2.
Move the tempdb database to the new location.
a. Open SQL Server Management Studio and connect to local database with administrative
privileges (sa or local machine administrator). In Object Explorer, expand
Databases ➤ System databases, right-click tempdb, and choose New Query.
b. Execute the following query:
ALTER DATABASE tempdb MODIFY FILE ( NAME = tempdev , FILENAME =
'e:\mssql\data\tempdb.mdf' )
ALTER DATABASE tempdb MODIFY FILE ( NAME = templog , FILENAME =
'e:\mssql\data\templog.ldf' )
c. Stop the SQL Server service.
d. Move tempdb.mdf and tempdb.ldf from C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data to e:\mssql\data
e. Start the SQL Server Service.
f. To verify changes in the database, execute the following query:
SELECT name, physical_name AS CurrentLocation, state_desc
FROM sys.master_files WHERE database_id = DB_ID(N'tempdb');
A summary table like the following should appear:
23
g.
3.
Name
CurrentLocation
state_desc
tempdev
E:\mssql\data\tempdb.mdf
ONLINE
templog
E:\mssql\data\templog.ldf
ONLINE
Close SQL Server Management Studio.
Turn off Customer Experience Improvement Program.
Vantage Analysis Server and NetworkVantage
Enterprise Manager Installation
When planning an installation of the VAS and NetworkVantage Enterprise Manager on a single
machine, ensure all hardware and software requirements are met by both components. Also take
into consideration any additional factors that may influence the operation of VAS or
NetworkVantage, such as service pack installation, upgrade of only one of the two services,
performance issues (during data collections performed by Enterprise Manager), and port
assignments (for communication with Probes and database server).
24
CHAPTER 4
Installing Vantage Analysis Server
Use the Vantage suite media browser to locate and start the installation wizard for your report
server. Note that no installation actions are performed until all of the installation information
has been gathered and you have confirmed that the installation should proceed.
During the installation process:
•
Click Next to record your selections for that step and proceed to the next step (unless errors
or inconsistencies are found in the choices you specify).
•
Click Back (if available) to go to the previous step and change settings.
•
Click Cancel (if available) to terminate the process.
Vantage Suite Media Browser
Use the Vantage suite media browser as your starting point for installing or upgrading any
Vantage product and for accessing a variety of related documentation.
1.
2.
Select the appropriate Vantage installation disc.
•
Disc 1 - Windows
•
Disc 2 - Linux
•
Disc 3 - Unix
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.
3.
The media browser opens to the Vantage tab by default.
The media browser has three tabs:
Vantage
All of the options on this tab of the Vantage Suite Media Browser are for creating
fresh software installations. The options on this tab do not work for upgrades, all of
which must be started from the Components/Upgrades tab.
25
Chapter 4 ∙ Installing Vantage Analysis Server
Components/Upgrades
The options on this tab of the Vantage Suite Media Browser are for upgrading
existing Vantage installations or installing individual Vantage components.
Utilities
The options on this tab of the Vantage Suite Media Browser are for upgrading other
software to use in conjunction with your Vantage software.
At the bottom of the media browser screen are various supplemental links:
Read Vantage Documentation
Opens the Vantage Installation Bookshelf, a list of hyperlinks to documentation on the
current installation disc.
Be sure to check FrontLine (http://frontline.compuware.com) for the latest versions of all
product documentation, including last-minute revisions to product release notes.
Documentation on the installation discs may be superseded by information online.
Compuware License Server (optional)
Installs Distributed License Management, an application for installing and managing your
Compuware licenses.
Compuware License Installation Guide
Opens Compuware Licensing Guide.pdf, a guide to the Vantage licensing process.
Adobe Reader
Installs Adobe Reader, an application for displaying and printing PDF files. Many Vantage
documents are PDF files.
Explore this media
Opens Microsoft Windows Explorer for browsing the file directory structure of the current
installation disc.
Performing the Installation
You must have Administrator privileges to install the Vantage Analysis Server.
CAUTION
Exit all programs before running the setup program. Some Windows programs, such as anti-virus
software, may interfere with the installation process.
To install the report server:
1.
2.
Locate Vantage installation disc 1 (Windows disc).
3.
26
Vantage
Components/Upgrades
Utilities
4.
On the Components/Upgrades tab, click the link to install the 32-bit version or the 64-bit
version of the software.
The Vantage Analysis Server is available in versions for 32-bit and 64-bit platforms.
•
If you are installing it on a machine with a 32-bit architecture, click Install Vantage
Analysis Server to install the 32-bit version.
•
If you are installing it on a machine with a 64-bit architecture and sufficient system
resources, you can use either the 32-bit or the 64-bit version of the Vantage Analysis
Server.
Compared with the 32-bit version, the 64-bit version of the Vantage Analysis Server
uses more memory to handle the same volume of traffic, but it is capable of managing
much larger volumes of traffic, provided your computer is equipped with sufficient
memory to support this. The recommended minimum memory size for installing the
64-bit version is 32 GB . If you decide to use the 64-bit version, click Install Vantage
Analysis Server x64.
You may briefly see one or two messages from the installation program telling you that it
is being prepared and initialized for the installation process. This may take a few seconds,
after which a welcome screen displays the product release number.
5.
If the detected amount of physical memory (RAM) on the target machine is lower than the
recommended amount, you will see a warning message.
Click Cancel to abort the installation and perhaps upgrade the machine's RAM before
restarting the installation process, or click Next (not recommended) to continue this
installation with less than the recommended amount of RAM.
6.
7.
Click Next on the Vantage Analysis Server welcome screen, view the license agreement
screen, and, if you agree with the terms of the license agreement, indicate your choice and
click Next to proceed with the installation or Cancel to terminate the installation.
Type or browse for the target installation directory and click Next.
If a previous installation is detected, you are offered the choice of reinstalling or upgrading
your product. Refer to Upgrading Vantage Analysis Server [p. 35] for details of
re-installation and upgrade procedures.
8.
Define the SQL database connection properties.
The Vantage Analysis Server requires a database to store run-time data. You need to specify
the information as shown on the following screen:
27
Figure 1. Defining SQL database connection properties
Note that if you are installing the report server and the SQL Server on a single machine, it
is required that the service name for SQL Server uses the default name (MSSQLSERVER). For
more information, see Report Server Installation and Upgrade Troubleshooting [p. 61].
You may need to consult the database administrator to determine the correct values. If the
database server is on the same machine, enter the word localhost in the Server field. For
remote servers, enter the server name or IP address. Add the port number (preceded by a
colon) if it is different from the default value of 1433. Using a “\” separator, you can indicate
the SQL database instance to which you want to connect. You can also point to the SQL
server instance by giving the port number only instead of the name. For more information,
see How do I determine the port number for a named instance of the SQL Server? [p. 64].
The database device location is the physical location of the database on the database server
computer.
The default database username can be replaced with a local database server user or a valid
domain user. Specify a domain name in the following format: domain\user.
CAUTION
If you are going to create a database on Microsoft SQL Server 2008 and want to use a
Windows domain user as the database user, you must enable this account on the SQL Server
prior to the report server installation.
Select or clear the Use SSL check box to indicate whether SSL should be used in
communication with a report server.
Click Next to submit your database connection choices.
28
9.
If a database of the specified name already exists, a warning message prompts you to specify
whether to Upgrade the existing database (and preserve the data) or Recreate the database
(and delete all of your existing data).
Figure 2. Selecting to upgrade or recreate a database
If you want to specify another database name, click Cancel to go back to the previous
installation screen.
10. If the Database Size screen appears, specify the size of the new database and then click
Next.
This screen is displayed if no database of the specified name already exists, or if you have
selected to overwrite an existing database. The suggested size displayed on this screen is
calculated to leave room for performing a backup of the database on the same disk.
11. If the Database Server Memory Setting screen appears, specify the maximum size of the
SQL server memory and then click Next.
This screen is displayed if a new database is created or if an existing database is overwritten.
Note that for the reconfiguration to take effect, the SQL server must be restarted. If you
are using a local SQL server, the installation program offers to restart it automatically. If
you have specified a remote server, you are asked to restart the server manually before
attempting to use the database.
12. Configure the connectivity and security options.
The configuration screen prompts you to specify the port number on which your Vantage
Analysis Server should be accessible. The host name under which your Vantage Analysis
Server will be recognized is shown on the screen for your information. You will view your
Vantage Analysis Server reports by accessing this host in your browser. The host name
should be followed by the port number, if the port number is not 80.
29
If you need to transfer or display the reports securely across the network, you can also
specify the HTTPS port number. When accessing the Vantage Analysis Server reports on
a port other that 443, remember to supply the selected port number together with the host
name in your browser. Note that HTTP/HTTPS settings can be modified by running the
Change/Remove program from the Add or Remove Programs utility.
Figure 3. An example of the Connectivity and Security Options screen
If you select the HTTPS option, the SSL Key Generation Data screen enables you to
either automatically generate a key and a certificate, or to use a custom encryption key. To
generate the key, provide the required data, which varies depending on whether you chose
automatic or custom key generation.
30
Figure 4. Supplying SSL key generation data
Choosing a custom encryption key requires configuring the server manually, which involves
copying both the key and the certificate to the proper directory and modifying the
common.properties file. For more information, see Configuring the Report Server to Use
Private Keys and Certificates [p. 33].
NOTE
On the SSL Key Generation Data screen, there is a Remember the key password check
box. If you decide not to store the password during the installation, you can supply it on
system start-up, but only if you are directly connected to the server. Remember that the
dialog box for entering the password will not appear if you are connected to the server
using a remote terminal.
Also, remember that not providing a password means that the key will not be encrypted.
13. Configure Vantage Configuration for Agentless End-User Experience connection properties
to enable VCAEUE Console Java Web Start.
You can access the VCAEUE Console directly from a Vantage Analysis Server using Java
Web Start, which automatically puts the configuration into the scope of the VAS you are
using. You need to specify connection details at installation time so that the Java Web
Start works instantly after the VAS is installed.
•
If you installed the VCAEUE with default settings and on the same machine where
you are installing the VAS leave the options unchanged and click Next to proceed with
installation.
•
For remote VCAEUE installation clear Local VCAEUE installation and type IP
address of the host where VCAEUE Server is running.
31
Verify the VCAEUE Server port number which by default is 4180. Click Next to proceed
with installation.
Figure 5. VCAEUE connection properties
Note that connection properties can be changed later in the report server Control Panel or
by running the Change/Remove program from the Windows software management utility.
For more information, see Changing Java Web Start-based VCAEUE Console Connection
Properties [p. 55] and Changing Java Web Start-based VCAEUE Console Connection
Properties Remotely in the Vantage for Real User Monitoring – System Administration
Guide.
14. Review the summary of your installation choices and, if you are satisfied with them, click
Install.
If you need to change anything, use the Back button to retrace your steps to the appropriate
configuration screen.
15. Your Vantage Analysis Server software is installed.
The process of installing and pre-configuring software components and defining your
database may take several seconds, minutes, or even hours, depending on the size of the
database. A progress box shows the status of the installation action currently in progress.
When all of the required actions have been completed, a final post-installation information
screen is displayed.
16. Perform post-installation actions.
Depending on the operating system you are using, you may be asked at this stage whether
you want to start Vantage Analysis Server. Indicate your choice in the check box provided
and click Finish.
32
Configuring the Report Server to Use Private Keys and
Certificates
You can set up your report server to use secure connections with users' web browsers, and to
use automatically generated data or your own keys and certificates.
Prerequisites
It is recommended that secure access be performed using TLSv1 (TLS version 1), which is more
secure than its predecessors. Use of older versions of the protocol can be configured by setting
the configuration property connector.ssl.SSLProtocol to SSLv3 or SSLv2, as required. Note
that Apache Tomcat default is all, with other acceptable values being SSLv2, SSLv3, TLSv1,
and SSLv2+SSLv3. Leaving the connector.ssl.SSLProtocol parameter empty causes the Web
browser negotiate the version of a secure protocol when connecting to the Web server. For more
information on secure connection configuration in Apache Tomcat, refer to
http://tomcat.apache.org/tomcat-6.0-doc/apr.html#HTTPS.
The report server implementation of SSL uses OpenSSL. This means that encryption,
certification, and other operations are handled as defined in OpenSSL.
The subdirectory tools\openssl of the report server installation directory contains the OpenSSL
tool, which can be used for SSL key and certificate generation, conversions, and management.
The report server installation process uses the tools in this directory to generate a self-signed
SSL certificate and a key pair for initial HTTPS server operation.
This certificate and the key pair are, by default, stored in the wwwroot/WEB-INF/ssl subdirectory
of the report server installation directory. To change this path, modify the
connector.ssl.SSLCertificateFile and connector.ssl.SSLCertificateKeyFile
configuration properties in common.properties.
To configure your own encryption keys and register the server in the CA (certificate authority)
infrastructure, the common.properties file has to be edited manually. Refer to the Apache
Tomcat documentation: http://tomcat.apache.org/tomcat-5.5-doc/apr.html.
All certification procedures, such as certificate request or certificate signing, have to be handled
manually by using the OpenSSL utility. For instructions on how to use the OpenSSL utility,
refer to http://www.openssl.org.
The report server can connect to the network via standard HTTP or HTTPS (HTTP over SSL),
both of which are supported by the report server installation process, or via other modes that
can be configured manually.
The connectivity configuration settings are stored in the configuration file common.properties,
in the config subdirectory of the report server installation directory. The names of the
configuration properties in common.properties follow the standard names used for Tomcat
and OpenSSL. (The format of the file is different, but the names of the configuration parameters
are the same.)
All of the connectivity configuration properties are set by the installation program during report
server installation.
33
NOTE
Subsequent modifications to connectivity settings are possible but should be performed with
great care. These settings require a thorough understanding of web server connector settings
and OpenSSL.
The simplest procedure for joining the server to the certification infrastructure can be summarized
as follows:
1.
Generate a private RSA key as described in http://www.openssl.org/docs/HOWTO/keys.txt.
It is suggested that the password should be encrypted. The report server can ask for the key
password every time it starts, or the password can be configured using the report server
installation program.
2.
3.
4.
Create a certificate request as described in
http://www.openssl.org/docs/HOWTO/certificates.txt (section 3).
Pass the certificate to a certification authority for signing.
Set configuration properties.
Configure the following settings in the common.properties file:
5.
•
Point connector.ssl.CertificateFile to the received certificate file.
•
Point connector.ssl.CertificateFileKey to the generated key.
•
Point connector.ssl.CertificateChainFile to the chain of certificates.
Set the key password.
If the key was encrypted, use the report server installation program to set the key password.
34
CHAPTER 5
Upgrading Vantage Analysis Server
The Vantage Analysis Server installation program will detect older versions of the product and
offer to upgrade them to the current release, optionally preserving configuration information
and traffic monitoring data contained in the Vantage Analysis Server database.
Configuration migration is fully supported for upgrades from versions 11.5 and 11.1. If upgrading
from an earlier version, some elements of configuration migration may have to be performed
manually. This applies, in particular, to the configuration of alarms.
Navigating the Upgrade Process
•
Click Next to record your selections for that step and proceed to the next step (unless errors
or inconsistencies are found in the choices you specify).
•
Click Back (if available) to go to the previous step and change settings.
•
Click Cancel (if available) to terminate the process.
Performing a Report Server Upgrade
You must have administrative privileges to upgrade Vantage Analysis Server.
CAUTION
Exit all programs before running the setup program. Some Windows programs, such as anti-virus
software, may interfere with the upgrade process.
To upgrade the Vantage Analysis Server (to install a newer version over an existing version):
1.
Stop the currently running server.
In Windows, click Start ➤ Programs ➤ Vantage Analysis Server ➤ Server ➤ Stop.
2.
3.
Locate Vantage installation disc 1 (Windows disc).
35
Chapter 5 ∙ Upgrading Vantage Analysis Server
4.
Vantage
Components/Upgrades
Utilities
5.
On the Components/Upgrades tab, click the link to install the 32-bit version or the 64-bit
version of the software.
The Vantage Analysis Server is available in two versions:
•
For a machine with a 32-bit architecture, click Install Vantage Analysis Server to
install the standard 32-bit version.
•
For a machine with a 64-bit architecture, you can use either the 32-bit version (as
above) or you can click Install Vantage Analysis Server x64 to install the 64-bit
version of the Vantage Analysis Server.
You should choose based on the available memory and the volume of traffic you need
to monitor. Compared with the 32-bit version, the 64-bit version of the Vantage Analysis
Server uses more memory to handle the same volume of traffic, but it is capable of
managing much larger volumes of traffic, provided your computer is equipped with
sufficient memory to support this. The recommended minimum memory size for
installing the 64-bit version is 32 GB.
NOTE
Upgrade from a 32-bit version to a 64-bit version is not supported. If you need to perform
such an upgrade, you must save your 32-bit configuration settings manually (this pertains
only to new server configuration files added after the 32-bit installation) and uninstall the
32-bit version of the product, while preserving the database. You should then install the
64-bit version as a new installation, not an upgrade, and perform a manual migration of
configuration settings. Note that those settings that are maintained in the database will be
migrated together with the database. For more information, see Migrating the Report Server
to 64-bit Version [p. 41].
When you select the version, you may briefly see one or two messages from the InstallShield
wizard telling you that InstallShield Wizard is being prepared and initialized for the
installation process, after which the welcome screen displays product release number
information and the amount of physical memory available is checked.
36
6.
If the detected amount of physical memory (RAM) on the target machine is lower than the
recommended amount, you will see a warning message.
Click Cancel to abort the installation and perhaps upgrade the machine's RAM before
restarting the installation process, or click Next (not recommended) to continue this
installation with less than the recommended amount of RAM.
7.
8.
Click Next on the welcome screen and view the license agreement screen.
If you agree with the terms of the license agreement, select the appropriate radio button
and click Next to proceed with the installation.
If you do not accept the terms of the license agreement, click Cancel to terminate the
installation process.
9.
Choose whether to perform a new installation or an upgrade to the current installation.
When an existing version of the software is detected, you are given the option to either
perform a fresh installation of the current version of the product, or to upgrade, while
optionally preserving configuration settings or database contents:
Figure 6. Choosing between a new installation and an upgrade
Note that configuration migration is fully supported for upgrades from versions 5.1 or later.
If upgrading from an earlier version, some elements of configuration migration may have
to be performed manually. This applies in particular to the configuration of alarms.
After you select an option (new installation or upgrade), click Next to proceed with the
new installation or upgrade. Note that Vantage Analysis Server component services will
be stopped before the installation or upgrade can be performed.
37
IMPORTANT
•
If you chose to perform a new installation, you should stop reading this procedure and
now refer to Step 7 [p. 27] of Installing Vantage Analysis Server [p. 25].
•
If you chose to perform an upgrade, continue with the next step of this procedure.
10. Confirm SQL database connection properties.
The Vantage Analysis Server requires a database to store run-time data. When you are
upgrading an existing installation, the current database connection properties are displayed,
enabling you to modify the database administrator login name and password:
Figure 7. Database Connection Properties screen
Select or clear the Use SSL check box to indicate whether SSL should be used in
communication with a report server.
Use the radio buttons to specify what to do with the database:
Recreate database
This option deletes the database and creates a new database of the same name. All
the information contained in the database is lost.
Reset database
This option purges traffic monitoring data from the database but preserves the product
configuration settings.
Upgrade database
This option preserves all traffic monitoring data and product configuration settings.
Click Next to submit your database connection choices.
38
11. Configure Vantage Configuration for Agentless End-User Experience connection properties
to enable VCAEUE Console Java Web Start.
You can access the VCAEUE Console directly from a Vantage Analysis Server using Java
Web Start, which automatically puts the configuration into the scope of the VAS you are
using. You need to specify connection details at installation time so that the Java Web
Start works instantly after the VAS is installed.
•
installation.
•
Verify the VCAEUE Server port number which by default is 4180. Click Next to proceed
with installation.
Note that connection properties can be changed later in the report server Control Panel or
by running the Change/Remove program from the Windows software management utility.
For more information, see Changing Java Web Start-based VCAEUE Console Connection
Properties [p. 55] and Changing Java Web Start-based VCAEUE Console Connection
Properties Remotely in the Vantage for Real User Monitoring – System Administration
Guide.
12. Optional: Modify HTTP/HTTPS settings.
During the upgrade procedure, you cannot change connectivity and security settings.
However, you can do so at any time after the upgrade by running the Change/Remove
program from the Add or Remove Programs utility located in the Windows Control
39
Panel. Each time, during the server upgrade to version 11.6, a screen will appear to remind
you about it.
Figure 9. The HTTP Connection Info screen
Figure 10. Modifying the HTTPS settings on the Change/Remove screen
For more information on how to configure HTTPS settings, refer to the Step 12 [p. 29] of
the Vantage Analysis Server installation procedure, and to Configuring the Report Server
to Use Private Keys and Certificates [p. 33].
40
13. Review the summary of installation choices.
Before the actual upgrade commences, a summary screen displays all of the choices you
have made. Review them carefully and, if you need to change any of them, use the Back
button to retrace your steps to the appropriate configuration screen.
14. Upgrade Vantage Analysis Server
On the summary screen, click Install to commence the actual process of upgrading and
pre-configuring software components and defining your database. The amount of time this
takes depends on the size of the database and may be anything between several seconds
and, for large databases, several hours. A progress box shows the status of the installation
action currently in progress. When all of the required actions have been completed, a final
post-upgrade information screen is displayed.
15. Perform post-installation actions.
Depending on the operating system you are using, you may be asked at this stage whether
you want to start Vantage Analysis Server. Indicate your choice in the check box provided
and click Finish. There is no such choice for Windows 2000, which requires re-booting
before the Vantage Analysis Server can function. In case of Windows 2000, after clicking
Finish on the post-installation information screen, you will be asked, in a separate message
box, if you want to re-boot the system now or later.
It is possible to change the database user password during the upgrade procedure (see Step
10 [p. 38]) or at any time after the installation or upgrade by running the Change/Remove
program from the Add or Remove Programs utility located in the Control Panel
(Figure 10. Modifying the HTTPS settings on the Change/Remove screen [p. 40]).
After selecting the option Change database user password choose Next and enter a new
password in the following screen.
Migrating the Report Server to 64-bit Version
Migrating a 32-bit version of the report server to a 64-bit version requires some manual
configuration.
Prerequisites
A working installation of a 32-bit version with a database attached is required to upgrade to a
64-bit version. Make a note of the administrative user sa database password and path to the
database.
NOTE
This procedure works for the same release number, but different architectures of the VAS. If
you want to upgrade your report server from release 11.1, 11.1, or 11.5, and migrate it to the
64-bit architecture, at first you have to upgrade it to release 11.6 and then apply the following
instructions.For more information, see Upgrading Vantage Analysis Server [p. 35] and
Performing a Report Server Upgrade [p. 35].
41
The path for upgrading to a 64-bit version of the VAS requires uninstalling the current 32-bit
version and installing the 64-bit version. This process requires a manual transfer of custom
settings from one version to the other. The majority of report server configurations and settings
are stored in the attached database. Only the configuration files that were created after the default
installation need to be transferred manually. These include customer-specific configuration files
located in C:\Program Files\Compuware\VAS\config folder and custom SQL scripts that are
located in the C:\Program Files\Compuware\VAS\config\sql\def folder.
To migrate a 32-bit instance of the VAS to the 64-bit architecture, perform the following steps:
1.
Back up the VAS database.
For more information, see Backing Up MS SQL Server 2005 Databases in the Vantage for
Real User Monitoring – System Administration Guide and Backing Up MS SQL Server
2008 Databases in the Vantage for Real User Monitoring – System Administration Guide.
2.
Create a temporary repository folder and back up the VAS configuration.
Navigate to C:\Program Files\Compuware\VAS\config and copy all the files and
subdirectories to the backup folder.
3.
4.
Uninstall the current 32-bit version using Add or Remove Programs in the Start ➤
Settings ➤ Control Panel.
Install the VAS 64-bit version using the same installation procedures and information used
for the 32-bit version.
NOTE
Ensure that during the installation process, the Upgrade option is chosen when the existing
database is detected.
Figure 11. Database upgrade
42
5.
6.
7.
Examine and compare the C:\Program Files\Compuware\VAS\config\sql\def folder
contents with the repository and copy the missing SQL scripts from the repository into the
new installation.
Examine and compare the C:\Program
Files\Compuware\VAS\config\locations-*.config folder contents with the repository
and copy the modified files from the repository into the new installation.
Examine and compare the C:\Program
Files\Compuware\VAS\config\reporting-groups-*.config folder contents with the
repository and copy the modified files from the repository into the new installation.
The new 64-bit installation will now contain the configuration read from the upgraded database
and all of the custom alarm and SQL scripts created in the 32-bit version.
Be sure to confirm that the new installation contains the proper settings before removing the
temporary repository.
43
44
CHAPTER 6
Logging in to the Report Server
To connect to your report server, enter the server address in your browser. After the initial
installation only the superuser account is active and requires no passwords. This lets you
perform basic configuration tasks, including defining additional users.
You should configure your own superuser password as one of the first actions you perform on
the server. You should then define additional users. Access the server as superuser only for
configuration purposes. For information on how to add users, see Adding New Report Server
User in the Vantage for Real User Monitoring – System Administration Guide.
For information on recommended browsers, see Supported Browsers and Connectivity [p. 13].
45
Chapter 6 ∙ Logging in to the Report Server
46
CHAPTER 7
VAS Basic Configuration Settings
When you use the Vantage Analysis Server for the first time, you will be asked to specify a
number of basic configuration options. These options are fundamental to the operation of the
product and must be specified before the VAS starts to function.
You must have administrative privileges to be able to modify the basic configuration settings.
Figure 12. The Vantage Analysis Server Configuration screen
VAS Personality
The Vantage Analysis Server (VAS) can be licensed in one of two personalities: Web or
Enterprise. The personality determines the types of reports offered.
VAS-Web and VAS-Enterprise are intended to work separately, on separate hardware, but they
can also be installed together in the same VAS instance. This option is particularly useful for
monitoring sites with relatively low traffic, where one machine has much more capacity than
is required either by VAS-Web or VAS-Enterprise.
Web
Primarily for analysis of end-user experience with Web-hosted applications.
47
Chapter 7 ∙ VAS Basic Configuration Settings
•
Analysis options for HTTP, SMTP, and DNS.
•
Dedicated reports for HTTP (including per-URL reports), SMTP, and DNS.
•
DMI access to all data, including HTTP (with per-URL data), SMTP, and DNS.
For the Web personality, the list of available reports includes Website Status, Activity
Map, User Activity, Mail Status and DNS Status from the Software Services group of
reports.
Enterprise
For analysis of performance and usage of key IT resources.
•
Analysis options for HTTP, SMTP, DNS and TCP generic transactions.
•
Reports providing unified view of all applications; no dedicated reports for HTTP,
SMTP, or DNS.
•
DMI access to all data, including HTTP (no per-URL data), SMTP, and DNS.
For the Enterprise server personality, the list of available reports includes all Network
reports: Network View, Link View, Software Services View, Reporting Groups, User
Diagnostics. Additionally, VoIP Status reports are available from the Software Services
group and VPN Status from the Network group. Note that VPN support is a licensed
feature, and VoIP reports require NetworkVantage Probe attached to the VAS to produce
VoIP performance data.
Regardless of the VAS personality settings and licenses, the reports from the Applications
menu are always available.
The VAS can be licensed with one or more of the following supplemental analysis options,
unrelated to personality settings and depending on presence of their own licenses:
48
•
DNS
•
IBM DB2/DRDA
•
IBM WebSphere MQ
•
Informix
•
Mail
•
Microsoft SQL Server/Sybase
•
Oracle SQL*Net
•
Oracle Forms
•
Tuxedo Jolt
•
VPN Gateway (Juniper Neoteris, Nortel Contivity, and Intel NetStructure)
•
Microsoft Outlook/Exchange
•
Thin Client (Citrix and Windows Terminal Services for Windows Server 2000 and 2003)
•
XML (transactional analysis with XML message tracking, including SOAP)
•
SAP GUI
NOTE
Personality selection or change is allowed only if the product has been licensed for the target
personality, though the license may be temporary.
Sites, User Aggregation, and User Tracking
A site is an organizing concept introduced to help report users identify particular IP networks.
In this context, a site is defined as an IP network or a part of a network.
A site is defined in one of two ways:
•
Manual sites are specified as explicit IP address ranges
•
Automatic sites are based on either AS names or CIDR blocks, where a block is defined
by an IP address and a network mask
All client IP addresses that are neither manual nor automatic sites are treated as belonging to
the Default site. All server IP addresses that do not fall into any of the manual or automatic site
categories are treated as belonging to the Default Data Center site.
User aggregation means that users are not recognized individually, but are counted per site.
Note that if sites are based on AS names, users can still be aggregated to CIDR blocks within
ASes. However, if sites are based on CIDR blocks, users cannot be aggregated to ASes because
these are not recognized as entities in this configuration.
The option Base automatic sites on enables you to select automatic sites based on either ASes
or CIDR blocks. You can also opt not to have automatic sites.
The option Base user aggregation on enables you to aggregate users to ASes or CIDR blocks,
subject to any additional aggregation and user tracking options you may configure.
Note that user aggregation is compatible with the way you configure the creation of automatic
sites. If automatic sites are based on CIDR blocks, user aggregation can also be based on CIDR
blocks, but it cannot be based on ASes, because ASes are not recognized entities. However, if
you choose automatic sites based on ASes, you will have the choice of aggregating users to
ASes or individual CIDR blocks.
Additional user tracking and aggregation options enable you to track or count all or selected IP
addresses or user identifiers while aggregating other users. These options may require you to
enter IP address ranges consisting of IP addresses separated by hyphens (in the form
nnn.nnn.nnn.nnn-nnn.nnn.nnn.nnn).
Modifying VAS Basic Configuration Settings
If further modifications to the basic product configuration are required after initial configuration,
you can return to the configuration screen for configuration refinements.
Select Settings ➤ Vantage Analysis Server ➤ Server Configuration from the Vantage
Analysis Server menu.
49
CAUTION
If you change the way automatic sites are defined, or if you modify the basic user aggregation
options from AS to CIDR or vice versa, the traffic monitoring data currently stored in the report
server database will no longer be compatible with the new definitions.
In such cases, a warning message will be displayed, giving you the option to abandon the
configuration changes or to proceed with or without purging the traffic monitoring information
in the database. A purge is recommended, since any attempt to access old traffic monitoring
data while new site or aggregation definitions are in place would have unpredictable results.
After clearing the database, the data gathered by the AMD is re-read by the report server.
Configuring Other VAS Settings
Procedures for setting all other configuration options supported by the Vantage Analysis Server
are described in Vantage for Real User Monitoring System Administration Manual.
Sections referring exclusively to the Vantage Analysis Server are marked “(VAS Only)”; other
VAS-applicable material can be found in sections referring to both report servers (VAS and
ADS).
50
CHAPTER 8
Changing Report Server Settings Defined During
Installation
The main parameters defined during installation of the report server can be changed later using
a dedicated tool which is accessible via Windows Control Panel. The set of available parameters
depends on the type of report server you are configuring.
For the VAS and ADS, the settings include:
•
Setting report server port number.
For more information, see Changing Connectivity and Security Settings for the Report
Server [p. 53].
•
Defining whether SSL should be used to communicate with the server (this also includes
SSL keys and certificate options).
For more information, see Changing Connectivity and Security Settings for the Report
Server [p. 53].
•
Changing database user password.
For more information, see Changing Report Server Database User Password [p. 55].
More settings can be modified for the VAS exclusively:
•
Changing connection settings for Java Web Start-based VCAEUE Console.
Changing Java Web Start-based VCAEUE Console Connection Properties [p. 55]
51
Chapter 8 ∙ Changing Report Server Settings Defined During Installation
Figure 13. An example of post-installation settings welcome screen
Note that each of the listed tasks must be performed when the report server is turned off. If the
setup program discovers a running VAS or ADS, it displays a warning screen and attempts to
stop the dedicated system service. Click Next to allow the service to stop so the requested
configuration screen can be accessed.
Figure 14. An example screen warning about active product services
52
Changing Connectivity and Security Settings for the
Report Server
You can reconfigure connection details (HTTPS connection settings and port numbers) after
the report server is deployed. If you need to transfer or display the reports securely across the
network, you can specify an HTTPS port number.
To change previously assigned port numbers or enable HTTPS access to your report server:
1.
2.
On the machine where the VAS or ADS is installed, access Windows Control Panel and
open the dialog box for installed software management (for example, Programs and
Features).
In the list, find the product you want to re-configure, such as Vantage Analysis Server
ver. 11.6.0 and click Uninstall/Change.
A dialog with a set of options opens.
3.
Select Change HTTP and SSL Server Settings and click Next.
The report server service will stop and Connectivity and Security Options window will
open.
4.
Apply the requested changes.
In the Connectivity and Security Options dialog box, you can change the previously
assigned HTTP port and specify whether a secure connection is enabled or not. Note that
you can enable both HTTP and HTTPS access to the report server.
Figure 15. An example of the Connectivity and Security Options screen
If you select the HTTPS option, the SSL Key Generation Data screen enables you to
either automatically generate a key and a certificate, or to use a custom encryption key. To
53
generate the key, provide the required data, which varies depending on whether you chose
automatic or custom key generation.
Choosing a custom encryption key requires configuring the server manually, which involves
copying both the key and the certificate to the proper directory and modifying the
common.properties file. For more information, see Configuring the Report Server to Use
Private Keys and Certificates [p. 33].
Figure 16. Supplying SSL key generation data
NOTE
On the SSL Key Generation Data screen, there is a Remember the key password check
box. If you decide not to store the password during the installation, you can supply it on
system start-up, but only if you are directly connected to the server. Remember that the
dialog box for entering the password will not appear if you are connected to the server
using a remote terminal.
Also, remember that not providing a password means that the key will not be encrypted.
5.
6.
54
Click Next to confirm modifications to the report server configuration.
Finish reconfiguration.
After the changes are made, the Change/Remove Summary window will list the changes.
Select Start [REPORT_SERVER_TYPE] after the reconfiguration and click Finish to bring
the report server online.
Changing Report Server Database User Password
The password of the default report server database can be changed at any time on the machine
where the server is installed.
To change a previously assigned database user password:
1.
2.
Features).
3.
Select Change database user password.
The report server service stops and the Database User Password Update window opens.
4.
5.
6.
Enter the new password (twice) for the default database user.
Changing Java Web Start-based VCAEUE Console
Connection Properties
When the address or TCP port number of the VCAEUE Server changes, you need to enter the
new values in the VAS configuration. If you can access the machine where the VAS is installed,
this is done by changing configuration details using Windows Control Panel.
The address and port number of the Vantage Configuration for Agentless End-User Experience
are defined during VAS installation or upgrade. When either of the two parameters changes,
you can immediately redefine connection properties. To change a previously assigned port
number or IP address of theVCAEUE Server:
1.
2.
Features).
3.
Select Change Console Java Web Start Options.
The report server service will be stopped and VCAEUE Connection Properties window
opens.
4.
Apply the requested changes.
55
•
installation.
•
5.
6.
To test new settings, start the Vantage Configuration for Agentless End-User Experience Console from the VAS menu or Windows menu shortcut. For more information, see Launching
Java Web Start-based VCAEUE Console in the Vantage for Real User Monitoring – System
Administration Guide and Launching Java Web Start-based VCAEUE Console from Windows
Shortcut in the Vantage for Real User Monitoring – System Administration Guide.
56
CHAPTER 9
Licensing Vantage for Real User Monitoring
Components
Vantage components are protected by a license management system called Compuware
Distributed License Management (DLM).
DLM uses the following components to help manage product licensing:
License File
DLM authorizes you to use Compuware products through a license file, which is a text
file that contains information about the component options purchased with the product,
including information for the product's features and the number and types of licenses that
were purchased.
Compuware License Service (cpwr.exe)
An application (invoked by the DLM application or executed from the command line)
that manages and services requests for the licenses of your Compuware products. The
Compuware License Service can be installed on Windows and UNIX platforms. In many
cases, you should co-locate the Compuware License Service with the server-based
components of one of the Compuware products you are installing.
License types
DLM offers several different types of licenses as described in the table below. Each Compuware
product may support different combinations of these license types.
Table 3. DLM license types
License type
Description
Trial License
A trial license ships with some
Installing the product.
Compuware products. This license type
lets you evaluate the product. The
default evaluation period is 30 days,
after which time the trial license expires.
Obtained by...
57
Chapter 9 ∙ Licensing Vantage for Real User Monitoring Components
License type
Description
Obtained by...
Temporary License A temporary license has a fixed
Requesting the license from
expiration date from the time that it is Compuware, not shipped with the
installed on your system. You must run product.
the DLM to install this license type.
Permanent
Node-Locked
License
A Permanent Node-Locked license is a
client-based single-user license and does
not have an expiration date. A
Node-Locked license is identified by the
HOSTID keyword in the license file and
must always run on the same machine
(same node, and hence the license is
“node-locked”) as it was originally
installed.
Running the DLM to determine your
node identifier and providing the
information to Compuware. Compuware
will e-mail you a license file based on
the node identifier.
Permanent
A Permanent Concurrent license is
Concurrent
server-based and allows you to purchase
(Floating) License a specific number of licenses without
assigning them to a particular
workstation. When all available licenses
are checked out from the License
Manager, no additional users can run the
product until a license is checked back
in.
Running the DLM on the server for the
License Manager to obtain the node
identifier and providing the information
to Compuware.
Vantage licenses will only recognize the
first NIC address identified during
system startup. If you have a
multi-homed system, you will need to
If you change workstations or NIC cards, obtain a license based on your disk serial
you must contact Compuware to obtain number.
a new license.
The License Manager software and the
license files must be installed on the
server. Use the DLM from the client
machines to connect them to the License
Manager.
This type of license has a license file
with SERVER and DAEMON lines.
Borrowed License A borrowed license is a license that the
user checks out of the borrow proxy
server and later checks back in. This
enables the user to detach from the
network and still use the Compuware
product.
License must be requested from
Compuware.
Requires the Borrow License Client
application to be installed in the same
directory as the DLM.
Licensing Report Server Features
Compuware recommends that you back up the license information (license file) before installing
the license with the Compuware Distributed License Management (DLM).
If DLM is not already installed on the computer on which you are installing the report server,
DLM will be installed automatically as part of the report server installation.
58
NOTE
A stand-alone installation of DLM can also be found on the report server installation CD. For
a 32-bit version of the report server, use the DLM version in the subdirectory named win32; for
a 64-bit version of the report server, use the DLM version in the x64 subdirectory.
When the report server is first installed, a 30-day trial license is installed with the product. The
trial license allows you to use both of the configurable personalities of the product as well as
all of the licensable features. To continue using the product past the trial period, contact
Compuware to obtain a license suited to your requirements.
If you are using multiple Compuware products, merge the license files with the DLM to easily
manage the licenses.
You can run the licensing utility by selecting Start ➤ Programs ➤ Compuware ➤ Distributed
License Management.
Refer to the License Manager documentation for instructions on using the DLM to install a new
or trial license.
NOTE
The report server checks for new licenses every few minutes. Therefore, it may take a number
of minutes before a newly applied license is recognized by the server.
Features are usually licensed on the report servers, with the feature-specific functionality being
enabled on the AMD, but if the AMD is a standalone product with no report server available,
it is also possible to license a feature on the AMD itself.
Post-licensing actions
After installation of a new license on the report server, re-application of the license to AMDs
is performed automatically. AMDs are able to accept a new license without restart. Note,
however, that if the new license extends the current functionality of the product, this new
functionality has to be configured before it can be used. For example, if the new license allows
you to monitor a new protocol, this protocol has to be added to the list of monitored protocols
by specifying it in the configuration settings.
Licensed Features Supported by VAS, ADS, and AMD
The Vantage Analysis Server (VAS) and Advanced Diagnostics Server (ADS) are licensed per
module, which means that you must purchase a license for each of the analysis options you use.
Note, however, that there is no exact one-to-one correspondence between report types or report
server menu options and licenses. For example, the Database Status report will show all database
traffic for all supported databases, though each database type requires a separate license.
Similarly, the Website Status set of reports will show HTTP traffic, including HTTPS, provided
that SSL analysis has been licensed.
Compuware does not limit the number of users of the report servers: any number of users can
access VAS and ADS reports.
59
60
APPENDIX A
Report Server Installation and Upgrade
Troubleshooting
Issues with installation and upgrade include database connectivity issues, system services startup,
and other areas.
After the installation, I cannot see Advanced Diagnostics Server or Vantage Analysis
Server in the services list. What do I do?
If you installed the report server and the SQL Server on a single machine, the service
name for SQL Server must be the default name. If the service name used to start SQL
Server is not MSSQLSERVER, the installer will not be able to create a service for the report
server. Although all necessary files will be successfully installed, you will not be able to
start the servers from the services list.
Check the log files if this is the issue. In default installations, the log files are C:\Program
Files\Compuware\VAS\log\install\wdgInstallNTService.log and C:\Program
Files\Compuware\VAS\log\install\wdgInstallServices.log. Open the files and
search for the following strings:
•
SQL service MSSQLServer is not found (The specified service does not
exist as an installed service. (0x424))
•
in wdgInstallServices.log
SQL service (MSSQLServer) is not found (The specified service does
not exist as an installed service. (424))
in wdgInstallNTService.log.
To work around this issue:
1.
In Windows, go to Administrative Tools ➤ Services.
2.
Double-click SQL Server (Instance_Name) (the main SQL Server service) to see
properties.
3.
Check the Service Name (not Display Name) for SQL Server on General tab.
4.
Open the command prompt and issue the following command:
"C:\Program Files\Common Files\Compuware\Watchdog\windowsjre_x64.exe"
-install "Vantage Analysis Server" "Vantage Analysis Server" “Service
name of the SQL Server checked in the step 3”
61
Appendix A ∙ Report Server Installation and Upgrade Troubleshooting
On 32-bit systems, you should use the "C:\Program Files\Common
Files\Compuware\Watchdog\windowsjre.exe" command.
5.
Reboot the machine where the report server is installed to apply the changes.
6.
After the machine restarts, check whether the Vantage Analysis Server service has
been added and starts correctly.
What do I do when the services cannot start?
There could be a number of reasons why the services might not start. The following
procedure will help you to determine the most frequent causes of this problem.
1.
Inspect the server.log file.
The file server.log can be opened by selecting Start ➤ Programs ➤ Compuware
➤ Vantage Analysis Server ➤ Documentation ➤ Server log.
2.
TCP port availability check.
Search server.log for the message “Address already in use:
JVM_Bind:port_number”. If you find such a message, it means the report server
cannot start because the TCP port reserved for the built-in Web server is already in
use by another software service process.
T
ADM
06-03-16 12:45:12.274
AAS Platform 3.7.0 (build 164)
T
ADM
06-03-16 12:45:12.324
Vantage Analysis Server 5.0.0 (build 152)
T
ADM
06-03-16 12:45:12.324
RTM Base System 2.2.0 (build 156)
T
ADM
06-03-16 12:45:12.324
RTM GATE 2.2.0 (build 149)
T
ADM
06-03-16 12:45:12.324
ND Core Base System 5.2.0 (build 165)
T
ADM
06-03-16 12:45:12.324
Vantage Analysis Server Service Pack 5.0.1
(build 9)
java.net.BindException: Address already in use: JVM_Bind:80
at
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:264)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:137)
at
org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1429)
at org.apache.catalina.startup.Embedded.start(Embedded.java:851)
at
adlex.delta.tomcat.embedded.TomcatBootstrap.startServer(TomcatBootstrap.java:176)
at adlex.delta.server.Admin.main(Admin.java:243)
LifecycleException: Protocol handler initialization failed:
java.net.BindException: Address already in use: JVM_Bind:80
at
org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1431)
at org.apache.catalina.startup.Embedded.start(Embedded.java:851)
at
adlex.delta.tomcat.embedded.TomcatBootstrap.startServer(TomcatBootstrap.java:176)
at adlex.delta.server.Admin.main(Admin.java:243)
HTTP server not started.
Please determine the service and terminate it.
You can list all the TCP and UDP ports that are currently in use. It can be done easily
with the netstat command:
netstat /a /n
This command lists all the active ports and their status, for example:
Active Connections
Proto
62
Local Address
Foreign Address
State
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
UDP
UDP
UDP
UDP
UDP
UDP
UDP
UDP
UDP
3.
0.0.0.0:80
0.0.0.0:135
0.0.0.0:443
0.0.0.0:445
0.0.0.0:1049
0.0.0.0:1433
0.0.0.0:6942
127.0.0.1:1060
127.0.0.1:7578
127.0.0.1:7579
192.168.1.100:139
0.0.0.0:445
0.0.0.0:500
0.0.0.0:1025
0.0.0.0:1026
0.0.0.0:1434
0.0.0.0:1464
0.0.0.0:3385
0.0.0.0:3456
0.0.0.0:4500
0.0.0.0:0
0.0.0.0:0
0.0.0.0:0
0.0.0.0:0
0.0.0.0:0
0.0.0.0:0
0.0.0.0:0
0.0.0.0:0
127.0.0.1:7579
127.0.0.1:7578
0.0.0.0:0
*:*
*:*
*:*
*:*
*:*
*:*
*:*
*:*
*:*
LISTENING
LISTENING
LISTENING
LISTENING
LISTENING
LISTENING
LISTENING
LISTENING
ESTABLISHED
ESTABLISHED
LISTENING
Database connectivity check.
Search server.log for the message “No connection to data base”. If you find
such a message, it means the report server could not start due to database connectivity
problems.
T
ADM
06-03-16 13:19:26.668
AAS Platform 3.7.0 (build 164)
T
ADM
06-03-16 13:19:26.688
Vantage Analysis Server 5.0.0 (build 152)
T
ADM
06-03-16 13:19:26.738
RTM Base System 2.2.0 (build 156)
T
ADM
06-03-16 13:19:26.738
RTM GATE 2.2.0 (build 149)
T
ADM
06-03-16 13:19:26.738
ND Core Base System 5.2.0 (build 165)
T
ADM
06-03-16 13:19:26.738
Vantage Analysis Server Service Pack 5.0.1
(build 9)
T
RPT
06-03-16 13:19:26.818
watchdog file created:
c:\prj\rtm50\config\nds.sem - Interval 15 min
T
DB
06-03-16 13:19:27.059
JDBC_DRIVER =
net.sourceforge.jtds.jdbc.Driver
T
DB
06-03-16 13:19:27.059
JDBC_URL =
jdbc:jtds:sqlserver://localhost:1433/delta;tds=8.0;
T
DB
06-03-16 13:19:27.059
JDBC_USER = delta
E
DB
06-03-16 13:19:28.261
Cannot get connection:Network error
IOException: Connection refused: connect
E
DB
06-03-16 13:19:59.235
E
DB
06-03-16 13:21:00.223
T
ADM
06-03-16 13:21:00.233
No connection to data base.
The error messages prior to the last one indicate the possible reason of the problem.
The following table lists the most frequent reasons of database connectivity problems.
Table 4. The database connectivity troubleshooting actions
Message
Cannot get
connection:Network error
Potential reason
Microsoft SQL Server is
down.
Troubleshooting action
Start Microsoft SQL Server.
IOException: Connection
refused: connect
Microsoft SQL Server in not Reconfigure Microsoft SQL
configured to listen on the
Server to enable TCP
TCP port though it was
connectivity.
listening during the product
installation.
63
Message
Potential reason
Troubleshooting action
Microsoft SQL Server is now
configured to listen on a
different TCP port than it was
during the installation
process.
Edit the
database does not exist.
You have to reinstall the
Compuware product to
recreate the database with
correct user rights. If you
have a database backup copy,
you can restore it.
The report server cannot
authenticate with Microsoft
SQL Server.
The password of the user
delta has been changed.
Reset it to the original value.
config\repository.properties
file to update the TCP/IP
settings. Edit the line starting
with JDBC_URL=... and enter
a correct IP address of the
If a remote Microsoft SQL
database server and the TCP
Server was used, it has
port on which it listens to
changed its IP address or the queries.
configured IP address has
been used by a different
computer.
Cannot get
connection:Cannot open
database requested in
login 'vas'. Login fails.
Cannot get
connection:Login failed
for user 'delta'.
How do I determine the port number for a named instance of the SQL Server?
If enabled, the default instance of the SQL Server Database Engine listens on TCP port
1433. Named instances of the database engine are configured for dynamic ports. This
means they select an available port when the SQL Server service is started. You can
determine your SQL Server named instance in several ways; using SQL Server
Configuration Manager is one of the simplest ways.
In general, you should refer to your SQL Server named instances by name so that you
always address the valid instance (the port number may change but the instance name
does not). If, during installation of the report server, you are unable to use the instance
name and are forced to give a port number, you can check its value:
1.
Log in to the system either remotely (via Remote Desktop, for example) or locally.
2.
In Windows, go to Programs ➤ Microsoft SQL Server <server_version> ➤
Configuration Tools and choose SQL Server Configuration Manager.
3.
Select Protocols for <instance_name> and then double-click TCP/IP to inspect the
instance TCP/IP settings.
4.
In the TCP/IP Properties dialog box, on the IP Addresses tab, determine the currently
assigned port number.
If the TCP Dynamic Ports dialog box contains 0, this indicates that the Database
Engine is listening on dynamic ports. The IPAll dialog contains the port number used
by the SQL Server named instance you selected.
64
Figure 18. TCP/IP Properties for the SQL Server named instance
5.
Click Cancel to close TCP/IP Properties.
6.
You can validate port number discovery using the netstat program.
Connect to the Database Engine with SQL Server Management Studio from a
remote machine. On the machine hosting SQL Server, issue the netstat command
and inspect the Local Address and Foreign Address columns. Find a matching pair
(or pairs) of addresses that represents your remote connection to the SQL Server. The
Local Address column contains the port number associated with the local machine
(separated by a colon from the IP address).
65
66
APPENDIX B
Protocols Supported by VAS
Table 5. Protocols supported by VAS
Analyzer
Protocol Version
Limitations
Example application
Cerner over
TCP
Cerner
over
TCP
Cerner 2005, Cerner
2007
Cerner Millennium
Cerner over
MQ
Cerner
over
MQ
Cerner 2007
Cerner Millennium
DNS
DNS
RFC 1035
UDP-based DNS only.
No support for multi-query
requests.
DRDA (DB2)
DRDA
(DB2)
DRDA version 2
Exchange/RPC Exchange MS Exchange 2003,
2007
Generic
TCP
RFC 793
Generic (with
transactions)
TCP
RFC 793
HTTP
HTTP
1.1, 1.0 (RFC 2616)
IBM DB2 Universal
Database 8.1
Encryption at application
level is reported as
“Encrypted transaction”
Microsoft Exchange
Server 2003
Advanced analysis for
GET/POST methods. For all
other methods, including
WebDAV, every hit is
reported separately.
No pipelining.
67
Appendix B ∙ Protocols Supported by VAS
Analyzer
Protocol Version
Limitations
Example application
IBM MQ
IBM
MQ
Traffic for channels with
encryption is not
monitored.
WebSphere
WebSphere 6.0
•
Traffic between
MQ servers,
(Manager to
Manager) and
between MQ
clients and MQ
servers can be
analyzed.
•
Dynamic queue
names are
recognized.
•
Persistent TCP
sessions are
supported.
Traffic for channels with
header compression is not
monitored.
message
segmentation is not
supported.
MQGET
68
ICA (Citrix)
Citrix
4 and 4.5
Citrix Metaframe
Presentation Server
ICA (Citrix)
Citrix
5.0 and 6.0
Citrix XenApp
ICMP
ICMP
RFC 792
Informix
Informix IDS 7.31, IDS 9.40
IP
IP
RFC 791
Jolt (Tuxedo)
Jolt
8.1
BEA Tuxedo
Kerberos
SMB
Microsoft Kerberos 5
All Microsoft
Windows systems that
use the SMB 1.0
protocol. (Tested on
Windows 2000 and
Windows XP.)
Oracle
Net8
9i, 10g R1, 10g R2,
11g R1
No support for TDE
Oracle 9i, 10g, 11g
encryption in Net8 10g R2.
If TDE encryption is
enabled, the Oracle
analyzer stops reporting
performance data.
Oracle
Applications
over HTTP
HTTP
1.1, 1.0 (RFC 2616)
Monitoring applications
using HTTP protocol may
register excessive traffic.
For more information, see
Informix Dynamic
Server
Oracle E-Business
Suite 11i
Oracle E-Business
Suite 12
Analyzer
Protocol Version
Limitations
Example application
Oracle
Applications
over HTTPS
HTTPS
HTTP 1.1
encapsulated in SSL,
SSL 3.0, TLS1.0 (RFC
2246)
Supported Packaged
Applications in the
Vantage for Real User
Monitoring – System
Administration Guide.
SSL support.
Oracle Forms
over HTTP
Oracle
Forms
6i, 10.1
Oracle Forms 6i
Oracle Application
Server 9i, 10i, 10g R2
Oracle Forms
over TCP
SSL support.
Oracle Forms
over SSL
Oracle Forms
over HTTPS
SAP GUI
SAP
6.40, 7.10
GUI
protocol
(DIAG)
SAP GUI for Java
7.10rev8, Windows
SAP GUI v.7.10, SAP
GUI Console
Siebel over
HTTP
HTTP
Siebel over
HTTPS
HTTPS
SMB
SMB
SMB 1.0
All Microsoft
Windows systems that
use the SMB 1.0
protocol. (Tested on
Windows 2000 and
Windows XP.)
SMTP
SMTP
RFC 821
Supported commands:
Only mail servers that
HELO/EHLO, MAIL FROM,
use the SMTP
RCPT TO, DATA, QUIT, RSET, protocol (TCP/25)
VRFY, HELP, EXPN, NOOP (no
support for: SEND, SOML,
SAML, TURN
1.1, 1.0 (RFC 2616)
A special parameter
Siebel CRM 7.8.2.0.
configuration is
SSL support.
recommended for
HTTP 1.1
analyzing Siebel
encapsulated in SSL, applications. For more
SSL 3.0, TLS1.0 (RFC information, see Global
2246)
Settings for Recognition
and Parsing of URLs in
the Vantage for Real User
Monitoring – System
Administration Guide.
Multi-part attachments are
always saved in one piece
69
Analyzer
Protocol Version
Limitations
Example application
(no segmentation is
preserved).
MS Exchange Server
native RPC protocol and
POP3 (e-mail download)
are not supported.
SOAP over
HTTP
SOAP
SOAP 1.1 and 1.2
Support for Remote
Procedures Calls only.
SOAP over
HTTPS
Any business
application that uses
SOAP for data
exchange over the
network.
SSL support.
SSL
HTTPS
SSL Decrypted
HTTP 1.1
encapsulated in SSL
56-bit DES is not
supported.
SSL 3.0,
Only RSA Key Exchange
Algorithm supported.
TLS1.0 (RFC 2246)
SSL support.
GET/POST methods only; no
pipelining.
Only a 1024-bit SSL key
supported on CryptoSwift
SSL cards.
Open SSL supports
1024-bit, 2048-bit, and
4096-bit keys.
nCipher cards support
1024-bit, 2048-bit, and
4096-bit keys.
Cavium NITROX XL
FIPS cards support
1024-bit and 2048-bit
keys.
TCP
TCP
RFC 793
TDS
TDS
5.0, 7.0, 8.0
MS SQL Server 7.0,
2000, 2005, 2008
Sybase 10.0, Sybase
Adaptive Server
Enterprise (ASE) 15
70
UDP
UDP
RFC 768
VoIP
RTP,
RTCP,
G.711,
RFC-3261, RFC-3550, ITU-T G.107 E-Model
ITU-T G.107, G.711, quality metrics
G.721, G.722,
(MOS/R-Factor) are only
Analyzer
XML
Protocol Version
Limitations
H.323, G.723.1, G.726,
SIP,
G.728, G.729,
UniStim H.225.0, H.245, H.323
(Nortel)
supported when an RTP
voice conversation is
monitored by a companion
RTCP conversation.
XML
XML over SSL
W3C recommendation Encapsulated in TCP, in
1.0 and 1.1
HTTP, and in HTTPS
Example application
SSL support.
XML over
HTTP
XML over
HTTPS
XML over MQ XML
MQ
XML: W3C
recommendation 1.0
and 1.1
MQ: WebSphere 6.0
XML encapsulated in MQ.
MQ traffic for channels
with encryption is not
monitored.
MQ traffic for channels
with header compression
is not monitored.
message
segmentation is not
supported.
MQGET
71
72
APPENDIX C
SQL Operations Performed During Report Server
Installation or Upgrade
The database installation process has two stages. Using the SQL Server administrator account,
the report server database, database user, and database user rights are set up. Then, using the
SQL user account created earlier, the database schema and all necessary tables and indexes are
set up and organized.
When you are asked for the sa password, this is because the installer needs it to:
•
Obtain SQL Server information
•
Set up databases
•
Set up a database user
•
Grant permissions to the database user
•
Set memory limit
During report server installation, none of the existing databases or users is modified. The installer
modifies only the Vantage for Real User Monitoring database you explicitly specify in the
installer dialog.
After the report server is installed, you can inspect the SQL scripts that were performed as the
sa user. The values you entered in the installer dialogs will be stored in the scripts. Go the to
report server's config directory, by default located in the C:\Program
Files\Compuware\VAS\config\sql\ms\setup path.
Example 1. SQL scripts stored on report server file system after installation
C20Database.sql
C30DomainLogin.sql
C30Login.sql
C50DomainUserRights.sql
C50UserRights.sql
SetMaxMemory-curr.sql
SetMaxMemory-max.sql
SetMaxMemory-recc.sql
SetMaxMemory.template
After installation, the database owner password is stored by the report server so that important
maintenance tasks could be performed. For more information, see Considerations for Report
73
Appendix C ∙ SQL Operations Performed During Report Server Installation or Upgrade
Server Database Migration in the Vantage for Real User Monitoring – System Administration
Guide.
Non sa-related part of installation
After the SQL Server environment is ready, the sa user account is logged out and the user
account defined during the installation is logged in to finish database setup.
A log of this part of the database installation is stored in:
C:\Program Files\Compuware\VAS\log\install\maintainDBTables_stdout.log
Database Creation
Network Delta, the main report server database, stores all data presented by the report server.
C20Database.sql is the script executed to create the database on SQL Server. The values of
the variables set in this script are gathered by the report server installer in the Database
Connection Properties, Database Size, and Database Server Memory Setting dialog boxes.
The database parameter settings made by the installer program are the following:
•
Automatic shrinking is turned off
•
Automatic statistics creation is turned on
•
Checking for out-of-date statistics is turned on
•
Simple Recovery model is turned on
•
SQL_Latin1_General_CP1_CI_AS
is used as the SQL collation
The variables used in the script are the following:
ND_DB_DATABASE
The name of the database. You enter the name in the installer in the Database Connection
Properties dialog box, in the Name of database box.
ND_DB_DATABASE_dat
The name of the database file on the SQL Server file system.
ND_DB_DEVICE
Where the database files are stored. You enter the value as the Database device location.
ND_DB_SIZE
The size of the database. The recommended size is calculated by the installer, but you can
override the calculated value in the Database Size dialog box.
ND_DB_DATABASE_log
The name of the database log file on the SQL Server file system. The name is the value
of the ND_DB_DATABASE variable with _log appended to it.
ND_LOG_DEVICE
The physical location of the database log file. The location is the same as for the database
file.
ND_LOG_SIZE
Database log size is calculated automatically based on the size of the database. This should
be about 0.25% of the database size.
74
Example 2. C20Database.sql script
if not exists (select * from master.dbo.sysdatabases where name = '$ND_DB_DATABASE')
begin
CREATE DATABASE $ND_DB_DATABASE
ON PRIMARY
( NAME = '$ND_DB_DATABASE_dat',
FILENAME = '$ND_DB_DEVICE',
SIZE = $ND_DB_SIZE,
FILEGROWTH = 10% )
LOG ON
( NAME = '$ND_DB_DATABASE_log',
FILENAME = '$ND_LOG_DEVICE',
SIZE = $ND_LOG_SIZE )
end
GO
/* Set database options */
alter database $ND_DB_DATABASE set AUTO_SHRINK OFF
GO
alter database $ND_DB_DATABASE set AUTO_CREATE_STATISTICS ON
GO
alter database $ND_DB_DATABASE set AUTO_UPDATE_STATISTICS ON
GO
alter database $ND_DB_DATABASE set RECOVERY SIMPLE
GO
alter database $ND_DB_DATABASE COLLATE SQL_Latin1_General_CP1_CI_AS
GO
CHECKPOINT
GO
reconfigure with override
GO
The database remains empty at this point. Tables and other structures are created later, after the
sa user logs out and the installer logs in as the default database user to finish setting up the
database.
Creating a Database User
You can select a Windows domain account or a regular database account to create a new database
user.
For more information, see Performing the Installation [p. 26].
Depending on your choice, the installer will execute either C30DomainLogin.sql or
C30Login.sql. For more information, see Create Windows domain user as a database user
(C30DomainLogin.sql) [p. 75] and Create a database user (C30Login.sql) [p. 76].
Create Windows domain user as a database user (C30DomainLogin.sql)
If you choose a Windows domain user (when you enter a string of the form domain\user in
the Name of database user box) as the default report server database user, the installer
automatically recognizes this and tries to set up the provided user as the default database user.
The domain\user is split into variables ND_DB_DOMAIN and ND_DB_LOGIN. They will be used
later by a script that sets domain user rights for the database. For more information, see Database
User Rights [p. 76].
75
Example 3. C30DomainLogin.sql script
USE master
GO
if not exists (select * from syslogins where name = '$ND_DB_DOMAIN\$ND_DB_LOGIN' )
begin
CREATE LOGIN [$ND_DB_DOMAIN\$ND_DB_LOGIN] FROM WINDOWS WITH
DEFAULT_DATABASE=[$ND_DB_DATABASE]
end
GO
ALTER LOGIN [$ND_DB_DOMAIN\$ND_DB_LOGIN] WITH DEFAULT_DATABASE = $ND_DB_DATABASE
GO
Create a database user (C30Login.sql)
The default database user name is entered in the Name of database user box and the password
for that user is determined in the Database user password box. The value of ND_DB_LOGIN is
substituted by the user name you provided. The user's default database (ND_DB_DATABASE)
becomes the database you provided in the installer's Name of database box.
Example 4. C30Login.sql script
USE master
GO
if not exists (select * from syslogins where name = '$ND_DB_LOGIN' )
begin
CREATE LOGIN $ND_DB_LOGIN WITH PASSWORD = 'tmpPswdCh@ngedInNextScript123',
DEFAULT_DATABASE = $ND_DB_DATABASE, CHECK_POLICY = OFF
end
GO
ALTER LOGIN $ND_DB_LOGIN WITH DEFAULT_DATABASE = $ND_DB_DATABASE
GO
The password is set by a procedure that does not log the password or store it in a file on a hard
disk.
Database User Rights
A database user with certain rights is required during the report server installation and operation.
These rights can be assigned by executing one of the following SQL scripts.
To this end, a database schema is created and then a set of rights is granted to the database user.
These rights include:
76
•
Backing up the database
•
Backing up the database log
•
Connecting to the database
•
Verifying the database state
•
Creating tables, procedures, and functions
•
Executing the select command on tables in which information on tables and indexes is
kept
•
Checking whether the database needs defragmenting
The database user must be able to verify that the database structure is consistent and that the
required tables, columns, and indexes exist. The default database user is also assigned the role
of bulkadmin so that records can be inserted into the database in the fastest possible way.
Set domain user rights
C50DomainUserRights.sql
is the script executed when the database user was set to be a
Windows domain user.
Example 5. C50DomainUserRights.sql script
USE $ND_DB_DATABASE
GO
if db_name() != '$ND_DB_DATABASE'
begin
raiserror('error: cannot create login, database ''$ND_DB_DATABASE'' does not
exist.',22,127) with log
return
end
GO
if not exists (select * from sysusers where name = '$ND_DB_DOMAIN\$ND_DB_LOGIN' and uid
< 16382)
begin
create user [$ND_DB_DOMAIN\$ND_DB_LOGIN] for login [$ND_DB_DOMAIN\$ND_DB_LOGIN] with
default_schema = [$ND_DB_DOMAIN\$ND_DB_LOGIN]
exec('create schema [$ND_DB_DOMAIN\$ND_DB_LOGIN] authorization
[$ND_DB_DOMAIN\$ND_DB_LOGIN]')
end
GO
grant
grant
grant
grant
grant
grant
grant
grant
backup database to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
backup log to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
connect to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
create table to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
view database state to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
create procedure to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
create function to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
create view to [$ND_DB_DOMAIN\$ND_DB_LOGIN]
grant
grant
grant
grant
grant
grant
grant
grant
grant
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
ON
ON
ON
ON
ON
ON
ON
ON
ON
sys.tables TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
sys.objects TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
sysobjects TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
sys.indexes TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
sysindexes TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
sys.columns TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
syscolumns TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
sys.all_columns TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
sys.database_principals TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
RECONFIGURE WITH OVERRIDE
GO
--------------------------------------------------------------------------------USE master
-- Ensure that the report user is allowed to invoke DBCC command.
GRANT VIEW SERVER STATE TO [$ND_DB_DOMAIN\$ND_DB_LOGIN]
EXEC sp_addsrvrolemember '$ND_DB_DOMAIN\$ND_DB_LOGIN', 'bulkadmin'
Set database user rights
is the script executed when the default database user is set up on the
database server directly.
C50UserRights.sql
77
Example 6. C50UserRights.sql script
USE $ND_DB_DATABASE
GO
if db_name() != '$ND_DB_DATABASE'
begin
raiserror('error: cannot create login, database ''$ND_DB_DATABASE'' does not
exist.',22,127) with log
return
end
GO
if not exists (select * from sysusers where name = '$ND_DB_LOGIN' and uid < 16382)
begin
create user $ND_DB_LOGIN for login $ND_DB_LOGIN with default_schema = $ND_DB_LOGIN
exec('create schema $ND_DB_LOGIN authorization $ND_DB_LOGIN')
end
GO
grant
grant
grant
grant
grant
grant
grant
grant
backup database to $ND_DB_LOGIN
backup log to $ND_DB_LOGIN
connect to $ND_DB_LOGIN
create table to $ND_DB_LOGIN
view database state to $ND_DB_LOGIN
create procedure to $ND_DB_LOGIN
create function to $ND_DB_LOGIN
create view to $ND_DB_LOGIN
grant
grant
grant
grant
grant
grant
grant
grant
grant
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
ON
ON
ON
ON
ON
ON
ON
ON
ON
sys.tables TO $ND_DB_LOGIN
sys.objects TO $ND_DB_LOGIN
sysobjects TO $ND_DB_LOGIN
sys.indexes TO $ND_DB_LOGIN
sysindexes TO $ND_DB_LOGIN
sys.columns TO $ND_DB_LOGIN
syscolumns TO $ND_DB_LOGIN
sys.all_columns TO $ND_DB_LOGIN
sys.database_principals TO $ND_DB_LOGIN
GO
--------------------------------------------------------------------------------USE master
-- Ensure that the report user is allowed to invoke DBCC command.
GRANT VIEW SERVER STATE TO $ND_DB_LOGIN
EXEC sp_addsrvrolemember '$ND_DB_LOGIN', 'bulkadmin'
Set Memory Size
The memory size used by SQL Server can be defined by the user during installation.
At installation time, the system checks the available amount of memory and recommends a
value to the user, who can use the recommended setting or enter another one. For more
information, see Performing the Installation [p. 26].
The current setting on SQL Server is saved in the file SetMaxMemory-curr.sql, the memory
size is increased to the maximum so that the installer (which is run by the script in file
SetMaxMemory-max.sql) has the best conditions to proceed, and then either the memory size
is restored (again with the use of the file SetMaxMemory-curr.sql) or set to a recommended
value with the help of the file SetMaxMemory-recc.sql.
78
Example 7. SetMaxMemory.template script template
This template is used by the installer to create the SetMaxMemory-curr.sql,
SetMaxMemory-max.sql and SetMaxMemory-curr.sql scripts.
USE master
EXEC sp_configure 'show advanced option', '1'
GO
EXEC sp_configure 'awe enabled', '1'
GO
EXEC sp_configure 'min server memory', '0'
GO
EXEC sp_configure 'max server memory', '$SQL_MAX_MEMORY'
GO
EXEC sp_configure 'min server memory', '$SQL_MIN_MEMORY'
GO
79
80
Index
64-bit
41
migrating report server to 41
A
DNS 67
DRDA (DB2)
67
VAS 67
E
AMD
19
hardware platforms 19
analyzer
67
supported by VAS 67
B
basic configuration settings 47
browser
13, 15
configuring 13
localization 15
versions supported 13
C
Compuware License Service 57
configuration
13, 23, 33
browser 13
Microsoft SQL Server 23
VAS 33
D
DB2 (DRDA)
67
VAS 67
decode
67
supported by VAS 67
DLM 57
Exchange/RPC 67
H
hardware
19
recommended platforms 19
HTTP 67
HTTPS 33, 53
I
IBM WebSphere MQ 67
ICA (Citrix) 67
ICMP 67
Informix 67
installation
17, 22, 25–26, 51, 55
changing database user password 55
changing report server settings 51
VAS 17, 25–26
international features support
15
character encoding 15
localized browser 15
localized server 15
IP 67
J
Jolt 67
81
Index
report server (continued)
supported browsers 13
troubleshooting 61
upgrading 35
RUM
19
system requirements 19
K
Kerberos 67
L
licensing
57–59
ADS 59
AMD 59
report server features 58
supported features 59
types 57
VAS 59
localization
15
browser 15
character encoding 15
server 15
logging in to report server 45
M
media browser 25
20, 22–23, 73–76, 78
configuration 23
installation 22, 73–76, 78
setup recommendations 22
version recommendations 20
migrating to 64-bit
41
VAS 41
O
SAP GUI 67
security
53, 55
report server access 53
Siebel 67
site
49
configuration 49
SMB 67
SMTP 67
SOAP 67
SQL Server, See Microsoft SQL Server
SSL 67
system requirements
13, 19–20, 22–24
22–23
configuration 23
installation 22
recommended operating system configuration 20
recommended software 20
supported browsers 13
VAS 24
T
Oracle 67
TCP 67
TDS 67
Tier 1
P
personality of VAS installations 47
protocol
67
analyzer 67
supported by VAS 67
R
release information
12
VAS 12
report server
13, 19–20, 33, 35, 51, 53, 55, 61
changing installation settings 51
changing port number 53
communication over HTTPS 33, 53
hardware platforms 19
recommended software 20
secure communication 33, 53
82
S
19
hardware classes 19
Tier 2
19
hardware classes 19
troubleshooting
61
installation and upgrade 61
U
UDP 67
upgrading
35, 41
VAS 35, 41
user
49
aggregation 49
tracking 49
Index
V
Vantage Analysis Server, See VAS
VAS
11–12, 24, 49, 67
configuration
49
modifying basic settings 49
release information 12
supported protocols 67
VAS (continued)
system requirements 24
VCAEUE Console
55
Java Web Start 55
VoIP 67
X
XML 67
83
Index
84

Vantage Analysis Server Installation Guide

Transcription

Similar documents

Atlantis Energy Systems Inc.

Regions CD Check Viewer Installation Guide

QuadraTec™ - Auralex Acoustics

Products_files/6 (catalogo DECO PROJECTS.EN)

aerocet 6650 installation pricing

Glass instructions

model vp180.b5 - Visiport Spin Window Systems

Company Profile

Time Matters

Giuliana Rancic - Stephanie Stephens