Dynatrace Network Analyzer

(1)

Dynatrace Network Analyzer

Installation Guide

(2)

Please direct questions about Dynatrace Network Analyzer or comments on this document to:

Customer Support

https://community.compuwareapm.com/community/display/SUPPORT

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

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

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

Adobe®_Reader®_{is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries.} All other company and product names are trademarks or registered trademarks of their respective owners.

(3)

C H A P T E R 1

Dynatrace Network Analyzer System

Requirements

Be sure to review the following requirements and recommendations before installing Dynatrace Network Analyzer (DNA) console or agent software.

NOTE

The term “console” refers to the main DNA software that is installed on a Windows machine, probably on your own desktop. You use the DNA console software to analyze application traffic data you have gathered from the network.

The term “agent” refers to the Dynatrace Network Analyzer Agent software that you install on various Windows or Unix machines carrying the network traffic you want to analyze.

You use DNA agents to gather data from various points in your network and use the DNA console software to correlate and analyze this data.

DNA System Requirements

The following are the minimum system requirements for the Dynatrace Network Analyzer console and agent.

DNA Console Hardware Requirements

The following are minimum hardware requirements for the DNA console. • Pentium III processor, 1.4 GHz

• 2 GB RAM

We recommend the following basic system: • Intel Core 2 duo, 2.13 GHz

• 3 GB RAM

Additional hardware minimum requirements:

(8)

• Video card and monitor (at least 16-bit color and 1024x768 bit or higher screen resolution) • Ethernet (10 Mbps, 100 Mbps, or 1 Gbps), use enhanced-mode 32-bit NDIS 3.0 or

higher-compatible promiscuous mode network cards.

DNA Console Operating System Compatibility

The Dynatrace Network Analyzer console software can run on any of the following Microsoft Windows versions.

• Windows Server 2008 (32-bit and 64-bit versions) with Service Pack 2 • Windows Server 2008 R2 (64-bit version) with Service Pack 1

• Windows 7 (32-bit and 64-bit versions) with Service Pack 1 • Windows 8 (32-bit and 64-bit versions)

• Windows 8.1 (32-bit and 64-bit versions) • Windows Server 2012

• Windows Server 2012 R2 NOTE

All platforms should have version 3.1 of the Windows Installer. If you are not running automatic Windows updates, you can find the Windows 3.1 Installer at http://update.microsoft.com/ and on the Dynatrace Setup browser Utilities tab.

DNA Console Other Software Requirements

The following are other software requirements for the DNA console.

• Microsoft Internet Explorer 9.0 or later is required for full DNA functionality. Compatibility Mode is not supported. No tablet or smart phone browsers are supported. You can use the latest stable release of Mozilla Firefox or Google Chrome for most DNA functionality, but be aware that the Browser Data Collection (BDC) add-in works only with Microsoft Internet Explorer.

To use BDC, Internet Explorer must permit third-party browser extensions to operate. By default, Windows 2008 Server does not do so. To change this setting:

1. Open Internet Explorer.

2. Select Tools ➤ Internet Options.

3. Click the Advanced tab.

4. Under Browsing, select Enable third-party browser extensions and click OK.

5. Restart Internet Explorer.

• To use the Transaction Expert tool, one of the following versions of Microsoft Word must be installed:

◦ Microsoft Word 2007

(9)

◦ Microsoft Word 2010 ◦ Microsoft Word 2013

• One of the SQL Server versions listed below must be installed and running prior to running Dynatrace Network Analyzer.

◦ SQL Server 2005 Express ◦ SQL Server 2005 ◦ SQL Server 2008 Express ◦ SQL Server 2008 ◦ SQL Server 2008 R2 ◦ SQL Server 2012 Express ◦ SQL Server 2012

If none of these are detected on your machine during installation, the Dynatrace Network Analyzer installer offers to install SQL Server Express. Migration tools are provided with Dynatrace Network Analyzer to migrate your existing databases. Dynatrace Network Analyzer currently is designed to support a dedicated per-user database and requires exclusive-use locks at the database level.

Additional DNA System Recommendations

The following are recommendations (not requirements) for improving processing on the Windows machine on which you have installed the DNA console software.

• Increase the amount of RAM in your system. • Install a faster processor.

• Install the Dynatrace Network Analyzer database on an SSD disc.

• Install your Dynatrace Network Analyzer database locally; performance may significantly degrade when using a remote database.

• Do not run other applications on your system when you are capturing traffic on the Dynatrace Network Analyzer console.

• Do not use a PCMCIA network adapter card in a 100 Mbps environment.

Recommendations When Using Unattended Capture Mode

A dedicated computer is recommended when using Unattended Capture Mode. Network traffic volume varies greatly depending on the network. The amount of this traffic affects the size of the hard disk you need. If you plan to use disk caching, your agents require a large amount of RAM and a large amount of free hard disk space.

Agent System Requirements

The Dynatrace Network Analyzer Agent can be installed on a variety of Windows and Unix/Linux platforms.

(10)

Windows DNA Agent System Requirements

The following are system requirements for a Windows machine running this release of DNA Agent software.

IMPORTANT

The Windows version of the DNA Agent software is designed to run on Windows systems as described below. The agent will not function on an Itanium system.

Operating System Requirements

A Windows system must have one of the following operating system versions to run the DNA Agent software:

• Windows Server 2008 (32-bit and 64-bit versions) with Service Pack 2 • Windows Server 2008 R2 (64-bit version) with Service Pack 1

• Windows Server 2008 R2 Server Core

• Windows 7 (32-bit and 64-bit versions) with Service Pack 1 • Windows 8 (32-bit and 64-bit versions)

• Windows 8.1 (32-bit and 64-bit versions) • Windows Server 2012

• Windows Server 2012 R2

• Windows Server 2012 Server Core • Windows Server 2012 R2 Server Core

Minimum Hardware Requirements

Following are the minimum system requirements for the DNA Agent. • IBM or compatible PC with Pentium III 1.2 GHz or faster processor • 1 GB RAM

Hard disk space:

A minimum of 35 MB of available hard disk space is required for temporary storage. For Unattended Capture Mode, you may need more disk space. We recommend 2 GB. NIC

Ethernet (10 Mbps, 100 Mbps or 1 Gbps), use enhanced-mode 32-bit NDIS 3.0 or higher-compatible promiscuous mode network cards.

(11)

Additional Software Required

Windows 3.1 Installer

All platforms should have the Windows 3.1 Installer. If you are not running automatic Windows updates, you can find the Windows 3.1 Installer at www.microsoft.com and on the Dynatrace Setup browser Utilities tab.

Additional System Recommendations When Using Unattended Capture Mode A dedicated computer is recommended when using Unattended Capture Mode. Network traffic volume varies greatly depending on the network. The amount of this traffic affects the size of the hard disk you will need. If you plan to use disk caching, your agent will require a large amount of RAM and a large amount of free hard disk space.

Unix Dynatrace Network Analyzer Agent System Requirements

The following are requirements for a Unix system running this release of the DNA agent software. This release of the DNA Unix agent supports the following systems:

IMPORTANT

Be sure to inspect the library requirements listed in this document for each of your platforms. Some libraries that were not required for earlier versions of the DNA Unix agent are now required starting with agent version 11.0.

Solaris

The following Solaris systems are supported:

• Solaris 8 32-bit and 64-bit (SPARC platform only) NOTE

Older versions of Solaris 8 SPARC may not have the libsendfile.so.1 library and older versions of DNA did not require it, but libsendfile.so.1 is required by DNA agent 11.0 and later, so be sure that it is included on any Solaris 8 SPARC platform.

• Solaris 9 32-bit and 64-bit (SPARC platform only)

• Solaris 10 32-bit and 64-bit (SPARC & Intel/AMD x86 platforms) NOTE

Solaris 10 (Intel/AMD x86 platforms) may have an older version of the older libc.so.1 library. This was sufficient for DNA agent 10.2, but a newer version of this library is required by DNA agent 11.0 and later, so be sure to update the libc.so.1 library on any Solaris 10 (Intel/AMD x86 platform) platform.

In all cases, be sure that your Solaris system meets these requirements:

Solaris SPARC dynamic library requirements:

• libpthread.so.1 (SUNW_1.2)

(12)

• libnsl.so.1 (SUNW_0.7, SUNWprivate_1.1)

• libsocket.so.1 (SUNW_1.4)

• libCrun.so.1 (SUNW_1.1)

• libm.so.1 (SUNW_1.1)

• libw.so.1 (SUNW_0.8)

• libc.so.1 (SUNW_1.18, SUNWprivate_1.1)

• librt.so.1 (SUNW_0.7): Required by DNA agent 11.0 and later.

• libsendfile.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later.

• libthread.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later.

Solaris i386 dynamic library requirements:

• libpthread.so.1 (SUNW_1.2)

• libnsl.so.1 (SUNW_1.7, SUNWprivate_1.1)

• libsocket.so.1 (SUNW_1.4)

• libCstd.so.1 (SUNW_1.1.1, SUNW_1.4)

• libCrun.so.1 (SUNW_1.4)

• libm.so.2 (SUNW_1.2)

• libc.so.1 (SUNW_1.22.1, SUNWprivate_1.1)

• librt.so.1 (SUNW_0.7): Required by DNA agent 11.0 and later.

• libsendfile.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later.

• libthread.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later.

Solaris hardware requirements:

• 5 MB plus capture buffer RAM (128 MB minimum system RAM recommended) • 30 MB disk space plus sufficient space for capture temp files

• 1 or more NICs running TCP/IP protocol

IBM AIX

The following IBM AIX systems are supported: • IBM AIX 5.3 32-bit and 64-bit

• IBM AIX 6.1 • IBM AIX 7.1

In all cases, be sure that your IBM AIX system meets these requirements:

• The bos.net.tcp.server fileset must be applied on AIX systems.

(13)

Libraries required for AIX: • /usr/lib/libpthreads.a(shr_comm.o) • /usr/lib/libpthreads.a(shr_xpg5.o) • /usr/lib/libC.a(shr3.o) • /usr/lib/libC.a(shr2.o) • /usr/lib/libC.a(shr.o) • /usr/lib/libcrypt.a(shr.o) • /usr/lib/libc.a(shr.o) • /usr/lib/libC.a(ansi_32.o)

• /usr/lib/libiconv.a(shr4.o): Required by DNA agent 11.0 and later.

HP-UX

The following HP-UX systems are supported: • HP-UX 11.11 32-bit and 64-bit

If you are installing the agent in an HP-UX 11.11 environment, you must apply patch PHSS_22898 for the C++ runtime library.

• HP-UX 11.23 32-bit and 64-bit • HP-UX 11.31 64-bit

In all cases, be sure that your HP-UX system meets these requirements:

• 1 or more NICs running TCP/IP protocol NOTE

The installer configures the agent without the capability to set network interfaces to promiscuous mode on HP-UX 11.00 and HP-UX 11.11 due to HP issue number JAGae83251 against HP-UX 11.00 and HP-UX 11.11. If promiscuous mode capture is required on these HP-UX releases, see the note regarding promiscuous mode capture in the troubleshooting section below.

Libraries required for HP:

• /usr/lib/libdld.2 • /usr/lib/libc.2 • /usr/lib/libcl.2 • /usr/lib/libisamstub.1 • /usr/lib/libm.2 • /usr/lib/libCsup_v2.2 • /usr/lib/librt.2

(14)

• /usr/lib/libpthread.1

• /usr/lib/libstd_v2.2

Linux

The following Linux kernel versions are supported: • Linux 2.4 32-bit Intel (libraries required; see below) • Linux 2.6 32-bit Intel (libraries required; see below)

• Linux 2.6 64-bit Intel EM64T/AMD64 (libraries required; see below)

This is not the same as the Linux distribution version. For example, Red Hat Enterprise Linux 3 is a Linux distribution based on the Linux 2.6 kernel, which is one of the kernel versions listed above. DNA agent 12.3 therefore supports Red Hat Enterprise Linux 3.

NOTE

To check your Linux kernel version, issue the command: % uname -r

and verify that the first two digits of the displayed kernel number are listed above. In all cases, be sure that your Linux system meets these requirements:

If you are installing the agent on a Linux machine, you must ensure your machine has the base C and C++ runtime libraries, sockets library, and threading libraries:

• libpthread.so.0 • libstdc++.so.6 or libstdc++.so.5 • libc.so.6 • libm.so.6 • libgcc_s.so.1 • libexpat.so.0

In Red Hat Linux distributions prior to release 6, these libraries were installed by default. In Red Hat Enterprise Linux 6, these libraries must be installed manually and may be available under different names.

The installation script checks the installed gcc version.

Libraries required for Linux systems with gcc 3.4.0 or higher:

• /usr/lib/libpthreads.a(shr_comm.o)

• /usr/lib/libpthreads.a(shr_xpg5.o)

• /usr/lib/libC.a(shr3.o)

(15)

• /usr/lib/libC.a(shr2.o)

• /usr/lib/libC.a(shr.o)

• /usr/lib/libcrypt.a(shr.o)

• /usr/lib/libc.a(shr.o)

• /usr/lib/libC.a(ansi_32.o)

• /usr/lib/libiconv.a(shr4.o): Required by DNA agent 11.0 and later.

Libraries required for Linux systems with gcc version below 3.4.0:

• libstdc++.so.5 (libstdc++.so.5.0.7): Required by DNA agent 11.0 and later.

• libpthread.so.0 (libpthread-2.3.4.so): Required by DNA agent 11.0 and

later.

• libm.so.6 (libm-2.3.4.so): Required by DNA agent 11.0 and later.

• libgcc_s.so.1 (libgcc_s-3.4.3-20050228.so.1): Required by DNA agent

11.0 and later.

• libc.so.6 (libc-2.3.4.so): Required by DNA agent 11.0 and later.

• /lib/ld-linux.so.2 (ld-2.3.4.so): Required by DNA agent 11.0 and later.

• libexpat.so.0 (libexpat.so.0.5.0): Required by DNA agent 11.0 and later.

NOTE

The 32-bit shared libraries are required for 64-bit Linux on amd64 and ia64 systems. These libraries are typically distributed as package ia32-libs.

Database Requirements

DNA uses a SQL database to store captured and imported data. This is done to ensure data integrity and the easy scaling of large numbers of traces.

IMPORTANT

We highly recommend a locally installed database for use with DNA. Performance may significantly degrade when using a remote database.

DNA currently is designed to support a dedicated per-user database and requires exclusive use locks at the database level. By default, Microsoft SQL Server Express is installed when you install DNA if a suitable SQL Server is not already installed. The engine loads when you start your computer so that it is available to support DNA.

Configuring an Existing SQL Server Installation

If you install Microsoft SQL Server Express during the DNA installation, it is automatically configured to work with DNA; skip to Installing Dynatrace Network Analyzer in the Dynatrace

Network Analyzer User Guide.

(16)

If SQL Server is already installed at the time DNA is installed, however, you must verify some SQL server settings manually before installing DNA:

Enabling TCP/IP

If SQL Server is already installed at the time DNA is installed, verify that TCP/IP is enabled.

1. Open the SQL Server Configuration Manager. NOTE

The location of SQL Server Configuration Manager depends on your SQL Server version. For SQL Server Express, click the Windows Start button and select Programs ➤ Microsoft

SQL Server [version] ➤ Configuration Tools ➤ SQL Server Configuration Manager.

2. In the SQL Server Configuration Manager navigation tree, open the Network Configuration branch and select Protocols for MSSQLSERVER.

3. The TCP/IP setting displayed in the right pane must have a status of Enabled for DNA to work. If it is not enabled, right-click TCP/IP and select Enable.

4. In the SQL Server Configuration Manager navigation tree, click the SQL Server Services branch.

5. In the right pane, right-click SQL Server and select Restart (or select Stop and then select

Start).

Enabling SQL Server Browser

If SQL Server is already installed at the time DNA is installed, verify that SQL Server Browser is enabled.

1. Open the SQL Server Configuration Manager. NOTE

The location of SQL Server Configuration Manager depends on your SQL Server version. For SQL Server Express, click the Windows Start button and select Programs ➤ Microsoft

2. Click SQL Server Services.

3. Right-click SQL Server Browser and select Properties. The SQL Server Browser Properties dialog box opens.

4. Click the Service tab.

5. Set Start Mode to Automatic and then click OK.

6. If SQL Server Browser is not already running, right-click SQL Server Browser and select

Start.

Enabling Server Authentication

If SQL Server is already installed at the time DNA is installed, verify that server authentication is enabled.

(17)

1. From the Windows Start button, select Programs ➤ Microsoft SQL Server [version] ➤

SQL Server Management Studio Express.

2. In the Registered Servers window, select the local server.

3. In the Object Explorer window, right-click the server and select Properties. The Server Properties dialog box opens.

4. On the Security page, select SQL Server and Windows Authentication mode and then click OK.

5. In the Object Explorer window, right-click the server and select Restart. Confirm the restart and wait for the server to restart.

6. In the Object Explorer window, open Security ➤ Logins, right-click the sa login, and select Properties.

The Login Properties dialog box opens.

7. On the General page, enter the sa password twice (Password and Confirm password).

8. On the Status page, set Login to Enabled and then click OK.

Changing Service Account to Local System

If SQL Server is already installed at the time DNA is installed, verify that Local System Account is selected.

1. From the Windows Start button, select Settings ➤ Control Panel ➤ Administrative

Tools ➤ Services.

2. Right-click SQL Server in the Services (Local) list and select Properties. The SQL Server Properties dialog box opens.

3. Click the Log On tab.

4. Select Local System Account and then click OK.

Migrating Existing Databases

DNA can migrate some older DNA database versions to the current version.

If you are upgrading from a previous version of DNA, the InstallShield will detect the earlier version of the software and database and will ask whether you want to migrate your database. Provide your database login information and click Next to migrate your database while the latest version of DNA is installed. This is the easiest and fastest way to migrate your database to the latest format.

If you choose to skip database migration during installation, however, you can still easily migrate your database later when you start DNA.

(18)

CAUTION

• Do not interrupt installation or migration processes.

• Migration is a one-way process. If you migrate an existing DNA database to DNA current format, the new database can be opened only by the current version of DNA, not by previous versions of DNA, and you cannot migrate it back to the older version. If you also want to continue working in the old version of DNA (on a different machine), you must keep a copy of the database in the old format. In such a case, back up the existing database before performing the migration.

• To avoid the possibility of data loss or corruption during software upgrade or database migration, you should always keep a recent backup of your database in a safe place.

Restricting SQL Service

When you enable TCP/IP for SQL service, it is automatically enabled for all IP addresses. To tighten security, you can restrict SQL Server to just the local address (127.0.0.1).

1. Open the SQL Server Configuration Manager.

The location of SQL Server Configuration Manager depends on your SQL Server version. For SQL Server Express, click the Windows Start button and select: Programs ➤ Microsoft

2. In the SQL Server Configuration Manager navigation tree, open the Network Configuration branch and select Protocols for MSSQLSERVER.

3. In the right pane, right-click TCP/IP and select Properties.

4. Change Listen All to No.

5. Click the IP Addresses tab.

6. Change the Active and Enabled settings to No for all entries except address 127.0.0.1, which must be set to Yes.

7. Click OK.

8. In the SQL Server Configuration Manager navigation tree, click the SQL Server Services branch.

9. In the right pane, right-click SQL Server and select Restart (or select Stop and then select

Start).

(19)

C H A P T E R 2

Installation

This chapter describes how to install Dynatrace Network Analyzer software on approved systems.

Console Installation

This section describes how to install the Dynatrace Network Analyzer console. If you are a previous user of Dynatrace Network Analyzer, you may be able to upgrade your existing installation and migrate your previous database to the new installation.

Assuming the DNA database is installed with SQL Server Express, provided with the DNA installation, and database size is less than 4 GB.

My time Estimating Criteria

Task/Factor

Each console must be upgraded by logging into the machine and manually upgrading it. Estimate How many DNA consoles are

installed?

up to 1 hour for each console installed (including database backup and upgrade), though you may be able to work on them in parallel.

Plan 0.5 hours for upgrade to complete on agents. How many agents to upgrade

automatically?

Plan on 0.25 hour for each agent to be upgraded. How many agents to upgrade

manually?

Perform a smoke test. Estimate 2 hours for console and agents.

Validate DNA is fully operational.

When you upgrade to release 12.3 from release 12.1 or 12.2, upgrade is automatic through the installer.

How many releases back is the console version you have installed?

When you upgrade to release 12.3 from an earlier version of DNA, however, you need to upgrade that earlier release to release 12.1 or 12.2 first, and then upgrade that installation to release 12.3. This will effectively double your console update time.

(20)

Task Duration Estimates

Assuming the DNA database is installed with SQL Server Express, provided with the DNA installation, and database size is less than 4 GB.

My time Estimating Criteria

Task/Factor

Each console must be upgraded by logging into the machine and manually upgrading it. Estimate How many DNA consoles are

installed?

up to 1 hour for each console installed (including database backup and upgrade), though you may be able to work on them in parallel.

Plan 0.5 hours for upgrade to complete on agents. How many agents to upgrade

automatically?

Plan on 0.25 hour for each agent to be upgraded. How many agents to upgrade

manually?

Perform a smoke test. Estimate 2 hours for console and agents.

Validate DNA is fully operational.

When you upgrade to release 12.3 from release 12.1 or 12.2, upgrade is automatic through the installer.

How many releases back is the console version you have installed?

When you upgrade to release 12.3 from an earlier version of DNA, however, you need to upgrade that earlier release to release 12.1 or 12.2 first, and then upgrade that installation to release 12.3. This will effectively double your console update time.

Upgrading Existing Console Installations

The Dynatrace Network Analyzer Release 12.3 console can be upgraded from Dynatrace Network Analyzer 12.1 or 12.2. Older Dynatrace Network Analyzer releases must be uninstalled before you can install the new version.

During the installation of Dynatrace Network Analyzer, you are prompted whether it is possible to upgrade your older version of Dynatrace Network Analyzer. If it is not possible, uninstall your older version before installing the new version. For more information, see Console Uninstallation - Interactive [p. 65].

Only one Dynatrace Network Analyzer release can be open at a time.

Installing SQL Server Management Studio Express

Some of the database management procedures in the DNA documentation are written with the assumption that you have installed SQL Server Management Studio Express, a tool that comes with Microsoft SQL Server Express. If you have not installed it already, we strongly recommend that you download and install Microsoft SQL Server Express.

1. Open web page http://www.microsoft.com/en-us/download/details.aspx?id=29062.

2. Download the appropriate installer for your system (32-bit or 64-bit).

(21)

3. Run the installer.

Additional installation instructions are included on the download page and in the software's readme file.

Migrating Existing Databases

DNA can migrate some older DNA database versions to the current version.

If you are upgrading from a previous version of DNA, the InstallShield will detect the earlier version of the software and database and will ask whether you want to migrate your database. Provide your database login information and click Next to migrate your database while the latest version of DNA is installed. This is the easiest and fastest way to migrate your database to the latest format.

If you choose to skip database migration during installation, however, you can still easily migrate your database later when you start DNA.

CAUTION

• Do not interrupt installation or migration processes.

• Migration is a one-way process. If you migrate an existing DNA database to DNA current format, the new database can be opened only by the current version of DNA, not by previous versions of DNA, and you cannot migrate it back to the older version. If you also want to continue working in the old version of DNA (on a different machine), you must keep a copy of the database in the old format. In such a case, back up the existing database before performing the migration.

• To avoid the possibility of data loss or corruption during software upgrade or database migration, you should always keep a recent backup of your database in a safe place.

Installing Dynatrace Network Analyzer Console

To perform this console installation procedure, you must be logged in as a user with administrative privileges.

Installations on computers that already have an older version of Dynatrace Network Analyzer or any Dynatrace product installed have a shorter installation procedure than computers that have never had a Dynatrace product installed. A full installation consists of installing: • Dynatrace Operating System Updates

• Dynatrace Network Analyzer • SQL Server Express

• Database

The installer automatically checks your computer for each of the above items. When an item is found, the installation step for that item is skipped.

1. Temporarily disable antivirus software on the target machine.

This is not necessary in all cases, but some antivirus software prevents DNA from installing.

(22)

2. Download the installation package from the Downloads section of the Dynatrace Community.

3. Extract the installation package into a temporary directory.

4. Double-click setup.exe in the installation package to open the installation browser.

5. On the Additional Products tab, click the Dynatrace Network Analyzer Console link. The DNA installer starts.

NOTE

• To install DNA, you must have administrator privileges for the target machine. • If you receive a Windows security message concerning the installer, click Install or

Run to continue with the installation.

• If you receive an OS Update Error, the target machine may need new certificates. For more information, see Installing Missing Certificates for DNA Installation [p. 29].

6. The Dynatrace operating system software is checked.

If updates are required, the necessary updates are listed. Review them and, if you are satisfied with the listed updates, click Next to make those updates and continue.

7. The installer program extracts the necessary files for DNA installation.

8. On the Welcome page, click Next.

9. On the License Agreement page, review the text of the license, select I accept the terms

in the license agreement, and then click Next to accept the terms of the license and begin

installing DNA.

10. Your computer is checked to see whether you have access to an appropriate SQL Server

instance.

If you do not, select Yes when prompted and click Next to install SQL Server Express. If you select No, you must otherwise arrange for this DNA installation to have access to an appropriate SQL Server instance. The Utilities tab of the media browser has a link that you can use at a later time to install it.

11. If you installed SQL Server Express in the previous step, you are now prompted to create

a password for the sa database administration account.

Type the new password twice, click Next, and wait while SQL Server is installed.

12. If you are upgrading DNA and you are asked to migrate the database, click Skip if you

don't want to migrate the database, or provide the SQL Server Instance, Database Name,

User Name, and Password and then click Next to migrate to the database.

13. On the Destination Folder page, review the default settings, change them if needed, and

then click Next.

14. On the Custom Setup page, select the Browser Data Collection, Documentation, Help,

and Trace Trimmer features you want to install and then click Next. By default, all features are installed.

Your computer is checked and you are warned if any system requirements are not met, but you are allowed to continue the installation. Click Back to discontinue the installation. Otherwise, click Next and continue responding to the requested information.

(23)

15. On the Promiscuous Mode page, you are asked to choose the capture type: either

promiscuous mode or non-promiscuous mode.

Leave the default selection (Yes) to have DNA capture all traffic the NIC card can see. Click No to have DNA capture only traffic to or from the NIC card itself. Click Next.

16. On the TCP Port Number page, provide the TCP port number for the DNA agent.

Click Next if your network does not have strict firewall policies and the default port of 2408 is suitable for your use. If the 2408 default port is not suitable for your use, click Yes and type the port information requested.

17. If this is a new installation, the Database Creation page appears; complete the database

information and click Next.

First select the database authorization method you want to use:

• Windows Authentication: If you select this method, access to DNA database will be

controlled by Windows user ID and password. The User name and Password fields on this page of the wizard will be hidden.

• SQL Authentication: If you select this method, access to DNA database will be

controlled by SQL user ID and password. Type the User name and Password information on this page of the wizard.

You can install the database on a remote server by selecting a server from the SQL Server

instance list, which displays all SQL server instances on your network. You can create the

database on any of these instances if you have the valid user ID and password for them. (You created a password for the user name sa in Step 11 [p. 22].) You can also enter the name or IP address of any other SQL Server. If the database you want to create already exists on the machine you select, you receive a message indicating that the database already exists on the server. You do not need to have DNA installed on the remote server to have the database installed on the server. If you choose a remote SQL Server, a database will be created but sample data will not be installed. If you want to have sample data, you will have to do it after installation using the database backup and restore tools.

Click Advanced if you want to change the install path, the database size, or the log size. DNA performance is adversely affected by use of a remote database. Each database can only be used by a single user at a time.

NOTE

• If this is an upgrade from an acceptable prior release, this dialog box does not appear. The default settings install the default database on your Microsoft SQL Server unless you make changes. Accept the defaults by clicking Next, unless you have a reason to customize the settings.

• If you skip this step, you will later have to create a DNA database (unless you have one from an earlier installation) and a Trace Trimmer database (required to use the Trace Trimmer trace filtering tool).

18. If you created a local database in Step 17 [p. 23], the Sample Data page asks whether you want to install sample data.

(24)

If you are new to DNA, you should select Yes to install the sample data. You can use the sample data to explore DNA without corrupting live data. Also, explanations in this documentation sometimes refer to examples from the sample database.

19. On the Ready to Install the Program page, review your selections, and then click Install

if they are correct.

You can use the Back button to go back and change settings, and then use Next to return to this point.

20. When the installation is finished, a Start ➤ Programs ➤ Compuware ➤ Dynatrace

Network Analyzer menu is created on the target machine.

The Dynatrace Network Analyzer menu includes: • Dynatrace Network Analyzer Agent Manager

• Dynatrace Network Analyzer User Guide

• Dynatrace Network Analyzer

• Get Support File

• Trace Trimmer

Before you use DNA:

• If you have disabled antivirus software on the target machine for DNA installation, be sure to enable it again.

• Reboot the machine. • Install a license.

• Disable network task offload. (Before capturing data, you must disable network task offload on your DNA machine. )

• Enable the Internet Explorer add-on from Dynatrace (Internet Explorer 9.0 and later, and only if you intend to use BDC). For more information, see Enabling Add-on for Internet Explorer [p. 25].

Disabling Network Task Offload

Network task offload is a Microsoft Windows feature for improving TCP/IP processing speed. However, it hides network traffic from DNA and thus may invalidate your network analysis. Before capturing data, you must disable network task offload on your DNA machine. NOTE

Disabling network task offload may degrade TCP/IP processing speed on that machine. To disable network task offload:

1. Click Start Search, right-click cmd, and choose Run as Administrator.

2. In the command shell, issue the following command:

netsh int ip set global taskoffload=disabled

(25)

You can copy the command from here, paste to the machine's command line, and press

[Enter]. There are no machine-specific parameters to change.

3. Reboot the machine before continuing to work with DNA.

Enabling Add-on for Internet Explorer

Starting with Microsoft Internet Explorer (IE) 9.0, all new IE add-ons are disabled by default. If you are going to use Browser Data Collection (BDC), you must enable the Dynatrace add-on called “InterceptorEventHandler”.

1. On the IE menu bar, select Tools ➤ Manage Add-ons.

2. In the “Compuware Corporation” section, select “InterceptorEventHandler” and click

Enable. 3. Restart IE.

Adding a Windows Firewall Exception for Mongoose

Mongoose is a third-party open-source component (web server) used by RTP 2.0.

If a Windows Security Alert states that “Windows Firewall has blocked some features” of a program called Mongoose when you first open Response Time Predictor 2.0, you should allow Mongoose to run and add an exception for Mongoose to your Windows Firewall.

User Accounts and Administrative Rights

The availability of some DNA features depends on user account privileges and how account privileges are managed by the machine's operating system.

Accounts with administrative rights

If the intended user's Windows account has administrative rights to the machine on which DNA is installed, all DNA features will be available to the user.

DNA by default runs with limited permissions even if the user account belongs to the

administrative group. To run DNA with administrative rights, you need to right-click the DNA icon or menu entry and specify that DNA should be run as an administrator.

Accounts without administrative rights but with AVUsers membership

If the intended user's Windows account does not have administrative rights to the machine on which DNA is installed, the system administrator should ensure that the intended user's Windows account is added to the Windows users group called AVUsers. The first time you run DNA on the intended user's account, you may see a message such as:

The current user does not have privileges to use full functionality of Dynatrace Network Analyzer. Do you want to elevate the current user's privileges? (You will need to provide administrator credentials to make this change.)

(26)

If you answer yes and provide administrator credentials, the user will be added automatically

to AVUsers. If you prefer to do so manually, see the Managing User Access Rights with AVUsers

Group Membership [p. 27] procedure for more information.

Adding a non-administrator user account to AVUsers will ensure that the user account has access to almost all DNA features. However, a small set of DNA features will remain unavailable to the user.

• The user will not be able to create a new database for Trace Trimmer.

Most users never need to create a new database for the Trace Trimmer trace filtering utility. • The user will be able to run the Get Support File utility for gathering system information

to report to customer support however, generated log will remain at info level only.

Accounts without administrative rights and without AVUsers membership If you do not add a non-administrator user account to AVUsers, the following additional items will be unavailable to that user:

• The user will not be able to change promiscuous mode for a local capture point. This is generally an important restriction.

• The user will not be able to access DNA databases using Windows authentication. To work around this, use the SQL Authentication or have the SQL administrator add the account manually to the DNA database using SQL Management Studio.

• In addition, restrictions described in Accounts without administrative rights but with AVUsers membership [p. 25] apply to the restrictions explained in this section.

To avoid these last two restrictions and minimize the need for administrator intervention, make the user's account a member of the AVUsers Windows users group where possible.

Running Dynatrace Network Analyzer for the First Time

After installing Dynatrace Network Analyzer, the system administrator should run Dynatrace Network Analyzer from the user's account to make sure the intended user has the appropriate access rights.

1. Log in to the intended user's account.

2. On the Windows desktop, double-click the Dynatrace Network Analyzer icon.

3. If you are prompted to do so, specify whether to elevate the current user's privileges. For more information, see User Accounts and Administrative Rights [p. 25] and Managing User Access Rights with AVUsers Group Membership [p. 27].

Click Yes to add the current Windows login to the list of users who can carry out

administrative-level actions through Dynatrace Network Analyzer. In this case, someone with Windows administrator privileges (presumably you if you are installing Dynatrace Network Analyzer) will have to enter admin-level login credentials to approve the selection. After approval, the original user can log back in to Windows and restart Dynatrace Network Analyzer.

Click No if you do not want to elevate the current user's privileges. Also select Do not ask

me this again if you do not want the current user to see this message again.

(27)

Managing User Access Rights with AVUsers Group Membership

Dynatrace Network Analyzer user rights are managed through a Windows user group named

AVUsers. To grant or deny a user access to Dynatrace Network Analyzer on the console machine,

manage the AVUsers Windows users group to add or delete that user's Windows user name.

1. In Windows, right-click My Computer and select Manage. The Computer Management dialog box is displayed.

2. In the navigation tree, select System Tools ➤ Local Users and Groups ➤ Groups.

3. In the list of user groups, double-click the AVUsers group. The AVUsers Properties dialog box is displayed.

This group normally is created automatically during Dynatrace Network Analyzer. If it does not exist, you should reinstall Dynatrace Network Analyzer or create the group manually (right-click the list of user groups and select New Group).

4. Click Add to add a user to the AVUsers group.

5. Type the Windows login name of the user you are adding to the AVUsers group, and then click OK.

That user now has administrative rights in Dynatrace Network Analyzer

DNA and VMware

DNA supports VMware environments with certain limitations. Follow Dynatrace guidelines to minimize the effects of running DNA in a VMware virtual environment.

Use hardware-based timing when possible

Virtual machine operations do not necessarily run in real time. For example, if a virtual machine is competing with other virtual machines for resources on a single piece of real hardware, an operation that would run in 1.0 seconds on a real (physical) machine might take 1.3 seconds of real time (time on the wall clock) to execute. The virtual machine might then attempt to make up for such a delay by executing another operation in less time than it would take to execute in real time.

In most cases, such minor adjustments go unnoticed, but they could make a difference in an application such as DNA in a virtual environment with a virtual clock. For example, a packet captured in the 11th real second since the (real) computer was turned on might be recorded as if it had arrived in the 8th second if the packet capture driver (running on a virtual machine) was not kept consistent with the underlying real time. Views that are affected to a degree dependent on the severity of the virtual timer are those that measure or allocate delay. These include CNS Breakdown, Performance Overview, Node Processing and Node Sending tables, Transaction Expert reports, and auto-adjustment (heuristic). For more information, see

http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf.

With DNA (console, agent, and Simple Capture) running on VMware ESX(i) 3.5 (or later) or VMware Workstation 6.5 (or later), you can now configure the driver to read the current time from the underlying host machine instead of depending on the (virtualized) operating system's time, which may be unsynchronized with real time.

(28)

For more information, see Enabling Hardware-Based Timekeeping in VMware Virtual Machines in the Dynatrace Network Analyzer - Help.

Use a separate VMware guest machine when possible

The preferred method for capturing network traffic in a VMware environment is to use a separate VMware guest machine dedicated to the Dynatrace Network Analyzer Agent.

• Make sure that this guest machine runs with high priority.

• Use the port spanning functionality available through the VMware vNetwork Standard Switch (vSS) or VMware vNetwork Distributed Switch (vDS). This configuration will allow the network traffic between VMware guest machines to be visible to the Agent machine. To learn more about vSS and vDS, see (external link)

http://www.vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf

Alternatively, you can install the Dynatrace Network Analyzer Agent directly on a guest machine. However, the additional processing performed by the machine may cause the virtual timing problem to be more pronounced.

NOTE

Some of the possible timing problems described below may be mitigated or negated if you can use the hardware-based timing method. For more information, see Use hardware-based timing when possible [p. 27].

VMware virtualization timing considerations affect some of DNA's performance analysis. Specifically, VMware's timer virtualization technique (called “apparent time”) allows a virtual timer to fall behind real time and then to catch up as needed. This time lag between the virtual machine and real time may reach a level greater than a millisecond. Such delays will be recorded in the time stamps in DNA traces.

These timing problems affect only the network trace capture phase. For trace analysis performed in the DNA console, it does not matter whether DNA runs in a VMware environment. It is accuracy of time stamps in the traces that matters.

For analyzing single trace files within DNA—without merging or adjusting to examine network delays—the following holds true:

• The inaccuracies resulting from using virtual time stamps will usually not be noticeable, and should have a negligible effect on most analyses. In these cases, views and functionality that offer byte/packet statistics, as well as protocol decodes, will not be affected beyond the loss of time stamp precision. These include the Packet Trace, Conversation Map,

Thread Analysis, Error Analysis, and Payload vs. Overhead views.

• Views that are affected to a degree dependent on the severity of the virtual timer are those that measure or allocate delay. These include CNS Breakdown, Performance Overview,

Node Processing and Node Sending tables, Transaction Expert reports, and

auto-adjustment (heuristic).

If the analysis will require merging or adjusting traces within DNA, extra caution may be required, especially if the network separating the capture points is low-latency. (High-latency WAN links easily mask most virtual time stamp inaccuracies.) For this reason, we do not

(29)

recommend merging trace files across low-latency links (< 20 milliseconds round-trip) where one of the trace files must come from a virtual machine. However, you may be able to use hardware-based timing on your virtual machine to mitigate this problem. For more information, see Use hardware-based timing when possible [p. 27].

Installing Missing Certificates for DNA Installation

If you receive an OS Update Error 1330 during Dynatrace Network Analyzer (DNA) installation, it indicates that the target machine requires a Windows update that includes certain required certificate updates, and that the machine does not have an Internet connection through which these updates could be made automatically.

If it is possible to give the target machine an Internet connection during DNA installation, you should do this and restart the installation process.

If you cannot give the target machine an Internet connection during DNA installation, or if the error occurs again after giving the machine an Internet connection, install the missing certificates manually before running the DNA installation:

1. On a machine that has an Internet connection, go to page:

https://search.thawte.com/support/ssl-digital-certificates/index?page=content&id=AR1406 2. Follow the instructions on that page for installing the “Code Signing Intermediate CA” and

“Thawte Primary Intermediate Root CA” certificates on the intended DNA machine. This will require you to create two certificate files manually, copy them to the intended DNA machine, and then use the Certificate Import Wizard in Microsoft Windows to install those certificates on the intended DNA machine.

3. After the certificates are installed, install DNA.

Trace Trimmer Configuration from Windows Control Panel

You can change some Trace Trimmer settings through the Windows Control Panel.

1. In Windows, select Start ➤ Control Panel.

2. Click Uninstall a program.

3. Select Dynatrace Network Analyzer Trace Trimmer.

4. Click Uninstall/Change.

5. Select the option you need to change and click Next. Options include:

• HTTP and SSL Server settings • Database user password

6. Change the configuration parameters.

7. Click Change.

8. Click Finish.

(30)

Agent Installation

Follow this procedure to install Dynatrace Network Analyzer Agent.

Remote capture using DNA can be performed on a variety of Windows and Unix/Linux machines on which you have installed the Dynatrace Network Analyzer Agent. (For a list of system requirements, see the Dynatrace Network Analyzer Agent release notes.)

Before anyone can perform remote captures on a machine using the Dynatrace Network Analyzer Agent, the agent must first be installed on that machine. The Dynatrace Network Analyzer Agent and the DNA console should not be installed on the same machine.

Importing of external third-party wireless LAN captures is not supported.

All platforms should have the Windows 3.1 Installer. If you are not running automatic Windows updates, you can download the Windows 3.1 Installer. For more information, see

http://update.microsoft.com.

Proper operation of wireless capture is dependent on the specific 802.11 adapter and Windows version in use. For many 802.11 adapters, you need to set the capture mode to non-promiscuous, with the consequence that the captured transaction traffic must be directed to/from the machine performing the capture. In other words, in non-promiscuous mode, the transaction needs to run from the machine performing the wireless DNA capture.

Capturing on wireless agent NICs is hardware dependent. DNA captures on most wireless NICs. For some wireless NICs you must reboot after installation or after changing the promiscuous mode setting.

To confirm proper operation of wireless capture, try capturing access to a Web page (HTTP traffic). Check to make sure the byte count is advancing during the capture. After completing the capture, go to the Payload View to verify that the packet content is correct.

During the installation of DNA on Windows machines, a Microsoft Installer file called

Transaction Trace Agent.msi is installed in Transaction Trace\Transaction Trace

Agent. This file is also available from the Dynatrace distribution.

For Unix agent installations, first read the readme located under the *Unix_Agents folder. The appropriate tar file and install script are inside each platform’s folder, such as AIX, HP-UX, Linux, and Solaris. The All folder contains another tar file that has all the platforms together. For Unix installations, run the script install from the Dynatrace distribution.

Administrator Installation Options

Depending on your target machines, you have various options for installing Dynatrace Network Analyzer Agent.

Windows

Your options for installing Dynatrace Network Analyzer Agent on a remote Windows machine are:

• Place the installer file on a network drive that is available to the remote machine.

• Install it on the remote machine from your own machine if you have remote control of that machine.

(31)

• Provide the installer file to the user of the remote machine and let that user install it on the remote machine.

• Put the file on a Web page for users to download and install.

• Include Dynatrace Network Analyzer Agent as part of your basic system configuration program.

• Use the Remote Installer to install Dynatrace Network Analyzer Agent software to a Windows machine on your network from a central location. This process is referred to as

remote (unattended) installation. See the release notes for Windows version compatibility

information.

• Conduct a silent installation. For more information, see DNA Silent Installations [p. 55].

Unix or Linux

Your options for installing Dynatrace Network Analyzer Agent on a remote Unix or Linux machine are:

• Copy the files, as appropriate for your platform, from the Dynatrace Unix or Linux distribution *_Unix_Agents folder to a temporary directory on your target Unix or Linux machine (/tmp) and run the install script.

• Download these files from the Dynatrace. In either case, untar the files and run the install script.

Creating an Encrypted User Credentials File for Silent Agent

Installations

To use an encrypted user credentials file with the AVAUTHFILE parameter during a silent agent installation, you have to run a small standalone utility included on your software distribution media.

1. On your software distribution media, locate the AVpasswd.zip file.

2. Unzip the file to a local directory.

3. Double-click the AVpasswd file to run the utility.

4. Type a user name and password in the edit boxes.

5. Change the destination folder if necessary.

6. Click the “Generate now” button. What to Do Next

The output file can now be referred to by an AVAUTHFILE parameter in an agent installation command. For more information, see Dynatrace Network Analyzer Agent Installation Command Syntax [p. 60].

To run the AVpasswd utility in batch mode:

1. Open the Windows command prompt.

2. Change the current directory to the folder in which AVpasswd was extracted.

(32)

3. Type bin\avpasswd.exe –u<Username> -p<Password> -o"<OutputFolder>" For example:

bin\avpasswd.exe –uAlice –pWhit3R4bbit -o"C:\MyTTAAgentPasswords\Agent007"

4. Wait until a new file ttagentauth.ppp is created at the path provided

Agent Installation on Windows Machines

Installing a Windows Dynatrace Network Analyzer Agent

Follow this procedure to install the DNA agent on a Windows machine.

DNA agent installation procedures vary depending on a company’s particular network

administration policies and procedures. Consult your Network Administrator for specific details for your location before installing the agent.

After agent installation, be sure to review the firewall notes that follow this procedure. For more information, see Verify firewall exceptions [p. 33].

1. To install an agent on a remote machine, copy the Transaction Trace Agent Installer folder to the remote machine.

During installation of the DNA console, a self-extracting executable file called Transaction

Trace Agent.msi is installed in the Transaction Trace\Transaction Trace Agent

Installer folder.

2. On either the remote machine or the machine that contains DNA, double-click the

Transaction Trace Agent.msi file to begin installation.

You must run it with elevated privileges. To do so, click Start Search ➤ cmd, right-click on cmd, and choose Run as administrator. Then execute msiexec /I

<properPath>\Transaction Trace Agent Follow the instructions as they appear on the screen.

3. On the Welcome page, click Next.

4. Optional: If you do not have .NET 4.0 or later installed, you will be asked whether you

want to install it.

The agent software itself does not require .NET, but you should install .NET to make agent troubleshooting easier. The Get Support File troubleshooting tool that is installed with the agent software requires that .NET 4.0 or later be installed on the target machine. If you prefer, you can install .NET if and when you need to run GetSupportFile for troubleshooting.

5. On the Destination Folder page, review the default settings, change them if needed, and then click Next.

6. On the Please Choose Data Location (Local Drive) page, specify a local directory in which to save captured data.

If there are multiple NICs, each has its own sub-directory.

7. On the Browser Data Collection Agent page, specify whether you want to install the Browser Data Collection (BDC) agent.

8. On the Promiscuous Mode page, specify whether to use promiscuous mode.

(33)

Unattended captures normally have Promiscuous Mode selected. You can change this setting later.

9. On the User Name and Password page, type an administrator User Name and Password (twice).

This is a unique identifier for this agent on this machine; it does not need to be related to any other Windows user names or passwords. It is used to activate, administer, and use the agent.

10. On the TCP Port Number page, specify a TCP port for accessing remote agents through

firewalls.

If your site has strict firewall policies, you can type a specific port number here so that DNA can exchange data through the firewall with remote agents. Your IT administrator can then make certain that traffic for that port is allowed through the firewall. To ensure communication with the remote agents when there is a firewall, always install an agent on the DNA console system and then use the same port number that you used on the remote machines where the agents are installed.

11. On the Ready to Install the Program page, click Install to apply your settings and install

the DNA agent.

12. When the installation is complete, the InstallShield Wizard Completed page will open.

It is not necessary to reboot the computer before using the agent.

What to Do Next

Verify firewall exceptions

• On a Windows Server 2008 R2 Server Core machine, the agent installer automatically sets a firewall exception for the DNA agent, but this exception is sometimes created incorrectly. To ensure that the firewall exception is correct, run the following command:

netsh advfirewall firewall add rule name="Transaction Trace Agent" protocol=TCP dir=in localport=2408 action=allow profile=private • On all other supported Windows releases, the agent installer does not automatically

set a firewall exception for the DNA agent if your NIC’s network location type is set to something other than private (public, domain). To view or change this setting, open the Network and Sharing Center control panel and click Customize.

• To view or change the list of firewall exceptions, open the Windows Firewall control panel, click the Change Settings, and then click the Exceptions tab. If the DNA agent is not on the list, click Add port and type the exception name and the agent’s TCP port number (by default, this is set during agent installation to 2408).

Enable Internet Explorer add-on for BDC

If you are using Internet Explorer and if you intend to use BDC, you must enable the Internet Explorer add-on from Dynatrace. For more information, see Enabling Add-on for Internet Explorer [p. 25].

(34)

Remote Installation of Dynatrace Network Analyzer Agent on Windows

The easiest and most general way to install the agent on a remote Windows system may be to use the PSExec utility from Microsoft.

1. Download PSExec from Microsoft.

http://technet.microsoft.com/en-us/sysinternals/bb897553 2. Determine the full path and file name to the installer msi.

3. Run the following command:

PsExec.exe \\<computer> -u <username> -p <password> cmd /c “msiexec.exe /i <path_to_agent_msi_package> [options] /qn”

where:

• <computer> is remote machine name or address.

• <[domain\]username> and <password> are a user with administrative privileges.

• <path_to_agent_msi_package> is the Dynatrace Network Analyzer Agent installer

msi. If your path includes spaces, be sure to enclose the entire path and file name in quotation marks.

• [options] are agent silent install options.

The agent is installed on the remote Windows machine.

For administrators of Windows Server systems, you may instead be able to use Group Policy to install the agent remotely. For instructions, see “How to use Group Policy to remotely install software in Windows Server 2008 and in Windows Server 2003 ” on the Microsoft website (http://support.microsoft.com/kb/816102).

Sample Dynatrace Network Analyzer Agent Installation Scripts

Use these samples to help you write commands for installing or upgrading Dynatrace Network Analyzer Agent on Windows machines.

Silent Installation Script Example with Mandatory Properties

The command for a silent installation of a Dynatrace Network Analyzer Agent using the mandatory properties and the default settings is:

msiexec.exe /I "Drive>\<Path>\Transaction Trace Agent.msi" /qn AVUSERNAME=<username> AVPASSWORD=<password>

TARGETDIR="C:\Program Files\Compuware\Transaction Trace Agent\"

New Installation Script Example with Optional Properties

Here is an example of a script for a new installation with the optional properties included:

msiexec.exe /I "C:\Transaction Trace Analysis Agent Installer\Transaction Trace Agent.msi" /qn

INSTALLDIR="C:\Program Files\Compuware\Transaction Trace Agent\" TARGETDIR="C:\Program Files\Compuware\Transaction Trace Agent\"

AVUSERNAME=admin AVPASSWORD=admin PROMISCUOUS=1 DATADIR=C:\AgentData PORT=2409

(35)

Upgrade Script

Here is an example of a script for an upgrade:

msiexec.exe /I "C:\Transaction Trace Analysis Agent Installer\Transaction Trace Agent.msi" /qn REINSTALLMODE=vomus REINSTALL=ALL

Agent Installation on UNIX Machines

Installing a Unix or Linux Dynatrace Network Analyzer Agent

Follow this procedure to install Dynatrace Network Analyzer Agent on a Unix or Linux machine. You must be logged in as the root user to run the install script.

1. Copy the following files to a temp folder on your target Linux/Unix/AIX machine.

• av12.3.0.0<platform>.tar

Choose the one with the platform matching your target Linux/Unix machine

• install

The script to do the install

• Instructions

Instructions

2. Change directory to the temp folder with those installation files.

3. Modify the file permission of the install file by typing the following command:

chmod 0550 install

4. Start the installation by typing the following command to run the script install. ./install

5. Follow the directions as they appear on your screen to install the Dynatrace Network Analyzer Agent.

The default values are displayed in brackets. To accept the default value, press [Enter].

a. Review the copyright notice and press [Enter] to continue.

b. Select the destination folder for the agent.

To accept the default name /opt/avagt, press [Enter] To specify a different name, enter it at the prompt. NOTE

• If the last sub-directory in the directory path is not /avagt, the install script appends /avagt to the name.

• If the directory already exists, you are notified and given the chance to specify another one.

c. Select the Dynatrace Network Analyzer Agent port number (for communication between the agent and the DNA console).

d. Select the destination folder for unattended capture temporary data files.

Dynatrace Network Analyzer

Dynatrace Network Analyzer

Installation Guide

Contents

C H A P T E R 1

Dynatrace Network Analyzer System

Requirements

DNA System Requirements

DNA Console Hardware Requirements

DNA Console Operating System Compatibility

DNA Console Other Software Requirements

Additional DNA System Recommendations

Agent System Requirements

Windows DNA Agent System Requirements

Unix Dynatrace Network Analyzer Agent System Requirements

Database Requirements

Configuring an Existing SQL Server Installation

Enabling TCP/IP

Enabling SQL Server Browser

Enabling Server Authentication

Changing Service Account to Local System

Migrating Existing Databases

Restricting SQL Service

C H A P T E R 2

Installation

Console Installation

Task Duration Estimates

Upgrading Existing Console Installations

Installing SQL Server Management Studio Express

Migrating Existing Databases

Installing Dynatrace Network Analyzer Console

Disabling Network Task Offload

Enabling Add-on for Internet Explorer

Adding a Windows Firewall Exception for Mongoose

User Accounts and Administrative Rights

Running Dynatrace Network Analyzer for the First Time

Managing User Access Rights with AVUsers Group Membership

DNA and VMware

Installing Missing Certificates for DNA Installation

Trace Trimmer Configuration from Windows Control Panel

Agent Installation

Administrator Installation Options

Creating an Encrypted User Credentials File for Silent Agent

Installations

Agent Installation on Windows Machines

Installing a Windows Dynatrace Network Analyzer Agent

Remote Installation of Dynatrace Network Analyzer Agent on Windows

Sample Dynatrace Network Analyzer Agent Installation Scripts

Agent Installation on UNIX Machines

Installing a Unix or Linux Dynatrace Network Analyzer Agent