HP OpenView Transaction Analyzer

Transcription

1 HP OpenView Transaction Analyzer For the UNIX (Sun Solaris, HP-UX, AIX, Linux) Operating Systems Software Version: 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 and , 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 Copyright Hewlett-Packard Development Company, L.P. Trademark Notices Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java TM 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: You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. This document is best viewed with Acrobat Reader version 6 or greater. 2

3 Support Please visit the HP OpenView support web site at: 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: To register for an HP Passport ID, go to: 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. 3

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

5 Contents 1 Overview Platform Support and System Requirements Measurement Server Remote OVTA Console Requirements Remote OVTA Configuration Editor Requirements Managed Node ActiveX Client Monitor JavaScript Client Monitor Installation Installing the OVTA Measurement Server Software Measurement Server Installation Wizard Licensing License Tool License Warnings Extending the 60-Day Trial License Configuring the Measurement Server Database SOLID Embedded Engine Oracle Standard Edition Upgrading the Measurement Server Managed Node Interoperability Installing OVTA on Web Server and Application Server Managed Nodes Managed Node Installation Wizard Installing Web Server and Application Server Managed Nodes on Multiple Machines Upgrading the Managed Nodes Silent Install Selecting Application Servers and Web Servers to be Monitored by OVTA Specifying a JVM for IPF Allowing Non-Root Use of OVTA Clock Synchronization Configuring Web Server Managed Nodes Sun Java System Web Server Configuration for Sun Java System Web Server Example magnus.conf File Example obj.conf File Apache Web Server Shared Memory Segments

6 5 Configuring Java and J2EE Application Server Managed Nodes BEA WebLogic Server (WLS) and BEA WebLogic Express (WLX) All Versions except WLS 8.1 on AIX and WLS 9 with HotSpot JVM Task 1: Running the config-wls.sh Script (Optional) Task 2: Configuring WLS for Each WLS Server Example Scripts Containing All Necessary Modifications Configuration for WebLogic Node Manager Additional Configuration for WebLogic All Versions, All Platforms (Optional) SQL Trace Sampling Scalable Client Monitoring Configuring the J2EE Collector BEA WebLogic Server (WLS) and BEA WebLogic Express (WLX) Version 8.1 on AIX and Version 9.x with HotSpot JVM Task 1: Running the BEAWlsInstall.sh Script Task 2: Instrumenting the JDBC Drivers Task 3: Configuring WLS for Each WLS Server Example Scripts Containing All Necessary Modifications Additional Configuration for WebLogic 8.1 on AIX or WebLogic 9.x with HotSpot (Optional) SQL Trace Sampling Scalable Client Monitoring Configuring the J2EE Collector IBM WebSphere Application Server 5.x Prerequisites for Configuring WebSphere 5.x Automatic Configuration of WebSphere 5.x Options WebSphere 5.x Installation Location Manual Configuration of WebSphere 5.x Task 1: Copy OVTA Jar Files to the WebSphere Extension Library Task 2: Set Environment Variables Task 3: Enable Servlet, JSP, Filter, EJB Monitoring Task 4: Enable JDBC Monitoring Task 5: Enable Apache SOAP Monitoring Task 6: Enable Web Services for J2EE SOAP Monitoring Verifying the Configuration of WebSphere 5.x Additional Configuration for WebSphere 5.x (Optional) SQL Trace Sampling Java Diagnostics Contextual Launch Scalable Client Monitoring IBM WebSphere Application Server 6.x Prerequisites for Configuring WebSphere 6.x Automatic Configuration of WebSphere 6.x Options Manual Configuration of WebSphere 6.x Task 1: Copy OVTA Jar Files to the WebSphere Extension Library Task 2: Set Environment Variables Task 3: Enable Servlet, JSP, Filter, EJB Monitoring Task 4: Enable JDBC Monitoring

7 Verifying the Configuration of WebSphere 6.x Additional Configuration for WebSphere 6.x (Optional) SQL Trace Sampling Java Diagnostics Contextual Launch Scalable Client Monitoring JBoss Application Server 3.2 and Automatic Configuration of the JBoss Application Server Manual Configuration of the JBoss Application Server Task 1: Copy OVTA Jar Files to the JBoss Library Task 2: Modify the Start Script of Each Instance of JBoss Verifying the Configuration of the JBoss Application Server Additional Configuration for JBoss (Optional) SQL Trace Sampling Java Diagnostics Contextual Launch Scalable Client Monitoring Tomcat Server (Servlet Container) 4.1, 5.0 and Automatic Configuration of the Tomcat Server Manual Configuration of the Tomcat Server Task 1: Modify the Tomcat Start Script Task 2: Copy OVTA Jar Files to the Tomcat Library Verifying the Configuration of the Tomcat Server Additional Configuration for Tomcat (Optional) SQL Trace Sampling Java Diagnostics Contextual Launch Scalable Client Monitoring Oracle Application Server 10g Version Automatic Configuration of the Oracle Application Server Manual Configuration of the Oracle Application Server Task 1: Copy OVTA Jar Files to the Oracle System Class Loader Directory Task 2: Append ovta-instr-all.jar to the System Classpath Task 3: Add OVTA to the OC4J Configuration Properties Verifying the Configuration of the Oracle Application Server Additional Configuration for the Oracle Application Server 10g (Optional) SQL Trace Sampling Java Diagnostics Contextual Launch Scalable Client Monitoring Enabling J2SE Monitoring for Java Starting and Stopping OVTA Starting OVTA Starting the OVTA Measurement Server Software Starting the OVTA Managed Node Software Verifying Communication between Managed Nodes and the Measurement Server Starting the OVTA Console Java Web Start Starting the OVTA Configuration Editor Using Java Web Start to Run the OVTA Configuration Editor

8 Stopping OVTA Stopping OVTA on the Measurement Server Stopping OVTA on Managed Nodes Uninstalling OVTA Uninstalling OVTA Software on Managed Nodes Unconfiguring the WebLogic Server Unconfiguring WebSphere Application Server Unconfiguring the JBoss Application Server Unconfiguring the Tomcat Application Server Unconfiguring the Oracle Application Server Unconfiguring the Sun Java System Web Server Unconfiguring the Apache Web Server Removing OVTA Uninstalling the Measurement Servers Removing the Oracle Database Removing OVTA HP-UX Solaris Uninstalling the OVTA Console Uninstalling the OVTA Configuration Editor Silent Uninstall Advanced Configuration Items that are Automatically Configured Client Monitor Transaction Agent Configuration Deploying the Client Monitor Web Application in a J2EE Application Server OVIS Integration Configuring the OVIS and OVTA Integration Running the OVIS and OVTA Console on a Client System OVTA and OVIS Web Recorder Transactions Java Diagnostics Agent Integration Managing Node Agents Running Node Agents as a Daemon Verifying that the UNIX Daemon is Running Starting Node Agents Manually Stopping Node Agents Changing from the SOLID Database to Oracle HTTPS Configuration Why use HTTPS? Server Authentication the Big Picture Configuring HTTPS in OVTA Example HTTPS Listener Configuration File Using Keytool to Configure HTTPS Configuring the OVTA Measurement Server for HTTPS Configuring the OVTA Managed Node for HTTPS Switching OVTA between HTTP and HTTPS

9 Alternate HTTP/HTTPS Port Number Configuration Configuring Proxy Settings Glossary Index

10 10

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

12 12 Chapter 1

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 Application Server Database Disk Space Memory Java 2 Platform, Standard Edition v 1.4 (JRE 1.4) (bundled with OVTA) HP Application Server (HP-AS) 8.1 (bundled with OVTA) 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) 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. 1 GB (minimum) System Requirements Disk Space in /tmp Directory SHMMAX Approximately 3 times the size of the OVTA installation program Greater than 20 MB SHMSEG Greater than or equal to 4 SEMMNI Should be increased by 2 13

14 System Requirements Maximum Process Heap Size (data segment size) Red Hat Linux 3 and 4, SuSE Linux Red Hat Enterprise Linux 2.1 Red Hat Linux Advanced Server 2.1 on IPF Solaris 5.8 (and later) on SPARC Greater than or equal to 256 MB ("ulimit -d" >= ) 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 or a latest version of this package. You can get this package from search.php?query=compat-libstdc%2b%2b The preferred installation location for this package is /opt/hpov_ipa/lib or / usr/lib. The "bc" package for example, bc i386.rpm (Other versions of Linux normally have this already installed.) Kernel version e.43smp or later Java Diagnostics requires recommended patches found at sunsolve.sun.com/pubcgi/show.pl?target=patches/j2se. Sun Solaris 8 Patches SunOS 5.8: Shared library patch for C++, SunOS 5.8: Linker patch Remote OVTA Console Requirements Component Java Browser Software Requirement JRE 1.4 (bundled with OVTA for most platforms) for Console use locally on the Measurement Server Microsoft Internet Explorer 5.0 or greater Netscape Navigator 4.7 or greater Java Web Start bundled with JRE 1.4 or greater Remote OVTA Configuration Editor Requirements Component Java Browser Software Requirement JRE 1.4 (bundled with OVTA for most platforms) for Console use locally on the Measurement Server Microsoft Internet Explorer 5.0 or greater Netscape Navigator 4.7 or greater Java Web Start bundled with JRE 1.4 or greater 14 Chapter 2

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 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 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) Platform Support and System Requirements 15

16 Supported Platforms 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 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 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 sdkrte1_3/downloads/index.html The BEA web site reports that WebLogic Server 6.1 is certified to work with SDKs from through Updates for WebLogic Server, SP1 through SP7, ship with a newer version of the Java SDK. For more up-to-date information on supported platforms, go to 16 Chapter 2

17 System Requirements Disk Space Disk Space in /tmp Directory SHMMAX 150 MB Approximately 3 times the size of the OVTA installation program Greater than 20 MB SHMSEG Greater than or equal to 2 Maximum Process Heap Size (data segment size) Red Hat Linux 3 and 4, SuSE Linux Red Hat Enterprise Linux 2.1 Red Hat Linux Advanced Server 2.1 on IPF Linux on IPF HP-UX IPF Solaris 5.8 (and later) on SPARC Sun Solaris Required Patches Other Patches Greater than or equal to 256 MB ("ulimit -d" >= ) 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 or a latest version of this package. You can get this package from search.php?query=compat-libstdc%2b%2b The preferred installation location for this package is /opt/hpov_ipa/lib or / usr/lib. The "bc" package for example bc i386.rpm (Other versions of Linux normally have this already installed.) Kernel version e.43smp or later libpthread-0.9.so and libc 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 so are included in glibc , which is available from RPM/redhat/enterprise/2.1AS/ia64/src/glibc src.html Library libstdc++-libc6.2-2.so.3. If this library is not already installed, you can download the gcc runtime package from At the time of this release, the following version is available. 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. Java Diagnostics requires recommended patches found at Solaris SunOS 5.8: Shared library patch for C++, SunOS 5.8: Linker patch All OS patches recommended by your JRE or JDK vendor. Platform Support and System Requirements 17

18 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. ActiveX Client Monitor Component Requirement Browser Microsoft Internet Explorer JavaScript Client Monitor Component Requirement Browser Microsoft Internet Explorer Netscape Navigator x 18 Chapter 2

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) Synchronize the Measurement Server and managed nodes clocks (see page 43) 19

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. 20 Chapter 3

21 If you create the link but delete the underlying directory, and then try to install OVTA, it will incorrectly report success. 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 <writable file system dir> 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. Installation 21

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 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 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 group ovta -jmxport 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. 13 Install and configure OVTA on the web server and application server managed nodes. 22 Chapter 3

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. 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. 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 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. Installation 23

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 Transaction Agent Tier 1 HP OV Transaction Agent Tier 2 HP OV Transaction Agent Tier 3 HP OV Transaction Agent Tier 4 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 Select autopass from the list of online product manuals. 24 Chapter 3

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. Installation 25

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 ( 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) or (800) Fax: (801) Hours of operation: 6:00 am to 6:00 pm MST Hewlett-Packard Password Center for Europe/Africa Phone: ( ) Fax: ( ) Hours of operation: 9:00 to 18:00 CET Hewlett-Packard Password Center for Asia Pacific Phone: (outside Japan) ( ) or (within Japan) ( ) Fax: ( ) 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) IP address and operating system platform of the OVTA Measurement Server 26 Chapter 3

27 Your trial license/password extension will be sent to you via . 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. Installation 27