Tivoli Enterprise Installation Release Notes Version 3.7

(1)

Tivoli Enterprise™ Installation Release Notes

Version 3.7

July 21, 2000

(2)

Tivoli Enterprise Installation Release Notes

Copyright Notice

Copyright © 2000 IBM Corp., including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corp. IBM Corp. grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corp. copyright notice. No other rights under copyright are granted without prior written permission of IBM Corp. The document is not intended for production and is furnished “as is” without warranty of any kind.All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: IBM, Tivoli, AIX, AS/400, DB2, IBMLink, OS/2, OS/390, OS/400, RS/6000, Tivoli Enterprise, TME.

In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.

Microsoft, Windows, Windows NT, and Visual C++ are trademarks trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Motif and UNIX are registered trademarks of The Open Group in the United States and other countries.

Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System’s or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

(3)

Chapter 1—Release Notes

Contacting Customer Support... 1-2 New Features in Version 3.7... 1-3 New Installation Features of Tivoli Management Framework ... 1-3 New Features of Tivoli Software Installation Service ... 1-4 System Requirements... 1-7 System Requirements for Tivoli Management Framework ... 1-9 TMR Servers, Managed Nodes, and Gateways ... 1-9 Tivoli Endpoints ... 1-15 System Requirements for Tivoli Software Installation Service ... 1-17 Disk Space Requirements ... 1-17 Disk Space Requirements for Tivoli Management Framework ... 1-17 TMR Servers, Managed Nodes, and Gateways ... 1-18 Tivoli Endpoints ... 1-19 Disk Space Requirements for Tivoli Software Installation Service... 1-19 RDBMS Interface Module (RIM) Requirements and Considerations... 1-21 Supported RDBMS Servers... 1-22 DB2 ... 1-23 Requirements for DB2 ... 1-23 Installing and Configuring DB2 ... 1-24 Informix... 1-26 Requirements for Informix ... 1-26 Installing and Configuring Informix... 1-28 Microsoft SQL Server ... 1-28 Requirements for Microsoft SQL Server... 1-28 Installing and Configuring Microsoft SQL Server ... 1-29 Oracle ... 1-29 Requirements for Oracle... 1-29 Installing and Configuring Oracle ... 1-30

(4)

Sybase ... 1-31 Requirements for Sybase ... 1-31 Installing and Configuring Sybase ... 1-31 Installing and Configuring the RDBMS ... 1-32 Troubleshooting the RIM Configuration ... 1-32 Installation and Product Notes... 1-34 Tivoli Management Framework Installation Notes ... 1-34 General Installation Notes ... 1-35 Upgrading Tivoli Management Framework on Solaris Systems

That Share Files with NFS ... 1-44 Upgrading Tivoli Management Framework When Tivoli Security Management Is Installed... 1-45 Creating Version 3.6 Managed Nodes in a Version 3.7 TMR ... 1-46 Tivoli Software Installation Service Product Notes... 1-47 Interpreter Types ... 1-50 Patches Included in This Release... 1-53 Tivoli Management Framework Patches ... 1-54 Tivoli Software Installation Service Patches ... 1-54 Defects Fixed in Version 3.7 ... 1-55 Tivoli Management Framework ... 1-55 Tivoli Software Installation Service... 1-58 Known Product Defects, Limitations, and Workarounds ... 1-60 Documentation ... 1-60 Endpoint Installation ... 1-63 NetWare Gateway Installation ... 1-68 Tivoli Management Framework Installation... 1-69 Tivoli Software Installation Service... 1-71 General ... 1-72 Client ... 1-72 Console ... 1-74 Depot ... 1-76 Command Line ... 1-77

(5)

Response Files ... 1-77 Installing Specific Products ... 1-78

Chapter 2—Internationalization Notes

Enabling Language Support ... 2-1 System Requirements for Asian Language Versions... 2-2 Japanese... 2-2 TMR Servers, Managed Nodes, and Gateways ... 2-2 Endpoints ... 2-3 Requirements for NEC PC98 Systems ... 2-3 Korean ... 2-5 TMR Servers, Managed Nodes, and Gateways ... 2-5 Endpoints ... 2-5 Simplified Chinese ... 2-6 TMR Servers, Managed Nodes, and Gateways ... 2-6 Endpoints ... 2-6 Traditional Chinese ... 2-6 TMR Servers, Managed Nodes, and Gateways ... 2-6 Endpoints ... 2-7 Cantonese Chinese ... 2-7 TMR Servers, Managed Nodes, and Gateways ... 2-7 Endpoints ... 2-7 Internationalization Defects, Limitations, and Workarounds ... 2-7 Tivoli Management Framework Installation... 2-8 Tivoli Software Installation Service... 2-10

(6)

(7)

1

Release Notes

These release notes provide important information about installing Tivoli^®Management Framework, Version 3.7, and using and installing Tivoli Software Installation Service (SIS), Version 3.7. Release notes are the most current information for the product.

Note: Before you install any Tivoli Enterprise application, read the release notes and documentation for that product. Having the necessary information will expedite the installations performed in your Tivoli environment.

These release notes cover the following:

■ The system requirements of Tivoli Management Framework and Tivoli Software Installation Service

■ The installation of Tivoli Management Framework to create Tivoli Management Region (TMR) servers, managed nodes, endpoints, and RDBMS Interface Module (RIM) objects

■ The use of Tivoli Management Framework installation mechanisms to install Tivoli Enterprise^™ applications

■ The installation and use of Tivoli Software Installation Service

■ Defects associated with Tivoli Software Installation Service and Tivoli Management Framework installation mechanisms

For Tivoli Management Framework information not related to installation, see the Tivoli Management Framework Release Notes.

(8)

Contacting Customer Support

These release notes include the following topics:

■ Contacting Customer Support

■ New Features in Version 3.7

■ System Requirements

■ Disk Space Requirements

■ RDBMS Interface Module (RIM) Requirements and Considerations

■ Installation and Product Notes

■ Patches Included in This Release

■ Defects Fixed in Version 3.7

■ Known Product Defects, Limitations, and Workarounds

■ Internationalization Issues, including the following:

• Enabling Language Support

• System Requirements for Asian Language Versions

• Internationalization Defects, Limitations, and Workarounds Both Tivoli and TME^®10 are used in our sales, marketing, and product literature. These terms are interchangeable. References to TME 10 will be removed in future product releases.

In addition, a Tivoli endpoint is sometimes called a Tivoli management agent (TMA), lcfd, Tivoli Lightweight Client, or endpoint daemon. All these terms refer to the Tivoli process running on the endpoint.

Contacting Customer Support

If you need support for this or any Tivoli product, contact Tivoli Customer Support in one of the following ways:

■ Submit a problem management record (PMR) electronically from our Web site at http://www.tivoli.com/support/reporting/. For information about obtaining support through the Tivoli Customer Support Web site, go to http://www.tivoli.com/support/getting/.

(9)

New Features in Version 3.7

■ Submit a PMR electronically through the IBMLink™ system. For information about IBMLink registration and access, refer to the IBM^® Web page at http://www.ibmlink.ibm.com.

■ Send e-mail to [email protected].

■ Customers in the U.S. can call 1-800-TIVOLI8 (1-800-848-6548).

■ Customers outside the U.S. should refer to the Tivoli Customer Support Web site at

http://www.tivoli.com/support/locations.html for customer support telephone numbers.

When you contact Tivoli Customer Support, be prepared to provide the customer number for your company so that support personnel can assist you more readily.

We are very interested in hearing from you about your experience with Tivoli products and documentation. We welcome your suggestions for improvements. If you have comments or suggestions about this documentation, please send e-mail to [email protected].

New Features in Version 3.7

The following sections list the new installation capabilities of Tivoli Management Framework and the new features of Tivoli Software Installation Service.

New Installation Features of Tivoli Management Framework

This section describes new features of Tivoli Management Framework that relate to installation. For information about new features not related to installation, refer to the Tivoli Management Framework Release Notes.

This release of Tivoli Management Framework has the following new installation features and capabilities:

■ APAR-IX82385: You can install Tivoli Desktop for Windows in silent mode into the Program Files directory on Windows^® and

(10)

Windows NT^®systems. To use this new installation, perform the following steps.

Attention: Exercise care when using the Windows NT Registry Editor. If a mistake is made in these steps, the system might be rendered unusable.

1. Enter the setup –R command to generate a

%WINDIR%\SETUP.ISS file. By default, %WINDIR%

is C:\WINNT on Windows NT and C:\WINDOWS on Windows 95 and Windows 98.

2. Edit the SETUP.ISS file by replacing the line:

szDir=C:\Program Files\Tivoli\desktop

with the following line:

szDir=" "

3. In the Windows registry, go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

Windows\CurrentVersion. Change the value of the ProgramFilesDir registry value to the location where you want to place the files for Tivoli Desktop for Windows, for example c:\My Tivoli.

Note: If you are installing on a Windows NT 3.5.1 system, you must create the CurrentVersion registry key.

4. Run setup –s –f1%WINDIR%\SETUP.ISS to install the desktop to the location you specified in step 3.

Note: This command will not work if you add a space between the –f1 argument and the path.

New Features of Tivoli Software Installation Service

This release of Tivoli Software Installation Service has the following new features and capabilities:

■ Tivoli Software Installation Service now uses a client/server architecture. The server is called the depot. The client provides both a command line interface and a graphical user interface (GUI), called the console. This architecture changes how Tivoli

(11)

Software Installation Service is installed and used. The new implementation provides the following benefits:

• Enhanced speed for installing over a wide area network (WAN) or other slow network connections

• Multiple Tivoli Software Installation Service clients that connect to a single depot, which allows multiple

administrators to share an install repository

• Improved performance and lower resource use

■ Tivoli Software Installation Service can now install Tivoli Enterprise software to endpoints.

■ The wsis command no longer displays installation and login passwords when you enter them in response to a prompt.

■ The endpoint installation images no longer reside in the install repository. Instead, they are read from the managed node on which the depot runs. Upgrading Tivoli Management Framework on that managed node updates the installation images for subsequent endpoint installations by Tivoli Software Installation Service.

■ The nonshared type of install repository is no longer supported.

■ You cannot share an install repository within a TMR. Sharing is now supported only between depots in different TMRs.

■ Usability enhancements have been made to the Tivoli Software Installation Service console. The most noticeable change is that the Tivoli Software Installation Service main dialog and Install Details dialog have been combined into a single Tivoli Software

Installation Service window (also known as the installation worksheet), and the functionality formerly accessed using buttons on those dialogs are now accessed through menus on the new window.

■ The console and command line can now be run from a different host system than the host that manages the install repository and performs installations.

■ You can now remove products from the install repository using either the wimport command or the console.

(12)

■ You can now remove computer systems from the install repository using the console, if they have no managed resources installed on them.

■ The preference settings that were formerly located in the SIS.INI file are now stored as object attributes of the SisDepot object.

Instead of editing this file, you now use the SIS Preferences dialog or the wsisprefs command to view or change settings.

■ The Tivoli Software Installation Service logging has been enhanced, including the following new capabilities:

• You can access the logs using a browser that organizes the logs, rather than searching for them in the install repository directories.

• You can access the depot logs from the computer system running the client without logging in to the computer system running the depot.

• You can automatically archive and delete depot log files.

■ In Tivoli Software Installation Service, Version 3.6, you were prompted to set default values of installation options immediately after importing the product into the install repository. There is no prompt now. You must set the values the first time you add the product to the installation worksheet or use the new wsisdefaults command.

■ In previous releases of Tivoli Software Installation Service, the default values for product installation options could be either of the following:

Global Applying to installations from all TMRs sharing the install repository.

Local Applying only to installations from a specific TMR.

The default values are now always local. You can still override the default for a specific system.

(13)

System Requirements

■ In previous releases of Tivoli Software Installation Service, installation prerequisites applied to all TMRs sharing an install repository. Prerequisites now apply only to the TMR in which they were defined.

System Requirements

The following sections describe the operating system software and hardware requirements for the following:

■ Tivoli Management Framework

• TMR servers, managed nodes, and gateways

• Endpoints

■ Tivoli Software Installation Service

They also describe the interpreter type values that are displayed by and provided as input to these two products.

For information about system requirements for Asian languages, refer to

“System Requirements for Asian Language Versions” on page 2-2.

Note: Tivoli software has specific software and hardware

prerequisites that must be met before it can be installed and deemed fully functional. These include operating systems, hardware platforms, relational and object database management systems, e-mail and Web servers, and support libraries. The prerequisites listed in these release notes are the recommended environment for Tivoli products at the time of publication.

Tivoli software is supported only when used with prerequisites that are officially supported by the third-party vendor.

Many vendors unilaterally withdraw support for their products on a regular basis. Tivoli reserves the right to unilaterally withdraw support for its software based on the availability of support from a vendor for any prerequisite software. Please contact the vendor of any prerequisite software if you have questions about its current support.

This section contains information about the supported operating system versions and required patches (if any) for each supported hardware architecture. Tivoli Systems does not distribute or maintain operating

(14)

System Requirements

system patches from hardware vendors. Contact your hardware vendor for information about obtaining and installing operating system patches.

The following table includes commands used to determine which operating system patches are installed:

If you are not sure how to contact your hardware vendor, contact your Tivoli support provider for details on the recommended procedure.

Note: Tivoli Enterprise products that support Microsoft^®

Windows 95, Windows 98, Windows NT, Windows 2000, IBM OS/2, and Novell NetWare must be installed on a IBM-compatible hardware.

Operating

System Example

AIX^® ^{instfix -a}

HP-UX ^swlist

OS/2^® To determine the operating system level, use the syslevel command.

To determine the level of TCP/IP, use the inetver command.

OS/400^® To determine the operating system level, use the dspsfwrsc command.

To determine what patches are installed, use the dspptf command.

Sun Solaris To determine if a patch is installed, look for a directory with that name in /var/sadm/patch.

Windows NT Open Windows NT Explorer and click About Windows NT in the Help menu.

(15)

System Requirements

System Requirements for Tivoli Management Framework

TMR Servers, Managed Nodes, and Gateways

Tivoli Management Framework is supported on the operating system versions listed in the following sections. For each operating system, restrictions and required patches are required. Some operating systems are supported only as a gateway. This is noted where applicable.

AIX on IBM RS/6000

^®

and PowerPC Systems

Tivoli Management Framework is supported on AIX 4.3, 4.3.1, or 4.3.2.

The following additional requirements and prerequisites are required:

■ Motif^® Version 1.2

■ The libtermcap.a library from the AIX 3.2 compatibility file set, bos.compat.termcap, must be installed.

Note: Tivoli Management Framework will operate on all AIX 4.x systems without the libtermcap library.

However, you will not be able to open or use an xterm window.

■ For AIX 4.3.x, the file sets listed in the following table must be applied.

bos.64bit.4.3.1.0.bff bos.acct.4.3.1.0.bff bos.acct.4.3.1.1.bff bos.adt.base.4.3.1.0.bff bos.adt.include.4.3.1.0.bff bos.adt.include.4.3.2.7.bff bos.adt.prof.4.3.1.0.bff bos.adt.prof.4.3.1.5.bff bos.adt.sccs.4.3.1.0.bff bos.atm.atmle.4.3.2.4.bff bos.compat.NetInstl.4.3.1.0.bff bos.diag.com.4.3.1.0.bff bos.diag.rte.4.3.1.0.bff bos.diag.util.4.3.1.0.bff

(16)

System Requirements

bos.INed.4.3.1.0.bff bos.mh.4.3.1.0.bff

bos.mh.4.3.1.3.bff bos.mp.4.3.1.0.bff

bos.mp.4.3.1.1.bff bos.mp.4.3.2.14.bff

bos.msg.en_US.rte.4.3.1.0.bff bos.net.nfs.cachefs.4.3.2.6.bff bos.net.nis.client.4.3.1.0.bff bos.net.nis.client.4.3.1.4.bff bos.net.nis.server.4.3.1.0.bff bos.net.nis.server.4.3.1.2.bff bos.net.tcp.client.4.3.1.0.bff bos.net.tcp.client.4.3.1.2.bff bos.net.tcp.client.4.3.2.10.bff bos.net.tcp.server.4.3.1.0.bff bos.net.tcp.server.4.3.1.1.bff bos.rte.boot.4.3.2.3.bff bos.rte.control.4.3.1.0.bff bos.rte.control.4.3.1.3.bff bos.rte.cron.4.3.1.0.bff bos.rte.cron.4.3.1.1.bff bos.rte.diag.4.3.1.0.bff bos.rte.install.4.3.0.4.bff bos.rte.libc.4.3.1.0.bff bos.rte.libc.4.3.1.5.bff bos.rte.libpthreads.4.3.1.0.bff bos.rte.net.4.3.1.0.bff

bos.rte.security.4.3.1.0.bff devices.pci.00100300.diag.4.3.1.0.bff devices.pci.14107c00.com.4.3.2.4.bff devices.ssa.network_agent.rte.4.3.1.0.bff ifor_ls.base.cli.4.3.2.0.bff ifor_ls.base.cli.4.3.2.1.bff

ipx.rte.4.2.1.1.bff Java.adt.docs.01.01.0004.0000.bff Java.adt.src.1.1.4.2.bff Java.rte.bin.1.1.4.2.bff

Java.rte.classes.1.1.4.2.bff Java.rte.Dt.1.1.4.1.bff

Java.rte.lib.1.1.4.2.bff Java.samples.demos.01.01.0004.0000.bff

(17)

System Requirements

AIX 4.2.1 is no longer supported (refer to RFA 998-073). However, to assist you in migrating to a supported version of AIX, the following table lists the file sets that must be applied for that version.

Java.samples.demos.1.1.4.2.bff netware.server.4.1.4.0.bff netware.server.4.1.4.7.bff perfagent.server.2.2.32.0.bff perfagent.server.2.2.32.2.bff perfagent.tools.2.2.32.0.bff perfmgr.common.2.2.1.0.bff perfmgr.common.2.2.1.2.bff perfmgr.local.2.2.1.0.bff perfmgr.local.2.2.1.4.bff perfmgr.network.2.2.1.0.bff perfmgr.network.2.2.1.4.bff

PEX_PHIGS.graPHIGS.adt.gks.4.3.1.0.bff PEX_PHIGS.graPHIGS.rte.plot.4.3.1.0.bff PEX_PHIGS.graPHIGS.rte.plot.4.3.1.1.bff X11.apps.aixterm.4.3.1.0.bff

X11.apps.pm.4.3.1.0.bff X11.apps.pm.4.3.1.1.bff X11.apps.xterm.4.3.1.0.bff X11.base.lib.4.3.1.0.bff X11.Dt.adt.4.3.1.0.bff

bos.acct.4.2.1.6.bff bos.adt.base.4.2.1.4.bff bos.adt.include.4.2.1.22.bff bos.adt.prof.4.2.1.16.bff bos.adt.sccs.4.2.0.1.bff bos.adt.syscalls.4.2.1.5.bff bos.compat.NetInstl.4.2.1.1.bff bos.diag.util.4.2.1.5.bff bos.ifor_ls.client.4.2.1.1.bff bos.INed.4.2.0.1.bff

bos.mh.4.2.0.2.bff bos.mp.4.2.1.28.bff

(18)

System Requirements

bos.net.nis.client.4.2.1.4.bff bos.net.nis.server.4.2.1.4.bff bos.net.tcp.client.4.2.1.26.bff bos.net.tcp.server.4.2.1.10.bff bos.rte.control.4.2.1.10.bff bos.rte.cron.4.2.1.3.bff bos.rte.install.4.2.1.8.bff bos.rte.libc.4.2.1.20.bff bos.rte.serv_aid.4.2.1.7.bff bos.rte.shell.4.2.1.10.bff bos.rte.tty.4.2.1.18.bff bos.sysmgt.serv_aid.4.2.1.9.bff bos.sysmgt.trace.4.2.1.3.bff bos.txt.tfs.4.2.1.2.bff

bos.txt.tfs.data.4.2.0.2.bff bos.up.4.2.1.28.bff

devices.common.IBM.atm.rte.4.2.1.16.bff devices.common.IBM.ethernet.rte.4.2.1.4.bff devices.common.IBM.fcs.rte.4.2.1.6 devices.common.IBM.fddi.rte.4.2.1.3.bff devices.mca.8f97.com.4.2.1.3.bff devices.mca.8f97.diag.4.2.1.6.bff devices.mca.8f97.rte.4.2.1.2.bff devices.mca.8fc8.com.4.2.1.4.bff devices.pci.14104500.diag.4.2.1.2.bff devices.pci.14104500.rte.4.2.1.2.bff devices.ssa.disk.rte.4.2.1.3.bff devices.ssa.IBM_raid.rte.4.2.1.3.bff devices.ssa.IBM_raid.vsm.4.2.1.1.bff devices.ssa.network_agent.rte.4.2.1.3.bff devices.ssa.tm.rte.4.2.1.1.bff ipx.rte.4.2.1.1.bff

netware.server.4.1.4.0.bff netware.server.4.1.4.7.bff perfagent.server.2.2.1.9.bff perfagent.tools.2.2.1.4.bff perfmgr.common.2.2.1.0.bff perfmgr.common.2.2.1.2.bff perfmgr.local.2.2.1.0.bff perfmgr.local.2.2.1.4.bff perfmgr.network.2.2.1.0.bff perfmgr.network.2.2.1.4.bff

(19)

System Requirements

HP-UX on HP 9000 Systems

Tivoli Management Framework is supported on HP 9000/700 or 800 series with the PA RISC 1.1 or PA RISC 2.0 architecture running HP-UX 10.20 or 11.x. The following restrictions and prerequisites apply:

■ Motif Version 1.2

■ For HP-UX 10.20 series 700, the following bundles and patches are required:

• PHKL_15240

• PHKL_8693

• B3782EA B.1020 HP-UX Media Kit

• HP-UX Eng RT700 B.1020 English HP-UX VUE Runtime Environment

• Y2K-1020S700 B.1020 B0125 HP-UX Core OS Year 2000 Patch Bundle

■ For HP-UX 10.20 series 800, the following bundles and patches are required:

• PHKL_15247

• PHKL_8694

• B3782EA B.1020 HP-UX Media Kit

• HP-UX Eng RT700 B.1020 English HP-UX VUE Runtime Environment

PEX_PHIGS.graPHIGS.adt.gks.4.2.1.1.bff PEX_PHIGS.graPHIGS.rte.plot.4.2.1.4.bff X11.apps.aixterm.4.2.1.2.bff X11.apps.msmit.4.2.1.4.bff

X11.apps.pm.4.2.1.1.bff X11.apps.xterm.4.2.1.2.bff X11.Dt.adt.4.2.1.1.bff X11.Dt.lib.4.2.1.9.bff X11.Dt.rte.4.2.1.17.bff X11.vsm.rte.4.2.1.10.bff

(20)

System Requirements

• Y2K-1020S700 B.1020 B0125 HP-UX Core OS Year 2000 Patch Bundle

■ For HP-UX 11.x, the following bundles and patches are required:

• Y2K-1100 B.11.00 B0315 HP-UX Core OS Year 2000 Patch Bundle

NetWare on Intel

^®

486 or Pentium

^®

Systems

Tivoli Management Framework is supported as a gateway only on NetWare 4.11 and 4.2 with Service Pack 8, or NetWare 5.0 with Service Pack 4.

Note: Enable long name support by loading the LONGNAME.NLM module before installing Tivoli Management Framework.

OS/2 on Intel 486 or Pentium Systems

Tivoli Management Framework is supported as a gateway only on OS/2 Warp 4.0 or Version 4.5 with the Tivoli management platform security for OS/2 installed.

Note: For details on installing the Tivoli management platform security, refer to the Tivoli Enterprise Installation Guide.

The following prerequisites must be met:

■ Security Enablement Services (SES). If SES is applied after fixpack installation, the fixpack must be reapplied to pick up service for SES. For details on installing SES, refer to the Tivoli Enterprise Installation Guide.

■ Fixpack 12, CSD Level XROM012, or the latest fixpack available at the time of the installation.

■ The 16 bit version of the rexec daemon, with the –q option turned on with the OS/2 TCP configuration tool.

■ Upgraded TCP/IP stacks:

• Version 4.0 stack

- Multiprotocol Transport Services (MPTS), CSD Level WR08421

- TCP/IP for OS/2, Version 4.02t

(21)

System Requirements

• Version 4.1 stack

- MPTS, Version 5.300

- TCP/IP for OS/2, Version 4.1

Solaris on Sun SPARC Systems

■ OpenLook or Motif Version 1.2

■ For Solaris 2.6.x, the following patches are required:

• 105210-27

• 106125-10

• 105464-02

• 105566-08

• 105621-23

• 105800-06

• 106193-05

• 106828-01

• 107492-01

• 107988-01

■ For Solaris 2.7, the following patches are required:

• 107359-02

• 107587-01

Windows NT on Intel 486 or Pentium Systems

Tivoli Management Framework is supported on Windows NT 4.0 with Service Pack 4 or greater.

Note: Tivoli Management Framework is not supported on

Windows NT multiuser add-ons such as Windows Terminal Server, WinDD, or Citrix Winframe.

Tivoli Endpoints

The Tivoli endpoint is supported on the operating system versions listed in the following sections.

(22)

System Requirements

AIX on IBM RS/6000 and PowerPC Systems

The endpoint is supported on AIX 4.2.1, 4.3.0, 4.3.1, or 4.3.2.

AS/400

^®

The endpoint is supported on AS/400 Release V4R3 or later. You must ensure that the following communication protocols are active to transfer files to and from AS/400 endpoints in the Tivoli network environment:

■ TCP/IP communications

■ ftp services

HP-UX on HP 9000 Systems

The endpoint is supported on HP-UX 10.20 or 11.x running on HP 9000/700 or 800 series with PA RISC 1.1 or PA RISC 2.0 architecture.

NetWare on Intel 486 or Pentium Systems

The endpoint is supported on Novell NetWare 4.1.1, 4.2, or 5.0.

OS/2 on Intel 486 or Pentium Systems

The endpoint is supported on OS/2 4.0 or 4.5 with the OS/2 TCP/IP package.

Solaris on Sun SPARC Systems

The endpoint is supported on Solaris 2.6, 2.6.1, or Solaris 7.

Windows Operating Systems on Intel 486 or Pentium Systems

The endpoint is supported on the following Windows operating systems:

■ Microsoft Windows 95 or Windows 98

■ Microsoft Windows 2000

■ Microsoft Windows NT 4.0 with Service Pack 4 or greater.

(23)

Disk Space Requirements

System Requirements for Tivoli Software Installation Service

Tivoli Software Installation Service, Version 3.7, runs on any 3.7 managed node or any 3.6.x managed node with patch 3.6.1-TMF-0045 installed, provided the operating system is not supported only as a gateway.

The Tivoli Software Installation Service depot and client can be installed on any TMR server or managed node running one of the following operating systems:

■ AIX

■ HP-UX

■ Solaris

■ Windows NT

Note: The display should be set to a resolution of 800 x 600 or greater and a minimum of 256 colors to avoid system hangs.

Disk Space Requirements

This section describes the disk space requirements for the following:

■ Tivoli Management Framework

• TMR servers, managed nodes, and gateways

• Endpoints

■ Tivoli Software Installation Service

Do not place files for Tivoli products on a remote file system or share Tivoli Management Framework files among systems in a Tivoli environment.

Disk Space Requirements for Tivoli Management Framework

This section lists the disk space requirements for TMR servers, managed nodes, gateways, and endpoints.

(24)

TMR Servers, Managed Nodes, and Gateways

The following table lists the estimated disk space required for Tivoli Management Framework. The estimated disk space includes space for the Tivoli libraries, binaries, server database, client database, manual pages, and message catalogs.

The following table presents the minimum memory requirements for Tivoli Management Framework.

Operating

System Libraries Binary Files

Server Database

Client Database

UNIX^® Man Pages

Message Catalogs

AIX 10 MB 48 MB 30 MB 10 MB 1 MB 0.5 MB

HP-UX 10 MB 94 MB 30 MB 10 MB 1 MB 0.5 MB

Solaris 10 MB 43 MB 30 MB 10 MB 1 MB 0.5 MB

Windows NT 57 MB combined in the same location

30 MB 10 MB N/A 0.5 MB

OS/2 94 MB combined in

the same location

N/A 10 MB N/A 0.5 MB

NetWare 80 MB combined in the same location

N/A 10 MB N/A 0.5 MB

Operating

System TMR Server

Managed Node (with Tivoli

Desktop)

Managed Node (without Tivoli

Desktop)

AIX 64 MB 48 MB 32 MB

HP-UX 64 MB 48 MB 32 MB

Solaris 64 MB 48 MB 32 MB

(25)

Note: The swap space for each architecture should be twice the amount of RAM on each computer.

As each Tivoli Enterprise application is added to your Tivoli

environment, additional disk space is required. Refer to the appropriate Tivoli Enterprise documentation for planning information and

additional disk space requirements.

Tivoli Endpoints

The endpoint client uses less than 2 MB of memory. It will run on any system configured to the recommended specifications of the vendor.

Disk Space Requirements for Tivoli Software Installation Service

The following table lists the estimated disk space required for the depot.

The estimated disk space includes space for the Tivoli binaries, server database, and client database.

Windows NT 48 MB 32 MB 24 MB

OS/2 N/A 64 MB 64 MB

NetWare N/A N/A 64 MB

Operating

System TMR Server

Managed Node (with Tivoli

Desktop)

Managed Node (without Tivoli

Desktop)

Operating System Binary Files

AIX 1,587 KB 205 KB 205 KB

HP-UX 2,602 KB 205 KB 205 KB

Solaris 1,625 KB 205 KB 205 KB

(26)

The following table lists the estimated disk space required for the client.

The estimated disk space includes space for the Tivoli binaries, libraries, server database, client database, and manual pages.

The following table lists the minimum memory requirements for running Tivoli Software Installation Service on a TMR server or managed node.

Note: The swap space for each architecture should be twice the amount of RAM on each system.

Windows NT 1,554 KB 205 KB 205 KB

Operating System Binary Files

Operating System Libraries Binary Files

Man Pages

AIX 19 KB 2,315 KB 26 KB 26 KB 49 KB

HP-UX 81 KB 3,329 KB 26 KB 26 KB 49 KB

Solaris 89 KB 2,352 KB 26 KB 26 KB 49 KB

Windows NT 14 KB 2,391 KB 26 KB 26 KB 4 KB

Operating System TMR Server Managed Node

AIX 64 MB 64 MB

HP-UX 128 MB 128 MB

Solaris 64 MB 64 MB

Windows NT 64 MB 64 MB

(27)

RDBMS Interface Module (RIM) Requirements and Considerations

This section provides information about the supported client and server database for each supported operating system, detailed information about each relational database management system (RDBMS), tips for installing and configuring the RDBMS software for use with Tivoli products, and troubleshooting information.

This information is intended for database administrators and others responsible for installing and configuring the RDBMS. Refer to the database vendor’s documentation to understand the implications of these tasks and for complete instructions about performing these tasks.

Consider the following information while configuring and using RIM:

■ The database client software must be properly installed and tested on the RIM host for database connectivity.

■ When creating a RIM object with the wcrtrim command, the password is limited to eight characters unless you use the –i option.

■ Although it is possible to configure multiple Tivoli Enterprise products to use a single database instance or combined application schemas, Tivoli Systems does not recommend using this

configuration with Tivoli products. If you choose to use this configuration, consult with a qualified database administrator about tuning the database server to ensure the best performance for each application involved. In addition, you should thoroughly test your environment to ensure that it works properly.

(28)

Supported RDBMS Servers

The following table lists the supported server databases for each operating system.

Operating System Supported Database Servers

AIX ^■ DB2^® 5.2, 6.1

■ Informix 7.3, 9.1, 9.2^†

■ Oracle 8.0.5 or later, 8.1.5 or later

■ Sybase 11.9.2, 12.x

HP-UX ^■ DB2 5.2, 6.1

■ Informix 7.3, 9.1, 9.2

■ Sybase 11.9.2, 12.x

Solaris ^■ DB2 5.2, 6.1

■ Informix 7.3, 9.1, 9.2

■ Sybase 11.9.2, 12.x

Windows NT ^■ DB2 5.2, 6.1

■ Informix 7.3, 9.1

■ Microsoft SQL Server 7.0 Service Pack 1

■ Sybase 11.9.2, 12.x

† Informix Server 9.2 is supported for server only. The RIM client for 9.2 is not supported on this operating system.

(29)

DB2

The following sections list the requirements for DB2 and provide information to help you install and configure DB2 for use with Tivoli products.

Requirements for DB2

The following table lists the supported DB2 client installations for each supported operating system.

Notes:

• DB2 is not supported on HP-UX 11.0.

• RIM does not support the DB2 5.2 client on a Solaris RIM host.

You must use the DB2 6.1 client on a Solaris RIM host.

• The DB2 user ID for the RIM object must be the DB2 instance owner and must match the instance name. This DB2 user ID must exist on both the DB2 client and server.

• For Windows NT systems, the DB2INSTANCE system environment variable must be set to the RIM DB2 instance name.

Operating System DB2 Server 5.2 DB2 Server 6.1

AIX DB2 5.2 CAE DB2 6.1 Runtime

HP-UX 10.20 DB2 5.2 CAE DB2 6.1 Runtime

HP-UX 11 — —

Solaris — DB2 6.1 Runtime

Windows NT DB2 5.2 CAE DB2 6.1 Runtime,

DB2 6.1 SDK

(30)

Installing and Configuring DB2

From a DB2 perspective, the RIM host is a database client. Therefore, the RIM host must have access to a DB2 server. Either a DB2 server or a DB2 client must be installed on the RIM host.

This information provides an overview of the steps required to configure DB2 for use with the RIM host. The installation process and

considerations for DB2 are independent of this documentation.

Therefore, you should follow the installation and configuration information provided in the IBM DB2 documentation.

Note: When you install DB2, the following environment variables are created in the .profile file of the instance owner:

DB2DIR The directory where the DB2 software is installed.

INSTHOME The home directory of the instance owner.

DB2INSTANCE

The active instance. This is the login name of the instance owner.

For UNIX systems, these variables can be set by running the

$DB2INSTANCE/sqllib/db2profile script (Bourne, bash, or Korn shell) or the $DB2INSTANCE/sqllib/db2cshrc script (C shell).

Considerations for the DB2 User Name

Create a user and use the same user for installing and configuring DB2.

For UNIX systems, the DB2 instance will be created in the home directory of the instance owner. The RIM object uses the user name as the DB2 instance name. You must name the DB2 user the same as the DB2 instance name.

Configuring the DB2 Server for Remote Client Access

If the RIM host is the same system as your DB2 server, no additional configuration is required. If you want remote DB2 managed nodes to access your DB2 server, perform the following steps:

1. Add the DB2COMM environment variable with the value tcpip.

(31)

2. Configure the DB2 server to accept TCP/IP clients. Edit the /etc/services file and add an entry for the connection port. The connection port name must be the same as the instance name. For example, add the following line to the services file:

TEC 3700/tcp #DB2 connection service port

3. From the command line, enter the following:

db2 update database manager configuration using svcename TEC

This command updates the service name with the connection port name (TEC), which is also the instance name in this example.

4. Issue a db2stop and then a db2start to enable listening on the service port previously defined.

Configuring the DB2 Client

To configure the DB2 client, perform the following steps:

1. Configure the client to use TCP/IP to connect to the server. Edit the /etc/services file and add the entry for the connection port. The connection port name must be the same as the instance name. For example, add the following line to the services file:

TEC 3700/tcp #DB2 connection service port

2. Add the DB2COMM environment variable with the value tcpip.

3. Catalog the server node and the remote database:

a. Start the DB2 interactive Structured Query Language (SQL) utility. Enter the following command:

db2

b. Catalog the server node:

catalog tcpip node db2node remote hostname \ server service_name

where:

db2node Specifies the name of the system where the DB2 client is installed. This name must be unique in your node directory list.

hostname Specifies the name of the system where the DB2 server is installed.

(32)

service_name Specifies the connection port name as defined in the services file.

c. Catalog the remote database:

catalog database db_name as alias_name at node db2node

where:

db_name Specifies the name of the remote database.

alias_name Specifies the name of the client instance.

db2node Specifies the name of the system where the DB2 client is installed.

4. Verify connectivity to the database:

connect to db_name user db_user using db_user_password

Note: You must catalog the authentication server. RIM does not support the default authentication (client).

Informix

The following sections list the requirements for Informix and provide information to help you install and configure Informix for use with Tivoli products.

Requirements for Informix

You must use unbuffered logging with all Informix databases. Do not use American National Standards Institute (ANSI)-mode logging. If you do not switch from ANSI-mode logging to unbuffered logging, you will likely have problems with database locks that cause Tivoli Enterprise application programs to hang. To switch to unbuffered logging, you need to back up, delete, and then re-create all of your databases used by Tivoli Enterprise products.

Refer to the Informix documentation for complete instructions about switching to unbuffered logging. The following steps provide a high-level description of the procedure:

1. Create a level 0 archive of the databases to replace.

2. Export existing tables using the dbexport command with the –ss option.

(33)

3. Drop current databases configured with ANSI-mode logging.

4. Create new databases configured with unbuffered logging.

5. Import the exported tables from step 2 into the new databases created in step 4 using the dbimport command.

The following table lists the supported Informix client installations for each supported operating system.

Notes:

• RIM hosts on AIX and Windows NT are not supported for Informix 9.2 servers.

• You should use the Informix ODBC 3.30 driver, which is packaged with SDK 2.3, for client connectivity.

• Testing has shown that Informix may have concurrency problems in a high-transaction or high-volume Tivoli environment. Under these conditions, you should tune your Informix server carefully to ensure that you do not have locking problems that result in data loss. Enabling row-level locking may resolve the locking problems with Tivoli Enterprise Console in certain environments. You should consult a qualified Informix database administrator to determine the best lock mode for your environment.

Operating System

Informix Server

7.3 and 9.1 9.2

AIX SDK 2.3 —

HP-UX SDK 2.3 SDK 6.3

Solaris SDK 2.3 SDK 6.3

Windows NT SDK 2.3 —

(34)

To set lock mode to row-level locking, run the following command on all tables:

ALTER TABLE table_name LOCK MODE (ROW);

where table_name is the name of the table to be set to row-level locking.

Installing and Configuring Informix

Install the Informix RDBMS server. For installation details, refer to your Informix documentation.

Before you begin creating an Informix repository, check the following prerequisites:

■ The user ID for an Informix RIM object must be informix. It must be a valid UNIX or Windows NT user ID on the computer system hosting the database server.

■ The Informix client must be installed on the RIM host and the .odbc.ini file must be installed in the directory where the Informix software is installed ($INFORMIXDIR).

■ You must disable ANSI-mode logging. Use unbuffered logging instead.

Microsoft SQL Server

The following sections list the requirements for Microsoft SQL Server and provide information to help you install and configure Microsoft SQL Server for use with Tivoli products.

Requirements for Microsoft SQL Server

The client installations required for Microsoft SQL Server are listed in the following table.

Operating System Microsoft SQL Server 7.0 SP1

Windows NT 7.0

(35)

Installing and Configuring Microsoft SQL Server

Install Microsoft SQL Server on the RDBMS server. For installation details, refer to your Microsoft SQL Server documentation.

Note: The Install Options dialog displayed during Microsoft SQL Server installation includes a Sort Order option. To use Microsoft SQL Server for your repository, you must select the Dictionary order, case-sensitive option at installation.

You must use a Windows NT managed node to be the RIM host with this database.

After your client is installed, verify connectivity using the isql or isqlw client applications.

Oracle

The following sections list the requirements for Oracle and provide information to help you install and configure Oracle for use with Tivoli products.

Requirements for Oracle

The following table lists the supported Oracle client installations for each supported operating system.

Notes:

• It is recommended that you install the Oracle 7.3.4 client for all UNIX RIM hosts, even if you are connecting to an Oracle 8.0.x or 8.1.x server. On UNIX systems, RIM is statically linked to the Oracle 7.3.4 libraries. A full 7.3.4 client installation ensures that all the necessary message catalogs are available. (However, Operating System Oracle Server 8.0.5

or Later

Oracle Server 8.1.5 or Later

UNIX 7.3.4 7.3.4

Windows NT 8.0.5 or later 8.1.5 or later

(36)

testing of RIM hosts with Oracle 8.0.x and 8.1.x clients has been successful on English language UNIX systems.)

• For Japanese, Simplified Chinese, or Korean environments, you must install the Oracle 7.3.4 client for all UNIX RIM hosts, even if you are connecting to an Oracle 8.0.x or 8.1.x server. If you do not install the Oracle 7.3.4 client on your UNIX RIM host, you might experience connectivity problems.

• On UNIX systems, if you have already installed an Oracle 8.x client, it is recommended that you install the Oracle 7.3.4 client in a separate location. By doing this, you preserve the Oracle 8.x client in case other applications depend on it.

• The TNS_ADMIN and LOCAL environment variables are not supported. If you need to store your tnsnames.ora file in a location other than $ORACLE_HOME/network/admin, create a link or copy the file to that directory.

Installing and Configuring Oracle

Install the Oracle RDBMS on the RDBMS server. For installation details, refer to your Oracle documentation.

Select a managed node to be the RIM host.

Complete the following steps to configure the RIM host as an Oracle client:

1. Install Oracle client software, which includes SQL*Plus, on the RIM host.

2. Use FTP in text mode to copy the tnsnames.ora file from the

%ORACLE_HOME%\network\admin directory on the RDBMS server to the %ORACLE_HOME%\network\admin directory on the RIM host. %ORACLE_HOME% is the environment variable equating to the directory where your Oracle server or client installation resides.

3. Verify that the tnsnames.ora file is properly updated to reflect your configuration. In other words, check that the host name of the server, the Oracle instance ID, the port number, and the

communication protocol are accurate.

4. Verify connectivity using the Oracle SQL*Plus client application.

(37)

Sybase

The following sections list the requirements for Sybase and provide information to help you install and configure Sybase for use with Tivoli products.

Requirements for Sybase

The following table lists the supported Sybase client installations for each supported operating system.

Note: Open Client/C 11.1.1 is distributed with Sybase Adaptive Server 11.5 and 11.9.2.

Installing and Configuring Sybase

Install the Sybase RDBMS. For installation details, refer to your Sybase documentation for instructions.

Select a managed node to be the RIM host.

Complete the following steps to configure the RIM host as a client of the RDBMS server:

1. Install the Sybase client software, which includes isql, on the RIM host.

2. If your RIM host is a Windows NT system, ensure that the PATH variable includes the directory where the Sybase dynamic link library (DLL) files are installed.

3. If your RIM host is a UNIX system, copy the interfaces file from the RDBMS server to the directory on the RIM host where the Sybase client software is installed.

Operating System Sybase Server 11.9.2 and 12.x UNIX Open Client/C 11.1.1, 12.x

Note: Open Client/C 12.x is not supported on HP-UX 10.20.

Windows NT Open Client/C 11.1.1, 12.x

(38)

Note: If the RDBMS server is a Solaris system and your RIM host is not or vice versa, do not copy the interfaces file to your RIM host. The interfaces file for Solaris is not compatible with other operating systems. You must create a new interfaces file that is compatible. Consult your database administrator for assistance.

4. For Sybase 12 only, use the Tivoli odadmin environ set command to set environment variables. The following table lists the

environment variables and their required settings.

5. Verify connectivity using the Sybase isql client application.

Installing and Configuring the RDBMS

The following sections contain information about installing and configuring the supported RDBMS databases.

Troubleshooting the RIM Configuration

You can run the RIM database agent manually to troubleshoot RIM connection problems using the RIM_DB_Agent command located in

$BINDIR/bin. It is in $PATH after you set the Tivoli environment

Environment Variable Value

SYBASE client_install_path

SYBASE_OCS OCS-12_0

PATH client_install_path/OCS-12_0/bin:$PATH AIX: LIBPATH client_install_path/OCS-12_0/lib:$LIBPATH HP-UX: SHLIB_PATH client_install_path/OCS-12_0/lib:$SHLIB_PATH Solaris:

LD_LIBRARY_PATH

client_install_path/OCS-12_0/lib:$LD_LIBRARY_PATH

(39)

variables. To run the RIM database agent manually, perform the following steps:

1. Set the shared library path. Note the following considerations:

■ If your RIM host is on a Windows NT system, make sure that the PATH system environment variable includes the path to the database vendor DLL files.

■ If your RIM host is on a UNIX system, you need to set the shared library path only if you are using DB2 or Informix.

■ For DB2, the shared library path must include

$INSTHOME/sqllib/lib.

■ For Informix, the shared library path must include

$INFORMIXDIR/lib:$INFORMIXDIR/lib/cli:$INFOR MIXDIR/lib/esql.

The following table lists the name of the environment variable to use as the shared library path for each operating system type.

2. Run the wgetrim rim_name command to obtain the parameters for the RIM object. You will use the values of these parameters in the next step.

Operating System Variable

AIX LIBPATH

HP-UX SHLIB_PATH

Solaris LD_LIBRARY_PATH

Windows NT PATH

(40)

Installation and Product Notes

3. Run RIM_DB_Agent using the values of the RIM object parameters that you obtained in step 2. The syntax of RIM_DB_Agent is as follows:

RIM_DB_Agent –d database –u user [–p password]

–H rdbms_home –s server_id [–I instance_home]

where:

DB Specifies the database type. Options are DB2, Informix, MS_SQL, Oracle, and Sybase.

database Specifies the database ID.

user Specifies the RDBMS user name.

password Specifies the RDBMS user password.

rdbms_home Specifies the database home directory. That is, the location in which the database client is installed on the RIM host.

server_id Specifies the server ID.

instance_home Specifies the instance home directory. (DB2 only) If the connection is successful, RIM_DB_Agent displays the message Connection Successful.If the connection fails, the appropriate database errors are displayed.

Installation and Product Notes

This section contains the following information:

■ Installation notes for Tivoli Management Framework

■ Product notes for Tivoli Software Installation Service

■ Lists of interpreter types

Tivoli Management Framework Installation Notes

This section contains important information that you should consider when installing Tivoli Management Framework or using its installation

(41)

mechanisms to install other Tivoli Enterprise software. It contains the following topics:

■ General Installation Notes

■ Upgrading Tivoli Management Framework on Solaris Systems That Share Files with NFS

■ Upgrading Tivoli Management Framework When Tivoli Security Management Is Installed

■ Creating Version 3.6 Managed Nodes in a Version 3.7 TMR

General Installation Notes

■ Tivoli Software Installation Service, Version 3.6.x, does not run on Tivoli Management Framework, Version 3.7. Therefore, before upgrading to Tivoli Management Framework, Version 3.7, on a managed node or TMR server where Tivoli Software Installation Service, Version 3.6 or 3.6.1, is installed, upgrade Tivoli Software Installation Service to Version 3.7.

Tivoli Software Installation Service, Version 3.7, operates on all versions of Tivoli Management Framework at or above

Version 3.6.1 with patch 3.6.1-TMF-0045 installed.

■ To install or upgrade AS/400 endpoints on Tivoli Management Framework, Version 3.7, you must install patch 3.7-TMF-0001 on all gateways and on each depot if you want to use Tivoli Software Installation Service to install or upgrade AS/400 endpoints.

(CMVC-98668)

Existing AS/400 endpoints at Version 3.6.1 or higher will continue to work with Tivoli Management Framework, Version 3.7, and your existing applications until you install an application that requires Version 3.7 endpoint functionality.

Because OS/400 CISC versions are no longer supported, it is no longer necessary to differentiate between the AS/400 interpreter types os400-v3r2 and os400-v3r7. New AS/400 code (including this code in this patch) uses only the os400 interpreter type.

(42)

Due to this change, the

$BINDIR/../lcf_bundle.40/generic/w4fix_interp.pl script is supplied to perform the following actions:

• Copies (or creates links in UNIX systems) of all directories with lcf_bundle/xxx/os400-v3r7 to lcf_bundle/xxx/os400.

• Adds os400 entries in all dependency sets in which there are entries for os400-v3r7.

• Adds a user login map entry for os400 that includes an entry for os400-v3r7.

This script runs automatically during the installation of this patch.

If you install a Version 3.6.x application after installing 3.7-TMF-0001, you must manually run the script. Enter the following command after installing any Version 3.6.x application on a managed node that already has AS/400 endpoint support:

$BINDIR/lcf_bundle.40/generic/w4fix_interp.pl

■ Before installing a product or patch, verify that all managed nodes in your TMR are quiescent. (Refer to the wlocktmr and lcfd commands.)

Tivoli strongly recommends that you do not share binaries between managed nodes or across TMR boundaries. However, if your installation shares its binaries from an NTFS file server, use the file manager on the NTFS server that holds the binaries to clear all remaining network connections that pertain to the Tivoli installation directories. Perform this step before starting the installation.

This prevents errors that may occur during the installation of Tivoli Management Framework that result in files not being updated. This may happen because it is not possible to move or replace files in a directory when NTFS has a read lock that has not expired on the directory.

■ When installing the TMR server on a Windows NT system, you can log in using any user ID. However, this user must be a member of the Administrators group on the local system.

(43)

■ On HP-UX, the following error is displayed if you run a Tivoli Distributed Monitoring engine during a Tivoli Management Framework upgrade:

libwnotutor.sl: File exists. Completed with errors.

This error message can be safely ignored. The libwnotutor.sl file, although included with Version 3.7, did not change from the previous version.

■ When you use the PATH variable to define your system path, Windows NT commands are unable to find the correct

environment and tools (sh.exe). Thus, method scripts spawned by the oserv hang. The variable should be set as Path (mixed case) instead of PATH (uppercase).

■ During installation on a UNIX TMR server, shell commands are sent to the managed node. If the root shell on the target system is the C shell, these commands fail. The root shell on target systems should be bash, Bourne, or Korn shell.

■ During installation, your environment setup files are written to the /etc/Tivoli directory on UNIX or to

%SystemRoot%\system32\drivers\etc\Tivoli on Windows NT.

Creating these files in a different directory or moving the files to a different directory is not supported.

■ You cannot install a TMR server, managed node, gateway, endpoint, or Tivoli Enterprise application into a location in a UNIX file system that has a path longer than 120 characters. If you must use a longer path, create a symbolic link of 120 characters or less that points to the actual directory.

■ You cannot install a managed node, gateway, endpoint, or Tivoli Enterprise application into a location in a OS/2 file system that has a path longer than 260 characters.

■ You cannot install a gateway or endpoint into a location in a NetWare file system that has a path longer than 100 characters.

■ When you install Tivoli Management Framework on any of the UNIX architectures, create a special account under which Tivoli

(44)

Management Framework will run. The account varies with each architecture as follows:

HP-UX tmersrvd:*:59999:59999:Reserved for TME:/:/bin/false

AIX nobody:*:4294967294:4294967294::/:

Solaris nobody:*:60001:60001::/:

This account is used by Tivoli Enterprise applications for most operations. If the account does not exist, Tivoli Management Framework randomly selects an account ID under which it runs required operations. As a rule, Tivoli Management Framework selects an account ID high enough so that conflicts do not occur.

The only way to ensure that these conflicts do not arise, however, is to create the accounts shown above.

Note: For AIX, installing Tivoli Management Framework fails if the nobody account does not exist.

■ On Windows NT systems, Tivoli Management Framework requires the tmersrvd account and the Tivoli_Admin_Privileges group account. These accounts are created during the installation and should not be deleted. If tmersrvd has been deleted from the Windows NT User Manager, the executable file ntconfig.exe must be run from the database directory on the local system to re-create this account. The ntconfig.exe file has the following functions:

• It runs as the user defined in the Default Access Account.

• It creates the tmersrvd account as well as the Tivoli_Admin_Privileges group account.

• It assigns the required user rights.

■ Tivoli Management Framework requires special accounts to manage NetWare gateways and endpoints. The following accounts are needed:

• For endpoints, Admin (for root) and lcfrsrvd (for nobody)

• For gateways, Admin (for root) and tmersrvd (for nobody) These accounts are created during the installation when it is done using Novell Requester. In bindery, the accounts are created on the

(45)

local machine. In Novell Directory Service (NDS), you choose whether to have a single lcfrsrvd or tmersrvd account in the NDS tree where the machine is located or to have one in each NDS subcontext.

If the Windows system does not have Novell Requester, the account is not created. To create the account, use the addadmin utility provided by Tivoli Management Framework.

Note: Never use the Novell NWADMIN utility to create the account.

■ When installing an AIX TMR server, you might see spurious warning messages on the console. This can be caused by an older version of Motif or X11. The warnings are harmless and can be ignored.

■ For UNIX systems, ensure that you have enough file system space on Network File System (NFS)-mounted file systems to install Tivoli Management Framework and Tivoli Enterprise

applications. If the file system lacks sufficient space, the

installation will hang without providing an adequate indication of the problem. Contact your operating system provider to report NFS problems.

■ When you install Tivoli Management Framework on a UNIX system, the /tmp/.tivoli directory is created. This directory contains files that are required by the oserv process. You should not delete this directory or any of its contents unless directed to do so by your Tivoli support provider. You should also ensure that regularly scheduled disk clean-up jobs (cron or Tivoli jobs) do not remove this directory or its contents.

To use a different directory, you must set an environment variable in both the oserv and the shell. After installing Tivoli Management Framework, Version 3.7, perform the following steps to set the necessary environment variables:

1. Create a directory. This directory must have public read and write permissions at a minimum; it is recommended that you define full permissions, and set the sticky bit to ensure that users cannot modify files that they do not own.

(46)

2. Set the environment variable in the oserv:

a. Enter the following command:

odadmin environ get > envfile

b. Add a line to envfile:

TIVOLI_COMM_DIR=new_directory_name

c. Enter the following command:

odadmin environ set < envfile

3. Edit the Tivoli-provided setup_env.csh, setup_env.sh, and oserv.rc files in the /etc/Tivoli directory to set the

TIVOLI_COMM_DIR environment variable.

4. Add the following line to the file that starts the oserv daemon on HP-UX or Solaris:

TIVOLI_COMM_DIR=new_directory_name

Insert the line near where the other environment variables are set, in a location that runs before the oserv is started. The following table lists the file that needs to be changed on each operating system.

5. Shut down the object dispatcher by entering the following command:

odadmin shutdown all

6. Restart the object dispatcher by entering the following command:

odadmin reexec all

■ When you install a managed node that is separated from the TMR server by a firewall, you need to configure the firewall to allow either remote execution or trusted host access to the On this operating systems... Change this file...

HP-UX /sbin/init.d/Tivoli

Solaris /etc/rc3.d/S99Tivoli

Tivoli Enterprise Installation Release Notes Version 3.7