HP OpenView Transaction Analyzer

(1)

HP OpenView Transaction Analyzer

For the UNIX

®

(Sun Solaris, HP-UX, AIX, Linux) Operating Systems

Software Version: 3.1.1

Installation and Configuration Guide

Document Release Date: May 2006 Software Release Date: May 2006

(2)

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements

accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notices

Trademark Notices

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. JavaTM_{is a U.S. trademark of Sun Microsystems, Inc.}

Microsoft®, MS-DOS®, and Windows® are U.S. registered trademarks of Microsoft Corporation. Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of The Open Group.

Documentation Updates

This manual’s title page contains the following identifying information:

• Software version number, which indicates the software version

• Document release date, which changes each time the document is updated

• Software release date, which indicates the release date of this version of the software

To check for recent updates, or to verify that you are using the most recent edition of a document, go to:

http://ovweb.external.hp.com/lpe/doc_serv/

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

(3)

Support

Please visit the HP OpenView support web site at:

http://www.hp.com/managementsoftware/support

This web site provides contact information and details about the products, services, and support that HP OpenView offers.

HP OpenView online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support site to:

• Search for knowledge documents of interest

• Submit enhancement requests online

• Download software patches

• Submit and track progress on support cases

• Manage a support contract

• Look up HP support contacts

• Review information about available services

• Enter discussions with other software customers

• Research and register for software training

Most of the support areas require that you register as an HP Passport user and log in. Many also require a support contract.

To find more information about access levels, go to:

http://www.hp.com/managementsoftware/access_level

To register for an HP Passport ID, go to:

http://www.managementsoftware.hp.com/passport-registration.html

Audience

This guide is intended for performance and application specialists and administrators who are familiar with software components on web servers, application servers, and database servers.

(4)

Prerequisites

To install and configure OVTA, you should be familiar with the following:

• Sun Solaris, HP-UX (IPF, PA-RISC), AIX, or Linux (IPF, x86) operating system

• Sun Java System Web Server (formerly iPlanet Enterprise Server/Sun ONE Web Server), IHS, or Apache web servers

• J2EE application servers

• Databases

OVTA is built on the following products:

• Hewlett-Packard Application Server (HP-AS)

• SOLID Embedded Engine

• Java Web Start

Additional Documentation

This document contains minimal information on configuring Java Diagnostics. See the HP OVTA Java Diagnostics User’s Guide for detailed configuration and usage information.

(5)

1 Overview

This guide explains how to install and configure the HP OpenView Transaction Analyzer (OVTA) on UNIX. For Windows instructions, see the HP OpenView Transaction Analyzer Installation and Configuration Guide for Windows Systems.

Installing and configuring OVTA consists of the following tasks:

1 Verifying the system requirements for the OVTA components

2 Installing the OVTA Measurement Server software

3 Configuring the database

4 Installing an OVTA transaction agent on managed nodes

5 Configuring the web server and application server managed nodes

6 Verifying that the OVTA components are successfully installed and configured, and that the managed nodes are successfully configured

7 Configuring the transaction classification rules to map URL requests into a smaller set of business transactions

8 Optionally, configuring the application transaction groups applicable to selected or all logical web hosts

9 Optionally, configuring OVTA to collect J2EE application server metrics

This guide also explains how to start and stop OVTA; provides instructions for uninstalling OVTA and upgrading OVTA; and discusses advanced configuration options.

➤

Note

It is highly recommended that, before installing any software, you first read the HP

OpenView Transaction Analyzer Performance and Scalability Guide. The guide explains how your deployment decisions will affect the performance and scalability of OVTA.

(12)

(13)

2 Platform Support and System Requirements

Before installing any software, read the HP OpenView Transaction Analyzer Performance and Scaling Guide, which provides information on how to correctly size your OVTA installation. For OVTA Java Diagnostics platform support and system requirements, see the HP OVTA Java Diagnostics User’s Guide.

See the Release Notes for any updated information.

Measurement Server

Supported Platforms

Operating System Sun Solaris 8 or 9

HP-UX 11i v1 and IIi v2 u2

Java Java 2 Platform, Standard Edition v 1.4 (JRE 1.4) (bundled with OVTA) Application Server HP Application Server (HP-AS) 8.1 (bundled with OVTA)

Database SOLID Embedded Engine 4.0 (bundled with OVTA for non-production use) or

Oracle 9i or Oracle 10g (if using Oracle rather than the OVTA embedded database)

Disk Space 1 GB

Disk space requirements can be higher depending on the configured data retention/archiving policies and the transaction classification rules governing the number of managed transaction types.

Memory 1 GB (minimum)

System Requirements

Disk Space in /tmp Directory

Approximately 3 times the size of the OVTA installation program

SHMMAX Greater than 20 MB

SHMSEG Greater than or equal to 4 SEMMNI Should be increased by 2

(14)

Remote OVTA Console Requirements

Remote OVTA Configuration Editor Requirements

Maximum Process Heap

Size (data segment size)

Greater than or equal to 256 MB ("ulimit -d" >= 256000)

Red Hat Linux 3 and 4, SuSE Linux

Library libstdc++-libc6.2-2.so.3. If you do not have the library

libstdc++-libc6.2-2.so.3 in your library path (/usr/lib or /usr/local/lib or /opt/ HPOV_IPA/lib), install the C++ compatibility package — for example, compat-libstdc++-7.3-2.96.122 or a latest version of this package. You can get this package from

http://rpmfind.net/linux/rpm2html/

search.php?query=compat-libstdc%2B%2B

The preferred installation location for this package is /opt/HPOV_IPA/lib or / usr/lib.

Red Hat Enterprise Linux 2.1

The "bc" package — for example, bc-1.06-5.i386.rpm (Other versions of Linux normally have this already installed.)

Red Hat Linux Advanced Server 2.1 on IPF

Kernel version 2.4.18-e.43smp or later

Solaris 5.8 (and later) on SPARC

Java Diagnostics requires recommended patches found at http:// sunsolve.sun.com/pubcgi/show.pl?target=patches/J2SE.

Sun Solaris 8 Patches 108434-03 SunOS 5.8: Shared library patch for C++, 109147-09 SunOS 5.8: Linker patch

Component Requirement

Java JRE 1.4 (bundled with OVTA for most platforms) for Console use locally on the Measurement Server

Browser Microsoft Internet Explorer 5.0 or greater Netscape Navigator 4.7 or greater

Software Java Web Start bundled with JRE 1.4 or greater

Java JRE 1.4 (bundled with OVTA for most platforms) for Console use locally on the Measurement Server

Browser Microsoft Internet Explorer 5.0 or greater Netscape Navigator 4.7 or greater

Software Java Web Start bundled with JRE 1.4 or greater

(15)

Managed Node

Supported Platforms

Operating System • Sun Solaris 8 or 9

• HP-UX 11i v1 (PA-RISC) and 11i v2 u2 ( PA-RISC and IPF)

• AIX 5.1, 5.2 or 5.3

• Red Hat Linux Advanced Server 2.1, 3.0 or 4.0 or Enterprise Server 2.1 or 3.0 (x86 and IPF) or 4.0 (x86 and IPF)

SuSE Linux Enterprise Server 8.0 and 9.x (not supported on IPF) Java • JRE 1.4 (bundled with OVTA except on HP-UX IPF, Linux IPF)

• JRE 1.4.2 or higher (required on HP-UX IPF, Linux IPF) BEA JRockit is not supported.

Web Server • Sun Java System Web Server 6.x (not supported on IPF platforms/SUSE Linux/RHEL 4.0)

• Apache 1.3.x or 2.0.43 or greater (Apache 1.3 not supported on IPF platforms/SUSE Linux/RHEL 3.0)

• IBM HTTP Server 1.3.x or 2.0 (not supported on IPF platforms/Linux RHEL 3.0, only 2.0 supported on SUSE Linux)

(16)

For more up-to-date information on supported platforms, go to

http://support.openview.hp.com/sc/support_matrices.jsp

Application Server • BEA WebLogic Server and WebLogic Express 6.1, 7.0, 8.1, 9.0 or 9.1 (6.1 and 7.0 not supported on IPF platforms)

• IBM WebSphere 5.x or 6.x (not supported on IPF platforms)

• JBoss Application Server 3.2 and 4.0 (not supported on IPF platforms/ AIX)

• Tomcat 4.1, 5.0 (not supported on IPF platforms/AIX), or 5.5 (not supported on IPF)

Tomcat should NOT be used with Sun Hotspot JDK 1.5 in production due to performance overhead.

• Oracle 10g Application Server version 10.1.2

NOTE:

Third-party JVMPI agents cannot be used with OVTA or Java Diagnostics transaction agents.

Java Diagnostics is not currently supported when using the following JVMs. Application Servers

JVM Affected

IBM JDK 1.4.x and 1.5.x* WAS 5.x and 6.x on Linux and AIX WLS 8.1 on AIX BEA JRockit 1.5.0** WLS 9.x, Tomcat 5.5 BEA JRockit prior to JRockit 1.4.2_02 WLS 7.0

* Hewlett-Packard and IBM are working to resolve this. ** Hewlett-Packard and BEA are working to resolve this.

On HP-UX PA-RISC systems, Java Diagnostics does not support BEA WebLogic Server (WLS) 6.1. Running Java Diagnostics with BEA WebLogic Server 6.1 for HP-UX on PA-RISC generates the following error.

/usr/lib/dld.sl: Unresolved symbol: __nw__13ObjectMonitorSFUl (code)

from jdk131/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl

The cause is the embedded Java SDK version 1.3.1.00 that ships with WLS 6.1.

To fix this, upgrade to a newer version of the SDK or install a service pack for WebLogic Server. Updates to the SDK 1.3 for the Java platform on HP-UX are available at http://www.hp.com/products1/unix/java/java2/ sdkrte1_3/downloads/index.html

The BEA web site reports that WebLogic Server 6.1 is certified to work with SDKs from 1.3.1.01 through 1.3.1.09. Updates for WebLogic Server, SP1 through SP7, ship with a newer version of the Java SDK.

(17)

System Requirements

Disk Space 150 MB

Disk Space in /tmp Directory

Approximately 3 times the size of the OVTA installation program

SHMMAX Greater than 20 MB

SHMSEG Greater than or equal to 2 Maximum Process Heap

Size (data segment size)

Greater than or equal to 256 MB ("ulimit -d" >= 256000)

Red Hat Linux 3 and 4, SuSE Linux

Library libstdc++-libc6.2-2.so.3

If you do not have the library libstdc++-libc6.2-2.so.3 in your library path (/ usr/lib or /usr/local/lib or /opt/HPOV_IPA/lib), install the C++ compatibility package — for example, compat-libstdc++-7.3-2.96.122 or a latest version of this package. You can get this package from

http://rpmfind.net/linux/rpm2html/

search.php?query=compat-libstdc%2B%2B

The preferred installation location for this package is /opt/HPOV_IPA/lib or / usr/lib.

Red Hat Enterprise Linux 2.1

The "bc" package — for example bc-1.06-5.i386.rpm (Other versions of Linux normally have this already installed.)

Red Hat Linux Advanced Server 2.1 on IPF

Kernel version 2.4.18-e.43smp or later

Linux on IPF libpthread-0.9.so and libc-2.2.4.so compatible libraries

Without these, the JD Node Agent may crash when a JD session is closed or canceled from the JD console. (This may be shown as a red X on the node name.) The shared libraries libpthread-0.9.so and libc-2.2.4.so are included in glibc-2.2.4-29.2, which is available from http://rpmfind.net//linux/ RPM/redhat/enterprise/2.1AS/ia64/src/glibc-2.2.4-29.2.src.html

HP-UX IPF Library libstdc++-libc6.2-2.so.3. If this library is not already installed, you can download the gcc runtime package from

http://gatekeep.cs.utah.edu/hppd/hpux/Gnu/

At the time of this release, the following version is available.

http://gatekeep.cs.utah.edu/hppd/hpux/Gnu/libgcc-4.1.0/

The path for the GNU run time libraries needs to be added to the path environment variable used to start OVTA components or web and application servers monitored by OVTA.

Solaris 5.8 (and later) on SPARC

Java Diagnostics requires recommended patches found at

http://sunsolve.sun.com/pubcgi/show.pl?target=patches/J2SE

Sun Solaris Required Patches

Solaris 8 – 108434-03 SunOS 5.8: Shared library patch for C++, 109147-09 SunOS 5.8: Linker patch

(18)

ActiveX Client Monitor

JavaScript Client Monitor

On HP-UX 11i, there are new options, described in section 8.4 (Large Private Data Space) of the HP-UX 11i Release Notes. Using this HP-UX option is incompatible with running armd. Consult the HP-UX 11i documentation or your system administrator to find out whether this option is in use on your system, and disable it if necessary.

Browser Microsoft Internet Explorer 5.0 – 6.0

Browser Microsoft Internet Explorer 5.0 – 6.0 Netscape Navigator 4.5 – 7.x

(19)

3 Installation

This chapter explains how to:

• Prepare to install the Measurement Server software, including the license (see next page)

• Use the installation wizard to install the Measurement Server software (see page 20)

• Obtain and install the product licenses (see page 23)

• Configure the Measurement Server database (see page 27)

• Upgrade the Measurement Server software (see page 32)

• Prepare to install the managed node software (see page 34)

• Use the installation wizard to install the managed node software (see page 34)

• Upgrade the managed node software (see page 36)

• Use silent install to install the Measurement Server or managed node software (see

page 38)

• Allow a non-root user to run the OVTA start/stop scripts (see page 40)

(20)

Installing the OVTA Measurement Server Software

When the OVTA Measurement Server software is installed, the OVTA Console, Java Diagnostics Console, and OVTA Configuration Editor are also installed. Before starting the installation, make sure that your system satisfies the requirements listed in Chapter 2, Platform Support and System Requirements, and verify that you are able to log in as root. If you are upgrading an existing OVTA installation, or reinstalling over the same version, see

Upgrading the Measurement Server on page 32.

You can install all of the OVTA software components, in any order, on a single machine. However, even when you install the components on different machines, it is a good idea to first install the Measurement Server software and then the managed nodes. To install all components on the same machine, you must go through the installation wizard twice. You can install the OVTA software using either the installation wizard or silent install. The installation wizard guides you through the installation procedure using a series of dialogs. Silent install requires no user interaction. It takes all input from a previously prepared input file and, therefore, is most useful for installing a large number of nodes.

OVTA 3.x is able to run a primary-secondary configuration of Measurement Servers that share the load associated with client monitoring, application monitoring on managed nodes, and graphical display. The primary-secondary architecture allows one (and only one) primary Measurement Server and any number of secondary Measurement Servers, all of which input and retrieve data from the same database. The scalability of the entire system is limited only by the scalability of the database, the number of transactions/sec that the database can process. The database must be a production quality one. It must be able to execute queries that span across large volumes of data in an acceptable time frame.

If you are installing both primary and secondary Measurement Servers, the primary Measurement Server must be installed first.

If you are using Oracle as your database, you must first install the primary Measurement Server, and then you must configure Oracle before you can install any secondary

Measurement Servers (see Oracle Standard Edition on page 29).

The secondary Measurement Servers provide a subset of the functionality of the primary Measurement Server. The archiving/summarization services run only on the primary Measurement Server. The Configuration Editor can run in read/write mode only on the primary Measurement Server.

For more information about primary and secondary Measurement Server configuration, see the HP OpenView Transaction Analyzer Performance and Scalability Guide.

Measurement Server Installation Wizard

The installer GUI uses the X-Window System (X11). The display host (whose graphical display you are viewing) must be running an X server. The system on which you are installing OVTA must have X11 installed, and you must set its DISPLAY environment variable to the address and display number of the display host. Before installing OVTA on a system, you should test that a simple X client such as “xterm” or “xclock” invoked there displays on your screen.

If the X-Window System is not available, you can use Silent Install on page 38.

The Measurement Server is installed to /opt/HPOV_IPA (on UNIX) and /usr/lpp/HPOV_IPA (on AIX). You cannot change the installation directory. If you cannot install under /opt, create a link called /opt/HPOV_IPA and point it to another directory.

(21)

1 Insert the OVTA product CD into the CD-ROM drive.

2 Mount the OVTA product CD using the mount command. See your system administrator for platform-specific documentation if you encounter any problems executing this

command.

3 Copy the installation program (install.bin) from the CD to a writable file system (for example, /tmp)

cp <CD mount point>/hpovta/InstData/<AIX|HPUX|Solaris|Linux>/VM/ install.bin

4 Change your current directory to the directory where you saved the OVTA installation program (install.bin).

5 Type sh ./install.bin

6 The OVTA installation wizard guides you through the installation. Note the following.

— Select either the primary Measurement Server or secondary Measurement Server. The process for installing a secondary Measurement Server is the same as installing a primary Measurement Server, except that there is an added panel. During

installation of each secondary Measurement Server, the added panel asks you for the attributes of the primary Measurement Server to which the secondary will connect. If you are installing both primary and secondary Measurement Servers, the primary Measurement Server must be installed first.

If you are using Oracle as your database, you must first install the primary

Measurement Server, and then you must configure Oracle before you can install any secondary Measurement Servers (see Oracle Standard Edition on page 29).

See the HP OpenView Transaction Analyzer Performance and Scalability Guide for more information about primary and secondary Measurement Server configurations.

— If the Hewlett-Packard Application Server (HP-AS) is already installed, enter the full path to its installation folder. Otherwise, enter the path to where you want to install HP-AS. The installer will prompt you for an HP-AS administrator password. It will then place the HP-AS installer and an installer input file in /opt/HPOV_IPA/hpas. After the installer exits, do the following:

– Run the HP-AS installer:

cd /opt/HPOV_IPA

jre/bin/java -jar hpas/hpas_install.jar -f \ /opt/HPOV_IPA/hpas/hpas_install.properties

– Run the OVTA installer again and select Measurement Server to install the Measurement Server components.

— Select the database (SOLID or Oracle) to store response time measurements from the Measurement Server. If you select Oracle, you must install and configure Oracle Standard Edition (see Configuring the Measurement Server Database on page 27 for more information).

Note: The SOLID database included with OVTA is for non-production use.

— The installer will ask you to specify the following attributes of the primary Measurement Server and each secondary Measurement Server that you install. If you create the link but delete the underlying directory, and then try to install OVTA, it will incorrectly report success.

(22)

– Measurement Server Protocol: Specify whether you want to use HTTPS to communicate with the Measurement Server. If you use HTTPS, you must configure your system for HTTPS communication (see Chapter 8, Advanced Configuration for more information).

– Measurement Server Host Name: Specify the fully qualified domain name system (DNS) name for the host on which the Measurement Server software is installed. Type the host name using the following format: machine.domain.com.

– Measurement Server HTTP Port: Specify the HTTP port number that OVTA transaction agents on remote systems will use to communicate with the

Measurement Server. You can enter any port number that you want. If you do not specify a value, OVTA uses port number 7555.

If you specify a port number that is different from the default, you must modify the listener-service ports in the hpas configuration file <hpas_installation_dir>/ config/ovta/http-service-config.xml.

– Measurement Server HTTPS Port: Specify the HTTPS port number that OVTA transaction agents on remote systems will use to communicate with the Measurement Server. You can enter any port number that you want.

If you do not specify a value, OVTA uses port number 443. If you specify a port number that is different from the default, you must modify the listener-service ports in the hpas configuration file <hpas_installation_dir>/config/ovta/

http-service-config.xml (see Chapter 8, Advanced Configuration for more information).

7 If any installation errors or warnings occur, check the installation log file and refer to the

HP OpenView Transaction Analyzer Troubleshooting Guide if necessary. Open the following text file for viewing:

/<ovta_installation_dir>/HP_OpenView_Transaction_Analyzer_InstallLog.xml /<ovta_installation_dir>/data/log/post-install.log

8 HP-AS uses ports 2200 and 22000 to communicate with OVTA. If these ports are already in use, modify the following parameters.

In <ovta_installation_dir>/bin/ovtams-launch.sh, search for and modify the port number:

HP_OVTA_ARGS=”port 22000 -group ovta -jmxport 2200” 9 Restart HP-AS.

10 After you complete the installation, verify that the OVTA patch was successfully applied to HP-AS.

To verify the patch, locate a file named /opt/HPOV_IPA/data/log/hpaspatch_8.log. If the file exists and contains a “BUILD SUCCESSFUL” message, the patch was applied correctly.

If the file does not exist, you must manually apply the patch. To manually apply the patch, run /opt/HPOV_IPA/bin/install_hpas_patch8.sh as root (or another privileged user that has access to write into the directory). The Measurement Server must be restarted for the patch to take effect.

11 If you choose Oracle as your database, refer to Configuring the Measurement Server Database on page 27 to complete the Measurement Server installation.

12 If you choose HTTPS communication, refer to Chapter 8, Advanced Configuration to complete the Measurement Server installation.

(23)

14 Verify the installation and configuration. Run the managed applications and verify that the data displays correctly in the OVTA Console.

15 Configure the appropriate transaction classification rules for the managed web applications.

Licensing

You must have a license key to use OVTA.

Both the primary and the secondary Measurement Servers get instant-on (trial) licenses when they are first installed. If the primary and secondary Measurement Servers are installed on different dates, their trial licenses will have different expiration dates.

The trial license code is TRIAL_OVTA. A trial license is good for 60 days. Before the 60-day period expires, you must obtain either a trial evaluation extension or a permanent license to continue to use OVTA.

To get a permanent license, contact your HP sales representative. If you are not sure about whom to contact, go to http://www.openview.hp.com/buy and click how to buy in the left navigation pane.

Use the OVTA license tool to install a permanent license or a license extension (see Extending the 60-Day Trial License on page 26).

Licensing is determined by counting the number of transaction agents reporting to the Measurement Server and the number of top-level client monitor transactions. (The trial license allows unlimited capacity.) All licenses must be installed on the primary Measurement Server, and not on the managed nodes.

Once you install a permanent license on the primary Measurement Server, the information is propagated to the secondary Measurement Servers, which then switch to permanent

licensing. However, you will need to restart the secondary Measurement Servers so that the receptors will pick up the new license.

License Tool

The License Tool GUI uses the X-Window System (X11). The display host (whose graphical display you are viewing) must be running an X server. The primary Measurement Server must have X11 installed, and you must set its DISPLAY environment variable to the address and display number of the display host.

Launch the license tool with the following:

/<ovta_installation_dir>/bin/OVTALicense.sh

Use the license tool to install permanent and evaluation extension licenses only on the primary Measurement Server. The licenses are communicated to the secondary Measurement Servers. On the secondary Measurement Servers, use the license tool only to view the licenses installed and the current use of these licenses.

The default HTTP measurement configuration results in the measurement of all web

applications, and a unique OVTA transaction is created for each individual URL. The default setting, however, is not appropriate for load testing or production environments where there is a large number of distinct URLs. The “Configuration” chapter in the HP OpenView Transaction Analyzer User’s Guide explains how to properly define web applications and set the classification configuration to map URLs to a smaller set of business transactions.

(24)

The following graphic shows the license tool.

The license tool displays a License Details panel and a summary report for each item listed in the panel. The summary is useful for determining if more licenses are needed.

To install a permanent license: 1 Launch the license tool.

2 Select License → Install

A series of screens guides you through the various options to import and install an OVTA permanent license. If you have an HP OpenView purchase order and a valid Internet connection, you can import the license keys from the Web. If you previously imported and saved the license keys, you can import them from the previously saved files.

When downloading the keys using your purchase order number, you must specify the number of licenses to use (LTUs) you want to enable for one or more of the following:

• HP OVTA Client Monitoring

• HP OVTA Client Monitoring Add’l 25

• HP OV Transaction Agent Tier 0

• HP OV Mainframe Transaction Agent

The Java Diagnostics license is displayed by the license tool, but it does not enable the core OVTA product.

More information on the common OpenView framework for importing permanent licenses is available at http://ovweb.external.hp.com/lpe/doc_serv/. Select “autopass” from the list of online product manuals.

(25)

License Warnings

The trial period provides unlimited capacity for transaction agents and client monitor transactions. When a client monitor pack license or a managed node license is installed, the product is deemed to have a permanent license installed. When a permanent license is installed, warning messages are generated whenever usage exceeds the number of licenses installed.

• Warnings about exceeding transaction agent licenses

The OVTA Measurement Server discovers the presence of managed nodes when the managed nodes report data and counts them. To transfer a managed node license to another machine, remove the managed node software and install it on that machine. If you do not have sufficient capacity licenses to support the number of configured managed nodes, you will receive warning messages when you launch the Console, Configuration Editor, or license manager.

If you removed managed node software from a node because capacity licenses were violated, that node will be counted and the warning messages will continue to appear until all data collected from that node is removed. By default, the data collected will be removed by the OVTA archiver after 30 days. This duration is configurable.

If you have zero number of managed node licenses, but you have a valid client monitor pack license, data will continue to be collected from all the installed managed nodes but the warning messages will continue to appear until the appropriate number of transaction agent licenses is installed.

• Warnings about exceeding client monitor transaction licenses

The OVTA Measurement Server counts the number of unique top-level transactions that have been reported by the client monitors.

If you do not have the correct license capacity to support the number of top-level transactions that are being monitored by client monitors, you will receive warning messages.

(26)

Without a valid OVTA license, any data that is forwarded by the OVIS probes to OVTA will not be collected by OVTA. It will not be possible to launch the OVTA Console from the OVIS dashboard.

Extending the 60-Day Trial License

To request a one-time, 60-day trial (evaluation) license key extension, contact the Hewlett-Packard Password Center.

1 Access the WebWare web site (www.webware.hp.com) and click contact a password delivery center to get the phone number for a regional Password Center. The phone numbers and hours of operation are provided below for your convenience. You may contact any Password Center even if it is outside of your region.

Hewlett-Packard Password Center for U.S.A Phone: (801) 431-1597 or (800) 326-0411 Fax: (801) 431-3654

Hours of operation: 6:00 am to 6:00 pm MST Hewlett-Packard Password Center for Europe/Africa

Phone: (+31-55-543-4642) Fax: (+31-55-543-4645)

Hours of operation: 9:00 to 18:00 CET

Hewlett-Packard Password Center for Asia Pacific

Phone: (outside Japan) (+81-3-3227-5672) or (within Japan) (+81-03-3227-5264) Fax: (+81-3-3227-5238)

Hours of operation: 9:00 am to 5:00 pm JST

2 Contact a Password Center and request a Trial (Evaluation) License Extension.

Important note: This is a one-time 60-day extension.

Be prepared to provide the following information to the WebWare representative:

– Product number (TRIAL_OVTA)

– Product name (HP OV Transaction Analyzer Eval Extension LTU)

(27)

Your trial license/password extension will be sent to you via email. You will need to install it by “importing” it into OVTA by using the OVTA license tool on the OVTA Measurement Server.

Configuring the Measurement Server Database

You can use SOLID or Oracle as your database. The SOLID database included with OVTA is for non-production use only.

For information on changing your database to Oracle from SOLID, see Changing from the SOLID Database to Oracle on page 111.

SOLID Embedded Engine

When you install the Measurement Server and select the SOLID database, the SOLID Embedded Engine is automatically installed, configured, and set to automatically launch at startup. By default, OVTA uses port number 1314 to communicate with the SOLID database server.

The SOLID database is installed only on the primary Measurement Server. If you need to use a different port, two files must be edited.

/<ovta_installation_dir>/data/conf/ipainit.xml

/<ovta_installation_dir>/data/databases/solid.ini

In each of these files, search and replace 1314 with the desired port number.

Configuring the SOLID Cache

The SOLID Embedded Engine has a configurable cache size setting. If you find that the OVTA GUI is slow when displaying large amounts of data, you may be able to improve its performance by increasing this setting. Edit the file <ovta_installation_dir>/data/ databases/ solid.ini and change the value named "CacheSize". For example, to set a cache size of 256 MB:

CacheSize=256m

After saving the file, restart the OVTA Measurement Server.

If the value is too large, SOLID may fail to start, displaying the following message:

SOLID Fatal error: Out of central memory (alloc size = ..., total bytes = ...)

You may be able to allocate more memory to SOLID by doing one of the following:

• Increase the limit on process data segment size. Run “limit” (csh) or “ulimit -a” and check the maximum “data” or “datasize.” If it is not “unlimited,” you may be able to specify a larger value using “limit datasize ...” or “ulimit -d ...”. See the “limit” or “ulimit” man page for details.

• Stop other processes that use large amounts of memory. Otherwise, you must decrease the SOLID cache size setting.

(28)

Backing up the SOLID Database

The SOLID embedded database is configured to create a backup every day at 1:00 am. The backup is created in the <ovta_installation_dir>/data/databases/backup directory. The time needed for making a backup is the time that passes between the messages “Backup started” and “Backup completed successfully.” These messages are written to the solmsg.out log files. To edit the time when the backup is made, edit the following entry in <ovta_installation_dir>/ data/databases/solid.ini and specify a different time:

At=01:00 backup

For example, to change the backup time to 11:00 pm, enter the following:

At=23:00 backup

It is best that automatic backups run during non-busy periods. When the backup completes, you can copy the backup files to another media for protection against disk crashes.

To edit the location in which the backup is made, edit the following entry in solid.ini:

BackupDirectory=backup

The backup directory must exist, and it must contain enough disk space for the backup files. It can be set to any existing directory, except the SOLID database file directory

(<ovta_installation_dir>/data/databases/), the log file directory (<ovta_installation_dir>/data/ databases/log), or the working directory (<ovta_installation_dir>/data/databases/).

All directory definitions are relative to the SOLID embedded database working directory unless the full path is provided. The backup directory entry must be a valid path name in the server’s operating system.

To have your changes take effect, restart the SOLID database.

Restoring Backups

There are two ways to restore a backup. You can either:

• Return to the state when the backup was created or

• Revive a backup database to the current state by using log files to add data inserted or updated after the backup was made.

To return to the state when the backup was created:

1 Stop all OVTA services on the primary and secondary Measurement Servers (HP OpenView IPA ARM 3.0 Collector, HP OpenView IPA ARM 3.0 daemon, HP OpenView IPA Embedded Database, HP OpenView IPA Measurement Server, HP OpenView TA J2EE Collector).

2 Delete the SOLID database (solid.db), log (sol*.log), and output (sol*.out) files from the

<ovta_installation_dir>/data/databases directory.

3 Copy the SOLID database (solid.db) alone from the backup directory to the database file directory.

4 Start all OVTA services on the Measurement Server (HP OpenView IPA ARM 3.0 Collector, HP OpenView IPA ARM 3.0 daemon, HP OpenView IPA Embedded Database, HP OpenView IPA Measurement Server, HP OpenView TA J2EE Collector). Also restart OVTA services on any secondary Measurement Servers.

(29)

To revive a backup database to the current state:

1 Stop all OVTA services on the primary and secondary Measurement Servers (HP OpenView IPA ARM 3.0 Collector, HP OpenView IPA ARM 3.0 daemon, HP OpenView IPA Embedded Database, HP OpenView IPA Measurement Server, HP OpenView TA J2EE Collector).

2 Delete the SOLID database (solid.db) files from the <ovta_installation_dir>/data/ databases directory.

3 Copy the SOLID database (solid.db) and log files (sol*.log) from the backup directory to the database file directory. If the same log file exists in both directories, do not overwrite files with backup files.

4 Start all OVTA services on the Measurement Server (HP OpenView IPA ARM 3.0 Collector, HP OpenView IPA ARM 3.0 daemon, HP OpenView IPA Embedded Database, HP OpenView IPA Measurement Server, HP OpenView TA J2EE Collector). Also restart OVTA services on any secondary Measurement Servers.

SOLID automatically uses the log files to perform a roll-forward recovery.

Oracle Standard Edition

By following the steps below, you will create tablespaces, the OVTA user, OVTA tables and indexes, and OVTA stored procedures and triggers. You will also set up service dependencies between Oracle and OVTA.

Do the following:

1 Install Oracle Standard Edition 9i or 10.x. Read Oracle's installation instructions for complete information.

Create a new database to store OVTA data or use an existing database.

You must create the Oracle database instance with the UTF-8 character set.

Configuring a Local Database

a Edit <ovta_installation_dir>/data/databases/schema/oracle/ipacreateuser.sql to set up the correct user name and password to be used by the OVTA Measurement Server components to access the database. In other words, modify “create user IPA identified by password” and replace “IPA” with the actual user name in “connect to IPA.”

Edit <ovta_installation_dir>/data/databases/schema/oracle/ipaoraclesetup.sql by modifying “connect ipa/password@ipa” to reflect the actual values. Make sure that the user name and password values match the ones specified in ipacreateuser.sql.

➤

Note

The TEMP database should be at least half the size of the OVTA data table space (default is 500 MB). A one-to-one ratio is ideal if space is available. Oracle uses the TEMP database for joins and sorts only. OVTA does not explicitly insert any data into temp tables.

➤

Note

The table spaces are specified in the file <ovta_installation_dir>/data/databases/schema/ oracle/ipacreatetablespace.sql. The default sizes are 500 MB for the tables and 200 MB for the indices. You can increase these values to size a larger database.

(30)

b Run SQL*Plus. Log on as the “system” user. The default password is “manager,” but your administrator may have changed this during installation. Run the

ipaoraclesetup.sql script.

SQL> @<ovta_installation_dir>/data/databases/schema/oracle/ ipaoraclesetup.sql

c Edit the OVTA initialization configuration file <ovta_installation_dir>/data/conf/ ipainit.xml to reflect the database name that contains the OVTA tables. The following line of code is an example of DB_CONFIG connection_string entry. It defines

sunov.rose.hp.com on port 1521 as the database hostname and port. The database is named “theDB” with the user name “admin” and password “admin”. The password can be encrypted; see step e on page 30 for details.

<DB_CONFIG

connection_string="jdbc:oracle:thin:@sunov.rose.hp.com:1521:theDB" jdbc_driver_class="oracle.jdbc.driver.OracleDriver" user="admin" password="admin"

max_guiconnection="10"/>

d Navigate to the bin subdirectory of OVTA and run the DbInitData.sh command to initialize the Oracle database with startup data.

cd <ovta_installation_dir>/bin

./DbInitData.sh

e To encrypt the password that was entered into ipainit.xml, after the Measurement Server has started up, run the OVTA Configuration Editor, select Measurement Server tab, click Change Password, and type the password in all three text fields. The Configuration Editor will encrypt the password when writing it to ipainit.xml. You do not need to restart the Measurement Server to pick up the same user name and password.

f Launch the OVTA console and verify that the Transactions navigation panel displays a hierarchical view of the Application Kind transaction groups, such as HTTP, EJB, and COM. This step validates that the OVTA schema has been correctly set up in the Oracle database and is accessible by the OVTA Measurement Server.

Configuring a Remote Database

a Make a directory on the machine where the database resides; for example,

<ovta_installation_dir>/data/databases/schema/oracle

b Ftp the following files from <ovta_installation_dir>/data/databases/schema/oracle to the directory made in step a:

ipacleantables.sql ipacreatetablespace.sql ipaoraclecleanup.sql ipacreateprocedures.sql ipacreatetriggers.sql ➤

Note

The steps that follow apply even if the remote database machine is not on the same platform as the Measurement Server. However, when you modify the paths, you need to enter the path names used on the remote database server. For example, if the database server is a Windows machine, you need to change the paths from, say, /opt/HPOV_IPA/... to the Windows path where the file will reside; for example, c:\Program Files\HPOV_IPA\....

(31)

ipadropsynonyms.sql ipaoraclesetup.sql ipacreatetables.sql ipacreateuser.sql ipadroptables.sql

c Edit ipacreateuser.sql to set up the correct user name and password to be used by the OVTA Measurement Server components to access the database. In other words, modify “create user IPA identified by password” and replace “IPA” with the actual user name in “connect to IPA.”

d Edit ipaoraclesetup.sql by modifying “connect ipa/password@ipa” to reflect the actual values. Make sure that the user name (connect ipa), password (password), and database name (ipa) values match the ones specified in ipacreateuser.sql. Modify the path to reflect the path you specified in step a.

e Edit ipacreatetablespace.sql by modifying the path to reflect the path you specified in

step a.

f Edit ipaoraclecleanup.sql by modifying the path to reflect the path you specified in

step a.

g Run SQL*Plus on the machine where the database resides. Log on as the system user. The default password is manager, but your administrator may have changed this during installation. Run the ipaoraclesetup.sql script.

SQL> @<ovta_copy_dir>/data/databases/schema/oracle/ ipaoraclesetup.sql

In the above, <ovta_copy_dir> represents the directory you made in step a.

h On the Measurement Server, edit the OVTA initialization configuration file

<ovta_installation_dir>/data/conf/ipainit.xml to reflect the database name that contains the OVTA tables. The following line of code is an example of the

DB_CONFIG connection_string entry. It defines sunovt.rose.hp.com on port 1521 as the database server. The database is named “theDB” with the user name “admin” and password “admin.”

<DB_CONFIG connection_string="jdbc:oracle:thin:@sunovt. rose.hp.com:1521:theDB"

jdbc_driver_class="oracle.jdbc.driver.OracleDriver" user="admin" password="admin"max_guiconnection="10"/>

i On the Measurement Server, navigate to the bin subdirectory of OVTA and run the DbInitData command to initialize the Oracle database with startup data.

./DbInitData.sh

j To encrypt the password that was entered into ipainit.xml, after the OVTA

Measurement Server application has started up, run the OVTA Configuration Editor, select the Measurement Server tab, click Change Password, and type the password in all three text fields. The Configuration Editor will encrypt the password when writing it to ipainit.xml.You do not need to restart the Measurement Server to pick up the same user name and password.

k After starting the Measurement Server application, launch the OVTA console

(IPAGUI.sh) and verify that the Transactions navigation panel displays a hierarchical view of the Application Kind transaction groups, such as HTTP, EJB, and COM. This step validates that the OVTA schema has been correctly set up in the Oracle database and is accessible by the OVTA Measurement Server.

(32)

Upgrading the Measurement Server

You can upgrade an existing OVTA installation, without first uninstalling, if all of the following are true:

• The existing version of OVTA is 2.0, 2.1, 3.0 or 3.1.

• The existing installation is either a managed node or a Measurement Server (not both on a single machine).

• You are installing the same type of installation (managed node or Measurement Server).

• You are using the same type of database (SOLID or Oracle) on a Measurement Server. When you upgrade an OVTA installation or reinstall over the same version, the installer preserves the OVTA configuration files and, on a Measurement Server, the database. An exception is the file <ovta_installation_dir>/data/conf/ipainit.xml, which the installer overwrites after making a backup copy. If any manual edits were made in this file, you must copy those edits to the new file as described in step 3 below.

The procedure for upgrading the Measurement Server consists of the following:

1 Stop OVTA following the instructions in Stopping OVTA on page 94.

2 Install the new OVTA software following the instructions in Installing the OVTA Measurement Server Software on page 20.

Oracle only: Do NOT perform the steps described in Configuring a Local Database on page 29 and Configuring a Remote Database on page 30.

3 If the file <ovta_installation_dir>/data/conf/ipainit.xml was modified in the previous installation, make the same modifications in the new ipainit.xml file. The old file is available as ipainit_<version>.xml.

4 Run the database upgrade script.

Oracle

— Run SQL*Plus. Log on as the OVTA user.

— If upgrading from OVTA 2.0, first run the 2.1 conversion script (the following is all one line):

SQL> @

<ovta_installation_dir>/data/databases/schema/oracle/

ipaSchemaChanges_from_2.0_to_2.1.sql

— If upgrading from OVTA 2.0 or 2.1, run the 3.0 conversion script (the following is all one line):

<ovta_installation_dir>/data/databases/schema/oracle/

— Finally, run the 3.1 conversion script (the following is all one line):

➤

Note

Before running the Oracle upgrade script:

• Make sure that the table space used for OVTA tables is less than 60% full.

(33)

SQL> @

<ovta_installation_dir>/data/databases/schema/oracle/

You can ignore errors on “DROP TRIGGER” commands.

SOLID

— Start the database server:

sh # Create a new environment.

. ./ovta_installation.sh . ./ovta_env.sh

solid -c "<ovta_installation_dir>/data/databases" -n "IPADB" -s start

exit # From sh, to restore your environment.

— If upgrading from OVTA 2.0, first run the 2.1 conversion script (the following is all one line):

<ovta_installation_dir>/bin/solsql -a -f

"<ovta_installation_dir>/data/databases/schema/solid/ ipaSchemaChanges_from_2.0_to_2.1.sql"

"tcpip localhost 1314" IPA homebrew

— If upgrading from OVTA 2.0 or 2.1, run the 3.0 conversion script (the following is all one line):

<ovta_installation_dir>/bin/solsql -a -f

"<ovta_installation_dir>/data/databases/schema/solid/ ipaSchemaChanges_from_2.1_to_3.0.sql"

"tcpip localhost 1314" IPA homebrew

— Finally, run the 3.1 conversion script:

<ovta_installation_dir>/bin/OVTASolidUpgrade_from_3.0_to_3.1.sh

You can ignore errors on “DROP TRIGGER” commands.

5 Start OVTA following the instructions in Starting OVTA on page 91.

Managed Node Interoperability

Once the Measurement Server has been upgraded to OVTA 3.1, it is not immediately necessary to update the managed nodes. An OVTA 3.x Measurement Server is compatible with both OVTA 2.0 and 2.1 managed nodes.

(34)

Installing OVTA on Web Server and Application Server

Managed Nodes

The following instructions describe how to install OVTA Web Server and Application Server managed node software on your system. Before you begin the installation, make sure that your system meets the requirements listed in Chapter 2, Platform Support and System Requirements, and make sure that you can log in as user “root.”

If you are upgrading an existing OVTA installation, or reinstalling over the same version, see

Upgrading the Managed Nodes on page 36.

If you are reinstalling OVTA, stop any Web and application servers that are configured for OVTA.

You can install all of the OVTA software components, in any order, on a single machine. However, even when you install the components on different machines, it is a good idea to first install the OVTA Measurement Server software and then the managed nodes. To install all components on the same machine, you must go through the installation wizard twice.

You can install the OVTA managed node software using either the installation wizard or silent install. The installation wizard provides a series of dialogs that guide you through the installation. Silent install requires no interaction from you. Silent install is useful when you are installing a large number of managed nodes or when you do not have X-Windows

available.

Managed Node Installation Wizard

The installer GUI uses the X-Window System (X11). The display host (whose graphical display you are viewing) must be running an X server. The system on which you are installing OVTA must have X11 installed, and you must set its DISPLAY environment variable to the address and display number of the display host. Before installing OVTA on a system, you should test that a simple X client such as “xterm” or “xclock” invoked there displays on your screen.

If the X-Window System is not available, you can use Silent Install on page 38.

1 Insert the OVTA product CD into the CD-ROM drive.

2 Mount the OVTA product CD using the mount command. See your system administrator for platform-specific documentation if you encounter any problems executing this

command.

3 Copy the installation program (install.bin) from the CD to a writable file system; for example, /tmp:

➤

Note

It is only necessary to install OVTA on web servers if you plan to monitor web server response times; otherwise, web applications can be monitored simply by installing OVTA on application servers.

➤

Note

When the Measurement Server and the managed nodes are installed on the same machine, it is not possible to configure both primary and secondary Measurement Servers. You will only be able to configure a primary Measurement Server.

(35)

cp <CD mount point>/hpovta/InstData/<AIX|HPUX|Solaris|Linux>/VM/ install.bin

For HP-UX IPF and Linux IPF:

cp <CD mount point>/hpovta/InstData/<HP-UX_IPF+Linux_IPF>/NoVM/ install.bin

4 If the managed node is HP-UX IPF or Linux IPF, set the PATH environment variable to point it to a JVM location you want the installer to use; for example:

export PATH=$PATH:/opt/java1.4.2/bin ./install.bin

5 Change your current directory to the directory on your machine where you saved the OVTA installation program (install.bin).

A managed node is always installed under the /opt/HPOV_IPA directory on Solaris, HP-UX and Linux, and /usr/lpp/HPOV_IPA on AIX.

The Java Diagnostics node agent is installed under /opt/OV/HPOvJD on Solaris, HP-UX, and Linux, and /usr/lpp/HPOvJD on AIX.

If you cannot install under /opt, create a link called /opt/HPOV_IPA and point it to another directory. During the installation, specify /opt/HPOV_IPA as the installation directory.

Check for free disk space on the file system where the managed node is to be installed. On Linux, do the following:

— If there is not enough free space on your file system, create a soft link to /opt/ HPOV_IPA from a local file system/location, as follows:

– cd /opt /* assuming /opt exists */

– mkdir /usr//HPOV_IPA /* assume there is enough space on the local file system /usr */

– ln -s /usr/HPOV_IPA HPOV_IPA /* (or ln -s /usr/HPOV_IPA .) */

— If /opt file system does not exist, or opt directory is absent under / file system and / file system does not have enough space, create the opt directory under / file system manually and then create a soft link.

6 Type sh ./install.bin

7 The OVTA installation wizard guides you through the installation. You will be asked to do the following:

— Select the Managed Node option.

— The installer will ask you to specify the JVM attributes on Linux IPF and HPUX IPF. For HPUX IPF, the JRE should be the location of the IA32 JVM. For Linux IPF, the JRE should be the 64-bit JVM location.

— The installer will ask you to specify the following attributes for the primary or secondary Measurement Server the managed node will communicate with.

See the HP OpenView Transaction Analyzer Performance and Scalability Guide for more information about primary and secondary Measurement Server configurations. If you create the link but delete the underlying directory, and then try to install the OVTA software, it will incorrectly report success.

(36)

– Measurement Server Protocol: Specify whether you want to use HTTPS to communicate with the Measurement Server. If you use HTTPS, you must

manually configure your system (see Chapter 8, Advanced Configuration for more information).

– Measurement Server Host Name: Specify the fully qualified domain name system (DNS) name for the host on which the Measurement Server software is installed. Type the host name using the following format: machine.domain.com.

– Measurement Server HTTP Port: Specify the HTTP port number that OVTA will use to communicate with the Measurement Server. You can enter any port number provided it matches the configuration of the Measurement Server. If you do not specify a value, OVTA uses port number 7555.

– Measurement Server HTTPS Port: Specify the HTTPS port number that OVTA will use to communicate with the Measurement Server. You can enter any port number provided it matches the configuration of the Measurement Server. If you do not specify a value, OVTA uses port number 443.

8 If any installation errors or warnings occur, check the installation log files and refer to the

HP OpenView Transaction Analyzer Troubleshooting Guide if necessary. Open the following text files for viewing:

/<ovta_installation_dir>/HP_OpenView_Transaction_Analyzer_InstallLog.xml /<ovta_installation_dir>/data/log/post-install.log

9 Configure the web server and application server for your system (see Chapter 4, Configuring Web Server Managed Nodes and Chapter 5, Configuring Java and J2EE Application Server Managed Nodes for complete instructions).

Installing Web Server and Application Server Managed Nodes on Multiple

Machines

To install the OVTA web server or application server software on multiple machines, either copy the installer (install.bin) file onto each machine or make the file available on a shared network file system.

The file is located in /hpovta/InstData/<AIX|HPUX|Solaris|Linux >/VM on the CD-ROM drive.

For HP-UX IPF and Linux IPF, the file is located in /hpovta/InstData/ <HP-UX_IPF+Linux_IPF>/NoVM on the CD-ROM drive.

After the installer is available on the machine, run the installer.

Upgrading the Managed Nodes

The procedure for upgrading a managed node consists of the following:

1 If your installation is configured to monitor WebLogic or WebSphere, you must unconfigure them by doing the following:

— If you are upgrading from OVTA 3.0 or earlier versions, or from OVTA 3.1 and WLS 8 on AIX, or an existing OVTA managed node that is configured to monitor WebLogic, you must follow the unconfigure steps on page 96.

However, if you are upgrading from OVTA 3.1 (except OVTA 3.1 with WLS 8 on AIX), you do not need to unconfigure WebLogic.

(37)

— If you are upgrading an existing OVTA managed node that is configured to monitor WebSphere, you must follow the unconfigure steps on page 97.

2 Stop all web server and application server processes that are configured for monitoring by OVTA.

3 Stop OVTA by running the following command:

/<ovta_installation_dir>/bin/ovta stop

4 Verify that no processes are running libarm3 by using the fuser command. The exact command varies according to the operating system, as shown in the following table.

If the output of the fuser command indicates that there are processing holding libarm3, shut down that program gracefully (do not use kill -9).

The fuser executable is normally in /sbin or /usr/sbin.

5 Install the new OVTA (and reconfigure anything unconfigured in step 1, including manually configured JDBC drivers) following the instructions in Installing OVTA on Web Server and Application Server Managed Nodes on page 34.

6 If the file <ovta_installation_dir>/data/conf/ipainit.xml was modified in the previous installation, make the same modifications in the new ipainit.xml file. The old file is available as ipainit_<version>.xml.

7 To monitor WebLogic or WebSphere, run the corresponding configuration script(s) as explained in Chapter 5, Configuring Java and J2EE Application Server Managed Nodes.

8 Start OVTA following the instructions in Starting OVTA on page 91. VERY IMPORTANT: You must follow steps 2 and 3 in order.

Operating System Login Requirement Command

HP-UX Must be root /usr/sbin/fuser /opt/HPOV_IPA/lib/libarm3.sl

Solaris fuser /opt/HPOV_IPA/lib/libarm3.so

AIX fuser -x /usr/lpp/HPOV_IPA/lib/libarm3.a

HP OpenView Transaction Analyzer