IBM Tivoli Monitoring for Applications

IBM Tivoli Monitoring for Applications: Installation and Setup GuideInstallation and Setup Guide Version 5.1.0
GC23-4810-00
Installation and Setup Guide Version 5.1.0
GC23-4810-00

Note Before using this information and the product it supports, read the information in Appendix F, “Notices” on page 141.
First Edition (September 2002)
This edition applies to version 5.1.0 of IBM Tivoli Monitoring for Applications and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2002. 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 What this guide contains . . . . . . . . . . ix Publications . . . . . . . . . . . . . . x
IBM Tivoli Monitoring for Applications library . . x Related publications . . . . . . . . . . xi Accessing softcopy publications . . . . . . xii Using the guide online . . . . . . . . . xii Viewing online help . . . . . . . . . . xii Ordering publications . . . . . . . . . . xii Providing feedback about publications . . . . xiii
Accessibility . . . . . . . . . . . . . . xiii Contacting Customer Support . . . . . . . . xiii Conventions used in this guide . . . . . . . xiii
Typeface conventions . . . . . . . . . . xiii Tivoli command syntax . . . . . . . . . xiv
Chapter 1. Overview . . . . . . . . . 1 Choosing an installation method. . . . . . . . 1 Migrating from previous Tivoli products . . . . . 2 Elements of a Basic installation . . . . . . . . 2
Chapter 2. Guidelines for installation and setup . . . . . . . . . . . . . . 5
Chapter 3. Pre-installation . . . . . . . 7 Supported operating systems . . . . . . . . . 7 Required and optional software . . . . . . . . 8 Disk space requirements . . . . . . . . . . 10 Recommendation for a basic Tivoli environment . . 11 Required permissions and privileges . . . . . . 12 About automatic upgrades . . . . . . . . . 12 Language requirements . . . . . . . . . . 12 TCP/IP for endpoints . . . . . . . . . . . 13 Backing up and restoring Tivoli databases . . . . 13 Handling security across firewalls . . . . . . . 15
Firewall documentation . . . . . . . . . 16 Verifying that the required software is running . . 16 Completing installation planning sheets . . . . . 19
Chapter 4. Performing a Typical installation . . . . . . . . . . . . . 23
Chapter 5. Performing a Custom installation . . . . . . . . . . . . . 33 Installing IBM Tivoli Monitoring for Applications. . 33 Manually creating a Windows proxy endpoint. . . 50
Chapter 6. Installing the product manually . . . . . . . . . . . . . . 55 Using Tivoli Software Installation Service . . . . 55 Accessing the Tivoli environment . . . . . . . 56 Installing managed nodes through an existing Tivoli environment . . . . . . . . . . . . . . 57 Installing endpoints through an existing Tivoli environment . . . . . . . . . . . . . . 60 Installing Tivoli patches manually . . . . . . . 64 Upgrading IBM Tivoli Monitoring manually . . . 67 Manually installing IBM Tivoli Monitoring for Applications software . . . . . . . . . . . 69 Installing the Web Health Console manually . . . 72
Chapter 7. Completing the installation of the product . . . . . . . . . . . 73 Verifying the installation of the product . . . . . 74 Installing the Java Runtime Environment . . . . 76 Linking to an existing Java Runtime Environment 77 Installing files to enable customization of resource models . . . . . . . . . . . . . . . . 78 Installing files to enable Tivoli Enterprise Data Warehouse for IBM Tivoli Monitoring for Applications . . . . . . . . . . . . . . 80 Installing the Tivoli Enterprise Data Warehouse Collector for IBM Tivoli Monitoring for Applications: mySAP.com . . . . . . . . . 83 Installing IBM Tivoli Language Support for this product. . . . . . . . . . . . . . . . 84 Updating Web Health Console files . . . . . . 87 Changing the gateway assignment of an endpoint 88 Integrating IBM Tivoli Monitoring for Applications with Tivoli Business Systems Manager . . . . . 89
Chapter 8. Migrating from previous versions of IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com . . . . . . . . . . . . 93 Installing Patch 220-SAP-0001 . . . . . . . . 94 Migrating R/3 objects . . . . . . . . . . . 95 Deleting Reliant UNIX R/3 objects . . . . . . 96 Completing migration to IBM Tivoli Monitoring for Applications: mySAP.com . . . . . . . . . 97 Mapping monitors to resource models . . . . . 97 Migrating tasks. . . . . . . . . . . . . 100 Monitoring database status . . . . . . . . . 102 Starting or stopping databases or servers . . . . 103 Moving Transports to mySAP systems . . . . . 103 Assigning mySAP system policy region names . . 103 Memory windows on HP-UX . . . . . . . . 103 Event server updates . . . . . . . . . . . 103
Appendix A. Problem determination 105 Troubleshooting installer problems . . . . . . 105
iii
About the log files for installation errors . . . . 109 Problems and workarounds . . . . . . . . 110 Testing endpoint connectivity . . . . . . . . 112 Cleaning up and removing the endpoint . . . . 113
Appendix B. Installation messages 117
Appendix C. Patches . . . . . . . . 131
Appendix D. Uninstalling the product 133 Uninstalling IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications endpoints . . . . . . . . . . . . . . 133 Uninstalling IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications managed nodes . . . . . . . . . . . . 134 Creating the Uninstall Monitoring for mySAP.com task . . . . . . . . . . . . . . . . 135
Uninstalling IBM Tivoli Monitoring for Applications: mySAP.com from the Tivoli server. . 136 Uninstalling IBM Tivoli Monitoring for Applications: mySAP.com managed nodes and endpoints . . . . . . . . . . . . . . 137
Appendix E. Accessibility . . . . . . 139 Using Assistive Technologies . . . . . . . . 139 Magnifying What is Displayed on the Screen . . . 139 Documentation in Accessible Formats . . . . . 139 Using Alternative Text . . . . . . . . . . 139
Appendix F. Notices . . . . . . . . 141 Trademarks . . . . . . . . . . . . . . 143
Index . . . . . . . . . . . . . . . 145
iv IBM Tivoli Monitoring for Applications: Installation and Setup Guide
Figures
1. Typical installation of a Tivoli management region . . . . . . . . . . . . . . . 4
2. Typical Installation: Typical option panel 25 3. Typical Installation: Basic tab for managed
nodes . . . . . . . . . . . . . . 26 4. Typical Installation: Advanced tab for
managed nodes . . . . . . . . . . . 26 5. Typical Installation: Basic tab for endpoints 28 6. Typical Installation: Advanced tab for
endpoints . . . . . . . . . . . . . 28 7. Sample Step List panel . . . . . . . . 30 8. Custom Installation: Region view in the
Planner . . . . . . . . . . . . . . 35 9. Custom Installation: Custom option panel 37
10. Custom Installation: Adding a managed node in the Planner . . . . . . . . . . . . 38
11. Custom Installation: Setting managed node properties in the Planner . . . . . . . . 39
12. Custom Installation: Adding a gateway in the Planner . . . . . . . . . . . . . . 41
13. Custom Installation: Associating a gateway with a managed node in the Planner . . . . 42
14. Custom Installation: Adding an endpoint in the Planner . . . . . . . . . . . . 43
15. Custom Installation: Setting endpoint properties in the Planner . . . . . . . . 44
16. Custom Installation: Adding the Web Health Console in the Planner . . . . . . . . . 45
17. Sample Step List panel . . . . . . . . 49 18. Step List Installer panel sample . . . . . 106 19. Detail dialog box of the Step List panel 107
v
vi IBM Tivoli Monitoring for Applications: Installation and Setup Guide
Tables
1. Guidelines for installation and setup . . . . 5 2. Supported operating systems for managed
nodes . . . . . . . . . . . . . . . 7 3. Supported operating systems for endpoints 8 4. Required and optional software for IBM Tivoli
Monitoring for Applications . . . . . . . 8 5. Disk space requirements for installing the
Tivoli environment . . . . . . . . . . 11 6. Firewall security features of the Tivoli
Management Framework . . . . . . . . 15 7. Managed resources and their purpose. . . . 19 8. Planning sheet for creating managed nodes 20 9. Planning sheet for creating endpoints . . . . 21
10. Software locations on installation CDs . . . 29 11. Custom installation goals . . . . . . . . 33 12. Removal of planner elements and possible
consequences . . . . . . . . . . . . 46 13. Software locations on installation CDs . . . 48 14. Guidelines for installing the product through
an existing Tivoli environment . . . . . . 55 15. Manual installation of the product:
Specifications of required patches . . . . . 65 16. Product locations on installation CDs . . . . 69
17. Guidelines for Completing the installation of the product . . . . . . . . . . . . 73
18. Language support and names of corresponding installation index (.IND) files . 85
19. Guidelines for migrating from previous versions of the product . . . . . . . . 93
20. Mapping monitors to resource models . . . 98 21. Task migration . . . . . . . . . . . 100 22. IBM Tivoli Monitoring for Applications:
mySAP.com start and stop tasks . . . . . 103 23. Overview of problem determination topics
and procedures . . . . . . . . . . . 105 24. Graphical user interface elements for the Step
List panel of the installer . . . . . . . 107 25. Error logs and descriptions . . . . . . . 110 26. Problems and workarounds . . . . . . . 110 27. Patches that the installer installs
automatically . . . . . . . . . . . 131 28. Required patches and APARs for required
and optional software . . . . . . . . . 131 29. Guidelines for uninstalling the product 133 30. mySAP_uninstall51.pl details . . . . . . 136
vii
viii IBM Tivoli Monitoring for Applications: Installation and Setup Guide
About this guide
This guide describes how to install and set up IBM® Tivoli® Monitoring for Applications to monitor and manage server resources and other objects in a Tivoli environment.
Who should read this guide System administrators refer to this guide to learn how to install and set up the following basic elements of the Tivoli environment: v A Tivoli server v Managed nodes v Managed computers, which are hosts for the Tivoli endpoint software
Readers should be familiar with the following: v UNIX® or Windows® operating systems v Administration of application servers
What this guide contains This guide contains the following sections: v Chapter 1, “Overview” on page 1
Provides an overview of the installation and setup of IBM Tivoli Monitoring for Applications.
v Chapter 2, “Guidelines for installation and setup” on page 5
Provides guidelines for installing and setting up IBM Tivoli Monitoring for Applications.
v Chapter 3, “Pre-installation” on page 7
Describes how to plan and prepare for installing the product. v Chapter 4, “Performing a Typical installation” on page 23
Describes the Typical installation method. v Chapter 5, “Performing a Custom installation” on page 33
Describes the Custom installation method. v Chapter 6, “Installing the product manually” on page 55
Describes how to install the product manually. v Chapter 7, “Completing the installation of the product” on page 73
Describes how to verify and complete the installation of the product. v Chapter 8, “Migrating from previous versions of IBM Tivoli Monitoring for
Applications, Version 5.1.0: mySAP.com” on page 93
Describes how to migrate from Tivoli Manager for R/3 Version 2.2.0 to IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com.
v Appendix A, “Problem determination” on page 105
Describes how to determine the source of common problems and suggests solutions.
v Appendix B, “Installation messages” on page 117
Describes messages that the product can generate.
ix
v Appendix C, “Patches” on page 131
Lists required patches. v Appendix D, “Uninstalling the product” on page 133
Describes uninstallation of the product. v Appendix E, “Accessibility” on page 139
Describes accessibility features of the product. v Appendix F, “Notices” on page 141
Provides information on copyrights and trademarks.
Publications
This section lists publications in the IBM Tivoli Monitoring for Applications library and any other related documents. It also describes how to access Tivoli publications online, how to order Tivoli publications, and how to submit comments on Tivoli publications.
IBM Tivoli Monitoring for Applications library The following documents are available in the IBM Tivoli Monitoring for Applications library. v IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications User’s Guide,
SC23-4819-00 Provides information about how to use IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications to manage Siebel resources.
v IBM Tivoli Monitoring for Applications: mySAP.com User’s Guide, SC23-4812-00 Provides information about how to use IBM Tivoli Monitoring for Applications: mySAP.com to manage mySAP.com resources.
v IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications Reference Guide, SC23-4818-00 Provides detailed information about IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications resource models, tasks, and commands.
v IBM Tivoli Monitoring for Applications: mySAP.com Reference Guide, SC23-4813-00 Provides detailed information about IBM Tivoli Monitoring for Applications: mySAP.com resource models, tasks, and commands.
v IBM Tivoli Monitoring for Applications Installation and Setup Guide, GC23-4810-00 Provides instructions for installing Tivoli Manager for Applications and setting it up to manage endpoint resources.
v IBM Tivoli Monitoring for Applications, Release Notes, GI11-0941-00 Describes product features and provides information about the latest changes to the installation requirements and procedures. The release notes also describe known limitations related to installation and explain how to work around each limitation.
v IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications: Limitations and Workarounds Supplement, SC23-4817-00 Provides the latest information about known product limitations and workarounds. To ensure that the information is the latest available, this document is provided only on the Web, where it is updated on a regular basis. You can access the Limitations and Workarounds document through the IBM Tivoli Monitoring for Applications link on the Tivoli Information Center Web site:
x IBM Tivoli Monitoring for Applications: Installation and Setup Guide
http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html
v IBM Tivoli Monitoring for Applications: mySAP.com: Limitations and Workarounds Supplement, SC23-4806-00 Provides the latest information about known product limitations and workarounds. To ensure that the information is the latest available, this document is provided only on the Web, where it is updated on a regular basis. You can access the Limitations and Workarounds document through the IBM Tivoli Monitoring for Applications link on the Tivoli Information Center Web site: http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html
Related publications The following documents provide related information: v IBM Tivoli Monitoring: Workbench User’s Guide, SH19-4571
Describes how to use the IBM Tivoli Monitoring Workbench to create new resource models and to modify existing ones.
v IBM Tivoli Monitoring User’s Guide, SH19-4569 Describes how to use the IBM Tivoli Monitoring user interface.
v IBM Tivoli Monitoring Collection Reference, SH19-4570 Describes the resource models that come with IBM Tivoli Monitoring software.
v Tivoli Management Framework User’s Guide, GC31-8433-04 Describes the Tivoli environment, including profiles and profile management.
v Tivoli Management Framework Reference Manual, SC31-8434-04 Provides detailed information about Tivoli commands.
v Tivoli Management Framework, Version 3.7.1: Installation Guide, GC32-0395-01 Provides information and procedures for installing and upgrading Tivoli Management Framework (Tivoli management region server, managed nodes, gateways, and endpoints), and provides the procedures for installing and upgrading Tivoli Enterprise products.
v Tivoli Management Framework, Version 3.7.1: Planning for Deployment Guide, GC32-0393-01 Explains how to plan for deploying your Tivoli environment, and describes Tivoli Management Framework and its services.
v Tivoli Enterprise Console User’s Guide, Version 3.7.1, GC32-0667-01 Describes how to use the Tivoli Enterprise Console® to correlate events and determine the severity and relationship of those events.
v Tivoli Enterprise Console, Version 3.7: Rule Builder’s Guide, GC32-0669-00 Provides information about developing rules for managing events with Tivoli Enterprise Console with a text editor and a graphical rule builder.
v TME 10 Software Installation Service User’s Guide, sis36ga Describes how to use the Tivoli Software Installation Service (SIS) to install Tivoli products.
v Tivoli Business Systems Manager, Version 1.5: User’s Guide
Describes how to use the Tivoli Business Systems Manager product. v Tivoli Business Systems Manager Console, Version 1.5: User’s Guide
Describes how to use the Tivoli Business Systems Manager console. v Tivoli Enterprise Data Warehouse documentation
About this guide xi
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://www.tivoli.com/support/documents/glossary/termsm03.htm
Accessing softcopy publications The publications for this product are available in PDF and HTML formats through the following media: v IBM Tivoli Monitoring for Applications: Version 5.1.0 Documentation CD
The Documentation CD contains all of the English language publications for this product, except for the Web-only Limitations and Workarounds supplements. To access the publications, use a Web browser to open the start.html file, which is located in the root directory of the CD.
v Tivoli Information Center IBM posts publications for this product and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Information Center Web site: http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html
Click the IBM Tivoli Monitoring for Applications link to access the product library.
http://www.tivoli.com/support/documents/
Using the guide online This document is available on the IBM Tivoli Monitoring for Messaging and Collaboration, Version 5.1.0: Documentation CD in PDF and HTML formats. Refer to the readme.txt file on the CD for instructions on downloading the Acrobat Reader, Version 3.0 or later, to view, save, and print the manual.
Use your HTML browser to open the start.html file on the CD to access the .html documentation files. Every navigation page also includes a link at the bottom to download the Acrobat reader for viewing, saving, and printing the files.
Viewing online help Online help is available in several forms: v Desktop — Access online help by clicking the Help buttons in dialog boxes. v Commands — You can display command syntax and parameter information for
command line interface (CLI) commands by typing the name of the command at a command prompt and pressing the Enter key.
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
xii IBM Tivoli Monitoring for Applications: Installation and Setup Guide
In other countries, see the following Web site for a list of telephone numbers: http://www.tivoli.com/inside/store/lit_order.html
Providing feedback about publications If you have comments or suggestions about our products and documentation, contact us in one of the following ways: v Send an e-mail to [email protected]. v Complete our customer feedback survey at the following Web site:
http://www.tivoli.com/support/survey/
Accessibility Accessibility features help users who have physical disabilities, 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 features of the graphical user interface.
For additional information, see the appendix on Appendix E, “Accessibility” on page 139.
Contacting Customer Support If you have a problem with any Tivoli product, you can contact IBM Customer Support for Tivoli products. See the Tivoli Customer Support Handbook at the following Web site: http://www.tivoli.com/support/handbook/
The handbook provides information about how to contact Customer Support, depending on the severity of your problem, and the following information: v Registration and eligibility v Telephone numbers and e-mail addresses, depending on the country in which
you are located v What information you should gather before contacting Customer Support
Conventions used in this guide This guide uses several conventions for special terms and actions and for command syntax.
Typeface conventions This guide uses the following typeface conventions:
Bold Commands, keywords, file names, authorization roles, URLs, or other information that you must use literally appear like this, in bold. Names of windows, dialogs, and other controls also appear like this, in bold.
Italics Variables and values that you must provide appear like this, in italics. Words and phrases that are emphasized also appear like this, in italics.
Monospace Code examples, output, and system messages appear like this, in a monospace font.
About this guide xiii
Tivoli command syntax The commands in this book use the following special characters to define Tivoli command syntax:
< > Indicates that the text enclosed in the angle brackets is a variable that you supply.
[ ] Identifies optional elements. Elements that do not have brackets around them are required.
... Indicates you can specify multiple values for the previous element. Separate multiple values by a space, unless the command information specifies differently.
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 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, meaning you can use the element on either the left or right of the vertical bar, but not both.
{ } Delimits a set of mutually exclusive elements when a command requires one of them, but not multiple elements. Brackets ([ ]) are around elements that are optional.
\ A backslash indicates that a command continues on the next line.
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 that they are optional. The ellipsis after the –a admin 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. The braces that surround the –f, –i, and object elements indicate that you are including required elements. If you specify the object argument, you can specify more than one object.
When you reference an object in a command issued from the command line, the reference is not an absolute object reference like those used in programming. Instead, the reference is a user-friendly name. This user-friendly name derives from a name given to the object by the user of the application, such as when creating a policy region.
xiv IBM Tivoli Monitoring for Applications: Installation and Setup Guide
Chapter 1. Overview
This document describes installation and setup of IBM Tivoli Monitoring for Applications, monitoring and management software for business-critical hardware and software. This document includes information on the following topics: v Determining the proper installation for your environment v Information about a typical Tivoli environment v Guidelines and worksheets for planning your installation and setup v Procedures for using the installation wizard or the Tivoli desktop to install your
monitoring product v Problem determination information for the installation wizard v Guidelines for migrating from Tivoli Manager for R/3, Version 2.2
Choosing an installation method The IBM Tivoli monitoring products offer several options for installing the software, depending on the complexity of your environment and your knowledge of Tivoli management systems. Your choices include the following:
Installation wizard The installation wizard (referred to in the rest of this guide as the installer) creates a complete Tivoli environment, if none exists, and installs the product. The installer also installs supplemental software, such as the Java run-time environment and language packs. Use the installer if you either have no previous Tivoli software installations or you have Tivoli Management Framework, Version 3.7, Revision A or Revision B, installed.
If you use the installer, you must choose between a Typical or Custom installation path. Use the following criteria to determine which path you want to take:
Use the Typical installation path when the following conditions are true:
v You want to install the product on a target computer that matches one of the following profiles: – Has no software installed for the Tivoli Management Framework.
—OR— – Has one of the following versions of the Tivoli Management
Framework installed: Version 3.7 (Revision A or Revision B) or Version 3.7.1. You cannot install this product on systems that run previous versions of the Tivoli Management Framework.
v You are a first-time Tivoli user. v Your environment matches the “Elements of a Basic installation” on
page 2.
Use the Custom installation path if you want to use the Planner tool that offers a tree view of the entire installation and provides additional control over directory paths and naming conventions. See Chapter 5, “Performing a Custom installation” on page 33. Use the Custom installation option if you are installing the Tivoli management region server on a UNIX computer and you want to create Windows endpoints.
1
Tivoli desktop and command line interface Use one of these options if you are a current Tivoli user with earlier versions of the Tivoli Management Framework. You might also want to use one of these options if you have expert knowledge of the Tivoli environment and plan to extensively customize your installation. The manual installation method enables you to create interconnected Tivoli management region servers and to create environments with more than 50 endpoints.
Chapter 6, “Installing the product manually” on page 55 provides manual installation instructions. For further information, see the documentation on the Tivoli Management Framework software CDs that come with IBM Tivoli Monitoring for Applications.
The Tivoli Software Installation Service (SIS) Go to http://www.tivoli.com/support for information about obtaining and using SIS.
Migrating from previous Tivoli products The following migration options exist for Tivoli Distributed Monitoring and Tivoli Manager for R/3: v Migrate or upgrade pre-existing software:
Note: The installer automatically migrates this software to IBM Tivoli Monitoring for Applications. When you perform a manual installation of the product, you must manually install the upgrade patch as described in Chapter 6, “Installing the product manually” on page 55.
– Upgrade previous versions of IBM Tivoli Monitoring to the required Version 5.1.1. See “Upgrading IBM Tivoli Monitoring manually” on page 67.
– Migrate Tivoli Manager for R/3 software as described in Chapter 8, “Migrating from previous versions of IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com” on page 93.
v Map tasks in the Tivoli Manager for R/3 product to IBM Tivoli Monitoring for Applications. You use configuration tasks in the new product in the same way that you used them in Tivoli Manager for R/3. The program code in the new tasks has changed to work with IBM Tivoli Monitoring for Applications, but the names of the tasks and their general purpose remains the same.
v Map monitors to resource models. See Chapter 8, “Migrating from previous versions of IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com” on page 93. IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications does not support concurrency with Tivoli Distributed Monitoring. You must uninstall Tivoli Manager for Siebel before using IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications resource models.
Elements of a Basic installation This section describes a basic Tivoli environment. The installer creates a basic Tivoli environment during the Typical installation.
During the Typical or Custom installation, you can create the following elements:
2 IBM Tivoli Monitoring for Applications: Installation and Setup Guide
v One required Tivoli management region server to monitor endpoints. The Tivoli server runs the Tivoli Management Framework and IBM Tivoli Monitoring software.
v A managed node computer system on which Tivoli Management Framework is installed. Each managed node has gateway software that increases performance in the Tivoli environment by reducing traffic on the Tivoli management region server. The IBM Tivoli Monitoring software also runs on a managed node.
v Up to 50 endpoints for monitoring resources on your network. You distribute monitoring software to the endpoints. An endpoint is a computer system on which Tivoli software is installed to enable communication with a Tivoli management region server.
v One Web Health Console on any computer in the same network as the Tivoli management region. If you use the installation wizard, you can automatically install the console on endpoints or managed nodes that you select. The console shows the status and health of a server in a Web browser. You can create an unlimited number of Web Health Consoles. Web Health Consoles have the following characteristics: – Can exist on an unlimited number of computers. – Can display the status of resources for an unlimited number of Tivoli
management regions – Require the deployment of the Java Runtime Environment, Version 1.3, on the
host computer.
Before you begin the installation process, you should have a basic understanding of the Tivoli environment. The Tivoli environment is software based on the Tivoli Management Framework that addresses network computing management issues across many platforms. In a Tivoli environment, a system administrator distributes software, manages user configurations, changes access privileges, automates operations, monitors resources, and schedules jobs.
Chapter 1. Overview 3
A Tivoli environment spans multiple computers, as shown in the Figure 1. A large company might have hundreds of managed nodes with gateways that monitor thousands of endpoints, which you set up using one of the installation methods. Figure 1 shows a typical installation of a Tivoli management region.
1. Tivoli management region server
This server is required. It monitors endpoints and runs the Tivoli Management Framework and IBM Tivoli Monitoring software.
2. Managed node with gateway
This managed node shares the processing load of the Tivoli management region server, runs the software, and communicates with its assigned endpoints. The managed nodes reduce the number of management and user administration operations the Tivoli server must perform. Tivoli network transactions flow to multiple servers instead of just to the Tivoli server.
Gateways enable the managed node to perform endpoint management operations for the Tivoli management region server. A gateway efficiently transfers large amounts of data to endpoints.
3. Endpoints
An endpoint is a computer system on which Tivoli software is installed to enable monitoring.
4. Web Health Console
This Web Health Console shows the status and health of endpoints. You can install a Web Health Console on any computer in the same network as the Tivoli management region server. The Web Health Console has the following characteristics:
v Can exist on an unlimited number of computers.
v Can display the status of resources for an unlimited number of Tivoli management regions.
Figure 1. Typical installation of a Tivoli management region
Chapter 2. Guidelines for installation and setup
Table 1 summarizes the procedures for installing and setting up IBM Tivoli Monitoring for Applications. It also lists where you can find the information and procedures that guide you through the installation.
Table 1. Guidelines for installation and setup
What you do Refer to
Before Installation
1. Check the system for compliance with the system requirements and set up or check the prerequisite software.
“Supported operating systems” on page 7
2. Back up an existing Tivoli environment, if you have one. If you encounter a problem during an installation, use the backup to restore the environment to a known working state.
“Backing up and restoring Tivoli databases” on page 13
3. Complete the planning sheets for the managed nodes and endpoints that you want to create. (Optional)
“Completing installation planning sheets” on page 19
4. Make sure Tivoli monitoring activity performs across your network firewalls.
“Handling security across firewalls” on page 15
5. If you have a Solaris Operating Environment (referred to in the remainder of this document as Solaris), you must install certain fix packages on the target computer to enable the installer.
Patches are available from the following Sun Web site: http://sunsolve.sun.com.
Fix packages for Solaris 2.6 105181-29, 105210-38, 105284-45, 105568-23, 105591-11, 105633-59, 105669-10, 106040-17, 106125-11, 106409-01, 106429-02, 106841-01, 106842-09, 107733-09, and 108091-03
Fix packages for Solaris 7 106327-10, 106541-17, 106950-14, 106980-17, 107081-37, 107153-01, 107226-18, 107544-03, 107636-08, 107656-07, 107702-09, 108374-05, 108376-29, and SUNWi1 fonts package Note: You can obtain the fonts package on the Solaris installation CD.
Fix packages for Solaris 8 108652-37, 108921-13, and 108940-32
6. If you have AIX Version 4.3.x systems, install IBM AIX maintenance package 9 to enable the installer.
Obtain the maintenance package at the following IBM Web site:
http://techsupport.services.ibm.com/rs6k/ml.fixes.html
7. Hewlett-Packard Company requires a set of patches for the HP-UX environment
See the following Web site for the latest required patches for the HP-UX operating system:
http://www.hp.com/products1/unix/java/ \ infolibrary/patches.html
8. Use the ping command to test network names of the target computers for the installation, which ensures the network recognizes the names. The target computer replies to the ping command with its IP address and statistics regarding the transaction if the name is valid, the network connection is active, and the target computer is running.
Ping command. Run a ping command to call each target computer. For example, enter the following command in the MS-DOS command prompt on Windows:
ping name
What you do Refer to
9. Confirm that the required software services are running on the target computers.
“Verifying that the required software is running” on page 16
Installation
10. Install the product. The installation can include the following: v managed nodes v endpoints v the Web Health Console
Note: You can create these components after installation. You can also use the Web Health Console’s installation executable to install the console on any computer in your Tivoli environment.
Chapter 4, “Performing a Typical installation” on page 23
—OR—
—OR—
—OR—
Use Tivoli Software Installation Service (SIS) to install IBM Tivoli Monitoring for Applications. For information about obtaining and using SIS, go to the following Web site:
http://www.tivoli.com/support/
After Installation
11. Back up the Tivoli environment after installation. If you encounter a problem during final configuration, use the backup copy to restore the environment to a known state.
“Backing up and restoring Tivoli databases” on page 13
12. Create managed nodes and endpoints if you did not create them during installation.
Tivoli Enterprise, Version 3.7.1: Installation Guide that comes with the Tivoli Management Framework software.
13. Verify the functionality of the Tivoli management region by running communication commands.
“Verifying the installation of the product” on page 74
14. Migrate or map older versions of Tivoli management and monitoring software to IBM Tivoli Monitoring for Applications.
Chapter 8, “Migrating from previous versions of IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com” on page 93
15. Install software to enable resource models, the Web Health Console, historical reporting, and national language versions of the product.
Chapter 7, “Completing the installation of the product” on page 73
16. Create server objects for the product to manage. See the following user’s guides:
v For IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications, see IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications User’s Guide
v For IBM Tivoli Monitoring for Applications: mySAP.com, see IBM Tivoli Monitoring for Applications: mySAP.com User’s Guide.
This chapter provides the following pre-installment requirements and procedures for IBM Tivoli Monitoring for Applications: v Supported operating systems v Required and optional software v Disk space requirements v Required permissions and privileges v Upgrades v Language requirements v TCP/IP for endpoints v Backing up and restoring the Tivoli environment v Handling security across firewalls v Verifying that prerequisite software is running v Planning and installation worksheets
Chapter 7, “Completing the installation of the product” on page 73 provides procedures for product or platform-specific prerequisites.
Supported operating systems This section lists the supported operating systems that work with managed nodes or endpoints for IBM Tivoli Monitoring for Applications.
Table 2. Supported operating systems for managed nodes
Supported operating systems for managed nodes1
Version Siebel mySAP.com
Yes Yes
1. IBM Tivoli Monitoring for Applications: mySAP.com provides support for Reliant UNIX systems only with the new Remote Management capabilities.
2. The Tivoli Business Systems Manager task server is not available for this platform.
7
Supported operating systems for endpoints
Version Siebel mySAP.com
Linux2 Red Hat, SuSE 7.0, SuSE 7.1, Turbo 7.0, zLinux
No Yes
Yes Yes
Notes:
1. The Tivoli Business Systems Manager task server is not available for this platform.
2. All Linux support is based on Linux kernel 2.4.
Required and optional software This section lists the required and optional software for IBM Tivoli Monitoring for Applications. If you use Tivoli Manager for R/3 see Chapter 8, “Migrating from previous versions of IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com” on page 93. If you use Tivoli Manager for Siebel, you must uninstall it before installing IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications.
Table 4 lists required and optional products for IBM Tivoli Monitoring for Applications.
See “Installing Tivoli patches manually” on page 64 for a list of required patches. The installer automatically installs required patches. If you manually install the product, you must also manually install any patches you want.
The Installed by the product installer? column of the table indicates software that the installer automatically installs. If you perform a manual installation of the product, you must manually install each of these products and their patches.
Table 4. Required and optional software for IBM Tivoli Monitoring for Applications
Product Release Installed by the product installer?
Required software
Table 4. Required and optional software for IBM Tivoli Monitoring for Applications (continued)
Tivoli Management Framework
The installer automatically detects an existing installation of Tivoli Management Framework, Version 3.7, Revision A or B, and upgrades it to the required Version 3.7.1.
If you have Tivoli Management Framework, Version 3.7.1, the installation is checked to ensure that the required patches are installed. If not, the installation is upgraded.
3.7.1 Yes
IBM Tivoli Monitoring
The installer automatically detects an existing installation of IBM Tivoli Monitoring, Version 4.1.x or Version 5.1.0, and upgrades it to the required Version 5.1.1.
5.1.1 Yes
IBM Tivoli Monitoring Component Services
When you use the installer to install IBM Tivoli Monitoring for Applications in an existing Tivoli environment, the installer upgrades Application Proxy software to IBM Tivoli Monitoring Component Services
5.1.0 Yes
5.1.0 Yes
Siebel eBusiness Applications 6.0.x for NT No
6.2.1 for NT, AIX 4.3.3, Solaris 2.6
Notes:
No
No
R/3 3.1.i, 4.0B, 4.5B, 4.6B, 4.6C, 4.6D
No
To enable monitoring of Windows endpoints: Microsoft Windows Management Instrumentation (WMI). This software comes with Windows 2000. You must install it manually on Windows NT endpoints.
Search for ″wmi″ on the following Web site for more information: http://msdn.microsoft.com
Version 5.1 is recommended. No
To enable Windows, UNIX and Linux endpoints: Java Runtime Environment, Version 1.3. See the note about HP-UX following this table.
1.3.0 or 1.3.1
No
To enable computers that run the Web Health Console: Java Runtime Environment, Version 1.3. See the note about HP-UX following this table.
1.3 No
To enable data logging for resource models on Windows NT and Windows 2000 endpoints: ODBC driver for Microsoft Access 2000.
If the endpoint does not have Microsoft Access 2000 installed:
1. Run the mdac_typ.exe file that is provided with Microsoft Data Access Components 2.1 (or later), at http://www.microsoft.com/data
2. Install Jet 4.0 Service Pack 3.
See the information in the left column of this row.
No
Tivoli Enterprise Data Warehouse
1.1-TDW-0005E Note: e-fix 1.1-TDW-0005E is superseded by 1.1-TDW-FP02 (TEDW 1.1 Fix Pack 2) when that fix pack becomes available.
1.1 or higher No
The following patch is required for both product components: 3.7.1-TEC-0001.
3.7.1-TEC-0004 is required for IBM Tivoli Monitoring for Applications: mySAP.com only.
3.7.1 No
Tivoli Inventory 4.0 No
Tivoli Business Systems Manager
The following patches are required: TBSM Patch 24, TBSM Patch 32, TBSM Patch 35, and 15-BSM-0038
1.5.1 No
Tivoli Software Installation Service 3.7 No
Disk space requirements This section lists the disk space requirements for the elements in the Tivoli environment.
Element Disk space requirements
Tivoli management region server
Approximately 5 GB (including temporary installation files for the installer)
Approximately 2.4 GB when you do not use the installer
For details of disk space requirements for individual components, refer to the following list:
v Tivoli Management Framework and IBM Tivoli Monitoring: 500 MB
v The installation depot (temporary directory): 2.6 GB (The installer provides the option to automatically delete this directory after installation.) Note: On Windows, the depot must reside on the target computer. You cannot perform an installation of the product on Windows using a depot that is located on a remote system. On UNIX, provide a directory path that is accessible from the installation computer to the installation depot.
v Files that the installer places in the temporary ($TEMP or %TEMP%) directories that are defined for your operating system: 3 MB
Additional Information: When Tivoli Management Framework is installed on this computer, obtain the name of this directory by accessing the Tivoli command line environment (as described in “Accessing the Tivoli environment” on page 56) and entering this command: wtemp.
v IBM Tivoli Monitoring for Applications: 200 to 300 MB
v (Optional) Web Health Console server: 130 to 200 MB, depending on the operating system of the target computer
Additional Information: The Java run-time environment, Version 1.3, is required to run the console. The space requirement for that software varies.
Managed node
Approximately 1.5 GB
For details of disk space requirements for individual components, refer to the following list:
v Tivoli Management Framework and IBM Tivoli Monitoring: 500 MB (Includes the space required by the gateway software that enables the managed node to communicate with an endpoint.)
v IBM Tivoli Monitoring for Applications: 200 to 300 MB
Note: The Java run-time environment, Version 1.3, is required to run the console. The space requirement for that software varies, depending on the operating system. For example, the run-time environment on Windows requires approximately 65 MB.
Endpoint
Approximately 100 MB (not includng the Web Health Console)
For details of disk space requirements by individual components, refer to the following list:
v The endpoint daemon for Tivoli Management Framework: 2 MB
v Required to run endpoints for IBM Tivoli Monitoring for Applications: Java run-time environment, Version 1.3: space requirement varies
v Required to run endpoints for IBM Tivoli Monitoring for Applications on Windows: Windows Management Instrumentation (WMI): refer to Microsoft specifications
Note: The Java run-time environment, Version 1.3, is required to run the console. The space requirement for that software varies, depending on the operating system. For example, the run-time environment on Windows requires approximately 65 MB.
Recommendation for a basic Tivoli environment This following list describes the recommended basic Tivoli environment. The installer can create this Tivoli environment during a Typical or Custom installation. v Required: One Tivoli management region server to monitor endpoints. v One managed node v Up to 50 endpoints for monitoring resources on your network. v One Web Health Console on a managed node or endpoint. You can create an
additional number of Web Health Consoles on an additional number of computers.
Chapter 3. Pre-installation 11
Required permissions and privileges You must have the following to install the product: v The license key for Tivoli Management Framework. Obtain this key in the
printed document that comes with the installation CDs for the Tivoli Management Framework.
v On UNIX, the user who installs the product must have root privileges. On Windows, the user who installs the product must have membership in the Administrators group. Tivoli recommends that you log on as root on UNIX and Administrator on Windows.
v A valid host name for all managed nodes and endpoints you create. Specify the unique domain name for the host name when multiple computers in the system have the same host name. For example, the fully qualified name of the tokyo computer might be tokyo.sales.mycompany.com, where sales is the domain name of the Sales Department’s domain at the company mycompany. The full name distinguishes the Sales Department’s server from a tokyo server in the marketing domain called tokyo.marketing.mycompany.com.
About automatic upgrades The installer automatically detects an existing installation of Tivoli Management Framework, Version 3.7, Revision A or B, and upgrades it to the required Version 3.7.1. The installer also installs the required patches.
If you have an earlier version of Tivoli Management Framework, you must manually upgrade to Version 3.7 Revision A or B or Version 3.7.1 before you can run the installer.
The installer automatically detects an existing installation of IBM Tivoli Monitoring, Version 4.1x or 5.1.0, and upgrades it to the required Version 5.1.1.
The Tivoli Management Framework software CDs that come with IBM Tivoli Monitoring for Applications contain the Tivoli Management Framework User’s Guide.
Chapter 6, “Installing the product manually” on page 55 describes how to install upgrade software through the Tivoli desktop or the command line interface, instead of using the installer.
Chapter 8, “Migrating from previous versions of IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com” on page 93 describes how to migrate from previous versions of Tivoli monitoring products.
Language requirements After you complete the installation, you can enable other languages in the product. See “Installing IBM Tivoli Language Support for this product” on page 84 for procedures regarding installing the product in these national languages: Brazilian Portuguese, Chinese (simplified), Chinese (traditional), French, German, Italian, Japanese, Korean, and Spanish.
TCP/IP for endpoints You must activate the TCP/IP communication protocol servers to enable communication with the Tivoli server. See the documentation for the server software that runs on your systems for instructions on enabling TCP/IP on an applications server. You can do this either before or after installing the software.
Backing up and restoring Tivoli databases
Objective To back up existing Tivoli object databases for all computers in the Tivoli management region so you can use these backup copies to restore the databases to a known working state if you encounter a problem during installation.
Background information
Note: This procedure describes a routine backup method that you can use frequently. In addition to this backup, arrange a complete backup of Tivoli whenever you make significant changes to the system, such as the installation of this product. If you encounter a problem during a change operation, you can use the system backup to restore the entire Tivoli environment to a known working state.
This procedure provides a stable and complete snapshot of the Tivoli database and a safer alternative to manually compressing the database files in a .tar or .zip format. For example, when you save a database to a .tar or .zip file, an error might occur if the Tivoli object dispatcher is simultaneously writing to the Tivoli database.
This procedure also enables you to estimate the size of the backup files to ensure that you have sufficient disk space in the target directory to complete the operation.
You back up or restore databases using the wbkupdb command. In a large Tivoli management region, the wbkupdb process can take a long time because backups of the managed node databases are performed serially. Concurrent backup processes are not allowed in the same Tivoli management region. You must complete one wbkupdb command before you execute a second instance of the command.
The Tivoli Management Framework must be running on the Tivoli management region server and on the managed node whose database is being restored. Otherwise, the wbkupdb command cannot restore any database (managed node or Tivoli management region server). See the Tivoli Management Framework Reference Guide for a description of all the capabilities of the wbkupdb command.
Required authorization role backup or super
Before you begin You must have a valid user login name and a group name for the computer on which the backup file is stored.
On UNIX, set umask to 022 for root.
When you finish None
Procedure You can perform backups in the Tivoli desktop or in the command line interface.
You can perform restore operations in the command line interface only.
Command line: Use the wbkupdb command.
wbkupdb [–d device] –r [node_name ...]
where:
–d device Specifies the file or device to which the backup file is saved or from which the backup file is retrieved. If you specify a file name with this option, you can insert a file date and time anywhere in the file name by adding the variable %t. The variable is replaced with a date/time stamp in the form Mondd-hhmm. For example, if you specify –d /usr/backups/TMR1%t.bk, the resulting file is named TMR1Dec21-0955.bk. The time is displayed in 24-hour mode.
–r Restores the databases for the specified nodes.
node_name Specifies the node to be backed up. You can specify multiple nodes.
See the description of the wbkupdb command in the Tivoli Management Framework Reference Manual for more options.
Examples: The following example backs up the Tivoli databases for all managed nodes in the Tivoli management region from which the wbkupdb command is run. The backups are written to the user-defined file /usr/backups/TMR1.bk. wbkupdb -d /usr/backups/TMR1.bk
The following example backs up the database of a single managed node, sherman. Use the wchkdb command to determine the names of databases that exist in the Tivoli management region. In this example, the backup file is saved to the default location, which is the backups directory in the Tivoli database directory. The backups directory is created if it does not exist when you run the wbkupdb command. wbkupdb sherman
The following example restores a single managed node, sherman. The -r flag restores the backed up database on sherman. The -d flag identifies /usr/backups/TMR1.bk as the backup file to restore. wbkupdb -r -d /usr/backups/TMR1.bk sherman
Tivoli desktop:
Note: The default directory to which backup files are written has root write permissions only. If you cannot log in as the root administrator, you must change the location of the backup file to a directory for which you have write access.
1. Select Backup from the Desktop menu to display the Backup Tivoli Management Region dialog box.
2. Select one or more managed nodes from the Available managed nodes scrolling list.
3. Click the left-arrow button to move them to the Backup these managed nodes area.
4. Type the name of the managed node on which the backup image or device is located in the Save image on node field.
5. Type the full path name for the backup file in the Device/File field. 6. Click the Estimate Backup Size button to see the estimated backup size
required for each managed node. Be sure that sufficient disk space exists for the target directory.
7. Click Close to display the Backup Tivoli Management Region dialog box. 8. Click Start Backup to display the Backup Status dialog box and begin backup
operation. 9. Click Close to close the Backup Tivoli Management Region dialog box and
display the Desktop window.
Handling security across firewalls Tivoli Management Framework, Version 3.7.1, enables security across firewalls for IBM Tivoli Monitoring for Applications. To protect privacy and data integrity, you can choose options such as Bulk Data Transfer (BDT) proxy mechanism, Secure Socket Layer 3 (SSL3) encryption support or the features of the Tivoli Management Framework Firewall Security Toolbox.
Firewalls often restrict communication by ports, by protocols, and by direction. For example, a firewall might allow communications from the Internet using port 80 and the HTTP protocol. Tivoli Management Framework features can work with a company’s firewall security requirements as follows: v Limit the ports used for Tivoli management communications v Use Tivoli relay functions to navigate across multiple security zones v Limit Tivoli communications to unidirectional transactions
The following table lists the security features available for Tivoli Management Framework and where to obtain the features:
Table 6. Firewall security features of the Tivoli Management Framework
Security feature Where to obtain it Description
Single Port Bulk Data Transfer
Included in the version of Tivoli Management Framework that ships with this product. See the Tivoli Management Framework documentation for further information.
Consolidates communications between servers and gateways to a single port. For example, this feature can consolidate software distribution transactions to a single port.
Endpoint Upcall Port Consolidation
Included in the version of Tivoli Management Framework that ships with this product. See the Tivoli Management Framework documentation for further information.
Channels all communication between an endpoint and its gateway through the listening port of the endpoint’s enabling software, the Tivoli Management Agent. Without this feature, Tivoli uses multiple ports for some transactions, including dynamically allocated ports, which are especially difficult to secure.
Table 6. Firewall security features of the Tivoli Management Framework (continued)
Security feature Where to obtain it Description
Tivoli Firewall Solutions Toolbox
Patch 1.2-TFST-0001. Download from the Customer Support Web site at http://www.tivoli.com/support.
Enables these security features:
v Endpoint and gateway proxies to consolidate communication between multiple endpoints and gateways into a single port using a TCP protocol.
v Use of multiple relay functions to safely pass Tivoli information through a series of firewall sectors called Demilitarized Zones (DMZs).
v Unidirectional communication that stores endpoint data at a proxy gateway outside a firewall until the original gateway calls for the data at scheduled intervals. You locate the original gateway inside a firewall so that the call transactions for Tivoli always originate from the more secure side of the network.
v Event Sink for collecting events on an endpoint outside a firewall. A Tivoli Enterprise Console server inside a firewall can poll the Event Sink and capture the events as Tivoli events, even events that have originated from computers that are not part of the Tivoli environment.
Unlike the other elements of the firewall solutions toolbox, the Event Sink requires that you install a Tivoli endpoint on the system. The Event Sink passes the events it receives to the endpoint. The endpoint can send a secure instance of the event through the Tivoli Management Framework to the Tivoli Enterprise Console server.
Firewall documentation For further information on security and firewall issues, refer to the following documentation: v Tivoli Enterprise Management across Firewalls, Redbook number: SG24-5510-01
Provides background information and includes scenarios that refer to IBM Tivoli Monitoring.
v Tivoli Firewall Magic, Redpaper number: REDP0227 Provides an overview of firewall features in the Tivoli Management Framework.
v Tivoli Management Framework: Release Notes, Version 3.7.1, GI11-0836-00 Provides information about security and new command options.
v Tivoli Management Framework: Planning for Deployment Guide, Version 3.7.1, GC32-0393-01 Provides information about Secure Sockets Layer Data Encryption.
v IBM Tivoli Monitoring, Version 5.1.1: User’s Guide, SH19-4569-01 Describes security capabilities of the Web Health Console. This console runs independently from the Tivoli Management Framework and has unique mechanisms for communicating with the other components across or within a firewall.
Verifying that the required software is running
Objective To confirm that software required to enable Tivoli transactions is running on the remote target computers that you configure during installation.
Background information One of the following basic execution daemons must be running on managed nodes and endpoints to enable Tivoli transactions: v For installation on UNIX target computers, test the rexecd daemon. v For installation on Windows target computers, test the Tivoli Remote Execution
Service (TRIP) process.
Before you begin None
When you finish Install the product using one of the following methods: v Chapter 4, “Performing a Typical installation” on page 23 v Chapter 5, “Performing a Custom installation” on page 33 v Chapter 6, “Installing the product manually” on page 55
Procedure You can perform this procedure from the command line only.
Command line to a UNIX target computer:
1. Run an rexec command string against the target computer. The rexec command runs commands on remote hosts that are running the rexec service. For example, run the following command: rexec <target_computer_name> echo test
2. Respond to the prompt for a user ID and password by typing the root ID and password. If the command is unsuccessful, you receive an error, for example, an authentication error, a notice that the server is down, or a notice that rexec failed to run. Do not continue installing this product until you can enable the rexec daemon on the target computer.
Command line to a Windows target computer:
1. Run an rexec command string against the target computer. The rexec command runs commands on remote hosts that are running the rexec service. For example, run the following command: rexec <target_computer_name> cmd /c echo test
2. Respond to the prompt for a user ID and password by typing the Administrator ID and password.
3. If the command is unsuccessful, you receive an error, for example, an authentication error, a notice that the server is down, or a notice that the process failed to run. Do not continue installing this product until you complete these steps: a. Log on to the target computer on which you want to confirm that the Tivoli
Remote Execution Service exists. b. Access the Services user interface in the Windows control panel. c. Find the Tivoli Remote Execution Service in the Services list and perform
one of the following actions: v If this service exists and the status is Stopped, click the Start button.
—OR—
v If this service exists and the status is Started, resolve firewall blocks or other network connectivity problems between this computer and the computer on which you are installing IBM Tivoli Monitoring. For example, you can increase access privileges to resolve some types communication failure. —OR—
v If this service does not exist, run the setup.exe executable in the TRIP directory of the software installation CD for Tivoli Management Framework. Follow the instructions in the panels of the installation wizard for this service.
Completing installation planning sheets A planning.html planning sheet exists in the root directory of the documentation CD for IBM Tivoli Monitoring for Applications. Use the planning sheet to plan the installation of IBM Tivoli Monitoring for Applications. You can open this .html file in an HTML editor, a word processor, or a spreadsheet application and type the values for your installation plan. You can also photocopy the sheets in this document or print the sheets from the PDF version of this document and complete them by hand.
This section describes the following types of managed resources that each planning sheet covers: v Managed nodes and the gateway on each managed node. v Endpoints.
Table 7. Managed resources and their purpose
Managed resource Purpose
Managed nodes Create managed nodes on servers to supplement the Tivoli management region server. A managed node runs the same software that runs on a Tivoli server. It can communicate with other managed nodes and can help the Tivoli server manage endpoints. When a managed node supplements the Tivoli server, the managed nodes share the processing burden of the Tivoli server. The Tivoli server works more efficiently because it performs fewer management and user administration operations.
Gateways Create gateways on managed nodes to enable the managed node to perform endpoint management operations on behalf of the Tivoli management region server. A gateway transfers large amounts of data to endpoints more efficiently. By default, the maximum amount of memory to use for storing transient data is set to 10 MB. Always enable managed nodes for IBM Tivoli Monitoring for Applications as gateways so that they can perform endpoint management operations.
When you use the Typical path in the installer for this product, the installer automatically establishes gateways on the managed nodes you create during installation. Be sure to create gateways on managed nodes that you create during a Custom installation or during an installation through an existing Tivoli environment. See “Installation options” on page 17 for more information on installation options.
Endpoints Create endpoints on the computers that you want to manage. Endpoints communicate with the Tivoli management region through a specific gateway on a managed node.
Use the following planning sheets to compile the information you need during installation: v Planning sheet for creating managed nodes in Table 8 on page 20 v Planning sheet for creating endpoints in Table 9 on page 21
Ta bl
e 9.
P la
nn in
g sh
ee t
fo r
cr ea
tin g
en dp
oi nt
Chapter 4. Performing a Typical installation
Objective To use an installation wizard with predefined default values to automatically create a Tivoli environment and install IBM Tivoli Monitoring for Applications. The wizard optionally creates managed resources in the Tivoli environment, as described in this procedure.
Note: Perform a Custom installation option if you are installing the Tivoli management region server on a UNIX computer and you want to create Windows endpoints. See Chapter 5, “Performing a Custom installation” on page 33. The Custom installation also provides more control over file-naming and other installation details.
Background information The target computer, which becomes the Tivoli management region server, must match one of the following profiles: v Has no software installed for the Tivoli Management Framework.
—OR— v Has Tivoli Management Framework, Version 3.7, Revision A or Revision B,
installed. You cannot install this product on systems that run previous versions of the Tivoli Management Framework.
v Has Tivoli Management Framework, Version 3.7.1, installed but does not have the required patches
Tivoli recommends that you close all other applications during an installation. For Windows installations, the installer requires that you restart the computer.
When you are installing a Tivoli management region server on a Windows operating system, the installer automatically creates the Windows proxy endpoint so you can create Windows endpoints in the domain of the Tivoli management region server.
You can also create managed nodes after installation.
Details of the Step List panel of the installer: “Background information” on page 105 describes the status icons and buttons of the Step List panel.
Required authorization On UNIX, the user who installs the product must have root privileges. On Windows, the user who installs the product must have membership in the Administrators group.
Before you begin See Chapter 2, “Guidelines for installation and setup” on page 5 for a checklist of activities prior to installation.
When you finish Complete the activities described in Chapter 7, “Completing the installation of the product” on page 73
23
Procedure 1. Log on to the computer that you want to be the main Tivoli server for the
Tivoli management region. 2. Run the setup executable in the root directory of the installation CD labeled
IBM Tivoli Monitoring for Applications, Version 5.1.0: Installation. Additional Information: The executable launches the IBM Tivoli Monitoring for Applications installer. Select the executable that matches your operating system: v For Windows, run setupAPP.bat
v For UNIX, run ./setupAPP.sh
3. Click Next. The installer panel displays the name of the product that it is installing.
4. Click Next to display the license agreement.
Note: When you click the Cancel button in an installer panel, you stop the installation.
5. Select ″I accept the terms of the license agreement″ and click Next to set the target directory for installation.
6. Specify the directory path where you want to install the product. Additional Information: This prompt does not display if you are installing the product into an existing Tivoli management region.
7. Specify a directory path to an installation depot (temporary directory) that is accessible from the target computer.
Note: On Windows, the depot must reside on the target computer. You cannot perform an installation of the product on Windows using a depot that is located on a remote system. On UNIX, provide a directory path that is accessible from the installation computer to the installation depot.
Additional Information: The depot directory contains all the files required for installation. After the installation is complete, the installer provides an option to automatically delete this directory.
If you click Cancel in an installer panel always delete the temporary depot directory. You can begin installation again by running the setup executable on the installation CD.
8. Click Next when the installer prompts you to restart the application and continue the installation.
9. Click Next to display the password panel. 10. Type the password for the user who is listed under User ID in the Password
field. Additional Information: If you enter an invalid password in the Password and Verify Password fields, the installer accepts it. The installer detects the error when it begins to install the software, and it displays an error message in the Step Detail dialog box. You can correct the error at that time.
11. Type the password again in the Verify Password field and click Next to display the license key panel.
12. Type the Tivoli Management Framework license key. Additional Information: Obtain this key in the printed document that comes with the installation CDs for the Tivoli Management Framework.
This prompt does not display if you are installing the product into an existing Tivoli management region.
13. Click Next to display the language options panel. 14. (Optional) Select languages that you want to enable for users of the product.
Additional Information: English is always enabled for this product. The installer installs the language enablement packages for additional languages that you choose.
15. Click Next.
16. Select the Typical option and click Next to display the introductory screen for creation of managed nodes.
17. Click Next to display a list of managed nodes. Additional Information: At least one managed node is displayed in the list. This managed node is the Tivoli management region server that the product creates automatically on the computer on which you install this product. The installer also discovers and lists any managed nodes created in a previous installation of Tivoli Management Framework, Version 3.7 or Version 3.7.1. You cannot edit or delete existing managed nodes.
18. (Optional) Click Add to create additional managed nodes through the Add a Managed Node tabbed dialog box.
Figure 2. Typical Installation: Typical option panel
Chapter 4. Performing a Typical installation 25
Additional Information: Make settings in both the Basic tab and the Advanced tab before you click OK to save the settings. When you click the OK, you save settings for both the Basic tab and the Advanced tab.
19. Follow these steps to create a managed node: a. Click the Basic tab. b. Specify values for the managed node in the fields of the Basic tab:
v Host Name — Type the fully qualified host name for the computer on which you create the managed node. For example, the fully qualified host name for tokyo might be tokyo.sales.mycompany.com.
v Platform — Click the drop-down list and select the name of the operating system on the managed node.
v User — Type the login user ID of the person who performs the installation on the managed node. Tivoli recommends that you use Administrator for Windows platforms, and root for UNIX platforms.
v Password and Verify Password — The login password of the user specified in the User field.
c. Click the Advanced tab.
d. Specify values in the fields of the Advanced tab. v Destination — (Optional) A customer path on the target machine where
you want to install the Tivoli software. Otherwise, Tivoli uses the default path specification.
v Reboot — You must select this check box when you add Windows managed nodes to the Tivoli management region. The managed node software is activated after you restart the Windows computer.
Figure 3. Typical Installation: Basic tab for managed nodes
Figure 4. Typical Installation: Advanced tab for managed nodes
e. Click OK to save your settings and return to the installer. 20. Click Next to display the panel for selection of product components. 21. Select the component or components that you want to install. 22. Click Next to display a list of managed nodes. 23. Select the check box beside each managed node on which you want to install
the component or components you selected in Step 21. Additional Information: When the component is already installed on a managed node, the row is not in edit mode. The check box is selected and you cannot modify it.
24. Click Next to display the Web Health Console panel. 25. (Optional) Install the Web Health Console as follows:
a. Click Install the Health Console. b. Click Next to display the list of available managed nodes. c. Place a check mark in the Web Health Console column beside the name of
each managed node on which you want to install the console. Additional Information: When you specify the installation of the Web Health Console on a pre-existing managed node, you must supply the user ID and password. Select the name of the managed node and click Edit to supply the password. If the Web Health Console is already installed, do not place a check mark here. Otherwise, the console is installed again because the installer cannot detect previous installations of the console.
26. Click Next to display the endpoint option panel. 27. (Optional) Create endpoints for Tivoli to monitor and manage. (You can also
create endpoints after installation, as described in “Installing endpoints through an existing Tivoli environment” on page 60.) Additional Information: By default, the installer for IBM Tivoli Monitoring for Applications assigns endpoints to managed nodes whenever possible. The installer assigns endpoints to the Tivoli management region server only when no managed node is available. If you want to change gateway assignments for an endpoint after installation, see “Changing the gateway assignment of an endpoint” on page 88. a. Click Create endpoints. b. Click Next.
Additional Information: The installer displays a list of existing endpoints, if any. You cannot use the installer to edit or delete existing endpoints.
c. Click Add to display the Add an Endpoint tabbed dialog box.
d. Click the Basic tab. e. Specify values for the endpoint in the fields of the Basic tab:
v Host Name — Type the fully qualified host name for the computer on which you create the endpoint. For example, the fully qualified host name for tokyo might be tokyo.sales.mycompany.com.
v Label — Type a unique name for the endpoint. This name can include alphanumeric characters, underscores (_), hyphens (-), and periods (.). The names are case-sensitive. For example, the name EPName is different from epname.
v Platform — Click the drop-down list and select the name of the operating system on the endpoint.
v User — Type the login user ID of the person who performs the installation on the endpoint. Tivoli recommends that you use Administrator for Windows platforms, and root for UNIX platforms.
v Password and Verify Password — The login password of the user specified in the User field.
f. Click the Advanced tab.
g. Specify values in the fields of the Advanced tab, if necessary. v Port — A port number dedicated to communication with the Tivoli
server. The default is 9495. v Destination — Path on the target machine where you want to install the
Tivoli software.
v Reboot — You must select this check box when you add Windows endpoints. The endpoint software is activated after you restart the target Windows computer.
h. Click OK to save your settings and continue installation in the installer panels.
28. Click Next to display a series of panels in which you specify the path for software. Additional Information: You specify the path to the installation CDs that contain the software listed in the following table. Type a directory path or click the Browse button to specify the path to CD.
Note: The installer also prompts you for Language Support CDs, if you specified a language support option earlier in the installation process.
Table 10. Software locations on installation CDs
Software to install CD on which software is located
1. Version 3.7, Revision B, of the Tivoli Management Framework
Tivoli Management Framework V 3.7, Revision B
2. Version 3.7.1 of the Tivoli Management Framework
Tivoli Management Framework Upgrade from 3.7 to 3.7.1
3. IBM Tivoli Monitoring software IBM Tivoli Monitoring V5.1.1
4. IBM Tivoli Monitoring for Applications
IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com Component Software
IBM Tivoli Monitoring for Applications, Version 5.1.0: Siebel eBusiness Applications Component Software
Depending on your choice of products earlier in the installation process, the installer prompts you for one or both CDs.
5. IBM Tivoli Monitoring Web Health Console
Tivoli Monitoring Web Health Console for AIX, HP, SUN v5.1.1
Tivoli Monitoring Web Health Console for Win, Linux v5.1.1
6. IBM Tivoli Monitoring Language Support
IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com Language Support
IBM Tivoli Monitoring for Applications, Version 5.1.0: Siebel eBusiness Application Language Support
29. Click Next to access the Step List panel of the installer. Additional Information: The Step List shows the software components that the installer installs, and it displays status updates for the installation process. See “Troubleshooting installer problems” on page 105 for a description of status icons and buttons in the Step List panel.
30. (Optional) If you want to cancel the installation while the Step List is running, perform the following steps: a. Click the Stop button and allow the currently running process to finish.
Additional Information: If you click Cancel without allowing the currently running process to finish, the system might remain in an unpredictable state.
b. Click Cancel to stop the installation and close the installer. c. Delete the temporary depot directory created by the installer.
31. See “Troubleshooting installer problems” on page 105 for information on working around or resolving the following types of problems in the installer: v Errors v Invalid user names and password for target computers v Deferred steps v Failed steps
32. (Optional) Double-click any item in the list to see details and to set processing instructions for that step in the Detail dialog box. Table 24 on page 107 describes the status icons and buttons of the Detail dialog box. Additional Information: The installer automatically enables you to create Windows endpoints. However, this capability exists only when you are installing the Tivoli management region server on a Windows operating system. In UNIX-based installations, you must manually enable installation of Windows endpoints while the Step List is running, as described in “Manually creating a Windows proxy endpoint” on page 50.
33. Click Run All to begin running the Step List. 34. Click OK in the final prompt of the Step List.
Figure 7. Sample Step List panel
Additional Information: This final prompt is displayed when all steps in the Step List show a Passed status. If all steps do not show a Passed status, see “Troubleshooting installer problems” on page 105 for troubleshooting information.
35. Click Next. 36. Select one of the following options:
v Delete the temporary files. Select this option to delete the directory of temporary installation files that you specified in at the beginning of the installation process. —OR—
v Do not delete the temporary files. Select this option to keep the temporary files. You can manually delete the files at any time.
37. Click Next. 38. Click Finish.
Chapter 5. Performing a Custom installation
Table 11 lists the goals of performing a Custom installation of IBM Tivoli Monitoring for Applications.
Table 11. Custom installation goals
Goal Refer to
Install IBM Tivoli Monitoring for Applications using the Install wizard and related Planner tool.
“Installing IBM Tivoli Monitoring for Applications” on page 33
Manually create a Windows proxy endpoint on a UNIX-based Tivoli management region server.
“Manually creating a Windows proxy endpoint” on page 50
Installing IBM Tivoli Monitoring for Applications
Objective To use the installer and related Planner tool to install IBM Tivoli Monitoring for Applications.
Background information The Custom installation method offers the following benefits: v You see all target computers in a single tree view for quick reference. v You control the naming of managed resources. (Naming is automatic in the
Typical installation method.) v You control the specification of target directories. For example, you can set a
customized path for the Tivoli database files. (You must accept the default directory paths in the Typical installation method.)
v You can export a Custom installation plan. In a later installation session you can import the plan to restore its specifications. The imported configuration plan overwrites all existing settings the Planner. Step 30 on page 47 describes this process.
Note: When you use the Custom installation path, you should define at least one gateway, as described in this procedure. If no gateway is defined, a severe error can occur that prevents the deployment process from proceeding. This error does not occur in the Typical installation path because in that option gateways are defined automatically.
The target computer, which becomes the Tivoli management region server, must match one of the following profiles: v Has no software installed for the Tivoli Management Framework.
—OR— v Has Tivoli Management Framework, Version 3.7, Revision A or Revision B,
installed. You cannot install this product on systems that run previous versions of the Tivoli Management Framework.
Tivoli recommends that you close all other applications during an installation. For Windows installations, the installer requires that you restart the computer after the following events:
33
v Creation of the user ID for the Tivoli Management Framework software v Installation of the Tivoli Management Framework software
When you are installing a Tivoli management region server on a Windows operating system, the installer automatically creates the Windows proxy endpoint so you can create Windows endpoints in the domain of the Tivoli management region server. When you are installing the Tivoli management region server on a UNIX-based operating system, see “Manually creating a Windows proxy endpoint” on page 50.
Details of the Step List panel of the installer: “Background information” on page 105 describes the status icons and buttons of the Step List panel in the installer.
About the Planner tool: The Custom installation method features a Planner that enables you to specify all elements to install. You must use the Planner tool while you perform a Custom installation.
The Planner makes no changes to any computer. After you complete actions in the Planner, you return to th

IBM Tivoli Monitoring for Applications

Documents

Transcript of IBM Tivoli Monitoring for Applications