Installation and Setup Guide

Transcription

1 IBM Tioli Monitoring for Messaging and Collaboration Installation and Setup Guide Version GC

2

3 IBM Tioli Monitoring for Messaging and Collaboration Installation and Setup Guide Version GC

4 Note Before using this information and the product it supports, read the information in Appendix F, Notices on page 147. Second Edition (December 2002) This edition applies to ersion of IBM Tioli Monitoring for Messaging and Collaboration and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures Tables ii About this guide ix Who should read this guide ix What this guide contains ix Publications x Documents for this product x Related publications xi Accessing softcopy publications xii Using the guide online xii Viewing online help xii Ordering publications xii Proiding feedback about publications.... xii Accessibility xiii Contacting Customer Support xiii Conentions used in this guide xiii Terminology xiii Typeface conentions xiii Tioli command syntax xi Chapter 1. Oeriew Choosing an installation method Elements of a basic installation Chapter 2. Guidelines for installation and setup Chapter 3. Pre-installation System requirements for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino... 7 Supported operating systems Required and optional software Disk space requirements Other prerequisites Backing up and restoring Tioli databases Handling security across firewalls Working with z/os systems across firewalls.. 16 Related documentation on firewalls Verifying that required software is running Completing installation planning sheets Chapter 4. Performing a Typical installation Chapter 5. Performing a Custom installation Performing a Custom installation Manually creating a Windows proxy endpoint Chapter 6. Installing the product manually Using Tioli Software Installation Serice Accessing the Tioli enironment Installing managed nodes through an existing Tioli enironment Installing Tioli patches manually Upgrading IBM Tioli Monitoring manually Manually installing Tioli software Installing endpoints through an existing Tioli enironment Installing the Web Health Console manually Installing the Management Console manually Chapter 7. Completing the installation 75 Verifying the installation of the product Changing the gateway assignment of an endpoint 76 Installing the Jaa Runtime Enironment Linking to an existing Jaa Runtime Enironment 78 Installing files to enable customization of resource models Installing files to enable Tioli Enterprise Data Warehouse Installing IBM Tioli Language Support for this product Updating Web Health Console files Chapter 8. Migrating from preious ersions of the product Migrating from preious Tioli software Mapping monitors to resource models Mapping Tioli Manager for Domino tasks Mapping Tioli Manager for Domino commands.. 94 Chapter 9. Installing and configuring the Lotus Domino component for z/os. 97 Tioli enironment for Monitoring for Lotus Domino in z/os systems Configuring timeouts for Tioli gateways Installing Monitoring for Lotus Domino for z/os on a z/os system Configuring Tioli NetView for z/os for monitoring Configuring the z/os security enironment to accept monitoring operations Installing the task serer for the first time Configuring the Tioli Business Systems Manager task serer to communicate with z/os systems Starting communication between the task serer and z/os Appendix A. Problem determination 111 Troubleshooting installer problems About the log files for installation errors Problems and workarounds Testing endpoint connectiity iii

6 Cleaning up and remoing the endpoint Appendix B. Installation messages 125 Appendix C. Uninstalling the product 139 Uninstalling the product s endpoints Uninstalling the product s managed nodes Uninstalling the Management Console Appendix D. Patches Appendix E. Accessibility Using Assistie Technologies Magnifying What is Displayed on the Screen Documentation in Accessible Formats Using Alternatie Text Appendix F. Notices Trademarks Index i IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

7 Figures 1. Typical installation of a Tioli management region Typical Installation: Typical option panel Typical Installation: Basic tab for managed nodes Typical Installation: Adanced tab for managed nodes Typical Installation: Basic tab for endpoints Typical Installation: Adanced tab for endpoints Step List panel sample Custom Installation: Region iew in the Planner Custom Installation: Custom option panel Custom Installation: Adding a managed node in the Planner Custom Installation: Setting managed node properties in the Planner Custom Installation: Adding a gateway in the Planner Custom Installation: Associating a gateway with a managed node in the Planner Custom Installation: Adding an endpoint in the Planner Custom Installation: Setting endpoint properties in the Planner Custom Installation: Adding the Web Health Console in the Planner Step List panel sample Tioli enironment for monitoring Lotus Domino for z/os Step List installer panel sample Detail dialog box of the Step List panel 114

8 i IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

9 Tables 1. Guidelines for installation and setup Supported operating systems for managed nodes Supported operating systems for endpoints 8 4. Disk space requirements for installing the Tioli enironment Firewall security features of Tioli Management Framework Managed resources and their purpose Planning sheet for creating managed nodes Planning sheet for creating endpoints Planning sheet for creating proxy managed objects Software locations on installation CDs Remoal of planner elements and possible consequences Guidelines for installing the product through an existing Tioli enironment Manual installation: Specifications of required patches Product locations on installation CDs Guidelines for completing the installation of the product Language support and names of corresponding installation index (.IND) files Guidelines for migrating from preious ersions of the product Tioli Manager for Domino monitors and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino resource models and proiders Tioli Manager for Domino proiders and the corresponding Tioli Manager for Domino monitors Tioli Manager for Domino tasks and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino tasks Tioli Manager for Domino commands and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino commands Goals for installation and configuration of Monitoring for Lotus Domino for z/os Oeriew of problem determination topics and procedures Status icons and buttons for the Step List panel of the installer Error logs and descriptions Common problems and workarounds Guidelines for uninstalling the product Patches that the installer installs automatically Patches and APARs for required and optional software ii

10 iii IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

11 About this guide Who should read this guide What this guide contains This guide describes how to install and set up IBM Tioli Monitoring for Messaging and Collaboration to monitor and manage serer resources and other objects in a Tioli enironment. This document explains how to install and set up the following basic elements of the Tioli enironment: A Tioli serer Managed nodes Managed Messaging and Collaboration computers, which are hosts for the Tioli endpoint software Readers should be familiar with the following: UNIX or Windows operating systems Messaging and Collaboration administration This guide contains the following sections: Chapter 1, Oeriew Proides an oeriew of the installation and setup of IBM Tioli Monitoring for Messaging and Collaboration. Chapter 2, Guidelines for installation and setup Proides guidelines for installing and setting up IBM Tioli Monitoring for Messaging and Collaboration. Chapter 3, Pre-installation Describes how to plan and prepare installing the product. Chapter 4, Performing a Typical installation Describes the Typical installation method. Chapter 5, Performing a Custom installation Describes the Custom installation method. Chapter 6, Installing the product manually Describes how to install the product manually. Chapter 7, Completing the installation Describes how to erify and finalize the installation of the product. Chapter 8, Migrating from preious ersions of the product Describes how to migrate to IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino software from preious ersions of the software. Appendix A, Problem determination Describes how to determine the source of common problems and suggests solutions. Appendix B, Installation messages Describes installation messages that the product can generate. ix

12 Appendix C, Uninstalling the product Describes uninstallation of the product. Appendix D, Patches Proides a list of required patches. Appendix E, Accessibility Describes accessibility features of the product. Appendix F, Notices Proides information on copyrights and trademarks. Publications This section lists publications in the IBM Tioli Monitoring for Messaging and Collaboration library and any other related documents. It also describes how to access Tioli publications online, how to order Tioli publications, and how to submit comments on Tioli publications. Documents for this product The following lists mention documents that proide detailed information on the product. Read the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1, Release Notes for updated information that could not be included in the documents that come with the product. The following documents describe how to use IBM Tioli Monitoring for Messaging and Collaboration and are included on the documentation CD in Portable Document Format (PDF) format and in HTML format: IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide, SC Proides information about how to use Tioli Manager for Messaging and Collaboration to manage Messaging and Collaboration resources. IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Reference Guide, SC Proides detailed information about Messaging and Collaboration resource models, tasks, and commands. IBM Tioli Monitoring for Messaging and Collaboration Installation and Setup Guide, GC Proides instructions for installing Tioli Manager for Messaging and Collaboration and setting it up to manage Messaging and Collaboration resources. IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1, Release Notes, GI Describes product features and proides 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. IBM Tioli Monitoring for Messaging and Collaboration Version 5.1.1: Limitations and Workarounds Supplement, SC Proides the latest information about known product limitations and workarounds. To ensure that the information is the latest aailable, this document is proided only on the Web, where it is updated on a regular basis. You can access the Limitations and Workarounds document through the IBM Tioli Monitoring for Messaging and Collaboration link on the Tioli Information Center Web site: x IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

13 Related publications The following documents proide other useful information: IBM Tioli Monitoring: Workbench User s Guide, SH Describes how to use the IBM Tioli Monitoring Workbench to create new resource models and to modify existing ones. IBM Tioli Monitoring User s Guide, SH Describes how to use the IBM Tioli Monitoring user interface. IBM Tioli Monitoring Collection Reference, SH Describes the resource models that come with IBM Tioli Monitoring software. Tioli Management Framework User s Guide, GC Describes the Tioli enironment, including profiles and profile management. Tioli Management Framework Reference Manual, SC Proides detailed information about Tioli commands. Tioli Enterprise, Version 3.7.1: Installation Guide, GC Proides information and procedures for installing and upgrading Tioli Management Framework (Tioli management region serer, managed nodes, gateways, and endpoints), and proides the procedures for installing and upgrading Tioli Enterprise products. Tioli Management Framework, Version 3.7.1: Planning for Deployment Guide, GC Explains how to plan for deploying your Tioli enironment, and describes Tioli Management Framework and its serices. Tioli Enterprise Console User s Guide, Version 3.7.1, GC Describes how to use the Tioli Enterprise Console to correlate eents and determine the seerity and relationship of those eents. Tioli Enterprise Console, Version 3.7: Rule Builder s Guide, GC Proides information about deeloping rules for managing eents with Tioli Enterprise Console with a text editor and a graphical rule builder. TME 10 Software Installation Serice User s Guide, sis36ga Describes how to use the Tioli Software Installation Serice (SIS) to install Tioli products. Tioli Business Systems Manager, Version 1.5: User s Guide Describes how to use the Tioli Business Systems Manager product. Tioli Business Systems Manager Console, Version 1.5: User s Guide Describes how to use the Tioli Business Systems Manager console. Tioli Enterprise Data Warehouse documentation Describes how to use Tioli Enterprise Data Warehouse to compile historical data to monitor your system and to help you make strategic management decisions regarding your network. Tioli Data Protection, Version 1.1.2: Installation and User s Guide Describes how to install and configure Tioli Data Protection. The Tioli Glossary includes definitions for many of the technical terms related to Tioli software. The Tioli Glossary is aailable, in English only, at the following Web site: About this guide xi

14 Accessing softcopy publications When IBM publishes an updated ersion of one or more online or hardcopy publications, they are posted to the Tioli Information Center. You can access updated publications in the Tioli Information Center from the following Customer Support Web site: The Tioli Information Center contains the most recent ersion of the books in the product library in PDF or HTML formats, or both. Translated documents are also aailable for some products. Note: If you print PDF documents on other than letter-sized paper, select the Fit to page check box in the Adobe Acrobat Print dialog. This option is aailable when you click File Print. Fit to page ensures that the full dimensions of a letter-sized page print on the paper that you are using. Using the guide online This document is aailable on the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Documentation CD in PDF and HTML formats. Refer to the readme.txt file on the CD for instructions on downloading the Acrobat Acrobat Reader, Version 3.0 or later, to iew, sae, and print the manual. Use your HTML browser to open the start.html file on the CD to access the.html documentation files. Eery naigation page also includes a link at the bottom to download the Acrobat reader for iewing, saing, and printing the files. Viewing online help Online help is aailable in seeral forms: Desktop Access online help by clicking the Help buttons in dialog boxes. 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 Tioli publications online at the following Web site: You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, see the following Web site for a list of telephone numbers: Proiding feedback about publications We are ery interested in hearing about your experience with Tioli products and documentation, and we welcome your suggestions for improements. If you hae comments or suggestions about our products and documentation, contact us in one of the following ways: Send an to pubs@tioli.com. Complete our customer feedback surey at the following Web site: xii IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

15 Accessibility Accessibility features help users who hae physical disabilities, such as restricted mobility or limited ision, to use software products successfully. With this product, you can use assistie technologies to hear and naigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface. For additional information, see the appendix on Appendix E, Accessibility on page 145. Contacting Customer Support If you hae a problem with any Tioli product, you can contact IBM Customer Support for Tioli products. See the Tioli Customer Support Handbook at the following Web site: The handbook proides information about how to contact Customer Support, depending on the seerity of your problem, and the following information: Registration and eligibility Conentions used in this guide Telephone numbers and addresses, depending on the country in which you are located What information you should gather before contacting Customer Support This guide uses seeral conentions for special terms and actions and for command syntax. Terminology This guide uses the following conentions when referring to software products and operating systems. This guide uses the term... Monitoring for Lotus Domino distributed To refer to... IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Non-z/OS platforms: AIX, HP-UX, Solaris, Windows (NT, 2000, and XP) AIX, HP-UX, and Solaris UNIX Windows Windows NT and Windows 2000 z/os z/os and OS/390 Note: This operating system includes the Multiple Virtual Storage (MVS) and UNIX System Serices (USS) enironments. Typeface conentions This guide uses the following typeface conentions: Bold Commands, keywords, file names, authorization roles, URLs, or About this guide xiii

16 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. Italic Monospace Variables and alues that you must proide appear like this, in italic. Words and phrases that are emphasized also appear like this, in italic. Code examples, output, and system messages appear like this, in a monospace font. Tioli command syntax The commands in this book use the following special characters to define Tioli command syntax: <> Indicates that the text enclosed in the angle brackets is a ariable that you supply. [] Identifies optional elements. Elements that do not hae brackets around them are required.... Indicates you can specify multiple alues for the preious element. Separate multiple alues 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 alues. 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 alues. For example, to specify two hosts for the option [ h host...], use h host1 host2. Indicates mutually exclusie information, meaning you can use the element on either the left or right of the ertical bar, but not both. {} Delimits a set of mutually exclusie 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, Tioli command syntax uses the typeface conentions described in the Preface of this guide. The following examples illustrate the typeface conentions used in Tioli command syntax: 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. wchkdb [ o outfile] [ u] [ x] { f infile i object...} The f, i, and object elements are mutually exclusie. 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. xi IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

17 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 deries from a name gien to the object by the user of the application, such as when creating a policy region. About this guide x

18 xi IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

19 Chapter 1. Oeriew This document describes installation and setup of IBM Tioli Monitoring for Messaging and Collaboration, monitoring and management software for business-critical hardware and software. The goal is to get your monitoring product up and running as quickly as possible. This document includes information on the following topics: Determining the proper installation for your enironment Information about a typical Tioli enironment Guidelines for planning your installation and setup, including worksheets Choosing an installation method Procedures for using the installation wizard or the Tioli desktop to install your monitoring product, as well as any necessary procedures for completing the installation Problem determination information for the installation wizard Guidelines for migrating or updating from the existing Tioli Manager for Domino installations. The IBM Tioli Monitoring products offer seeral options for installing the software, depending on the complexity of your enironment and your knowledge of Tioli management systems. Your choices include the following: Installation wizard The installation wizard (referred to in this guide as the installer) creates a complete Tioli enironment, if none exists, and installs the product. The installer also installs supplemental software, such as the Jaa runtime enironment and language packs. Use the installer if you hae no preious Tioli software installations or you hae Tioli Management Framework, Version 3.7, Reision A or Reision B, installed. If you use the installation wizard, 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: You want to install the product on a target computer that matches one of the following profiles: Has no software installed for the Tioli Management Framework. OR Has one of the following ersions of the Tioli Management Framework installed: Version 3.7 (Reision A or Reision B) or Version You cannot install this product on systems that run preious ersions of the Tioli Management Framework. You are a first-time Tioli user. Your enironment 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 iew of the entire installation and proides additional control oer directory paths and naming conentions. See Chapter 5, Performing 1

20 a Custom installation on page 35. Use the Custom installation option if you are installing the Tioli management region serer on a UNIX computer and you want to create Windows endpoints. Tioli desktop and command line interface Use one of these options if you are an current Tioli user with earlier ersions of the Tioli Management Framework. You might also want to use one of these options if you hae expert knowledge of the Tioli enironment and plan to extensiely customize your installation. The manual installation method enables you to create interconnected Tioli management regions and to create enironments with more than 50 endpoints. Chapter 6, Installing the product manually on page 55 proides manual installation instructions. For further information, see the documentation on the Tioli Management Framework software CDs that come with IBM Tioli Monitoring for Messaging and Collaboration. Tioli Software Installation Serice (SIS) For information about obtaining and using this installation option, go to the following Web site: Also see Using Tioli Software Installation Serice on page 55. Setting up Monitoring for Lotus Domino on z/os The Tioli Business Systems Manager task serer enables communication between Tioli distributed enironments and z/os enironments. For more information about working with z/os systems, see Chapter 9, Installing and configuring the Lotus Domino component for z/os on page 97. The term task serer and the term Tioli Business Systems Manager eent enablement are used to refer to software that enables communication between Tioli distributed enironments and z/os enironments. The task serer is a component of Tioli Business Systems Manager eent enablement. Elements of a basic installation This section describes a basic Tioli enironment. The installer creates a basic Tioli enironment during the Typical installation. During the Typical or Custom installation, you can create the following elements: One required Tioli management region serer to monitor endpoints. The Tioli serer runs the Tioli Management Framework and IBM Tioli Monitoring software. A managed node computer system on which Tioli Management Framework is installed. Each managed node has gateway software that increases performance in the Tioli enironment by reducing traffic on the Tioli management region serer. The IBM Tioli Monitoring software also runs on managed nodes. 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 Tioli software is installed to enable communication with a Tioli management region serer. One Web Health Console on any computer in the same network as the Tioli management region. If you use the installation wizard, you can automatically 2 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

21 install the console on endpoints or managed nodes that you select. The console shows the status and health of a serer in a Web browser. You can create an unlimited number of Web Health Consoles. Web Health Consoles hae the following characteristics: Can exist on an unlimited number of computers. Can display the status of resources for an unlimited number of Tioli management regions Require the deployment of the Jaa Runtime Enironment, Version 1.3, on the host computer. The Tioli enironment is software based on the Tioli Management Framework that addresses network computing management issues across many platforms. In a Tioli enironment, a system administrator distributes software, manages user configurations, changes access priileges, automates operations, monitors resources, and schedules jobs. Chapter 1. Oeriew 3

22 A Tioli enironment spans multiple computers, as shown in Figure 1. A large company might hae hundreds of managed nodes with gateways that monitor thousands of endpoints, which you will set up using one of the installation methods. Figure 1 shows a typical installation of a Tioli management region. 1. Tioli management region serer This serer is required. It monitors endpoints and runs the Tioli Management Framework and IBM Tioli Monitoring software. 2. Managed node with gateway The managed node shares the processing load of the Tioli management region serer, runs the software, and communicates with its assigned endpoints. The managed nodes allow the Tioli serer to work more efficiently because it performs fewer management and user administration operations. Tioli network transactions flow to multiple serers instead of just to the Tioli serer. Gateways enable a managed node to perform endpoint management operations for the Tioli management region serer. A gateway transfers large amounts of data to endpoints. 3. Endpoints An endpoint is a computer system on which Tioli software is installed to enable monitoring. 4. Web Health Console The 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 Tioli management region serer. The Web Health Console has the following characteristics: Can exist on an unlimited number of computers. Can display the status of resources for an unlimited number of Tioli management regions. Figure 1. Typical installation of a Tioli management region 4 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

23 Chapter 2. Guidelines for installation and setup Table 1 summarizes the procedures for installing and setting up IBM Tioli Monitoring for Messaging and Collaboration. It also tells where you can find the information and procedures that guide you through the installation. Table 1. Guidelines for installation and setup What you do Before Installation 1. Check the system for compliance with the system requirements and set up or check the prerequisite software. 2. Back up an existing Tioli enironment, if you hae one. If you encounter a problem during an installation, use the backup to restore the enironment to a known working state. 3. Complete the planning sheets for the managed nodes and endpoints that you want to create. (Optional) 4. Make sure Tioli monitoring actiity works across your network firewalls. 5. If you hae a Solaris Operating Enironment (referred to in the remainder of this document as Solaris), you must install certain fix packages on the target computer before you install the product. 6. If you hae AIX, Version 4.3.x computers, install IBM AIX maintenance package 9 to enable the installer. 7. Hewlett-Packard Company requires a set of patches for the HP-UX enironment. 8. Use the ping command to test network names of the target computers for the installation; this ensures the network recognizes the names. The target computer replies to the ping command with its IP address and statistics regarding the transaction if name is alid, the network connection is actie, and the target computer is running. 9. Confirm that the required software serices are running on the target computers. Installation Refer to System requirements for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino on page 7 Backing up and restoring Tioli databases on page 13 Completing installation planning sheets on page 19 Handling security across firewalls on page 15 Patches are aailable from the following Sun Web site: Obtain the maintenance package at the following IBM Web site: See the following Web site for the latest required patches for the HP-UX operating system: patches.html 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 where name is the name of the target computer. Verifying that required software is running on page 17 5

24 Table 1. Guidelines for installation and setup (continued) What you do 10. Install the product. The installation may include the following: managed nodes endpoints the Web Health Console Note: You can create these components after installation. You can also use the Web Health Console s executable for installation to install it on any computer. Refer to Chapter 4, Performing a Typical installation on page 25 OR Chapter 5, Performing a Custom installation on page 35 OR Chapter 6, Installing the product manually on page 55 OR After Installation 11. Back up the Tioli enironment after installation. If you encounter a problem during final configuration, use the backup copy to restore the enironment to a known state 12. Create managed nodes and endpoints if you did not create them during installation. 13. Verify the functionality of the Tioli management region by running communication commands. 14. Map monitors from preious Tioli software to resource models in IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. 15. Install software to enable resource models, the Web Health Console, historical reporting, and national language ersions of the product. 16. If you want to monitor Domino serer endpoints in z/os systems, install and configure Monitoring for Lotus Domino for z/os. Use Tioli Software Installation Serice (SIS) to install the product. For information about obtaining and using SIS, go to the following Web site: Backing up and restoring Tioli databases on page 13 Tioli Enterprise, Version 3.7.1: Installation Guide that comes with the Tioli Management Framework software. Verifying the installation of the product on page 75 Chapter 8, Migrating from preious ersions of the product on page 89 Chapter 7, Completing the installation on page 75 Chapter 9, Installing and configuring the Lotus Domino component for z/os on page Create serer objects for the product to manage. See the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide. 6 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

25 Chapter 3. Pre-installation This chapter proides the pre-installment requirements and procedures for IBM Tioli Monitoring for Messaging and Collaboration. You will find information about the following: Supported operating systems. Required and optional software. Disk space requirements. Recommendations for a basic Tioli enironment. Required permissions and priileges. Upgrades. Language requirements. TCP/IP for endpoints. Backing up and restoring the Tioli enironment. Handling security across firewalls. Verifying that prerequisite software is running. Planning and installation worksheets. Chapter 7, Completing the installation on page 75 proides procedures for product or platform-specific prerequisites. For example, you must run the DMLinkJre task on endpoints to ensure that IBM Tioli Monitoring can access the Jaa runtime enironment. System requirements for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino This section lists supported operating systems, related software, and other prerequisites for installing IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. Supported operating systems This section lists the operating systems that work with managed nodes or endpoints for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. Table 2. Supported operating systems for managed nodes Supported operating systems for managed nodes Version Monitoring for Lotus Domino Valid for all types of Tioli managed resources, besides endpoints. AIX Yes HP-UX 2, Yes Solaris 1 2.6, 2.7, 2.8 Yes Windows NT Serice Pack 4 or Yes higher Windows Serer, Adanced Yes Serer, Data Center, XP Linux (Intel) 4 Version 2.4 Kernel No 7

26 Table 2. Supported operating systems for managed nodes (continued) Supported operating systems for managed nodes Version Monitoring for Lotus Domino OS/ No z/os 4 1.1, 1.2, 1.3, 1.4 No Notes: 1. For this operating system, Monitoring for Lotus Domino supports Version 4.6 and Version 5.0 of Lotus Domino. 2. Lotus Domino is not aailable for this operating system. 3. The Tioli Business Systems Manager task serer is not aailable for this platform. 4. For this operating system, Monitoring for Lotus Domino supports only Version 5.0 of Lotus Domino. Table 3. Supported operating systems for endpoints Supported operating systems for managed nodes Version Monitoring for Lotus Domino Valid for all types of Tioli managed resources, besides endpoints. AIX Yes HP-UX 2, No Solaris 1 2.6, 2.7, 2.8 Yes Windows NT Serice Pack 4 or Yes higher Windows Serer, Adanced Yes Serer, Data Center, XP Linux (Intel) 4, 5 Version 2.4 Kernel Yes OS/ Yes 6 z/os 4 1.1, 1.2, 1.3, 1.4 Yes 6 Notes: 1. For this operating system, Monitoring for Lotus Domino supports Version 4.6 and Version 5.0 of Lotus Domino. 2. Lotus Domino is not aailable for this operating system. 3. The Tioli Business Systems Manager task serer is not aailable for this platform. 4. For this operating system, Monitoring for Lotus Domino supports only Version 5.0 of Lotus Domino. 5. This operating system cannot support the proxy endpoint configuration that enables monitoring of z/os systems. 6. Endpoint support is achieed through a proxy endpoint. Required and optional software This section lists the required and optional software for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. If you use a preious release of Tioli Manager for Domino, see Chapter 8, Migrating from preious ersions of the product on page 89. 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. 8 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

27 Product Release Installed by the product installer? Required software Tioli Management Framework Yes The installer automatically detects an existing installation of Tioli Management Framework, Version 3.7, Reision A or B, and upgrades it to the required Version The installer also automatically installs the required patches. Table 13 on page 61 lists the patches that the installer deploys. If you hae Tioli Management Framework, Version 3.7.1, the installation is checked to ensure that the required patches are installed. If not, the installation is upgraded. IBM Tioli Monitoring Yes The installer automatically detects an existing installation of IBM Tioli Monitoring, Version 4.1.x or Version 5.1.0, and upgrades it to the required Version IBM Tioli Monitoring for Messaging and Collaboration Yes IBM Tioli Monitoring Component Serices Yes Lotus Domino 4.6 or 5.0 No To enable monitoring of Windows endpoints: Microsoft Windows Management Instrumentation (WMI). This software comes with Windows You must install it manually on Windows NT endpoints. No To enable Unix endpoints: Jaa Runtime Enironment, Version 1.3. To enable computers that run the Web Health Console: Jaa Runtime Enironment, Version 1.3. To enable data logging on Windows NT and Windows 2000 endpoints: ODBC drier for Microsoft Access or Solaris endpoints must hae Version No No No If the endpoint does not hae Microsoft Access 2000 installed: 1. Run the mdac_typ.exe file that is proided with Microsoft Data Access Components 2.1 (or later), at 2. Install Jet 4.0 Serice Pack 3. To enable communication with z/os systems: Tioli Business Systems Manager Eent Enablement 1.5 No The following patch is required: 15-BSM-0038 Note: Patch 15-BSM-0043 supercedes 15-BSM-0038 when that patch becomes aailable. To enable communication with z/os systems: Tioli NetView for OS/390 or Tioli NetView for z/os If you use Tioli NetView for OS/390, Version 1.3, you must apply the fixes for the following APARs: OW54528 OW52785 OW46984 Tioli NetView for OS/390: 1.3 or higher Tioli NetView for z/os: No Chapter 3. Pre-installation 9

28 Product Release Installed by the product installer? Optional software Web Health Console Yes Tioli Enterprise Data Warehouse 1.1 or higher No The following patches and fix packs are required: 1.1-TDW-FP01a (Tioli Enterprise Data Warehouse 1.1 Fix Pack 1) 1.1-TDW-0005E Note: e-fix 1.1 TDW-FP02 (TEDW 1.1 Fix Pack 2) supercedes 1.1-TDW-005E when that fix pack becomes aailable. IBM Tioli Monitoring, Version 5.1.1, warehouse enablement pack IBM DB2 Uniersal Database Enterprise Edition Version No This software is required in the optional Tioli Enterprise Data Warehouse. The following patches are required for DB2: IBM DB2 Uniersal Database Enterprise Edition, Version 7.2, Fixpack TDW-002 (required e-fixes to the ersion of DB2) Tioli Enterprise Console or 3.8 No The following patches are required: TEC-0001 and TEC-0004 Tioli Inentory 4.0 No Tioli Software Installation Serice or 3.7 No Tioli Business Systems Manager 1.5 No The following patches are required: TBSM Patch 24, TBSM Patch 32, TBSM Patch 35, and 15-BSM-0038 Tioli Data Protection, with Tioli Storage Manager (TSM), Versions 4.1 or later, which enables automated backup and restore of Lotus Domino databases. Versions or later No Disk space requirements This section lists the disk space requirements for the elements in the Tioli enironment. 10 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

29 Table 4. Disk space requirements for installing the Tioli enironment Element Tioli management region serer Approximately 5GB (including temporary installation files) Managed node Approximately 1.5 GB Endpoint Approximately 100 MB (not including the optional Web Health Console) Disk space requirements The product installation requires a minimum of 1.5 GB of disk space on the Tioli management region serer and on managed nodes. Tioli Management Framework and IBM Tioli Monitoring: 500 MB 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, proide a directory path that is accessible from the installation computer to the installation depot. The installation depot (temporary directory): 2.6 GB Files that the installer places in the temporary ($TEMP or %TEMP%) directories that are defined for your operating system: 3 MB Additional information: Obtain the name of this directory by accessing the Tioli command line enironment (as described in Accessing the Tioli enironment on page 56) and entering this command: wtemp. IBM Tioli Monitoring for Messaging and Collaboration: 200 to 300 MB The optional Web Health Console requires 250 MB of disk space and 400 MB of RAM. The Jaa runtime enironment, Version 1.3.0, requires 75 MB of disk space. The Jaa runtime enironment is required on all endpoints for this product and is required on any computer that runs the Web Health Console. Tioli Management Framework and IBM Tioli Monitoring: 500 MB (Includes the space required by the gateway software that enables the managed node to communicate with an endpoint.) IBM Tioli Monitoring for Messaging and Collaboration: 200 to 300 MB The optional Web Health Console requires 250 MB of disk space and 400 MB of RAM. The Jaa runtime enironment, Version 1.3.0, requires 75 MB of disk space. The Jaa runtime enironment is required on all endpoints for this product and is required on any computer that runs the Web Health Console. The endpoint daemon for Tioli Management Framework: 2 MB The optional Web Health Console requires 250 MB of disk space and 400 MB of RAM. The Jaa runtime enironment, Version 1.3.0, requires up to 75 MB of disk space. The Jaa runtime enironment is required on all endpoints for this product and is required on any computer that runs the Web Health Console. * The space requirement for the Jaa runtime enironment aries, depending on the operating system. For example, the runtime enironment on Windows requires approximately 65 MB. Other prerequisites This section describes the other system prerequisites to consider before installing the product: Permissions and priileges About automatic upgrades Language requirements TCP/IP for endpoints Chapter 7, Completing the installation on page 75 proides procedures for product or platform-specific prerequisites. For example, you must run the DMLinkJre task on UNIX computers that hae existing ersions of the Jaa runtime enironment. Chapter 3. Pre-installation 11

30 Permissions and priileges You must hae the following key, permissions, and priileges to install the product: The license key for Tioli Management Framework. Obtain this key in the printed document that comes with the installation CDs for the Tioli Management Framework. On UNIX, the user who installs the product must hae root priileges. On Windows, the user who installs the product must hae membership in the Administrators group. Tioli recommends that you log on as root on UNIX and Administrator on Windows. A alid 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 hae 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 serer from a tokyo serer in the marketing domain called tokyo.marketing.mycompany.com. About automatic upgrades The installer automatically detects an existing installation of Tioli Management Framework, Version 3.7, Reision A or B, and upgrades it to the required Version It also installs for required patches. If you hae an earlier ersion of Tioli Management Framework, you must manually upgrade to Version 3.7, Reision A or B, or to ersion before you run the installer. The installer automatically detects an existing installation of IBM Tioli Monitoring, Version 4.1.x or Version 5.1.0, and upgrades it to the required Version If you hae Tioli Distributed Monitoring at an earlier ersion than 4.1x, you must upgrade to Tioli Distributed Monitoring Version 4.1x before you can run the installer. Chapter 6, Installing the product manually on page 55 describes how to install upgrade software through the Tioli desktop or the command line interface in that document when you do not want to use the installer. Chapter 8, Migrating from preious ersions of the product on page 89 describes how to migrate from preious ersions of Tioli monitoring products. This chapter also describes how to map Tioli monitors from preious ersions of monitoring products to resource models. Language requirements After you complete the installation, you can enable other languages in the product. See Installing IBM Tioli 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 Before or after you load the endpoint software, you must actiate the TCP/IP communication protocol serers to enable communication with the Tioli serer. See the documentation for the serer software that runs on your systems for instructions on enabling TCP/IP on a Messaging and Collaboration Serer. 12 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

31 Backing up and restoring Tioli databases Objectie To back up existing Tioli object databases for all machines in the Tioli management region so you can use these backup copies to restore them 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, you should arrange a complete backup of Tioli wheneer 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 Tioli enironment to a known working state. This procedure proides a stable and complete snapshot of the Tioli database and related files and a safer alternatie to manually compressing the database files in a.tar or.zip format. For example, when you sae a database to a.tar or.zip file, an error might occur if the Tioli object dispatcher is simultaneously writing to the Tioli database. This procedure also enables you to estimate the size of the backup files to ensure that you hae sufficient disk space in the target directory to complete the operation. You back up or restore databases using the wbkupdb command. In a large Tioli 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 Tioli management region. You must complete one wbkupdb command before you execute a second instance of the command. The Tioli Management Framework must be running on the Tioli management region serer and on the managed node whose database is being restored. Otherwise, the wbkupdb command cannot restore any database (managed node or Tioli management region serer). See the Tioli 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 hae a alid 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 Tioli desktop or in the command line interface. You can perform restore operations in the command line interface only. Command line: Use the wbkupdb command. Chapter 3. Pre-installation 13

32 wbkupdb [ d deice] [ r] [node_name...] where: d deice Specifies the file or deice to which the backup file should be saed or from which the backup file should be retrieed. 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 ariable %t. The ariable 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 TMR1Dec 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 Tioli Management Framework Reference Manual for more options. Examples: The following example backs up the Tioli databases for all managed nodes in the Tioli 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 wbkupdb command to determine the names of databases that exist in the Tioli management region. In this example, the backup file is saed to the default location, which is the backups directory in the Tioli 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 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 hae write access. 1. Select Backup from the Desktop menu to display the Backup Tioli Management Region dialog box. 2. Select one or more managed nodes from the Aailable managed nodes scrolling list. 3. Click the left-arrow to moe them to the Backup these managed nodes area. 4. Type the name of the managed node on which the backup image or deice is located in the Sae image on node field. 5. Type the full path name for the backup file in the Deice/File field. 14 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

33 6. Click Estimate Backup Size 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 Tioli 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 Tioli Management Region dialog box and display the Desktop window. Handling security across firewalls Tioli Management Framework, Version 3.7.1, enables security across firewalls for IBM Tioli Monitoring for Messaging and Collaboration. To protect priacy 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 Tioli 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. Tioli Management Framework features can compliment a company s firewall security requirements as follows: Limit the ports used for Tioli management communications Use Tioli relay functions to naigate across multiple security zones Limit Tioli communications to unidirectional transactions The following table lists the security features aailable for Tioli Management Framework and where to obtain the features: Table 5. Firewall security features of Tioli Management Framework Security feature Where to obtain it Description Single Port Bulk Data Transfer Endpoint Upcall Port Consolidation Included in the ersion of Tioli Management Framework that comes with this product. See the Tioli Management Framework documentation for further information. Included in the ersion of Tioli Management Framework that comes with this product. See the Tioli Management Framework documentation for further information. Consolidates communications between serers and gateways to a single port. For example, this feature can consolidate software distribution transactions to a single port. Channels all communication between an endpoint and its gateway through the listening port of the endpoint s enabling software, the Tioli Management Agent. Without this feature, Tioli uses multiple ports for some transactions, including dynamically allocated ports, which are especially difficult to secure. Chapter 3. Pre-installation 15

34 Table 5. Firewall security features of Tioli Management Framework (continued) Security feature Where to obtain it Description Tioli Firewall Solutions Toolbox Patch 1.2-TFST Download from the Tioli Support Web site at Enables these security features: Endpoint and gateway proxies to consolidate communication between multiple endpoints and gateways into a single port using a TCP protocol. Use of multiple relay functions to safely pass Tioli information through a series of firewall sectors called Demilitarized Zones (DMZs). Unidirectional communication that stores endpoint data at a proxy gateway outside a firewall until the original gateway calls for the data at scheduled interals. You locate the original gateway inside a firewall so that the call transactions for Tioli always originate from the more secure side of the network. Eent Sink for collecting eents on an endpoint outside a firewall. A Tioli Enterprise Console serer inside a firewall can poll the Eent Sink and capture the eents as Tioli eents, een eents that hae originated from computers that are not part of the Tioli enironment. Unlike the other elements of the firewall solutions toolbox, the Eent Sink requires that you install a Tioli endpoint on the system. The Eent Sink passes the eents it receies to the endpoint. The endpoint can send a secure instance of the eent through the Tioli Management Framework to the Tioli Enterprise Console serer. Working with z/os systems across firewalls In z/os systems, host name authentication might fail across firewalls. Your firewall system might require a custom solution. How host name authentication works in Monitoring for Lotus Domino Host name authentication adds a layer of security to IBM Tioli Monitoring for Messaging and Collaboration, based on a host name authentication algorithm. When you run the object creation task, the distributed system that is acting as the proxy endpoint is registered with the addin for IBM Tioli Monitoring for Messaging and Collaboration. After this point, the addin only accepts connections from this remote system. Any other system that attempts to make a connection is denied. This configuration preents communication across a firewall unless these conditions are met: The distributed endpoint does not reside behind a firewall unless the IP address of the client can flow through the firewall. The Domain Name System (DNS) can resole that IP address into the host name of the proxy endpoint. Troubleshooting host name authentication in Monitoring for Lotus Domino When you run the object creation task, the distributed code for IBM Tioli Monitoring for Messaging and Collaboration must be able to obtain the primary host name for the system in the Domain Name System (DNS). The task calls gethostname(), gethostbyname(), and then gethostbyaddr(). If this sequence of calls does not return the primary host name of the system, the create object task might fail. If the create serer task fails with a Domain Name System (DNS) error check the following points: 16 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

35 On Windows 2000, you must specify the full computer name in the System Properties, Network Identification properties. On Windows NT, the fully qualified host name must appear before the short name in the c://winnt/system32/etc/hosts file. On UNIX platforms, the fully qualified host name must appear before the short name in the /etc/hosts file. Chapter 9, Installing and configuring the Lotus Domino component for z/os on page 97 describes how to configure TCP/IP and other features for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino for z/os. Related documentation on firewalls For further information on security and firewall issues for Tioli products, refer to the following documentation: Tioli Enterprise Management across Firewalls, Redbook number: SG Proides background information and includes scenarios that refer to IBM Tioli Monitoring. Tioli Firewall Magic, Redpaper number: REDP0227 Proides an oeriew of firewall features in the Tioli Management Framework. Tioli Management Framework: Release Notes, Version 3.7.1, GI Proides information about security and new command options. Tioli Management Framework: Planning for Deployment Guide, Version 3.7.1, GC Proides information about Secure Sockets Layer Data Encryption. IBM Tioli Monitoring, ersion 5.1.1: User s Guide, SH Describes security capabilities of the Web Health Console. This console does not run under Tioli Management Framework and has unique mechanisms for communicating with the other components across or within a firewall. See the Enabling Secure Socket Layer Support for the Web Health Console topic for more information. Verifying that required software is running Objectie To confirm that software required to enable Tioli 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 Tioli transactions: For installation on UNIX target computers, test the rexecd daemon. For installation on Windows target computers, test the Tioli Remote Execution Serice (TRIP) process. Required authorization role On UNIX, the user who installs the product must hae root priileges. On Windows, the user who installs the product must hae membership in the Administrators group. On the Tioli system: install_product Chapter 3. Pre-installation 17

36 Before you begin None When you finish Install the product using one of the following methods: Chapter 4, Performing a Typical installation on page 25 Chapter 5, Performing a Custom installation on page 35 Chapter 6, Installing the product manually on page 55 Procedure You can perform this procedure from the command line only. Command line in UNIX: 1. Run an rexec command string against the target computer. The rexec command runs commands on remote hosts that are running the rexec serice. For example, run the following command from an xterm window: 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 receie an error, for example, an authentication error, a notice that the serer is down, or a notice that rexec failed to run. Do not continue installing this product until you can enable the rexec daemon accessible on the target computer. Command line in Windows: 1. Run an rexec command string against the target computer. The rexec command runs commands on remote hosts that are running the rexec serice. For example, run the following command from a DOS prompt: 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 receie an error, for example, an authentication error, a notice that the serer 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 Tioli Remote Execution Serice exists. b. Access the Serices user interface in the Windows control panel. c. Find the Tioli Remote Execution Serice in the Serices list and perform one of the following actions: If this serice exists and the status is Stopped, click the Start button. OR If this serice exists and the status is Started, resole firewall blocks or other network connectiity problems between this computer and the computer on which you are installing IBM Tioli Monitoring. For example, you can increase access priileges to resole some types communication failure. OR If this serice does not exist, run the setup.exe executable in the TRIP directory of the software installation CD for Tioli Management Framework. Follow the instructions in the panels of the installation wizard for this serice. 18 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

37 Completing installation planning sheets Table 6. Managed resources and their purpose A planning.html planning sheet exists in the root directory of the documentation CD for IBM Tioli Monitoring for Messaging and Collaboration. Use the planning sheet to plan the installation of IBM Tioli Monitoring for Messaging and Collaboration. You can open this.html file in an HTML editor, a word processor, or a spreadsheet application and type the alues for your installation plan. You can also photocopy the sheets in this document or print the sheets from the PDF ersion of this document and complete them by hand. Table 6 describes the following types of managed resources that each planning sheet coers: Managed nodes and the gateway on each managed node. Endpoints. Proxy managed nodes. You can use proxy managed nodes when you manage applications that hae multiple objects, such as database instances in a database application. Managed resource Managed nodes Gateways Purpose Create managed nodes on serers to supplement the Tioli management region serer. A managed node runs the same software that runs on a Tioli serer. It can communicate with other managed nodes and can help the Tioli serer manage endpoints. When a managed node supplements the Tioli serer, you achiee the following benefits: The managed nodes share the processing burden of the Tioli serer. The Tioli serer works more efficiently because it performs fewer management and user administration operations. Tioli network transactions flow to multiple serers instead of to the Tioli serer only. Create gateways on managed nodes to enable the managed node to perform endpoint management operations on behalf of the Tioli management region serer. 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 Tioli Monitoring for Messaging and Collaboration 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 Tioli enironment. See the When you finish section for more information on installation options. Endpoints Create endpoints on the computers that you want to manage. Endpoints communicate with the Tioli management region through a specific gateway on a managed node. Chapter 3. Pre-installation 19

38 Table 6. Managed resources and their purpose (continued) Managed resource Proxy managed nodes Purpose When to use: When you monitor and manage multiple objects on a single endpoint, you can use a proxy managed node to store unique information about each object. For example, multiple database objects can exist on a single endpoint. The Tioli management region serer must hae information to identify each database object, such as the name of the database and the password for the database. When not to use: You do not need a proxy managed node if the serers in the Tioli enironment do not need to store unique information about multiple objects on a single endpoint. For example, in some cases only one managed object exists on a single endpoint. If you manage serer objects for messaging products like Lotus Domino or Microsoft Exchange, the managed object is the serer itself. The Tioli endpoint that runs on the serer and the serer object together supply complete information for the Tioli serer. No proxy managed node is required because there is only one managed serer object on the endpoint. Remember that, een if a database object exists alone on an endpoint, it has unique identifiers and possibly a password that enables co-existence with other objects. The Tioli serer must hae this information. You must store this information on a gateway or consider storing it on a proxy managed node. Benefits: Proxy managed nodes are optional, but can add efficiency to the Tioli enironment. Depending on its power and location in the network, the proxy node can enable the Tioli serer to access information it needs more easily. The node also enables the Tioli serer to restore operations quicker when a gateway serer shuts down temporarily. By default, Tioli stores unique information about managed objects on the gateway. When the managed node that contains this gateway is geographically remote from the Tioli serer, the connection to the gateway can be lost. Tioli enables transfer of operations to an alternate gateway when a serer goes down. Howeer, that alternate gateway does not contain the unique information on managed objects that is required for operations that affect specific managed objects. In this case, execution of these operations must wait until the original gateway returns to serice. Optimizing a proxy managed node: When you want to ensure that the Tioli serer always has access to unique information on managed objects, create a proxy managed node on a computer that has optimal network connectiity with the Tioli serer. For example, if an endpoint gateway serer is geographically remote from the Tioli serer, local network connectiity might be faster and more stable than remote connectiity. If so, create a proxy managed node at the same geographic site as the Tioli serer. See the user s guide for the product for details on creating a proxy managed node. Use the following planning sheets to compile the information you need during installation: Planning sheet for creating managed nodes in Table 7 on page 21 Planning sheet for creating endpoints in Table 8 on page 22 Planning sheet for creating proxy managed nodes in Table 9 on page IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

39 Table 7. Planning sheet for creating managed nodes Key Concept: One managed node must exist in a Tioli management region. This principal managed node is called the Tioli management region serer. Host name Gateway name * Platform User name Password Destination of installation files Name of the target computer in the network Name of the gateway ** Operating system of the managed node root or Administrator Password of the user on the serer Path on the target computer for installation of the product Example: ision03 Example: ision03_gw Example: Solaris Example: root Example: /data/mynode * This name can include alphanumeric characters, underscores (_), hyphens (-), and periods (.). The names are case-sensitie. For example, the name GWName is different from gwname. ** You should create a gateway on all managed nodes for this product. A gateway enables the managed node to communicate with endpoints. In a Typical installation, the installer automatically creates a gateway on eery managed node that you create. The installer creates a unique name for these gateways by adding the _gateway suffix to the host name. In a Custom installation, you can use any unique naming conention for the gateways that you create. Chapter 3. Pre-installation 21

40 Table 8. Planning sheet for creating endpoints An endpoint is a computer on which Tioli software is installed to enable communication with the Tioli management region serer. Host name Endpoint name * Platform User name Password Destination of installation files Name of the target computer in the network Name you assign to the endpoint Operating system of the endpoint root or Administrator Password of the user on the serer Path on the target computer for installation of the product Example: ision03 Example: ision03_ep Example: Solaris Example: root Example: /data/mynode * This name can include alphanumeric characters, underscores (_), hyphens (-), and periods (.). The names are case-sensitie. For example, the name EPName is different from epname. 22 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

41 Table 9. Planning sheet for creating proxy managed objects Host name Managed node name Endpoint name Managed object name * Object type Name of the target computer in the network Name of the managed node you use as proxy The endpoint where one or more database instance exists. Name of the managed object on the managed node Type of object associated with the proxy serer Example: my_host Example: my_host_mn Example: my_database@my_endpoint Example: Oracle 11i * This name can include alphanumeric characters, underscores (_), hyphens (-), and periods (.). The names are case-sensitie. For example, the name MNName is different from mnname. Chapter 3. Pre-installation 23

42 24 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

43 Chapter 4. Performing a Typical installation This chapter describes how to use the Typical installation option to install IBM Tioli Monitoring for Messaging and Collaboration. Objectie To use an installation wizard with predefined default alues to automatically create a Tioli enironment and install IBM Tioli Monitoring for Messaging and Collaboration. The wizard optionally creates managed resources in the Tioli enironment, as described in this procedure. Note: Perform a Custom installation if you want more control of file naming conention and other installation details. Also, use the Custom installation option if you are installing the Tioli management region serer on a UNIX computer and you want to create Windows endpoints. See Chapter 5, Performing a Custom installation on page 35. Background information The target computer, which becomes the Tioli management region serer, must match one of the following profiles: Has no software installed for the Tioli Management Framework. Has Tioli Management Framework, Version 3.7, Reision A or Reision B, installed. You cannot install this product on systems that run preious ersions of the Tioli Management Framework. Has Tioli Management Framework, Version 3.7.1, installed but does not hae the required patches. Tioli 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 Tioli management region serer on a Windows operating system, the installer automatically creates the Windows proxy endpoint so you can create Windows endpoints in the domain of the Tioli management region serer. You can also create managed nodes after installation. Details of the Step List panel of the installer Background information on page 111 describes the status icons and buttons of the Step List panel. Required authorization On UNIX, the user who installs the product must hae root priileges. On Windows, the user who installs the product must hae membership in the Administrators group. Before you begin See Goals for planning and preparing for installation in Table 1 on page 5 for a checklist of actiities prior to installation. 25

44 When you finish Complete the actiities described in Chapter 7, Completing the installation on page 75. Procedure 1. Log on to the computer that you want to be the main Tioli serer for the Tioli management region. 2. Run the setup executable in the root directory of the installation CD labeled IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Installation to launch the IBM Tioli Monitoring for Messaging and Collaboration installer: For Windows, run setupmc.bat For UNIX, run./setupmc.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. After you cancel the installation, always delete the temporary depot directory that the installer creates. You can begin installation again by running the setup executable on the installation CD. 5. Select I accept the terms of the license agreement and click Next to set the target direction for installation. 6. Specify the directory path where you want to install the product. 7. Specify the directory path where you want to create a depot for product installation. Additional information: The depot directory contains all the files required for installation. After the installation is complete, the installer proides an option to automatically delete this directory. 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, proide a directory path that is accessible from the installation computer to the installation depot. 8. Click Next when the installer prompts you to restart the 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 inalid 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. If you are installing the product in an existing Tioli enironment, the license key panel is not necessary and does not appear. 11. Type the password again in the Verify Password field and click Next to display the license key panel. 12. Click Next. 13. Type the Tioli Management Framework license key. Additional information: Obtain this key in the printed document that comes with the installation CDs for the Tioli Management Framework. 26 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

45 14. Click Next to display the language options panel. 15. (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. 16. Click Next. Figure 2. Typical Installation: Typical option panel 17. Select the Typical option and click Next to display the introductory screen for creation of managed nodes. 18. Click Next to display a list of managed nodes. Additional information: This list displays at least one managed node: the Tioli management region serer created automatically on the computer on which you install this product. The installer also discoers and lists any managed nodes from preious installations of Tioli Management Framework, Version 3.7 or Version You cannot edit or delete existing managed nodes. 19. (Optional) Click Add to create additional managed nodes through the Add a Managed Node tabbed dialog box. Chapter 4. Performing a Typical installation 27

46 Figure 3. Typical Installation: Basic tab for managed nodes Note: Make settings in both the Basic tab and the Adanced tab before you click OK to sae the settings. When you click the OK, you sae settings for both the Basic tab and the Adanced tab. 20. Follow these steps to create a managed node: a. Click the Basic tab. b. Specify alues for the managed node in the fields of the Basic tab: 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. Platform Click the drop-down list and select the name of the operating system on the managed node. User Type the login user ID of the person who performs the installation on the managed node. Tioli recommends that you use Administrator for Windows platforms, and root for UNIX platforms. Password and Verify Password The login password of the user specified in the User field. c. Click the Adanced tab. Figure 4. Typical Installation: Adanced tab for managed nodes d. Specify alues in the fields of the Adanced tab. Destination (Optional) A customer path on the target machine where you want to install the Tioli software. Otherwise, Tioli uses the default path specification. Reboot You must select this check box when you add Windows managed nodes to the Tioli management region. The managed node software is actiated after you restart the Windows computer. 28 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

47 e. Click OK to sae your settings and return to the installer. 21. Click Next to display the product selection panel. 22. Select the component or components that you want to install and 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 product or products you selected in Step 22. Additional information: When the product 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 Consoleand click Next to display the list of aailable managed nodes. b. 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. The installer prompts you for this information when you click Next. 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 preious installations of the console. 26. Click Next to display the endpoint option panel. 27. (Optional) Create endpoints for Tioli to monitor and manage. Note: You can also create endpoints after installation, as described in Installing endpoints through an existing Tioli enironment on page 68. Additional information: By default, the installer for IBM Tioli Monitoring for Messaging and Collaboration assigns endpoints to managed nodes wheneer possible. The installer assigns endpoints to the Tioli management region serer only when no managed node is aailable. If you want to change gateway assignments for an endpoint after installation, see Changing the gateway assignment of an endpoint on page 76. a. Click Create endpoints and 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. b. Click Add to display the Add an Endpoint tabbed dialog box. Chapter 4. Performing a Typical installation 29

48 Figure 5. Typical Installation: Basic tab for endpoints c. Click the Basic tab. d. Specify alues for the endpoint in the fields of the Basic tab: 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. Label Type a unique name for the endpoint. This name can include alphanumeric characters, underscores (_), hyphens (-), and periods (.). The names are case-sensitie. For example, the name EPName is different from epname. Platform Click the drop-down list and select the name of the operating system on the endpoint. User Type the login user ID of the person who performs the installation on the endpoint. Tioli recommends that you use Administrator for Windows platforms, and root for UNIX platforms. Password and Verify Password The login password of the user specified in the User field. e. Click the Adanced tab. Figure 6. Typical Installation: Adanced tab for endpoints f. Specify alues in the fields of the Adanced tab, if necessary. Port A port number dedicated to communication with the Tioli serer. The default is Destination Path on the target machine where you want to install the Tioli software. 30 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

49 Reboot You must select this check box when you add Windows endpoints. The endpoint software is actiated after you restart the target Windows computer. g. Click OK to sae 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 Table 10. 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, Reision B, of the Tioli Management Framework 2. Version of the Tioli Management Framework IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Installation If you chose to create Linux endpoints earlier in the installation process, the installer also prompts you for the CD that contains the Tier 2 ersion of this software. IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Installation 3. IBM Tioli Monitoring software IBM Tioli Monitoring V IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino 5. IBM Tioli Monitoring Web Health Console IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Component Software Depending on your choice of products earlier in the installation process, the installer might prompt you for multiple Component Software CDs. IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Installation 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 111 for a description of status icons and buttons in the Step List panel. Chapter 4. Performing a Typical installation 31

50 Figure 7. Step List panel sample 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 111 for information on working around or resoling the following types of problems in the installer: Errors Inalid user names and password for target computers Deferred steps 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 112 describes the status icons and buttons of the Detail dialog box. Additional information: The installer automatically enables you to create Windows endpoints. Howeer, this capability exists only when you are installing the Tioli management region serer 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 Click Run All to begin running the Step List. 34. Click OK in the final prompt of the Step List. 32 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

51 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 111 for troubleshooting information. 35. Click Next. 36. Select one of the following options: 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 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 4. Performing a Typical installation 33

52 34 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

53 Chapter 5. Performing a Custom installation This chapter describes how to use the Custom installation option to install IBM Tioli Monitoring for Messaging and Collaboration. Performing a Custom installation Objectie To use an installation wizard and related Planner tool to install IBM Tioli Monitoring for Messaging and Collaboration. Background information For a enterprise that has a larger, more complex Tioli enironment the Custom installation method offers the following benefits: You see all target computers in a single tree iew for quick reference. You control the naming of managed resources. (Naming is automatic in the Typical installation method.) You control the specification of target directories. For example, you can set a customized path for the Tioli database files. (You must accept the default directory paths in the Typical installation method.) 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 oerwrites all existing settings the Planner. Step 31 on page 48 describes this process. The target computer, which becomes the Tioli management region serer, must match one of the following profiles: Has no software installed for the Tioli Management Framework. Has Tioli Management Framework, Version 3.7, Reision A or Reision B, installed. You cannot install this product on systems that run preious ersions of the Tioli Management Framework. Has Tioli Management Framework, Version installed. Tioli 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 Tioli management region serer on a Windows operating system, the installer automatically creates the Windows proxy endpoint so you can create Windows endpoints in the domain of the Tioli management region serer. When you are installing the Tioli management region serer on a UNIX-based operating system and you want to create Windows endpoints, see Manually creating a Windows proxy endpoint on page 50. Details of the Step List panel of the installer: Background information on page 111 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. 35

54 The Planner makes no changes to any computer. After you complete actions in the Planner, you return to the installer. The installer references the plan you created in the Planner and implements it. When a Tioli enironment already exists, the installer discoers existing managed nodes, gateways, endpoints, and preiously installed of IBM Tioli Monitoring products. These elements are displayed in the Planner. You cannot modify these the discoered managed nodes and endpoints, except to change the login name and password setting. See Completing installation planning sheets on page 19 for more information on the role of managed nodes, gateways, and endpoints The elements displayed in the tree iew in Figure 8 represent a basic plan for a Tioli enironment. The Planner automatically specifies these elements when you are creating a new Tioli enironment: Region A Tioli policy region to contain the Tioli enironment. Managed Nodes A first managed node, which is the Tioli management region serer. This node exists on the computer on which you are installing IBM Tioli Monitoring for Messaging and Collaboration. Tioli Gateway A gateway on the first managed node. Applications Applications that enable IBM Tioli Monitoring for Messaging and Collaboration or that enable optional features, for example: Tioli Management Framework, Version IBM Tioli Monitoring, Version 5.1.1, including the Web Health Console and the IBM Tioli Monitoring Component Serices Figure 8. Custom Installation: Region iew in the Planner Step 31 on page 48 describes how to import a configuration plan that you preiously saed in the Planner. You can import a configuration plan at any time in the Planner. The imported configuration plan oerwrites all existing settings that you typed or selected in the Planner. Required authorization On UNIX, the user who installs the product must hae root priileges. On Windows, the user who installs the product must hae membership in the Administrators group. 36 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

55 Before you begin See Goals for planning and preparing for installation in Table 1 on page 5 for a checklist of actiities prior to installation. When you finish Complete the actiities described in Chapter 7, Completing the installation on page 75. Procedure 1. Log on to the computer that you want to be the main Tioli serer for the Tioli management region. 2. Run the setup executable in the root directory of the installation CD labeled IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Installation to launch the IBM Tioli Monitoring for Messaging and Collaboration installer: For Windows, run setupmc.bat For UNIX, run./setupmc.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. After you cancel the installation, always delete the temporary depot directory that the installer creates. You can begin installation again by running the setup executable on the installation CD. 5. Select I accept the terms of the license agreement and click Next to set the target direction for installation. 6. Specify the directory path where you want to install the product. 7. Specify the directory path where you want to create a depot for product installation. Additional information: The depot directory contains all the files required for installation. After the installation is complete, the installer proides an option to automatically delete this directory. 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, proide a directory path that is accessible from the installation computer to the installation depot. 8. Click Next when the installer prompts you to restart the 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 inalid 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. If you are installing the product in an existing Tioli enironment, the license key panel is not necessary and does not appear. 11. Type the password again in the Verify Password field and click Next to display the license key panel. 12. Click Next. Chapter 5. Performing a Custom installation 37

56 13. Type the Tioli Management Framework license key. Additional information: Obtain this key in the printed document that comes with the installation CDs for the Tioli Management Framework. 14. Click Next to display the language options panel. 15. (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. 16. Click Next. Figure 9. Custom Installation: Custom option panel 17. Select the Custom option and click Next. Additional information: Next and Back buttons are not aailable in the Planner. After you complete actions in the Planner, you return to the installer. 18. Click Launch Planner. 19. Create a managed node to supplement the Tioli management region serer. Additional information: See the Planning sheet for creating managed nodes in Table 7 on page 21 for a planning sheet you can use to compile a list of information that the installer requires. The Planner automatically discoers any managed nodes in an existing Tioli enironment. 38 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

57 Figure 10. Custom Installation: Adding a managed node in the Planner a. Right-click the Managed Nodes item in the tree iew. b. Click Add in the pop-up menu. c. Select the name of the operating system on the managed node. Additional information: The following options are aailable: AIX, Windows, HP-UX, and Solaris. After you select an option, the Managed Node Properties options are displayed in the right panel of the window. A red letter X is displayed on the icon of the managed node you created. When you proide the required configuration properties for the managed node and click Apply, the red X disappears. Chapter 5. Performing a Custom installation 39

58 Figure 11. Custom Installation: Setting managed node properties in the Planner d. (Optional) Modify the default settings in the Managed Node Properties iew. Additional information: Mandatory fields in the Planner window contain an asterisk (*) and hae a yellow background. Aailable options ary depending on the type of operating system you want to install on the managed node. When you hae an existing installation of the Tioli enironment, the Planner displays any existing managed nodes. You cannot modify existing nodes, except to change the user name and password setting. Hostname 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. Binary Directory The absolute path of the directory where you want to install the binary files. Database Directory The absolute path of the directory where you want to install the Tioli database. Library Directory (UNIX-based systems only.) The absolute path of the directory where you want to install the Tioli library. Message Catalog Directory (UNIX-based systems only.) The absolute path of the directory where you want to install the message catalog. Applications Default Directory (UNIX-based systems only.) The absolute path of the directory where you want to install the X11 resource files. X11 files are the UNIX desktop files. Man Pages Default Directory (UNIX-based systems only.) The absolute path of the directory where you want to install the Tioli man pages. This includes the man pages for all Tioli products. 40 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

59 Login The required login user ID of the person who performs the installation. Tioli recommends that you use Administrator for Windows platforms, and root for UNIX platforms. Password The login password of the user specified in the Login text box. Reboot This check box must be checked when you add Windows managed nodes to the Tioli management region. After the computer restarts, the software is running. e. Click Apply to apply the settings. Additional information: You must click Apply to sae your changes. If you go to another iew in the Planner before you click Apply, your changes are lost. 20. Repeat Step 19 for each managed node that you want to create. 21. Click the Tioli Gateways item in the tree iew. 22. Modify the default settings for gateways in the Tioli Gateways properties iew, if necessary. It is recommended that you use the default alues, which are deried from a study of best practices. Note: Only users with adanced experience with Tioli Management Framework software should change the defaults. If you create gateways on Windows computers, click Windows defaults to access the settings for Windows gateways. If you create gateways on UNIX-based computers, click UNIX defaults to access the settings for Windows gateways. The following gateway properties are aailable: Protocols The network protocol used to communicate with this gateway. The only supported protocol is TCP/IP. Port The number of the port that the endpoints use to communicate with this gateway. Timeout The amount of time the gateway waits for a response from the endpoint. Max Jobs The maximum number of simultaneous connections that the gateway can initiate. Debug Leel The leel (0 through 8) of message information that the gateway logs. Max number of connections The maximum number of simultaneous connections that the repeater initiates during a distribution. Net load The maximum amount of data (in kilobytes per second [KBps]) that the repeater sends to the network for each distribution. Disk directory The location of temporary disk space. Memory Percentage The percentage of the system s RAM that the gateway can use. Disk Max/Min The fixed minimum disk alue in megabytes for the gateway s temporary space. Disk Percentage The percentage of free disk space that is the maximum disk alue gien to the gateway to use as temporary space. The percentage setting allows the temporary disk space to adjust dynamically to maximize the space aailable to the gateway. The maximum disk alue changes with the amount of aailable free disk space, as in the following examples: Chapter 5. Performing a Custom installation 41

60 If you specify 20 MB for Disk Max/Min, 10 percent for Disk Percentage, and hae 500 MB of free disk space, the gateway can use a maximum of 50 MB (10 percent of 500 MB) for temporary space. If you specify 100 MB for Disk Max/Min, 10 percent for Disk Percentage and hae 500 MB of free disk space, the gateway can use a maximum of 100 MB for temporary space, because in this case, the Disk Max/Min is greater than the Disk Percentage and oerrides it. Figure 12. Custom Installation: Adding a gateway in the Planner 23. Create a gateway on a managed node. Additional information: Each managed node can be a gateway that can communicate with endpoints. You can add one gateway to each managed node that you create. The Planner automatically discoers any managed nodes in an existing Tioli enironment. a. Right-click Tioli Gateways in the tree iew. b. Click Add. c. Select Gateway in the pop-up menu to create the gateway and display the Gateway Properties iew. A red letter X is displayed on the icon of the gateway you created. When you proide the required configuration properties for the gateway and click Apply, the red X disappears. d. Type a unique name in the Gateway Name field. 42 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

61 Additional information: This can be any name. It is recommended to use <host name>_gw to distinguish this gateway from other gateways and endpoints. For example, if the host name of the managed node is ision35, name the gateway ision35_gw. e. Select the node on which to install the gateway in the Managed Node Host Name drop-down list. When you hae an existing installation of the Tioli enironment the Planner displays any existing gateways. You cannot modify the name of an existing gateway or change the managed node with which it is associated. Additional information: You cannot create an amount of gateways that exceeds the number of aailable managed nodes. Otherwise the Managed Node Host Name list is empty and you are unable to associate the gateway with a managed node. f. Click Apply. Additional information: You must click Apply to sae your changes. If you go to another iew in the Planner before you click Apply, your changes are lost. Figure 13. Custom Installation: Associating a gateway with a managed node in the Planner 24. Repeat Step 23 for each gateway that you want to create. Chapter 5. Performing a Custom installation 43

62 Figure 14. Custom Installation: Adding an endpoint in the Planner 25. Create an endpoint to enable a computer to communicate with the Tioli management region serer: Additional information: When you install an endpoint, required software must be running on the target computer. See the Verifying that required software is running on page 17 for more information. See Table 7 on page 21 for a planning sheet you can use to compile a list of endpoint information that the installer requires. By default, the installer for IBM Tioli Monitoring for Messaging and Collaboration assigns endpoints to managed nodes wheneer possible. The installer assigns endpoints to the Tioli management region serer only when no managed node is aailable. If you want to change gateway assignments for an endpoint after installation, see Changing the gateway assignment of an endpoint on page 76. The Planner automatically discoers any endpoints in an existing Tioli enironment. a. Right-click Endpoints in the tree iew. b. Select Add in the pop-up menu. c. Select the operating system of the serer on which you are creating an endpoint. Additional information: Most text boxes in the Endpoint Properties iew are common to all the platforms. If you hae a UNIX Tioli management region serer, endpoints installed on Windows platforms require a proxy agent. See Manually creating a Windows proxy endpoint on page 50 for instructions on creating a proxy endpoint. 44 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

63 Figure 15. Custom Installation: Setting endpoint properties in the Planner A red letter X is displayed on the icon of the endpoint you created. When you proide the required configuration properties for the endpoint and click Apply, the red X disappears. d. Enter required alues and optionally modify the default settings in the Endpoint Properties iew: When you hae an existing installation of the Tioli enironment the Planner displays any existing endpoints. You cannot modify existing endpoints, except to change the login name and password setting. Proxy name (Windows only.) Type the name of an existing Windows endpoint that seres as the new endpoint s proxy agent. This proxy should share the same domain as the Tioli management region domain because it uses Windows Uniersal Naming Conention (UNC) methods to proide remote access to newly created Window endpoints. The proxy endpoint enables creation of Windows endpoints in any domain that has a trust relationship with the domain that contains the proxy. Endpoint Name The name you gie to the endpoint. Tioli recommends that you name it <host_name>_ep, in case you hae a gateway with the same name on the same computer. This naming conention distinguishes the gateway from the endpoint. For example, ision35_ep and ision35_gw. Base directory The absolute path of the directory where you want to install the endpoint. Hostname 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. Chapter 5. Performing a Custom installation 45

64 Port The number of the port that the endpoint uses to communicate with the gateway. Do not type the same port number that you specified in the Gateway Properties in Step 23. Login The user ID of the user who performs the installation. On UNIX, the user must hae root priileges. On Windows, the user must hae membership in the Administrator group. Tioli recommends that you specify root on UNIX and Administrator on Windows. Password The login password of the user you specify in the Login text box. e. Click Apply. Additional information: You must click Apply to sae your changes. If you go to another iew in the Planner before you click Apply, your changes are lost. Figure 16. Custom Installation: Adding the Web Health Console in the Planner 26. Repeat Step 25 for each endpoint that you want to add. 27. (Optional) Install the Web Health Console on managed nodes or endpoints: Additional information: Automated discoery in the Planner does not include discoery of existing Web Health Consoles. Confirm that the Web Health Console does not exist on a target system before you complete this step, otherwise the console is installed again on the target system. When you specify the installation of the Web Health Console on a pre-existing managed node or endpoint, you must supply the user ID and password. The installer prompts you for this information. The information you proide must match the user ID and password specified for the managed node or endpoint in the Tioli enironment. Remember that the Planner gies you the option to 46 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

65 change the user ID and password specification for any managed node or endpoint as described in preious steps of this procedure. a. Click Applications in the tree iew to expand the nested items. b. Click IBM Tioli Monitoring in the tree iew to expand the nested items. c. Select WAS/Web Health Console to display the Web Health Console iew. d. Place a check mark in the Web Health Console column of the Managed Nodes table in the row for each host that should hae a console. e. Place a check mark in the Web Health Console column of the Endpoints table for each host that should hae a console. f. Click Apply. Additional information: You must click Apply to sae your changes. If you go to another iew in the Planner before you click Apply, your changes are lost. 28. Install IBM Tioli Monitoring for Messaging and Collaboration on managed nodes. a. Click Applications in the tree iew to display the nested items. b. If IBM Tioli Monitoring for Messaging and Collaboration is not displayed in the tree iew, click Add to add it to the tree iew. c. Place a check mark in the product column of the Managed Nodes table in the row for each node on which you want to install the product. Additional information: The IBM Tioli Monitoring and Component Serices software is required to install IBM Tioli Monitoring for Messaging and Collaboration. The Planner automatically places a check mark on IBM Tioli Monitoring and Component Serices for the corresponding host. Also, the Managed Node table displays any pre-existing ersions of IBM Tioli Monitoring for Messaging and Collaboration and automatically places a check mark beside the names of hosts on which a ersion of the product already exists. You cannot remoe this check mark. d. Click Apply. Additional information: You must click Apply to sae your changes. If you go to another iew in the Planner before you click Apply, your changes are lost. 29. Confirm that all managed nodes, gateways, and proxy agents that you hae configured are alid and necessary. Additional information: In a complex plan you might need to remoe an element from your configuration plan, as in the following examples: You cannot obtain required configuration information prior to installation of the product. You cannot access a serer because it is temporarily down or inaccessible in the network. If you identify elements to remoe, consult table 11 to plan the successful remoal of the element without causing an error for other elements that it references. Table 11. Remoal of planner elements and possible consequences Element to remoe Managed node Possible consequence The gateway associated with the managed node you remoe becomes inalid. Correctie Action Select the inalid gateway. Change its properties. Associate it with an existing managed node. Click Apply. Chapter 5. Performing a Custom installation 47

66 Table 11. Remoal of planner elements and possible consequences (continued) Element to remoe Gateway (Windows only) Proxy endpoint Possible consequence All the endpoints associated with the gateway you remoe become inalid. All endpoints associated with the proxy endpoint you remoe become inalid. Correctie Action Select the inalid endpoints and change their properties. Associate them with an existing gateway. Click Apply. Select the inalid agents, and change their properties. Associate them with an existing proxy endpoint. Click Apply. 30. Remoe any unnecessary managed nodes, endpoints, or applications you hae created. a. Right-click the entity you want to delete. b. Click Remoe in the pop-up menu. c. Click OK. 31. (Optional) Export your Planner settings to a.xml file for future use in the Planner: a. Select Export in the File menu. b. Select a directory in which to sae the file. c. Name the file. d. Click Sae. e. If a tree iew item has a red X mark, you must supply missing alues as follows: 1) Click the item. 2) Complete or modify the data fields in the properties iew. 3) Click Apply. Additional information: A confirmation message, The changes hae been applied successfully is displayed. 32. (Optional) Import configuration settings that you saed preiously: a. Select Import in the File menu. Additional information: The Planner warns you that the imported file oerwrites any settings you hae made in the current planning session. b. Click OK to confirm the importation of a configuration settings (.xml) file. c. Find the directory that contains the file. d. Select the file. e. Click Open to import the configuration settings to the Planner. 33. Click File menu. 34. Select Sae to sae all configurations settings. 35. Click File menu. 36. Select Close to exit the Planner and return to the installer. 37. 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 111 for a description of status icons and buttons in the Step List panel. 48 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

67 Figure 17. Step List panel sample 38. (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. 39. See Troubleshooting installer problems on page 111 for information on working around or resoling the following types of problems in the installer: Errors Inalid user names and password for target computers Deferred steps Failed steps 40. (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 112 describes the status icons and buttons of the Detail dialog box. Additional information: The installer automatically enables you to create Windows endpoints. Howeer, this capability exists only when you are installing the Tioli management region serer 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 Click Run All to begin running the Step List. Chapter 5. Performing a Custom installation 49

68 Note: If you are installing the product on a UNIX-based computer and want to create Windows endpoints in the Tioli management region go immediately to Step 42. Otherwise skip Step (Optional) UNIX-based Tioli management region serers only: Click the Stop button at the top of the Step List and perform the procedure described in Manually creating a Windows proxy endpoint on page Click OK in the final prompt of the Step List. 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 111 for troubleshooting information. 44. Click Next. 45. Select one of the following options: 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 Do not delete the temporary files. Select this option to keep the temporary files. You can manually delete the files at any time. 46. Click Next. 47. Click Finish. Manually creating a Windows proxy endpoint Objectie To manually create a proxy endpoint on a UNIX-based Tioli management region serer. Background information The installation wizard can create Windows endpoints for the Tioli management region serer that you are installing. Howeer, this capability exists only when you are installing the Tioli management region serer on a Windows operating system. Chapter 4, Performing a Typical installation on page 25 and Chapter 5, Performing a Custom installation on page 35 describe the installation process which includes creation of endpoints. A proxy endpoint must exist in a Windows domain to enable the installer to create Windows endpoints. When the Tioli management region serer runs on Windows and you want to create Windows endpoints, the installer automatically creates the proxy endpoint in the domain in which that serer resides. This proxy should share the same domain as the Tioli management region domain because it uses Windows Uniersal Naming Conention (UNC) methods to proide remote access to newly created Window endpoints. The proxy endpoint enables creation of Windows endpoints in any domain that has a trusted relationship with the domain that contains the proxy. The Tioli serer uses the user ID and password for the proxy endpoint to obtain access to the file system of the other Windows serers. The installation wizard also associates the proxy endpoint with a gateway in the Tioli management region. Otherwise, the Tioli management region serer cannot use the proxy endpoint. You perform this procedure at a specific point during the installation process when a gateway has been created to associate with the proxy endpoint. 50 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

69 With this proxy access, the Tioli serer is able to install endpoints on Windows systems in that domain and in other Windows domains in the network that hae a trust relationship. Without a proxy endpoint, the Tioli serer cannot create Windows endpoints in that remote domain. In UNIX installations, the wizard does not automatically create the proxy endpoint that Windows requires. When the Tioli management region serer you are installing runs a UNIX operating system, you must use this procedure. The procedure sets up the required proxy endpoint in the Windows domain that contains target Windows serers that you want to monitor with IBM Tioli Monitoring for Messaging and Collaboration. 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 seere error can occur that preents the deployment process from proceeding. This error does not occur in the Typical installation path because in that option gateways are defined automatically. Required authorization On UNIX systems, the user who installs the product must hae root priileges. On Windows systems, the user who installs the product must hae membership in the Administrators group. Before you begin Perform the first part of the Custom installation procedure. This procedure is described in Chapter 5, Performing a Custom installation on page 35. During this procedure you access the Step List wizard panel. You manually configure a Windows proxy endpoint in the Step List wizard panel, during the installation procedure. Identify the Windows computer that will sere as the proxy endpoint. You need the endpoint name as well as the host name for the machine. For instance, if the host name is ision35.mycompany.com, you might want to name the endpoint ision35_ep. When you finish None. Procedure You perform this procedure in the product Custom installer and Tioli Management Framework Endpoint Setup wizard. This procedure supplements the installation process, at the point when the installer begins to process the Step List. Use this procedure only if you are installing the product on a UNIX-based serer. This procedure is not necessary if you are installing the product on a Windows-based serer. Installation wizards: 1. Click the Stop button at the top of the Step List when the installer starts running Step 1. The system displays a message indicating that it will stop at Chapter 5. Performing a Custom installation 51

70 the end of the current step. 2. Click OK and wait for the step to finish processing. 3. In the Step List scroll to the TMA installation step, which installs any endpoints that you hae configured. 4. Double-click on the TMA installation step to access the Detail dialog box for the step. 5. Perform the following steps in the Detail dialog box: a. Click Toggle Breakpoint. b. Click OK. Additional information: This action sets a breakpoint for when the installer begins to install endpoints. A stop sign icon indicates the step at which you inserted a breakpoint. While this step is in breakpoint mode, you enable the endpoint proxy as described in Step Click Run All at the top of the Planner window. Additional information: Processing of the steps in the Step List resumes, until the installer reaches the breakpoint and stops. Prior to the breakpoint you set in Step 5 the installer completes the creation of a gateway. To install correctly, the proxy endpoint must refer to this gateway. Otherwise the Tioli management region serer cannot recognize the proxy endpoint. 7. When the installer reaches the breakpoint you created in Step 5 install the proxy endpoint using the following steps. Perform these steps on the computer where you are going to install the proxy endpoint, not on the Tioli management region serer. a. Insert the Tioli Management Framework, Version 3.7.1, CD into the CD drie of the computer. b. Run the setup executable located in the following subdirectory path of the Tioli installation directory:..\pc\lcf\winnt 52 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

71 c. Click Next in the Tioli Management Framework Endpoint Setup dialog box. d. Read the license agreement. e. Click Next to display the Endpoint installation options dialog box f. (Optional) Click Browse to change the destination directory for the software. g. Click Next to display the Tioli Remote Access Account dialog box. h. Type the user name and password of the account through which Tioli Management Framework accesses remote file systems. If you do not require access to remote domains, click Next to skip this step. i. Click Next to access the Adanced Configuration dialog box. j. Specify the startup and configuration options information listed in the following table: Field name Use when... Gateway The gateway uses a port number other than the default Endpoint Other You want to specify a port for the endpoint to use other than the default. The default is Use the g <host_name_of_the_gateway> option to specify the intercepting gateway. Use the n <host_name_of_the_endpoint> option to specify the name of the endpoint you are installing as the proxy. Note: For a Custom installation of IBM Tioli Monitoring for Messaging and Collaboration, the parameters you supplied in the Planner tool must match the parameters you specify in this step for the-g and -n options. k. Click Next to continue the installation process. Additional information: The installer reports that communication of the proxy endpoint and the gateway was successful. The endpoint is installed and logged into a gateway. The installation process configures the endpoint system to automatically start the endpoint serice when the system starts. If the system does not start, there might be a problem with the communication between the proxy endpoint and the gateway. See Cleaning up and remoing the endpoint on page 119 to remoe the endpoint, then reinstall the endpoint. l. Click Next to display the Setup Complete dialog box. m. Click Finish to display the Restart Windows dialog box. n. Select No to preent the restarting of the operating system. Additional information: You can restart the system after the installation of IBM Tioli Monitoring for Messaging and Collaboration is complete. When you restart the computer the Tioli Endpoint serice is created, with the startup type set to automatic. 8. Press OK to complete the endpoint installation. 9. On the Tioli management region, click Run All in the installer and complete the Custom installation steps that follow Step 42 on page 50. Additional information: After the Custom installation process finishes, you perform the procedures in Chapter 7, Completing the installation on page 75 which include erification of the installation of all endpoints and managed nodes. Chapter 5. Performing a Custom installation 53

72 54 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

73 Chapter 6. Installing the product manually This chapter describes how to install IBM Tioli Monitoring for Messaging and Collaboration and related software through an existing Tioli enironment. These procedures enable you to install and set up the product without using the Typical or Custom installation options in the installer. An optional product, the Tioli Software Installation Serice (SIS), can install multiple Tioli products on multiple systems in parallel, as described in Using Tioli Software Installation Serice. Version of the Tioli Management Framework must be installed in the Tioli enironment before you begin performing any of the procedures in this section. This software comes with the installation CDs for this product. Table 12. Guidelines for installing the product through an existing Tioli enironment Goal Refer to Access the Tioli enironment. Accessing the Tioli enironment on page 56 Install managed nodes to assist the Tioli serer with management and monitoring operations. Install Tioli patches to update performance of the Tioli Management Framework software or to upgrade software. Upgrade an installation of IBM Tioli Monitoring to the required Version Install Tioli software, including IBM Tioli Monitoring and IBM Tioli Monitoring for Messaging and Collaboration Install endpoint software to enable target computers to communicate in the Tioli enironment. Install the Web Health Console on computers to display real-time status of managed resources. Installing managed nodes through an existing Tioli enironment on page 57 Installing Tioli patches manually on page 60 Upgrading IBM Tioli Monitoring manually on page 64 Manually installing Tioli software on page 66 Installing endpoints through an existing Tioli enironment on page 68 Installing the Web Health Console manually on page 72 Install the Management Console on a workstation. See IBM Tioli Monitoring User s Guide for information on using the console. Installing the Management Console manually on page 73 See IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide for information on using the Management Console. Using Tioli Software Installation Serice An optional product, the Tioli Software Installation Serice (SIS), can install multiple Tioli products on multiple systems in parallel. This Jaa-based product can install more products on more systems in less time than the Tioli Management Framework s installation facility. Tioli Software Installation Serice performs product prerequisite checks and, if defined, user-specified prerequisite checks to aoid or eliminate installation failure. In most cases, failures occur only when machines are turned off or remoed from the network. 55

74 Tioli Software Installation Serice also creates an installation repository into which you can import the installation image of one or more Tioli products. You can import only the interpreter types you require in your enironment, which saes disk space and import time. The installation repository is then the source of all your Tioli installations. You can een share a single installation repository across multiple Tioli management regions. For details of the platforms on which the Tioli Software Installation Serice can run and for instructions on installing and using the product, see the Tioli Software Installation Serice User s Guide and the release notes for that product. Accessing the Tioli enironment Objectie To access the Tioli enironment so that you can use the operations and functions of the Tioli Management Framework. Background information You can access the Tioli desktop or the Tioli command line interface in order to use the operations and functions of Tioli Management Framework. The Tioli desktop is a user interface that proides point-and-click access to features and functions. The Tioli desktop proides a central control point for you to organize, manage, and delegate system management operations. The command line interface (CLI) enables you to enter commands from the keyboard. You can use these commands in shell scripts and with system utilities such as the UNIX cron utility. For more information about using commands, refer to the Tioli Management Framework Reference Manual. Required authorization role The installation routine for IBM Tioli Monitoring for Messaging and Collaboration creates the Tioli administrator who is authorized to perform this procedure. Depending on the commands they want to run, other administrators might require the super, senior, admin, or user authorization roles. Before you begin None When you finish Perform installation operations or administratie operations in the Tioli enironment. Procedure You can perform this procedure from the desktop of your workstation or from the command line. Command line: Use one of the following two methods to access the Tioli command line interface, depending on whether you use a Windows or UNIX operating system: Windows 1. Log on to a Windows managed node or Tioli management region serer. 2. Select Start Command Prompt in the Windows task bar to open the command prompt window. 3. Enter the following command to run the enironment initialization and setup script: 56 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

75 %SystemRoot%/system32/driers/etc/Tioli/setup_en.cmd This command enables you to perform all of the IBM Tioli Monitoring for Messaging and Collaboration operations. OR UNIX 1. Log on to a UNIX managed node or Tioli management region serer. 2. Run the enironment initialization and setup script. If you are using the Bourne, Korn, or bash shell, run the following command:. /etc/tioli/setup_en.sh If you are using the C shell, run the following command: source /etc/tioli/setup_en.csh Tioli desktop: 1. Do one of the following to access the login screen of the Tioli desktop: Click Start in the Windows task bar and select Programs Tioli Tioli. OR Enter the tioli command. See the Tioli Management Framework Reference Manual for more information on this command. 2. Type the following alues in the fields of the login screen: Host Machine specifies the Tioli managed node, including the Tioli serer where the Tioli desktop should connect. Log In As specifies the login name to the managed node. Password specifies the password for the specified login name. 3. Click OK. The Tioli desktop appears. Installing managed nodes through an existing Tioli enironment Objectie To install managed nodes using an existing Tioli user interface. Background information This procedure enables you to install and set up managed nodes without using the Typical or Custom installation options in the installer. This procedure uses the default settings for a managed node. See the Tioli Enterprise Installation Guide to learn how to oerride the defaults. Required authorization role install_client or super Before you begin As a precautionary measure, back up the Tioli management region as described in Backing up and restoring Tioli databases on page 13. Start the command line interface or Tioli desktop as described in Accessing the Tioli enironment on page 56. When you finish None Chapter 6. Installing the product manually 57

76 Procedure Tioli desktop: 1. Select Managed Node in the Create menu to display the Client Install dialog box. Additional information: The managed node is created in the current policy region. See the Tioli Enterprise Installation Guide to learn about creating managed nodes in other policy regions. 2. In the TMR Installation Password field, type the installation password. Additional information: If a password was not specified when the Tioli management region serer was created, leae this field empty. If a password was specified, you must use this password for each managed node. 3. Select the radio button in the Default Access Method area to indicate how the Tioli management regions contacts each system: Account In the Account field, type the name and password of the priileged user to contact the system. In the Password field, type the password for this user. This option applies to UNIX, Windows NT, and Windows 2000 systems. Trusted Host (UNIX only) For trusted host access, the /.rhost file on each system must grant access to the system performing the installation by adding and entry for root@hostname, where hostname is the host name of the Tioli management region serer or managed node performing the installation. Note: You can oerride the access method when you add a single system, load systems from a file, or after the systems are added to the list. 4. Click Add Clients to display the Add Clients dialog box. 5. Configure the client as follows: a. In the Add Client field, type the name of the system you want to configure as a managed node. b. Specify the access method that the Tioli management region serer uses to contact the system: Select Use Default Access Method to use the default access method that you specified in Step 3. OR Select Account to use account access that you specified in Step 3. OR Select Trusted Host Access to use trusted host access in UNIX that you specified in Step 3. c. Click Add & Close to add the system to the list and return to the Client Install dialog box. 6. Repeat Steps 4 and 5 for each computer that you want to configure as a managed node. 7. If you need to change the access method for any of the listed systems, perform the following steps in the Client Install dialog box: a. Select the system to change. b. Click Access Method to display the Select Access Method dialog box. c. Select the access method you want. d. Click Set to return to the Client Install dialog box. 8. Click Select Media to display the File Browser dialog box in which you specify the path to the directory that contains the installation images. 58 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

77 9. Use the File Browser dialog box to naigate to the correct file. 10. Click Set Media & Close to sae your setting and display the Install Options dialog box Additional information: See the Tioli Management Framework User s Guide for instructions on how to use the File Browser dialog box. Note: Normally, you use same installation image to create the Tioli management region serer and managed nodes. 11. Modify the installation options, if necessary. Additional information: The options in this dialog box apply to all listed systems. 12. Click Set to sae your changes and return to the Client Install dialog box. 13. Click Install & Close to start the installation of the managed node. Additional information: The Client Install dialog box is displayed. This dialog box lists operations that will take place during the installation and any problems that you might want to correct before continuing the installation. 14. Click Continue Install. 15. (Windows only) Perform the following steps in the Tioli Remote Access Account dialog box that is displayed: a. Select one of the following radio buttons: Account Defines an account other than the default access account. None Specifies that there is no Tioli remote access account. If reinstalling and there is a preious Tioli remote access account, this option does not oerwrite the original account. Use Installation Access Method Account Specifies that Tioli remote access account is the default access account. This selection grants the full rights that the default access account has. For more information about Tioli remote access account, see the Tioli Enterprise Installation Guide. b. Click Continue. Additional information:the Client Install dialog box returns and displays information on the progress of installation. c. Click OK in the Confirm Reboot of Clients prompt to reboot these systems. Additional information: You can click Close and restart the computer later, if necessary. The managed node is enabled only after you restart. 16. (UNIX only) When the installation completes, the Client Install dialog box ends with the following completion message: 17. Click Close when the Client Install dialog box displays the Finished client install message 18. Select Refresh in the Desktop menu to display the icon of the managed nodes you created and erify success of this procedure. 19. (Windows only) Configure Simple Mail Transfer Protocol (SMTP) as follows. This protocol enables Tioli to generate for alerts and other messages: a. Access the Tioli command line enironment as described in Accessing the Tioli enironment on page 56. b. Enter the following command: wmailhost hostname where hostname is the name of the network mail serer. For additional information, see the Tioli Enterprise Installation Guide. Chapter 6. Installing the product manually 59

78 20. Install gateway software on the managed node as follows: a. Right-click the EndpointManager icon and select Create Gateway to access the Create Gateway dialog box. b. In the Name field, type a unique name for the gateway. c. In the Port field, type the port number through which the gateway will communicate with its endpoints in TCP/IP. d. In the Managed Node Proxy field, type the name of the managed node on which the gateway will run. e. Click Create & Close. Command line: Use the wclient command to create a managed node. The following example creates a managed node named eerest: wclient -c F:\cdrom -d -p austin_pr eerest where -c F:\cdrom Specifies the path to the installation image. d Sets installation ariables to their last set alues. Commonly, each installed managed node uses the same set of installation ariables. This option proides a shortcut for setting the ariables. In this case, the managed node obtains settings for the installation ariables from the Tioli serer. p austin_pr Specifies that the managed node is for the austin_pr policy region. After creating a managed node on a Windows NT or Windows 2000 system, you must reboot the system to complete the installation. In IBM Tioli Monitoring for Messaging and Collaboration, each managed node should hae a gateway to enable communication with endpoints. Use the wcrtgate command to create a gateway on the managed node. The following command creates a gateway on managed node eerest using the default settings: wcrtgate -h eerest After creating the gateway, you can configure its behaior as a repeater and as a ehicle for software distribution using the wrpt and wmdist commands. For additional information see the Tioli Management Framework Reference Manual. See to Tioli command syntax on page xi for information on Tioli command line syntax. Installing Tioli patches manually Objectie To install Tioli patches using an existing Tioli desktop or command line interface. Background information This procedure enables you to install patches for the Tioli Management Framework without using the Typical or Custom installation options in the installer. 60 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

79 You must perform this procedure on eery managed node in the Tioli enironment. Configure the wpatch command to install the patch on all managed nodes automatically, as described in this procedure. The patches are located in the PATCHES directory of the following installation CDs: IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Installation IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Component Software IBM Tioli Monitoring V5.1.1 Note: See Limitations and Workarounds Supplement on page x to learn how to obtain any updates to this information. The installer automatically installs the following patches for the Tioli Management Framework. You must manually install the patch for Tioli Business Systems Manager. For a manual installation of the product, you install the patches as described in this procedure in the sequence shown: Table 13. Manual installation: Specifications of required patches Software release Patch name Prerequisite patches Purpose Tioli Management Framework 3.6 Proides required updates to Tioli Management Framework TMF-0034 Linux support TMF TMF-0034 Linux support Tioli Management Framework 3.7 Proides required updates to Tioli Management Framework Tioli Management Framework TMF TMF TMF-0034 & 0062 Linux-390 support 3.7-TMF-0035 Linux support TMF TMF TMF-0073 * TMF TMF-0034 & TMF-0087 * TMF-0073 HP-UX support for product installer * After you install this patch, you must run the following commands to restart the local object dispatchers: odadmin shutdown clients odadmin reexec 1 odadmin start clients Product upgrades To upgrade Tioli products, you install patches as described in this procedure. Use one of the following options to upgrade Version of IBM Tioli Monitoring for Messaging and Collaboration: Chapter 6. Installing the product manually 61

80 When Monitoring for Lotus Domino, Version 5.1.0, is installed, upgrade to Version as follows: Use the wpatch command and reference the PATCH511.IND patch that is located in the UPGRADE directory of the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Lotus Domino, Component Software installation CD. OR Perform a Typical installation as described in Chapter 4, Performing a Typical installation on page 25. The installer automatically upgrades Version to Version When Tioli Manager for Domino, Version 3.x, is installed, upgrade to Version as follows: 1. Use the installation CDs for Version of Monitoring for Lotus Domino to install the product as follows: Use the winstall command and reference the NOTES_51.IND product index file. OR Use the installation wizard to perform a Typical installation of the product. 2. Use the installation CDs for Version of Monitoring for Lotus Domino to upgrade to Version as follows: Use the wpatch command and reference the PATCH511.IND patch that is located in the UPGRADE directory of the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Lotus Domino, Component Software installation CD. OR Perform a Typical installation as described in Chapter 4, Performing a Typical installation on page 25. The installer automatically upgrades Version to Version Create new Lotus Domino Serer objects for each Lotus Domino serer that you managed with Tioli Manager for Domino, as described in Migrating from preious Tioli software on page 89. Required authorization role install_product Before you begin As a precautionary measure, back up the Tioli management region as described in Backing up and restoring Tioli databases on page 13. Start the command line interface or Tioli desktop as described in Accessing the Tioli enironment on page 56. When you finish None Procedure You can perform this procedure from the Tioli desktop or from the command line. Command line: Use the wpatch command to install patches. wpatch [-c <source_dir>] -i patch_name [-y].ind [-n <managed_node1> <managed_node2>...] where: 62 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

81 -c <source_dir> Specifies the complete path to the directory containing the installation image. -i patch_name.ind Specifies the product index file to reference for the installation. -n Installs the product on all managed nodes that do not currently hae the product installed. <managed_node> Installs the product on the managed nodes you specify. Use blank spaces to separate the names of multiple managed nodes. If you do not specify managed nodes, the patch is installed on all managed nodes in the Tioli management region. -y Installs the product without requesting confirmation. Refer to the Tioli Management Framework Reference Manual for more information about this command. Refer to Tioli command syntax on page xi for information on Tioli command line syntax. Tioli desktop: 1. Select Install in the Desktop menu. 2. Select Install Patch in the sub-menu to display the Install Patch dialog box. 3. If necessary, click OK to bypass a harmless error message about the media settings. 4. Click Select Media to display the File Browser dialog box. 5. In the Path Name text field, enter the full path to the patch installation files in the CD-ROM drie. Be sure to use backward slashes (\) for Windows path names instead of forward slashes (/). 6. Click Set Path. The File Browser dialog box displays the contents of the specified media in the Files scrolling list. 7. Click Set Media & Close. 8. Select the patch from the Select Patch to Install scrolling list in the Install Patch dialog box. 9. Select the target clients on which to install the patch from the Aailable Clients scrolling list, 10. Click the right arrow to moe the selected clients to the Aailable Clients scrolling list. 11. Click Install & Close to display the Patch Install window and a list of pending installation actions. 12. Click Continue Install to begin the installation process. Additional Information: The Patch Install window displays the progress of the installation. View the messages in the task output dialog box to determine whether the patch installation was successful. If necessary, see About the log files for installation errors on page 115 for information on problem determination. 13. Click Close to close the Patch Install window. 14. Select Refresh from the View menu bar. The desktop displays the icon for the patch you installed. 15. As a precautionary measure, back up the Tioli management region databases as described in Backing up and restoring Tioli databases on page 13. Use a unique name for the new backup files. Chapter 6. Installing the product manually 63

82 Upgrading IBM Tioli Monitoring manually Objectie To install the patches that upgrade IBM Tioli Monitoring using an existing Tioli desktop or command line interface. Background information This procedure enables you to upgrade IBM Tioli Monitoring without using the Typical or Custom installation options in the installer. For IBM Tioli Monitoring, Version 4.x: If you use Version 4.x of IBM Tioli Monitoring, you must perform this procedure twice. First install the patch to upgrade Version 4.x to Version then run the patch to upgrade Version to Version 5.1.1, as described in this procedure. Required authorization role install_product Before you begin As a precautionary measure, back up the Tioli management region as described in Backing up and restoring Tioli databases on page 13. Start the command line interface or Tioli desktop as described in Accessing the Tioli enironment on page 56. When you finish None Procedure You can perform this procedure from the Tioli desktop or from the command line. Command line: Run the following command from the command prompt: wpatch [-c <source_dir>] -i patch_name [-y].ind [-n <managed_node1> <managed_node2>...] [-y] where: -c <source_dir> Specifies the complete path to the directory containing the installation image. -i patch_name Specifies the product index file to reference for the installation. Install these patches from the IBM Tioli Monitoring V5.1.1 installation CD in the following order: 1. If you are upgrading from IBM Tioli Monitoring, Version 4.x, run this patch: /upg41to51/dm51upg.ind. After you run this patch you hae Version of this product. 2. If you are upgrading from IBM Tioli Monitoring, Version to Version 5.1.1, run this patch: /upgrade/dm51upg.ind. -n Installs the product on all managed nodes that do not currently hae the product installed. <managed_node> Installs the product on the managed nodes you specify. Use blank spaces 64 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

83 to separate the names of multiple managed nodes. If you do not specify managed nodes, the patch is installed on all managed nodes in the Tioli management region. -y Installs the product without requesting confirmation. Refer to the Tioli Management Framework Reference Manual for more information about this command. Refer to Tioli command syntax on page xi for information on Tioli command line syntax. Tioli desktop: 1. Select Install in the Desktop menu. 2. Select Install Patch in the sub-menu to display the Install Patch dialog box. 3. If necessary, click OK to bypass a harmless error message about the media settings. 4. Click Select Media to display the File Browser dialog box. 5. In the Path Name text field, enter the full path to the language support files in the CD-ROM drie. Be sure to use backward slashes (\) for Windows path names instead of forward slashes (/). Install these patches from the IBM Tioli Monitoring V5.1.1 installation CD in the following order: a. If you are upgrading from IBM Tioli Monitoring, Version 4.x, run this patch: /upg41to51/dm51upg.ind. After you run this patch you hae Version of this product. b. If you are upgrading from IBM Tioli Monitoring, Version to Version 5.1.1, run this patch: /upgrade/dm51upg.ind. 6. Click Set Path. The File Browser dialog box displays the contents of the specified media in the Files scrolling list. 7. Click Set Media & Close. 8. Select the patch from the Select Patch to Install scrolling list in the Install Patch dialog box. 9. Select the target clients on which to install the patch from the Clients to Install On scrolling list, 10. Click the right arrow to moe the selected clients to the Aailable Clients scrolling list. 11. Click Install & Close to display the Patch Install window and a list of pending installation actions. 12. Click Continue Install to begin the installation process. Additional Information: The Patch Install window displays the progress of the installation. View the messages in the task output dialog box to determine whether the patch installation was successful. If necessary, see About the log files for installation errors on page 115 for information on problem determination. 13. Click Close to close the Patch Install window. 14. Select Refresh from the View menu bar. The desktop displays the icon for the patch you installed. 15. As a precautionary measure, back up the Tioli management region databases as described in Backing up and restoring Tioli databases on page 13. Use a unique name for the new backup files. Chapter 6. Installing the product manually 65

84 Manually installing Tioli software Table 14. Product locations on installation CDs Product to install 1. IBM Tioli Monitoring software Objectie To install Tioli software manually using an existing Tioli desktop or command line interface. Background information This procedure enables you to install and set up IBM Tioli Monitoring and IBM Tioli Monitoring for Messaging and Collaboration without using the Typical or Custom installation options in the installer. Table 14 lists the installation CDs that contain the Tioli software and the directory location of the software. Use the information in this table while you perform the installation procedure, when you identify the path to the index (.IND) file for product installation. Install this software when no ersion of IBM Tioli Monitoring exists on the computer. Otherwise, see Upgrading IBM Tioli Monitoring manually on page 64 to upgrade existing IBM Tioli Monitoring software. IBM Tioli Monitoring and its resource models can co-exist with an installation of Tioli Distributed Monitoring. You do not need to uninstall Tioli Distributed Monitoring. 2. IBM Tioli Monitoring Component Serices, Version The IBM Tioli Monitoring Component Serices software proides a set of extensions for Tioli products. You must install IBM Tioli Component Serices on the same resources where you will install IBM Tioli Monitoring for Messaging and Collaboration; in other words, on the Tioli management region serer and on each gateway. 3. IBM Tioli Monitoring for Messaging and Collaboration Depending on your choice of products, you need to install products from multiple Component Software CDs. Name of installation CD on which product is located IBM Tioli Monitoring V5.1.1 IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Component Software IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Component Software 4. Language Support for the products in items 1 and 2. See Installing IBM Tioli Language Support for this product on page IBM Tioli Monitoring Web Health Console Installing the Web Health Console manually on page 72 Required authorization role install_product Before you begin See Goals for planning and preparing for installation in Table 1 on page 5 for a checklist of actiities prior to installation. As a precautionary measure, back up the Tioli management region as described in Backing up and restoring Tioli databases on page 13. Start the command line interface or Tioli desktop as described in Accessing the Tioli enironment on page IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

85 When you finish After you install IBM Tioli Monitoring for Messaging and Collaboration, complete the actiities described in Chapter 7, Completing the installation on page 75. After you install IBM Tioli Monitoring for Messaging and Collaboration, see the Chapter 2 of the IBM Tioli Monitoring for Messaging and Collaboration: User s Guide for information on setting up and using the product. Procedure You can perform this procedure from the Tioli desktop or from the command line. Command line: Run the following command from the command prompt: winstall [-c <source_dir>] [-s <serer>] -i product_code [-y].ind [-n <managed_node1> <managed_node2>...] where: -c <source_dir> Specifies the complete path to the directory containing the installation image. -s <serer> Specifies the name of the managed node to use as the installation serer. By default, the installation serer is Tioli serer. -i product_code.ind Specifies the product index file to reference for the installation. In this case, the file is product_code.ind where the following codes identify the.ind files: /cdrom/dm511.ind: IBM Tioli Monitoring, Version /images/cmptsvcs.image/cmptsvcs.ind/dm511.ind: IBM Tioli Monitoring Component Serices, Version /PRODUCT/NOTES511.IND: IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Note: You use the NOTES511.IND to manually install Version of the product for the first time. If you hae preiously installed Tioli products for Lotus Domino, manual installation requires that you use one of the following methods to install Version of the product: If you use Version of the product, run the PATCH511.IND patch in the UPGRADE directory. See Installing Tioli patches manually on page 60 for more information on patch installation. If you use Tioli Manager for Domino, Version 3.x, follow this sequence: 1. Use winstall to install Version by referencing the NOTES_51.IND product index file on the installation CDs for Version Upgrade Version of the product to Version by running the PATCH511.IND patch in the UPGRADE directory on the installation CDs for Version See Installing Tioli patches manually on page 60 for more information on patch installation. -n Installs the product on all managed nodes that do not currently hae the product installed. Chapter 6. Installing the product manually 67

86 <managed_node> Installs the product on the managed nodes you specify. Use blank spaces to separate the names of multiple managed nodes. -y Installs the product without requesting confirmation. Refer to the Tioli Management Framework Reference Manual for more information about this command. Refer to Tioli command syntax on page xi for information on Tioli command line syntax. Tioli desktop: 1. Select Install in the Desktop menu. 2. Select Install Product in the menu to display the Install Product dialog box. 3. If necessary, click OK to bypass a harmless error message about the media settings. 4. Click Select Media to display the File Browser dialog box. 5. In the Path Name text field, enter the full path to the.ind file in the CD-ROM drie. Be sure to use backward slashes (\) for Windows path names instead of forward slashes (/). 6. Click Set Path. The File Browser dialog box displays the contents of the specified media in the Files scrolling list. 7. Click Set Media & Close. 8. Select the product from the Select Product to Install scrolling list in the Install Product dialog box. 9. Select the target clients on which to install the product from the Clients to Install On scrolling list, 10. Click the right arrow to moe the selected clients to the Aailable Clients scrolling list. 11. Click Install & Close to display the Product Install window and a list of pending installation actions. 12. Click Continue Install to begin the installation process. Additional Information: The Product Install window displays the progress of the installation. View the messages in the task output dialog box to determine whether the product installation was successful. If necessary, see About the log files for installation errors on page 115 for information on problem determination. 13. Click Close to close the Product Install window. 14. Select Refresh from the View menu bar. The desktop displays the icon for the product you installed. 15. As a precautionary measure, back up the Tioli management region databases as described in Backing up and restoring Tioli databases on page 13. Use a unique name for the new backup files. Installing endpoints through an existing Tioli enironment Objectie To install and configure the endpoint software on an endpoint using the Tioli desktop or command line interface. Note: See Chapter 9, Installing and configuring the Lotus Domino component for z/os on page 97 for information on installing endpoints for Lotus Domino serers running on z/os systems. 68 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

87 Background information Creation of endpoints during installation of the product is optional. This procedure describes how to create endpoints after you hae installed the product. You must install the endpoint software on a Messaging and Collaboration serer host to enable communication with the Tioli serer. You perform this procedure from the Tioli serer. The user account you use to log on to the Tioli serer must hae membership in the Administrators group for the Windows operating system. For example, the default user in the Windows operating system, Administrator, has membership in the Administrators group by default. Tioli strongly recommends that you log on as Administrator or root. You can perform this procedure in the endpoint wizard or in the command line interface. When you use the endpoint wizard, you specify the operating system of the Messaging and Collaboration serer host. For Messaging and Collaboration serer hosts that reside on Windows machines, you must hae at least one proxy endpoint in each Windows domain that contains serers that you want to manage. The installer routine for IBM Tioli Monitoring for Messaging and Collaboration creates a proxy endpoint for the domain of the Tioli serer. This proxy endpoint enables you to install the endpoint on Windows serers that reside in the domain of the Tioli serer. You can create more proxy endpoints in other Windows domains as described in Manually creating a Windows proxy endpoint on page 50.At the end of this procedure the endpoint is running on the Messaging and Collaboration serer host. Required authorization role admin Before you begin If the Messaging and Collaboration serer on which you want to install the endpoint software resides in a domain other than the Tioli serer domain, you must create a proxy endpoint for that domain. See Manually creating a Windows proxy endpoint on page 50 to learn how to create a proxy endpoint. (Optional) Use the Planning sheet for creating endpoints in Table 8 on page 22 to prepare to perform this procedure for Messaging and Collaboration serer hosts. When you finish None Procedure This procedure describes installation of endpoints from the command line or using the Endpoint Setup Wizard in Windows. Endpoint Setup Wizard (for Windows only): 1. Insert the Tioli Management Framework, Version CD into the CD-ROM drie into the drie. 2. Run the setup executable located in the following subdirectory path:..\pc\lcf\winnt 3. Click Next in the Tioli Management Framework Endpoint Setup dialog box. 4. Read the license agreement. 5. Click Next to display the Endpoint Installation Options dialog box 6. Click Browse to change the destination directory for the software. Chapter 6. Installing the product manually 69

88 7. If you do not want to use the default directory, click Browse to change the default directory to C:\Tioli\lcf. This directory path matches the destination directory of the other product software. 8. Click Next to display the Tioli Remote Access Account dialog box. 9. Type the user name and password of the account through which Tioli Management Framework accesses remote file systems. If you do not require access to remote domains, click Next to skip this step. 10. Click Next to access the Adanced Configuration dialog box. 11. Specify the startup and configuration options information listed in the following table: Field Name Use When... Gateway The gateway uses a port number other than the default Endpoint You want to specify a port for the endpoint to use. The default is Other Use the g hostname option to specify the intercepting gateway. Use the n hostname of the endpoint option to specify the name of the endpoint you are installing as the proxy. Note: For a Custom installation of IBM Tioli Monitoring for Messaging and Collaboration, the parameters you supply in the Planner tool must match the parameters you specify in this step for the -g and -n options. 12. Click Next to continue the installation process. Additional information: The wizard reports that communication of the proxy endpoint and the gateway was successful. The endpoint is installed and logged into a gateway. The installation process configures the endpoint system to automatically start the endpoint serice when the system starts. If the system does not start, there might be a problem with the communication between the proxy endpoint and the gateway. See Cleaning up and remoing the endpoint on page 119 to remoe the endpoint, then reinstall the endpoint. 13. Click Next to display the Setup Complete dialog box. 14. Click Finish to display the Restart Windows dialog box. 15. Select No. Additional information: You can restart the system after the installation of IBM Tioli Monitoring for Messaging and Collaboration is complete. When you restart the computer the Tioli Endpoint serice is created, with the startup type set to automatic. Command line: Use the winstlcf command to install an endpoint from the command line. This command enables you to remotely install endpoints on UNIX, Windows NT, and Windows 2000 systems. For Windows systems, you must use the endpoint you created with the Endpoint Setup Wizard. See Endpoint Setup Wizard (for Windows only) on page 69 for more information, partial CLI syntax for the winstlcf command is included in the following section. See the Tioli Management Framework Reference Manual for a complete description of the winstlcf command. Note: The installation password that you specify with the winstlcf command becomes the default for all subsequent installations. 70 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

89 winstlcf [ C <locale_name>] [ d <dir_name>] [ f <file_name>] [ g <machine[+port]>] [ L <config_options>] [ l <ep_port>] [ N <endpoint>] [ n <ep_label>] [ P ][ Y ] <host> [<user_acct> <password>] where: C <locale_name> (UNIX only) Specifies the language locale for Messaging and Collaboration serer hosts that use the UNIX operating system. d <dir_name> Specifies the target directory on which to install the endpoint. The default location is /opt/tioli/lcf for UNIX and C:\Tioli\lcf for Windows NT and Windows When installing a Windows NT or Windows 2000 endpoint from a UNIX serer, forward slashes in path names are also supported. f <file_name> Specifies the file containing a list of systems on which to install endpoints. This file contains one system name per line, specifying the user ID and password to be used. Use the following format for each line in this file: host_name [ userid [ password]] g <machine[+port]> Specifies the Internet Protocol (IP) address or host name and, optionally, the port number of the gateway to which the endpoint logs in. L <config_options> Passes configuration options to the lcfd command for starting the endpoint. See the lcfd command in the Tioli Management Framework Reference Manual for a list of alid options. The example in this section shows how to specify options. If you specify multiple options or hae spaces in a single option, you must enclose the text in double quotation marks ( ). l <ep_port> Specifies the port number for the endpoint. The default port number is N <endpoint> Specifies the reference endpoint from which you install other endpoints in a Windows domain. In IBM Tioli Monitoring for Messaging and Collaboration specify one of the following alues for the <endpoint> inthe Windows domain where you are installing the endpoint: For serer endpoints in the domain of the Tioli serer, specify %HOST%_ep. For Messaging and Collaboration serer endpoints in a domain other than the domain of the Tioli serer, specify the name of the reference endpoint that you manually create, as described in Manually creating a Windows proxy endpoint on page 50. n Specifies an endpoint label proided by a user. If you do not assign a name, the command generates a unique name automatically. P This option is useful only when you are installing on remote hosts with different passwords. If each machine has the same password or if you do not use the P option, you are prompted for a global password to use for each machine. Specifies that the winstlcf command prompts for a password for each machine. Use this option only when you install endpoints on remote hosts Chapter 6. Installing the product manually 71

90 that use different passwords. If each machine uses the same password or if you do not use the P option, the winstlcf command prompts you for a global password to use for each machine. Y Specifies that the installation proceeds without confirmation. By default, this command identifies the actions that you must take to perform the installation and requests confirmation before continuing. When you use the -Y option, the winstlcf command identifies the actions and performs the installation without requesting confirmation. <host> [<user_acct> <password>] Specifies the name of the Messaging and Collaboration serer host on which to install the endpoint. When you specify only the host name, the winstlcf command uses the root or Administrator account and prompts you for the password. If you want to specify a different account and password on the host, enclose the host name, account name, and password in single quotation marks. For example, the following command installs the endpoint on the host ernon, using the DOMAIN-NT\chris account with the password pa55word: winstlcf ernon DOMAIN-NT\chris pa55word where DOMAIN-NT is the domain in which chris is located. When the Windows NT or Windows 2000 domain and the local computer use the same name for user_acct, you must proide the fully qualified name for the account. For example, if you want to specify a user account named Administrator in a domain called DOMAIN-NT, you must use the fully qualified name DOMAIN-NT\Administrator for the ariable user_acct. Examples: The following example installs and starts the endpoint software on a UNIX workstation named ernon. The C frstatement specifies that the endpoint process uses the French locale. By default, winstlcf uses the root account and prompts you for the root password on ernon. winstlcf -C fr ernon The following example installs a endpoint on a machine named cedar and prompts you for a password. The password you enter becomes the default password for all subsequent installations. winstlcf -P cedar In the following example, the winstlcf command installs the endpoint on a Messaging and Collaboration serer host named serer06 in the domain mycompany.com. The winstlcf command passes configuration options to the lcfd command to use when it starts the endpoint. The command assigns port 9131 for endpoint transactions. The g option specifies the gateway cedar and the port 1616 as the endpoint to contact for initial login. The L flag specifies options for the D flag of the lcfd command. The D lcs.machine_name flag assigns the name serer06_ep to the endpoint. winstlcf -g cedar l L "-D lcs.machine_name=serer06_ep" serer06.mycompany.com Installing the Web Health Console manually Objectie To install the Web Health Console using a command line interface. 72 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

91 Background information This procedure enables you to install and set up the Web Health Console without using the Typical or Custom installation options in the installer. Required authorization role Log on priileges for the target computer. Before you begin None When you finish See the IBM Tioli Monitoring User s Guide for information on using the console. Procedure You can perform this procedure from the command line only. Command line: 1. Copy the contents of the HCONSOLE directory of catalog files from one of the following installation CDs: For the English language, copy catalog files from the IBM Tioli Monitoring V5.1.1 installation CD. For other languages, copy catalog files from the IBM Tioli Monitoring for Messaging and Collaboration: Language Support installation CD. 2. Paste the contents of the directory in the resources directory in the following path on the target computer: INSTALL_DIR/installedApps/dm.ear/dm.war/WEB-INF/classes/com/tioli/ DmForNt/resources 3. Run the following setup executable to launch the installation wizard: On UNIX:./setupPLATFORM.bin where PLATFORM is the name of the operating system. On Windows: setup.exe 4. Follow the instructions in the wizard panels. Additional information: See IBM Tioli Monitoring User s Guide for more information. Installing the Management Console manually Objectie To install the Management Console on a workstation so that an administrator can manage Domino serers from her or his workstation. Background information The Management Console is the graphical user interface for Windows that runs as an application. The Jaa software requires approximately 65 MB of disk space. The Management Console software requires approximately 80 MB of disk space. Required authorization role Any user who can log on to the workstation can install the Management Console. Before you begin None Chapter 6. Installing the product manually 73

92 When you finish None Procedure Tioli Desktop: 1. Open the MGMNT directory of the installation CD. 2. Run setup.exe. 3. Click Next. 4. Select the I accept the terms of the license agreement radio button in the license agreement panel, and then click Next. 5. Select a location for installation as follows: Click Next to accept the default destination. OR Select a different, existing destination: a. Click Browse. b. Select a directory. c. Click Next. 6. Click Next when the summary panel appears. 7. Click Finish to exit the wizard. 74 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

93 Chapter 7. Completing the installation This section describes how to erify the installation and enable functionality for IBM Tioli Monitoring for Messaging and Collaboration. Table 15. Guidelines for completing the installation of the product Goal Refer to Verify the success of the installation of the managed Verifying the installation of the product on page 75 nodes and endpoints. Changing the gateway assignment of an endpoint. Changing the gateway assignment of an endpoint on page 76 Set up the Jaa Runtime Enironment, Version on endpoints. This software enables distribution of resource models. Install the Jaa software on endpoints that do not hae it. If the Jaa software already exists on the endpoint, run a Tioli task to link the software to IBM Tioli Monitoring. Map monitors to IBM Tioli Monitoring for Messaging and Collaboration. (Optional) Load class files that enable you to customize the resource models that come with the IBM Tioli Monitoring for Messaging and Collaboration. Installing the Jaa Runtime Enironment on page 77 Linking to an existing Jaa Runtime Enironment on page 78 Chapter 8, Migrating from preious ersions of the product on page 89 Installing files to enable customization of resource models on page 80 See IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide for information on using the resource models. Enable the storage of historical data that you can use in the Tioli Enterprise Data Warehouse. Assign authorization roles required to use the product to manage and monitor serers. Install aailable language support packages after installation when you choose to not install language packs during installation. Update enablement files for the Web Health Console when you upgrade or add components to the product. See IBM Tioli Monitoring Workbench User s Guide to learn how to use the optional Workbench tool to create custom resource models to use with IBM Tioli Monitoring for Messaging and Collaboration. Installing files to enable Tioli Enterprise Data Warehouse on page 81 The IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide describes required authorization roles. Installing IBM Tioli Language Support for this product on page 84 Updating Web Health Console files on page 87 Verifying the installation of the product Objectie To erify successful installation of the product. 75

94 Background information This procedure describes how to use the Tioli command line interface to list the elements of the Tioli enironment. You should complete this procedure before running the product to confirm correct installation and connectiity for all elements. Required authorization role The installation routine for IBM Tioli Monitoring for Messaging and Collaboration creates the Tioli administrator who is authorized to perform this procedure. On UNIX, the user who runs the installer must hae root priileges. On Windows, the user who runs the installer must hae membership in the Administrators group. For other users, one of the following Tioli roles is recommended: user, admin, senior, or super Before you begin Access the Tioli enironment as described in Accessing the Tioli enironment on page 56. When you finish If you cannot erify connection with an endpoint, see Testing endpoint connectiity on page 118. Procedure You can perform this procedure from the Tioli desktop or from the command line. Command Line: Run the wlsinst command to list the products and patches in the Tioli enironment. The following example lists the products installed, the host name and interpreter type on which each product was installed, and the directories in which each product was installed: wlsinst -p -h where: p Lists all products installed in the Tioli management region. h Lists the host name and interpreter type of the machines on which the products or patches are installed. Run the wep command to list all gateways and their associated endpoints in the Tioli management region. In the recommended configuration for this product, you install a gateway on each managed node that you create. The following command lists all managed nodes or gateways in the Tioli management region: wep ls See the Tioli Management Framework Reference Manual for a complete description of all options aailable for these commands. Desktop: 1. Access the Tioli desktop as described in Accessing the Tioli enironment on page View the icons for the managed resources that you installed to erify that they exist. Changing the gateway assignment of an endpoint Objectie To assign an endpoint to a different gateway on a managed node. 76 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

95 Background information An endpoint communicates with the Tioli management region through gateway software that exists on a managed node. By default, the installer for IBM Tioli Monitoring for Messaging and Collaboration assigns endpoints to managed nodes wheneer possible. The installer assigns endpoints to the Tioli management region serer only when no other managed node is aailable. In IBM Tioli Monitoring for Messaging and Collaboration, the primary role of the Tioli management region serer is to administer managed nodes. The primary role of managed nodes is to administer endpoints. If you use the Tioli management region to administer endpoints, you decrease the amount of system resources aailable for the administration of managed nodes. If you want the Tioli management region to administer endpoints, you can change the gateway assignment as described in this procedure. Required authorization role senior Before you begin None When you finish None Procedure You can perform this procedure from the command line. Command line: 1. Access the Tioli command line interface as described in Accessing the Tioli enironment on page Run the wep ls command to iew gateway assignments. 3. Run the following command: wep <endpoint> migrate <gateway> where <endpoint> is the name of the endpoint to migrate and <gateway> is the name of the new gateway assignment. Installing the Jaa Runtime Enironment Objectie To install the Jaa Runtime Enironment and link it to IBM Tioli Monitoring. Background information Each endpoint in an IBM Tioli Monitoring system requires a local installation of the Jaa Runtime Enironment (JRE), Version or Solaris endpoints must hae Version The runtime enironment enables the distribution and running of resource models. Installation images for the Jaa Runtime Enironment are aailable on the IBM Tioli Monitoring, Version 5.1.1: Tools installation CD. You can choose one of the following setup methods: Use the wdmdistrib command or the Jaa Runtime Enironment manual installation process. The Jaa software for this installation options is aailable on the product CD in compressed format. This procedure describes how to use the wdmdistrib command to install the Jaa Runtime Enironment. Chapter 7. Completing the installation 77

96 If the endpoint already has an appropriate ersion of the Jaa Runtime Enironment installed, perform the procedure Linking to an existing Jaa Runtime Enironment to link IBM Tioli Monitoring for Messaging and Collaboration to the runtime enironment. Use the Tioli Software Installation Serice (SIS). See Using Tioli Software Installation Serice on page 55 for more information on using this method to install the runtime enironment. After you use this method you must perform the Linking to an existing Jaa Runtime Enironment procedure. If you do not install and link the Jaa Runtime Enironment, the deployment of resource models fails. The use of an IBM ersion of the Jaa Runtime Enironment is recommended for support purposes. All ersions of the Jaa Runtime Enironment on the IBM Tioli Monitoring CD are supplied by IBM, except for the HP-UX ersion. Prerequisites for the Jaa Runtime Enironment are described in a readme file in the JRE directory on the product installation CD for IBM Tioli Monitoring. Required authorization role The installation routine for IBM Tioli Monitoring for Messaging and Collaboration creates the Tioli administrator who is authorized to perform this procedure. On UNIX, the user who runs the installer must hae root priileges. On Windows, the user who runs the installer must hae membership in the Administrators group. Other users must hae one of the following roles: admin, senior, or super. Before you begin Access the Tioli enironment as described in Accessing the Tioli enironment on page 56. When you finish Procedure You can perform this procedure from the command line. Command Line: Run the following command to install the Jaa Runtime Enironment and link it to IBM Tioli Monitoring: wdmdistrib J "JRE_location_dir" l subscriber where JRE_location_dir Specifies the complete path to the directory on a local drie where Jaa Runtime Enironment (JRE) is located on the installation CD (excluding the platform directory). Enclose the path in quotation marks. subscriber Specifies the name of the subscriber to which you want to distribute the software. See the IBM Tioli Monitoring User s Guide for full information on this ariable. See the IBM Tioli Monitoring User s Guide for full information on the wdmdistrib command. Linking to an existing Jaa Runtime Enironment Objectie To link the IBM Tioli Monitoring software to an existing Jaa Runtime Enironment. 78 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

97 Background information Endpoints must run the Jaa Runtime Enironment (JRE), Version or Solaris endpoints must hae Version This software enables the distribution and running of resource models. The Tioli DMLinkJre task enables the endpoint to identify the correct path to the Jaa software. When the required Jaa Runtime Enironment is installed on the computer before you install IBM Tioli Monitoring for Messaging and Collaboration, you must run the DMLinkJre task. You also must run the DMLinkJre task when you use Tioli Software Installation Serice or the installation routine that Sun Microsystems, Inc. proides to install the runtime enironment. Running the DMLinkJre task is not required when you use the wdmdistrib command to install the runtime enironment. See Installing the Jaa Runtime Enironment on page 77 for more information on these options. Required authorization role On UNIX, the user who runs the installer must hae root priileges. On Windows, the user who runs the installer must hae membership in the Administrators group. Before you begin Install the Jaa Runtime Enironment, as described in Installing the Jaa Runtime Enironment on page 77. When you finish None Procedure You can perform this procedure from the Tioli desktop only. Tioli desktop: 1. Select TMR Connections in the Desktop menu. 2. Select Top Leel Policy Regions in the sub-menu to display the Top Leel Policy Regions dialog box. 3. Double-click the TioliDefaultMw2kRegion icon to display the Policy Region dialog box. 4. Double-click the IBM Tioli Monitoring Tasks task library icon to display the Task Library dialog box. 5. Double-click the DMLinkJre task icon to display the Execute Task dialog box. 6. Select the endpoint or endpoints that you want to link to the Jaa software. Additional information: Alternatiely, you can select target endpoints by selecting the profile managers that contain those endpoints. The installation path for the Jaa software on each endpoint must be the same on each target endpoint in that profile. Note: The task alidates the link to the Jaa software and adises you of a path error. The path error becomes eident later, when the distribution of resource models to the endpoint generates an error stating that the Jaa software is missing or not installed. 7. Click Execute to display the Configure Task Arguments dialog box. 8. Type the fully-qualified path to the top-leel directory of the Jaa software. Additional information: For example, if the Jaa software is installed in the /usr/jaa/bin/jaa directory path, type this alue in the text field: /usr/jaa Chapter 7. Completing the installation 79

98 9. Click Set & Execute. Additional information: To confirm success of this operation distribute a resource model to the endpoints you hae linked. Distribution is described in the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide. When the DMLinkJre task is successful, distribution of the resource model completes without generating an error message. Installing files to enable customization of resource models Objectie To load class files that enable you to customize the resource models that come with the product. Background information The IBM Tioli Monitoring Workbench is a programming tool for creating, modifying, debugging, and packaging resource models for use with IBM Tioli Monitoring products. Samples of best practice resource models hae also been proided for your use within the Workbench. You can use these resource models as working examples for creating new resource models. The Tioli Maintenance and Support Contract coers assistance with problem and issues relatie to the operation of the IBM Tioli Monitoring Workbench, but does not coer assistance for new or modified resource models other than the ones that are included in the Workbench. The IBM Tioli Monitoring Workbench User s Guide describes how to use the Workbench. When you customize one of these resource models in the Workbench, you must associate the new resource model with a class file called a Managed Object Format (MOF) file. This procedure describes how to make the.mof files for IBM Tioli Monitoring for Messaging and Collaboration aailable to Workbench. A.mof file is an ASCII file that contains the formal definition of a resource. For example, the DB2 CPU Utilization resource model monitors the total DB2 system and user central processing unit time used by the database manager agents in a DB2 installation. The.mof file for this resource model defines the properties (CPU utilization) of this resource. The.mof file format adheres to the platform-neutral Common Information Model (CIM) standard of the Distributed Management Task Force (DMTF) industry consortium. This standard reduces the cost and complexity of managing computer resources. The Workbench tool is aailable on Windows only and it must hae access to the resources of the Microsoft Windows Management Instrumentation (WMI) SDK. Information and software for the SDK is aailable through the Microsoft Corporation. Specifically, this procedure uses the MOF Compiler, mofcomp.exe, that comes with the SDK. See the Windows Management Instrumentation: Platform SDK online help for more information. Required authorization role You must hae log on priileges for the target computer. Before you begin Install the Microsoft Windows Management Instrumentation (WMI) SDK from Microsoft Corporation. WMI already exists on Windows 2000 systems. 80 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

99 When you finish See IBM Tioli Monitoring Workbench User s Guide to learn how use the optional Workbench tool. You use the Workbench to create resource models based on the standard resource models that come with IBM Tioli Monitoring for Messaging and Collaboration. As part of the creation process, you create a dependency between the new resource model and one of the.mof files you hae installed. Procedure You can perform this procedure from the command line only. Command line: 1. Access the mofcomp.exe executable in the following directory path: %SystemRoot%\system32\wbem 2. Run the following command: mofcomp -N:Root\Cim2 mof_file_name where mof_file_name is the name of a.mof file for IBM Tioli Monitoring for Messaging and Collaboration. \\Root\Cim2 refers to the namespace in the class repository that includes resource model information. Additional information: The product.mof files are located on the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Component software installation CD. Installing files to enable Tioli Enterprise Data Warehouse Objectie To install application warehouse packs that proide the extract, transform, and load (ETL) processes and that enable reporting in the Tioli Enterprise Data Warehouse report interface. Background information Note: This procedure describes installation of enablement files on a Tioli Enterprise Data Warehouse enironment that exists on a single computer. This type of installation simplifies configuration and setup, but might sere only as a test or demonstration enironment, and can only be installed on Windows. Most monitoring enironments require a distributed installation of Tioli Enterprise Data Warehouse. To learn how to install and configure enablement files for a distributed enironment, see Installing and Configuring Tioli Enterprise Data Warehouse, Version 1, Release 1. You can extract, transform, and load operational data from resource models into the central data warehouse database. Furthermore, you can extract, transform, and load historical data to produce historical reports. This procedure describes installing the warehouse packs on a single, dedicated computer that has all of the Tioli Enterprise Data Warehouse components. Specifically, the central data warehouse ETL (ETL1) process and the data mart ETL (ETL2) process perform the respectie tasks: Extract operational data from the IBM Tioli Monitoring for Business Integration resource models and load it into the central data warehouse. This process enables data collection for software components that are based on IBM Tioli Monitoring, Version Chapter 7. Completing the installation 81

100 Extract historical data from the central data warehouse for use in tabular and graphical reports. This process enables custom functionality for IBM Tioli Monitoring for Business Integration. Consider the following points: The installer must hae a alid, fully qualified host name to complete the installation. The user who performs the installation must hae a alid user name and password to access the DB2 instance for this product. See the Installing and Configuring Tioli Enterprise Data Warehouse, Version 1, Release 1, Guide for detailed information on all installation and configuration options for the warehouse packs, as well as uninstallation information. See the Installing and Configuring sections in the following documents for information on software prerequisites, supported hardware and platforms, limitations, and database sizing considerations, see IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Warehouse Enablement Guide. Required authorization role superadmin in the Tioli Enterprise Data Warehouse enironment Before you begin Install Tioli Enterprise Data Warehouse and the required DB2 database software (IBM DB2 Uniersal Database Enterprise Edition) as described in the Installing and Configuring Tioli Enterprise Data Warehouse, Version 1, Release 1 Guide. When you finish Run ETL processes to extract, transform, and load Lotus Domino Integrator data. Generate tabular and graphical reports as described as described in IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide. Install and configure the Tioli Enterprise Data Warehouse Support Component. See the Integration with Tioli Enterprise Data Warehouse chapter in the IBM Tioli Monitoring User s Guide for details. You must install this component first on the Tioli management region serer and then on all managed nodes. Procedure You perform this procedure using the Tioli Enterprise Data Warehouse installation program. Installation wizard: 1. Log on to the computer that runs Tioli Enterprise Data Warehouse. Additional information: On Windows, the user who runs the installer must hae membership in the Administrators group. 2. Run the Windows setup executable setup.exe located in the root directory of the Tioli Enterprise Data Warehouse installation CD. 3. Install the IBM Tioli Monitoring, Version warehouse pack that proides the central data warehouse ETL1 that extracts data and loads it into the central data warehouse by doing the following (This warehouse pack ships on the IBM Tioli Monitoring, Version CD (LK3T ): a. Click Next to display the installation options panel. b. Select Application Installation only. c. Select the directory path where you want to install the program. Additional information: You must install the warehouse pack in the installation directory for Tioli Enterprise Data Warehouse. 82 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

101 d. Click Next. e. Type the host name. Additional information: The wizard requires the fully qualified host name for the computer. For example, the fully qualified host name for myhost might be myhost.mycompany.com. f. Type the user name and password for configuring DB2. g. Type the directory path for the warehouse pack configuration file. Additional information: The twh_app_install_list.cfg configuration file for this warehouse pack is located on the IBM Tioli Monitoring, Version CD in directory /tedw_apps_etl/amx. h. Select Now to erify the source directory immediately. i. Click Next. j. If the wizard detects a path error, modify the source directory path and click Next again. k. Click Next. Additional information: This procedure does not require use of the option to install additional packages. The wizard displays a summary of the program installation, including disk space required. l. Click Install. m. Click Finish in the final summary screen. Additional information: For troubleshooting information, see the troubleshooting chapter in Installing and Configuring Tioli Enterprise Data Warehouse, Version 1, Release 1, Guide. 4. Install the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.0: Lotus Domino warehouse pack that proides the data mart ETL2 that extracts data from the central data warehouse for use in tabular and graphical reports. (This warehouse pack ships on the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Lotus Domino Component Software CD.) a. Repeat Steps 1 and 2 to re-launch the Tioli Enterprise Data Warehouse installation wizard. b. Click Next to display the installation options panel. c. Select Application Installation only. d. Select the directory path where you want to install the program. e. Click Next. f. Type the host name. Additional information: The wizard requires the fully qualified host name for the computer. For example, the fully qualified host name for myhost might be myhost.mycompany.com. g. Determine which warehouse pack you want to install and type the directory path for the its configuration file. h. Type the directory path of the program files. Additional information: The twh_app_install_list.cfg configuration file is located in the following path, /tedw_apps_etl/dom, ontheibm Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Lotus Domino Component Software CD. i. Select Now to erify the source directory immediately. j. Click Next. Chapter 7. Completing the installation 83

102 k. If the wizard detects a path error, modify the source directory path and click Next again. l. Click Next. Additional information: This procedure does not require use of the option to install additional packages. The wizard displays a summary of the program installation, including disk space required. m. Click Install. n. Click Finish in the final summary screen. Additional information: The twh.log file lists eents that occur during the installation. This file is located in the directory containing the installed Tioli Enterprise Data Warehouse program. By default, this directory path is C:\Program Files\TWH. The Enironment tab of the Windows System Properties control panel displays the path alue for the enironment ariable TWH_TOPDIR in your installation. 5. Stop and restart the following serices for Tioli Presentation Serices: Serer for IBM Console Web Serices for the IBM Console See the Starting and stopping Tioli Presentation Serices appendix in Installing and Configuring Tioli Enterprise Data Warehouse, Version 1, Release 1 Guide for further information. 6. If necessary, perform final configuration tasks to enable reporting. See the chapter on creating reports in the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide. Installing IBM Tioli Language Support for this product Objectie To install language support packages to enable one or more of the nine aailable national language ersions of the product. Background information By default, IBM Tioli Monitoring for Messaging and Collaboration is enabled in English. To enable other languages, install the appropriate language support pack from one of the following installation CDs: IBM Tioli Monitoring for Messaging and Collaboration Version 5.1.1: Lotus Domino Language Support IBM Tioli Monitoring V5.1.1: Language Support You can install multiple language support packages for a single product. Language support packages exist for the languages listed in Table 16. The table also shows product-name prefixes and language-support suffixes. You concatenate a prefix and a suffix to form the complete name of the.ind file. For example, the following.ind files contain German language support packages for DB2: DOM_DE.IND is the name of the German language support package for DB2. AMW_DE.IND is the name of the German language support package for IBM Tioli Monitoring. 84 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

103 Table 16. Language support and names of corresponding installation index (.IND) files Language Prefix for DOM Prefix for IBM Tioli Monitoring Language code suffix Brazilian Portuguese Chinese (simplified) Chinese (traditional) DOM AMW _PTBR (Exception: the suffix for IBM Tioli Monitoring is _PT_B) DOM AMW _ZHCH (Exception: the suffix for IBM Tioli Monitoring is _ZH_C) DOM AMW _ZHTW (Exception: the suffix for IBM Tioli Monitoring is _ZH_T) French DOM AMW _FR German DOM AMW _DE Italian DOM AMW _IT Japanese DOM AMW _JA Korean DOM AMW _KO Spanish DOM AMW _ES Some command line and keyword options are not translated in the language support packages. This approach aoids any programming complexities for scripts that can run under multiple locales. Run the scripts under the locale in which the retrieed data is stored. Tioli Management Framework uses the software in the language support packages. For more information, see the following documents on the installation CDs for Tioli Management Framework: Chapter 2 Internationalization in the Tioli Enterprise Installation Guide Release Notes Required authorization role install product Before you begin As a precautionary measure, back up the Tioli management region as described in Backing up and restoring Tioli databases on page 13. Start the command line interface or Tioli desktop as described in Accessing the Tioli enironment on page 56. When you finish The installer enables language support for the Web Health Console automatically. If you manually installed the console, see Installing the Web Health Console manually on page 72. If you install a language pack after you create one or more objects, the message catalog files are not automatically updated on the endpoints for those objects. To update the message catalogs for the language pack, right-click the object in the Tioli desktop and select Push Dependencies in the Diagnostics menu. The new language pack dependencies are downloaded to the endpoint. Alternatiely, you can recreate the objects that you created before installing the language pack. Chapter 7. Completing the installation 85

104 Procedure You can perform this procedure from the Tioli desktop or from the command line. Command line: 1. Insert the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1: Language Support CD in the CD-ROM drie. 2. Access the Tioli command line interface as described in Accessing the Tioli enironment on page Type bash and press Enter to access the complete libraries of Tioli commands. 4. Execute the following command: winstall -c /cdromdrie -i INDFILENAME y where INDFILENAME is the language you want to install and cdromdrie is the path to the location of the.ind files. Additional information: When the command completes, the message Finished Product Installation is displayed. 5. Repeat Step 4 to install additional language support packages. Refer to the Tioli Management Framework Reference Manual for more information about the winstall command. Refer to Tioli command syntax on page xi for information on Tioli command line syntax. Tioli desktop: 1. Select Install in the Desktop menu. 2. Select Install Product in the sub-menu to display the Install Product dialog box. 3. If necessary, click OK to bypass a harmless error message about the media settings. 4. Click Select Media to display the File Browser dialog box. 5. In the Path Name text field, enter the full path to the language support files in the CD ROM drie. Be sure to use backward slashes (\) for Windows path names instead of forward slashes (/). 6. Click Set Path to refresh the iew. Additional information: The Directories list displays.cfg files and the Files list displays the.ind files that include the names of all nine languages. 7. Click Set Media & Close to return to the Install Product dialog box. 8. Select the language that you want to install in the Select Product to Install list. For example, select IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.1, [de] German language to choose German language support for installation. 9. Select the target clients on which you want to install language support from the Aailable Clients scrolling list. 10. Click the right arrow to moe the selected clients to the Clients to Install On scrolling list. 11. Click Install & Close to launch the installation progress window. 12. Click Continue Install when the prompt is displayed. 13. Click Close when the Finished Product Installation message is displayed. 14. Repeat these steps to install another language support package. 86 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

105 Updating Web Health Console files Objectie To update the Web Health Console files when you install a new component or upgrade IBM Tioli Monitoring for Messaging and Collaboration. Background information This procedure describes how to update the class files for the Web Health Console when you add a component to the product. The class files specify the standard text that the console displays. Wheneer you add or upgrade components for your installation of IBM Tioli Monitoring for Messaging and Collaboration you must perform this procedure. For example, if you upgrade Version of the product to a later release, you must update the class files located on the computer that hosts the Web Health Console. The new class files become aailable after you restart the Web Application Serer that enables the console. When you install the Web Health Console for the first time, the installer automatically installs the required class files and this procedure is not necessary. When you install the product without using the installer, use the procedure Installing the Web Health Console manually on page 72. Required authorization role The same authorization roles that are required for the target computer. Before you begin None When you finish None Procedure You can perform this procedure from the command line only. Command line: 1. Copy the contents of the HCONSOLE directory of catalog files from one of the following installation CDs: For the English language updates to IBM Tioli Monitoring, copy catalog files from the IBM Tioli Monitoring V5.1.1 installation CD. For the English language updates to IBM Tioli Monitoring for Messaging and Collaboration, copy catalog files from the IBM Tioli Monitoring for Messaging and Collaboration installation CDs. For other languages, copy catalog files from the IBM Tioli Monitoring for Messaging and Collaboration: Language Support installation CDs. 2. Paste the contents of the HCONSOLE directory in the followingresources directory on the target computer that hosts the Web Health Console: INSTALL_DIR/installedApps/dm.ear/dm.war/WEB-INF/classes/com/tioli/ \ DmForNt/resources Chapter 7. Completing the installation 87

106 88 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

107 Chapter 8. Migrating from preious ersions of the product This chapter describes how to migrate to IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino from Tioli Manager for Domino, Version 3.x. There is no fully automated migration process, but the compatibility mode in IBM Tioli Monitoring enables you to work with monitors until you want to migrate to resource models. IBM Tioli Monitoring for Messaging and Collaboration supports concurrency with Tioli Distributed Monitoring. You can continue to run the old monitoring systems based in Tioli Distributed Monitoring (specifically, Tioli Manager for Domino) after you hae installed IBM Tioli Monitoring for Messaging and Collaboration. You can gradually reproduce the functionality of your old monitors in resource models and run the resource models in IBM Tioli Monitoring. See IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide for more information on using resource models. Table 17. Guidelines for migrating from preious ersions of the product Goal Refer to Migrate Tioli Manager for Domino software Migrate Tioli Distributed Monitoring software to IBM Tioli Monitoring software Map monitors in Tioli Distributed Monitoring to resource models in IBM Tioli Monitoring, Version Map tasks in Tioli Manager for Domino to IBM Tioli Monitoring for Messaging and Collaboration Map commands in Tioli Manager for Domino to IBM Tioli Monitoring for Messaging and Collaboration Chapter 8, Migrating from preious ersions of the product on page 89 Chapter 6, Installing the product manually on page 55 Table 18 on page 91 Mapping Tioli Manager for Domino tasks on page 93 Mapping Tioli Manager for Domino commands on page 94 Migrating from preious Tioli software Objectie To migrate from Tioli Manager for Domino, Version 3.x, to IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino, Version 5.1.0, using an installation wizard with predefined default alues to automatically create a Tioli enironment and install IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. Note: When you want to migrate from Tioli Manager for Domino, Version 3.x, to Version of Monitoring for Lotus Domino, you must perform this procedure first. After you complete this procedure, upgrade Version to Version as described in Installing Tioli patches manually on page

108 Background information After you install the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino software, the Tioli Manager for Domino 3.x continues to be enabled on your system. The following icons will exist: On the Tioli desktop: A IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino icon and a Tioli Manager for Domino icon On the operating system desktop: A IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Management Console icon and a Tioli Manager for Domino Management Console icon You can manage your pre-migrated Lotus Domino Serers from the Tioli Manager for Domino Management Console. Your newly created or updated Lotus Domino Serers can be managed from the IBM Tioli Monitoring for Messaging and Collaboration 5.1 Management Console. When iewing your existing Lotus Domino Serer objects in the IBM Tioli Monitoring for Messaging and Collaboration 5.1 Management Console, the objects are gray. This will help you identify your non-migrated Lotus Domino Serer objects. Required authorization On UNIX, the user who installs the product must hae root priileges. On Windows, the user who installs the product must hae membership in the Administrators group. Before you begin Ensure that you hae all of the required software and patches installed on your system prior to migration. For a list of these requirements, see System requirements for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino on page 7. You must hae Tioli Manager for Domino, Version 3.x, with both patches 6 and 7 installed on your system. If you hae Application Serices, Version 1.2 installed on your system, you will need the following patch, Application Serices, Patch 1.2 ASV If you hae Tioli Distributed Monitoring, Version 3.7 installed on your system, you need the following patches: Patch 3.7-DMN-0001 Patch 3.7-DMN-0004 Patch 3.7-DMN-0020 Patch 3.7-DMN-0023 Patch 3.7-DMN-0025 Patch 3.7-DMN-0028 When you finish Run the Configure TEC for Messaging and Collaboration task to enable tasks to be sent to the Tioli Enterprise Console. For information on running this task, see the Lotus Domino Serer tasks chapter in the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Reference Guide. Procedure 1. Use the installation CDs for Version of Monitoring for Lotus Domino to install the product as follows: 90 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

109 Use the winstall command and reference the NOTES_51.IND product index file as described in Manually installing Tioli software on page 66. OR Use the installation wizard to perform a Typical installation of the product as described in Chapter 4, Performing a Typical installation on page Run the wtmdupdateaddin command to manually migrate Lotus Domino Serers to the IBM Tioli Monitoring for Messaging and Collaboration, Version 5.1.0: Lotus Domino software. For information on running this command, see the Lotus Domino Serer commands chapter of the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Reference Guide. 3. You must delete any pre-migration Domino Performance Stations and then recreate them using the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino software. For information on how to delete and then configure Domino Performance Stations, see the Working with Domino Performance Stations chapter of the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide. Mapping monitors to resource models This section proides the following two types of information : monitors in the preious software, Tioli Manager for Domino, that correspond to resource models and proiders in the software, IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. See Table 18. proiders and the monitors that correspond to them in the preious software, Tioli Manager for Domino. See Table 19 on page 92. The following table lists the specific monitors that correspond to each resource model: Table 18. Tioli Manager for Domino monitors and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino resource models and proiders Tioli Manager for Domino monitors Dbcorruption and LogQuery monitors Mail.Dead and Mail.Waiting monitors Replication check monitor Serer Aailability and LogQuery monitors IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino resource models Domino Database Management resource model Domino Mail Statistics Monitor resource model Domino Replication Status resource model Domino Serer Aailability resource model IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino proiders DMXDominoDBCorruption DMXDominoStalledMail DMXDominoReplCheck DMXDominoSererAailability Serer Health monitor Domino Serer Health resource model DMXDominoSererHealth SMTPMTA.Dead and SMTPMTA.Waiting monitors Domino SMTP Mail Statistics resource model DMXDominoStat DPSCalendarEntry monitor DPSCalendarEntry resource model DMXDominoPerformanceStation DPSDatabaseAccess monitor DPSDatabaseAccess resource model DMXDominoPerformanceStation DPSIntegrity monitor DPSIntegrity resource model DMXDominoPerformanceStation DPSNABSearch monitor DPSNABSearch resource model DMXDominoPerformanceStation Chapter 8. Migrating from preious ersions of the product 91

110 Table 18. Tioli Manager for Domino monitors and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino resource models and proiders (continued) Tioli Manager for Domino monitors IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino resource models IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino proiders DPSNetEcho monitor DPSNetEcho resource model DMXDominoPerformanceStation DPSReplicateLocal monitor DPSReplicateLocal resource model DMXDominoPerformanceStation DPSRoundTripMail monitor DPSRoundTripMail resource model DMXDominoPerformanceStation DPSWebAccess monitor DPSWebAccess resource model DMXDominoPerformanceStation The following table lists all of the monitors and their proiders that are included in the Tioli Manager for Domino software, including the ones that do not currently hae corresponding resource models: Table 19. Tioli Manager for Domino proiders and the corresponding Tioli Manager for Domino monitors Tioli Manager for Domino proiders Tioli Manager for Domino monitors DMXDominoClusterStatus ClusterStatusSync/Async DMXDominoDbActiity N/A DMXDominoDBCorruption DbCorruptionSync/Async DMXDominoDBFrequency DatabaseFrequency DMXDominoDBStatistics DbStatisticsSync/Async, DbTemplateSync/Async, UMStatisticsSync/Async DMXDominoLogQuery LogQuerySync/Async DMXDominoMailBox MailInBox DMXDominoReplCheck ReplicationCheckSync/Async DMXDominoSererAailability DominoSererAailable DMXDominoSererHealth SererHealthSync/Async DMXDominoStalledMail StalledMailSync/Async, MailWaitingSync/Async DMXDominoStat Agent, Calendar, Comm, Database, DatabaseRM, Disk, DiskSys, Domino, ICM, IMAP, LDAP, Mail, Memory, MemoryAssessment, MTA, NET, NETBIOS, NNTP, NNTPRemote, Object, POP3, QOS, Replication, Serer, SMTP, SMTPMTA, SPIN, SwapDisk, Web, XPC DMXDominoTDPSchedule TdpSchedule DMXDominoTransactionLogSize TransLogSize DMXDominoTransactionLogStatus TransLogStatus DMXDominoPerformanceStationIntegrity DPSIntegrity DMXDominoPerformanceStation DPSRoundTripMail, DPSReplicateLocal, DPSDatabaseAccess, DPSWebAccess, DPSNABSearch, DPSCalendarEntry, DPSNetEcho N/A DataRollupInteral 92 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

111 The following profiles do not hae resource models associated with them: Domino 4.6 Web Serer Resource Models Domino 4.6 Application Serer Resource Models Domino 4.6 News Serer Resource Models Domino 5.0 Web Serer Resource Models Domino 5.0 Application Serer Resource Models Domino 5.0 News Serer Resource Models For these profiles to be associated with resource models, the resource models must be created. See the Creating resource models using the IBM Tioli Monitoring Workbench appendix in the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Reference Guide. Mapping Tioli Manager for Domino tasks Table 20 contains a list of tasks from the preious ersion of the software, Tioli Manager for Domino, and corresponding tasks for the software, IBM Tioli Monitoring for Messaging and Collaboration. Any tasks included with Tioli Manager for Domino, but not included with IBM Tioli Monitoring for Messaging and Collaboration are noted as withdrawn in the table. Table 20. Tioli Manager for Domino tasks and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino tasks Tioli Manager for Domino task Actiate Databases Archie Transactional Log Check Database Corruption Check for Inactie Users Check Health Check Replication Get ACLs Inactiate Transaction Logging Incremental Backup Mail Waiting Modify Database ACLs Query Actiate Query Backup Query Log Query NAB Query Restore Query Statistics Query Transaction Log Recycle NT Serer Serice Recycle Serer Remote Console Restore Databases IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino task Actiate Databases Archie Transactional Log Check Database Corruption Check for Inactie Users Check Health Check Replication Get ACLs Inactiate Transaction Logging Incremental Backup Mail Waiting Modify Database ACLs Query Actiate Query Backup Query Log Query NAB Query Restore Query Statistics Query Transaction Log Recycle NT Serer Serice Recycle Serer Remote Console Restore Databases Chapter 8. Migrating from preious ersions of the product 93

112 Table 20. Tioli Manager for Domino tasks and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino tasks (continued) Selectie Backup Selectie Backup Start Engine Start Engine Start Serer Start Serer Stop Engine Stop Engine Stop Serer Stop Serer Verify Mail Verify Mail N/A Cluster Status N/A Delete Serer N/A Domino TBSM Discoery N/A Mailbox Statistics N/A Purge Mail N/A Query Database Actiity N/A Restart Addin N/A Serer Aailable N/A Stalled Mail N/A Update Addin Configure TEC for TMD Configure TEC for Messaging and Collaboration Clean Database withdrawn Configure Notes Client Install 3.1 withdrawn Configure Notes Client Upgrade 3.1 withdrawn Start Monitors withdrawn Start Station Monitors withdrawn Stop Monitors withdrawn Stop Station Monitors withdrawn Mapping Tioli Manager for Domino commands Table 21 contains a list of commands from the preious ersion of the product, Tioli Manager for Domino, and the corresponding commands for the software, IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. Any commands included with Tioli Manager for Domino, but not included in IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino are noted as withdrawn in the table. Table 21. Tioli Manager for Domino commands and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino commands Tioli Manager for Domino command IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino command wtmdaclmod wtmdaclmod wtmdactiatedbs wtmdactiatedbs wtmdarchietranslog wtmdarchietranslog wtmdcheckhealth wtmdcheckhealth 94 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

113 Table 21. Tioli Manager for Domino commands and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino commands (continued) wtmdcheckrep wtmdcheckrep wtmdchkdbcorruption wtmdchkdbcorruption wtmdchkinactusers wtmdchkinactusers wtmdcleandb withdrawn N/A wtmdclusterstatus wtmdcollectsupportdata witmcollectsupportdata wtmdcreateserer wtmdcreateserer wtmddbactiity wtmddbactiity N/A wtmddbstats N/A wtmddbusage wtmddelet wtmddelet wtmddeleteserer wtmddeleteserer wtmdgetacl wtmdgetacl wtmdgetsrname wtmdgetsrname wtmdinactiatetranslog wtmdinactiatetranslog wtmdincrementalbackup wtmdincrementalbackup wtmdlocateserer wtmdlocateserer N/A wtmdmailbox wtmdmailwaiting wtmdmailwaiting wtmdpingtioli wtmdpingtioli wtmdpurg wtmdpurg wtmdqueryactiiate wtmdqueryactiate wtmdquerybackup wtmdquerybackup wtmdquerylog wtmdquerylog wtmdquerynab wtmdquerynab wtmdqueryrestore wtmdqueryrestore wtmdquerystat wtmdquerystat wtmdquerytranslog wtmdquerytranslog wtmdrasaddtrace wtmdrasaddtrace wtmdrascreatelog wtmdrascreatelog wtmdrasdeletelog wtmdrasdeletelog wtmdrasgetlog wtmdrasgetlog wtmdquerylog wtmdquerylog wtmdrecyclentsrsc wtmdrecyclentsrsc wtmdrecycleserer wtmdrecycleserer wtmdremoteconsole wtmdremoteconsole N/A wtmdrestartaddin wtmdrestoredbs wtmdrestoredbs wtmdselectiebackup wtmdselectiebackup N/A wtmdsereraailable Chapter 8. Migrating from preious ersions of the product 95

114 Table 21. Tioli Manager for Domino commands and the corresponding IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino commands (continued) N/A wtmdstalledmail wtmdsendmail withdrawn wtmdstartengine wtmdstartengine wtmdstartmonitors wtmdstartmonitors wtmdstartserer wtmdstartserer wtmdstopengine wtmdstopengine wtmdstopmonitors wtmdstopmonitors wtmdstopserer wtmdstopserer N/A wtmdupdateaddin wtmderifymail wtmderifymail N/A wdpsaddprobe wdpsaddserer wdpsaddserer N/A wdpsclearprobes wdpscreate wdpscreate wdpsdelete wdpsdelete wdpsintegrity wdpsintegrity wdpsprobeonce wdpsprobeonce wdpsprobestatus wdpsprobestatus wdpsquerystatus wdpsquerystatus wdpsqueryserers wdpsqueryserers wdpsreboot wdpsreboot wdpsremoeserer wdpsremoeserer wdpsstart wdpsstart wdpsstartengine withdrawn wdpsstartmonitors wdpsstartmonitors wdpsstop wdpsstop wdpsstopengine withdrawn wdpsstopmonitors wdpsstopmonitors N/A wdpsqueryprobes N/A wdpsresetprobes N/A wdpsdeleteprobe 96 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

115 Chapter 9. Installing and configuring the Lotus Domino component for z/os This chapter describes the installation and configuration of Monitoring for Lotus Domino for z/os. For a list of the specific operating systems, applications, and protocols that Monitoring for Lotus Domino for z/os requires, refer to the IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino for z/os Program Directory and System requirements for IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino on page 7. Table 22 shows the goals for installation and configuration of Monitoring for Lotus Domino for z/os. Table 22. Goals for installation and configuration of Monitoring for Lotus Domino for z/os Goal Refer to 1. Reiew the architecture details to ensure that you understand all prerequisites and components. 2. Increase timeout settings for gateway transactions that require more than the default time period. Tioli enironment for Monitoring for Lotus Domino in z/os systems on page 98 Configuring timeouts for Tioli gateways on page Configure NetView on a z/os system. Configuring Tioli NetView for z/os for monitoring on page Install Monitoring for Lotus Domino for z/os. 5. Set up security permissions in the z/os system. 6. Install a task serer to be used for monitoring a z/os system. 7. Enable communications between the task serer and the z/os system. 8. Start communications between the task serer and the z/os system. Installing Monitoring for Lotus Domino for z/os on a z/os system on page 100 Configuring the z/os security enironment to accept monitoring operations on page 101 Installing the task serer for the first time on page 103 Configuring the Tioli Business Systems Manager task serer to communicate with z/os systems on page 105 Starting communication between the task serer and z/os on page

116 Tioli enironment for Monitoring for Lotus Domino in z/os systems A Tioli enironment for monitoring Lotus Domino for z/os spans multiple systems, as shown in Figure 18. Items 1 to 4 show the distributed (non-z/os) area of the Tioli management region. Items 5 and 6 show the z/os area of the Tioli management region. The list following the figure describes software requirements for each item in the figure. Figure 18. Tioli enironment for monitoring Lotus Domino for z/os 1. Tioli management region serer 2. (Optional) A computer to host a Tioli Enterprise Console eent serer for collecting eents from z/os systems Like item 4, this computer communicates directly with z/os systems. 3. Managed node with gateway 4. Managed node with endpoint This computer communicates directly with a z/os system. 5. Target and focal point z/os system You can configure this z/os system to be a focal point for Tioli communication with multiple z/os systems. 6. (Optional) Additional target z/os systems operating in a system complex and communicating through the IBM Tioli NetView for z/os focal point Item 5 is the focal point for Tioli communication with these z/os systems. The following list summarizes the required software for each element in Figure 18: 1. The Tioli serer requires IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino. 2. This optional computer communicates directly with z/os using TCP/IP and runs the eent serer of the Tioli Enterprise Console to proide eent filtering and correlation. You must install IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino on this computer. See the IBM Tioli Monitoring 98 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

117 for Messaging and Collaboration: Lotus Domino User s Guide for more information about using Tioli Enterprise Console with this product. This product does not support local eent correlation on a z/os system. The z/os system sends Tioli Enterprise Console eents directly to the Tioli Enterprise Console serer. The eent classes and eent rules are the same for z/os systems and for distributed systems. 3. This managed node runs the following software: IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Tioli gateway software to enable communication with endpoints 4. This managed node runs the following software: IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino Tioli endpoint software to enable communication with the Tioli enironment The task serer, a Tioli Business Systems Manager component that enables communication with a z/os system or with multiple z/os systems in a system complex. This communication is encrypted. A system complex, called sysplex, is a set of z/os systems communicating and cooperating with each other through multisystem hardware components and software serices to process customer workloads. The task serer communicates directly with a single z/os system using TCP/IP. Howeer, it can communicate with multiple NetView Operators on that one system to improe performance. TCP/IP to communicate with z/os 5. The z/os system runs the following software: TCP/IP IBM Tioli NetView for z/os. The purpose of IBM Tioli NetView for z/os is to sere as a focal point for Tioli communication with multiple z/os systems. A focal point system only needs to run IBM Tioli NetView for z/os. It is possible for a system to be a focal point and not run Lotus Domino software or Monitoring for Lotus Domino software. In this case, the system only enables communication between Tioli and other z/os systems that are running Lotus Domino. IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino for z/os, if you are monitoring Lotus Domino resources on this z/os system 6. Additional target z/os systems that operate and communicate through the IBM Tioli NetView for z/os focal point run the following software: Systems Network Architecture (SNA) protocol for IBM Tioli NetView communication between z/os systems TCP/IP IBM Tioli NetView for z/os IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino for z/os This configuration enables you to manage multiple instances of Domino on multiple z/os systems using the same proxy endpoint. Item 4 in the diagram represents the proxy endpoint, which is located in the distributed area of the Tioli management region. Chapter 9. Installing and configuring the Lotus Domino component for z/os 99

118 Configuring timeouts for Tioli gateways Objectie To extend the default duration for gateway transactions to match requirements of Monitoring for Lotus Domino for z/os systems. Background information Seeral of the IBM Tioli Monitoring for Messaging and Collaboration tasks might take more time to complete on the z/os systems than the default fie-minute timeout alue that is configured on Tioli gateways. You can allocate more time to these tasks so that they complete successfully. Required authorization role senior Before you begin None When you finish None Procedure Increase the default gateway timeout alue to 600 seconds or greater on all gateways that serice endpoints located on a Tioli Business Systems Manager task serer. Run the following command from the command line on any ManagedNode in the Tioli management region that has the Tioli enironment sourced: wgateway<gateway_name> set_session_timeout 600 where <gateway_name> is the name of the gateway with the timeout you want to change. For more information on the wgateway command, see the Tioli Management Framework Reference Manual. Installing Monitoring for Lotus Domino for z/os on a z/os system Objectie To plan for Monitoring for Lotus Domino for z/os installation on a z/os system. Note: You install other elements of a Monitoring for Lotus Domino for z/os system in the distributed area of the Tioli management region, as shown in Tioli enironment for Monitoring for Lotus Domino in z/os systems on page 98. Background information Install Monitoring for Lotus Domino for z/os on each z/os system that is running Lotus Domino resources that you want to manage. The z/os software distribution tape contains the Monitoring for Lotus Domino for z/os software. Distribution from the tape is performed by the System Modification Program Extended (SMP/E). Before you begin IBM Tioli NetView for z/os must be installed on each z/os system. 100 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

119 When you finish Install the task serer as described in Installing the task serer for the first time on page 103. Procedure Use the System Modification Program Extended (SMP/E) to install the product from the software distribution tape. Additional information: The IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino for z/os Program Directory comes with the software distribution tape and describes the requirements and procedures for installation. Configuring Tioli NetView for z/os for monitoring Objectie To set up Tioli NetView for z/os to facilitate communication with the z/os system from a managed node endpoint. Background information See Tioli enironment for Monitoring for Lotus Domino in z/os systems on page 98 for a diagram of the Tioli management region for z/os systems, including the managed node endpoint. The following documents proide comprehensie information on this procedure: For Version 1.3 of Tioli NetView for OS/390: Tioli NetView for OS/390, Version 1.3, Installation and Administration Guide and the chapters entitled Preparing the MVS System and Installing NetView For Version 1.4 of Tioli NetView for OS/390: Tioli NetView for OS/390, Version 1.4, Installation: Configuring Additional Components and the chapter entitled Setting Up UNIX System Serices for the NetView Program For Version 5.1 of Tioli NetView for z/os: Tioli NetView for z/os, Version 5.1, Installation: Configuring Additional Components and the chapter entitled Setting Up UNIX System Serices for the NetView Program Before you begin Tioli NetView for z/os must be installed and set up as described in the documentation for that product. When you finish Configure the security enironment as described in Configuring the z/os security enironment to accept monitoring operations. Procedure Follow the procedures in the Tioli NetView documentation to set up the NetView UNIX Command Serer. Configuring the z/os security enironment to accept monitoring operations Objectie To configure the security serer in your z/os system to accept operations for Monitoring for Lotus Domino. Chapter 9. Installing and configuring the Lotus Domino component for z/os 101

120 Background information This procedure proides examples of configuration settings for a Resource Access Control Facility (RACF) security serer. Use equialent settings to configure other security serers. The following documents are aailable on the IBM Publications Center Web site, and proide further information on RACF security serers in z/os: z/os Security Serer RACF Command Language Reference z/os Security Serer RACF Security Administrator s Guide The following list shows equialent documents for preious ersions of z/os (OS/390): For z/os (also referred to as OS/390), Version 1.1 to Version 1.3: z/os SecureWay Security Serer RACF Command Language Reference and z/os SecureWay Security Serer RACF Security Administrator s Guide For OS/390, Version 2.10: OS/390 V2R10.0 SecureWay Security Serer RACF Command Language Reference and OS/390 V2R10.0 SecureWay Security Serer RACF Security Administrator s Guide Before you begin Perform the procedure mentioned in Configuring Tioli NetView for z/os for monitoring on page 101. When you finish Start the task communication with the z/os system as described in Starting communication between the task serer and z/os on page 108. Procedure 1. Assign the user ID 0 (UID=0) for each of the NetView operators that you define on the task serer located on the managed node endpoint to communicate with the z/os system. Additional information: See Configuring the Tioli Business Systems Manager task serer to communicate with z/os systems on page 105 for information on defining operators on the task serer. You must perform this step for each NetView operator that you want to define on the task serer. 2. Define BPX.SERVER and permissions to all NetView operators by running the following series of commands in the Time Sharing Option (TSO) command serer: a. Run these commands to define BPX.SERVER: RDEFINE FACILITY BPX.SERVER UACC(NONE) SETROPTS RACLIST(FACILITY) REFRESH Note: Perform this step one time on the system. BPX.SERVER might already be actiated on your system. b. Run these commands for each NetView operator ID to permit each NetView operator ID to access BPX.SERVER: PERMIT BPX.SERVER CLASS(FACILITY) ID(<NetView_operator_ID>) ACC(read) SETROPTS RACLIST(FACILITY) REFRESH where NetView_operator_ID is the ID of one of the NetView operator that you defined on the task serer located on the managed node endpoint to communicate with the z/os system. Additional information: See Configuring the Tioli Business Systems Manager task serer to communicate with z/os systems on page 105 for 102 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

121 information on defining operators on the task serer. Perform this step for each NetView operator that you define on the task serer. Note: Run the following command to list and confirm which users are authorized for BPX.SERVER: RLIST FACILITY BPX.SERVER AUTHUSER 3. Define the SURROGAT class and permit each NetView operator to be a surrogate of all Domino user IDs. Run the following commands on the Time Sharing Option (TSO) command serer to define surrogate user ID: a. Actiate the SURROGAT class support in RACF as follows: SETROPTS CLASSACT(SURROGAT) Note: Perform this step one time on the system. The SURROGAT class might already be actiated on your system. b. Define a SURROGAT class profile for each surrogate Lotus Domino serer s user ID as follows. RDEFINE SURROGAT BPX.SRV.<domino_user_id> UACC(NONE) Additional information: Perform this step for each user ID (domino_user_id in the example) that can start a Lotus Domino serer on the system. In other words, you perform this step for the owner of each notes.ini file. c. Enable each NetView operator ID to be a surrogate of each Lotus Domino serer user ID as follows: PERMIT BPX.SRV. <domino_user_id> CLASS(SURROGAT) ID(<NetView_operator_ID>) ACCESS(READ) where NetView_operator_ID is the ID of one of the NetView operators that you want to enable to perform monitoring operations and domino_user_id is the user ID for each owner of a notes.ini file. Additional information: Perform this step for each NetView operator to specify all Domino serer user IDs. For example, if you hae two NetView operators (oper1 and oper2) and two Domino serers that run under the user IDs (domino1 and domino2 respectiely), permit oper1 to be a surrogate of domino1 and domino2, and permit oper2 to be a surrogate of domino1 and domino2. Note: To list and confirm surrogates users of a particular Domino user ID, use the following command: RLIST SURROGAT BPX.SRV.<domino_user_id> authuser d. Run the following command to refresh the SURROGAT class and apply the changes: SETROPTS RACLIST(SURROGAT) REFRESH Installing the task serer for the first time Objectie To install the task serer that sends and receies commands and monitoring data for z/os systems. Background information Use one installation of the task serer on a dedicated serer to communicate with the z/os system. Use a separate installation of the task serer for Tioli Business Systems Manager. Chapter 9. Installing and configuring the Lotus Domino component for z/os 103

122 Install the task serer in the distributed area of the Tioli management region. See Tioli enironment for Monitoring for Lotus Domino in z/os systems on page 98 for a diagram of the Tioli management region for z/os systems. The target computer can be Windows, an AIX, or a Solaris managed node that has IP connectiity with the z/os system that is running the focal point NetView. The task serer is not aailable on HP-UX platforms. The task serer is installed as part of the Tioli Business Systems Manager Eent Enablement product, which is proided on the IBM Tioli Monitoring for Business Integration, Version 5.1.1: Lotus Domino Component Software installation CD in the \TBSM\EE directory. The task serer process starts automatically when you start the operating system. You can erify or modify this behaior as follows: On Windows, access the Windows serice called Tioli BSM Task Serer in the Serices dialog box through the Windows Control Panel. On AIX and Solaris, access the ihscts daemon in the following configuration files: For AIX: /etc/rc.tbsm For Solaris: /etc/rc3.d/s95tbsm and /etc/rc0.d/k05tbsm An entry is added to the inittab file with the ID rctbsm. The Version 1.5 task serer cannot coexist with a preious ersion of the task serer or the Tioli Global Enterprise Manager topology serer. If a preious ersion of the task serer or the topology serer is installed, use the tserer remoe command to uninstall it before installing the Version 1.5 task serer. Required authorization role super Before you begin See Goals for planning and preparing for installation in Table 1 on page 5 for a checklist of actiities prior to installation. As a precautionary measure, back up the Tioli management region as described in Backing up and restoring Tioli databases on page 13. Start the Tioli desktop as described in Accessing the Tioli enironment on page 56. When you finish Install Tioli Business Systems Manager patch 1.5-BSM-0038 to update the task serer, as described in Installing Tioli patches manually on page 60. Patch 15-BSM-0043 supercedes the 15-BSM-0038 patch when that patch becomes aailable. Configure the task serer as described in Configuring the Tioli Business Systems Manager task serer to communicate with z/os systems on page 105. Start communication between the z/os system and the task serer as described in Starting communication between the task serer and z/os on page IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

123 Procedure Tioli desktop: 1. Select Install in the Desktop menu. 2. Select Install Product to display the Install Product dialog box. 3. If necessary, click OK to bypass a harmless error message about the media settings. 4. Click Select Media to display the File Browser dialog box. 5. In the Path Name text field, enter the full path to the.ind file on the CD-ROM drie. Additional information: The index (.IND) file contains details regarding the components of the product installation. Be sure to use backward slashes (\) for Windows path names instead of forward slashes (/). 6. Click Set Path to display the File Browser dialog box containing the specified media in the Files scrolling list. 7. Click Set Media & Close. 8. Select Tioli Business Systems Manager Eent Enablement 1.5 in the Select Product to Install scrolling list. 9. Select the target client from the Aailable Clients scrolling list. 10. Click the left arrow to moe the selected client to the Clients to Install On scrolling list. 11. If necessary, select the clients on which you do not want to install the task serer from the Clients to Install On list and click the right arrow to moe them to the Aailable Clients list. 12. Click Install & Close to display the Product Install window and a list of pending installation actions. 13. Click Continue Install to begin the installation process. Additional Information: The Product Install window displays the progress of the installation. View the messages in the task output dialog box to determine whether the product installation was successful. See About the log files for installation errors on page 115 for information on problem determination. 14. Click Close to close the Product Install window. 15. As a precautionary measure, back up the Tioli management region databases as described in Backing up and restoring Tioli databases on page 13. Use a unique name for the new backup files. Configuring the Tioli Business Systems Manager task serer to communicate with z/os systems Objectie To enable the Tioli Business Systems Manager task serer to communicate with the z/os NetView system with commands that you enter on the Tioli managed node that hosts the task serer. Background information Use one installation of the task serer for communication with the z/os system. Note: Use a separate installation of the task serer for Tioli Business Systems Manager Eent Enablement. Chapter 9. Installing and configuring the Lotus Domino component for z/os 105

124 The following actions included in this procedure enable the task serer to communicate with the z/os system: Gie a user account the required priileges and rights in Windows (Windows only) A user account must hae seeral priileges and rights that Windows systems require to enable Tioli operations. Change TCP/IP port numbers, if other applications use these port numbers: If other applications use the default TCP/IP ports for the task serer (4020 and 4042) you must assign new, unique port numbers. Enable the task serer to reference multiple operator IDs on the z/os system The task serer achiees multithreading of communications by referencing multiple operator IDs when it sends hostcmd commands to IBM Tioli NetView for z/os. The task serer alternates between the aailable operator IDs, inoking them concurrently to improe performance and response time. See the Tioli Business Systems Manager Administration Guide, Version 1.5 for more information on this set of commands. Required authorization role This procedure requires the following authorizations: On UNIX: root On Windows: Administrator Within Tioli: super Before you begin Install the task serer as described in Installing the task serer for the first time on page 103. When you finish None Procedure 1. (Windows only) Gie a user account the required priileges and rights in Windows by doing the following: a. Log on to the computer that runs the task serer using a user account with Administrator priileges. b. Select Programs in the Start menu of the Windows taskbar. c. Select User Manager or User Manager for Domains for NT serers in the Administratie Tools (Common) menu to display the User Manager window. d. Select the user you want to modify in the Username list. e. Add the user to the Administrators group as follows: 1) Double-click the user name to access the Users Properties window. 2) Click Groups to access the Group Memberships dialog box. 3) Select Administrators in the Not member of list. 4) Click Add to moe Administrators to the Member of list. 5) Click OK to return the Users Properties window. 6) Click OK to sae your changes and to return to the User Manager window. f. Select User Rights in the Policies menu to access the User Rights Policy dialog box. g. Click Show Adanced User Rights. 106 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

125 h. Assign the Act as part of the operating system user right to the user as follows: 1) Select Act as part of the operating system in the Right drop-down list. 2) Click Add to access the Add Users and Groups dialog box. 3) Click Show Users. 4) Select the user in the Names list. 5) Click Add. 6) Click OK to return to the User Rights Policy dialog box. i. Repeat Step 1h to assign the Replace a process leel token user right to the user. In Step 1h1 you select Replace a process leel token instead of Act as part of the operating system. j. Repeat Step 1h to assign the Log on as a serice user right to the user. In Step 1h1 you select Log on as a serice instead of Act as part of the operating system. k. Click OK to sae the user rights assignments. l. Click Close to close the User Manager window. m. Log off your user account to apply these changes by doing the following: 1) Click Start in the Windows taskbar and select Shut Down. 2) Select Close all programs and log on as a different user?. 3) Click Yes. Additional Information: When you log in again, your user account has the required authorizations. 2. (Optional) Change TCP/IP port numbers by doing the following if other applications use these port numbers: a. Open the serices text file in the following directory path: On AIX or Solaris: /etc On Windows: %SystemRoot%\system32\driers\etc b. Find the following entries and change the default port settings (4020 or 4042) to unique port numbers: tserer_tbsm 4020/tcp #serer z/os port tserer_ts 4042/tcp #task serer port Additional information: If you reassign the default z/os port number (4020), you must also customize the IBM Tioli NetView for z/os Port keyword in the DUIFPMEM file. For more information about the Port keyword, see IBM Tioli NetView for OS/390 Administration Reference. 3. Identify one or more z/os NetView operators to the task serer: a. Access the Tioli enironment as described in Accessing the Tioli enironment on page 56. b. Access the following bin directory on the task serer in the path defined by the Tioli BINDIR enironment ariable: On UNIX: $BINDIR/TDS/EentSerice/bin On Windows: %BINDIR%/TDS/EentSerice/bin c. (Windows only) Type bash to access the bash command-line interface. d. Enter the following command to enable the task serer to reference the IBM Tioli NetView for z/os operator ID and password:./hostcmdoper -u operator_id -p password Chapter 9. Installing and configuring the Lotus Domino component for z/os 107

126 where operator_id and password correspond to a NetView operator on the z/os system. The hostcmdoper command encrypts the password and stores it on disk on the task serer. See the Tioli Business Systems Manager Administration Guide, Version 1.5 for more information on this command. e. Repeat 3d for each operator ID that you want to reference. f. Run the following command to erify success of Step 3d:./hostcmdoper -s Additional information: Refer to the Tioli Business Systems Manager Administration Guide, Version 1.5 for more information on this command. g. (Optional) Run the following command to delete a reference to NetView operator IDs. This command deletes the first operator ID reference that you defined in Step 3d:./hostcmdoper -d operator_id 4. If necessary, start the task serer as follows to enable communication with NetView in the z/os system. Additional information: The task serer process is configured to run by default, but might be stopped manually. The process must be running to complete this procedure. a. Access the bin directory for the task serer. For AIX and Solaris: $BINDIR/TDS/EentSerice/bin For Windows: %BINDIR%\TDS\EentSerice\bin b. Enter the following command: tserer start Starting communication between the task serer and z/os Objectie To initiate and erify the communication between the task serer and IBM Tioli NetView for z/os on the z/os system. Background information The task serer starts automatically as a process when you start the operating system. This procedure tells how to establish communication between the task serer and IBM Tioli NetView for z/os on the z/os system. Examples in this procedure describe how to set up authorization and access in a Resource Access Control Facility (RACF) security system. The Resource Access Control Facility program proides access control on the OS/390 Security Serer and is also aailable as a separate program for the Multiple Virtual Storage (MVS) enironment within a z/os system. Monitoring for Lotus Domino for z/os has no RACF options, but you can enable Monitoring for Lotus Domino for z/os programs to access a protected resource. See the documentation for Resource Access Control Facility for instructions on enabling access to protected resources. If you use IBM Tioli NetView security features to control authorization and access, see IBM Tioli NetView for z/os Security Reference for more information. Required authorization role This procedure requires the following authorizations: On UNIX: root On Windows: Administrator Within the Tioli enironment: super 108 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

127 Before you begin Perform the procedure Configuring the Tioli Business Systems Manager task serer to communicate with z/os systems on page 105. The task serer must be running when you perform this procedure. The task serer is configured to run automatically. To erify that it is running, check the status of one of the following processes: On Windows, the task serer starts automatically as a Windows serice called Tioli BSM Task Serer. To reiew or alter these settings, access the Serices dialog box through the Windows Control Panel. On AIX and Solaris, the task serer starts automatically as the daemon ihscts. To reiew or alter these settings, see the following configuration files: For AIX: /etc/rc.tbsm For Solaris: /etc/rc3.d/s95tbsm and /etc/rc0.d/k05tbsm When you finish None Procedure 1. In the distributed area of the Tioli management region, start the task serer if it is not already running. Additional information: The task serer is configured to run automatically. Normally you do not need to start it manually. The procedure for configuring the task serer describes how to start the task serer manually in Step 4 on page 108. If you want to erify that the task serer is running, check the status of the task serer process, which is mentioned in the Before you begin section. 2. In the z/os system, confirm that the IBM Tioli NetView for z/os CNMTAMEL task is actie, as follows: a. Access the NetView Command Facility console (called NCCF). b. Type the list cnmtamel command. c. If the command does not generate a result, type the following command to start the task: start task=cnmtamel Additional information: See IBM Tioli NetView for z/os documentation for more information. 3. Run the following command on the operator console of IBM Tioli NetView for z/os: netcon action=start ip=hostname where hostname is the IP address or the fully qualified host name of the computer on which the task serer runs. Additional information: The following example establishes a TCP/IP connection with a task serer located on a computer whose IP address is : netcon action=start ip= This session enables TCP/IP communication with the task serer and must remain actie. Wheneer you stop and start the task serer, you must enter the NETCONV command again. Chapter 9. Installing and configuring the Lotus Domino component for z/os 109

128 4. Run the following command on the IBM Tioli NetView for z/os operator console to start the NetView UNIX Command Serer: start unixser=* Additional information: The start unixser=* command allows NetView to route commands to the NetView UNIX Command Serer. The following command stops the NetView UNIX Command Serer: stop unixser=* 5. Verify that communication between IBM Tioli NetView for z/os and MVS is successful by doing the following: a. Access the Tioli enironment as described in Accessing the Tioli enironment on page 56. b. Access the following bin directory on the task serer in the path defined by the Tioli BINDIR enironment ariable: On UNIX: $BINDIR/TDS/EentSerice/bin On Windows: %BINDIR%/TDS/EentSerice/bin c. (Windows only) Type bash to access the bash command-line interface. d. Run the following command on the task serer:./hostcmd "ms d a,l" -h hostname where hostname is the IP address or the fully qualified host name of the z/os system on which the command is to be executed. The hostcmd command displays the list of all actie tasks running on the z/os system. See the Tioli Business Systems Manager Administration Guide, Version 1.5 for more information on the hostcmd command. e. Verify that the task serer is communicating correctly with the NetView Command Serer by entering the following command on the task serer workstation from a bash command line interface:./hostcmd "netasis pipe unix pwd corrwait 30 console" -h hostname where hostname is the IP address or the fully qualified host name of the z/os system on which the command is to be executed. The hostcmd command displays the list of all actie tasks running on the z/os system. Note: NetView communicates with UNIX System Serices through the NetView UNIX Command Serer. This serer must be running to enable communication. Additional information: Successful output consists of a display of the home directory of the NetView operator ID that was used to run the command, such as in this example: /u/oper1. If erification fails, ensure that the following conditions are true before you attempt to erify communication again: Proper host name authorization exists. See the Problems on z/os systems section of the table in Problems and workarounds on page 116. Other authorization and security setup is correct. If you use a Resource Access Control Facility (RACF) security system, check the authorizations and setup. NetView UNIX Command Serer is started, as described in Step IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

129 Appendix A. Problem determination This appendix describes how to determine the source of problems and how to correct those problems. The following table proides an oeriew of the topics and procedures coered in this appendix. Table 23. Oeriew of problem determination topics and procedures Topic or procedure Where to find information Use indicators and tools in the installer to identify and Troubleshooting installer problems on page 111 resole problems. Work with the error message log that the Tioli About the log files for installation errors on page 115 Management Framework Endpoint Setup wizard generates when installing the agent. Determine the source of a common problem and resole it. Determine the source of connectiity errors in a Messaging and Collaboration endpoint and resole the errors. To clean up the endpoint process and remoe endpoint files from the Tioli enironment. Note: Use this procedure to resole connectiity problems. Remoe the endpoint using this procedure and then reinstall it. A completely new installation of the agent might resole the connectiity problem. Problems and workarounds on page 116 Testing endpoint connectiity on page 118 Cleaning up and remoing the endpoint on page 119 Troubleshooting installer problems Objectie: To resole or work around common problems that can arise during a Typical or Custom installation. Background information: This procedure describes actions you can take in the Step List panel of the installer. The Step List proides detailed information about the progress of installation. This panel is displayed near the end of the installation process, when the installer is processing all of your configuration settings. 111

130 Figure 19. Step List installer panel sample The Step List panel contains a list of the installation steps. You can see information such as the following on any step you select: The software that you are installing and configuring The installation status of the current step A short description of the step Error messages and error resolution options in case of a warning or step failure. Table 24 shows the status icons and buttons in the Detail dialog box: Table 24. Status icons and buttons for the Step List panel of the installer Name Icon Value Status icons in the Step List Pending None The step was not run. Passed The step completed successfully. Passed_Reboot Passed_Warning The step completed successfully and you must reboot the system. This status causes the installer to prompt you to restart the computer. The step completed with one or more warnings. For example, the installer might warn you to restart computers on which you installed the Web Health Console. Otherwise, the console is not actiated. The installer might also list warnings from the installation logs of the Tioli Management Framework. You can consult the documentation that comes on the installation CDs for Tioli Management Framework for information on this type of warning. Also see Table 25 on page 116. for information on error logs. Failed The step failed. This procedure describes how to analyze and handle failed steps. Deferred The step was postponed. This icon is displayed after you defer a step in the Detail dialog box, as described near the end of the installation procedure. See the description of the Defer button in this table for more information. 112 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide

131 Table 24. Status icons and buttons for the Step List panel of the installer (continued) Name Icon Value Breakpoint The step was placed in breakpoint mode. The installer stops processing steps at the breakpoint. You can check progress and change settings, if necessary. Buttons Defer Postpones the step to a later time. Before you use this button consider the following points: Do not defer a step that other steps depend on. For example, do not defer creation of a managed node when you plan to use the installer to create an endpoint that references that managed node. Endpoints must hae a managed node assignment at the time they are created. You cannot undo a deferral. When you defer a step, you must perform Step 5 to run it. When you run deferred steps, the status of all other steps in the list must be Passed. You must run all deferred steps in sequence, as they are listed in the Step List. Toggle Breakpoint Reboot OK Change Actiate or Deactiate the breakpoint. If you actiate the breakpoint, the automatic installation process is interrupted when it reaches that step and you are asked for input. If you want the installer to pause after specific steps are complete, actiate a breakpoint on the subsequent step. For example, you can set a breakpoint to enable installation of proxy endpoints as described in Manually creating a Windows proxy endpoint on page 50. Reboots the system when required. Returns to the preious dialog box. Enables you to make the following types of change: Change the user ID or password. Change the destination directory for the creation of a managed node or endpoint. Required authorization: On UNIX, the user who installs the product must hae root priileges. On Windows, the user who installs the product must hae membership in the Administrators group. Before you begin: Use the installer to start one of the following types of installation: Typical installation as described in Chapter 4, Performing a Typical installation on page 25. Custom installation as described in Chapter 5, Performing a Custom installation on page 35. While you work with the installer, you can use the options described in this procedure to work around and resole problems. When you finish: Complete the actiities described in Chapter 7, Completing the installation on page 75. Procedure: 1. (Optional) If you want to cancel the installation while the Step List is running, perform the following steps: a. Click Stop 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. Appendix A. Problem determination 113

132 2. (Optional) Double-click any item in the Step list to see details and to set processing instructions for that step in the Details dialog box. Figure 20. Detail dialog box of the Step List panel 3. Respond to the Step List error, eent, or action prompts that might be displayed. Error message logs: Consult the following resources in case of installation errors The error log in the following directory: tioli/depot/deployengine/logs/deploy.log. Customer Support uses this file to determine the source of problems. See Appendix A, Problem determination on page 111 for more information on problem determination. See the Tioli Enterprise Installation Guide that comes with Tioli Management Framework, Version 3.7.1, for complete troubleshooting analysis. Warnings: The step might complete with one or more warnings. For example, the installer might warn you to restart computers on which you installed the Web Health Console. Otherwise, the console is not actiated. The installer might also list warnings from the installation logs of the Tioli Management Framework. You can consult the documentation that comes on the installation CDs for Tioli Management Framework for information on this type of warning. Also see Table 25 on page 116. Change alue operations: Perform the following steps any time you become aware of a user name or password error: a. Double-click the step in which an error occurs to display the Detail dialog box. b. Click Change to display the Change Value dialog box. c. Enter the new alue in the Change Value dialog box for user ID, password, and destination directory, as needed. d. Click OK. 4. If a Change Value operation fails, perform the following steps: a. See Table 24 on page 112 for a description of the proper use of the Defer option. b. Click Defer in the Step Detail dialog box. c. Allow the installer to finish processing the Step List. 5. If you hae made changes that will permit successful execution of deferred steps, execute steps that you deferred. 114 IBM Tioli Monitoring for Messaging and Collaboration: Installation and Setup Guide