Tivoli Tivoli Monitoring Transaction Performance -...

Tivoli® IBM Tivoli Monitoring for Transaction Performance

Installation and Configuration Guide

Version 5.3.0

SC32-9107-00

��

Tivoli® IBM Tivoli Monitoring for Transaction Performance

Installation and Configuration Guide

Version 5.3.0

SC32-9107-00

��

Note

Before using this information and the product it supports, read the information Appendix G, “Notices,” on page 141.

First Edition (October 2003)

This edition applies to Version 5.3.0 of IBM® Tivoli® Monitoring for Transaction Performance and to all subsequent

releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2003. All rights reserved. US Government Users

Restricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this guide . . . . . . . . . . . ix

Who should read this guide . . . . . . . . . ix

Publications . . . . . . . . . . . . . . ix

IBM Tivoli Monitoring for Transaction

Performance library . . . . . . . . . . . ix

Related publications . . . . . . . . . . . x

Accessing publications online . . . . . . . xi

Ordering publications . . . . . . . . . . xii

Accessibility . . . . . . . . . . . . . . xii

Tivoli technical training . . . . . . . . . . xii

Support information . . . . . . . . . . . xii

Conventions used in this guide . . . . . . . xiii

Typeface conventions . . . . . . . . . . xiii

Operating system-dependent variables and

paths . . . . . . . . . . . . . . . xiii

Tivoli command syntax . . . . . . . . . xiii

Chapter 1. Installation overview . . . . 1

Preparing for installation . . . . . . . . . . 1

Choose an installation option . . . . . . . . 2

Using installation files from the Web . . . . . 2

Using installation files from a CD-ROMs . . . . 3

Chapter 2. Prerequisites . . . . . . . . 7

Supported operating systems . . . . . . . . . 7

Management server prerequisites . . . . . . . 13

Space and memory requirements . . . . . . 13

Prerequisite software . . . . . . . . . . 13

Management agent and Store and Forward agent

prerequisites . . . . . . . . . . . . . . 13

Space and memory requirements . . . . . . 13

Prerequisite software . . . . . . . . . . 14

Supported browsers . . . . . . . . . . . 14

Java Virtual Memory (JVM) heap size requirements 14

Communications Ports . . . . . . . . . . . 15

Chapter 3. Preparing an existing

database for configuration with the

management server . . . . . . . . . 17

Preparing an existing DB2 database . . . . . . 17

Guidelines for preparing an Oracle database . . . 21

Chapter 4. Installing a management

server . . . . . . . . . . . . . . . 27

Typical installation: management server . . . . . 27

Custom installation: management server . . . . . 34

Chapter 5. Installing a Store and

Forward agent . . . . . . . . . . . 45

Chapter 6. Installing a management

agent . . . . . . . . . . . . . . . 51

Installing a management agent . . . . . . . . 51

Setting up management agents for z/OS . . . . 54

Installing and configuring a management agent in

OS/400 . . . . . . . . . . . . . . . . 60

Configuring your management agent to start at

OS/400 IPL . . . . . . . . . . . . . 61

Chapter 7. Verifying your installation 63

Verifying the installation of a management agent . . 63

Chapter 8. Installing the Synthetic

Transaction Recorders and Generic

Windows . . . . . . . . . . . . . . 65

Preparing for installation of Synthetic Transaction

software . . . . . . . . . . . . . . . 66

Prerequisites for a Synthetic Transaction Recorder 67

Installing the recording software for Synthetic

Transaction Investigator . . . . . . . . . . 67

Installing Generic Windows recording and playback 71

Chapter 9. Creating and deploying SSL

key files . . . . . . . . . . . . . . 73

Creating key files . . . . . . . . . . . . 73

Procedure . . . . . . . . . . . . . . 73

Creating a KeyDataBase for the WebSphere

Caching Proxy on the Store and Forward Agent . 75

Importing certificates into the JKS and KDB files 76

Deploying the WebSphere Application Server key

files . . . . . . . . . . . . . . . . 77

Deploying the management server key file . . . 78

Deploying the Store and Forward Agent key file 78

Deploying the management agent key file . . . 79

Chapter 10. Configuring product

settings in WebSphere Application

Server . . . . . . . . . . . . . . . 81

Accessing the administrative console of the

WebSphere Application Server . . . . . . . . 81

Possible port number conflicts on AIX . . . . . 81

Assigning authorization roles . . . . . . . . 81

Chapter 11. Installing a language pack 85

Appendix A. Upgrading an installation

of IBM Tivoli Monitoring for

Transaction Performance . . . . . . . 89

Upgrading IBM Tivoli Monitoring for Transaction

Performance Version 5.2 to Version 5.3 . . . . . 89

Upgrading IBM Tivoli Monitoring for Transaction

Performance Version 5.1 to Version 5.3 . . . . . 94

iii

Cleaning up the WebSphere Application Server

base directory . . . . . . . . . . . . . 101

Appendix B. Uninstalling IBM Tivoli

Monitoring for Transaction

Performance components . . . . . . 103

Appendix C. Performing a silent

installation . . . . . . . . . . . . 111

Performing a silent installation of the management

server . . . . . . . . . . . . . . . . 111

Performing a silent installation of a management

agent . . . . . . . . . . . . . . . . 114

Syntax of the installation command . . . . . . 115

Basic syntax . . . . . . . . . . . . . 115

Syntax of configuration options . . . . . . 117

Requirements for a response file . . . . . . . 117

When to use a response file . . . . . . . 118

When not to use a response file . . . . . . 118

Lists of settings and options . . . . . . . . 118

Options for monitoring installation messages . . . 118

Installation program settings . . . . . . . . 119

Configuration options for the management server 121

-G configuration options . . . . . . . . . 122

-P configuration option . . . . . . . . . 123

-W configuration options . . . . . . . . 123

Configuration options for the management agent 129

-G configuration options . . . . . . . . . 130

-P configuration option . . . . . . . . . 130

-W configuration options . . . . . . . . 131

Appendix D. Integrating with IBM

Tivoli Intelligent Orchestrator . . . . 133

Installing the management agent automation

package . . . . . . . . . . . . . . . 133

Appendix E. Enabling Java 2 security

with IBM Tivoli Monitoring for

Transaction Performance . . . . . . 135

Appendix F. Support information . . . 137

Searching knowledge bases . . . . . . . . . 137

Search the information center on your local

system or network . . . . . . . . . . . 137

Search the Internet . . . . . . . . . . 137

Obtaining fixes . . . . . . . . . . . . . 137

Contacting IBM Software Support . . . . . . 138

Determine the business impact of your problem 139

Describe your problem and gather background

information . . . . . . . . . . . . . 139

Submit your problem to IBM Software Support 139

Appendix G. Notices . . . . . . . . 141

Trademarks . . . . . . . . . . . . . . 142

Index . . . . . . . . . . . . . . . 145

iv IBM Tivoli Monitoring for Transaction Performance: Installation and Configuration Guide

Figures

1. Embedded installation information window 29

2. SSL Enablement for Management Server

Communication window . . . . . . . . 30

3. SSL Enablement for Management Server

Communication window . . . . . . . . 38

4. Communication with the Management Server

or with the Store and Forward Agent window . 47

5. Key File window . . . . . . . . . . . 49

6. Download STI Recorder window . . . . . 69

7. Synthetic Transaction Investigator Management

Server Information window . . . . . . . 70

v

vi IBM Tivoli Monitoring for Transaction Performance: Installation and Configuration Guide

Tables

1. Summary of goals for installing the product 1

2. Estimated size of installation images . . . . 2

3. Supported operating systems for management

servers, management agents, and store and

forward agents . . . . . . . . . . . . 8

4. Supported operating systems for J2EE

instrumentation . . . . . . . . . . . 9

5. Supported operating systems for Synthetic

Transaction Recorder (STI) and Generic

Windows . . . . . . . . . . . . . 11

6. Supported operating systems for Quality of

Service (QoS) . . . . . . . . . . . . 12

7. Space and memory requirements . . . . . 13

8. Space and memory requirements . . . . . 13

9. Communications ports — SSL enabled . . . 15

10. Communications ports — SSL not enabled 15

11. OS/400 installation prerequisites . . . . . 60

12. Goals for the installation of Synthetic

Transaction software . . . . . . . . . 66

13. Synthetic Transaction Recorder and player

requirements . . . . . . . . . . . . 67

14. Available authorization roles . . . . . . . 82

15. Locations of language pack installation

programs . . . . . . . . . . . . . 87

16. Goals for the uninstallation of management

agents . . . . . . . . . . . . . . 103

17. Goals for the silent installation of the product 111

18. Methods for specifying options in an

installation command . . . . . . . . . 113

19. Trace level settings for installation log files 119

20. Product options for installing a management

server . . . . . . . . . . . . . . 120

21. Configuration options for the management

server . . . . . . . . . . . . . . 121

22. Configuration options for global responses 123

23. Product option for management server 123

24. Wizard-related options for the management

server . . . . . . . . . . . . . . 124

25. Configuration options for the management

agent . . . . . . . . . . . . . . 129

26. Configuration options for global responses 130

27. Product option for management agents 130

28. Wizard-related options for the management

agent . . . . . . . . . . . . . . 131

vii

viii IBM Tivoli Monitoring for Transaction Performance: Installation and Configuration Guide

About this guide

IBM Tivoli Monitoring for Transaction Performance enables you to manage the

availability and performance of your Web application environment. It gathers the

detailed information you need to track and improve transaction times, with the

goal of ensuring optimal responsiveness.

Who should read this guide

This guide is for system and Web administrators who want to install IBM Tivoli

Monitoring for Transaction Performance and related software. The guide assumes

that readers are familiar with maintaining operating systems, administering Web

servers, maintaining databases, and general information technology (IT)

procedures. Specifically, readers of this guide must have some knowledge of the

following software:

v Operating systems on which you intend to install product components.

Supported operating systems include Windows® 2000, Windows XP, AIX®,

Solaris Operating Environment (referred to as Solaris in this document), Red Hat

Linux, SuSE Linux, TurboLinux, HPUX, z/OS®, and OS/400®.

v Web servers, such as IBM® HTTP Server, Apache HTTP Server, and Microsoft®

Internet Information Server.

v Web application servers, such as IBM WebSphere® Application Server.

v Internet protocols such as HTTP, HTTPS, TCP/IP, Secure Sockets Layer (SSL),

and Transport Layer Security (TLS).

v Digital certificates for secure communication.

v IBM DB2® or Oracle database management systems.

The product provides optional integration with the IBM Tivoli Enterprise Console

and Tivoli Enterprise™ Data Warehouse products. Readers must have some

knowledge of these products to decide whether to use them in conjunction with

IBM Tivoli Monitoring for Transaction Performance.

Publications

This section lists publications in the IBM Tivoli Monitoring for Transaction

Performance library and related documents. It also describes how to access Tivoli®

publications online and how to order Tivoli publications.

IBM Tivoli Monitoring for Transaction Performance library

The following documents provide information about the IBM Tivoli Monitoring for

Transaction Performance product:

v IBM Tivoli Monitoring for Transaction Performance Installation and Configuration

Guide, SC32-9107-00

Provides prerequisite information and instructions for installing the product.

This guide also contains information that you might find useful after installing

the product, such as uninstallation instructions.

v IBM Tivoli Monitoring for Transaction Performance Evaluation Guide, GC32-9190-00

Provides prerequisite information and instructions for performing a very simple

installation of the product and deploying one of the components for evaluation

ix

purposes. This document enables you to go through the installation wizards and

see the product’s user interface performing some basic task and functions.

v IBM Tivoli Monitoring for Transaction Performance Administrator’s Guide,

GC32–9189–00

Provides detailed procedures for deploying and using each of the product

components.

v IBM Tivoli Monitoring for Transaction Performance Checking Performance and

Availability Guide, SC32–9106–00

The guide also describes the browser-based graphical user interface (GUI), the

help system, and how to produce graphical reports from transaction

performance data.

v IBM Tivoli Monitoring for Transaction Performance Problem Determination Guide,

SC32-9108–00

Provides the latest information about known product limitations and

workarounds for the product. To ensure that the information is the latest

available, this document is provided only on the Web, where it is updated as

needed.

v IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance

Warehouse Enablement Pack Implementation Guide, SC32-9109-00

Describes how to install and configure the warehouse enablement pack for the

product. This document also describes the data flow and data structures used by

the warehouse pack. The warehouse pack enables the product to transfer data to

the Tivoli Enterprise Data Warehouse.

v Program Directory for IBM Tivoli Monitoring for Transaction Performance for z/OS,

Version 5.3

Describes installing and maintaining IBM Tivoli Monitoring for Transaction

Performance for z\OS.

Related publications

IBM Tivoli Monitoring for Transaction Performance can optionally be integrated

with a number of enterprise products to provide more advanced capabilities.

Following is a list of these products and some of the publications provided by each

product.

v IBM Tivoli Enterprise Console®

– IBM Tivoli Enterprise Console Installation Guide, GC32–0823

Discusses how to install, upgrade, and remove IBM Tivoli Enterprise Console

components and provides details about using the event database installation

assistant.

– IBM Tivoli Enterprise Console User’s Guide, GC32-0667

Provides information needed to understand and set up the IBM Tivoli

Enterprise Console and describes procedures for using all components of the

product.

– IBM Tivoli Enterprise Console Rule Builder’s Guide, GC32-0669

Provides information about developing rules for automating the management

of IBM Tivoli Enterprise Console events received by the IBM Tivoli Enterprise

Console event server.v Tivoli Enterprise Data Warehouse

– Tivoli Enterprise Data Warehouse Release Notes®, GI11-0857

Provides late-breaking information about Tivoli Enterprise Data Warehouse

and lists hardware requirements and software prerequisites.

x IBM Tivoli Monitoring for Transaction Performance: Installation and Configuration Guide

– Installing and Configuring Tivoli Enterprise Data Warehouse, GC32-0744

Describes how Tivoli Enterprise Data Warehouse fits into your enterprise,

explains how to plan for its deployment, and gives installation and

configuration instructions. It provides an introduction to the built-in program

for creating and running reports, and contains maintenance procedures and

troubleshooting information.

– Enabling an Application for Tivoli Enterprise Data Warehouse, GC32-0745

Provides information about connecting an application to Tivoli Enterprise

Data Warehouse. This book is for application programmers who use Tivoli

Enterprise Data Warehouse to store and report on their application’s data,

data warehousing experts who import Tivoli Enterprise Data Warehouse data

into business intelligence applications, and customers who use their local data

in the warehouse.v IBM WebSphere Site Analyzer

All information about IBM WebSphere Site Analyzer is provided on the

following Web site:

http://www-3.ibm.com/software/webservers/siteanalyzer/library.html

The following IBM Redbooks™ provide information about advanced

configuration options for WebSphere Application Server, which hosts the

management server application for IBM Tivoli Monitoring for Transaction

Performance:

– IBM WebSphere Application Server System Management and Configuration:

WebSphere Handbook Series, SG24-6195

– IBM WebSphere Security WebSphere Handbook Series, SG24-6573v IBM WebSphere Application Server, Version 5.1

All information about the IBM WebSphere Application Server Version 5.1 is

provided on the following Web site:

http://www-3.ibm.com/software/webservers/appserv/was/library/

v IBM WebSphere Caching Proxy, Version 5.1

All information about the IBM WebSphere Caching Proxy Version 5.1 is

provided on the following Web site:

http://www-306.ibm.com/software/webservers/appserv/ecinfocenter.html

The Tivoli Glossary includes definitions for many of the technical terms related to

Tivoli software. The Tivoli Glossary is available, in English only, at the following

Web site:

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm

Accessing publications online

The documentation CD contains the publications that are in the product library.

The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become

available and whenever they are updated, to the Tivoli software information center

Web site. Access the Tivoli software information center by first going to the Tivoli

software library at the following Web address:

http://www.ibm.com/software/tivoli/library/

About this guide xi

http://www-3.ibm.com/software/webservers/siteanalyzer/library.html

http://www-3.ibm.com/software/webservers/appserv/was/library/

http://www-306.ibm.com/software/webservers/appserv/ecinfocenter.html

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm

http://www.ibm.com/software/tivoli/library/

Scroll down and click the Product manuals link. In the Tivoli Technical Product

Documents Alphabetical Listing window, click M to access all of the IBM Tivoli

Monitoring product manuals.

Note: If you print PDF documents on other than letter-sized paper, set the option

in the File → Print window that allows Adobe Reader to print letter-sized

pages on your local paper.

The IBM Software Support Web site provides the latest information about known

product limitations and workarounds in the form of technotes for your product.

You can view this information at the following Web site:

http://www.ibm.com/software/support

Ordering publications

You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/

publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755

v In Canada: 800-426-4968

In other countries, see the following Web site for a list of telephone numbers:

http://www.ibm.com/software/tivoli/order-lit/

Accessibility

Accessibility features help users with a physical disability, such as restricted

mobility or limited vision, to use software products successfully. With this product,

you can use assistive technologies to hear and navigate the interface. You can also

use the keyboard instead of the mouse to operate most features of the graphical

user interface.

For additional information, see the Accessibility Appendix in the administrator’s

guide for this product.

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli

Education Web site:

http://www.ibm.com/software/tivoli/education/

Support information

Appendix F, “Support information,” on page 137 describes the following options

for obtaining support for IBM products:

v “Searching knowledge bases” on page 137

v “Obtaining fixes” on page 137

v “Contacting IBM Software Support” on page 138

xii IBM Tivoli Monitoring for Transaction Performance: Installation and Configuration Guide


http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

http://www.ibm.com/software/tivoli/order-lit/

http://www-306.ibm.com/software/tivoli/education/

Conventions used in this guide

This guide uses several conventions for special terms and actions, and operating

system-dependent commands and paths.

Typeface conventions

This guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwise

difficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spin

buttons, fields, folders, icons, list boxes, items inside list boxes,

multicolumn lists, containers, menu choices, menu names, tabs, property

sheets), labels (such as Tip:, and Operating system considerations:)

v Keywords and parameters in text

Italic

v Words defined in text

v Emphasis of words (for example, ″Use the word that to introduce a

restrictive clause.″)

v New terms in text (except in a definition list)

v Variables and values you must provide

Monospace

v Code and other examples

v File names, programming keywords, and other elements that are difficult

to distinguish from surrounding text

v Message text and prompts addressed to the user

v Text that the user must type

v Values for arguments or command options

Operating system-dependent variables and paths

The publications in this library use the UNIX® convention for specifying

environment variables and for directory notation.

When using the Windows command line, replace $variable with %variable% for

environment variables and replace each forward slash (/) with a backslash (\) in

directory paths. The names of environment variables are not always the same in

Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in

UNIX.

Note: If you are using the bash shell on a Windows system, you can use the UNIX

conventions.

Tivoli command syntax

The following special characters define Tivoli command syntax:

[ ] Identifies elements that are optional. Required elements do not have

brackets around them.

... Indicates that you can specify multiple values for the previous element.

Separate multiple values by a space, unless otherwise directed by

command information.

About this guide xiii

If the ellipsis for an element follows a closing bracket, use the syntax

within the brackets to specify multiple values. For example, to specify two

administrators for the option [–a admin]..., use –a admin1 –a admin2.

If the ellipsis for an element is within the brackets, use the syntax of the

last element to specify multiple values. For example, to specify two hosts

for the option [–h host...], use –h host1 host2.

| Indicates mutually exclusive information. You can use the element on

either the left or right of the vertical bar.

{ } Delimits a set of mutually exclusive elements when a command requires

one of them. Brackets ([ ]) are around elements that are optional.

In addition to the special characters, Tivoli command syntax uses the typeface

conventions described in “Typeface conventions” on page xiii. The following

examples illustrate the typeface conventions used in Tivoli command syntax:

v wcrtpr [–a admin]... [–s region] [–m resource]... name

The name argument is the only required element for the wcrtpr command. The

brackets around the options indicate they are optional. The ellipsis after the –a

admin resource option means that you can specify multiple administrators

multiple times. The ellipsis after the –m resource option means that you can

specify multiple resources multiple times.v wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}

The –f, –i, and object elements are mutually exclusive. Braces that surround

elements indicate that you are including a required element. If you specify the

object argument, you can specify more than one object.

xiv IBM Tivoli Monitoring for Transaction Performance: Installation and Configuration Guide

Chapter 1. Installation overview

Table 1 summarizes the installation activities for IBM Tivoli Monitoring for

Transaction Performance.

Table 1. Summary of goals for installing the product

Goals Refer to

Pre-installation

Choose an installation option. See “Choose an installation option” on page 2 to decide

which option to use.

Review the software and hardware requirements. Chapter 2, “Prerequisites,” on page 7

Obtain the installation software. “Using installation files from the Web” on page 2“Using

installation files from a CD-ROMs” on page 3

Installing the management server and management agents

Perform the installation. Perform the following installation procedures:

v Install a management server Chapter 4, “Installing a

management server,” on page 27

v Optionally install a Store and Forward agent

Chapter 5, “Installing a Store and Forward agent,” on

page 45

v Install a management agent Chapter 6, “Installing a

management agent,” on page 51

Upgrade

Upgrade Version 5.1 or 5.2 to Version 5.3. Appendix A, “Upgrading an installation of IBM Tivoli

Monitoring for Transaction Performance,” on page 89

Completing an installation

Verify your installation. “Verifying the installation of a management agent” on

page 63

Install synthetic transaction recorders that you use to

create transactions that you can run repeatedly. (You use

recorded transactions in Playback policies that monitor

the performance of the system for typical user

operations.)

Chapter 8, “Installing the Synthetic Transaction Recorders

and Generic Windows,” on page 65

Install Generic Windows. “Installing Generic Windows recording and playback” on

page 71

Uninstallation

Uninstall the management server, management agents

and other product components to resolve problems or at

the end of the product life cycle.

Appendix B, “Uninstalling IBM Tivoli Monitoring for

Transaction Performance components,” on page 103

Preparing for installation

This section provides the following descriptions and procedures for preparing to

install IBM Tivoli Monitoring for Transaction Performance:

v “Choose an installation option” on page 2

v “Using installation files from the Web” on page 2

v “Using installation files from a CD-ROMs” on page 3

1

Choose an installation option

Choose the installation procedure that meets your requirements.

The typical installation process installs IBM Tivoli Monitoring for Transaction

Performance (management server and management agent), IBM DB2 Version 8.1,

WebSphere Application Server Version 5.1, and, with the secured installation, the

Store and Forward agent.

A custom installation enables you to use an existing version of a database, either

IBM DB2 or Oracle, and an existing version of WebSphere Application Server. The

installation software looks for existing databases and versions of WebSphere

Application Server. If they exist on the computer on which you are performing this

installation, follow the custom installation procedures.

Note: If you want to install the management server on a computer that already

hosts Tivoli products, consider these points:

v Health Console for IBM Tivoli Monitoring: The Health Console runs on

the IBM WebSphere Application Server, Version 4.0. Version 4.0 server

uses the same default ports as Version 5.x. Install the WebSphere server

for the management server (Version 5.x) on a port other than the default

or the two versions of WebSphere could have a port conflict.

v Previous version of IBM Tivoli Monitoring for Transaction Performance:

If a previous version of the product is installed on the target computer,

you must perform an upgrade to version 5.3. See Appendix A,

“Upgrading an installation of IBM Tivoli Monitoring for Transaction

Performance,” on page 89 for more information.

Using installation files from the Web

Objective

To obtain and access the installation files for IBM Tivoli Monitoring for Transaction

Performance from the Web.

Background information

This procedure describes how to download the installation software from the Web.

This method requires a user ID and password to access the software download site

for IBM. Your IBM Sales representative provides this ID and password. See Step 1

on page 3 for details. The following table contains the estimated size of the

installation files:

Table 2. Estimated size of installation images

Components Installation image size

Management server 1 G

Store and Forward agent 400® MB

Management agent 400 MB

DB2 (embedded installation image) 500 MB

IBM WebSphere Application Server

(embedded installation image)

500 MB

IBM WebSphere Caching Proxy 220 MB

2 IBM Tivoli Monitoring for Transaction Performance: Installation and Configuration Guide

Required authorization role

On UNIX, the user who performs this procedure must have root privileges. On

Windows, the user who performs this procedure must have membership in the

Administrators group.

Before you begin

None

When you finish

You are ready to install the product.

Procedure

1. Contact your IBM sales representative to receive your user ID and password

and Web site address for Passport Advantage® of the IBM Software Group.

Contact IBM Sales for more information. No fee is charged for this distribution

option.

2. Choose a directory in which to store the installation images.

Additional Information: The directory must be accessible to the computers on

which you are installing the management server and management agents. For a

remote installation on UNIX systems, mount the remote directory on the target

computer. For a remote installation on Windows systems, map the remote

directory to the target computer in Windows Explorer.

3. Expand the software packages to create a directory to hold the installation

images.

The expanded directory structure is as follows:

Note: There is no ITMTP_WTP_2 directory as designed. If you receive the

product on CD-ROMs the content of the ITMTP_WTP_1/disk2 directory

is contained on CD-ROM ITMTP_WTP_2.

installation_image_directory

ITMTP_WTP_1

disk1 — management server

disk2 — rational robot (installation from the management server)

ITMTP_WTP_3

MA — management agent

SnF — store and forward agent

ITMTP_WTP_4

MS_52Upgrade — upgrade from Version 5.2 to 5.3

SnFUpgrade — upgrade the store and forward agent

ITMTP_WTP_5

51_Upgrade — upgrade from Version 5.1 to 5.3

Robot — rational robot (expanded image for installation from CD-ROM)

tdw_weps — Tivoli Data Warehouse enablement

tio — Tivoli Intelligent Orchestrator

Using installation files from a CD-ROMs

Objective

To install IBM Tivoli Monitoring for Transaction Performance using installation

CD-ROMs.

Chapter 1. Installation overview 3


This procedure describes your options for using the installation CD-ROMs.

(Alternatively, you can download the installation software from the IBM Web site,

as described in “Using installation files from the Web” on page 2.)





Before you begin

None

When you finish

You are ready to install the product.

Procedure

You can use the CD-ROMs in either of the following ways:

Copy the contents of the CD-ROMs to a hard drive and create a directory to

hold the installation images.

Note: If you create a directory to hold the installation images on your hard

drive the content of ITMTP_WTP_2 must be copied to

ITMTP_WTP_1/disk2. See, Step 3 on page 3.

– OR–

Run an installation from CD-ROMs

Launch the installation program from the CD-ROM drive of your

computer. See the Problem Determination Guide for information about

mounting the CD-ROM drive on UNIX-based operating systems.

In a CD–ROM based installation of the management server and Store and

Forward agent, the installation program copies the product installation files

to a temporary directory on your hard disk. The installation program then

starts on your computer, prompting you for the CD-ROMs that contain

enablement software, such as IBM WebSphere Application Server or IBM

DB2, or information about existing versions of these applications. These

images require at least 1 G of space.

Notes:

1. You must remove all of the installation program files and directories

from the temporary directory before rerunning the installation. The

temporary directory is: $temp\tmtpInst\

2. If you are installing with CD-ROMs, the installation program prompts

you to insert the DB2 and WebSphere Application Server CD-ROMs for

the management server and the WebSphere Caching Proxy CD-ROM

for the Store and Forward agent.

In some cases on a Windows computer, the installation program also

automatically launches the installation wizards for these products.

Minimize the wizards, if they appear. The installation takes place

silently, without user intervention.

You can disable the Windows autorun feature as follows:

a. Access the utilities directory in the installation CD-ROM.

b. Copy the enable_autorun.reg and disable_autorun.reg scripts to a

temporary directory on the target computer.


c. Run the disable_autorun.reg script in a command-line interface or

by double-clicking it. The script disables the autorun feature in the

Windows Registry.

d. Restart Windows so that your changes take effect.

e. Complete the installation of the product.

f. Run the enable_autorun.reg script in a command-line interface. The

script enables the autorun feature again.

Chapter 1. Installation overview 5


Chapter 2. Prerequisites

The following table lists the operating systems that IBM Tivoli Monitoring for

Transaction Performance supports. All service levels listed are minimum service

levels.

Further information about prerequisites can be found in the following sections:

v “Supported operating systems”

v “Management server prerequisites” on page 13

v “Management agent and Store and Forward agent prerequisites” on page 13

v “Supported browsers” on page 14

Supported operating systems

7

Tabl

e 3.

S

uppo

rted

op

erat

ing

syst

ems

for

man

agem

ent

serv

ers,

m

anag

emen

t ag

ents

, an

d st

ore

and

forw

ard

agen

ts

Op

erat

ing

Sys

tem

M

anag

emen

t se

rver

1

Man

agem

ent

agen

t S

tore

an

d fo

rwar

d

agen

t

AIX

V

ersi

on 5.

1 Ye

s Ye

s Ye

s

AIX

V

ersi

on 5.

2 Ye

s Ye

s Ye

s

HP-

UX

11

i Ye

s Ye

s Ye

s

OS/

400

Ver

sion

5

Rel

ease

2

Yes

OS/

400

Ver

sion

5

Rel

ease

3

Yes

Red

H

at E

nter

pris

e L

inux

V

ersi

on 2.

1 on

a

2.4

kern

el on

xS

erie

s®

Yes

Yes

Yes

Red

H

at E

nter

pris

e L

inux

V

ersi

on 3.

0 A

dva

nced

Se

rver

, Ent

erpr

ise

Serv

er an

d

Wor

ksta

tion

on

iS

erie

s™, x

Seri

es, a

nd zS

erie

s®

Yes

Yes

Red

H

at E

nter

pris

e L

inux

V

ersi

on 3.

0 A

dva

nced

Se

rver

, Ent

erpr

ise

Serv

er an

d

Wor

ksta

tion

on

pS

erie

s®

Yes

Yes

Red

Fl

ag A

dva

nced

Se

rver

4.

0 Ye

s Ye

s

Sun

Sola

ris

8 Ye

s Ye

s Ye

s

Sun

Sola

ris

9 Ye

s Ye

s Ye

s

SuSE

SL

ES

Ver

sion

7

on a

2.4

kern

el on

xS

erie

s an

d zS

erie

s Ye

s Ye

s

SuSE

SL

ES

Ver

sion

8

or U

nite

dL

inux

1.

0 w

ith

Serv

ice

Pack

2a

on

iS

erie

s Ye

s Ye

s

SuSE

SL

ES

Ver

sion

8

or U

nite

dL

inux

1.

0 w

ith

Serv

ice

Pack

2a

on

pS

erie

s, xS

erie

s an

d

zSer

ies

Yes

Yes

Yes

Win

dow

s 20

00 A

dva

nced

Se

rver

w

ith

Serv

ice

Pack

42

Yes

Yes

Yes

Win

dow

s 20

00 Pr

ofes

sion

al w

ith

Serv

ice

Pack

42

Yes

Win

dow

s 20

00 Se

rver

w

ith

Serv

ice

Pack

42

Yes

Yes

Yes

Win

dow

s 20

03 Se

rver

E

nter

pris

e E

dit

ion

and

St

and

ard

E

dit

ion2

Yes

Yes

Yes

Win

dow

s X

P Pr

ofes

sion

al w

ith

Serv

ice

Pack

12

Yes

z/O

S V

ersi

on 1,

R

elea

se 4

Yes

z/O

S V

ersi

on 1

Rel

ease

5

Yes

Not

es:

1.

All

patc

hes

that

ar

e re

quir

ed by

W

ebSp

here

A

pplic

atio

n Se

rver

5.

1 ar

e al

so re

quir

ed fo

r th

is pr

oduc

t.

2.

You

cann

ot in

stal

l on

em

ulat

ed ix

86 en

viro

nmen

ts or

en

viro

nmen

ts w

here

W

ind

ows

is no

t th

e in

itia

lly lo

aded

op

erat

ing

syst

em (s

uch

as sl

ave

ix86

pr

oces

sor

card

s or

m

ixed

pr

oces

sor

envi

ronm

ents

)


Tabl

e 4.

S

uppo

rted

op

erat

ing

syst

ems

for

J2E

E in

stru

men

tatio

n

Op

erat

ing

Sys

tem

W

ebS

ph

ere,

Ver

sion

4.

0x

Ad

van

ced

En

terp

rise

an

d

Web

Sp

her

e 4.

1 E

nte

rpri

se E

dit

ion

Web

Sp

her

e,

Ver

sion

s 5.

0, 5.

0.1,

and

5.

0.2

Bas

e E

dit

ion

an

d

En

terp

rise

E

dit

ion

Web

Sp

her

e V

ersi

ons

5.1

and

5.1.

1 B

ase

Ed

itio

n

Web

Sp

her

e V

ersi

ons

5.1

Bu

sin

ess

Inte

grat

ion

S

erve

r

Web

Log

ic 7.

0 S

ervi

ce P

ack

1

AIX

V

ersi

on 5.

1 Ye

s Ye

s Ye

s Ye

s Ye

s

AIX

V

ersi

on 5.

2 Ye

s Ye

s Ye

s Ye

s Ye

s

HP-

UX

11

i Ye

s Ye

s Ye

s Ye

s

OS/

400

Ver

sion

5

Rel

ease

2

Yes1

OS/

400

Ver

sion

5

Rel

ease

3

Yes1

Red

H

at E

nter

pris

e L

inux

V

ersi

on 2.

1 on

a

2.4

kern

el

on xS

erie

s Ye

s Ye

s Ye

s Ye

s

Red

H

at E

nter

pris

e L

inux

, Ver

sion

3.

0 A

dva

nced

Serv

er, E

nter

pris

e Se

rver

an

d W

orks

tati

on on

iS

erie

s an

d pS

erie

s

Yes

Yes

Red

H

at E

nter

pris

e L

inux

, Ver

sion

3.

0 A

dva

nced

Serv

er, E

nter

pris

e Se

rver

an

d W

orks

tati

on on

xS

erie

s an

d zS

erie

s

Yes

Yes

Red

Fl

ag A

dva

nced

Se

rver

4.

0 Ye

s Ye

s

Sun

Sola

ris

8 Ye

s Ye

s Ye

s Ye

s Ye

s

Sun

Sola

ris

9 Ye

s Ye

s Ye

s Ye

s Ye

s

SuSE

SL

ES

Ver

sion

7

on a

2.4

kern

el on

xS

erie

s Ye

s Ye

s Ye

s

SuSE

SL

ES

Ver

sion

7

on a

2.4

kern

el on

zS

erie

s Ye

s Ye

s

SuSE

SL

ES

Ver

sion

8.

0 or

U

nite

dL

inux

1.

0 w

ith

Serv

ice

Pack

2a

on

a

2.4

kern

el on

a

2.4

kern

el on

iSer

ies

and

pS

erie

s

Yes

Yes

Yes

SuSE

SL

ES

Ver

sion

8.

0 or

U

nite

dL

inux

1.

0 w

ith

Serv

ice

Pack

2a

on

a

2.4

kern

el on

xS

erie

s Ye

s Ye

s Ye

s Ye

s Ye

s

SuSE

SL

ES

Ver

sion

8.

0 or

U

nite

dL

inux

1.

0 w

ith

Serv

ice

Pack

2a

on

a

2.4

kern

el on

zS

erie

s Ye

s Ye

s Ye

s Ye

s

Win

dow

s 20

00 A

dva

nced

Se

rver

w

ith

Serv

ice

Pack

4

Yes

Yes

Yes

Yes

Yes

Win

dow

s 20

00 Se

rver

w

ith

Serv

ice

Pack

4

Yes

Yes

Yes

Yes

Chapter 2. Prerequisites 9

Tabl

e 4.

S

uppo

rted

op

erat

ing

syst

ems

for

J2E

E in

stru

men

tatio

n (c

ontin

ued)

Op

erat

ing

Sys

tem

W

ebS

ph

ere,

Ver

sion

4.

0x

Ad

van

ced

En

terp

rise

an

d

Web

Sp

her

e 4.

1 E

nte

rpri

se E

dit

ion

Web

Sp

her

e,

Ver

sion

s 5.

0, 5.

0.1,

and

5.

0.2

Bas

e E

dit

ion

an

d

En

terp

rise

E

dit

ion

Web

Sp

her

e V

ersi

ons

5.1

and

5.1.

1 B

ase

Ed

itio

n

Web

Sp

her

e V

ersi

ons

5.1

Bu

sin

ess

Inte

grat

ion

S

erve

r

Web

Log

ic 7.

0 S

ervi

ce P

ack

1

Win

dow

s 20

03 Se

rver

E

nter

pris

e E

dit

ion

and

St

and

ard

Ed

itio

n Ye

s Ye

s Ye

s

Win

dow

s X

P Pr

ofes

sion

al w

ith

Serv

ice

Pack

1

Yes

z/O

S V

ersi

on 1,

R

elea

se 42

z/O

S V

ersi

on 1

Rel

ease

53

Not

es:

1.

Supp

ort

for

this

pl

atfo

rm is

on

W

ebSp

here

, Ver

sion

5.

1.1

Bas

e E

dit

ion

only

.

2.

Supp

ort

for

z/O

S, V

ersi

on 1

Rel

ease

4

is fo

r W

ebSp

here

fo

r z/

OS

5020

4 an

d hi

gher

se

rvic

e le

vels

on

ly.

3.

Supp

ort

for

z/O

S, V

ersi

on 1

Rel

ease

5

is fo

r W

ebSp

here

fo

r z/

OS

5100

03 an

d hi

gher

se

rvic

e le

vels

on

ly.

4.

For

Web

se

rvic

es su

ppor

t, th

e fo

llow

ing

vers

ions

of

W

ebSp

here

A

pplic

atio

n Se

rver

5.

0.2

and

ab

ove

are

requ

ired

:

v z/

OS:

W

ebSp

here

A

pplic

atio

n Se

rver

50

2014

an

d hi

gher

se

rvic

e le

vels

; Web

Sphe

re A

pplic

atio

n Se

rver

51

0200

an

d hi

gher

se

rvic

e le

vels

v O

S/40

0: W

ebSp

here

A

pplic

atio

n Se

rver

5.

1.1

Bas

e E

dit

ion

wit

h PT

F SI

1550

2 an

d hi

gher

se

rvic

e le

vels

v O

ther

(d

istr

ibut

ed)

plat

form

s:

– W

ebSp

here

A

pplic

atio

n Se

rver

5.

0.2.

7 B

ase

Ed

itio

n an

d hi

gher

se

rvic

e le

vels

w

ith

patc

h PQ

8949

2_50

27_F

ix.ja

r (l

ater

ve

rsio

ns of

W

ebSp

here

A

pplic

atio

n Se

rver

5.

0.2.

x re

quir

e PQ

8949

2_50

2x_F

ix.ja

r)

– W

ebSp

here

A

pplic

atio

n Se

rver

5.

1.0.

5 B

ase

Ed

itio

n an

d hi

gher

se

rvic

e le

vels

w

ith

patc

h PQ

8949

2_51

05_F

ix.ja

r. (l

ater

ve

rsio

ns of

W

ebSp

here

A

pplic

atio

n Se

rver

5.

1.0.

y re

quir

e PQ

8949

2_51

0y_F

ix.ja

r)

– W

ebSp

here

A

pplic

atio

n Se

rver

5.

1.1.

0 B

ase

Ed

itio

n w

ith

patc

h PQ

9149

4

– W

ebSp

here

A

pplic

atio

n Se

rver

5.

1.1.

1 B

ase

Ed

itio

n an

d hi

gher

se

rvic

e le

vels


Tabl

e 5.

S

uppo

rted

op

erat

ing

syst

ems

for

Syn

thet

ic Tr

ansa

ctio

n R

ecor

der

(ST

I) an

d G

ener

ic W

indo

ws

Op

erat

ing

Sys

tem

S

TI

Gen

eric

W

ind

ows

Win

dow

s 20

00 A

dva

nced

Se

rver

w

ith

Serv

ice

Pack

4

Yes

Yes

Win

dow

s 20

00 Pr

ofes

sion

al w

ith

Serv

ice

Pack

4

Yes

Yes

Win

dow

s 20

00 Se

rver

w

ith

Serv

ice

Pack

4

Yes

Yes

Win

dow

s 20

03 Se

rver

E

nter

pris

e E

dit

ion

and

St

and

ard

E

dit

ion

Yes

Win

dow

s X

P Pr

ofes

sion

al w

ith

Serv

ice

Pack

1

Yes

Yes


Tabl

e 6.

S

uppo

rted

op

erat

ing

syst

ems

for

Qua

lity

of S

ervi

ce (Q

oS)

Op

erat

ing

Sys

tem

Q

oS

AIX

V

ersi

on 5.

1 w

ith

mai

nten

ance

le

vel

Yes

AIX

V

ersi

on 5.

2 w

ith

mai

nten

ance

le

vel

Yes

Red

H

at E

nter

pris

e L

inux

V

ersi

on 2.

1 on

a

2.4

kern

el on

xS

erie

s Ye

s

Red

H

at E

nter

pris

e L

inux

, Ver

sion

3.

0 A

dva

nced

Se

rver

, Ent

erpr

ise

Serv

er an

d W

orks

tati

on on

xS

erie

s an

d zS

erie

s Ye

s

Sun

Sola

ris

8 Ye

s

Sun

Sola

ris

9 Ye

s

SuSE

SL

ES

Ver

sion

7

on a

2.4

kern

el on

xS

erie

s an

d zS

erie

s Ye

s

SuSE

SL

ES

Ver

sion

8.

0 on

a

2.4

kern

el or

U

nite

dL

inux

1.

0 w

ith

Serv

ice

Pack

2a

on

a

2.4

kern

el on

xS

erie

s an

d zS

erie

s Ye

s

Win

dow

s 20

00 A

dva

nced

Se

rver

w

ith

Serv

ice

Pack

4

Yes

Win

dow

s 20

00 Se

rver

w

ith

Serv

ice

Pack

4

Yes

Win

dow

s 20

03 Se

rver

E

nter

pris

e E

dit

ion

and

St

and

ard

E

dit

ion

Yes


Management server prerequisites

Space and memory requirements

Table 7. Space and memory requirements

Requirement Value

Recommended memory1 2 GB

Temporary space 400 MB2

Typical installation: Disk space 1.9 GB

Custom installation: Disk space for an

installation of the management server only

760 MB

Custom installation: Disk space required for

an installation of IBM WebSphere

Application Server

540 MB

Custom installation: Disk space required for

an installation of IBM DB2

600 MB

Notes:

1. The minimum memory is 1 GB.

2. On AIX and Solaris, the temporary space required if installing IBM DB2 is 1460 MB and

1440 MB, respectively.

Prerequisite software

For installations where you are using a previously-installed database, you must

have one of the following databases:

v IBM DB2 Universal Database™ Enterprise Edition, Version 7.2 with Fix Pack 7 or

higher

v IBM DB2 Universal Database Enterprise Extended Edition , Version 7.2 with Fix

Pack 7 or higher

v IBM DB2 Universal Database Enterprise Server Edition, Version 8.1 with Fix

Pack 3 or higher

v Oracle Database 8i Standard Edition, Release 3 (Version 8.1.7)

v Oracle Database 9i Standard Edition Release 2 (Version 9.2)

For installations where you are using a previously-installed WebSphere Application

Server, you must have one of the following application servers:

v WebSphere Application Server, Base Edition, Version 5.0.2

v WebSphere Application Server Base Edition, Version 5.1 (Recommended over

5.0.2)

Management agent and Store and Forward agent prerequisites

Space and memory requirements

Table 8. Space and memory requirements

Requirement Value

Recommended memory1 512 MB

Temporary space 120 MB


Table 8. Space and memory requirements (continued)

Requirement Value

Disk space 90 MB2

Additional space required for the Generic

Windows Component

350 MB

Additional space for the Quality of Service

component

33 MB

Additional space required for the J2EE

component

15 MB

Additional space required for the STI

component

85 MB

Notes:

1. The minimum memory is 256 MB.

2. For Store and Forward agents, if you do not already have WebSphere Caching Proxy

Version 5.1 installed, you must have 200 MB of additional disk space.

Prerequisite software

The following software is required:

v On z/OS computers, UNIX System Services (USS)

v For OS/400 computers, see “Installing and configuring a management agent in

OS/400” on page 60 for full prerequisites.

Supported browsers

To access the user interface for IBM Tivoli Monitoring for Transaction Performance,

you must use Internet Explorer 6.0, with Service Pack 1 or higher from one of the

following operating systems:

v Windows 2000 Professional with Service Pack 4

v Windows 2000 Server with Service Pack 4

v Windows 2000 Advanced Server with Service Pack 4

v Windows 2003 Server Enterprise Edition

v Windows 2003 Server Standard Edition

v Windows XP Professional with Service Pack 1

The applet for IBM Tivoli Monitoring for Transaction Performance, Version 5.3

supports Java™ JVM 1.3.1 plug-in versions starting at 1.3.1_08 or later.

Java Virtual Memory (JVM) heap size requirements

Your management server computer must have enough physical RAM to

accommodate the following JVM heap size guidelines:

Number of management agents JVM heap size setting

1–500 512 MB

501–1000 1024 MB

1001–2000 2048 MB

This setting is changed in the WebSphere Application Server console.


Communications Ports

The following tables list the default communication ports used between the IBM

Tivoli Monitoring for Transaction Performance management server, management

agent, and Store and Forward agent.

Table 9. Communications ports — SSL enabled

Components Port numbers

Management agent to Store and Forward agent 443

Store and Forward agent to management server 9446

Management server to management agent

Note: The management server talks directly to the management

agent , not through Store and Forward agent.

1976

Table 10. Communications ports — SSL not enabled

Components Port numbers

Management agent to Store and Forward agent 80

Store and Forward agent to management server 9081

Management server to management agent

Note: The management server talks directly to the management

agent , not through Store and Forward agent.

1976



Chapter 3. Preparing an existing database for configuration

with the management server

You can use an existing DB2 or Oracle database in your environment. If you

choose to use an existing database, you must prepare the database before you

begin installing IBM Tivoli Monitoring for Transaction Performance.

For an existing DB2 database, see “Preparing an existing DB2 database” on page

17.

For an existing Oracle database, see “Guidelines for preparing an Oracle database”

on page 21.

Preparing an existing DB2 database

Objective

To prepare an existing DB2 database for use by the management server.


This section describes configuration tasks and requirements for setting up a DB2

database to work with a management server. For detailed information on DB2

architecture, commands, and procedures, consult the DB2 documentation.





Before you begin

Note: The database for the management server must use encoding UTF8 in order

to handle non-ASCII values (such as Chinese characters).

You must have a valid user name and password to give you access to the required

database for the management server.

When you finish

None

Procedure

Create the database by doing the following:

Create the database to be used for the management server under a DB2 Instance

associated with that client. To create the database, log on as an authorized user of

the DB2 Instance or log on as the user under which the DB2 client was installed.

The user under which the DB2 client was installed has access to all DB2 Instances

associated with the client.

1. Install the DB2 client on the computer to be used for the management server.

17

2. Use the following command to create the database:

Note: (Double-byte character environments only): You must enable your database

to store monitoring information that comes in double-byte character

strings. The following command for creating a database enables storage

of double-byte character sets:

- db2: create database database_name USING CODESET UTF-8 TERRITORY US

db2 create database database_name

where database_name is the name of the database.

Example: If db2Admin is the user name under which the DB2 database client

was installed on the management server, you can log on as db2Admin and create

a database named itmtpDB to support the management repository.

db2 create database itmtpDB

Create the database user on the operating system of the DB2 server computer.

Create a database user directly on the server or from within the DB2 client. database

user refers to the system user account the management server uses to access the

DB2 database that supports the management repository.

Example: If the DB2 server is installed on a Windows computer, enter the

following command at a DOS prompt on that computer to create a database user

account that the management server can use to access the management repository.

This example creates a user named itmtp53 with password itmtp53. (The password

is the second itmtp53 entry.)

net user itmtp53 itmtp53 /add

Create and implement a buffer pool by doing the following:

1. To implement a buffer pool, you must disconnect all applications connected to

the database.

2. Connect to the database on which you are changing the buffer pool size.

3. Create a buffer pool as large as possible without using operating system

paging.

Note: The default buffer pool and page size for DB2 are smaller than required

for optimal performance by applications using the management

repository. Use a buffer pool size of at least 250.

Example: to create a buffer pool of size 250, with pagesize of 32K, enter the

following command in DB2:

create bufferpool buffpool32k size 250 pagesize 32k

4. Update the database configuration for database_name using the APPLHEAPSZ 513

command.

update database configuration for database_name using APPLHEAPSZ 513

5. Enter the following command to view the new buffer pool:

select * from syscat.bufferpools

6. List all applications connected to the database using the following command:

db2 list applications

A list of applications similar to the following displays:


Auth ID Appl. Appl. Application ID DB #of

Name Handle Name Agents

-------- ---- ------ --------------------------- ---- ------

DB2INST1 java 14 *LOCAL.db2instl.000918161203 CSWA 1


7. Close all connections to the database and repeat the following command for

each application connected:

db2 force application (applicationhandle)

where applicationhandle is the application handle number listed in the Appl.

Handle column of the list of applications (see Step 6 on page 18).

8. Reconnect to the database:

v If you are logged on as a user authorized to the DB2 Instance under which

the database was created, enter the following command:

db2 "connect to databasename"

where databasename is the name of the database to be used for the

management server.

v If you are not logged on as a user authorized to the DB2 Instance under

which the database was created, enter the following command:

db2 "connect to databasename user InstUser using InstUserPasswd"

where databasename is the name of the database to be used for the

management server and InstUser and InstUserPasswd are the userID and

password of a user authorized to the DB2 Instance under which the database

was created.

Information similar to the following displays:

$db2 connect to cswa

Database Connection Information

Database server = DB2/NT 8.1.0

SQL authorization ID = DB2INST1

Local database alias = CSWA

1. Grant permissions to the database user (the user account that the management

server uses to access the database) by using the following commands:

Note: The database user must have authority to create and edit tables.db2 "grant dbadm on database to user user"

db2 "grant use of tablespace tablespace to user user"

where user is the user ID of the database user and tablespace is the name of the

tablespace to be created for the management server.

Additional Information: These commands grant DBADM authority to the database

and to the tablespace. To issue these commands, you must be logged on as a

user authorized to the DB2 Instance under which the database was created.

Example: If you created a database user named itmtp53 for the management

server to use and a tablespace named userspace1, use the following commands

to grant authority to the database and to the tablespace.

db2 "grant dbadm on database to user itmtp53"

db2 "grant use of tablespace userspace1 to user itmtp53"

(Optional) You can use the following process to verify that the DB2 database

configuration is optimized:

Chapter 3. Preparing an existing database for configuration with the management server 19

Note: This sample procedure optimizes database configuration for use with

IBM Tivoli Monitoring for Transaction Performance applications by

increasing the number of log primaries and turning on the log retain

function.

a. List the database configuration information by entering:

db2 "get db cfg for databasename"

b. Increase the number of log primaries by entering:

db2 "update db cfg for databasename using logprimary number"

c. Turn on the log retain function by entering:

db2 "update db cfg for databasename using logretain on"

d. List all applications connected to the database by entering:

db2 list applications

A list of applications similar to the following is displayed:

Auth ID Appl. Appl. Application ID DB #of

Name Handle Name Agents

-------- ---- ------ --------------------------- ---- ------



e. Close all connections to the database. Repeat the following command for

each application:

db2 force application (applicationhandle)

where applicationhandle is the application handle number listed in the Appl.

Handle column of the list of applications (see Step 1d).

f. Make an offline backup and apply db logs to roll forward. Enter the

following:

db2 "backup db databasename to backupdirectory"

g. Repeat Step 1d.Set up a DB2 client connection by doing the following:

Follow these guidelines when installing and configuring the DB2 Client

Application Enabler:

Note: If the DB2 RDBMS is installed on a separate computer from the client

(the management server), you must install the DB2 Client Application

Enabler on the client computer and set up connectivity to the database.

v Ensure that there is no DB2 Client Application Enabler installation (either

complete or partial) on the system. If an installation already exists, uninstall

it.

v Customize the options to select Java database connectivity (JDBC). A JDBC

driver is installed as part of the DB2 Client Application Enabler installation.

v Ensure that approximately 2 MB are available in the selected home directory

to accommodate the DB2 Client Application Enabler.

v (UNIX only) Source the db2profile file (for the Korn or Bourne shell) or the

db2cshrc file (for the C shell) to be able to run DB2 commands and utilities

such as catalog and connect.

The db2profile and db2cshrc files are located in the home directory of the

DB2 instance owner, under the sqllib subdirectory. Source the appropriate

file in the .profile or .cshrc file of each account that needs to use the DB2

environment and tools.


v (AIX only) To verify the setup of the RDBMS and of the DB2 client, ensure

that the following environment variables are set correctly. (If you have

sourced the db2profile or db2cshrc file, these variables are correct.)

– DB2DIR must point to the directory where the DB2 Client Application

Enabler is installed.

– DB2INSTANCE must be set to the database instance name. This is set during

installation of the database.

After the DB2 Client Application Enabler is installed, you must set up

connectivity both to the RDBMS server and to the database. DB2 commands for

setting up connectivity are issued from the client system. You must run these

commands even when DB2 is running on the same computer that hosts the

management server.

v The following example command connects the client with an RDBMS server

named ghost, which has the node name or alias ims_db2 and uses port 50000:

db2 "catalog tcpip node ims_db2 remote ghost server 50000"

v The following example command connects the client to a database named

timsdev with the alias ims_dev, located on the server whose node name or

alias is ims_db2:

db2 "catalog database timsdev as ims_dev at node ims_db2"

Provide extra shared memory segments for DB2 connections on AIX by doing

the following:

Note: By default, 32-bit applications cannot attach more than 11 shared

memory segments per process, of which a maximum of 10 can be used

for local DB2 connections. Use the EXTSHM (extended shared memory)

functionality to ensure that an adequate number of shared memory

segments are available for DB2 connections. The EXTSHM functionality

is available for DB, Version 7.2 (which is the result of installation of DB2

UDB, Version 7.1 Fix Pack 3) or for later versions of DB2. If you do not

provide an adequate number of shared memory segments, you might see

the following error message:

SQL1224N A database agent could not be started to service a request,

or was terminated as a result of a database system shutdown or a force

command. SQLSTATE=55032

Enable EXTSHM as follows:

v In DB2 client sessions: export EXTSHM=ON

v When starting the DB2 UDB Server:

export EXTSHM=ON

db2set DB2ENVLIST=EXTSHM

db2start

v On DB2 UDB EEE:

EXTSHM=ON

export EXTSHM

You also add these lines to the sqllib/db2profile file.

Guidelines for preparing an Oracle database

Objective

To prepare an existing Oracle database for use by the management server.



This section describes configuration tasks and requirements for setting up an

existing Oracle database that can be used to support the management server. The

Oracle configuration tasks described in this chapter are meant to serve as a general

guide to the basic requirements for setting up the database, not as comprehensive

instructions. A database administrator might use a different approach. For detailed

Oracle information, consult the Oracle documentation.





You must also have a valid user name and password to give you access to the

required database for the management server.

Before you begin

Note: The database for the management server must use encoding UTF8 in order

to handle non-ASCII values (such as Chinese characters) as described in the

procedure.

When you finish

None

Procedure

1. Create sufficient table space for the management repository.

Additional Information: One month of operational data might require a minimum

of 10 GB. Your space requirements might vary, depending on your environment

and monitoring configuration. For test purposes, a smaller database (300 MB to

400 MB) is sufficient.

2. Create a user ID and password for the table space for which the user has

authority to create and edit tables.

3. Configure a rollback segment using the Oracle default size for rollback

segments.

4. Review the sample configuration scripts in “Sample scripts for configuring

existing databases” on page 23 as a guide for creating your own script to

configure your database.

5. (Double-byte character environments only) If your operating system is enabled for

a single-byte character set, it does not automatically accept double-byte

character sets. You must enable your database to store monitoring information

that comes in double-byte character strings. The following sample command for

creation of a database includes the CHARACTER SET UTF8 string (in bold text).

This string enables storage of double-byte character sets:

CREATE DATABASE v920u

MAXINSTANCES 1

MAXLOGHISTORY 1

MAXLOGFILES 5

MAXLOGMEMBERS 3

MAXDATAFILES 100

DATAFILE ’C:\Oracle\oradata\v920u\system01.dbf’ SIZE 200M REUSE AUTOEXTEND ON

NEXT 10240K MAXSIZE UNLIMITED

EXTENT MANAGEMENT LOCAL

DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE ’C:\Oracle\oradata\v920u\temp01.dbf’


SIZE 10M REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED

UNDO TABLESPACE "UNDOTBS1" DATAFILE ’C:\Oracle\oradata\v920u\undotbs01.dbf’ SIZE

50M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED

CHARACTER SET UTF8

NATIONAL CHARACTER SET AL16UTF16

LOGFILE GROUP 1 (’C:\Oracle\oradata\v920u\redo01.log’) SIZE 102400K,

GROUP 2 (’C:\Oracle\oradata\v920u\redo02.log’) SIZE 102400K,

GROUP 3 (’C:\Oracle\oradata\v920u\redo03.log’) SIZE 102400K;

Sample scripts for configuring existing databases

You can use the following sample scripts to configure a database repository for the

management server in a test environment. Do not use these scripts in a production

environment. The following scripts are available:

v “Sample SQL script for creating fixed table space in Oracle”

v “Sample SQL script for creating flexible tablespace in Oracle” on page 24

Sample SQL script for creating fixed table space in Oracle: The following

sample script creates a tablespace of fixed size. It does the following:

v Creates tablespaces called tims_main_ts and tims_temp_ts.

v Assumes that the Oracle installation directory is /data/home/oracle/dbs.

v Creates a tablespace user named tims, with the password tims.

v Uses path names in UNIX format. If your Oracle installation is on a Windows

computer, use path names in Windows format. That is, use backslash characters

(\) instead of forward slash (/) characters.create tablespace tims_main_ts

datafile ’/data/home/oracle/dbs/tims_main.dbf’ size 1500M

default storage (

initial 4M

next 4M

minextents 2

maxextents unlimited

pctincrease 0)

offline;

commit;

create tablespace tims_temp_ts

temporary datafile ’/data/home/oracle/dbs/tims_temp.dbf’ size 100M

default storage (

initial 1M

next 1M

minextents 2

maxextents unlimited

pctincrease 0)

offline;

commit;

alter tablespace tims_main_ts online;

commit;

alter tablespace tims_temp_ts online;

commit;

create profile tims_profile limit

sessions_per_user 50

cpu_per_session unlimited

cpu_per_call 6000

logical_reads_per_session unlimited

logical_reads_per_call 100

idle_time 30

connect_time 480;

commit;


create user tims

identified by tims

default tablespace tims_main_ts

temporary tablespace tims_temp_ts

quota unlimited on tims_main_ts

profile tims_profile;

commit;

GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TO

tims identified by tims;

commit;

Sample SQL script for creating flexible tablespace in Oracle: Instead of setting

permanently fixed sizes for the tablespace and temporary data file, the following

sample script uses AUTOEXTEND to enlarge these items as needed. It autoextends the

tablespace (named $username) 5 MB at a time, and the temporary data file 100 KB

at a time.

#!/bin/ksh

if [ $# -ne 1 ]

then

echo "Usage: create_users.sh username"

exit 1

fi

username=$1

echo "Creating SQL file: /dbs1/create/"$username"_create.sql"

cat << E_O_F > /dbs1/create/"$username"_create.sql

REM

REM Execute the following SQL fragment as Oracle RDBMS user "sys":

REM

create tablespace ts_$username

datafile ’/dbs1/ts_$username.dbf’ size 30M

default storage (

initial 100K

next 50K

minextents 2

maxextents 120)

offline;

commit;

create tablespace tmp_ts_$username

datafile ’/dbs1/tmp_ts_$username.dbf’ size 3M

default storage (

initial 100K

next 50K

minextents 2

maxextents 20)

TEMPORARY

offline;

commit;

alter tablespace ts_$username online;

commit;

alter tablespace tmp_ts_$username online;

commit;


create profile profile_$username limit

sessions_per_user 10

cpu_per_session unlimited

cpu_per_call 6000

logical_reads_per_session unlimited

logical_reads_per_call 100

idle_time 30

connect_time 480;

commit;

create user $username

identified by $username

default tablespace ts_$username

temporary tablespace tmp_ts_$username

quota unlimited on ts_$username

profile profile_$username;

commit;

GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TO

$username identified by $username;

commit;

ALTER DATABASE DATAFILE ’/dbs1/ts_$username.dbf’ AUTOEXTEND ON NEXT 5M;

commit;

ALTER DATABASE DATAFILE ’/dbs1/tmp_ts_$username.dbf’ AUTOEXTEND ON NEXT 100K;

commit;

E_O_F



Chapter 4. Installing a management server

The management server is shared by all IBM Tivoli Monitoring for Transaction

Performance components and serves as the control center of your IBM Tivoli

Monitoring for Transaction Performance installation. The management server

collects information from, and provides services to, the management agents in your

environment. Management server components are Java Management Extensions

(JMX) MBeans.

The installation program discovers the license key downloaded with the

installation images. This license key limits the number of management agents

supported by this management server to 500. If you have purchased a license key

that enables the support of additional management agents you can enter it during

the installation process. For more information contact your IBM sales

representative.

The typical installation process installs IBM Tivoli Monitoring for Transaction

Performance (management server and management agent), IBM DB2 Version 8.1,

WebSphere Application Server Version 5.1, and, optionally, the Store and Forward

agent.

The custom installation enables you to use an existing version of a database, either

IBM DB2 or Oracle, and an existing version of WebSphere Application Server. The

installation software looks for existing databases and versions of WebSphere

Application Server. If they exist on the computer on which you are performing this

installation, follow the custom installation procedures.

Typical installation: management server

Objective

To install the IBM Tivoli Monitoring for Transaction Performance management

server.


The management server is a J2EE application that is configured within WebSphere.

Note: If you receive an error message during installation, use the message

identifier, such as BWMIS0103E, to find additional information in the IBM

Tivoli Monitoring for Transaction Performance Problem Determination Guide.


In UNIX environments, the user who installs the product must have root

privileges. In Windows environments, the user who installs the product must have

membership in the Administrators group.

Notes:

1. The following requirements apply to the user that you define for WebSphere

Application Server:

v Windows: must have membership in the Administrators group.

v UNIX: must have root privileges.

27

(Windows-only) The user that runs the management server needs the privileges

″Act as part of the Operating System″ and ″Logon as Service.″ To verify these

permissions, go to Control Panel → Administrative Tools → Local Security

Policies.

2. The following requirements apply to the admin, fence (UNIX-only), and

instance users that you define for DB2:

v Window: create a new user.

v UNIX: create a new user or use a preexisting user. You must define a group

name and home directory for new accounts.

The accounts you create have full administrative rights to the DB2 database.

Before you begin

Perform the following actions before you begin the installation:

1. Verify that your computer meets the system and software prerequisites. See

“Management server prerequisites” on page 13.

2. (Optionally) Enable Java 2 security. See, Appendix E, “Enabling Java 2 security

with IBM Tivoli Monitoring for Transaction Performance,” on page 135.

3. Obtain the installation software as described in “Using installation files from

the Web” on page 2 or “Using installation files from a CD-ROMs” on page 3.

4. HP-UX and Solaris: Change all recommended kernel configuration parameters

set as formulas to integer values. You must reboot your system for these

changes to take affect.

5. Close all other applications.

When you finish

v Install the latest patches for DB2 and WebSphere Application Server.

v (Optionally) Install the Store and Forward agent. See, Chapter 5, “Installing a

Store and Forward agent,” on page 45.

v Install a IBM Tivoli Monitoring for Transaction Performance management agent.

See, Chapter 6, “Installing a management agent,” on page 51.

Notes:

1. These instructions are written as if you have downloaded the installation files

from the IBM Web site. If you are installing IBM Tivoli Monitoring for

Transaction Performance from CD-ROMs, you will see additional panels

prompting you to insert the required CD-ROMs as needed.

2. If you receive a warning that there is not enough temp space to perform the

installation, cancel and restart the installation to restart the temp space monitor.

Note:

Procedure

1. Log on to the computer that will be the management server.

2. Access the installation files downloaded in the “Using installation files from

the Web” on page 2.

3. Launch the executable file for your operating system from the directory that

contains your installation images,

installation_image_directory/ITMTP_WTP_1/disk1:

v Windows: setup_MS_w32.exe

v AIX: setup_MS_aix.bin

v Solaris: setup_MS_sol.bin

v Linux xSeries: setup_MS_lin.bin


v Linux zSeries: setup_MS_lin390.bin

v Linux pSeries: setup_MS_linppc.bin

v HP-UX: setup_MS_hp11.bin

4. Click Next in the Welcome window to display the CD-ROM installation

selection window.

Note: If the installation program detects that your computer does not match

the installation prerequisites a failure window displays instead of the

Welcome window. Refer to the information on the window to correct

the situation and restart the installation.

5. Clear the Perform Embedded Installation Using CD-ROMs check box and

click Next to display the Software License Agreement window.

Notes:

a. If you are installing from CD-ROM, do not clear this check box so that the

management server installation image can be copied to a temporary

directory on your hard disk clearing the CD-ROM drive for the rest of the

required installation disks. These management server installation images

require at least 1 G of space.

b. On UNIX: You must use the -W tempBrowsePanel.active=true flag if the

following conditions apply:

v You are performing the installation from the CD-ROMs.

v You are performing an interactive installation.

v You are not installing the versions of WebSphere Application Server and

DB2 that are delivered with IBM Tivoli Monitoring for Transaction

Performance.

Figure 1. Embedded installation information window

Chapter 4. Installing a management server 29

c. On AIX: If you are installing IBM WebSphere Application Server, Version

5.1 from the IBM Tivoli Monitoring for Transaction Performance, Version

5.3 CD-ROMs, you must use the default temporary directory. 6. Select the radio button to accept the terms of the license agreement and click

Next.

7. Click Next to accept the default installation directory path and display the

secure communication panel.

Additional Information: You can change this path by typing or browsing to a

different directory. If you specify a directory that does not exist, the

installation program creates the directory.

8. Provide the following information:

License Key

The installation program discovers the license key downloaded with

the installation images. If you have purchased a license key that

enables the support of additional management agents, enter that key.Enable one of the following SSL options:

Note: See Chapter 9, “Creating and deploying SSL key files,” on page 73 for

information on modifying the default SSL configuration.

Option A: Disable Secure Sockets Layer (SSL):

Note: When SSL is disabled, password encryption is also disabled for

communications between the management agents and the management

server.

Figure 2. SSL Enablement for Management Server Communication window


Enable SSL

Clear this check box (selected by default) to disable secure sockets

layer (SSL).

Port for non-SSL agents

Accept the default port number (9081). This is the port by which a

management agent communicates with the management server in a

non-secure environment.

Port for the management server Console

Accept the default port number (9082). This port is used to access the

IBM Tivoli Monitoring for Transaction Performance user interface in a


Note: If the default port number is busy, try an alternate port number. You

can specify any valid TCP/IP port numbers from 1 to 65535.

Option B: Enable Secure Sockets Layer (SSL) to protect HTTP

communications between management server and agents by providing the

following information:

Enable SSL

Ensure this check box is selected.

Key File Name

Type the directory path to the ms.jks file. Sample jks files are

delivered with the installation images:

installation_image_directory/ITMTP_WTP_1/disk1/keyfiles

Key File Password

Type changeit, which is the default password.

Trust File Name




Trust File Password


Copy SSL Files Locally

Copies the SSL files to a local directory. This enables you to access the

files even if you lose your network connection or remove the

installation CD-ROM.

Note: Clear this check box if you are using custom SSL.


Accept the default setting of 9081. This is the port by which a



Port for SSL agents

Accept the default setting of 9446. You use this port number again

during the Store and Forward Service installation. This is the port by

which an agent communicates with the management server in a

secure environment.

Port for the management server console

Accept the default setting of 9445. This port is used to access the IBM

Tivoli Monitoring for Transaction Performance user interface in a

secure environment.


9. Click Next to display the configuration window for the WebSphere

Application Server.

10. Perform the following steps to create a new user account for WebSphere that

has membership in the Administrators group.

User Type a user name for a valid user account on the host computer. This

user must have membership in the Administrators group. Create a

user for IBM Tivoli Monitoring for Transaction Performance. There are

no case or character restrictions for this user name.

(Windows-only) The user that runs the management server needs the

privileges ″Act as part of the Operating System″ and ″Logon as

Service.″ To verify these permissions, go to Control Panel →

Administrative Tools → Local Security Policies.

Password

Type the user password that corresponds to the user name in User.

Cell Name, Server Name, Node Name

These fields are read only.

Admin Console Port

Accept the default port setting of 9090, unless the port is in use. If the

default port is in use, try an alternate port number such as 9091 or

9092. You can specify any valid TCP/IP port numbers from 1 to 65535.

Note: AIX 5.1 and 5.2 use port 9090 for WebSM by default. Change

this port number if you are running on an AIX 5.1 or 5.2 system

with WebSM. Alternatively, an AIX administrator can disable

WebSM using the following command in the /usr/websm/bin

directory of the WebSM installation:

wsmserver -disable

If you install the management server on a computer on which the

Health Console for IBM Tivoli Monitoring is installed, the default

ports for WebSphere are probably in use. The Health Console runs on

the IBM WebSphere Application Server, Version 4.0. The Version 4.0

server uses the same default ports as Version 5.x. When you install the

WebSphere server for the management server (Version 5.x), be sure to

use an available port other than the default. Otherwise, the two

versions of WebSphere can have a port conflict.11. Select Install DB2 and click Next to display the database options window.

12. Provide user account information for DB2:

Note: The following requirements apply to the admin, fence (UNIX-only), and


v Windows: create a new user.

v UNIX: create a new user or use a preexisting user. You must define a

group name and home directory when you create a new user.

User Name

Type the user name for the DB2 Admin user account. The installation

creates the user account. This account has full DB2 privileges.

Password

Type the password to correspond with the DB2 Admin user account.

This string can have one to eight characters, without spaces. The

string must not begin with a number or an ampersand. The only valid

symbols are: @, #, $, &.


Group Name

(UNIX only) Type the group name.

Home Directory

(UNIX only) Type the home directory for the user type admin.13. (UNIX-only) Click Next and provide the fence user account information for

DB2:

User Name

Type the user name for the DB2 fence user account. The installation

creates the user account, if it does not already exist. This account has

privileges to administer the database.

Password

Type the password to correspond with the DB2 fence user account.

Group Name


Home Directory

(UNIX only) Type the home directory for the fence user.14. Click Next and provide the instance user account information for DB2:

Instance Name

Type the name of the DB2 Instance.

User Name

Type the user name for the DB2 Instance user account. The installation

creates the user account, if it does not already exist. This account has

privileges to administer the database.

Password

Type the password to correspond with the DB2 Instance user account.

Group Name


Home Directory

(UNIX only) Type the home directory for the instance.15. Click Next to display the installation image location information for

WebSphere Application Server and DB2.

16. Click Next to accept the installation image locations or click Browse to

indicate a different location.

17. Click Next to display the product installation directories.

18. Click Next to display the management server information confirmation

window.

19. Click Next to begin installation.

20. (Windows-only) Select whether to restart the WebSphere Application Server

now or do it manually at a later time.

Note: If you restart the WebSphere Application Server now you do not need

to do steps 22 and 23 of this procedure.

21. When the installation program completes, click Finish.

22. (UNIX-only) If you use DB2 for IBM Tivoli Monitoring for Transaction

Performance, you must activate (or source) the DB2 environment:

a. Access a command-line interface window.

b. Run the following command to activate the DB2 environment.


Note: The initial period followed by a space is required.. db2 instance user homedir root/sqllib/db2profile

Note: Do not dismiss this instance of the command-line interface window.

You must perform the next step in this window so that WebSphere

communicates correctly with the DB2 environment.23. Restart the WebSphere Application Server to activate the management server:

v UNIX:

cd WAS_BASEDIR/Appserver/bin

./stopServer.sh server1 -username WAS_username -password WAS_password

./startServer.sh server1

v Windows:

cd MS_BASEDIR\WAS51\bin

stopServer.bat server1 -username WAS_username -password WAS_password

startServer.bat server1

where:

WAS_BASEDIR

Specifies the directory where the WebSphere Application Server is

installed.

MS_BASEDIR

Specifies the directory where the IBM Tivoli Monitoring for

Transaction Performance management server is installed.

WAS_username

Specifies the name of a user account for the server.

WAS_password

Specifies the password for the user account.

Note: (Windows only) If you installed DB2 and the WebSphere Application

Server that come with IBM Tivoli Monitoring for Transaction

Performance, the software is automatically placed in the directory

structure of the management server software.

Windows: MS_BASEDIR\WAS51

MS_BASEDIR\DB2

UNIX: opt/WebSphere/Appserver

opt/WebSphere/DB2

24. Launch IBM Tivoli Monitoring for Transaction Performance from the icon on

the machine on which you installed your management server or by entering

the URI on your browser:

Secure installation

https://management_server_name:9445/tmtpUI

Non-secure installation

http://management_server_name:9082/tmtpUI

Custom installation: management server

Objective


server using full configuration options.



The custom installation enables you to install the product using an existing

database application (DB2 or Oracle) and an existing IBM WebSphere Application

Server.

Notes:

1. IBM Tivoli Monitoring for Transaction Performance does not run with a version

of IBM WebSphere Application Server, Version 5.1 that is managed by Network

Deployment. You must install the version of IBM WebSphere Application Server

that is included with the installation software or an existing, standalone version

of IBM WebSphere Application Server.

2. If you use an existing WebSphere Application Server installation, WebSphere

Application Server must be installed on the management server computer.

3. If you use an existing DB2 installation, DB2 can exist on the management

server or a remote computer. If DB2 is installed on a remote computer, you

must also install the DB2 client on the management server. Complete the

procedure to prepare your DB2 database as described in “Preparing an existing

DB2 database” on page 17.

The management server is a J2EE application that is configured within WebSphere.





Notes:

1. The following requirements apply to the user that you define for WebSphere

Application Server:

v Windows: must have membership in the Administrators group.

The user that runs the management server needs the privileges ″Act as part

of the Operating System″ and ″Logon as Service.″ To verify these

permissions, go to Control Panel → Administrative Tools → Local Security

Policies.

v UNIX: must have root privileges.2. The following requirements apply to the admin, fence, and instance users that

you define for DB2:

v Windows: create a new user.

v UNIX: create a new user or use a preexisting user. You must define a group

name and home directory for new accounts.

The accounts you create have full administrative rights to the DB2 database.

Before you begin


1. Verify that your computer meets the system and software prerequisites. See

“Management server prerequisites” on page 13.

2. (Optionally) Enable Java 2 security. See, Appendix E, “Enabling Java 2 security


3. Obtain the installation software as described in “Using installation files from

the Web” on page 2 or “Using installation files from a CD-ROMs” on page 3.

4. To configure the management server to use an existing database, see Chapter 3,

“Preparing an existing database for configuration with the management

server,” on page 17.


5. HP-UX and Solaris: change all recommended kernel configuration parameters

set as formulas to integer values. You must reboot your system for these

changes to take affect.


When you finish

v Install the latest patches if you installed the embedded versions of DB2 and

WebSphere Application.

v (Optionally) Install the Store and Forward agent. See, Chapter 5, “Installing a


v Install a IBM Tivoli Monitoring for Transaction Performance management agent.

See, Chapter 6, “Installing a management agent,” on page 51.

Procedure

Note: These instructions are written as if you have downloaded the installation

files from the IBM Web site. If you are installing IBM Tivoli Monitoring for



1. Log on to the computer that will be the management server.

2. Access the installation files downloaded in the “Using installation files from

the Web” on page 2.

3. (Pre–existing DB2 installation on UNIX only) If you are using an existing

installation of IBM DB2, you must source in the DB2 environment before you

run the installation program.


b. Run the following command to activate the DB2 environment.

Note: The initial period followed by a space is required.. db2 instance user homedir root/sqllib/db2profile


You must perform the next step in this window so that WebSphere

communicates correctly with the DB2 environment. 4. Launch the executable file for your operating system from the directory that


installation_image_directory/ITMTP_WTP_1/disk1:









selection window.






6. Clear the Perform Embedded Installation Using CD-ROMS check box and


Notes:

a. If you are installing from CD-ROM, do not clear this check box so that the

management server installation image can be copied to a temporary

directory on your hard disk clearing the CD-ROM drive for the rest of the

required installation disks. These management server installation images

require at least 1 G of space.

b. On UNIX: You must use the -W tempBrowsePanel.active=true flag if the

following conditions apply:

v You are performing the installation from the CD-ROMs.

v You are performing an interactive installation.

v You are not installing the versions of WebSphere Application Server and

DB2 that are delivered with IBM Tivoli Monitoring for Transaction

Performance.c. On AIX: If you are installing IBM WebSphere Application Server, Version

5.1 from the IBM Tivoli Monitoring for Transaction Performance, Version

5.3 CD-ROMs, you must use the default temporary directory. 7. Select the radio button to accept the terms of the license agreement and click

Next.

8. Click Next to accept the default installation directory path in the Directory

Name field.





9. Provide the following information:

License Key

The installation program discovers the license key downloaded with

the installation images. If you have purchased a license key that

enables the support of additional management agents, enter that key.Enable one of the following SSL options:






server.

Enable SSL


layer (SSL).









Figure 3. SSL Enablement for Management Server Communication window




—OR—




Enable SSL


Key File Name




Key File Password


Trust File Name




Trust File Password











Port for SSL agents




secure environment.




secure environment.10. Click Next to display the configuration window for the WebSphere

Application Server.

11. Enter the following information to specify your IBM WebSphere Application

Server configuration:

User Type a user name.

Note: The user must have the following privileges, depending on

your system configuration:

v Existing installation of WebSphere Application Server running

with Global Security enabled: WAS Administrator Role.


v Existing installation of WebSphere Application Server running

without Global Security enabled: membership in the

Administrators group on Windows or root privileges on

UNIX.

v New WebSphere Application Server installation: membership

in the Administrators group on Windows or root privileges

on UNIX.

(Windows only) The user that runs the management server

needs the privileges ″Act as part of the Operating System″

and ″Logon as Service.″ To verify these permissions, go to

Control Panel → Administrative Tools → Local Security

Policies.

Password

Type a user password.

Cell Name

(Existing WebSphere only) Type the name of the group (cell) for the

application server that you want to monitor.

Note: Windows: entries in this field are case sensitive.

This group can span multiple computers. The application server

belongs to a specific node, which you name in the Node Name field.

The node belongs to a specific cell, which you name in the Cell Name

field. Typically, a cell contains multiple nodes. Consult the WebSphere

Administrative Console to identify the existing cells and their nodes.

Server Name

(Existing WebSphere only) Type the name of the WebSphere Application

Server where IBM Tivoli Monitoring for Transaction Performance runs.


Node Name

(Existing WebSphere only) Type the name of the subgroup (cell) of

application server that you want to monitor.


This subgroup exists on a single computer. Normally, the default node

name is the short host name. For example, on a computer named

topshelf the node name could be topshelf.

SOAP Connector Port

(Existing WebSphere only) Accept the default SOAP port setting (8880).

This connector port is used by the WebSphere Application Server to

send commands using the Simple Object Access Protocol (SOAP). You

obtain this information in the following file:

WAS_base_dir/config/cells/cell/nodes/node/serverindex.xml

where WAS_base_dir is the installation directory for WebSphere, cell

and node are the cell and node names for the WebSphere Application

Server that hosts the management server.

Admin Console Port

(New installation of WebSphere only) Accept the default port setting

(9090).


Note: On AIX, Version 5.x, port 9090 is reserved for WebSM. If this

port is busy, try using port 9091, 9092, and so on until you

locate a free port. Alternatively, an AIX administrator can

disable WebSM using the following command in the

/usr/websm/bin directory of the WebSM installation:

wsmserver -disable

Select the check box if WAS Security currently is enabled

(Existing WebSphere only) Select the check box if Global Security is

enabled on the WebSphere Application Server. You must provide the

following values:

Client Key File Name

The full path name for the Client Key File Name, as in this

example for the Windows platform:

C:\WebSphere\AppServer\etc\DummyClientKeyFile.jks

Client Key File Password

Type the client key file password. The default is WebAS

Client Trust File Name

The full path name (WebAS is the default password) for the

Client Trust File Name, as in this example for the Windows

platform:

C:\WebSphere\AppServer\etc\DummyClientTrustFile.jks

Client Trust File Password

Type the client trust file password. The default is WebAS

12. Click Next to display the database options window.

13. Choose one of the following database options:

v Option A: Use an existing DB2 database

v Install DB2 (This database is valid for use only with IBM Tivoli Monitoring

for Transaction Performance. You do not see this option if the installation

program discovers an existing installation of DB2 on the target computer.)

v Use an existing Oracle database

14. Complete the database user account information as follows:

Existing DB2 database:

Database Name

Type the name of the existing DB2 database that you want to use.

Database User ID

Type the name of an existing user of the DB2 instance.

Database Password

Type the password of an existing user of the DB2 instance.

JDBC Path

Verify the full path to the required Java DataBase Connectivity (JDBC)

files or browse to the directory in which the files reside.

For example, these files might be located in the following paths:

v Windows example: C:\Program Files\IBM\SQLLIB\java

v AIX example: /usr/db2inst1/sqllib/java

Note: If you are using Version 7.2 of IBM DB2, the JDBC files are

located in the installation path in a java12 directory, not the

java directory.


Option B: New DB2 database:

Note: The following requirements apply to the admin, fence (UNIX-only), and


v Windows: the installation program automatically creates the new

user. You cannot use a preexisting user.

v UNIX: create a new user or use a preexisting user. You must define a

group name and home directory when you create a new user.

User Name

Type a user name.

Password

Type a user password.

Group Name


Home Directory

(UNIX only) Type the home directory for the user type (admin, fence,

or instance).Option C: Existing Oracle database:

Database Host Name

Type the fully qualified host name .

Do not include a protocol in the host name. For example, use

myserver.ibm.tivoli.com, not https://myserver.ibm.tivoli.com.

Port Number

Provide a port number. Do not accept the default port assignment

(1521) if you have assigned other applications to use that port number.

SID Type the Oracle system identifier number for the database.

Database User ID

Type the name of an existing user of the Oracle database.

Database Password

Type the password of an existing user of the Oracle database.15. Click Next to display the installation image location information for

WebSphere Application Server and DB2 if you are installing this software.




18. Click Next to display the management server information confirmation

window.


20. (Windows-only) Select whether to restart the WebSphere Application Server

now or do it manually at a later time.

Note: If you restart the WebSphere Application Server now you do not need

to do Steps 22 and 23.

21. When the installation program completes, click Finish to exit.

22. (UNIX only) If you use DB2 (instead of Oracle) for IBM Tivoli Monitoring for

Transaction Performance, you must source the DB2 environment as follows:



b. Run the following command to activate the DB2 environment. The initial

period followed by a space in the command is an essential part of the

command:

. db2 instance user homedir root/sqllib/db2profile


You must run Step 23 in this window so that WebSphere

communicates correctly with the DB2 environment.23. Restart the WebSphere Application Server to activate the management server:

v UNIX:

cd WAS_BASEDIR/Appserver/bin

./stopServer.sh server1 -username WAS_username -password WAS_password

./startServer.sh server1

v Windows using the embedded installation of WebSphere Application Server:

cd MS_BASEDIR\WAS51\bin

stopServer.bat server1 -username WAS_username -password WAS_password

startServer.bat server1

where:

WAS_BASEDIR

Specifies the directory where the WebSphere Application Server is

installed.

MS_BASEDIR

Specifies the directory where the IBM Tivoli Monitoring for

Transaction Performance management server is installed.

WAS_username

Specifies the name of a user account for the server.

WAS_password

Specifies the password for the user account.

Note: If you installed the WebSphere Application Server that comes with IBM

Tivoli Monitoring for Transaction Performance, that software is

automatically placed in the directory structure of the management

server software.

Windows: MS_BASEDIR\WAS51

UNIX: opt/WebSphere/Appserver




Secure installation






Chapter 5. Installing a Store and Forward agent

The Store and Forward Service is software on a dedicated management agent that

acts as a proxy to channel IBM Tivoli Monitoring for Transaction Performance

monitoring data across firewalls. The Store and Forward agent has the following

characteristics:

v The Store and Forward Service is required for management agents that are

separated from the management server by a firewall.

v It performs no communication or processing of management agent data. It only

relays data.

The installation program installs the required version of the Java Virtual Machine

(JVM).

Installing a Store and Forward agent

Objective

To install a IBM Tivoli Monitoring for Transaction Performance Store and Forward

agent to enable secure communication between computers across a firewall.

Security settings enable you to restrict communication between computers.


The installation programs for the Store and Forward agent performs these tasks:

v Install the Store and Forward agent software on a computer outside of the

firewall, including the following unique items:

– The WebSphere Caching Proxy, which is one of the Edge components for

WebSphere Application Server, Version 5.1.

If one of the WebSphere Application Server Edge components already exists

on the server, you must define a virtual host name for the Store and Forward

Service, as described in this procedure.

Note: Before you begin this procedure you must work with an enterprise

system administrator to register the server that hosts the Store and

Forward Service as follows:

- List the server in the Domain Name System (DNS). This server

should have a fixed IP address.

- Enable communications from the server to traverse firewalls with

bidirectional communication using port 1976.v Installs management agent software on computers in the following locations:

– In the enterprise.

– Outside of the firewall.

A management agent that is located outside of the firewall connects to the

management server through the management agent that hosts the Store and

Forward Service.

45


In UNIX environments, the user who installs the product must have root

privileges. In Windows environments, the user who installs the product must have

membership in the Administrators group.

Before you begin


1. Verify that your computer meets the system and software prerequisites.

2. Complete the installation of the IBM Tivoli Monitoring for Transaction

Performance management server.


4. Work with an enterprise system administrator to register the server that hosts

the Store and Forward Service as follows:

v List the server in the Domain Name System (DNS).

v Enable communications from the server to traverse firewalls using port 1976.

When you finish

Install a management agent to communicate through this Store and Forward agent.

Procedure





1. Log on to the computer on which you want to install the Store and Forward

management agent.

Additional Information: This is a separate computer from the server and acts as

the gateway for communication between the management server and the

management agents.



installation_image_directory/ITMTP_WTP_3/SnF:

v Windows: setup_SnF_w32.exe

v AIX: setup_SnF_aix.bin

v Solaris: setup_SnF_sol.bin

v Linux xSeries: setup_SnF_lin.bin

v Linux pSeries: setup_SnF_linppc.bin

v Linux 390: setup_SnF_lin390.bin

v HP-UX: setup_SnF_hp11.bin


selection window.








5. Select the radio button to accept the terms of the license agreement and click

Next.


configure server and agent communication window.




7. Provide the following information to configure server and agent

communication configuration:

SnF Host Name (fully qualified)

Verify the fully qualified host name or IP address of the computer that

hosts the Store and Forward Service. Do not include a protocol in the

host name. For example, use myserver.ibm.tivoli.com, not

https://myserver.ibm.tivoli.com

Enable SSL

Select the check box for SSL authentication on the management server.

Notes:

a. If the WebSphere Caching Proxy (WCP) that hosts the Store and

Forward Service already exists on the system, you must change its

configuration. Find the ibmproxy.conf file in the installation

directory of the WCP. Open the file in a text editor and set the

SSLTunneling flag to off.

Figure 4. Communication with the Management Server or with the Store and Forward Agent window

Chapter 5. Installing a Store and Forward agent 47

b. See Chapter 9, “Creating and deploying SSL key files,” on page 73

for information on modifying the default SSL configuration.

SSL Key Store File

Enter the directory path to the dmzagent.jks key file location or

browse to the appropriate directory. Sample jks files are delivered with

the installation images:

installation_image_directory/ITMTP_WTP_3/SnF/keyfiles

SSL Key Store Password

Enter the default password, changeit.

Use default port number?

Accept the Yes default.

Copy Key Store Locally

Note: Do not copy these files locally if you are using custom SSL files

as recommended.Select this check box to copy the SSL files to a local directory. This

enables you to access the files even if you lose your network

connection or remove the installation CD-ROM.

Port Number

Accept the default port number. This number must match the port

number for the WebSphere Caching Proxy.

Incoming Request Port

Accept the default port number of 1976. This is the bidirectional

communication port used by the management server to traverse

firewalls and communicate with this agent. 8. Click Next and provide the following information to configure the proxy host

and mask:

URL to Management Server

Enter a URL to specify the computer that hosts the Store and Forward

Service (proxy server) in the following format: https://hostname:port

number where:

hostname

Specifies the name of the management server.

port number

Specifies the port number of the management server. Use the

same port as the Port for SSL agents in the management

server installation.

Mask Specify IP addresses for all computers that have permission to access

the management server through the Store and Forward Service.

Separate IP addresses with a comma. For example, @(9.48.*,10.*)

You can use regular expressions in a mask, as in these examples:

v This mask allows one specific IP address: @(9.48.101.99)

v This mask allows all IP addresses from the 9.48. domain:

@(9.48.*)

v This mask allows all IP addresses: @(*)


User Name

Specify a User account that exists on the WebSphere Application

Server of the management server. This user account must have the

agent role.

User Password

Specify the password associated with the specified user name. 9. Click Next to display the Key File window.

10. Complete the following fields in the WebSphere Caching Proxy window:

Pathname for .kdb file

Type the directory path to the key.kdb file or browse to the

appropriate directory. Sample kdb files are delivered with the

installation images:


Pathname for password stashed file

Type the directory path to the key.sth password file or browse to the

appropriate directory. Sample sth files are delivered with the

installation images:


Copy KDB files to local config directory

Accept the default.11. (Windows only) Click Next to display the user account window.

Figure 5. Key File window

Chapter 5. Installing a Store and Forward agent 49

Use an existing Windows user, or click the Create a new, dedicated user

account radio button and fill in the following fields:

User Choose one of the following options to specify the user account

through which the management agent runs :

v Use the default user name, TMTPAgent.

v Type a unique user name.

Password, and Verify Password

Type a unique user password.12. Click Next to install WebSphere Caching Proxy, Version 5.1 from the default

location and display the installation image location information.

Additional information: Use Browse to install from a different directory. You

will not see this window if you have already installed WebSphere Caching

Proxy, Version 5.1 on this computer.




15. Click Next to display an installation confirmation window.


17. (Windows only) Click OK to restart the computer.

Additional information: You will not see this window if you have already

installed WebSphere Caching Proxy, Version 5.1 on this computer.

18. Click Finish to complete the installation of Store and Forward agent.


Chapter 6. Installing a management agent

Management agents are installed on computers across your environment. Based on

Java Management Extensions (JMX), the management agent software provides the

following functionality:

v Listening and playback behaviors – A management agent can have any or all of

the listening and playback components installed.

v ARM engine for data collection – A management agent uses the ARM API to

collect performance data.

v Policy management – When a discovery, listening, or playback policy is created,

an agent group is assigned to run the policy.

v Thresholding – Management agents are capable of conducting a range of

sophisticated thresholding operations.

v Event support – Management agents send component events to the management

server.

v Communication with the management server – Management agents

communicate with the management server using Web services and the secure

socket layer (SSL).

Installing a management agent

Objective

To install a IBM Tivoli Monitoring for Transaction Performance management agent.


While it is possible for the management server and management agent to both

operate on a single computer, this configuration is not supported for production

use.





Before you begin


v Verify that your computer meets the system and software prerequisites. See

“Management agent and Store and Forward agent prerequisites” on page 13.

v Complete the installation of the IBM Tivoli Monitoring for Transaction

Performance management server. See, Chapter 4, “Installing a management

server,” on page 27.

v Optionally, complete the installation of the IBM Tivoli Monitoring for

Transaction Performance Store and Forward agent. See, Chapter 5, “Installing a


v Close all other applications.

When you finish

v Verify the installation of the management agent, as described in “Verifying the

installation of a management agent” on page 63.

51

v Generate your own jks key files and trust files. This product provides default

Secure Socket Layer (SSL) certificates so you can set up a secure environment

without customization. These .jks files are meant for test purposes only and

expire shortly after deployment. These file are not recommended for use in a

production environment. See Chapter 9, “Creating and deploying SSL key files,”

on page 73 for more information on setting up SSL.

Procedure





1. Log on to the computer on which you want to install the management agent.



installation_image_directory/ITMTP_WTP_3/MA:

v Windows: setup_MA_w32.exe

v AIX: setup_MA_aix.bin

v Solaris: setup_MA_sol.bin

v Linux xSeries: setup_MA_lin.bin

v Linux zSeries: setup_MA_390.bin

v Linux pSeries: setup_MA_linppc.bin

v HP-UX: setup_MA_hp11.bin

3. Click Next in the Welcome window to display the Software License

Agreement window.






Next.


communication configuration window.




6. Complete the following fields to establish agent and server communication

and click Next:

Host Name (fully qualified)

Type the fully qualified host name or IP address of the computer to

which this agent directs communication. If the agent is within the

enterprise and there is no firewall between the agent and the server,

type the management server computer information. If a firewall exists

between the agent and the server, type the Store and Forward Service

information. Do not include a protocol in the host name. For example,

type myserver.ibm.tivoli.com, not https://myserver.ibm.tivoli.com.

User Name

Type the user ID of a user who is authorized to log on to the

management server. This user must have the agent role on the IBM

WebSphere Application Server.


User Password

Type the password that corresponds to the user specified in the User

Name field.

Enable SSL

Ensure that this check box is selected for a secure installation or

cleared for a nonsecure installation.

SSL Key Store File

Type the directory path to the .jks file or browse to the appropriate

location. Sample jks files are delivered with the installation images:

installation_image_directory/ITMTP_WTP_3/MA/keyfiles.









Accept the Yes default if you used the default port number when you

installed the management server.

Port Number


number for the management server or Store and Forward Service to

which you are connecting.

No Proxy, Socks, HTTP

v Accept the default if you do not use a proxy server to represent the

management server.

v Select Socks if you use a Socket (Socks) server as a proxy server to

represent the management server.

v Select HTTPS if you use an HTTPS (secure Web) server as a proxy

server to represent the management server.

Proxy Host

Note: This fields is read only if you do not use a proxy server to

represent the management server.The fully qualified name of the proxy host.

Port Number


represent the management server.The port number of the proxy host.


Accept the default port number of 1976. This is the port that is used

by the management server to communicate with this management

agent. Port number 1976 must be available to use any of the IBM

Tivoli Monitoring for Transaction Performance component functions,

such as Synthetic Transaction Investigator or J2EE.

Chapter 6. Installing a management agent 53

7. (Windows only) Use an existing Windows user or click the Create a new,

dedicated user account radio button and fill in the following fields:






Type a unique password. 8. Click Next to display the management agent information window.


10. Click Finish to complete the installation of the management agent software.

Setting up management agents for z/OS

Objective

To set up management agents to work in a z/OS environment.


After completing the SMP/e installation, you must configure each management

agent. This section provides the following configuration information for z/OS

management agents:

v Setting up a z/OS management agent

v Installing IBM Tivoli Monitoring for Transaction Performance for z/OS software

in SYSPLEX

v Starting or stopping a management agent


Several roles are involved in installing and configuring IBM Tivoli Monitoring for

Transaction Performance for z/OS. Each role can be the responsibility of a different

person. The following list describes the typical user roles and their tasks:

Network administrator

v Enables communication between systems, such as opening ports.

v Understands firewall implications.

Tivoli administrator

v Installs and configures the management system.

v Provides the SSL key database file to the USS administrator.

v Installs and configures the Tivoli Enterprise Console® server, if not

already completed.

v Enables Tivoli Enterprise Console by installing the base BAROC files.

z/OS system programmer

v Performs SMP/e installation of IBM Tivoli Monitoring for Transaction

Performance on z/OS. SMP/e installation is usually completed under

UID=0 (in MVS™ terms). The same user who performs the SMP/e

installation can perform the configuration and operation. To perform the

configuration and operation, the user must be TMTPAGNT, under

group, TMTPGRP. TMTPAGNT does not need to be the same user who

performed the SMP/E installation.

z/OS security (RACF®) administrator

v Defines users and groups.


v Sets up the system to allow the management agent to be started as a

task.

z/OS USS administrator

v Defines and sets up file systems (such as run time directory as its own

file system, and Tivoli common directory as its own file system).

v Sets up SSL for the management agent.

Before you begin

v Complete the SMP/e installation. See the Program Directory for IBM Tivoli

Monitoring for Transaction Performance Management Agent for instructions on

installing SMP/e.

v Verify that your computer meets the system and software prerequisites.

When you finish

Verify your installation, as described in “Verifying the installation of a management

agent” on page 63.

Procedure

Setting up a z/OS management agent: After completing the SMP/e installation,

perform the following steps on each management agent in the LPAR environment:

Additional Information: This section assumes IBM Tivoli Monitoring for Transaction

Performance for z/OS was installed using the installation steps as defined in the

Program Directory and no installation defaults were changed (such as z/OS UNIX

System Services directories).

1. Access the F2 relfile.

2. Copy the BWMSTRT and BWMSTOP JCL jobs to the system PROCLIB

concatenation, such as SYS1.PROCLIB.

Additional Information: The BWM jobs are provided as sample jobs in the F2

relfile. SYS1.PROCLIB is a PDS dataset. A PROCLIB is a procedure library.

3. Run the following Resource Access Control Facility (RACF®) commands on a

Time Sharing Option (TSO):

a. Create a new user and group by running the following commands:

ADDGROUP TMTPGRP OMVS(GID(TMTP_GID)) SUP(SYS1)

ADDUSER TMTPAGNT DFLTGRP(TMTPGRP) PASSWORD(TMTPAGNT_PASSWORD)

+ OMVS(UID(TMTPAGNT_UID) HOME(’/var/tmtp’) PROGRAM(’/bin/sh’)

+ ASSIZEMAX(2147483647) CPUTIMEMAX(2147483647) THREADSMAX(1000))

SETROPTS GENERIC(STARTED)

where:

TMTP_GID

Specifies any integer selected by the administrator to represent the

group ID on the system.

TMTPAGNT_PASSWORD

Specifies any password selected by the administrator.

TMTPAGNT_UID

Specifies any integer selected by the administrator to represent the

user ID.b. Add start and stop jobs to the STARTED class by running the following

commands:


RDEFINE STARTED BWMSTRT.* STDATA(USER(TMTPAGNT) GROUP(TMTPGRP))

RDEFINE STARTED BWMSTOP.* STDATA(USER(TMTPAGNT) GROUP(TMTPGRP))

SETROPTS CLASSACT(STARTED) RACLIST(STARTED)

SETROPTS RACLIST(STARTED) REFRESH

SETROPTS GRPLIST

c. Add TMTPAGNT user to the WebSphere® Application Server default group

by running the following command:

CONNECT TMTPAGNT GROUP(WAS_GRP) GRPACC

where:

WAS_GRP

Specifies the WebSphere Application Server default group name

(typically WSCFG1). This is the group associated with the

WebSphere files in the Hierarchical File System (HFS).d. Add WebSphere Application Server user to the TMTPAGNT default group

by running the following command:

CONNECT ASSR1 GROUP(TMTPGRP) GRPACC

e. (Optional) Perform the following steps if you run J2EE with WebSphere

security enabled:

1) Create a RACF key ring containing a certificate authority signed

certificate for the TMTPAGNT user by running the following command:

RACDCERT ADDRING(WASKeyring) ID(TMTPAGNT)

2) Generate a digital certificate by running the following command:

where:

COMMON_NAME

Specifies the common name, such as John Smith or

WTSC57.ITSO.IBM.COM. The (Secure Sockets Layer) SSL

convention uses the domain name as the common name.

ORGANIZATION

Specifies the organization name, such as IBM.

LOCAL_CERTIFICATE_AUTHORITY

Specifies the Certificate Authority certificate, which must be the

WebSphere Certificate Authority. You must have the Certificate

Authority of the WebSphere server on the client key ring to

validate the WebSphere Application Server certificate. You can

use different certificate authorities to sign the certificates, but

you must connect all certificate authorities to all key rings. Each

server or client key ring must contain the certificate authority of

each peer (everyone it communicates with over SSL) as well as

its own. A client certificate is not required for communication

with WebSphere Application Server.

If the LOCAL_CERTIFICATE_AUTHORITY that signed the

TMTPAGNT personal certificate is not the same as the

WebSphere certificate, you must connect your

LOCAL_CERTIFICATE_AUTHORITY to the WebSphere server

key ring and restart the server.3) Give the TMTPAGNT user ID the authority to read the key ring and

certificates from the IRR.DIGTCERT profiles by running the following

commands:

RACDCERT ID (TMTPAGNT) GENCERT SUBJECTSDN(CN(’COMMON_NAME’) 0(’ORGANIZATION’)) +

WITHLABEL(’TMTPCert’) SIGNWITH(CERTAUTH LABEL(’LOCAL_CERTIFICATE_AUTHORITY’))


PERMIT IRR.DIGTCERT.LIST CLASS(FACILITY) ID(TMTPAGNT) ACC(READ)

PERMIT IRR.DIGTCERT.LISTRING CLASS(FACILITY) ID(TMTPAGNT) ACC(READ)

SETROPTS RACLSIT(FACILITY) REFRESH

4) Connect the certificate to the key ring by running the following

command:

where:


Specifies the Certificate Authority certificate, which must be the

WebSphere Certificate Authority. You must have the Certificate

Authority of the WebSphere server on the client key ring to

validate the WebSphere Application Server certificate. You can

use different certificate authorities to sign the certificates, but

you must connect all certificate authorities to all key rings. Each

server or client key ring must contain the certificate authority of

each peer (everyone it communicates with over SSL) as well as

its own. A client certificate is not required for communication

with WebSphere Application Server.

If the LOCAL_CERTIFICATE_AUTHORITY that signed the

TMTPAGNT personal certificate is not the same as the

WebSphere certificate, you must connect your

LOCAL_CERTIFICATE_AUTHORITY to the WebSphere server

key ring and restart the server.5) Connect the certificate to the server key ring by running the following

command:

RACDCERT CONNECT (CERTAUTH LABEL(LOCAL_CERTIFICATE_AUTHORITY)

RING(keyringname))

where:


Specifies the Certificate authority label.

keyringname

Specifies the name of the key ring.4. Log in to UNIX System Services (USS) as a user with, UID=0.

5. On UNIX System Services, run the following commands:

mkdir /var/tmtp

chown TMTPAGNT:TMTPGRP /var/tmtp

mkdir /etc/tmtp

chown TMTPAGNT:TMTPGRP /etc/tmtp

Additional Information: The above commands create the UNIX System Services

directories, /var/tmtp and /etc/tmtp, with the user and group,

TMTPAGNT:TMTPGRP.

6. Log off of UNIX System Services.

7. Log in to UNIX System Services as TMTPAGNT, and change to the /tmp

directory.

8. Configure the management agent by performing the following steps:

a. Copy the /usr/lpp/tmtp/V5R3M0/MA/config1/prepConfig.sh and

setupEnv.sh files to the /tmp directory.

RACDCERT ID(TMTPAGNT) CONNECT (CERTAUTH LABEL(’LOCAL_CERTIFICATE_AUTHORITY’)

RING(WASKeyring))


b. Ensure that the /var/tmtp and /etc/tmtp directories have minimum

permissions of 750.

Additional Information: All directories are created with 755 permissions,

except for /var/tmtp/MA/app which has 775 permissions.

c. Verify that the setupEnv.sh command script points to the correct JAVA_DIR

and TMTP_DIR directories.

d. Run the prepConfig.sh command script.

e. Change directories to /etc/tmtp/MA/config.

f. Open the zos.properties file and customize the following values so that the

configMa.sh command script can register the management agent to the

management server:

Property file setting Description

zos.msHostName=mshost mshost is the fully qualified host name for the

management server.

zos.msUserName=user user is the name of the user that exists in the

management server.

zos.msUserPassword=password password is the password for the user name specified

above.

zos.sslEnabled=false Set this to ″true″ if the management server is secure.

zos.msProtocol=http Set this to ″https″ if the management server is secure.

zos.msPort=9081 Set this to the secure port if the management server is

secure. The default is 9446.

zos.proxyProtocol=noproxy Specify the proxy protocol as one of the following

options: noproxy, https, or socks. The default is

noproxy.

zos.proxyHostName= If there is a proxy, specify the host name of the proxy.

zos.proxyPortNumber= If there is a proxy, specify the port number used by the

proxy.

#zos.epKeyStore=keyStore If the management server is secure, uncomment this

setting and set the keyStore value to the location of the

JKS certificate file. The default key is located in the

/etc/tmtp/MA/config/agent.jks.

#zos.epKeyPass=keyPass If the management server is secure, uncomment this

setting and set the keyPass value to the password of the

JKS certificate. The default password for the agent.jks

file is changeit.

#zos.maHostName=maHostname Uncomment this setting and type the fully qualified

local host name of the management agent for

maHostname. If not commented out, this setting is

determined automatically.

g. Run the configMa.sh command script with the argument ″install″ such as >>

./configMa.sh install.

h. (Optional) Start the management agent as described in “Starting and

stopping a management agent” on page 59.

i. (Optional) Change the zos.properties file permissions to protect the password.

j. Enable synchronization between the WebSphere Application Server Network

Deployment Manager, node agent, and the WebSphere Application Server by

performing the following steps:

1) Disable Global Security.


2) Restart the WebSphere Application Server Network Deployment

Manager, the node agent, and the WebSphere Application Server.

3) Set the WebSphere Application Server configuration parameter,

GlobalSecurity → CustomProperties → EnableTrustedApplications to

true.

4) Re-enable WebSphere Application Server Global Security.

5) Restart the WebSphere Application Server Network Deployment

Manager, node agent, and WebSphere Application Server.

Installing IBM Tivoli Monitoring for Transaction Performance for

z/OS software in a SYSPLEX environment

When installing IBM Tivoli Monitoring for Transaction Performance software in a

SYSPLEX environment on the z/OS operating system, perform the following steps:

1. On one LPAR in the SYSPLEX environment, create the zone and complete the

SMP/e installation.

2. On each LPAR in the SYSPLEX environment, perform the following steps:

a. Run the RACF configuration steps as described in Step 3 on page 55.

b. Configure system environment settings (including semaphores).

c. Configure each management agent individually as described in Step 8 on

page 57.

Starting and stopping a management agent

After you configure each management agent, you can start or stop the

management agent using one of the following options:

v As a script from UNIX System Services:

– Start the management agent by running the

/etc/tmtp/MA/config/start_tmtpd.sh command script while logged in to

UNIX System Services as TMTPAGNT.

—OR—

– Stop the management agent by running the

/etc/tmtp/MA/config/stop_tmtpd.sh command script while logged in to

UNIX System Services as TMTPAGNT.v As a task from Multiple Virtual Storage (MVS):

– Start the management agent with the BWMSTRT job.

—OR—

– Stop the management agent with the BWMSTOP job.

Additional Information: When canceling MVS processes, qualify the

TMTPAGNT processes with an ASID. The tapmagent and management agent

Java processes listed in the SDSF console do not have separate job names. To

cancel MVS processes without using BWMSTOP, qualify the cancel command

with individual ASIDs by running the following command from the MVS

console:

"C TMTPAGNT,A=hexasidnumber"

where hexasidnumber is the ASID for one of the two processes.

You can verify that the management agent is active by checking the IBM Tivoli

Monitoring for Transaction Performance UI System Administration → Work with

Agents view.


Installing and configuring a management agent in OS/400

Objective

To set up a management agent in OS/400 to monitor transaction performance

using secure communication between computers.


This installation process sets up a management agent. Review the following system

requirements before beginning the installation. The following table outlines the

requirements for a secure typical installation . Software prerequisites:

Note: Always use the latest cumulative PTF levels.

Table 11. OS/400 installation prerequisites

Product Product ID - PTF/PTE

OS/400 V5R2 or V5R3 5722SS1 Option *BASE

QShell 5722SS1 Option 30

TCP/IP Connectivity Utilities 5722TC1 Option *BASE

IBM Developer Kit for Java (*BASE) 5722JV1 Option *BASE

Java Developer Kit 1.3 (Option 5) 5722JV1 Option 5

IBM Toolbox for Java 5722JC1 Option *BASE

PTF/PTE Cumulative Package (for V5R2

or V5R3)

5722999 Current® cumulative package

QShell PTF/PTE (V5R3) SI12897

–OR–(V5R2) SI12625

Crypto Access Provider 128-bit for

AS/400®

5722AC3 *BASE


The user who installs the product must have at least *SYSADMIN privileges.

Before you begin

v Verify that your computer meets the system and software prerequisites.

v Close all other applications.

When you finish

Verify your installation, as described in “Verifying the installation of a management

agent” on page 63.

Procedure

1. Access the installation images, either by inserting a CD-ROM into the OS/400

target computer, or downloading them from the Web site. See, “Using

installation files from the Web” on page 2.

Note: If you are installing from the CD-ROM skip to Step 7.

2. Map a drive to the OS/400 target computer on which you are installing the

management agent. (Note: you must use the install ID that exists on the

computer):

\\system_name\root

3. Create a directory to hold the installation images on the OS/400 system.


4. Drag the installation images

\installation_images_directory\ITMTP53_WTP_3\MA into the directory you

created on the OS/400 computer.

5. Sign on to the OS/400 system that is to be installed.

6. Invoke QShell on the command line qsh.

7. Change directory to the installation folder that was created in the above steps.

8. Run the installation script: install-OS400.sh.

9. Select option 1 to continue.

10. Select option 1 to accept the license agreement.

11. Enter the Management Server hostname.

12. Enter the Management Server user ID, for example Administrator.

13. Enter the Management Server password.

14. Select option 1 if the management server is secure.

15. Enter the keystore file path: install_folder/keyfiles/agent.jks.

16. Enter the keystore password changeit.

17. Select option 1.

Configuring your management agent to start at OS/400 IPL

During installation your system configuration is not changed to start the IBM

Tivoli Monitoring for Transaction Performance management agent at IPL. For

instructions on how to make those changes, refer to the OS/400 documentation

and add the following to the new startup program:

QSYS/QSH CMD(’/QIBM/USERDATA/TIVOLI/TMTP/MA/BIN/START_TMTPD.SH’)

MONMSG MSGID(CPF0000)

To access the OS/400 documentation do the following:

1. Go to http://publib.boulder.ibm.com/pubs/html/as400/infocenter.html.

2. Select a region. For example, North America.

3. Select a language and OS/400 VRM. For example, English – V5R2.

4. Follow the appropriate path for the version you are using:

V5R2: Systems management → Basic system operations → iSeries basic operations

→ Start and stop the iSeries → Start the system → Change the IPL startup

program

V5R3: Systems management → Basic system operations → Start and stop the

iSeries → Start the system → Change the IPL startup program



Chapter 7. Verifying your installation

This chapter describes how to verify the installation of management agents.

Performing this procedure enables you to see management agent details including

the name, description, status, platform, IP address, current version, upload interval,

start time, and management policies for components that you have deployed.

Verifying the installation of a management agent

Objective

To verify successful installation of a management agent.


You can verify a successful installation in the View Details window.


You must have the authorization necessary to log in to the management server.

Before you begin

None

When you finish

None

Procedure




Secure installation




2. Click Work with Agents in the System Administration section of the left

navigation frame. The Work with Management Agents window is displayed.

When the installation and registration process for the management agents is

complete, all of the management agents registered to this management server

should be displayed in the table on the Work with Management Agents window

with a status of Online.

63


Chapter 8. Installing the Synthetic Transaction Recorders and

Generic Windows

Note: The Synthetic Transaction Investigator recorder and Generic Windows are

available only on Windows.

This chapter describes how to install the Synthetic Transaction software. Use this

software to record transactions that represent typical user experiences on your Web

site. Play back these recorded transactions at scheduled intervals to test system

performance. For more information on working with Synthetic Transaction

Recorders and Generic Windows refer to the IBM Tivoli Monitoring for Transaction

Performance Administrator’s Guide.

The following types of Synthetic Transaction components are available:

v Synthetic Transaction Investigator (STI) that consists of two subcomponents:

The recorder: A standalone application that records a sequence of steps that

make up a Web transaction. The recording is stored in XML as a set of HTTP

requests. A management agent plays the recorded transaction to evaluate

performance and availability under varying conditions.

The player: A component in IBM Tivoli Monitoring for Transaction Performance

that runs prerecorded Web transactions from the STI Recorder. You deploy the

player to one or more management agents. The management agents use the

player to run synthetic transactions at intervals that you set, so that you can

evaluate performance and availability under varying conditions. You install the

STI Recorder separately.

v Generic Windows player/recorder:

Player/recorder: An application from the IBM Rational software suite that

records a sequence of steps in a Windows application or environment, including

transactions in Internet Explorer. The recording is actually a set of SQA Basic

commands. You run a recorded transaction on a management agent to evaluate

performance and availability under varying conditions. The playback engine that

is included with this application enables a management agent to run a Generic

Windows recording.

You can also use a Rational® VU script to perform high-scale transaction

simulations that check multiple servers in a short time period.

The available recorders for IBM Tivoli Monitoring for Transaction Performance are

STI Recorder and Generic Windows recorder. You can install a recorder on any

computer with the following characteristics:

v The computer runs one of the supported versions of Windows.

v The computer can connect to the Web resources needed for the synthetic

transaction.

v The computer is accessible to the management server for the uploading of

completed recordings.

The target computer for recording does not have to be a management server or a

management agent. The management server deploys the recordings to the

management agents specified. For this reason, the management server must be

accessible to the management agent

65

The target management agent on which you play transaction recordings must have

player software. For Generic Windows, this management agent always has both the

player and recorder on it because the two tools exist in a single software

application called Rational Robot. You can run the synthetic transaction on any

management agent that runs a supported version of Windows. See the Chapter 8,

“Installing the Synthetic Transaction Recorders and Generic Windows,” on page 65

for more information on installation options.

Table 12 summarizes the goals for the installation of the Synthetic Transaction

software.

Table 12. Goals for the installation of Synthetic Transaction software

Goals Refer to

1. Install recording software.

v STI Recorder

v Generic Windows player/recorder (Rational Robot)

“Installing the recording software for

Synthetic Transaction Investigator” on

page 67

“Installing Generic Windows recording

and playback” on page 71

2. Install playback software.

v STI component

v Generic Windows, which consists of two parts:

– Rational Robot

– Generic Windows components

“Installing Generic Windows recording

and playback” on page 71

3. Deploy software that enables playback of transactions on a

management agent.

v For STI, this deployment enables STI communications in IBM Tivoli

Monitoring for Transaction Performance.

The playback software runs STI transactions. The playback

component responds to the Playback policy you configure in the

last step of this process.

v For Generic Windows, deployment of the playback software is the

same as the installation of the recorder because both components

exist in a single application.

For STI, this procedure is described in

the IBM Tivoli Monitoring for Transaction


For Generic Windows, this procedure is

described in “Installing Generic

Windows recording and playback” on

page 71.

Preparing for installation of Synthetic Transaction software

This section lists system requirements and provides a planning sheet for

installation of Synthetic Transaction software.


Prerequisites for a Synthetic Transaction Recorder

Table 13. Synthetic Transaction Recorder and player requirements

Requirements1 Windows2

Operating system for recorders and

players

v Windows 2003 for Synthetic Transaction Investigator only

v Windows 2000 with Service Pack 4 or higher, in the following releases of

this operating system:

– Professional

– Server

– Advanced Server

v XP Professional, service pack 1 or higher

Disk space: Recorders Space requirements for recorders:

v Synthetic Transaction Investigator recorder: 35 MB

v Generic Windows recorder: 350 MB (The recorder software includes the

player.)

Disk space: Players Space requirements for players:

v Synthetic Transaction Investigator player: 85 MB

v Generic Windows player: 350 MB (The player software includes the

recorder.)

Processor Intel-compatible, ix86, 1.2 GHz

Memory 256 MB

Swap Space 400 MB

Bit architecture 32-bit

Notes:

1. The installation program for management agents automatically installs the required Java software. This software

enables the management server to upload the synthetic transactions that you record. For operating systems other

than Solaris, the required Java Runtime Environment, Version 1.3.1, is available from IBM. For Solaris, the

required Java Runtime Environment, Version 1.3.1, is available from Sun Microsystems, Inc.

2. Emulated ix86 environments or environments where Windows is not the initially loaded operating system (slave

ix86 processor cards or mixed processor environments) are not supported.

Installing the recording software for Synthetic Transaction Investigator

Objective

To install the recording software so that you can record STI (Synthetic Transaction

Investigator) synthetic transactions.


Note: IBM Tivoli Monitoring for Transaction Performance, Version 5.3 Administrator’s

Guide describes the process that deploys the STI player software to

management agents.


The user who installs the product must have stiradmin privileges.

Chapter 8. Installing the Synthetic Transaction Recorders and Generic Windows 67

Before you begin

v Verify that the management server is up and running. The installation process

registers the STI Recorder with the management server.

v Collect the information about the management server:

– The fully qualified host name or the IP address of the host computer for the

management server.

– The type of communication—secure (SSL-enabled) or non-secure—used by the

management server. (If you specify https:// in the Web address for the

management server when accessing it from a Web browser, it is a secure

server.)

– The port number used by the management server for communication. The

default port number for non-secure communication is 9082. The default port

number for secure communication is 9446.v Verify that the proxy is configured in the connection settings of Internet Explorer

if the recording software needs to connect to the management server through a

proxy server.

Note: Microsoft Internet Explorer Version 6.0 must be installed on the computer

where you are installing the STI Recorder.

1. Open the Internet Explorer browser.

2. Select Internet Options from the Tools menu.

3. Select the Connections tab.

4. Click the LAN Settings button.

5. Click the check box labeled Use a proxy server for your LAN.

6. Enter the fully qualified name of the host computer for the proxy server in

the Address field.

7. Enter the port number used by the proxy server in the Port field.

When you finish

v Deploy the STI player software to management agents as described in the IBM

Tivoli Monitoring for Transaction Performance, Version 5.3 Administrator’s Guide. The

player can play the transactions your record.

v Use the recorder software to record a synthetic transaction as described in the

IBM Tivoli Monitoring for Transaction Performance, Version 5.3 Administrator’s Guide.

v Add the synthetic transaction to a Playback policy, as described in the IBM Tivoli

Monitoring for Transaction Performance, Version 5.3 Administrator’s Guide. The

Playback policy runs the synthetic transaction on the schedule you specify.

Procedure

1. Access the Downloads section of the IBM Tivoli Monitoring for Transaction

Performance interface.


2. Click Download Synthetic Transaction Investigator Recorder.

3. Click the setup_sti_recorder.exe download link to display the file download

window.

4. Click Save to save setup_sti_recorder.exe to the hard disk of the target

computer.

5. Double-click the installation executable file on the target computer to begin

installation.

6. Click Next on the Welcome window to display the license agreement window.

7. Select I accept the terms in the license agreement and click Next to display

the destination directory window.

8. Perform one of the following actions:

v Accept the default installation directory that is displayed in the Directory

name field.

v Use the Browse button to select a different installation directory.

v Enter a different installation directory in the Directory name field. 9. Click Next. The installation program creates the installation directory you

specified if it does not already exist.

The Management Server Information window is displayed.

Figure 6. Download STI Recorder window


10. Type information in the following fields about the management server to

which the software will be registered:

Hostname Enter the fully qualified host name or the IP address of the

host computer for the management server. Do not include a

protocol. For example, enter server_name.your_company.com,

not https://server_name.your_company.com.

SSL Enabled Select this box if the management server is using Secure

Sockets Layer (SSL) communications. If you specify https://

in the Web address for the management server when accessing

it from a Web browser, select this option.

Use Default Port Number?

Specify whether the management server uses the port number

displayed in the Port Number field. By default, the Yes radio

button is selected. To specify a different port, click the No

radio button and enter the correct port number in the Port

Number field.

Port Number Enter the port number used by the management server. This

field is active only if the Use Default Port Number? radio

button is set to No.11. Click Next. An information screen displays the installation path and the

amount of disk space that is required for the installation.

12. Click Next to proceed with the installation.

Figure 7. Synthetic Transaction Investigator Management Server Information window


13. When the installation program completes, click Finish to exit.

Additional Information: To start the software, click Start in the Windows taskbar

and access the Programs folder. Click the Synthetic Transaction Investigator

Recorder shortcut for launching the Synthetic Transaction software that is

located in the Tivoli folder. See the Administrator’s Guide for more

information on recording synthetic transactions.

Installing Generic Windows recording and playback

Objective

To install the recording and playback software for Generic Windows synthetic

transactions.


The recording and playback software for Generic Windows transactions exists in a

single software application called Rational Robot. In contrast, the STI recorder and

player are separate applications.

The process of working with Generic Windows synthetic transactions includes

installation of software, recording, uploading a recorded transaction, and creating a

Playback policy that distributes and plays the transaction on one or more

management agents.

Note: Install Generic Windows on a computer that is not a management agent.

Otherwise, the recording and testing of one transaction could interfere with

playback of a separate transaction.


If you are downloading the installation image on the IBM Tivoli Monitoring for

Transaction Performance user interface, you must have gwadmin privileges.

If you are installing from the installation CD-ROMs, on UNIX you must have root

privileges and on Windows you must have membership in the Administrators

group.

Before you begin

If plan to run Rational Robot on a Citrix server you must contact IBM Software

Support and request a floating Rational Robot License key before starting your

installation.

When you finish

Deploy software to enable Generic Windows communications in IBM Tivoli

Monitoring for Transaction Performance on management agents as described in the

IBM Tivoli Monitoring for Transaction Performance Administrator’s Guide.

Record a synthetic transaction in Rational Robot. See the documentation for

Rational Solutions for Windows for more information.

Add the synthetic transaction to a Playback policy, as described in the IBM Tivoli

Monitoring for Transaction Performance Administrator’s Guide. The Playback policy

runs the synthetic transaction on the schedule you specify.


Procedure

Note: If you purchased installation CD-ROMs, you can run the robot2003.exe

installation executable file from the CD-ROM drive of the target computer.

This procedure is written as if you were downloading the installation image

on the IBM Tivoli Monitoring for Transaction Performance user interface

1. Choose the Download Generic Windows Recorder item in the Download

section of the navigation tree of IBM Tivoli Monitoring for Transaction

Performance.

2. Read the license agreement for this software in the Download Generic

Windows Recorder page.

3. Click robot2003.zip to download the zipped software image.

4. Unzip the file.

5. Run the installation executable file, robot2003.exe.

6. Follow the instructions in the windows of the installation program.

During the installation process you must provide a Rational Robot license key.

The license key is contained in the .upd file that was downloaded as part of the

robot2003.zip file. Browse to the directory in which you expanded the

robot2003.zip file and select the .upd file.


Chapter 9. Creating and deploying SSL key files

This section describes how to customize the default settings for SSL authentication

in IBM Tivoli Monitoring for Transaction Performance.

Note: If you performed an embedded installation of the WebSphere Application

Server with IBM Tivoli Monitoring for Transaction Performance, use the

WebSphere default key. For more information on WebSphere default keys,

refer to the WebSphere Application Server documentation.

Creating key files

This section describes how to create key files to secure the IBM Tivoli Monitoring

for Transaction Performance environment.

Note: For third party vendor key file procedures, go to “Deploying the WebSphere

Application Server key files” on page 77.

Java Key Store (JKS) format enables you to store keys privately on your hard disk.

If other users have access to a key store file, they cannot edit the key unless they

know the password for that key. IBM Tivoli Monitoring for Transaction

Performance makes use of the following files:

v JKS file used by the management server.

v JKS file used by the Store and Forward agent and management agents that

connect to the management server through the Store and Forward agent.

v JKS file used by management agents that have a direct connection to the

management server.

v Key database file used by the WebSphere Caching proxy.


UNIX: the user must have root privileges.

Windows: the user must be a member of the Administrators group.

Procedure

1. Launch the IBM Key Management Utility on the management server as

follows:

v Windows:

a. Open Windows Explorer and navigate to the following directory:

WebSphere\AppServer\bin\

b. Double-click the iKeyman.bat file to launch iKeyman.v UNIX:

a. Open the command-line interface and navigate to the following

directory: WebSphere/AppServer/bin/

b. Type iKeyman.sh to launch iKeyman. 2. From the iKeyman toolbar, Click Key Database File → New.

3. Complete the following fields:

73

Key database type

Select JKS from the drop-down menu.

Filename

Type the name of the key file. For example:

v prodms.jks - Suggested key file name for the management server

v proddmz.jks - Suggested key file name for the Store and Forward

Agent and management agents that connect to Store and Forward

agent

Location

Select the directory location for the files. 4. Click OK.

5. Enter a password for the JKS file in the Password field.

Note: You must remember and save this password. This password cannot be

reset. If this password is lost or forgotten, you must create new key

files.

6. Type the password again in the Confirm Password field.

7. Click OK to complete the creation of the key database file and display the

IBM Key Management window. A list of existing certificates stored in the key

database and marked as trusted (Signer) certificates is displayed.

8. Click Create → New Self Signed Certificate.

9. Enter the following self-certificate details:

Key Label

prodms

Common Name

Fully qualified host name of the host where the management server

will be installed, for example, testing03.uk.tivoli.com.

Organization

IBM

Country or Region

Select the country or region where you are located.

Validity Period

365 days is the default. You can specify a different length of time.Leave the rest of the optional fields blank. The new self-signed certificate is

displayed in the Personal Certificates list.

10. Click Extract Certificate to extract the new prodms self-signed certificate and

display the Extract Certificate to a File window.

11. Choose the following options in the Extract Certificate to a File fields:

Data type

Base64-encoded ASCII data

Certificate filename

Name of the certificate file. For example:

v prodmscert.arm - Suggested certificate file name for the

management server

v proddmzcert.arm - Suggested certificate file name for the Store and

Forward Agent

v prodagentcert.arm - Suggested certificate file name for the

WebSphere Caching Proxy on the management agent


Location

The directory location of the certificate files.12. Click OK.

13. Repeat steps 1 to 12 to create the Store and Forward key files.

14. Repeat steps 1 to 12 to create the management agent key files.

After creating the key files you should have the following files:

v prodms.jks

v prodmscert.arm

v proddmz.jks

v proddmzcert.arm

v prodagent.jks

v prodagentcert.arm

Creating a KeyDataBase for the WebSphere Caching Proxy on

the Store and Forward Agent

The KeyDataBase (KDB) file is created using the GSKIT5 tool that is provided with

the WebSphere Application Server as an installable package. The installation files

are located in the WebSphereroot/gskit7install/ directory. After installation, start the

utility with the gsk7ikm executable/binary.

Note: You must have Java 1.4 installed to run gsk7ikm.

Use the following steps to create a KeyDataBase:

1. Launch the GSKIT5 utility on the management server as follows:

v On Windows, open Windows Explorer and navigate to the Program

Files\ibm\gsk7\bin\ directory.

v On UNIX-based systems, open the command-line interface and navigate to

the directory containing gsk7ikm.sh. The path to this directory varies by

UNIX platform. 2. Run one of the following commands:

v On Windows, run gsk7ikm.exe.

v On UNIX-based systems, run gsk7ikm.sh. 3. From the iKeyman toolbar, click Key Database File → New.

4. Complete the following fields:

Key database type

Select CMS key database file from the drop-down menu.

Filename

prodsnf.kdb - Suggested file name for the Store and Forward Agent

KeyDataBase file.

Location

Select the directory location for the files. 5. Click OK.

6. Type a password for the .kdb file in the Password field.

7. Type the password again in the Confirm Password field.

8. Select Stash the password to a file to store the password in the prodsnf.sth

file.

9. Click OK.

Chapter 9. Creating and deploying SSL key files 75

10. Repeat steps 8 to 12 of “Creating key files” on page 73 to create a certificate

file for the WebSphere Caching Proxy on the Store and Forward Agent.

After creating the KeyDataBase, you should have following files:

v prodsnf.kdb

v prodsnf.sth

v prodsnf.arm

Importing certificates into the JKS and KDB files

Import the .arm certificates into the JKS and KDB files. The following list shows

the JKS and KDB files and necessary certificates:

key file name Certificates

prodms.jks prodms.arm, prodagent.arm, proddmz.arm, prodsnf.arm

prodagent.jks prodsnf.arm, prodms.arm, prodsnf.arm

proddmz.jks proddmz.arm, prodms.arm, prodsnf.arm

prodsnf.kdb prodsnf.arm, proddmz.arm, prodms.arm

Use the following steps to import certificates:

1. Launch the IBM Key Management Utility on the management server.

2. Click Key Database File → Open.

3. Add certificates to the prodms.jks file:

a. Browse to the directory where the prodms.jks file is located.

Additional Information: This is the directory location you specified in step 3

on page 73.

b. After the key file is open, select Signer Certificates from the drop-down

menu.

c. Click Add.

d. Browse to the directory where prodms.arm file is located.

e. Click OK.

f. Type a label for the certificate, such as prodms and click OK.

g. Repeat Steps 3c to 3f to add the following additional certificates to the

prodms.jks file:

v prodagent.arm

v proddmz.arm

v prodsnf.armh. Click Key Database File → Close.

4. Add certificates to the proddmz.jks file:

a. Browse to the directory where the proddmz.jks file is located.


menu.

c. Click Add.

d. Browse to the directory where the proddmz.arm file is located.

e. Click OK.

f. Type a label for the certificate, such as proddmz and click OK.


proddmz.jks file:


v prodms.arm

v prodsnf.armh. Click Key Database File → Close.

5. Add certificates to the prodagent.jks file by performing the following steps:

a. Browse to the directory where the prodagent.jks file is located.


menu.

c. Click Add.

d. Browse to the directory where the prodagent.arm file is located.

e. Click OK.

f. Enter a label for the certificate, such as prodagent and click OK.


prodagent.jks file:

v prodms.arm

v prodsnf.armh. Click Key Database File → Close to close the key file.

6. Add certificates to the prodsnf.kdb file by performing the following steps:

a. Open the IBM GSKIT5 utility and browse to the directory where the

prodsnf.kdb file is located.


menu.

c. Click Add.

d. Browse to the directory where the prodsnf.arm file is located.

e. Click OK to display the Enter a Label window.

f. Enter a label for the certificate, such as prodsnf and click OK.


prodsnf.kdb file:

v proddmz.arm

v prodms.armh. Click Key Database File → Close to close the key file.

Deploying the WebSphere Application Server key files

Use the WebSphere Administrative Console to modify the IBM Tivoli Monitoring

for Transaction Performance security settings to use the new management server

key file, prodms.jks.

Note: Copy the key file to a location on the management server where it can

reside permanently.

Use the following steps to deploy the WebSphere Application Server key files:

1. Launch the WebSphere Administrative Console, located at

https://mshostname:9043/admin/, and log in.

2. Modify the : host/TMTPSettings_WithOut_ClientAuth settings by performing

the following steps:

a. Click Security → SSL → : host/TMTPSettings_WithOut_ClientAuth.

b. Change keyfilename to /data/prodms.jks.

c. Change keyfile Password to the prodms.jks password you created in Step 5

on page 74.


d. Change Trust filename to /data/prodms.jks.

e. Change Trust File Password to the prodms.jks password you created in step

5 on page 74.

f. Click OK to save these changes and display a confirmation window.

g. Click Save to apply changes to the master configuration.

h. Click Save.3. Modify the host/TMTPSettings_With_ClientAuth settings by performing the

following steps:

a. Click Security SSL.

b. Select host/TMTPSettings_With_ClientAuth.

c. Change keyfilename to prodms.jks.

d. Change keyfile Password to the /data/prodms.jks password.

e. Change Trust filename to /data/prodms.jks.

f. Change Trust File Password to the prodms.jks password.

g. Click OK to save these changes and display a confirmation window.

h. Click Save to apply changes to the master configuration.

i. Click Save.4. Log out of the WebSphere Administrative Console

Deploying the management server key file

Deploy the new management server key file to the management server. Use the

following steps:

1. Install patch 5.2-TIV-WTP-0012, which contains the password encryption utility,

pass_util.jar, to encrypt the password used by the key file.

2. Copy the pass_util.jar file to the management agent base directory, C:\Program

Files\ibm\tivoli\MA\.

3. Open a command-line interface, and run the following command:

ma_base>/jre131/jre/bin/java -jar pass_util.jar <password of prodms.jks keyfile

where password of prodms.jks keyfile is the password you entered in step 5 on

page 74.

Note: This prints out a new management agent and management server key

password in an encrypted format. You only need the management server

key for this step.

4. Copy the ms_base/config/server.properties file before modifying it.

5. Modify the following values in the server.properties file:

a. ms.keystore=newly encrypted prodms.jks password

where newly encrypted prodms.jks password is the password from you entered

in step 5 on page 74.

b. ms.keypass=prodms.jks location

where prodms.jks location is the location of the new management server key.6. Restart WebSphere Application Server for changes to take effect.

Deploying the Store and Forward Agent key file

Deploy the Store and Forward Agent key file to the Store and Forward agent.


Note: Before deploying the Store and Forward Agent key file, copy the

pass_util.jar file to the management agent base directory (C:\Program

Files\ibm\tivoli\MA\) if you have not already done so.

Use the following steps to deploy the key file:

1. Copy the dmzagent.jks, prodsnf.kdb, and prodsnf.sth agent key files to the

management agent directory (C:\Program Files\ibm\tivoli\MA\).

2. Run the following command from a command line:

MA_BASE/jre131/jre/bin/java -jar pass_util.jar password of dmzagent.jks keyfile

where password of dmzagent.jks keyfile is the password you entered in Step 5 on

page 74.

Note: This prints out a Store and Forward Agent and management server key

password in an encrypted format. You only need the management agent

key for this step.

3. Copy the /SnF/config/endpoint.properties file before modifying it.

4. Modify the following values in the endpoint.properties file:

endpoint.keystore=newly encrypted dmzagent.jks key password

endpoint.keypass=dmzagent.jks key location

where dmzagent.jks key location is the location of the new management agent

key.

5. Go to the WebSphere Caching Proxy directory, C:\Program

Files\ibm\edge\cp\etc\en_US.

6. Copy of the ibmproxy.conf file before modifying it.

7. Modify the following values in the ibmproxy.conf file:

KeyRingprodsnf.kdb key location

where prodsnf.kdb key location is the location of the prodsnf.kdb key.

KeyRingStashprodsnf.sth key location

where prodsnf.sth key location is the location of the prodsnf.sth key.

8. Restart the Store and Forward Agent and WebSphere Caching Proxy service for

changes to take effect.

Deploying the management agent key file

Deploy the management agent key file to the management agent.

Note: Before deploying the management agent key file, copy the new agent key

file (prodagent.jks) and the pass_util.jar file to the management agent base

directory (C:\Program Files\ibm\tivoli\MA\) if you have not already done

so.

Use the following steps to deploy the management agent key file:

1. Run the following command from a command line:

MA_BASE/jre131/jre/bin/java -jar pass_util.jar password of prodagent.jks keyfile

where password of prodagent.jks keyfile is the password you entered in step 5 on

page 74.

2. Copy the /ma_base/config/endpoint.properties file before modifying it.

3. Modify the following values in the endpoint.properties file:


endpoint.keystore=newly encrypted prodagent.jks key password

endpoint.keypass=prodagent.jks key location

where prodagent.jks key location is the location of the new management agent

key.

Note: This prints out a management agent and management server key

password in an encrypted format. You only need the management agent

key for this step.

4. Restart the management agent for changes to take effect.

5. Repeat this procedure on each management agent that communicates with the

Store and Forward agent.


Chapter 10. Configuring product settings in WebSphere

Application Server

IBM Tivoli Monitoring for Transaction Performance runs as a service in WebSphere

Application Server. The following sections provide information on configuring the

WebSphere Application Server:

v “Accessing the administrative console of the WebSphere Application Server”

v “Assigning authorization roles”

v “Possible port number conflicts on AIX”

The user account used to install IBM Tivoli Monitoring for Transaction

Performance is automatically authorized to perform all operations in IBM Tivoli

Monitoring for Transaction Performance. You can authorize other users to perform

some or all of these procedures as described in “Assigning authorization roles.”

Accessing the administrative console of the WebSphere Application

Server

You can configure WebSphere Application Server security, permissions, and other

settings for IBM Tivoli Monitoring for Transaction Performance because the

product runs as an application in the WebSphere Application Server. By default,

the administrative console for the WebSphere Application Server can be accessed at

the following locations:

When IBM WebSphere Global Security is enabled

https://hostname:9043/admin

When IBM WebSphere Global Security is not enabled

http://hostname:9090/admin

Where hostname is the name of the computer where the WebSphere Application

Server product is installed.

Possible port number conflicts on AIX

The port 9090, which is the default port for the version of WebSphere Application

Server delivered with IBM Tivoli Monitoring for Transaction Performance, is

typically used on AIX by the AIX WebSM service. To avoid port conflicts, change

the Admin Console Port value to a free port or disable WebSM. To disable

WebSM, run the following command:

/usr/websm/bin/wsmserver -disable

Assigning authorization roles

Objective

To enable users to perform specific tasks in IBM Tivoli Monitoring for Transaction

Performance by assigning authorization roles.

81


The user account used to install IBM Tivoli Monitoring for Transaction

Performance is automatically authorized to perform all procedures. You can

authorize other users to perform some or all of these procedures. You can use role

assignment to control access to the product user interface or to simplify navigation

for specific groups of users. You can assign any combination of roles to a user. For

example, a user can be a Quality of Service administrator (qosadmin) and a

Generic Windows administrator (gwadmin).

The WebSphere Application Server user that you specify during installation

receives all available roles. This user can perform all operations in IBM Tivoli


Table 14 shows the available authorization roles.

Table 14. Available authorization roles

Name Authorized

action

Target of action

admin (all actions) All views in the user interface

genarmadmin Modify View all genarm policies

Modify policies:

- create new

- edit,

- delete,

- create from,

- view details,

- disable, and

- view discovered transactions

genarmviewer View All genarm policies

gwadmin Modify Deploy the Generic Windows component

Generic Windows policy

Transaction recordings

Schedules for playback

Agent groups

Configure user settings

gwviewer View Generic Windows policy

Transaction recordings


Agent groups


j2eeadmin Modify Deploy the J2EE component

J2EE listening policies

J2EE discovery policies

Schedules for listening and discovery policies

Agent groups


j2eeviewer View J2EE listening policies

J2EE discovery policies


Agent groups



Table 14. Available authorization roles (continued)

Name Authorized

action

Target of action

qosadmin Modify Deploy the QoS component

QoS discovery policies

QoS listening policies


Agent groups


qosviewer View QoS discovery policies

QoS listening policies


Agent groups


reportsviewer View All reporting views


stipadmin Modify Deploy the STI component

STI playback policies

Realms

Transaction recording


Agent groups


stiradmin Modify Download STI Recorder

Transaction Recordings


stiviewer View STI playback policies

Realms

Transaction recording


Agent groups


systemadmin View Management agents

Configure event details

Manage data

Event Responses

System events

Log files

Management server details


systemviewer View System events

Log files

Management server details



You must specify a user name and password for a user account in IBM WebSphere

Application Server.

Before you begin

None

Chapter 10. Configuring product settings in WebSphere Application Server 83

When you finish

None

Procedure

1. Access the Administrative Console for the IBM WebSphere Application Server,

which is located by default at the following HTTP address on the host

computer:

http://server_name:9090/admin

where server_name is the name of the WebSphere Application Server.

The user ID and password is the user account under which the secure

WebSphere Application Server is running. This user account is defined in the

operating system. You associate the account with IBM Tivoli Monitoring for

Transaction Performance during installation.

2. Expand the Applications section of the navigation tree.

3. Click Enterprise Applications.

4. In the Enterprise Applications table, click ITMTP.

5. In the Additional Properties table, click Map security roles to users/groups.

6. Apply a role to one or more users as follows:

a. Select the role that you want to apply to a user. For example, if you want to

authorize a user to administer the Quality of Service component, select

qosadmin. SeeTable 14 on page 82 for details of the different roles.

b. Click Lookup users.

c. Find the users to which you want to apply a role. For example, to search for

all available users for the current operating system, type an asterisk (*) in

the Search String box and click Search.

d. Move the users you want to authorize into the Selected users column by

highlighting a user and clicking on the >> button.

e. Click OK and then click OK again.7. In the Message(s) pane, click Save.

8. Click Save.

9. Restart the ITMTP application so that your changes take effect:

a. Click Enterprise Applications in the Applications section of the navigation

tree.

b. Select ITMTP and click Stop in the toolbar at the top of the view.

c. Click Start to restart the application.


Chapter 11. Installing a language pack

A language pack is a set of files you install to view the GUI or log files in a

language other than English. For example, when a Spanish language pack is

installed on the host computer for the management server, you can view the IBM

Tivoli Monitoring for Transaction Performance GUI in Spanish from any browser

that is set to display in Spanish.

Installing a language pack

Objective

To install a language pack so that you can view the user interface, log files, or the

STI Recorder in a language other than English.


Language packs are available for the following components of the product:

Component Language pack function Additional information

Management server Provides the ability to see

the user interface in any of

the installed languages.

When you install language

packs on the management

server, they are automatically

downloaded and installed on

the management agents.

Management agent Provides the ability to see

log files in any of the

installed languages.

In an international

environment, the operating

system locale of different

management agents can vary.

To enable viewing of log files

in the language of a

particular management

agent, select the language

pack that matches the

operating system locale of

the computer.

STI Recorder Provides the ability to see

the STI Recorder GUI in any

of the installed languages.

None.

IBM Tivoli Monitoring for Transaction Performance provides language packs in the

following languages:

Brazilian Portuguese

Chinese (Traditional)

Chinese (Simplified)

Italian

French

German

Japanese

Korean

Spanish

You can install language packs for some or all of the supported languages in a

single installation. For example, you might install multiple language packs on the

management server, to allow administrators in different locations to view the GUI

in their language.

85





Before you begin

1. Verify the installation directory of the IBM Tivoli Monitoring for Transaction

Performance component (management server or STI Recorder) on the computer

where you plan to run the language pack installation program. You must install

the language packs to the same directory. The following are default installation

directories for the management server:

v Windows: C:\Program Files\IBM\tivoli\MS

v All UNIX systems: /opt/ibm/Tivoli/MS2. Verify that there is sufficient space for temporary files. The language pack

installation programs require a minimum of 64 MB for temporary files.

The language pack installation programs place temporary files by default in the

following locations:

v On Windows systems, the location specified by the TEMP environment

variable setting

v On AIX and Linux, the /tmp directory

v On Solaris, the /var/tmp directory

You can change the location for temporary files by using the -is:tempdir option

when you start the installation program.

3. If you are installing language packs for the management server and

management agents, stop the management server before starting the

installation. See IBM Tivoli Monitoring for Transaction Performance Administrator’s

Guide for instructions on starting and stopping these components.

When you finish

1. Restart the management server or management agent.

2. Verify the installation by accessing the user interface or the STI Recorder.

Browsers are set to display by default in the language of the operating system

of the computer where the browser is installed. To verify the installation of

multiple language packs, do the following in the browser:

a. If necessary, add more languages to the language setting of the browser.

b. Each time you want to display the GUI in a different language, move that

language to the top of the priority list.3. If you want to view log files in multiple languages on an management agent,

you must reset the locale of the operating system each time you want to switch

languages.

Procedure

The language pack installation programs are provided on the IBM Tivoli Monitoring

for Transaction Performance, Language Support CD.

1. Start the installation program by either browsing to the location of the

installation program and double clicking on the appropriate program, or by

running the following command from a command line:

command [-is:tempdir temp_dir]

where command is the command found in table Table 15 on page 87 and

temp_dir is the directory where you want the installation program to place

temporary files.


Table 15. Locations of language pack installation programs

Operating

System

Management server Management agent STI Recorder

Windows w32-ix86/ ITMTPS.exe w32-ix86/ITMTPA.exe w32–ix86/STIRLP.exe

AIX aix_power/ITMTPS.bin aix_power/ITMTPA.bin Not applicable

Sun Solaris solaris/ITMTPS.bin solaris/ITMTPA.bin Not applicable

Linux with

Intel™

Processor

linux-ix86/ITMTPS.bin linux-ix86/ITMTPA.bin Not applicable

Linux

mainframe

with s/390

processor

linux-390/ITMTPS.bin linux-390/ITMTPA.bin Not applicable

2. Click Next on the Welcome screen.

3. Read the software license agreement. Select the radio button to accept the

terms of the agreement.

4. Click Next.

5. Click Next to install the language pack to the directory displayed in the

Directory name field. Use the Browse button to select a different directory.

Notes:

v You must install the language pack to the same directory where the

management server or STI Recorder is installed. The Directory name field

displays the default installation directory for the component.

v On UNIX systems, do not install to a directory with special characters in

the directory name. 6. Click Next.

7. In the customization window, clear the check boxes for the language packs

that you do not want to install.

8. Click Next.

The installation program displays a window that shows the location, features,

and size of the language packs to be installed.

9. Click Next to start installation of the language packs.

10. When the installation is complete, click Finish to exit.

Chapter 11. Installing a language pack 87


Appendix A. Upgrading an installation of IBM Tivoli

Monitoring for Transaction Performance

This section provides information for upgrading to IBM Tivoli Monitoring for

Transaction Performance, Version 5.3 from either Version 5.1 or 5.2.

Upgrading IBM Tivoli Monitoring for Transaction Performance Version

5.2 to Version 5.3

Objective

To upgrade a Version 5.2 installation of IBM Tivoli Monitoring for Transaction

Performance to Version 5.3.


The IBM Tivoli Monitoring for Transaction Performance, Version 5.2 to 5.3 installs

the new software on your management server and migrates your WebSphere

Application Server to Version 5.1 if you have not already running Version 5.1 or

5.0.2.

When you launch the upgrade program, the upgrade and migration are preformed

in the following order:

Note: If you are running WebSphere Application Server, Version 5.0.2 only the

management server is upgraded. There is no WebSphere Application Server

migration performed.

1. WebSphere Application Server, Version 5.1 is installed.

2. WebSphere Application Server, Version 5.0.1 is stopped and migrated to Version

5.1.

3. A back up file is created for WebSphere Application Server, Version 5.1 in the

installation directory:

Windows

C:\MS_INSTDIR\WAS51\was51_backup.zip

UNIX /opt/WebSphere/AppServer51/was51_backup.zip

AIX /usr/WebSphere/AppServer51/was51_backup.zip4. The IBM Tivoli Monitoring for Transaction Performance management server is

upgraded from Version 5.2 to 5.3.

If the management server fails, you can use the back up file to restore WebSphere

Application Server, Version 5.1 to its original condition and then run the

management server upgrade again.





89

Before you begin

v Back up your current database, refer to your database documentation for the

proper back up procedure.

v Create a back up of your current management server directory.

v Backup your WebSphere Application Server configuration:

backupConfig server1 -username username -password password

The backupConfig command is located in:

UNIX WAS_BASEDIR/bin/backupConfig.sh

Windows

WAS_BASEDIR\bin\backupConfig.bat

The restore commands are located in the same directories. Restore as follows:

restoreConfig backup_file -username username -password password

v If you have WebSphere Application Server, Version 5.0.1 Embedded Messaging

installed, you must upgrade WebSphere Application Server to Version 5.0.2 by

applying WebSphere Application Server Fixpack 2 before upgrading the

management server. Refer to the migration information on

http://wasinfo.raleigh.ibm.com for further information.

v Upload data to the IBM Tivoli Warehouse to ensure that you do not lose any

information.

v Ensure that the IBM WebSphere Application Sever is running.

v Upgrade all platforms to Version 5.3 supported levels before starting the

upgrade. See, Chapter 2, “Prerequisites,” on page 7.

v (Optionally) Enable Java 2 security. See, Appendix E, “Enabling Java 2 security


When you finish

v (Optionally) If you have performed the upgrade successfully using the embedded

migration to IBM WebSphere Application Server, Version 5.1, manually uninstall

IBM WebSphere Application Server, Version 5.0.1. Refer to the migration

information on http://wasinfo.raleigh.ibm.com for further information.

v Clean up the IBM WebSphere Application Server base directory. See, “Cleaning

up the WebSphere Application Server base directory” on page 101.

v Manually start IBM WebSphere Application Server, Version 5.1. IBM WebSphere

Application Server, Version 5.1 does not populate the start menu after an

upgrade.

Procedure

Notes:





2. These instructions assume you are migrating WebSphere Application Server,

Version 5.0.1 to Version 5.1. If you have already moved to WebSphere

Application Server, Versions 5.0.2 or 5.1 you will not see the windows

describing the WebSphere Application Server migration below.


http://wasinfo.raleigh.ibm.com

http://wasinfo.raleigh.ibm.com

Part 1. Upgrade the Version 5.2 management server

Note: Schedule your upgrade for when it is convenient for the management server

to be down and IBM WebSphere Application Server to be restarted.

1. Log on to the host computer for the management server.

2. Close all browser windows that are connected to the IBM Tivoli Monitoring

for Transaction Performance user interface being upgraded.

3. Access your installation_image_directory\ITMTP_WTP_4\MS_52Upgrade\disk1

directory:

v For Windows, run setup_MSUpgrade_w32.exe.

v For AIX, run setup_MSUpgrade_aix.bin.

v For Solaris, run setup_MSUpgrade_sol.bin.

v For Linux xSeries, run setup_MSUpgrade_lin.bin.

v For Linux 390, run setup_MSUpgrade_lin390.bin

4. Click Next in the Welcome window to display the embedded installation

information window.




Next.

7. Click Next to accept the default installation directory.

Additional information: The installation procedure discovers the location of the

current IBM Tivoli Monitoring for Transaction Performance management

server. If the displayed location is incorrect, browse to the correct location.

8. Enter the password information for the discovered WebSphere Application

Server user account and for the WebSphere Application Server key file and

trust files and click Next.

Note: The information entered on this panel is not verified against the

WebSphere Application Server. If you change any of the default entries

ensure that the information you enter is accurate.

9. Enter the password for the database user ID displayed and click Next.

Additional information: This information is confirmed with a test connection to

the database.

10. Click Next to accept the installation image locations or browse to the location

in which the IBM WebSphere Application Server, Version 5.1 installation

images are located.

11. Click Next to begin the migration of WebSphere Application Server, Version

5.0.1 to Version 5.1.

Additional information: This process installs WebSphere Application Server,

Version 5.1 and migrates all of the pertinent information for IBM Tivoli

Monitoring for Transaction Performance to the new installation. WebSphere

Application Server, Version 5.1 is installed in the following locations:

Windows

C:\MS_INSTDIR\WAS51

UNIX /opt/WebSphere/AppServer51

AIX /usr/WebSphere/AppServer5112. Click Next on the WebSphere Application Server migration complete window.

Appendix A. Upgrading an installation of IBM Tivoli Monitoring for Transaction Performance 91

13. Click Next to accept the installation locations for the management server

upgrade location.

14. Click Next and view the progress bar for the upgrade program.

15. Click Finish on the summary window.


the machine on which you upgraded your management server or by entering


Secure installation




Part 2. Upgrading the Version 5.2 Store and Forward agent

1. Log on to the computer on which you want to upgrade the Store and Forward

management agent.

Additional Information: This is a separate computer from the server and acts as

the gateway for communication between the management server and

management agents.

2. Copy the WebSphere Caching Proxy, Version 5.1 installation image into the

Store and Forward agent upgrade installation image directory:

installation_image_directory/ITMTP_WTP_4/SnFUpgrade/wcp.



installation_image_directory/ITMTP_WTP_4/SnFUpgrade:

v Windows: setup_SnFUpgrade_w32.exe

v AIX: setup_SnFUpgrade_aix.bin

v Solaris: setup_SnFUpgrade_sol.bin

v Linux: setup_SnFUpgrade_lin.bin

4. If the upgrade program detects IBM WebSphere Caching Proxy, Version 5.0

you are instructed to remove that product. IBM WebSphere Caching Proxy,

Version 5.1 is installed later in the upgrade process.

a. Cancel the current upgrade.

b. Remove IBM WebSphere Caching Proxy, Version 5.0. On Windows, reboot

your system.

Note: IBM WebSphere Caching Proxy, Version 5.0 is uninstalled using the

product installation image. You must locate your IBM WebSphere

Caching Proxy, Version 5.0 installation image and use that products

installation wizard to complete the uninstallation.

c. Restart the Store and Forward agent upgrade. 5. Click Next in the Welcome window to display the License Agreement

window.


Next.

7. Click Next to accept the default upgrade directory path and display the

Configuration of Proxy Host and Mask window.

8. Verify the information on the window and click Next to display the

WebSphere Caching Proxy window. This information is discovered by the

upgrade program and is read only.


9. Verify the information on the window and click Next to display the Product

Installation Directory window.

10. The Product Installation Directory window provides the location in which the

products are installed.

11. Click Next to display an installation confirmation window.

12. Click Next to begin upgrade.

Note: (Windows only) The computer will restart at this time.

13. Click Finish to complete the upgrade of Store and Forward agent.

Part 3. Upgrade the Version 5.2 management agent

Note: For J2EE, schedule your management agent upgrade for when it is

convenient for the application server you are instrumenting to be restarted.

If you selected auto-restart during your initial deployment of the J2EE

component your server restarts automatically during the upgrade. If you did

not select auto-restart during your initial deployment of the J2EE component

or you instrumented BEA WebLogic you must restart the instrumented

application server to complete the upgrade.

1. Access the upgraded IBM Tivoli Monitoring for Transaction Performance

management server user interface.

2. Select System Administration → Work with Agent Updates to display the Work

with Agent Updates window.

3. Select the management agents that you want to upgrade.

Notes:

a. The management agent table also displays the monitoring components

running on each agent and the update status of each component. In

situations where synthetic transaction investigator transactions are sent

through a quality of service proxy to the J2EE management server, the

components must be upgraded in the following order:

J2EE management server

Quality of Service

Synthetic Transaction Investigator

b. If you are upgrading J2EE instrumentation to a previously instrumented

secure IBM WebSphere Application Sever, Version 4, perform the following:

1) Edit the following fields in the

WAS_BASEDIR/properties/sas.client.props file:

com.ibm.CORBA.loginSource ----> set this value to properties

com.ibm.CORBA.loginUserid ----> set the login user id

com.ibm.CORBA.loginPassword---> set the login password

2) When the J2EE instrumentation upgrade is complete, the settings can be

set back to their original values.4. Select Install Update from the drop-down list, and click Go.

Additional information: When the update is complete the Update Status column

displays an Update Finished message.

If you were upgrading J2EE instrumentation to a IBM WebSphere Application

Server, Version 5.1 on Windows and there is a BMW directory in the WAS_HOME

directory, either reboot your computer or refer to the IBM Tivoli Monitoring for

Transaction Performance Problem Determination Guide for further instructions.


Upgrading a management agent on z/OS

Note: For J2EE, schedule your management agent upgrade for when it is

convenient for the application server you are instrumenting to be restarted.

If you selected auto-restart during your initial deployment of the J2EE

component your server restarts automatically during the upgrade. If you did

not select auto-restart during your initial deployment of the J2EE component

or you instrumented BEA you must restart the instrumented application

server to complete the upgrade.

Configure the management agent by performing the following steps:

1. Stop the management agent.

2. Copy the /usr/lpp/tmtp/V5R3M0/MA/config1/prepUpgradeConfig.sh and

setupEnv.sh files to the /tmp directory.

3. Verify that the setupEnv.sh command script points to the correct JAVA_DIR and

TMTP_DIR directories.

4. Run the prepUpgradeConfig.sh command script.

5. Change directories to /etc/tmtp/MA/config.

6. Open the zos.properties file and customize the following values so that the

configMa.sh command script can register the management agent to the

management server:

zos.baseDir=/usr/lpp/tmtp/V5R3M0/MA

7. Run the configMa.sh command script with the argument ″upgrade″ such as >>

./configMa.sh upgrade.

8. Start the management agent as described in “Starting and stopping a

management agent” on page 59.

9. Change the zos.properties file permissions to protect the password.

Upgrading IBM Tivoli Monitoring for Transaction Performance Version

5.1 to Version 5.3

Objective

To upgrade a Version 5.1 installation of IBM Tivoli Monitoring for Transaction

Performance to Version 5.3.


An upgrade requires the following conditions and sequence of events:

v The upgrade is performed on the computer that hosts the Tivoli Internet

Management Server (TIMS) for IBM Tivoli Monitoring for Transaction

Performance, Version 5.1.

Note: The upgrade migrates currently referenced Version 5.1 tasks and jobs

along with all associated configuration information. Migrated tasks run as

5.3 management policies. Additional configuration information that exists

in the Version 5.1 TIMS environment but is not referenced by the

upgraded tasks does not migrate. For example, if a Version 5.1

environment has ten recorded STI transactions, but only nine transactions

are referenced by jobs at the time of the upgrade, only the nine referenced

transaction recordings upgrade. The recording that is not in current use

does not migrate.


v The database for the Version 5.1 Tivoli Internet Management Server must be

running during the upgrade.

v The following Version 5.1 components do not have to be running because the

upgrade program references static files:

– The Tivoli Internet Management Server

– The Internet Management Endpoints for the Tivoli Internet Management

Serverv The following Version 5.3 components must be installed and running:

– The management server.

– (When you perform the upgrade across the firewall only) A management agent

located outside of the firewall and hosting the Store and Forward Service

(called the Store and Forward agent). The Store and Forward agent enables

communication across a firewall to the management server.v The management agent software for Version 5.3 is installed on each Version 5.1

endpoint that you want to upgrade. This software enables you to deploy and

run monitoring components, such as J2EE, QoS, and synthetic transactions.

v The final stage of the upgrade process on the Version 5.3 management server is

complete. This stage results in the deployment of updated monitoring

components and the initiation of monitoring.

An upgrade transfers STI endpoints, QoS endpoints, and QoS and STI jobs from

Version 5.1 to Version 5.3 of the product.

Note: If you run Version 5.1 QoS endpoints on Solaris 7, you must upgrade the

operating system to Solaris 8 before performing an upgrade.





Before you begin

v Back up your current database, refer to your database documentation for the

proper back up procedure.

v Create a back up of your current management server directory.

v Backup your WebSphere Application Server configuration:

backupConfig server1 -username username -password password

The backupConfig command is located in:

UNIX WAS_BASEDIR/bin/backupConfig.sh

Windows

WAS_BASEDIR\bin\backupConfig.bat

The restore commands are located in the same directories. Restore as follows:

restoreConfig backup_file -username username -password password

v Confirm that 100 MB of free disk space is available for the temporary directory

on the computer that hosts the Tivoli Internet Management Server. The upgrade

program temporarily stores files in that location. The temporary directory is

defined by an environment variable for the operating system. For example, the

environment variable for this directory on Windows typically is %TEMP%.


When you finish

v System Events configured to Event Responses that run a script in IBM Tivoli

Monitoring for Transaction Performance, Version 5.1 do not get configured to

run the same scripts in Version 5.3. These script task responses need to be

configured in the new version.

v If recorded transactions from Version 5.1 have meta-refresh content, you must

re-record them with the Version 5.3 Transaction Recorder. Otherwise, Page

Analyzer Viewer records cannot be generated for all redirected content.

v Restore an abort on violation setting from Version 5.1. The upgrade does not

preserve an abort on violation setting that was applied to STI transactions on an

endpoint in an installation of Version 5.1. Do the following to restore the setting:

1. Launch IBM Tivoli Monitoring for Transaction Performance, Version 5.3.

Secure installation




2. Access the Work with Playback Policies window of the Configuration section.

3. Select the check box beside the playback policy to which you want to apply

the abort on violation setting. Additional information: This abort on violation

setting applies to all management agents that are governed by this policy.

4. Select Edit in the drop-down menu in the table header.

5. Click Go to display the Configure Playback Policy window.

6. Select the Abort On Violation check box.

7. Click Finish to save your changes.v If you have the QoS component deployed, run the following steps to improve

performance after an upgrade:

1. Access the qos.config file located in /src/Qos/apache/conf/w32-ix86/qos.conf

2. Change all ProxyRequests from on to off.

3. Delete all lines that contain Rewrite directives (such as: RewriteEngine,

RewriteLogLevel, RewriteMap, RewriteRule) except for the lines within the

section labeled: This is the default host for the controller to contact.

4. Copy the two lines with ProxyPassReverse from each virtual host section and

paste the copies above the ProxyPassReverse lines without removing the #

character.

5. Change the ProxyPassReverse directive to ProxyPass. For example, update

the following lines:

ProxyPassReverse / http://host.example.com:80/

#ProxyPassReverse / OSPROTOCOL://OSHOSTNAME/

to:

ProxyPass / http://host.example.com:80/

#ProxyPass / OSPROTOCOL://OSHOSTNAME/

ProxyPassReverse / http://host.example.com:80/

#ProxyPassReverse / OSPROTOCOL://OSHOSTNAME/

Note: The apache-rproxy.conf-servers file is no longer needed after completing

these steps. you can optionally delete the file.

v Clean up the IBM WebSphere Application Server base directory. See, “Cleaning

up the WebSphere Application Server base directory” on page 101.


Procedure

Part 1. Upgrade the Version 5.1 Tivoli Internet Management

Server

1. Log on to the host computer for the Tivoli Internet Management Server.

2. Access your installation_image_directory\ITMTP_WTP_5\51_Upgrade directory:

See “Using installation files from the Web” on page 2 for more information on

obtaining installation files.

v For Windows, run setup_upgrade_w32.exe.

v For AIX, run setup_upgrade_aix.bin.

v For Solaris, run setup_upgrade_sol.bin.

v For Linux xSeries, run setup_upgrade_lin.bin. 3. Click Next in the Welcome window to display the Software License

Agreement window.

4. Select the I accept the terms in the license agreement radio button to accept

the terms of the license agreement.

5. Click Next to display the Connection Parameters for the Version 5.3

Management Server window.

6. Provide values for the following fields:

Host Name

The name of the computer that hosts the IBM Tivoli Monitoring for

Transaction Performance, Version 5.3, management server.

User Name

A valid user name on the management server that you specify in the

Host Name field.

User Password

A password for the user that you specify in the User Name field. 7. Type values for the following fields to define behavior for SSL authentication:

Enable one of the following SSL options:






server.

Enable SSL


layer (SSL).















Enable SSL


Key File Name




Key File Password


Trust File Name




Trust File Password











Port for SSL agents




secure environment.




secure environment. 8. Click Next and view the progress bar for the upgrade program.

9. Read the list of completed tasks in the final window that contains a Finish

button. This list shows the Version 5.1 monitoring tasks related to STI and

QoS that are automatically upgraded to be monitoring policies in Version 5.3

of the product.

10. Click Finish.

Note: System Events configured to Event Responses that run a script in IBM Tivoli

Monitoring for Transaction Performance, Version 5.1 do not get configured

to run the same scripts in Version 5.3. These script task responses need to be

configured in the new version.


Notes:

1. To perform this step you access the installation software that you obtained as

described in “Using installation files from the Web” on page 2. The following

steps describe enablement of SSL authentication for the management agent. You

have the option to disable SSL authentication. For example, a management

agent that you set up inside the enterprise might be secure and you might

want to disable SSL authentication when you install the agent.





Part 2. Installing the management agent software








installation_image_directory/ITMTP_WTP_3/MA:





v Linux zSeries: setup_MA_lin390.bin

v Linux pSeries: setup_MA_linppc.bin

v HP-UX: setup_MA_hp11.bin

3. Click Next in the Welcome window to display the Software License

Agreement window.






Next.


communication configuration window.




6. Complete the following fields to establish agent and server communication:

Host Name (fully qualified)

Type the fully qualified host name or IP address of the computer to

which this agent directs communication. If the agent is within the

enterprise and there is no firewall between the agent and the server,

type the management server computer information. If a firewall exists

between the agent and the server, type the Store and Forward Service

information. Do not include a protocol in the host name. For example,

type myserver.ibm.tivoli.com, not https://myserver.ibm.tivoli.com.


User Name

Type the user ID of a user who is authorized to log on to the

management server. This user must have the agent role on the IBM

WebSphere Application Server.

User Password

Type the password that corresponds to the user specified in the User

Name field.

Enable SSL

Ensure that this check box is selected for a secure installation or

cleared for a nonsecure installation.

SSL Key Store File

Type the directory path to the .jks file or browse to the appropriate

location. Sample jks files are delivered with the installation images:

installation_image_directory/ITMTP_WTP_3/MA/keyfiles.









Accept the Yes default if you used the default port number when you

installed the management server.

Port Number


number for the management server or Store and Forward Service to

which you are connecting.

No Proxy, Socks, HTTP

v Accept the default if you do not use a proxy server to represent the

management server.

v Select Socks if you use a Socket (Socks) server as a proxy server to

represent the management server.

v Select HTTPS if you use an HTTPS (secure Web) server as a proxy

server to represent the management server.

Proxy Host


represent the management server.The fully qualified name of the proxy host.

Port Number


represent the management server.The port number of the proxy host.



Accept the default port number of 1976. This is the port that is used

by the management server to communicate with this management

agent. 7. Click Next.

8. (Windows only) Use an existing Windows user or click the Create a new,

dedicated user account radio button and fill in the following fields:






Type a unique password. 9. Click Next to display the management agent information window.


11. Click Finish to complete the installation of the management agent software.

Part 3. Completing deployment

1. Access the upgraded IBM Tivoli Monitoring for Transaction Performance

management server.

2. Select System Administration → Work with Agent Updates to display the Work

with Agent Updates window.

3. Select the management agents that you want to upgrade.

4. Select Install Update from the drop-down list, and click Go.

Additional information: When the update is complete the Update Status column

displays an Update Finished message.

Cleaning up the WebSphere Application Server base directory

After completing the upgrade you should remove the listed .jar files from the

IBM_WebSphere_base_directory/lib/ext directory. This must be done when the

application server is down. The server needs to be down because the files are

locked when the server is up. The following file should be removed:

WebSphere Application Services Versions 4 and 5:

application_server_home/lib/ext/armjni.jar

application_server_home/lib/ext/copyright.jar

application_server_home/lib/ext/core_util.jar

application_server_home/lib/ext/ejflt.jar

application_server_home/lib/ext/eppam.jar

application_server_home/lib/ext/jffdc.jar

application_server_home/lib/ext/jflt.jar

application_server_home/lib/ext/jlog.jar

application_server_home/lib/ext/probes.jar

WebLogic:

application_server_home/server/lib/ext/armjni.jar

application_server_home/server/lib/ext/copyright.jar

application_server_home/server/lib/ext/core_util.jar

application_server_home/server/lib/ext/ejflt.jar

application_server_home/server/lib/ext/eppam.jar

application_server_home/server/lib/ext/jffdc.jar


application_server_home/server/lib/ext/jflt.jar

application_server_home/server/lib/ext/jlog.jar

application_server_home/server/lib/ext/probes.jar


Appendix B. Uninstalling IBM Tivoli Monitoring for

Transaction Performance components

This section describes how to uninstall the product components.

Table 16. Goals for the uninstallation of management agents

Goals Refer to

1. Uninstall management agents.

Note: You uninstall management agents

before you uninstall the management

server so that the uninstallation program

can delete management agent

registration information from the

management server.

“Uninstalling a management agent”

2. Uninstall management server. “Uninstalling the management server” on

page 106

3. Uninstall related software.

You can uninstall any related software

that came with your installation of IBM

Tivoli Monitoring for Transaction

Performance. These versions of the

software can be used only with IBM

Tivoli Monitoring for Transaction

Performance.

Note: If you used a preexisting

installation of DB2 or IBM WebSphere

Application Server, do not uninstall them

unless you are sure that they are not

being used for other purposes.

“Uninstalling the WebSphere Application

Server” on page 107

“Uninstalling IBM DB2” on page 107

“Uninstalling the recorder software” on page

108

“Uninstalling language packs” on page 109

Uninstalling a management agent

Objective

Uninstall a management agent for IBM Tivoli Monitoring for Transaction

Performance, including management agents that host the Store and Forward

Service.


To uninstall this software, you run an uninstall program from the command line.

On Windows, you can also use the Add/Remove Programs tool to uninstall the

management agent.

One or more management agents might host the Store and Forward Service, which

enables management agents located outside of the firewall to communicate with

the management server across the firewall. This procedure describes how to

uninstall this service.





103

Before you begin

None

When you finish

None

Procedure

Uninstall a management agent as follows::

1. Run the uninstallation program using one of the following options:

v Command Line: Run the uninstall program from the command line. For

example, on Windows launch the MS-DOS command-line interface.

– UNIX: product_installation_directory/MA/_uninst53/uninstall.bin

– Windows: product_installation_directory\MA\_uninst53\uninstall.exe

—OR—

v Add/Remove Programs tool:(Windows only) Use the Add/Remove Programs

tool as follows:

a. Access the Start menu in the Windows taskbar.

b. Choose Control Panel in the Settings menu item.

c. Click Add/Remove Programs.

d. Choose IBM Tivoli Monitoring for Transaction Performance

Management Agent in the list of available programs.

e. Click Remove to launch the uninstallation program.2. Click Next in the welcome window to display the directory window.

3. Click Next in the directory identification window.

4. Click Finish to complete the uninstallation.

Uninstall the Store and Forward Service that one or more management agents is

hosting:

Note: Uninstall all of the management agents that communicate through the Store

and Forward agent before uninstalling the agent.


v Run the uninstall program from the command line. For example, on

Windows launch the MS-DOS command-line interface.

– UNIX: product_installation_directory/SnF/_uninst53/uninstall.bin

– Windows: product_installation_directory\SnF\_uninst53\uninstall.exe

—OR—

v (Windows only) Use the Add/Remove Programs tool as follows:




d. Choose Store and Forward Agent in the list of available programs.

e. Click Remove to launch the uninstallation program.2. Click Next in the welcome window to display the directory window.



Note: The WebSphere Configuration Proxy is not uninstalled at this time.


Uninstalling a management agent in OS/400

Objective

Uninstall a management agent for IBM Tivoli Monitoring for Transaction

Performance, including management agents that host the Store and Forward

Service.


To uninstall this software, you run an uninstall program from the command line.


The user who installs the product must have at least *SYSADMIN.

Before you begin

None

When you finish

Edit the start up program so that the uninstalled management agents do not

appear in the list to start at IPL.

Procedure

1. Run QShell from the command line: qsh

2. Access the uninstallation directory:

/QIBM/UserData/tivoli/tmtp/MA/_uninst53/uninstall-OS400.sh

3. Run uninstall-OS400.sh.

Uninstalling a management agent for z/OS

Objective

Unregister a z/OS management agent for IBM Tivoli Monitoring for Transaction

Performance.


Uninstalling the z/OS management agent does not remove the deployed J2EE

components. WebSphere can fail to start if the management agent on z/OS is

uninstalled without first removing J2EE components.


The user who installs the product must have at least TMTPAGNT under the

TMTPGRP privileges.

Before you begin

None

When you finish

None

Procedure

1. Remove J2EE components from the z/OS management agent by performing

the following steps:

a. In the UI, click System Administration → Work with Agents, and select the

agents on which the J2EE component is running.

b. Select Remove component from the drop-down list, and click Go.

c. Select the J2EE component for removal, select Remove from the drop-down

list, and click Go.

Appendix B. Uninstalling IBM Tivoli Monitoring for Transaction Performance components 105

d. Restart the J2EE-instrumented application server.2. On the management agent, change to the following directory:

/etc/tmtp/MA/config.

3. Run the following command to unregister the management agent from the

management server:

./configMa.sh uninstall

Uninstalling the management server

Objective

Uninstall the management server for IBM Tivoli Monitoring for Transaction

Performance.


To uninstall this software you run an uninstall program from the command line.

On Windows, you can also use the Add/Remove Programs tool to uninstall the

management server instead of using the command line.





Before you begin

Uninstall management agents as described in “Uninstalling a management agent”

on page 103.

When you finish

Uninstall the related software.

Procedure


v Command Line: Run the uninstall program from the command line. For

example, on Windows launch the MS-DOS command-line interface.

– UNIX: product_installation_directory/MS/_uninst53/uninstall.bin

– Windows: product_installation_directory\MS\_uninst53\uninstall.exe

—OR—

v (Windows only) Use the Add/Remove Programs tool as follows:




d. Choose IBM Tivoli Monitoring for Transaction Performance

Management Server in the list of available programs.

e. Click Remove to launch the uninstallation program.2. Click Next in the welcome window to display the WebSphere Application

Server information window.

3. Verify the information in this window. Select the check box and enter the

correct information if it is not correct. You must update this window if you

changed the WebSphere Application Server as recommended in the installation

instructions.

4. Click Next to display the database options window.


5. Verify the information on this window and either enter the corrected

information or click Next to accept the discovered information and display the

directory identification window and begin the uninstall.

6. (Windows only) Click OK to restart the computer.


Uninstalling the WebSphere Application Server

Objective

To uninstall the IBM WebSphere Application Server that hosts IBM Tivoli



None


None

Before you begin

Uninstall the management server and management agents as described in the

following topics:

1. “Uninstalling a management agent” on page 103

2. “Uninstalling the management server” on page 106

When you finish

None

Procedure

1. Open the command line. For example, on Windows launch the MS-DOS

command-line interface.

2. Run the following uninstallation executable file that is located in a subdirectory

in the installation path for IBM Tivoli Monitoring for Transaction Performance:

Note: The uninstallation file might be in a different location if you did not

install IBM WebSphere Application Server through the IBM Tivoli

Monitoring for Transaction Performance installation program.

v Windows: installation_image_directory\WAS51\_uninstall\uninstall.exe

Note: Alternatively you can use the Windows Add/Remove Programs tool in

the Windows Control Panel to uninstall WebSphere software.

v UNIX: /opt/websphere/Appserver3. Follow the instructions in the uninstallation program windows. See the

WebSphere documentation for further information.

Uninstalling IBM DB2

Note: This procedure removes IBM DB2 software from a computer. However, it

does not remove configuration information. This configuration information

would prevent you from performing a new installation of the IBM Tivoli

Monitoring for Transaction Performance. See the Background information for

additional information.

When you install IBM Tivoli Monitoring for Transaction Performance you have the

option to install a database for use by the management server. The product


provides Version 8.1 of DB2. (Alternatively you can configure the management

server to use an existing DB2 or Oracle database.) To uninstall the version of DB2

that IBM Tivoli Monitoring for Transaction Performance provides, you must use

the following general process:

1. Consult a DB2 administrator for assistance in removing the databases, users,

and services that might be associated with the DB2 application.

2. Perform the uninstallation procedures that matches your goals and the

operating system on which DB2 is running. These procedures are described in

the DB2 documentation.

Uninstalling the recorder software

Objective

To uninstall the software for the STI Recorder or Generic Windows recorder.

Note: On each management agent on which you play synthetic transactions you

install playback software. To uninstall playback software, see the Remove

Component command in the IBM Tivoli Monitoring for Transaction



Recorder software can be installed on any supported Windows operating system.

So the target computer for this uninstallation procedure might be a computer that

is not a management agent or a management server. The procedure that uninstalls

management agents or the management server does not uninstall any recorder

software.


None

Before you begin

Generic Windows uses Rational Project to play back scripts. Before uninstalling the

Generic Windows Monitoring component from the management agent, you must

unregister and delete the Rational Project using the Rational Administrator Tool.

If you do not unregister and delete Rational Project, project files delete when you

uninstall the Generic Windows component, and the Rational Project created for use

by the Generic Windows component is not unregistered from Rational. A Rational

Project with the same name cannot be created.

When you finish

None

Procedure

Uninstalling STI Recorder:

Note: Instead of the following steps, you can use the Add/Remove Programs

utility in the Windows Control Panel. Select IBM Tivoli Monitoring for

Transaction Performance 5.3, STI Recorder, click Remove, and follow the

instructions for uninstallation.

1. Access the Tivoli folder in the Start menu of the Windows taskbar.

2. Select Uninstall Synthetic Transaction Investigator Recorder to launch the

uninstallation program.

3. Click Next in the welcome window to display the directory window.




Uninstalling Generic Windows recorder: Use the Add/Remove Programs tool as

follows:

1. Access the Start menu in the Windows taskbar.

2. Choose Control Panel in the Settings menu item.

3. Click Add/Remove Programs.

4. Choose Rational Robot in the list of available programs.

5. Click Remove to launch the uninstallation program.

6. Follow the instructions in the windows of the uninstallation program.

Uninstalling language packs

Objective: To remove some or all language packs from the component

(management server, management agent, or STI Recorder) where they are installed.

Background information: You might want to remove language packs when they

are no longer needed or as part of an upgrade. IBM Tivoli Monitoring for

Transaction Performance provides an uninstall program that enables you to remove

some or all language packs from the component (management server, management

agent, or STI Recorder) where they are installed.

When you install language packs, the installation program creates an

uninstall.jar file and places it in the following directory:

install_dir/_uninstlp

where install_dir is the installation directory of the IBM Tivoli Monitoring for

Transaction Performance component (management server, management agent, or

STI Recorder).

You can use the uninstall.jar file to start the uninstall program. Note that there is

no automatic uninstallation for management agents. You must start the uninstall

program from each management agent where you want to remove language packs.

Required authorization role: None

Before you begin: Stop the management server or management agent before

uninstalling language packs for either of these IBM Tivoli Monitoring for

Transaction Performance components. See the IBM Tivoli Monitoring for Transaction

Performance Administrator’s Guide for instructions to stop and starting the

management server and management agents.

When you finish: If you uninstalled language packs for the management server

or a management agent, restart the management server or management agent.

Procedure: Follow these steps to remove one or more language packs for a IBM

Tivoli Monitoring for Transaction Performance component (management server,

management agent, or STI Recorder). If you want to remove language packs for

more than one component on the same computer, repeat the steps for each

component.

1. Enter the following command from the root directory to start the uninstall

program:

java -jar install_dir/_uninstlp/uninstall.jar


where install_dir is the directory where the IBM Tivoli Monitoring for

Transaction Performance component is installed.

2. Click Next on the Welcome screen.

The uninstallation program displays a list of all supported language packs with

checked boxes next to the language packs that are installed on the computer.

3. Click the checked box next to each language pack that you do not want to

remove. The uninstall program removes only the language packs that remain

checked.

4. Click Next to start the uninstallation.

5. When the uninstallation is complete, click Finish to exit.


Appendix C. Performing a silent installation

This chapter describes how to use a command-line interface instead of a graphical

user interface to install IBM Tivoli Monitoring for Transaction Performance.

Installation through the command line without user interaction is called silent

installation.

The installation program references the files it needs on a hard drive in the

network. You can specify the location of these files on the command line.

Alternatively you can create a directory tree that enables the installation program

to automatically find all files that it requires.

This section lists the configuration options for installing IBM Tivoli Monitoring for

Transaction Performance. Set these options when you install the product

components using a command-line interface. Type these options in the command

line or record the options in a response file that you specify using the installation

command.

Note: While it is possible for the management server and management agent to

both operate on a single computer, this configuration is not supported for

production use.

Table 17. Goals for the silent installation of the product

Goals Refer to

1. Install the management server. “Performing a silent installation of the management

server”

2. Install the management agent that hosts the Store and

Forward Service and all other management agents

that you want to connect to the management server.

“Performing a silent installation of a management agent”

on page 114

3. Uninstall software at the end of the product life cycle. Appendix B, “Uninstalling IBM Tivoli Monitoring for

Transaction Performance components,” on page 103

Performing a silent installation of the management server

Objective

To install the management server through a command-line interface without

interaction. By using command-line options you can automate installation of this

product.


You use the silent installation mode to install the product using a command that

specifies a response file. The response file specifies configuration values. A silent

mode installation has the following advantages:

v You can reuse the response file in multiple installations.

Note: If you are performing multiple, simultaneous management agent

installations, you must perform them in groups of no more than 500. If

you try to install more than 500 management agents at the same time

some of the installations might fail.

111

v The response file records configuration data for an installation, so that you can

identify configuration details at a later date.

Error messages: The installation program logs a message when an error condition

exists, such as missing prerequisite software. Each message is preceded by a

″BWM″ message identifier (for example, BWMIS0103E). The IBM Tivoli Monitoring

for Transaction Performance Problem Determination Guide contains a list of all

installation error messages, ordered by message identifier, with instructions on

what corrective action to continue the installation.

Default installation directories: By default, the installation program places the

product in one of the following directory paths, depending on the operating

system of the host computer for the management server.

v Windows: C:\Program Files\ibm\tivoli\MS

v UNIX: /opt/ibm/Tivoli/MS

The management server is responsible for deploying software to the management

agents of an IBM Tivoli Monitoring for Transaction Performance system. These

software images are stored in the same directory path as the management server

software. For example, the software images the STI Recorder, and for the available

monitoring applications are stored in the management server’s directory path. You

must also install language packs in this directory path, as described in Chapter 11,

“Installing a language pack,” on page 85.





Before you begin

Prepare a response file using the options listed in “Lists of settings and options”

on page 118. See “Requirements for a response file” on page 117 for more

information on building a response file.

Obtain access to the product installation images. See, Chapter 1, “Installation

overview,” on page 1 for information.

If you want to configure the management server to use an existing Oracle or DB2

database, prepare the database as follows:

v For an existing DB2 database: prepare the database as described “Preparing an

existing DB2 database” on page 17.

v For an existing Oracle database: prepare the database as described in

“Guidelines for preparing an Oracle database” on page 21.

If you do not want to use an existing database, install the version of DB2 that

comes with IBM Tivoli Monitoring for Transaction Performance as described in this

procedure so that none of these preparatory actions are required.

Note: HP-UX and Solaris: Change all recommended kernel configuration

parameters set as formulas to integer values. You must reboot your system

for these changes to take affect.


When you finish

Create management agents as described in “Performing a silent installation of a

management agent” on page 114.

Procedure

1. Log on to the computer on which you want to install the management server.

2. Use the command-line interface to access the directory that contains the

installation executable file.

installation_image_directory/ITMTP_WTP_1/disk1

3. Type the installation command and press Enter.

Additional information: See, “Syntax of the installation command” on page 115

for detailed information on the proper command syntax. See, “Lists of settings

and options” on page 118 for a complete list of installation options.

The following table provides example management server installation commands.

Table 18. Methods for specifying options in an installation command

Method Description/Syntax example

Command-line *

Description of Method: Type all options in the command line. Use the options that correspond to

the type of installation you want, management server, management agent, or synthetic transaction

recorder. The following syntax examples show options relevant to installation of a management

server. Options for all types of installation are listed in “Lists of settings and options” on page 118.

Syntax example for Windows (installing a management server):

installer_name.exe -silent -is:javaconsole -P ms.installLocation=

"D:\Tivoli\MS" -W wasService.user="username" -W wasService.password="password"

-W wasService.cellName="cellname" -W wasService.soapConnectorPort="8880"

-W wasService.nodeName="nodename" -W wasService.serverName="srvrname"

-W databaseChoice.installDb2="true" -W db2DasUser.das_username="adminusr"

-W db2DasUser.das_password="password" -W db2InstanceUser.inst_username="instuser"

-W db2InstanceUser.inst_password="password" -G replaceExistingResponse="yesToAll"

-G replaceNewerResponse="yesToAll" -G removeExistingResponse="yesToAll"

-G removeModifiedResponse="yesToAll"

-P msConfig.db2CdromDir="DB2_install_image_location"

Syntax example for UNIX-based systems (installing a management server):

./installer_name.bin -silent -is:javaconsole -P ms.installLocation="/opt/MS"

-W wasService.user="username" -W wasService.password="password" -W

wasService.cellName="cellname" -W wasService.soapConnectorPort="8880"

-W wasService.nodeName="nodename" -W wasService.serverName="srvrname"

-W databaseChoice.installDb2="true" -W db2DasUser.createUser="true"

-W db2DasUser.das_username="username" -W db2DasUser.das_password="password"

-W db2DasUser.das_groupname="grpname" -W db2DasUser.das_home_dir="/home/db2admin"

-W db2FenceUser.createUser="true" -W db2FenceUser.fen_username="fenceusr"

-W db2FenceUser.fen_password="password" -W db2FenceUser.fen_groupname="inst_grp"

-W db2FenceUser.fen_home_dir="/home/db2fenc1" -W db2InstanceUser.createUser="true"

-W db2InstanceUser.inst_InstanceName="instname" -W db2InstanceUser.inst_username="instuser"

-W db2InstanceUser.inst_password="password"

-W db2instanceuser.inst_groupname="name" -W db2instanceuser.inst_home_dir="home_dir"

-G replaceExistingResponse="yesToAll" -G replaceNewerResponse="yesToAll"

-G removeExistingResponse="yesToAll" G removeModifiedResponse="yesToAll"

-P msConfig.db2CdromDir="DB2_install_image_location"

Appendix C. Performing a silent installation 113

Table 18. Methods for specifying options in an installation command (continued)

Method Description/Syntax example

Command-line with

option file *

Description of Method: Use the -options flag to call a text file that specifies most options.

See “Requirements for a response file” on page 117 for more information on building an option file.

As the following examples show, you type the flags -silent, -options, and any -is items in the

command line, and not in the option file.

Syntax example for Windows:

installer_name.exe -silent -is:javaconsole -is:silent -options setup.opt

Syntax example for UNIX-based systems:

./installer_name.bin -silent -is:javaconsole -is:silent -options setup.opt

* Each example command includes the following three -is (installer settings) options:

v -silent — Hides the graphical user interface for installation.

Note: You must use this option to enable a command-line installation as described in this procedure.

v -is:javaconsole — This option enables standard output to the console. Otherwise errors, stack traces, and other

messages are hidden.

v -is:silent — This option hides the installation splash screen.

You must type any -is strings in the command line. You cannot specify -is settings in an options file. See

“Installation program settings” on page 119 for descriptions of the -is options.

Performing a silent installation of a management agent

Objective

To install the management agent through a command-line interface using an option

file to specify configuration values. You can also enable the management agent that

you install to host the Store and Forward Service, as described in this procedure.


You use the silent installation mode to install the product using a command that

specifies a response file. The response file specifies configuration values. A silent

mode installation has the following advantages:

v You can reuse the response file in multiple installations.


installations, you must perform them in groups of no more than 500. If

you try to install more than 500 management agents at the same time

some of the installations might fail.

v The response file records configuration data for an installation, so that you can


Error messages: The installation program logs a message when an error condition

exists, such as missing prerequisite software. Each message is preceded by a

″BWM″ message identifier (for example, BWMIS0103E). The IBM Tivoli Monitoring

for Transaction Performance Problem Determination Guide contains a list of all

installation error messages, ordered by message identifier, with instructions on

what corrective action to continue the installation.

The Store and Forward Service is software on a dedicated management agent that

acts as a proxy to channel IBM Tivoli Monitoring for Transaction Performance

monitoring data across firewalls. The Store and Forward agent has the following

characteristics:


v The Store and Forward Service is required for management agents that are

separated from the management server by a firewall.

v It performs no communication or processing of management agent data. It only

relays data.





Before you begin

Work with an enterprise system administrator to register the server that hosts the

Store and Forward Service as follows:

v List the server in the Domain Name System (DNS).

v Enable communications from the server to traverse firewalls.

When you finish

Create other management agents that gather transaction performance data for the

enterprise, as described in Chapter 6, “Installing a management agent,” on page 51.

Procedure


installations, you must perform them in groups of no more than 500. If you

try to install more than 500 management agents at the same time some of

the installations might fail.


2. Use the command-line interface to access the directory that contains the

installation executable file.

installation_directory/ITMTP_WTP_3/MA

3. Type the installation command and press Enter.

Additional information: See, “Syntax of the installation command” for detailed

information on the proper command syntax. See, “Lists of settings and options”

on page 118 for a complete list of installation options.

Syntax of the installation command

This section describes the syntax of the installation command, including

instructions for calling a response file that specifies configuration options for the

component that you are installing.

Basic syntax

This section describes the basic syntax of the installation command:

install_executable [installer_setting...] -silent [config_option...] \

[-options option_file]

where:

install_executable

Specifies the installation executable file for the system on which you are

installing the product. You can specify this option only in the command

line, not in a response file. The following executable files are available:


For a management server:








For management agents:








v OS/400: install-OS400.sh

For Store and Forward agents:

v Windows: setup_SnF_w32.exe

v AIX: setup_SnF_aix.bin

v Solaris: setup_SnF_sol.bin

v Linux xSeries: setup_SnF_lin.bin

v Linux pSeries: setup_SnF_linppc.bin

v Linux 390: setup_SnF_lin390.bin

v HP-UX: setup_SnF_hp11.bin

installer_setting

Specifies -is settings that determine the behavior of the installer. You can

specify this option only in the command line, not in a response file. See

“Installation program settings” on page 119 for a complete list.

-silent

Specifies a silent installation. You can specify this option only in the

command line, not in a response file. When you omit this parameter, the

installation wizard launches and prompts you for configuration details.

config_option

Specifies one or more data options not included in the response file. Use

either of the following methods to apply a configuration option:

v Enter a configuration option on the command line.

v Enter a configuration option in a response file.

-options

Causes the installer to obtain configuration data from the response file that

you specify in the option_file variable. You can specify this option only in

the command line, not in a response file.

option_file

Specifies a response file. The response file is a plain text file that contains


one or more data options, each listed on a separate line. For detailed

information on a response file, see “Requirements for a response file.”

Syntax of configuration options

This section describes the syntax for configuration options for both the

management server and management agent installations.

You can use configuration options in the command line or in a response file. There

are three flags for configurations options, -P, -W, and -G:

v The -P and -W options specify information for each entity involved in an

installation, such as the management server, database servers, Web servers, and

management agents. A -P option (product option) adds files or configuration

features to the system. A -W option (wizard panel option) specifies data needed

by the installation program.

v The -G options specify responses to pop-up confirmation windows that might be

displayed when the install or uninstall program is about to install or remove

files or directories.

The configuration options accept the following parameters:

-P entity_ID.dataItem="value"

-W entity_ID.dataItem="value"

-G globalResponseType="value"

where:

entity_ID

Identifies an entity involved in an installation, such as a management

server.

dataItem

Name of an attribute of an entity involved in an installation, such as the

installation path or the communications port.

value Specifies the value for an attribute of an entity involved in an installation,

such as the specific path C:\Program Files\IBM\tivoli\MS. For global

response (-G) options, value specifies one of the following actions for a

specific type of response: yesToAll, yes, noToAll, or no.

globalResponseType

Name of an automatic action performed by the installer in response to a

prompt. This field is always associated with the -G flags.

Requirements for a response file

Notes:

1. Response files must not contain blank lines or comment lines.

2. There are sample response files with your installation images.

installation_image_directory/ITMTP_WTP_1/disk1/response_files

3. When you use a response file to specify options, you can type additional

options in the command line.

This is general information and applies to any response file you create, either for a

management server or a management agent. A response file must have the

following characteristics:

v Contains the data options for your installation or uninstallation, which are listed

in “Lists of settings and options” on page 118:


– The names of the data options must follow the uppercase and lowercase

conventions shown in “Lists of settings and options,” as they are case

sensitive.

– Each data option must exist on a separate line.

– The data options can be sorted in any order.v Does not contain the -silent flag, the -options flag, or -is. See “Syntax of the

installation command” on page 115 for descriptions of these elements.

v Contains no comment lines or blank lines.

v Is saved in plain text format with a .opt suffix.

When to use a response file

You might want to build a response file for a silent installation or uninstallation for

the following reasons:

v You can reuse the response file for multiple installations or uninstallations.

v The response file preserves configuration data for an installation, so that you can


When not to use a response file

This section lists some reasons to manually type options, instead of using a

response file:

v Unique options: To reuse the response file in multiple installations, but some of

the options are unique to each installation. Manually type the unique options in

the command line during each installation. The response file supplies the values

that are valid for multiple target computers.

v Password protection: To safeguard the password by manually entering it during

each installation. If you record the password in the option (.opt) file, the

password is unencrypted and visible to anyone who opens the file.

The following example sets the password on the command line and relies on an

.opt file to provide all other configuration details:

setup_MA_w32 -silent -W serviceUser.password="tivoli" -options ma.opt

Lists of settings and options

The following topics provide lists of the available settings and options and

descriptions:

v “Options for monitoring installation messages”

v “Installation program settings” on page 119

v “Configuration options for the management server” on page 121

v “Configuration options for the management agent” on page 129

Options for monitoring installation messages

The following two configuration options in IBM Tivoli Monitoring for Transaction

Performance control the display or logging of installation messages. These options

can help you monitor and debug all phases of an installation.

v -W logSettings.consoleOut="true | false" specifies whether to display

messages issued by installation, upgrade, or uninstall program on the console. If

you use this option with a native launcher, it must be used in combination with

the -is:javaconsole option.

v -W logSettings.logLevel="trace_level" specifies the level of tracing for the

installation log files. The amount of tracing for a specific level includes the


messages for that level and all messages at a higher severity. For example, if you

choose the "WARNING" trace level, the following messages are logged: "WARNING",

"ERROR", and "FATAL". During the installation maximum logging is turned on by

default. Table 19 lists and describes the available settings. Access the installation

log files in the following path:

– UNIX: /var/ibm/tivoli/common/BWM/logs

– Windows: C:\Program Files\ibm\tivoli\common\BWM\logs

Table 19. Trace level settings for installation log files

Feature or entity that

the option configures

Option String / Description

Trace levels -W logSettings.level="FATAL"

Log fatal messages. A fatal message reports an error from which the program cannot

recover. A fatal message is the most severe message.

-W logSettings.level="ERROR"

Log error messages. An error message reports a serious failure. An error message is less

severe than a fatal message.

-W logSettings.level="WARNING"

Log warning messages. A warning message reports that an abnormal condition has

occurred. The condition might or might not require the user to take action.

-W logSettings.level="INFO"

Log information messages. An information message indicates a condition that is worth

noting but does not require the user to take action.

-W logSettings.level="DEBUG_MIN"

Log debug messages that provide minimal detail. DEBUG_MIN is appropriate for a software

trace that is always running. It provides some information about the program state with

only minimal impact to performance. DEBUG_MIN is the default setting for installation log

files.

-W logSettings.level="DEBUG_MID"

Log debug messages that provide a medium amount of detail. The DEBUG_MID setting

produces a level of detail between DEBUG_MIN and DEBUG_MAX.

-W logSettings.level="DEBUG_MAX"

Log debug messages that provide the most detail about program execution. Program

performance is usually not an issue when debugging in this mode.

-W logSettings.level="ALL"

Enable all message logging.

These options are also mentioned briefly in the lists of configuration options for

the management server, management agents, and other components. See “Syntax

of the installation command” on page 115 for information on overall command

syntax.

Installation program settings

This section describes the optional installation program settings, that you apply

using the -is flag in a command. These settings apply to any installation or

uninstallation process.

When you use -is flags, you must type them on the command line, not in a

response file. See “Syntax of the installation command” on page 115 for

information on overall command syntax. Use the following syntax within -is flags:

-is:entity_ID

-is:entity_ID name


where:

entity_ID

Identifies one of the following InstallShield settings: tempdir, log,

javaconsole, silent, or javahome. These settings are described later in this

section.

name Name of setting, such as the directory path or file name.

Table 20. Product options for installing a management server



-is option String / Description

Temporary directory -is:tempdir temp_dir

Specifies a directory for storing temporary files. If the directory you specify does not exist,

or is not a directory, the installation, upgrade, or uninstall program writes temporary files

to the default temporary directory. No error message is issued.

Note: AIX: If you are installing IBM WebSphere Application Server, Version 5.1 from the

IBM Tivoli Monitoring for Transaction Performance, Version 5.3 CD-ROMS on AIX you

must use the default temporary directory.

Error log file -is:log log_file_name

Specifies the name of a file for logging error messages issued by InstallShield during

launcher initialization. You can specify a fully qualified or a relative path name. If you

specify only the file name, the program creates the file in the current directory. This option

is especially useful for determining problems when the installation, upgrade, or uninstall

program fails just after starting.

Java console -is:javaconsole

Specifies that error messages are to be displayed to a console window as well as logged.

The displayed error messages are not necessarily the same as the error messages logged by

the -is:log option.

The following two IBM Tivoli Monitoring for Transaction Performance options are related

to the -is options because they enable you to control aspects of logging and console output:

v -W logSettings.loglevel="trace_level" specifies a trace level setting for the installation

log files. Access the installation log files in the following path:

– On UNIX-based systems: /var/ibm/tivoli/common/BWM/logs

– On Windows systems: C:\Program Files\ibm\tivoli\common\BWM\logs

v -W logSettings.consoleOut="true | false" specifies whether to display messages

issued by installation, upgrade, or uninstall program on the console. If you use this

option with an installation program file, it must be used in combination with the

-is:javaconsole option.

See the IBM Tivoli Monitoring for Transaction Performance Problem Determination Guide for a

comprehensive description of logging, troubleshooting, and other options you can enable.

Message window

control

-is:silent

Suppresses the InstallShield Wizard message window that is displayed at the start of an

installation, upgrade, or uninstallation. The -silent option, used for silent installations or

uninstallations, does not suppress this window.


Configuration options for the management server

This section lists options for configuration of a management server.

Note: The Syntax column in this table includes default values or platform-specific

examples. Modify these settings as required to match your system

configuration. For example, specify different key store files, if you do not

want to use the key store files that come with IBM Tivoli Monitoring for


Table 21. Configuration options for the management server

Option Syntax

Installation directory (Use this

option if you want to change

the default installation

directory path.)

-P ms.installLocation="C:\Program Files\IBM\tivoli\MA"]

SSL configuration <-W sslConfig.copyKeyFiles="[true | false]

<-W sslConfig.sslValue="[true | false]">

<-W sslConfig.keyFilename="C:\ms.jks">

<-W sslConfig.keyFilenamePassword="changeit">

<-W sslConfig.trustFilename="C:\ms.jks">

<-W sslConfig.trustFilenamePassword="changeit">

<-W sslConfig.portWithoutAuth="9081">

<-W sslConfig.portManagementServer="9445">

<-W sslConfig.portWithAuth="9446">

Web Application Server

configuration

<-W wasService.user="username">

<-W wasService.password="password">

<-W wasService.cellName="cellname">

<-W wasService.soapConnectorPort="8880">

<-W wasService.adminconsoleport="9090">

<-W wasService.nodeName="nodename">

<-W wasService.serverName="srvrname">

<-W wasService.wasSslEnabled="[true | false]">

-W wasService.wasKeyFilename=

"/opt/WebSphere/AppServer/etc/DummyClientKeyFile.jks"

-W wasService.wasKeyFilenamePassword="WebAS"

-W wasService.wasTrustFilename=

"/opt/WebSphere/AppServer/etc/DummyClientTrustFile.jks"

-W wasService.wasTrustFilenamePassword="WebAS"

Note: The following requirements apply to the admin, fence, and instance users that you define for DB2:

v On Windows, you must create a new user. You cannot use a preexisting user.

v On UNIX-based systems, you can create a new user or use a preexisting user.

v When you create a new user on UNIX-based systems, you must define a group name and home directory for the

user account.

Database settings: when you

use an existing DB2 database.

<-W dbConfig.databasename="database_name">

<-W dbConfig.database_type="DB2">

<-W dbConfig.user="adminusr">

<-W dbConfig.password="password">

<-W dbConfig.jdbcPath="C:Program Files\sqllib\java12">


use an existing Oracle

database.

<-W dbConfig.sid=NBN>

<-W dbConfig.database_type="ORACLE">

<-W dbConfig.port="1521">

<-W dbConfig.user="adminusr">


<-W dbConfig.server="fully_qualified_host_name | ip_address">


Table 21. Configuration options for the management server (continued)

Option Syntax


are installing new DB2

software on Windows.

<-W databaseChoice.installDb2="true">

<-W db2DasUser.das_username="adminusr">

<-W db2DasUser.das_password="password">

<-W db2InstanceUser.inst_username="instuser">

<-W db2InstanceUser.inst_password="password">


are installing new DB2

software on UNIX-based

systems.

<-W databaseChoice.installDb2="[true]">

<-W db2DasUser.createUser="[true | false]">

<-W db2DasUser.das_username="username">


<-W db2DasUser.das_groupname="grpname">

<-W db2DasUser.das_home_dir="/home/db2admin">

<-W db2FenceUser.createUser="[true | false]">

<-W db2FenceUser.fen_username="fenceusr">

<-W db2FenceUser.fen_password="password">

<-W db2FenceUser.fen_groupname="inst_grp">

<-W db2FenceUser.fen_home_dir="/home/db2fenc1">

<-W db2InstanceUser.createUser="[true | false]">

<-W db2InstanceUser.inst_InstanceName="instname">

<-W db2InstanceUser.inst_username="instuser">


<-W db2InstanceUser.inst_groupname="name">

<-W db2InstanceUser.inst_home_dir="home_dir">

DB2 installation image location -P msConfig.db2CdromDir="<DB2_install_image_location>"

IBM WebSphere Application

Server installation image

location

-P msConfig.wasCdromDir="<WAS_install_image_location>"

Global response settings <-G replaceExistingResponse="yesToAll | yes | noToAll | no">

<-G replaceNewerResponse="yesToAll | yes | noToAll | no">

<-G removeExistingResponse="yesToAll | yes | noToAll | no">

<-G removeModifiedResponse="yesToAll | yes | noToAll | no">

Log settings <-W logSettings.level="trace_level">

<-W logSettings.consoleOut="true | false">

-G configuration options

The -G options specify responses to pop-up confirmation windows that might be

displayed when the install or uninstall program is about to install or remove files

or directories. The following example shows the -G option that suppresses all

windows with this message, so that no confirmation windows are displayed

during a silent installation:

-G replaceExistingResponse="yesToAll"


Table 22. Configuration options for global responses


the option configure


Automatic responses -G replaceExistingResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to replace a file that already exists.

-G replaceNewerResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to replace an existing file if that file is newer than the file being

installed.

-G removeExistingResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to remove an existing file.

-G removeModifiedResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to remove a file that has been modified since installation.

-P configuration option

A -P option (product option) adds files or configuration features to the system.

Table 23. Product option for management server




DB2 installation image

location

-P msConfig.db2CdromDir="<DB2_install_image_location>"

Specifies the location of the DB2 installation image. This must be specified to run the

embedded installation of DB2.

IBM WebSphere

Application Server

installation image

location

-P msConfig.wasCdromDir="<WAS_install_image_location>"

Specifies the location of the WebSphere Application Server installation image. This must

be specified to run the embedded installation of WebSphere Application Server .

Location of installation -P ms.installLocation="C:\Program Files\IBM\tivoli\MS"

(Optional) Specifies the installation directory for the management server. If you do not

specify this option, the installation program uses the default directory path. The preceding

example is Windows-based.

-W configuration options

A -W option (wizard panel option) specifies data needed by the installation

program.


Table 24. Wizard-related options for the management server




SSL settings on the

management server

<-W sslConfig.sslValue="[true | false]">

Enables SSL authentication for communications in the product environment when you

specify true.

<-W sslConfig.copyKeyFiles="[true | false]">

Copies the key and trust files to a local directory when you specify true. This enables you

to access the file if you lose network connectivity or have to remove the installation

CD-ROM from the drive.

<-W sslConfig.keyFilename="C:\ms.jks">

Specifies the location of the private key file that enables SSL communication. The default

.jks file is a self-signed certificate that can enable SSL communications. You should replace

this file with one that meets the policies and practices of your company regarding SSL

communications.

Note: The .jks files are provided for test purposes only and expire relatively soon. This

files are not recommended for use in a production environment.

<-W sslConfig.keyFilenamePassword="changeit">

Specifies the default password of the key file. You should change this password to a new,

secure value.

<-W sslConfig.trustFilename="C:\ms.jks">

Specifies the location of an optional public key file, called a Trust File, that enables SSL

handshaking. By storing the public key separately from the private key you enable a

higher degree of security because you can store the private key file in a less accessible,

more secure location on the server. The default .jks file is a self-signed certificate that can

enable SSL communications. You should replace this file with one that meets the policies

and practices of your company regarding SSL communications.

Note: The .jks files are provided for test purposes only and expire relatively soon. This

files are not recommended for use in a production environment.

<-W sslConfig.trustFilenamePassword="changeit">

Specifies the default password of the key file. You should change this password to a new,

secure value.

<-W sslConfig.portWithoutAuth="9081">

Specifies the port for product communications when SSL authentication is not enabled. The

default is 9081.

<-W sslConfig.portManagementServer="9445">

Specifies the port for accessing the user console. The default for SSL is 9445. The default

for non-SSL is 9082.

<-W sslConfig.portWithAuth="9446">

Specifies the port for product communications when SSL authentication is enabled. The

default is 9446.


Table 24. Wizard-related options for the management server (continued)




Web Application Server

configuration

<-W wasService.user="username">

Specifies the name of a user in the WebSphere Application Server environment.

<-W wasService.password="password">

Specifies the password of a user in the WebSphere Application Server environment.

<-W wasService.cellName="cellname">

When you are using an existing installation of WebSphere software, you use this flag to

specify the name of a cell in a WebSphere Application Server distributed network. A cell is

a configuration concept that allows WebSphere administrators to logically associate nodes

with each another. You can use any of the existing cell names that are defined in the cell

directory. For example, the cell directory is located in the following path on Windows:

\WAS_BASEDIR\config\cells

<-W wasService.soapConnectorPort="8880">


specify the connector port that the WebSphere Application Server to send commands using

the Simple Object Access Protocol (SOAP). The default is 8880.

<-W wasService.nodeName="nodename">


specify the name of a computer that runs an application server and an administrative

server. Normally, the default node name is the short host name. For example, on a

computer named topshelf the node name could be topshelf.

<-W wasService.serverName="srvrname">


specify the name of the WebSphere Application Server where IBM Tivoli Monitoring for

Transaction Performance runs. In a simple installation this server might be named server1.

<-W wasService.adminconsoleport="9090">

When you use the installation of WebSphere Application Server that comes with IBM

Tivoli Monitoring for Transaction Performance you use this flag to specify the port used

by the WebSphere Administrative Console. The default is 9090.

Note: On AIX, Version 5.x, port 9090 is reserved for Websm.

Do not use the default if port 9090 is assigned to another service, such as Websm on AIX,

Version 5.x. Alternatively, an AIX administrator can disable WebSM using the following

command in the /usr/websm/bin directory of the WebSM installation:

wsmserver -disable

<-W wasService.wasSslEnabled="[true | false]">

When you are using an existing installation of WebSphere software for which Global

Security is enabled, you use this flag to enable SSL authentication for communications, by

specifying true.

WebSphere SSL Key

and Trust Files

-W wasService.wasKeyFilename=

"/opt/WebSphere/AppServer/etc/DummyClientKeyFile.jks"

-W wasService.wasKeyFilenamePassword="WebAS"

-W wasService.wasTrustFilename=

"/opt/WebSphere/AppServer/etc/DummyClientTrustFile.jks"

-W wasService.wasTrustFilenamePassword="WebAS"

Specifies the names and passwords for the SSL key files that enable SSL communications.

These files are used when you set the value of <-W wasService.wasSslEnabled="[true |

false]"> to true.






Basic database settings:

when you use Oracle or

DB2.

<-W dbConfig.database_type="db_type">

Specifies the type of database you use for the product. The choices are Oracle or DB2.

<-W dbConfig.user="database_user">

Specifies the user ID for the Oracle table space or DB2 database to be used for the

management repository.


Specifies the password of the dbConfig.user that you specify.

DB2 database settings:

when you use an

existing DB2 database.

<-W dbConfig.databasename="database_name">

Specifies the alias used on the management server to refer to the DB2 database for the

management repository.

<-W dbConfig.jdbcPath="C:Program Files\sqllib\java12">

Specifies the full path to the required Java DataBase Connectivity (JDBC) files. For

example, these files might be located in the following path: c:\Program

Files\IBM\SQLLIB\java12

Oracle database

settings: when you use

an existing Oracle

database.

<-W dbConfig.sid=NBN>

Specifies the Oracle system identifier number.

<-W dbConfig.server="fully_qualified_host_name | ip_address">

Specifies the fully qualified host name or the IP address of the host computer for the

Oracle database which contains table space for the management repository. For example,

servername.it.company.com shows typical syntax for fully qualified host name.

<-W dbConfig.port="1521">

The default port is 1521.

DB2 database settings:

when you are installing

new DB2 software on

Windows.

<-W databaseChoice.installDb2="true | false">

Enables installation of DB2 when you specify true.

<-W db2DasUser.das_username="adminusr"> (name that you provide)

Specifies the name of a user in the DB2 environment.


Specifies the password of a user in the DB2 environment.

<-W db2InstanceUser.inst_username="instuser"> (name that you provide)

Specifies the name of a user of the DB2 Instance.


Specifies the password of a user of the DB2 Instance.






Database settings:

when you are installing

new DB2 software on

UNIX-based systems.

<-W databaseChoice.installDb2="[true | false]">

Enables installation of DB2 when you specify true.

<-W db2DasUser.createUser="[true | false]">

Enables creation of a DB2 Administrative user account when you specify true.

<-W db2DasUser.das_username="username"> (name that you provide)

Specifies the name of a DB2 Administrative user account.


Specifies the password of the DB2 Administrative user account.

<-W db2DasUser.das_groupname="grpname"> (name that you provide)

Specifies the group name of the DB2 Administrative user account.

<-W db2DasUser.das_home_dir="/home/db2admin">

Specifies the home directory of the DB2 Administrative user account.

<-W db2FenceUser.createUser="[true | false]">

(UNIX only) Enables creation of a user account to perform fenced operations when you

specify true.

<-W db2FenceUser.fen_username="fenceusr"> (name that you provide)

(UNIX only) Specifies the name of a user account that is enabled to perform fenced

operations.

<-W db2FenceUser.fen_password="password">

(UNIX only) Specifies the password of a user account that is enabled to perform fenced

operations.

<-W db2FenceUser.fen_groupname="inst_grp">

(UNIX only) Specifies the group name for an instance of the user account that you create

for fenced operations.

<-W db2FenceUser.fen_home_dir="/home/db2fenc1">

(UNIX only) Specifies the home directory for the instance of the user account that you

create for fenced operations.

<-W db2InstanceUser.createUser="[true | false]">

Enables creation of an instance when you specify true.

<-W db2InstanceUser.inst_InstanceName="instname"> (name that you provide)

Specifies the name of an instance.

<-W db2InstanceUser.inst_username="instuser"> (name that you provide)

Specifies the name of an instance user.


Specifies the password of an instance user.

<-W db2InstanceUser.inst_groupname="name">

Specifies the group name of an instance user.

<-W db2InstanceUser.inst_home_dir="home_dir">

Specifies the home directory of an instance user.






Message generation -W logSettings.consoleOut="true | false"

Specifies whether to display messages issued by installation, upgrade, or uninstallation

program on the console.

-W logSettings.loglevel="trace_level"

Specifies the trace level setting for the installation log files. This log file lists error,

warning, informational, and debug messages that are issued by the installation program.

See “Options for monitoring installation messages” on page 118 for a complete list of trace

level settings. Access the installation log files in the following path:

v On UNIX-based systems: /var/ibm/tivoli/common/BWM/logs

v On Windows systems: C:\Program Files\ibm\tivoli\common\BWM\logs


Configuration options for the management agent

Table 25 lists options for configuration of a management agent.

Note: The Syntax column in this table includes default values or platform-specific

examples. Modify these settings as required to match your system

configuration. For example, specify different key store files, if you do not

want the use the key store files that come with IBM Tivoli Monitoring for


Table 25. Configuration options for the management agent

Option Syntax

Installation directory for the

Store and Forward Service.

(Use this option if you want to

change the default installation

directory path.)

<-P snf.installLocation="C:\Program Files\IBM\tivoli\SnF">

Settings for a management

agent that hosts the Store and

Forward Service.

<-W SnFAgentPanel.protocolHostPortUri="[http | https]:

//fully_qualified_host_name_of_management_server:9446">

<-W SnFAgentPanel.mask="@(IP_address01,IP_address02)">

<-W SnFAgentPanel.msuserName="user_name">

<-W SnFAgentPanel.mspassword="password">

<-W kdbInfo.kdbKeyRing="c:/temp/key.kdb">

<-W kdbInfo.kdbPasswdStashed="c:/temp/key.sth">

<-W kdbInfo.copyToConfig="[true | false]">

<-W msConnection.hostName="fully_qualified_host_name">

<-W msConnection.sslValue="[true | false]">

<-W msConnection.portNumber="443"> (This is the default value.)

<-W msConnection.maPort="1976"> (This is the default value.)

<-W msConnection.epKeyStore="c:/temp/dmzagent.jks">

<-W msConnection.epKeyPass="changeit">

<-W msConnection.maName="maname"> (Optional)

<-W serviceUser.user="TMTPAgent"> (Windows only)

<-W serviceUser.password="tivoli"> (Windows only)

WebSphere Caching Proxy

installation image location

<-P snfConfig.wcpCdromDir="WCP_install_image_location">

Installation directory for

management agents that do

not host the Store and Forward

Service. (Use this option if you

do not want to use the default

installation directory path.)

<-P ma.installLocation="C:\Program Files\IBM\tivoli\MA">

Settings for management

agents that do not host the

Store and Forward Service.


<-W msConnection.userName="tmtpuser">

<-W msConnection.password="tmtppassword">


<-W msConnection.portNumber="9446"

<-W msConnection.maPort="1976"> (This is the default value.)

<-W msConnection.epKeyStore="c:/tmtp/agent.jks">


<-W serviceUser.user="TMTPAgent"> (Windows only)

<-W serviceUser.password="tivoli"> (Windows only)


Table 25. Configuration options for the management agent (continued)

Option Syntax

Global response settings <-G replaceExistingResponse="yesToAll | yes | noToAll | no">

<-G replaceNewerResponse="yesToAll | yes | noToAll | no">

<-G removeExistingResponse="yesToAll | yes | noToAll | no">

<-G removeModifiedResponse="yesToAll | yes | noToAll | no">

Log settings [-W logSettings.level="trace_level"]

[-W logSettings.consoleOut="true | false"]

-G configuration options

The -G options specify responses to pop-up confirmation windows that might be

displayed when the install or uninstall program is about to install or remove files

or directories. The following example shows the -G option that suppresses all

windows with this message, so that no confirmation windows are displayed

during a silent installation:

-G replaceExistingResponse="yesToAll"

Table 26. Configuration options for global responses


the option configure


Automatic responses -G replaceExistingResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to replace a file that already exists.

-G replaceNewerResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to replace an existing file if that file is newer than the file being

installed.

-G removeExistingResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to remove an existing file.

-G removeModifiedResponse="yesToAll | yes | noToAll | no"

Specifies whether you want to remove a file that has been modified since installation.

-P configuration option

A -P option (product option) adds files or configuration features to the system.

Table 27. Product option for management agents

Feature or entity that the

option configures



the Store and Forward

Service.

<-P snf.installLocation="C:\Program Files\IBM\tivoli\SnF">

[Windows default shown here.]

Specifies the installation directory for the management agent that hosts the Store and

Forward Service. If you do not specify this option, the installation program uses the

default directory path.


management agents that

do not host the Store and

Forward Service.

<-P ma.installLocation="C:\Program Files\IBM\tivoli\MA">

[Windows default shown here.]

Specifies the installation directory for the management agent. If you do not specify this

option, the installation program uses the default directory path.

WebSphere Caching Proxy

installation image location

<-P snfConfig.wcpCdromDir="WCP_install_image_location">

Specifies the location of the installation image for WebSphere Caching Proxy, Version

5.1.


-W configuration options

A -W option (wizard panel option) specifies data needed by the installation

program.

Table 28. Wizard-related options for the management agent

Feature or entity

that the option

configures


Settings for a

management agent

that hosts the Store

and Forward

Service.

<-W SnFAgentPanel.protocolHostPortUri="[http | https]:

//fully_qualified_host_name:9446">

Specifies the fully qualified name of the host computer for the management server.

<-W SnFAgentPanel.mask="@(IP_address01,IP_address01)">

Specifies the mask that filters IP addresses.

<-W SnFAgentPanel.msuserName="user_name">

Note: Store and Forward agent installations only.Specifies a valid user name on the

management server.

<-W SnFAgentPanel.mspassword="password">

Note: Store and Forward agent installations only.Specifies the password that corresponds to the

user name.

<-W kdbInfo.kdbKeyRing="c:/temp/key.kdb">

Specifies the SSL key file that enables SSL handshaking.

<-W kdbInfo.kdbPasswdStashed="c:/temp/key.sth">

Specifies the stash file for the SSL key file

<-W kdbInfo.copyToConfig="[true | false]">

Specifies whether to copy files to a configuration directory.


(Example: server01.domain.ibm.com")>

Specifies the fully qualified name of the host computer that hosts the Store and Forward

Service (local computer).


Specifies enablement (true) or disabling (false) of SSL authentication.

<-W msConnection.portNumber="443" (This is the default value.)

Specifies the port number for Store and Forward communications.


Copies the key and trust files to a local directory when you specify true. This enables you to

access the file if you lose network connectivity or have to remove the installation CD-ROM

from the drive.

<-W msConnection.epKeyStore="c:\temp\dmzagent.jks">

Specifies the SSL key file that enables communication with management agents located in the

DMZ.

Note: The .jks files are provided for test purposes only and expire relatively soon. This files

are not recommended for use in a production environment.


Specifies the password for the SSL key file.

<-W msConnection.maPort="1976">

Specifies the port that is used by the management server to communicate with this

management agent.

<-W serviceUser.user="TMTPAgent">

Specifies the user name for the IBM Tivoli Monitoring for Transaction Performance agent

service. (Windows only)

<-W serviceUser.password="tivoli">

Specifies the password that corresponds to the user. (Windows only)


Table 28. Wizard-related options for the management agent (continued)

Feature or entity

that the option

configures


Settings for

management

agents that do not

host the Store and

Forward Service.


Specifies the fully qualified name of the host computer for the management server or the Store

and Forward Service.

<-W msConnection.userName="tmtpuser">

Specifies the IBM Tivoli Monitoring for Transaction Performance user name on the

management server.

<-W msConnection.password="tmtppassword">

Specifies the password that corresponds to the user.


Specifies enablement (true) or disabling (false) of SSL authentication.

<-W msConnection.portNumber="9446">

Specifies the port number for communication with the management server or the Store and

Forward Service that the management agent uses.


Copies the key and trust files to a local directory when you specify true. This enables you to

access the file if you lose network connectivity or have to remove the installation CD-ROM

from the drive.

<-W msConnection.epKeyStore="c:\tmtp\agent.jks">

Specifies the SSL key file. This file should be located on the local hard drive.

Note: The .jks files are provided for test purposes only and expire relatively soon. This files

are not recommended for use in a production environment.


Specifies the password for the SSL key file.

<-W serviceUser.user="TMTPAgent">

Specifies the user name for the IBM Tivoli Monitoring for Transaction Performance agent

service. (Windows only)

<-W serviceUser.password="tivoli">

Specifies the password that corresponds to the user. (Windows only)

<-W msConnection.maPort="1976">

Specifies the port that is used by the management server to communicate with this

management agent.

Message

generation

-W logSettings.consoleOut="true | false"

Specifies whether to display messages issued by installation, upgrade, or uninstallation

program on the console.

-W logSettings.loglevel="trace_level"

Specifies the trace level setting for the installation log files. This log file lists error, warning,

informational, and debug messages that are issued by the installation program. See “Options

for monitoring installation messages” on page 118 for a complete list of trace level settings.

Access the installation log files in the following path:

v On UNIX-based systems: /var/ibm/tivoli/common/BWM/logs

v On Windows systems: C:\Program Files\ibm\tivoli\common\BWM\logs


Appendix D. Integrating with IBM Tivoli Intelligent

Orchestrator

IBM Tivoli Intelligent Orchestrator is an automated resource management solution

for corporate and Internet data centers that creates a direct, real-time correlation

between application specific service level commitments and the computing

resources required to meet these commitments. The IBM Tivoli Monitoring for

Transaction Performance management agent image is a software product in IBM

Tivoli Intelligent Orchestrator.

Installing the management agent automation package

Objective


agent automation package for IBM Tivoli Intelligent Orchestrator.


The management agent automation package contains different components that

integrate IBM Tivoli Monitoring for Transaction Performance into IBM Tivoli

Intelligent Orchestrator, including scripts and sample workflows that you can use

for configuration. For a detailed accounting of what this package contains, see the

package readme.

Authorization roles

Before you begin

Ensure you meet the following prerequisites:

v IBM Tivoli Intelligent Orchestrator, Version 2.1, is installed and running.

v An IBM Tivoli Monitoring for Transaction Performance management server is

installed and can communicate with the IBM Tivoli Intelligent Orchestrator

server.

When you finish

Configure IBM Tivoli Intelligent Orchestrator, as described in package readme. To

access the readme from the navigation tree in the Tivoli Intelligent Orchestrator

product:

1. Click System Configuration and Workflow Management -> Device Drivers ->

Software Products -> ITMTP Management Agent.

2. Click the Documentation tab.

Procedure

Use the following steps to install the automation package:

1. Copy the ITMTP_MA.tcdriver from the installation media to the

TIO_HOME/drivers directory, where TIO_HOME is the directory where IBM

Tivoli Intelligent Orchestrator is installed.

2. Run the following command from the TIO_HOME/drivers directory:

v For Windows computers, type tc-driver-manager.cmd InstallDriver

v For UNIX systems, type tc-driver-manager.sh InstallDriver ITMTP_MA

3. Copy the management agent installation image to the

TIO_HOME/repository/tivoli/ITMTP/cdrom/ITMTP_WTP_3/MA directory.

133

4. Install the IBM Tivoli Monitoring for Transaction Performance management

server.


Appendix E. Enabling Java 2 security with IBM Tivoli

Monitoring for Transaction Performance

Objective

To enable Java 2 security to work with IBM Tivoli Monitoring for Transaction

Performance on an existing installation of the IBM WebSphere Application Server.


Java 2 security provides a policy-based, fine-grain access control mechanism that

increases overall system integrity by checking for permissions before allowing

access to certain protected system resources. Java 2 security guards access to

system resources such as file I/O, sockets, and properties.)





Before you begin

None

When you finish

1. Perform an install or upgrade of IBM Tivoli Monitoring for Transaction

Performance.

2. Restart the IBM WebSphere Application Server.

Procedure

1. Access the java.policy file: WAS_BASEDIR/java/jre/lib/security.

2. Edit the file with the following information:

grant codeBase "file:/MS_INSTALL_DIR/lib/-" {

permission java.security.AllPermission;

};

grant codeBase "file:${was.install.root}/lib/-" {

permission com.tivoli.jmx.MBeanServerPermission "MBeanServer.*";

permission com.tivoli.jmx.MBeanServerPermission "MBeanServerFactory.*";

permission com.tivoli.jmx.AllMBeanPermission "*";

};

grant codeBase "file:${java.home}/lib/ext/*" {

permission java.security.AllPermission;

permission com.tivoli.jmx.MBeanServerPermission "MBeanServerFactory.*";

permission com.tivoli.jmx.MBeanServerPermission "MBeanServer.*";

permission com.tivoli.jmx.AllMBeanPermission "*";

};

3. Restart the WebSphere Application Server.

135


Appendix F. Support information

This section describes the following options for obtaining support for IBM

products:

v “Searching knowledge bases”

v “Obtaining fixes”

v “Contacting IBM Software Support” on page 138

Searching knowledge bases

If you have a problem with your IBM software, you want it resolved quickly. Begin

by searching the available knowledge bases to determine whether the resolution to

your problem is already documented.

Search the information center on your local system or

network

IBM provides extensive documentation that can be installed on your local machine

or on an intranet server. You can use the search function of this information center

to query conceptual information, instructions for completing tasks, reference

information, and support documents.

Search the Internet

If you cannot find an answer to your question in the information center, search the

Internet for the latest, most complete information that might help you resolve your

problem. To search multiple Internet resources for your product, expand the

product folder in the navigation frame to the left and select Web search. From this

topic, you can search a variety of resources including:

v IBM technotes

v IBM downloads

v IBM Redbooks

v IBM DeveloperWorks

v Forums and newsgroups

v Google

Obtaining fixes

A product fix might be available to resolve your problem. You can determine what

fixes are available for your IBM software product by checking the product support

Web site:

1. Go to the IBM Software Support Web site

(http://www.ibm.com/software/support).

2. Under Products A - Z, select your product name. This opens a product-specific

support site.

3. Under Self help, follow the link to All Updates, where you will find a list of

fixes, fix packs, and other service updates for your product. For tips on refining

your search, click Search tips.

4. Click the name of a fix to read the description and optionally download the fix.

137


To receive weekly e-mail notifications about fixes and other news about IBM

products, follow these steps:

1. From the support page for any IBM product, click My support in the

upper-right corner of the page.

2. If you have already registered, skip to the next step. If you have not registered,

click register in the upper-right corner of the support page to establish your

user ID and password.

3. Sign in to My support.

4. On the My support page, click Edit profiles in the left navigation pane, and

scroll to Select Mail Preferences. Select a product family and check the

appropriate boxes for the type of information you want.

5. Click Submit.

6. For e-mail notification for other products, repeat Steps 4 and 5.

For more information about types of fixes, see the Software Support Handbook

(http://techsupport.services.ibm.com/guides/handbook.html).

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM

software maintenance contract, and you must be authorized to submit problems to

IBM. The type of software maintenance contract that you need depends on the

type of product you have:

v For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational products, as well as DB2 and WebSphere products that run

on Windows or UNIX operating systems), enroll in Passport Advantage in one

of the following ways:

– Online: Go to the Passport Advantage Web page

(http://www.lotus.com/services/passport.nsf/WebDocs/

Passport_Advantage_Home) and click How to Enroll

– By phone: For the phone number to call in your country, go to the IBM

Software Support Web site

(http://techsupport.services.ibm.com/guides/contacts.html) and click the

name of your geographic region.v For IBM eServer™ software products (including, but not limited to, DB2 and

WebSphere products that run in zSeries, pSeries, and iSeries environments), you

can purchase a software maintenance agreement by working directly with an

IBM sales representative or an IBM Business Partner. For more information

about support for eServer software products, go to the IBM Technical Support

Advantage Web page (http://www.ibm.com/servers/eserver/techsupport.html).

If you are not sure what type of software maintenance contract you need, call

1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to

the contacts page of the IBM Software Support Handbook on the Web

(http://techsupport.services.ibm.com/guides/contacts.html) and click the name of

your geographic region for phone numbers of people who provide support for

your location.

Follow the steps in this topic to contact IBM Software Support:

1. Determine the business impact of your problem.

2. Describe your problem and gather background information.


http://techsupport.services.ibm.com/guides/handbook.html

http://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home

http://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home

http://techsupport.services.ibm.com/guides/contacts.html

http://www.ibm.com/servers/eserver/techsupport.html

http://techsupport.services.ibm.com/guides/handbook.html

3. Submit your problem to IBM Software Support.

Determine the business impact of your problem

When you report a problem to IBM, you are asked to supply a severity level.

Therefore, you need to understand and assess the business impact of the problem

you are reporting. Use the following criteria:

Severity 1 Critical business impact: You are unable to use the program,

resulting in a critical impact on operations. This condition

requires an immediate solution.

Severity 2 Significant business impact: The program is usable but is

severely limited.

Severity 3 Some business impact: The program is usable with less

significant features (not critical to operations) unavailable.

Severity 4 Minimal business impact: The problem causes little impact on

operations, or a reasonable circumvention to the problem has

been implemented.

Describe your problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include all relevant

background information so that IBM Software Support specialists can help you

solve the problem efficiently. To save time, know the answers to these questions:

v What software versions were you running when the problem occurred?

v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.

v Can the problem be recreated? If so, what steps led to the failure?

v Have any changes been made to the system? (For example, hardware, operating

system, networking software, and so on.)

v Are you currently using a workaround for this problem? If so, please be

prepared to explain it when you report the problem.

Submit your problem to IBM Software Support

You can submit your problem in one of two ways:

v Online: Go to the ″Submit and track problems″ page on the IBM Software

Support site (http://www.ibm.com/software/support/probsub.html). Enter

your information into the appropriate problem submission tool.

v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.

v Can the problem be recreated? If so, what steps led to the failure?

v Have any changes been made to the system? (For example, hardware, operating

system, networking software, and so on.)

v Are you currently using a workaround for this problem? If so, please be

prepared to explain it when you report the problem.

If the problem you submit is for a software defect or for missing or inaccurate

documentation, IBM Software Support creates an Authorized Program Analysis

Report (APAR). The APAR describes the problem in detail. Whenever possible,

IBM Software Support provides a workaround for you to implement until the

APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the

IBM product support Web pages daily, so that other users who experience the

same problem can benefit from the same resolutions.

Appendix F. Support information 139

http://www.ibm.com/software/support/probsub.html

For more information about problem resolution, see Searching knowledge bases

and Obtaining fixes.


Appendix G. Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may

be used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not give you

any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other

country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the publication. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM

product and use of those Web sites is at your own risk.

141

IBM may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement or any equivalent agreement

between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may

vary significantly. Some measurements may have been made on development-level

systems and there is no guarantee that these measurements will be the same on

generally available systems. Furthermore, some measurement may have been

estimated through extrapolation. Actual results may vary. Users of this document

should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of

performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the

suppliers of those products.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating

platform for which the sample programs are written. These examples have not

been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or

imply reliability, serviceability, or function of these programs. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM for the purposes of developing, using, marketing, or distributing application

programs conforming to IBM‘s application programming interfaces.

Trademarks

AIX, DB2, IBM, the IBM logo, IBMLink™, Informix®, OS/2®, OS/400, Tivoli, the

Tivoli logo, Tivoli Enterprise Console, and TME® are trademarks or registered

trademarks of International Business Machines Corporation in the United States,

other countries, or both.


Intel, the Intel Inside logos, MMX™, and Pentium® are trademarks of Intel

Corporation in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

Microsoft and Windows NT® are registered trademarks of Microsoft Corporation in

the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or

registered trademarks of Sun Microsystems, Inc. in the United

States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other

countries.

SET™ and the SET Logo are trademarks owned by SET Secure Electronic

Transaction™ LLC.

Other company, product, and service names may be trademarks or service marks

of others.

Appendix G. Notices 143


Index

Aaccessibility xii

authorization rolesassigning 81

available 82

using 81

Bbooks

feedback on ix

online ix

ordering ix

see publications xi

browserssupported 14

CCD-ROM

installation images 3

command lineinstallation 111

commandsspecial characters xiii

syntax xiii

conventionstypeface xiii

custom installationmanagement server 34

customer supportsee Software Support 138

Ddatabase, existing

DB2 17

Oracle 21

preparing 17

DB2configuration tasks for 17

preparation 17

uninstalling 107

DB2 Client Application Enablerusing JDBC drivers when

installing 20

directory names, notation xiii

directory structureinstallation 3

downloadinginstallation images 2

Eeducation

see Tivoli technical training xii

embedded installationmanagement server 27

environment variables, notation xiii

Ffixes, obtaining 137

Ggeneric windows

installing 71

uninstalling 109

generic windows recorderuninstalling 108

IIBM Tivoli Intelligent Orchestrator

integrating 133

information centers, searching to find

software problem resolution 137

installationcommand line 111

custom 2

database options 41

directory structure 3

embedded 2

goals 1

imagesCD-ROM 3

Web download 2

management agent 51

management servercustom 34

typical 27

options 2

overview 1

preparation 1

silent 111

Store and Forward agent 45

typical 2

internet browserssupported 14

Internet, searching to find software

problem resolution 137

JJava 2 security

enabling 135

JDBC driversusing as part of DB2 Client

Application Enabler installation 20

Kkey files

creating 73

management agentdeploying 79

management serverdeploying 78

key files (continued)Store and Forward agent

deploying 78

WebSphere Application Serverdeploying 77

KeyDataBase filecreating 75

knowledge bases, searching to find

software problem resolution 137

Llanguage packs


installing 85

overview 85

uninstalling 109

Mmanagement agent

IBM Tivoli Intelligent Orchestratorautomation package 133

installing 51

key files, deploying 79

OS/400 installation 60

overview 51

port numbers 15

prerequisites 13

silent installation 114

system requirements 13

uninstalling 103

verifying installation 63

version 5.1 upgrade 99


z/OS configuration 54

z/OS in SYSPLEX 54, 59

z/OS set up 54

management servercustom installation 34

embedded installation 27

installation overview 27


port numbers 15

prerequisites 13

silent installation 111


typical installation 27

uninstalling 106



manualsfeedback on ix

online ix

ordering ix

see publications xi

145

Nnotation

environment variables xiii

path names xiii

typeface xiii

Oonline publications

accessing xi

operating systemssupported 7

Oracleconfiguration tasks for 21

preparation 21

rollback segments 22

ordering publications ix, xii

OS/400 management agentconfiguring 61

installing 60

prerequisites 60

setting up 61

uninstalling 105

overviewinstallation 1

Ppath names, notation xiii

playback and recordingsoftware installation 71

port numberscommunication 15

preparinginstallation 1

prerequisites 7

management agent 13

management server 13

OS/400 management agent 60


synthetic transaction investigator 67

problem determinationdescribing problem for IBM Software

Support 139

determining business impact for IBM

Software Support 139

submitting problem to IBM Software

Support 139

publicationsaccessing online xi

feedback on ix

online ix

ordering ix, xii

Rrational project, see generic windows 71

rational robot, see generic windows 71

recorder softwareinstalling 67

uninstalling 108

recording and playbacksoftware installation 71

rollback segmentsrequirements for Oracle configuration

tasks 22

Ssilent installation 111

management agent 114


Software Supportcontacting 138

describing problem for IBM Software

Support 139

determining business impact for IBM

Software Support 139

submitting problem to IBM Software

Support 139

SSL key filescreating 73

deploying 73

importing certificates 76

STI, see synthetic transaction

investigator 65

Store and Forward agentinstalling 45


overview 45

port numbers 15

prerequisites 13


uninstalling 104


synthetic transaction investigatoroverview 65

player 65

preparing for installation 66

prerequisites 67

recorder 65

installation 67

uninstalling 108

SYSPLEXinstalling in 59

system requirementsmanagement agent 13




TTivoli software information center xi

Tivoli technical training xii

training, Tivoli technical xii

typeface conventions xiii

typical installationmanagement server 27

Uuninstalling

DB2 107

generic windows recorder 108, 109


Performance 103

language packs 109

management agent 103

uninstalling (continued)management server 106

OS/400 management agent 105



WebSphere Application Server 107

z/OS management agent 105

upgrading5.1 management agent 99

5.1 management server 97

5.2 management agent 93

5.2 management server 91

5.2 Store and Forward agent 92

cleanup 101


Performance, 5.1 to 5.3 94


Performance, 5.2 to 5.3 89

z/OS management agent 94

Vvariables, notation for xiii

verifying installationmanagement agent 63

WWeb download


WebSphere Application Serveradministrative console 81

configuring 81


uninstalling 107

WebSphere Caching ProxyKeyDataBase file

creating 75

Zz/OS management agent

configuring 54

installing in SYSPLEX 54, 59

setting up 54

uninstalling 105



��

Printed in USA

SC32-9107-00

Date post:	20-Apr-2020
Category:	Documents
Upload:	others
View:	10 times
Download:	0 times