Tivoli Management Framework: Release Notespublib.boulder.ibm.com/tividd/td/framework/GI11... · evaluation and verification of operation in conjunction with other products, except

Tivoli Management Framework

Release NotesVersion 4.1

GI11-0890-00

��

Tivoli Management Framework Release Notes

Copyright Notice (November 2002)© Copyright IBM Corporation 1998, 2002. All rights reserved. May only be used pursuant to a Tivoli SystemsSoftware License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBMCustomer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored ina 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 Corporation. IBMCorporation grants you limited permission to make hardcopy or other reproductions of any machine-readabledocumentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyrightnotice. No other rights under copyright are granted without prior written permission of IBM Corporation. Thedocument is not intended for production and is furnished “as is” without warranty of any kind. All warranties onthis document are hereby disclaimed, including the warranties of merchantability and fitness for a particularpurpose.U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corporation.

TrademarksIBM, AIX, DB2, OS/2, OS/400, S/390, pSeries, Tivoli,, Tivoli Enterprise, Tivoli Enterprise Console, Tivoli SecureWay,TME, zSeries, and the Tivoli logo are trademarks or registered trademarks of International Business MachinesCorporation or Tivoli Systems Inc. in the United States, other countries, or both.

Lotus and Lotus Notes are a registered trademarks of IBM Corporation and Lotus Development Corporation in theUnited States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they willbe available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, orservices is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used.Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionallyequivalent product, program, or service can be used instead of the referenced product, program, or service. Theevaluation and verification of operation in conjunction with other products, except those expressly designated byTivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patentapplications covering subject matter in this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBMCorporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

© Copyright International Business Machines Corporation 2002. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . vConventions used in this guide . . . . . . . . vAccessing publications online. . . . . . . . . vOrdering publications . . . . . . . . . . . viProviding feedback about publications . . . . . viContacting customer support . . . . . . . . vi

Chapter 1. About this release . . . . . 1New features . . . . . . . . . . . . . . 1

Multicast support . . . . . . . . . . . . 1Distribution management by target . . . . . . 1Microsoft Windows XP support . . . . . . . 2HTTP service replacement . . . . . . . . . 2Endpoint encryption . . . . . . . . . . . 2Multiple endpoint support. . . . . . . . . 2Secure Socket Layer for Linux . . . . . . . 2Tivoli desktop customization . . . . . . . . 3AutoTrace utility . . . . . . . . . . . . 3RIM object changes . . . . . . . . . . . 3Firewall Security Toolbox . . . . . . . . . 4

Compatibility and interoperability . . . . . . . 4Patches included in Version 4.1 . . . . . . . . 5Defects fixed . . . . . . . . . . . . . . 5

Chapter 2. Installation and upgradenotes . . . . . . . . . . . . . . . 15Determining operating system patch levels . . . . 15Determining operating system swap space . . . . 15System requirements . . . . . . . . . . . 16

AIX operating system on pSeries and PowerPCsystems. . . . . . . . . . . . . . . 17HP-UX operating system on HP 9000 systems . . 17Linux on Intel 486 or Pentium systems . . . . 18Linux on zSeries systems . . . . . . . . . 18NetWare on Intel 486 or Pentium systems . . . 18OS/2 on Intel 486 or Pentium systems . . . . 18OS/400 systems . . . . . . . . . . . . 19Solaris operating environment on Sun SPARCsystems. . . . . . . . . . . . . . . 19Windows operating system on Intel 486 orPentium systems . . . . . . . . . . . 20

Browsers requirements . . . . . . . . . . 20SSL security packages requirements . . . . . . 20

SSL-A package requirements. . . . . . . . 20SSL-B package requirements . . . . . . . . 20

Disk space requirements . . . . . . . . . . 21Tivoli servers, managed nodes, and gateways . . 21Endpoints . . . . . . . . . . . . . . 22

RDBMS requirements . . . . . . . . . . . 22Supported RDBMS servers . . . . . . . . 22Requirements for DB2 clients by server version 23Requirements for Informix clients by serverversion . . . . . . . . . . . . . . . 24

Requirements for Microsoft SQL Server clients byserver version . . . . . . . . . . . . 25Requirements for Oracle clients by server version 25Requirements for Sybase clients by server version 25

Installation and product notes . . . . . . . . 25Installation notes . . . . . . . . . . . 26

General Installation Notes . . . . . . . 26Upgrading to Tivoli Management Framework,Version 4.1. . . . . . . . . . . . . 27Upgrading Tivoli Management Framework onAIX operating systems when an Oracle clientis installed. . . . . . . . . . . . . 28Upgrading Tivoli Management Frameworkwhen Tivoli Security Management is installed . 28

Product notes. . . . . . . . . . . . . 29General product notes . . . . . . . . . 29OS/2 and NetWare gateways . . . . . . 31Windows 2000 . . . . . . . . . . . 32

Interpreter type mappings . . . . . . . . . 33

Chapter 3. Software limitations,problems and workarounds. . . . . . 35Limitations . . . . . . . . . . . . . . 35Known defects and workarounds . . . . . . . 36

Endpoint and gateways . . . . . . . . . 36Endpoint installation . . . . . . . . . . 36Multiplexed Distribution . . . . . . . . . 37NetWare gateway . . . . . . . . . . . 37Object dispatcher . . . . . . . . . . . 37Product installation . . . . . . . . . . . 37RIM . . . . . . . . . . . . . . . . 38Serviceability . . . . . . . . . . . . . 38Miscellaneous . . . . . . . . . . . . 38

Chapter 4. Documentation . . . . . . 39Changes affecting UNIX manual pages only . . . 39Changes affecting all reference information . . . . 40Changes affecting installation information . . . . 42Changes affecting task information . . . . . . 43Changes to firewall documentation . . . . . . 43

Chapter 5. Internationalization notes . . 47Installation and upgrade notes . . . . . . . . 47

Enabling language support . . . . . . . . 47System requirements for Asian environments . . 48

Java requirements . . . . . . . . . . 48Endpoint notes . . . . . . . . . . . 48NEC PC98 systems . . . . . . . . . . 48Cantonese Chinese . . . . . . . . . . 49

Software limitations, problems, and workarounds . 49

© Copyright IBM Corp. 2002 iii

iv Tivoli Management Framework: Release Notes

Preface

These release notes provide important information about Tivoli® ManagementFramework, Version 4.1. These release notes are the most current information forthe product. Review these notes thoroughly before installing or using this product.

Both Tivoli and TME® 10 are used in our sales, marketing, and product literature.These terms are interchangeable with Tivoli Management Framework. Referencesto TME 10 will be removed in future product releases.

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

Conventions used in this guideThis guide uses several typeface conventions for special terms and actions. Theseconventions have the following meaning:

Bold Commands, keywords, file names, authorization roles, URLs, names ofwindows and dialogs, other controls, or other information that you mustuse literally are in bold.

Italics Variables and values that you must provide, new terms, and words andphrases that are emphasized are in italics.

MonospaceCode examples, output, and system messages are in a monospace font.

This guide uses the UNIX convention for specifying environment variables and fordirectory notation:v When using the Windows command line, replace $variable with %variable% for

environment variables and replace each forward slash (/) with a backslash (\) indirectory paths.

v When using the bash shell on Windows, use the UNIX conventions.

Accessing publications onlinePublications in the product libraries are included in PDF on the product CD.

When IBM publishes an updated version of one or more online or hardcopypublications, they are posted to the Tivoli Information Center. You can accessupdated publications in the Tivoli Information Center from the following TivoliCustomer Support Web site:

http://www.tivoli.com/support/documents

The Tivoli Information Center contains the most recent version of the books in theproduct library in PDF or HTML formats, or both. Translated documents are alsoavailable for some publications.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print dialog (which is available when

© Copyright IBM Corp. 2002 v

http://www.tivoli.com/support/documents

you click File → Print) to ensure that the full dimensions of a letter-sizedpage are printed on the paper that you are using.

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

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

From this Web page, select Publications and follow the instructions.

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968v In other countries, for a list of telephone numbers, see the following Web site:

http://www.tivoli.com/inside/store/lit_order.html

Providing feedback about publicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you havecomments or suggestions about our products and documentation, contact us in oneof the following ways:v Send an e-mail to [email protected] Complete our customer feedback survey at the following Web site:

http://www.tivoli.com/support/survey/

Contacting customer supportIf you have a problem with any Tivoli product, you can contact Customer Supportat the following Web site:

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

From this site, you can select the Software Support Guide link. This documentprovides detailed information about how to contact Customer Support, dependingon the severity of your problem, and contains the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv What information you should gather before contacting support

vi Tivoli Management Framework: Release Notes

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

http://www.tivoli.com/inside/store/lit_order.html

http://www.tivoli.com/support/survey

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

Chapter 1. About this release

This chapter describes the new features included in Tivoli ManagementFramework, Version 4.1, product compatibility and interoperability, the patchesincluded in this release, and the fixed defects included in this release.

New featuresThis section briefly describes the new features or enhancements of TivoliManagement Framework, Version 4.1. The new features are as follows:v Multicast support for MDist 2 distributionsv Distribution management by targetv Microsoft® Windows® XP supportv HTTP service replacementv Endpoint encryptionv Multiple endpoint supportv Secure Socket Layer support for Linuxv Tivoli desktop customizationv AutoTrace utilityv RIM object changesv Firewall Security Toolbox

Multicast supportUsing MDist 2 multicast support, you can simultaneously distribute profiles fromthe source host to the depot, known as depot preloading, or simultaneouslydistribute profiles from the depot to the endpoints.v To enable multicast support for depot preloading, each repeater that hosts a

MDist 2 depot must be configured to receive multicast distributions. Toconfigure a repeater to use multicast, use the wmdist command to set therepeater_multicast keyword to TRUE. To change the multicast configuration of arepeater, use the wmcast command.

v To enable an endpoint to receive a multicast distribution, use the wmdistcommand to set the endpoint_multicast keyword to TRUE. To change the depotdirectory for the endpoint, use the wep set_config depot_dir command.

When using multicast support, configure the repeaters to distribute only as fast asthe slowest connection. Because each packet of the distribution is sent at a definedrate, packets can be dropped. Dropped packets are resent using unicast.

Distribution management by targetUsing the Distribution Status console and the wmdist command, you can cancel,pause, and resume distributions to select targets as well as to the entiredistribution. This information is not in Tivoli Management Framework ReferenceManual. For information, see “Changes affecting all reference information” onpage 40.

© Copyright IBM Corp. 2002 1

Microsoft Windows XP supportThis release of Tivoli Management Framework supports Microsoft Windows XPProfessional operating systems as endpoints.

HTTP service replacementThe HTTP service (spider service) was replaced with using a third-party Webserver and Web application server. For accessing Tivoli Enterprise™ Webapplications, use the new Web access software. For additional information, seeTivoli Enterprise Installation Guide.

Endpoint encryptionThe communication between endpoints and gateway can be encrypted. You canenable encryption on a per endpoint basis or on a per gateway basis. To enableencryption at the gateway-level, run the wgateway set_crypt_mode command andrestart the gateway. To enable encryption at the endpoint-level, run the wepset_crypt_mode command followed by the wep sync_gateways command. Theencryption modes available are DES and NONE. When set to DES, 56-bitencryption is enabled. For additional information, see Tivoli Management FrameworkReference Manual.

Multiple endpoint supportTo enable multiple endpoints on a single system, the –e option was added to thelcfd command. The new –e option, which causes a unique machine identifier to begenerated when installing the endpoint. This option allows machines with multipleendpoints to be viewed by select Tivoli Enterprise applications as if each were on adifferent machine. When this option is not specified, all endpoints installed on thissingle system return the same machine identifier.

Multiple endpoints are not supported on all operating systems. You cannot installmultiple endpoints on OS/2®, OS/400®, and NetWare systems.

Additionally, you can install endpoints on Windows operating systems using theprovided Microsoft Installer (MSI) package. The image for launching the MSIendpoint package is in the /msi directory on the Tivoli Management FrameworkCD (2 of 2). For information about using MSI, see the following articles in theMicrosoft Knowledge Base:

Q255905Information about using Microsoft ORCA to edit MSI packages.

Q302430Information about deploying MSI packages in an Active Directoryenvironment.

Note: Although multiple endpoints are supported, you can only install them usingeither the winstlcf command or the provided local installer. In other words,you cannot use Tivoli Software Installation Service to install more than oneendpoint on a system.

Secure Socket Layer for LinuxThis release of Tivoli Management Framework adds Secure Socket Layer (SSL) keymanagement support for Linux operating systems. On Linux operating systems,OpenSSL is installed and enabled by default. For additional information, see Tivoli

2 Tivoli Management Framework: Release Notes

Management Framework Planning for Deployment Guide, Tivoli Management FrameworkUser’s Guide, and Tivoli Enterprise Installation Guide.

Tivoli desktop customizationThis release of Tivoli Management Framework includes the wdtmsg command.You can use this command to change the message that is displayed when theTivoli desktop is started. For information about this command, see TivoliManagement Framework Reference Manual.

AutoTrace utilityThis release of Tivoli Management Framework has an embedded utility calledAutoTrace for use by IBM® Support. AutoTrace uses shared memory segments forlogging purposes.

AutoTrace is not supported on all operating systems. It is not supported onmachines running OS/2, NetWare, and Linux on zSeries®. Additionally, AutoTraceis not supported by Tivoli endpoints, but it might be supported by a TivoliEnterprise application running on the endpoint.

On Windows operating systems, the concept of shared memory is unlike otheroperating systems. To create, support, and use shared memory segments (or tracechannels), the AutoTrace Runtime service, or atserv service, is installed during theinstallation of Tivoli Management Framework. This service is a common service forall Tivoli Enterprise applications installed on the system. The atserv service isinstalled to the \Program Files\Common Files directory as atserv.exe.

Tivoli Management Framework cannot determine which Tivoli Enterpriseapplications are AutoTrace enabled. Therefore, you must know what is installed onyour system and the effect that removing this service could cause. UninstallingTivoli Management Framework does not remove this service, because it might beused by other applications.

To determine whether it is safe to remove the atserv service:1. Read the documentation for all installed applications to determine whether

AutoTrace is mentioned.2. If documented, run the atctl product command to see what products are

initialized into the AutoTrace environment. Determine whether these productsare still on the system and active.

3. Run the atctl config command to see which products show up in the AutoTraceenvironment configuration.

You need to run the commands in both steps 2 and 3 before you uninstall TivoliManagement Framework, because the atctl program will get removed during theuninstall process.

If Tivoli Management Framework is the last AutoTrace-enabled application on theparticular system, you can remove this service. To remove, run the followingcommands:net stop atserv%SystemDrive%:\Program Files\Common Files\atserv -uninstall

RIM object changesBecause of changes in RIM technology, you must upgrade all systems that are RIMhosts to the same level as the Tivoli management region server (Tivoli server).

Chapter 1. About this release 3

When the Tivoli server and RIM hosts are at different release levels, you cannottake advantage of the new RIM technology. This includes using the wcrtrim,wsetrim, wgetrim, wrimtrace, wrimtest, and wmvrim commands from anymanaged node that is not at Tivoli Management Framework, Version 4.1.

Firewall Security ToolboxFirewall Security Toolbox provides a solution for managing your Tivolienvironment across firewalls without compromising security. On the secure side ofthe firewall, Firewall Security Toolbox provides an endpoint proxy that connects tothe gateway as if it were the endpoints. On the less secure side of the firewall, theendpoints are connected to a gateway proxy as if it were the gateway. The gatewayproxy and the endpoint proxy communicate with each other through the firewall.For information, see Tivoli Management Framework Firewall Security Toolbox User’sGuide.

Compatibility and interoperabilityThis section contains information about the compatibility and interoperability ofTivoli Management Framework.

Note: The compatibility of a Tivoli Enterprise product with Tivoli ManagementFramework does not indicate that the Tivoli Enterprise product is alsocompatible with new operating system releases that are supported by TivoliManagement Framework. For information about which operating systemsare supported by Tivoli Enterprise products, refer tohttp://www.tivoli.com/Tivoli_Electronic_Support/ vcert.nsf/Page1.

The terms compatibility and interoperability are defined as follows:

CompatibilityWhether different versions of a Tivoli Enterprise product can communicatewith different versions of Tivoli Management Framework.

InteroperabilityWhether different versions of the same Tivoli Enterprise product cancommunicate with each other.

Tivoli Management Framework, Version 4.1, can interoperate with all supportedversions of Tivoli Management Framework. When you upgrade your Tivolimanagement region server (Tivoli server) to Version 4.1, the endpoint manager isupgraded. After upgrading your server, upgrade your gateways. You can upgradeendpoints using the wepupgrd command or by using a login_policy script toautomatically upgrade endpoints the first time they log in to the upgradedgateway.

Note: Endpoint methods associated with a previous version can be downloadedand run on Version 4.1 endpoints when a Tivoli environment has bothversions of gateways.

Tivoli Management Framework, Version 4.1 is compatible with all supportedversions of Tivoli Enterprise products. For a definitive statement about whether aspecific Tivoli Enterprise product is compatible with Tivoli ManagementFramework, Version 4.1, refer to the release notes for that product. In some cases, apatch is required for these products to be compatible.

Note:


Tivoli Management Framework supports Network Address Translation(NAT). NAT managed nodes cannot communicate with non-NAT managednodes. However, the following combinations between gateways andendpoints are supported:v Non-NAT endpoint to non-NAT gatewayv Non-NAT endpoint to NAT gatewayv NAT endpoint to non-NAT gatewayv NAT endpoint to NAT gateway

Because Tivoli Enterprise software supports Kerberos 4.0 and becauseKerberos 4.0 depends on static IP addresses, Kerberos and NAT cannotcoexist.

Patches included in Version 4.1Tivoli Management Framework, Version 4.1, includes all Tivoli ManagementFramework patches through 3.7.1-TMF-0075. For a complete listing of all patchescontained in this release, see the TMF.IND file.

Defects fixedv APAR IX78353, IX83794, IX89276, defects 39824 86595 87085: Additional

documentation was added for using the widmap command with Tivoliadministrators.

v APAR IX78618, defect 40354 : On NetWare secure console, the NLMs are loadedcorrectly.

v APAR IX78868, defect 40965: The timeout value specified on the wpingcommand works.

v APAR IX81875, defect 47954: After changing the encryption level for the objectdispatcher and restarting the Tivoli server and managed nodes, the objectdispatcher no longer hangs.

v APAR IX83767: The documentation for tasks and jobs was modified. Taskscannot be copied to desktop, only jobs.

v APAR IX84946: The entire query results are displayed even when they containnew lines and carriage returns.

v APAR IX85813: On NetWare operating systems, there is now a place to specifythe context when recording and playing back response files for installingendpoints.

v APAR IX86000: Additional documentation was added for creating Tivoliadministrators. The name or label of a Tivoli administrator and the loginassociated with that administrator cannot be the same.

v APAR IX89513: Additional documentation added to specify which files aremodified during the installation of UNIX endpoints.

v APAR IX89556: Additional documentation added concerning timeout values. Thetimeout value for the gateway must be greater than the timeout value for a task.

v APAR IY01218: On machines with multiple interface cards, only configuredinterfaces that are denoted as up are detected.

v APAR IY03771: Windows 98 endpoints will report their host name now as justthe host name, no longer fully-qualified with the network name.

v APAR IY05657: The odadmin start command no longer creates random sourceports for managed node communications.


v APAR IY08217: All communication occurs through the designated port range forendpoints.

v APAR IY09608: No database problems should occur when running the bdbxcommand.

v APAR IY09973: The required authorization role is now senior for both thewepmgr start command and the wepmgr stop command.

v APAR IY11080: On Windows operating systems, the gateway process no longerrandomly consumes all the CPU.

v APAR IY11265: The waddaction command works as designed.v APAR IY11310: Additional documentation was added about the

TIVOLI_COMM_DIR variable on HP-UX operating systems.v APAR IY12003: The passwords are synchronized when set with the odadmin

install_pw and the odadmin region_pw commands.v APAR IY13333: Additional information was added about character limitation

when naming tasks. The first character of the name must be an alphabeticcharacter. The remaining characters can be alphanumerics, underscores (_),hyphens (-), periods (.), or spaces.

v APAR IY13471, defect 116983: On Windows operating systems, fixed thepath-specification problem with the image_report script.

v APAR IY14451: Disabling the tmersrvd domain account no longer causesfailures.

v APAR IY14722: On Windows operating systems, the memory leak concerns withthe lcfd process are fixed.

v APAR IY15078: Concerns with the wlookup –L command fixed.v APAR IY15180, defect 116976: Concerns with the wgettask command fixed.v APAR IY15334: The output is no longer truncated when viewing a large software

distribution with Tivoli Desktop for Windows on Windows 98 operatingsystems.

v APAR IY15586: On Windows operating systems, Daylight Savings Time (DST)changes are appropriately handled when processing dependencies betweenendpoints and gateways.

v APAR IY15672: On AIX® operating systems, the output of the wdiskspacecommand is the same as all other operating systems.

v APAR IY15732: Concerns with the disk_dir option of the wrpt command fixed.v APAR IY15755, defect 118116: The BuiltinNTAdministrator account now works in

the widmap for method.v APAR IY16013: On Windows 98 operating systems, upgrading an endpoint using

the wadminep upgrade command no longer automatically reboots the system.When using this command, a window is displayed prompting the user with anoption to reboot. Until this system is rebooted, no additional upgrades can occur.

v APAR IY16086: Added the address_notif_retry_count keyword to the lcfdcommand. This keyword controls the number of times that the endpoint willretry sending its IP address to the gateway every address_notif_interval secondsbefore attempting to contact another gateway in its login interfaces list.

v APAR IY16146, defect 120632: Repeaters no longer fail during initialization withan exception about the MDist2.bdb database file.

v APAR IY16254: Task Language Library (TLL) concerns fixed.v APAR IY16262, IY28256: The timeout value for the bdt_timed_open function

now works correctly.


v APAR IY16290: On Windows 2000 endpoints installed in a domain, theCrashOnAudit key in the LSA registry entry fixed.

v APAR IY16296: Concerns with the wep set command for connected Tivoliregions fixed.

v APAR IY16488: Can launch Tivoli Desktop for Windows on managed node withmultiple network interface cards (NICs).

v APAR IY16537: The installation of Tivoli Desktop for Windows as a softwarepackage works when a previous version of Tivoli Desktop for Windows isinstalled on the machine.

v APAR IY16691, IY16930: On NetWare operating systems, the wdskspc commandno longer fails when the customer tries to distribute a software package.

v APAR IY16834: The wdelep command deletes the endpoint from both the Tivoliname registry and the endpoint manager database.

v APAR IY16839: The fact that deleting or changing the Administrator label hasadverse effects was added to the documentation.

v APAR IY16918: The fact that installing an endpoint in the C shell (csh), a UNIXcommand interpreter, is not supported was added to the documentation.

v APAR IY16920: The wgateway stop command requires the senior authorizationrole as documented. This command will no longer work if run by anadministrator with only the admin authorization role.

v APAR IY17084, defect 120948: Filepackage blocks are now correctly created evenwhen using the do_compress=yes option.

v APAR IY17091: On OS/2 operating systems, Tivoli commands no longer conflictwith operating systems commands.

v APAR IY17165: Concerns with running and scheduling jobs fixed.v APAR IY17291: The wsetadmin command can now be run on policy subregions.v APAR IY17325: When a managed node is deleted, a notice is written to the TME

Administration notice group.v APAR IY17372: The value of LCF_DUPL_LOGIN in the allow_install_policy

script returns the first normal login timestamp of the endpoint instead of 1.v APAR IY17416: The distribution of a software package with restart set to an

endpoint starts the distribution the next time the endpoint connects to itsgateway, not when the repeater times out.

v APAR IY17422: In connected Tivoli regions, deleting an endpoint in a local Tivoliregion no longer crashes the endpoint manager in a remote Tivoli region when awep command is run in the remote Tivoli region against the deleted endpoint.

v APAR IY17614: User environment settings correctly set to run tasks.v APAR IY17627: When using SMTP to send e-mail over the Windows network,

there are no longer junk characters at the end of the that email.v APAR IY17645: After deleting a profile, all profile copies and subscriptions are

now removed.v APAR IY17762: After upgrading NetWare endpoints, the LCF.NCF file is no longer

corrupted.v APAR IY17830: Files names that are longer than 24 characters are no longer

truncated.v APAR IY17872: Windows 98 endpoints behave normally after being removed

from suspend mode.v APAR IY18197: Status for unreachable endpoints now correctly displayed.v APAR IY18204: Policy region wording in notices groups entries now correct.v APAR IY17642, IY18240: Scheduled restricted distributions now behave properly.


v APAR IY18360: Can now configure multiple email addresses when sendingnotification of an operation.

v APAR IY18624: Resolved data collection concerns when collecting data from anendpoint that is powered down.

v APAR IY18625: wep migrate_to_pref –n –g command no longer fails with the″resource not found″ message.

v APAR IY18667: Turning on the debug option while running the wbkupdbcommand no longer causes failures.

v APAR IY18703: On AIX operating systems, color saturation concerns withlaunching the Tivoli desktop resolved.

v APAR IY18726: Space allocation issues associated with starting the endpointservice resolved.

v APAR IY18731: Authorization role issues with query and query librariesresolved.

v APAR IY19078: Issues with simultaneously running 500 or less tasks resolved.v APAR IY19101: On NetWare gateways, the page fault processor exception that is

raised when running the winstsp command resolved.v APAR IY19252: The wbkupdb command no longer fails when a file changes size

during the tar in snapshot.v APAR IY19269: Tivoli Software Installation Service now removes extra white

spaces in installation index files.v APAR IY19313: The labels assigned to endpoints when using the

allow_install_policy script now added the object dispatcher number only whenthe specified endpoint label is not unique.

v APAR IY19325: The checkpoint offset is now set for segment identifiers.v APAR IY19352: On Windows operating systems, issues with the gateway or

repeater hanging during a distribution to multiple endpoints resolved.v APAR IY19416: Modified the behavior of job notifications.v APAR IY19491: On an AIX Tivoli server, installing managed nodes using the

wclient command no longer causes memory faults.v APAR IY19500: On NetWare gateways, concerns with the page fault processor

exception resolved.v APAR IY19514: Concerns with distribution log files resolved.v APAR IY19546, defect 118030: On Windows operating systems, installing

endpoints using the winstlcf command no longer fail.v APAR IY19647: The /etc/wlocalhost file now has read access.v APAR IY19684: Windows endpoints with multiple NICs no longer fail initial

login.v APAR IY19853: Can now reinstall patches that use obsolete directories.v APAR IY19899: Truncation concerns during marshalling and unmarshalling

resolved.v APAR IY19940: Removing a managed node now removes the gateway and

cleans up the repeater structure.v APAR IY19988: Concerns about when multiple tasks try to write files to

endpoints addressed.v APAR IY20118, IY20091: On Windows 98 endpoints, the endpoint now remains

connected after the user logs off.v APAR IY20172: The wchkdb command now cleans up back gateway references.


v APAR IY20398: The winstlcf command no longer fails when used with endpointproxies.

v APAR IY20512: Additional documentation added for the wmdist command.v APAR IY20649: The wschedjob command no longer ignores the value specified

for the retry_unit keyword.v APAR IY20655: After upgrading an endpoint, the endpoint settings are now

correct.v APAR IY20729: The documentation concerning the output of the wcrtjob

command corrected.v APAR IY20790, defect 116126: The wdepot delete command no longer reports

packages that are in use.v APAR IY20800: Concerns with opening the endpoint HTTP Web page resolved.v APAR IY20970: On NetWare operating systems, the ADDADMIN.NLM now

allows 256 characters instead of 61 characters.v APAR IY21187: Viewing a distribution requires the RIM_view or senior

authorization role. The administrator no longer needs the RIM_updateauthorization role.

v APAR IY21272: To close a security hole added the –D http_pw=password optionthat can be specified during endpoint installation. With the gateway down, nolcf.dat file created, but the new httpd.dat file is created. With gateway up,endpoint logs in successfully and the lcf.dat and httpd.dat files are created.

v APAR IY21291: Concerns about using an Oracle RDBMS for RIM databasesresolved.

v APAR IY21440: Fixed the return values associated with the wdistrib –rcommand when run against an inventory profile.

v APAR IY21518, defect 119160: Can now register resources associated with TivoliManager products.

v APAR IY21558: The examples for the wlsnotif command now match the output.v APAR IY21598: Concerns with Windows gateways randomly crashing resolved.v APAR IY21606: After importing a new image, Tivoli Software Installation Service

now refreshes a shared depot across Tivoli region boundaries.v APAR IY21614: On Windows 2000 operating systems, installing a managed node

correctly handles the installation of the msvcrt40.dll file.v APAR IY21769: Running the wepmgr fsck command now fixes the endpoints in

the Tivoli Name Registry.v APAR IY21788: On HP-UX 11 operating systems, can now delete jobs.v APAR IY21796: Deleting profiles now removes references in the Tivoli object

database.v APAR IY22155: Can now shutdown a Windows 98 operating system where an

endpoint is installed.v APAR IY22228: On UNIX operating systems, changed file permissions for the

/tools subdirectory from 777 to 700.v APAR IY22285: The size of the Mobile Computing console no longer grows each

time it is started.v APAR IY22401: Using the spider service no longer allows access to all files when

accessed from the Tivoli server.v APAR IY22403: The gateway no longer crashes on HTTP requests with large

URLs.v APAR IY22419: Column headers associated with UserProfile profiles are now

text.


v APAR IY22486: When using Tivoli Manager for Oracle, distribution using thePreserve Modification option now correctly distributes the profiles to targets.

v APAR IY22597: After upgrading a Windows 98 endpoint, the user can specifywhen to reboot the system.

v APAR IY22910: The gateway list now shows the correct protocol for gatewaysthat are down.

v APAR IY22926: Endpoint upcall issues for monitors resolved.v APAR IY22970: When using Tivoli Software Installation Service to install

endpoints on Windows operating systems, the TivoliAP.dll file and LAS_Keyare now registered.

v APAR IY23083: You can now create an instance of a resource and delete aninstance of that resource at the same time without causing a deadlock betweenthe Instance Manager and the Tivoli Name Registry.

v APAR IY23224, defect 126008: Using the waddaction command to define profileactions now works.

v APAR IY23327: Tivoli object IDs are no longer truncated.v APAR IY23466, defect 116515: After migrating an endpoint, distributions now

expire.v APAR IY23523: When using Tivoli Software Installation Service to upgrade Tivoli

Advanced Development Environment, the correct directory paths are now used.v APAR IY23729: Added the set_rpc_maxthreads keyword to the wgateway

commands.v APAR IY23751: On NetWare endpoints, the console screen no longer shows

debug information.v APAR IY23801: The wadminep wake_up command now sends the wakeup

packet to endpoints.v APAR IY23878: Gateways now resolve software distribution dependencies.

Libraries are now pushed down to the endpoint.v APAR IY23880: Deleting a record from a distributed profile no longer causes a

core dump.v APAR IY23955: Memory leaks associated with the Distribution Status console

fixed.v APAR IY23959, defect 114460: Thread issues in connected Tivoli regions resolved.v APAR IY24110: Endpoints now use alternate gateways.v APAR IY24195: On Windows operating systems, running tasks from the

Inventory administrative interface no longer causes memory allocation errors.v APAR IY24353: While running the monitoring engine, you can now start an

endpoint.v APAR IY24392: On NetWare endpoints, distributing profiles no longer raises

page fault exceptions.v APAR IY24461, defect 113834: Distributions are resumed after restarting

gateways.v APAR IY24539, defect 126204: You can now cancel a distribution that is targeted

to a roaming or migrated endpoint.v APAR IY24590: The output of the widmap list_maps command now correctly

formats.v APAR IY24851: While editing tasks, no erroneous error message windows are

displayed when you click Cancel or Cancel & Close.v APAR IY24863: Terminology associated with error messages modified. Removed

the references to managed nodes.


v APAR IY24908: Improved the performance of the wsub command in connectedTivoli regions

v APAR IY25016: The wlsinst –l command and the Tivoli desktop now showpatches installed using Tivoli Software Installation Service.

v APAR IY25027: The wgateway command no longer fails to process remaininggateways when an exception is raised.

v APAR IY25054, IY25113: Concerns with resource registration resolved.v APAR IY25116: Documentation added about the encryption used by Tivoli

Desktop for Windows.v APAR IY25239: The missing column header added to the output of the wep ls –i

all command.v APAR IY25259: For an isolated endpoint login, the endpoint now uses the list of

alternate gateways.v APAR IY25293: The connection algorithm between the Tivoli server and

gateways was modified.v APAR IY25310: The wrpt command now provides correct return values.v APAR IY25350: On Windows operating systems, you can now save task and job

files to different drives.v APAR IY25392: The repeater manager no longer obtains a global lock in

connected Tivoli regions.v APAR IY25403, defect 126669: Route now updated for roaming endpoints in

connected Tivoli regions.v APAR IY25405: Perl executables are now installed on OS/400 endpoints.v APAR IY25770: The endpoint manager now handles the automigration of

endpoints.v APAR IY25773: Concerns with connection timeouts resolved.v APAR IY25790: Using Microsoft Internet explorer to access the Endpoint Status

page no longer disconnects the endpoint for its gateway.v APAR IY25848, IY26764, defect 132339: Can now edit monitor arguments from

the Tivoli desktop.v APAR IY25872: On an AIX Tivoli server, concerns with the object dispatcher

using 100% of CPU resolved.v APAR IY25908: Can no longer run the wdepot command against the same

image.v APAR IY25964: Documentation added about having each job write its output to

different files.v APAR IY25969: The gateway now filters ISOLATION to MIGRATION and

MIGRATION to ISOLATION logins.v APAR IY25992: The endpoint manager now filters MIGRATION logins.v APAR IY26040: The wep sync_gateways command no longer hangs when done

while an endpoint is being upgraded.v APAR IY26118: Upgrading Tivoli Software Installation Service no longer loses

default endpoint setting.v APAR IY26195: Updated the randomization routine that the object dispatcher

uses for key generation.v APAR IY26197: The endpoint manager no longer crashes when an endpoint is

deleted before an orphaned login is completed.v APAR IY26337: The formatted output of the wmdist –e command corrected.v APAR IY26365: Performance improved for the wmdist –I command.


v APAR IY26366: The spider server now accepts concurrent and overlappingrequests without requiring a service-restart.

v APAR IY26520: The Scheduler can now handle large emails as part ofnotifications.

v APAR IY26577: The wmdist –c command now cleans up the depot.v APAR IY26613: The wep set interfaces –e ep gw_addr+port command now

provides information that the endpoint is not connected to this gateway.v APAR IY26653: Can now set the Tivoli remote access account to a trusted

domain account.v APAR IY26908, IY26909, IY26910: Memory usage issues with tasks and other

operations resolved.v APAR IY27529, defect 131107: Authorization roles for the oserv command

updated.v APAR IY27598, defect 133697: Distributions that use BARC scripts are removed

after distribution.v APAR IY27730: Marshalling errors on data from a profile now resolved.v APAR IY27844: Endpoints now run the login_policy script when they do a

normal login to their assigned gateway.v APAR IY27966: Distributions can now be specified in bytes instead of kilobytes

(KBs) by specifying SLOW_LINK=TRUE with the wmdist command. When thecurrent value of SLOW_LINK=FALSE, input of packet_size is treated as KB,net_load is treated as KB/second, and target_netload is treated as KB/second.

v APAR IY28204, defect 131696: Logins using TCP/IP connections instead of UDPnow respect the udp_interval and udp_attempts settings in retrying loginattempts to the gateway.

v APAR IY28259, defect 125818: Load on source host no longer fail.v APAR IY28334: The scheduler now correctly reschedules missed jobs.v APAR IY28473: Launching the gateway Web page no longer crashes the gateway.v APAR IY28480: The mobile.cfg file can now be updated by all users.v APAR IY28501: When a connection already exists, clicking the Mobile computing

icon in the system tray no longer launches the dial-up window.v APAR IY28552: Modifying an administrator with the wsetadmin command or

from the Tivoli desktop no longer crashes the Tivoli desktop when theadministrator does not have the appropriate authorization roles.

v APAR IY28613: The select_gateway_policy script now checks for an invalidgateway object ID and whether the gateway is operational before allowing theinstallation of an endpoint that connects to the gateway.

v APAR IY28709, defect 120559: When a software distribution requires input froma user on a Windows XP target endpoint, the window on the endpoint is placedinto the task bar, but the user can now double click the window or open thewindow.

v APAR IY28741: The TIVOLI_ADMIN_PRIVILEGES group on Windows 2000Domain Controller servers using Active directory in a BDC relationship to aMaster of Operation Domain Controller now gets permissions assigned to it bythe endpoint installer.

v APAR IY28750: Administrators can now launch the Distribution Status consolefrom the Tivoli desktop.

v APAR IY28759, IY29910: Performance enhanced so that gateways no longer takea long time to boot when the endpoint activity database (epact.bdb) contains alarge number of entries.


v APAR IY28820: Added Discretionary Access Control Lists (DACLs) to only taskscripts and binaries in temporary files.

v APAR IY28898: The gateway policy now returns only local gateways forISOLATION and MIGRATION logins.

v APAR IY28993: Authorization roles required to delete and to create resourcesmodified.

v APAR IY29116: The navigator window opens on the Tivoli desktop.v APAR IY29335: The distribution manager process no longer stops when an

endpoint in the UNAVAILABLE state is migrated to another gateway and theRDBMS server cannot be accessed.

v APAR IY29391, defect 135559: Rejected and installed distributions no longerappear in the Mobile console if the console is refreshed after the gateway isrestarted and all of the targets of the distribution have not completed.

v APAR IY29394: If an endpoint label is the same as the managed node label,uninstalling a product now looks for files on the managed node.

v APAR IY29480: The Scheduler now handles submitting a job that installssoftware packages to thousands of endpoints.

v APAR IY29639: The login_policy script no longer passes incorrect IP addresses.v APAR IY29695: Library issues when upgrading Tivoli Management Framework

on AIX operating systems resolved.v APAR IY29819: The wbkupdb command no longer fails when single port BDT

and SSL are both enabled.v APAR IY29912: The wake_up_recv_session function in the gateway no longer

consumes 100% of the CPU.v APAR IY29917: After an HMAC failure, the gateway no longer consumes 100%

of the CPU because of incorrect handling of exceptions.v APAR IY30312: The distribution algorithm used to calculate net_load and

target_netload no longer results in network flooding when a distribution isrestarted after being halted.

v APAR IY30850: The definition of the WLOCALHOST variable is the setup_envfiles fixed.

v APAR IY30962: The wcrtfpblock command no longer core dumps.v APAR IY31358: The custom task dialog gadgets used by Tivoli Manager for

Oracle now resolve correctly.v APAR IY31720: If during the startup of the endpoint service (lcfd), no domain

controller is available for the authentication of the Tivoli remote access account,lcfd fails to initialize the Tivoli Authentication Package (TivoliAP.dll).Subsequent operations on the endpoint no longer fail. The endpoint serviceretries the TivoliAP.dll initialization on subsequent downcall requests.

v APAR IY32328: Dependencies for sample_app-lcf-base are now set correctlyduring the installation of Tivoli Advanced Development Environment.

v APAR IY32447: Installing an endpoint using Tivoli Software Installation Servicenow registers the TivoliAP.dll file.

v APAR IY32459: The error message is no longer written to the distributionmanager log file (distmgr.log) when an endpoint migrates to a gateway that isalready in the route.

v APAR IY32641, defect 142873: If a distribution either expires or a command isapplied to a distribution while waiting for the send method to return a result,Mdist 2 now disregards any command if the receiver is successful.



Chapter 2. Installation and upgrade notes

This chapter contains the following information:v Determining operating system patch levels and swap spacev System, disk space, and database requirementsv Installation and product notesv Interpreter type mappings

Determining operating system patch levelsTable 1 shows the commands used to display which operating system level orpatches are installed on various systems supported by Tivoli ManagementFramework.

Table 1. Commands for determining operating system level and installed patches byoperating system

Operating system Example

IBM AIX instfix -a

HP-UX swlist

IBM OS/2 To determine the operating system level, use the syslevelcommand.

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

IBM OS/400 To determine the operating system level, use the dspsfwrsccommand.

To determine what patches are installed, use the dspptfcommand.

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

Microsoft Windows Open Windows Explorer and click About Windows in the Helpmenu.

Determining operating system swap spaceTable 2 shows the commands used to display the amount of swap space and thenumber of process slots on various systems supported by Tivoli ManagementFramework.

Table 2. Commands for determining swap space and process slots by operating system

Operating system Swap space Process slots

IBM AIX /usr/sbin/lsps –a /usr/bin/sar –v

HP-UX /etc/swapinfo /usr/bin/sam

Sun Solaris /usr/sbin/swap –s /usr/bin/sar –v

Microsoft Windows In the System Properties dialogon the Control Panel, select thePerformance tab, and clickChange

N/A


Refer to your operating system documentation to increase the amount of swapspace or the number of process slots on your system.

System requirementsThis section describe the operating system software and hardware requirements forTivoli Management Framework resources. For information about additional systemrequirements for Asian languages, see “System requirements for Asianenvironments” on page 48.

Tivoli Enterprise software has specific software and hardware prerequisites thatmust be met before it can be installed and considered functional. Theserequirements include operating systems, hardware platforms, relational and objectdatabase management systems, e-mail and Web servers, and support libraries. Theprerequisites listed in this document are the recommended environment for TivoliEnterprise software at the time of publication. Tivoli Enterprise software issupported only when used with prerequisites that are officially supported by thethird-party vendor.

Many vendors unilaterally withdraw support for their products on a regular basis.IBM reserves the right to unilaterally withdraw support for its software based onthe availability of support from a vendor for any prerequisite software. Contact thevendor of any prerequisite software if you have questions about its currentsupport.

This section contains information about the supported operating system versionsfor each supported hardware platform. IBM does not distribute or maintainoperating system patches from hardware vendors, except for IBM operatingsystems. Contact your hardware vendor for information about obtaining andinstalling the most current operating system patches. If you do not know how tocontact your hardware vendor, contact your IBM support provider for details onthe recommended procedure.

Table 3 lists which Tivoli Management Framework resources (Tivoli managementregion server[Tivoli server], managed node, gateway, endpoint) are supported onwhich operating systems.

Table 3. Resource types supported on operating systems

Operating system Resource type

AIX Tivoli serverManaged nodeGatewayEndpoint

HP-UX Tivoli serverManaged nodeGatewayEndpoint

Linux on Intel Tivoli serverManaged nodeGatewayEndpoint

Linux on z/OS Tivoli serverManaged nodeGatewayEndpoint


Table 3. Resource types supported on operating systems (continued)

Operating system Resource type

NetWare GatewayEndpoint

OS/2 GatewayEndpoint

OS/400 Endpoint

OS/390® Endpoint

Solaris Tivoli serverManaged nodeGatewayEndpoint

Windows 98Windows XP

Endpoint

Windows NTWindows 2000

Tivoli serverManaged nodeGatewayEndpoint

AIX operating system on pSeries and PowerPC systemsThe following Tivoli resources supported on AIX 4.3.3 or AIX 5.1 on pSeries® andPowerPC systems in 32-bit mode:v Tivoli serverv Managed nodev Gatewayv Endpoint

For AIX 4.3.3, you must install maintenance level 4330-09.

For AIX 5.1, you must install maintenance level 5100-01.

Note: Before installing maintenance level 5100-01, you must apply and commitAPAR IY19375 using the AIX System Management Interface Tool (SMIT).This fix includes the following filesets:v bos.mp64 5.1.0.1v bos.mp 5.1.0.1v bos.up 5.1.0.1

After installing these filesets, reboot the system, install maintenance level5100-01, and reboot the system again.

These maintenance levels and fixes can be downloaded from the following site:

http://techsupport.services.ibm.com/rs6000/fixes

HP-UX operating system on HP 9000 systemsThe following Tivoli resources supported on HP 9000/700 or 800 series with thePA RISC 1.1 or PA RISC 2.0 architecture running HP-UX 11i or HP-UX 11.0:v Tivoli serverv Managed nodev Gatewayv Endpoint

Chapter 2. Installation and upgrade notes 17

http://techsupport.services.ibm.com/rs6000/fixes

For HP-UX 11i, you must install Quality Pack GOLDQPK11i

For HP-UX 11, you must install Quality Pack QPK1100

The quality pack bundles can be downloaded from the following site:

http://www.software.hp.com/SUPPORT_PLUS/qpk.html

Java support can be downloaded from the following site:

http://www.hp.com/products1/unix/java/infolibrary/patches.html

Linux on Intel 486 or Pentium systemsThe following Tivoli resources are supported on Linux on Intel® or Pentium®

systems running Red Hat 7.2 or SuSE 7.2:v Tivoli serverv Managed nodev Gatewayv Endpoint

Linux on zSeries systemsThe following Tivoli resources are supported on IBM S/390 G5, G6, or MP3000system with the Linux 2.2 or 2.4 kernel running Red Hat 7.2 on zSeries, SuSEEnterprise Server 7.2 on zSeries:v Tivoli serverv Managed nodev Gatewayv Endpoint

Linux on S/390 does not support a native Tivoli desktop. You can install TivoliDesktop for Windows on another system and connect to a Linux on S/390managed node.

Note: The C Runtime Library (libc) version 3.1.3-176 or later is included in allsupported distributions. If you do not have this version or greater, upgradethis library using the Developer Kit for Linux. To determine the level ofglibc on your system, enter the following command from a shell prompt:rpm -q libc

Newer version of libc can be compiled to provide floating stack support.This version of Java will not run when floating stack support is enabled.

NetWare on Intel 486 or Pentium systemsThe following Tivoli resources are supported on NetWare 5.1 or NetWare 6.0:v Gatewayv Endpoint

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

OS/2 on Intel 486 or Pentium systemsThe following Tivoli resources are supported on OS/2 Warp Server for eBusiness4.5:v Gateway when Tivoli management platform security is installed


http://www.software.hp.com/SUPPORT_PLUS/qpk.html

http://www.hp.com/products1/unix/java/infolibrary/patches.html

v Endpoint

The following Tivoli resource is supported on OS/2 Warp Server for eBusiness 4.0:v Endpoint

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

For gateways, the following requirements or prerequisites must be met:v 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 installingSES, refer to the Tivoli Enterprise Installation Guide.

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

v Upgraded TCP/IP stacks:– Version 4.0 stack

- Multiprotocol Transport Services (MPTS), CSD Level WR08421- TCP/IP for OS/2, Version 4.02t

– Version 4.1 stack- MPTS, Version 5.300- TCP/IP for OS/2, Version 4.1

For Java support on OS/2 systems, the following requirements must be met:v For DBCS locales, fixpack FX00505 or greater.v Workspace On-Demand OS/2 client, Version 2.0 or 3.0

OS/400 systemsOnly an endpoint is supported on all supported releases of IBM OS/400. You mustensure that the following communication protocols are active to transfer files toand from OS/400 endpoints in the Tivoli environment:v TCP/IP communicationsv File Transfer Protocol (FTP) services

Note: You cannot install multiple endpoints to an OS/400 system.

Solaris operating environment on Sun SPARC systemsThe following Tivoli resources are supported on Solaris 7 or Solaris 8:v Tivoli serverv Managed nodev Gatewayv Endpoints

For Solaris operating systems, you must install Patch Clusters with a date ofJanuary 2002 or later.

Additional information for downloading patches is available from the followingsite:

http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

Additional information regarding Java support is available from the following site:

http://java.sun.com/j2se/1.3/install-solaris-patches.html


http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

http://java.sun.com/j2se/1.3/install-solaris-patches.html

Windows operating system on Intel 486 or Pentium systemsThe following Tivoli resources are supported on Windows NT® 4.0 with ServicePack 6a or greater, Windows 2000 Server, or Windows 2000 Advanced Server:v Tivoli serverv Managed nodev Gatewayv Endpoint

The following Tivoli resource is supported on Windows 98, Windows 2000Professional, and Windows XP Professional:v Endpoint

Note: Tivoli Management Framework does not support multiuser add-ons such asWindows Terminal Server, WinDD, or Citrix Metaframe. When running witha multiuser add-on, Tivoli Management Framework manages this machineas a single entity.

Browsers requirementsDepending on the operating system, the requirements for browsers differ. Browsersare used to access and display Tivoli Management Framework Web contents.

Note: For any Web browser, ensure that you have the latest security patchinstalled on your operating system. These patches can be downloaded fromthe Web site of the vendor.

The supported minimum and maximum versions are as follows:v For OS/2 operating systems, you must use Netscape, Version 4.6, or Netscape,

Version 4.6.1.v For all other operating systems, you must use at least Netscape, Version 4.72, but

you can use any version of Netscape up to, but not including, Version 6.0.v For all Windows operating systems, you must use at least Internet Explorer,

Version 5.5 with service pack 1, but you can use any version of Internet Explorerup to Version 6.0. With any version of Internet Explorer, you must use theversion with 128-bit encryption.

SSL security packages requirements

SSL-A package requirementsSSL encryption using the Tivoli Management Framework SSL-A package is fullysupported for single-port bulk data transfers communication channels on thefollowing systems:v AIX at levels 4.3.3 or 5.1v Solaris at levels 7 or 8v OS/2 for level 4.5v HP-UX at levels 10.20 series 700 or 800 and 11 or 11i for SSL-A encryption is

available for oserv communication channels only, not for BDT.

SSL-B package requirementsThe SSL-B package only contains key management utilities for use with OpenSSL.These utilities work on all supported Linux platforms and releases.


Disk space requirementsThis section describes the disk space requirements for the following:v Tivoli servers, managed nodes, and gatewaysv Endpoints

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

Required disk space for any product can be estimated by checking the size of theinstallation folder for that product and calculating that the uncompressed valuewill be 20% to 70% larger. For example, if the JAVA folder is 100 MB, the actualinstallation size will be between 120 MB and 170 MB.

Tivoli servers, managed nodes, and gatewaysThe following table lists the estimated disk space required for Tivoli ManagementFramework. The estimated disk space includes space for the Tivoli libraries,binaries, server database, client database, manual (man) pages, and messagecatalogs.

Operating System Libraries Binary files Server database Client database Manualpages

Messagecatalogs

AIX 20 MB 110 MB 30 MB 10 MB 1 MB 1 MB

HP-UX 15 MB 115 MB 30 MB 10 MB 1 MB 1 MB

Linux 15 MB 100 MB 30 MB 10 MB 1 MB 1 MB

Solaris 15 MB 105 MB 30 MB 10 MB 1 MB 1 MB

Windows 110 MB in the same location 30 MB 10 MB N/A 1 MB

OS/2 100 MB in the same location N/A 10 MB N/A 1 MB

NetWare 100 MB in the same location N/A 10 MB N/A 1 MB

The following table presents the minimum memory requirements for TivoliManagement Framework.

Operating System Tivoli server Managed node (with Tivolidesktop)

Managed node (withoutTivoli desktop)

AIX 128 MB 128 MB N/A

HP-UX 128 MB 128 MB N/A

Linux 128 MB 128 MB N/A

Solaris 128 MB 128 MB N/A

Windows 128 MB 128 MB 128 MB

OS/2 N/A 128 MB 128 MB

NetWare N/A N/A 128 MB

As each Tivoli Enterprise product is added to your Tivoli environment, additionaldisk space is required. Refer to the appropriate documentation for planninginformation and additional disk space requirements.


EndpointsThe endpoint client uses less than 2 MB of memory. It runs on any systemconfigured to the recommended specifications of the vendor.

RDBMS requirementsThis section provides information about the supported client and server databasefor each supported operating system, detailed information about each relationaldatabase management system (RDBMS), tips for installing and configuring theRDBMS software for use with Tivoli Enterprise products, and troubleshootinginformation.

This information is intended for database administrators and others responsible forinstalling and configuring the RDBMS. Refer to the database vendordocumentation to understand the implications of these tasks and for completeinstructions about performing these tasks.

Consider the following information while configuring and using the RDBMSInterface Module (RIM):v The database client software must be properly installed and tested on the RIM

host for database connectivity.v When creating a RIM object with the wcrtrim command, the password is limited

to eight characters unless you use the –i option.v You can configure multiple Tivoli Enterprise products to use a single database

instance or combined application schemas. If you choose to use a configurationwith a single database instance, consult a qualified database administrator abouttuning the database server to ensure the best performance for each applicationinvolved. In addition, you should thoroughly test your environment to ensurethat it works properly.

Supported RDBMS serversThe following table lists the supported server databases for each operating system.

Operating system Supported database servers

AIX v DB2® 7.1, 7.21

v Informix 9.20, 9.21. 9.30

v Oracle 8.1.7, 9i2

v Sybase 12.0, 12.5

HP-UX v DB2 7.1, 7.21

v Informix 9.20, 9.21. 9.30

v Oracle 8.1.7, 9i2

v Sybase 12.0, 12.5

Linux on Intel v DB2 7.1, 7.21

v Informix 9.20, 9.21. 9.30

v Oracle 8.1.7, 9i2

v Sybase 12.0, 12.5

Linux on z/OS v DB2 7.21


Operating system Supported database servers

Solaris v DB2 7.1, 7.21

v Informix 9.20, 9.21. 9.30

v Oracle 8.1.7, 9i2

v Sybase 12.0, 12.5

Windows v DB2 7.1, 7.21

v Informix 9.20, 9.21. 9.30

v Microsoft SQL Server 7.0 Service Pack 1, SQL Server2000

v Oracle 8.1.7, 9i2

v Sybase 12.0, 12.5

z/OS v DB2 73

1 Support for Enterprise Edition (EE) and Enterprise-Extended Edition (EEE).2 Oracle 9i, Release 1 (9.0.1) and Oracle 9i, Release 2 (9.2.0).3 Only the DB2 server is supported on z/OS operating systems.

Upgrade note: Because of changes in the supported version of Oracle software,different upgrade scenarios must be used. The followinginformation will help you decide your required upgrade path tomaintain a working Tivoli environment.v Tivoli Management Framework, Version 4.1 supports Oracle 8.1.7

and Oracle 9i (Release 1 and Release 2).v Tivoli Management Framework, Version 3.7 Revision B, Tivoli

Management Framework, Version 3.7.1, and Tivoli ManagementFramework, Version 4.1 support Oracle 8.1.7.

v Tivoli Management Framework Version 3.7.1 and TivoliManagement Framework, Version 4.1 support Oracle 9i (Release1 and Release 2).

Using this information, you notice that Tivoli ManagementFramework, Version 3.7 Revision B, cannot be used with Oracle 9i.If you are running Tivoli Management Framework, Version 3.7Revision B, you must upgrade to Tivoli Management Framework,Version 4.1, and then upgrade Oracle software to Oracle 8.1.7 or 9i.If you are running Tivoli Management Framework, Version 3.7.1,you can upgrade Tivoli Management Framework or the Oraclesoftware in any order without harming your Tivoli environment.

Requirements for DB2 clients by server versionThe following table lists the supported DB2 client installations for each supportedoperating system.

Operating System DB2 Server

7.0 on z/OS 7.1 7.2

AIX DB2 7.2 Connect DB2 7.1 Runtime DB2 7.2 Runtime

HP-UX DB2 7.2 Connect DB2 7.2 Runtime DB2 7.2 Runtime

Linux on Intel DB2 7.2 Connect — DB2 7.2 Runtime


Operating System DB2 Server

7.0 on z/OS 7.1 7.2

Linux on z/OS DB2 7.2 Connect — DB2 7.2 Runtime

Solaris DB2 7.2 Connect DB2 7.1 Runtime DB2 7.2 Runtime

Windows DB2 7.2 Connect DB2 7.1 Runtime, DB27.1 SDK

DB2 7.2 Runtime,DB2 7.2 SDK

Requirements for Informix clients by server versionYou must use unbuffered logging with all Informix databases. Do not use AmericanNational Standards Institute (ANSI)-mode logging. If you do not switch fromANSI-mode logging to unbuffered logging, you might experience problems withdatabase locks that cause Tivoli programs to hang. To switch to unbufferedlogging, you need to back up, delete, and then re-create all of your databases usedby Tivoli Enterprise products.

Refer to the Informix documentation for complete instructions about switching tounbuffered logging. The following steps provide a high-level description of theprocedure:1. Create a level 0 archive of the databases to replace.2. Export existing tables using the dbexport command with the –ss option.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

by using the dbimport command.

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

Operating System Informix Server 9.20, 9.21, 9.30

AIX SDK 2.7

HP-UX SDK 2.7

Linux on Intel SDK 2.7

Solaris SDK 2.7

Windows SDK 2.7

Notes:

1. Use the Informix ODBC 3.30 driver, which is packaged with Informix SDK 2.3,for client connectivity.

2. Testing has shown that Informix can have concurrency problems in ahigh-transaction or high-volume Tivoli environment. Under these conditions,tune your Informix server carefully to ensure that you do not have lockingproblems that result in data loss. Enabling row-level locking can resolve thelocking problems with IBM Tivoli Enterprise Console® in certain environments.You should consult a qualified Informix database administrator to determinethe best lock mode for your environment.To set lock mode to row-level locking, run the following command on alltables:ALTER TABLE table_name LOCK MODE (ROW);


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

Requirements for Microsoft SQL Server clients by serverversion

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

Operating System Microsoft SQL Server 7.0 SP1 Microsoft SQL Server 2000

Windows Microsoft SQL Server 7.0 client Microsoft SQL Server 2000client

Requirements for Oracle clients by server versionThe following table lists the supported Oracle client installations for eachsupported operating system.

Operating System Oracle Server 8.1.7 Oracle Server 9i

AIX 8.1.7 9i

HP-UX 8.1.7 9i

Linux on Intel 8.1.7 9i

Solaris 8.1.7 9i

Windows 8.1.7 9i

Notes:

1. On AIX systems, connection problems might persist if the proper bootparameters are not set for the AIX operating system to run with asynchronousI/O. For details on resolving this issue, see “Upgrading Tivoli ManagementFramework on AIX operating systems when an Oracle client is installed” onpage 28.

2. For Japanese, Simplified Chinese, or Korean environments, you must install theOracle client. If not fully installed on your UNIX RIM host, you can experienceconnectivity problems.

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

Requirements for Sybase clients by server versionThe following table lists the supported Sybase client installations for eachsupported operating system.

Operating System Sybase Server 12.0 Sybase Server 12.5

UNIX SDK 12.0 SDK 12.0

Windows SDK 12.0 SDK 12.0

Installation and product notesConsider the following important information before installing Tivoli ManagementFramework or while using the product.


Installation notesThis section contains important information that you should consider wheninstalling Tivoli Management Framework or using its installation mechanisms toinstall other Tivoli Enterprise software. It contains the following topics:v “General Installation Notes”v “Upgrading to Tivoli Management Framework, Version 4.1” on page 27v “Upgrading Tivoli Management Framework when Tivoli Security Management

is installed” on page 28v “Upgrading Tivoli Management Framework on AIX operating systems when an

Oracle client is installed” on page 28

General Installation Notesv Although the license key does not need to be specified, the installation shows

the error, ″ERROR: You entered an invalid license key″ followed by anexplanation that they can enter the key later when you do not specify one. Thelicense key is ignored within the system when one is provided or not.

v The default remote connection setting for Version 4.1 managed nodes isversion_2. Previous installation of managed nodes used version_1 as the defaultremote connection setting. To enable remote connections from Java clients usingTivoli Management Framework, Version 3.7.x use the odadmin command asfollows:odadmin set_allow_rconnect TRUE

v Before installing a product or patch, verify that all managed nodes in your Tivolimanagement region (Tivoli region) are quiescent. (Refer to the wlocktmr andlcfd commands.)Do not share binaries between managed nodes or across Tivoli regionboundaries. However, if your installation shares its binaries from an NTFS fileserver, use the file manager on the NTFS server that holds the binaries to clearall remaining network connections that pertain to the Tivoli installationdirectories. Perform this step before starting the installation.This prevents errors that can occur during the installation of Tivoli ManagementFramework that result in files not being updated. This can happen because it isnot possible to move or replace files in a directory when NTFS has a read lockthat has not expired on the directory.

v Products are sometimes listed by the wlsinst command even when they cannotbe uninstalled using the wuninst command. A common cause is that the productdoes not provide the uninstall script required by the wuninst command. Refer tothe product documentation for information about how to uninstall theseproducts.

v Products are sometimes listed by the wlsinst –p command even after they havebeen uninstalled from the Tivoli region. If you suspect this is happening, use thewlsinst –p –v command to check whether the product is installed on anysystems in the Tivoli region.

v The root shell on UNIX managed nodes should be bash, Bourne, or Korn shell.During installation, shell commands are sent to the managed node. If the rootshell on the target system is the C shell (csh) , these commands fail.

v For UNIX operating systems, ensure that you have enough file system space onNetwork File System (NFS)-mounted file systems to install Tivoli ManagementFramework and Tivoli Enterprise applications. If the file system lacks sufficientspace, the installation hangs without providing an adequate indication of theproblem. Contact your operating system provider to report NFS problems.


v Tivoli Management Framework installs the msvcrt40.dll file, the C runtimelibrary, in the %SystemRoot%\system32 directory on supported Windowsoperating systems for use by Tivoli Enterprise applications. This version of theruntime library is the one that is shipped with Microsoft Visual C++, Version 6.0.If the %SystemRoot%\system32 directory contains a newer version of this file,Tivoli Management Framework copies the file located in$BINDIR/mslib/msvcrt40.dll to the following locations:– %DBDIR%

– $BINDIR/bin

– $BINDIR/tools

If a Tivoli Enterprise application has command-line interface (CLI) programs thatare not in the $BINDIR/bin or $BINDIR/tools directory, Tivoli ManagementFramework copies $BINDIR/mslib/msvcrt40.dll to the directories where the CLIprograms reside. Complete the following steps if a Tivoli-based application runsa method that changes the current working directory and spawns a programthat links with msvcrt40.dll. This procedure ensures that no incompatibilitiesoccur between the C runtime library needed by Tivoli Enterprise applicationsand the one needed by non-Tivoli applications.1. Determine the directory where a command might reside by using the type

command in the bash shell. The following example shows that the wepcommand is in the $BINDIR/bin directory:C:\>shbash$ type wepwep is e:/Tivoli/bin/w32-ix86/bin/wep.exebash$ echo $BINDIR/bine:/Tivoli/bin/w32-ix86/bin

2. Put a copy of the $BINDIR/mslib/msvcrt40.dll file in the new currentworking directory or the directory where the spawned program resides.

Upgrading to Tivoli Management Framework, Version 4.1To enable Tivoli Management Framework for non-English environments, you mustinstall the Tivoli Management Framework Language Support CD after upgradingTivoli Management Framework.

Upgrading from Tivoli Management Framework, Version 3.7B or Version 3.7.1:If you are upgrading from the Tivoli Management Framework, Version 3.7 RevisionB or Version 3.7.1, you can upgrade directly to Version 4.1 by using the installationimages on the Tivoli Management Framework Upgrade from Version 3.7 to Version4.1 CD.

Note: If you upgraded from Tivoli Management Framework, Version 3.7.1 beforeapplying Fixpack 3, you must install the following patches to ensureinteroperability with applications the used Tivoli Management Framework,Version 3.6.5 or Version 3.7.1:v 4.1-TMF-004 for 3.6.5 lcf_bundle librariesv 4.1-TMF-005 for 3.6.5 Tivoli server and manage node librariesv 4.1-TMF-006 for 3.7.1 Tivoli server and manage node libraries

Upgrading from Tivoli Management Framework, Version 3.7: If you areupgrading from the Tivoli Management Framework, Version 3.7 level, perform thefollowing steps:1. Upgrade to Tivoli Management Framework, Version 3.7 Revision B, by

installing the following patches:


v 3.7-TMF-0003v 3.7-TMF-0004

2. Upgrade to Tivoli Management Framework, Version 4.1 using the TivoliManagement Framework Upgrade from Version 3.7 to Version 4.1 CD.


Upgrading from Tivoli Management Framework, Version 3.6: If you areupgrading from the Tivoli Management Framework, Version 3.6.x level, upgrade toTivoli Management Framework, Version 4.1, using the installation images on theTivoli Management Framework Upgrade from Version 3.6 to Version 4.1 CD.


Upgrading Tivoli Management Framework on AIX operatingsystems when an Oracle client is installedTo upgrade Tivoli Management Framework on an AIX operating system with anOracle client, perform the following steps using the System Management InterfaceTool (SMIT):1. To change the characteristics of asynchronous I/O, enter the following

command:smith chaio

2. From the menu, select State to be configured at system restart.3. Change the value of this option from defined to available.4. Press Enter.5. Exit SMIT by pressing F10.6. Restart the system by entering the following command:

shutdown -r

Upgrading Tivoli Management Framework when Tivoli SecurityManagement is installedThis section contains information related to Tivoli SecureWay® Security Managerand Tivoli Access Control Facility that you should consider when upgrading TivoliManagement Framework:v Always start an object dispatcher or endpoint using the full path to the daemon.

Start the object dispatcher using $BINDIR/bin/oserv. Start the endpoint daemonusing $LCF_BINDIR/lcfd.If you created or customized scripts that start the object dispatcher or endpoint,they must be edited. If you use the oserv or lcfd command from the commandline, specify the full path.


If you do not specify the full path to the oserv or endpoints, you cannot performbasic Tivoli Access Control Facility related functions, such as populating anddistributing security profiles or running tasks.

v When upgrading Tivoli Management Framework on a UNIX Tivoli server ormanaged node where Tivoli Access Control Facility is installed, or whenupgrading endpoints on which Tivoli Access Control Facility is installed, thefollowing steps are required for a successful upgrade:1. Define root as a Tivoli Access Control Facility administrator using the

Add/Remove TACF Administrator/Auditor task in the Tivoli Access ControlFacility Tasks task library.

2. Stop the Tivoli Access Control Facility daemons using the Stop TACFServers task.

3. Upgrade Tivoli Management Framework on affected systems. For moreinformation about how to do this, see the Tivoli Enterprise Installation Guide.

4. As root, use the selang –l utility to explicitly retrust oserv (and possiblytask_endpoint) on a Tivoli server or managed node or to retrust lcfd on anendpoint. This is illustrated in the following examples.For a Tivoli server or managed node running Tivoli Access Control Facility,Version 3.6.x, that has been upgraded from Version 3.2:/usr/seos/bin/selang -lTACF> cr PROGRAM /path/oserv trustTACF> cr PROGRAM /path/task_endpoint trustTACF> quit

For a Tivoli server or managed node running Tivoli Access Control Facility,Version 3.6.x, that has not been upgraded from Version 3.2:/usr/seos/bin/selang -lTACF> cr PROGRAM /path/oserv trustTACF> quit

For an endpoint:/usr/seos/bin/selang -lTACF> cr PROGRAM /path/lcfd trustTACF> quit

Note: You can create a task to perform the retrust on all the UNIX systemson which programs must be retrusted.

5. Restart the Tivoli Access Control Facility daemons using the Start TACFServers task.

Note: You can remove the Tivoli Access Control Facility administrator role fromroot using the Add/Remove TACF Administrator/Auditor task in theTivoli Access Control Facility Tasks task library.

Product notesThis section contains important information to consider when using TivoliManagement Framework. It contains the following topics:v “General product notes”v “OS/2 and NetWare gateways” on page 31v “Windows 2000” on page 32

General product notesv Applications not linked to Version 3.7.x libraries cannot take advantage of port

consolidation or SSL over their BDT channels. For example, an application built


on Tivoli Management Framework, Version 3.6.x does not have access to thenew features of SSL encryption and port consolidation for BDT channels. Theseapplications perform IOM and other BDT operations in the pre-3.7.1 manner;that is, according to the port range and without SSL.

Note: A managed node or application that is not SSL-capable cannot encryptBDT or oserv communications using SSL.

Implications include the following:– Use caution when specifying the FORCE_SSL option on SSL-capable nodes in

a Tivoli environment where incapable managed nodes or applications exist.Version 3.6.x applications, pre-3.7.1 managed nodes, and certain interps arenot capable of communicating with SSL. For example, you cannot consolidateBDT operations between Tivoli Desktop for Windows and a Tivoli server setto FORCE_SSL. The same is true for any Version 3.6.x-linked applications;that is, FORCE_SSL options within the Tivoli environment can cause theapplications to fail to operate.

– In a Tivoli environment where 3.6.x applications are in use, it might not bepossible to tighten firewall restrictions to the full extent intended by thedesign of single-port BDT. Configuring your firewalls to be restrictedaccording to single-port BDT design can cause 3.6.x applications to fail if andwhen they attempt to make BDT connections. Keep in mind that pre-3.7.1managed nodes also are not capable of using single-port BDT.

Recommendation: You should not modify firewall configurations to takeadvantage of port consolidation if you are using either of the following withinthe firewall environment:– Tivoli Enterprise products that were not designed to take advantage of Tivoli

Management Framework, Version 4.1 features– Pre-3.7.1 managed nodes

In either case, the existing firewall configurations for pre-3.7.1 communicationsshould remain unchanged. If this is a new Tivoli implementation, you can set upthe firewall configuration to use the pre-3.7.1 based port range settings.

v On managed nodes where odadmin single_port_bdt is set to TRUE on whichthere is also a gateway, the gateway process serves as the port consolidationproxy for IOM/BDT operations originating from that node. For managed nodeswithout gateways installed, the rpt2 process handles BDT proxying.You must consider the implications to BDT operations before stopping thegateway or rpt2 process on a managed node. To stop either of these processesmeans to end all active IOM/BDT channels; thereby, interrupting Tivoliprocesses on the node, including desktop operations, software installations,backups, inventory scans, event accumulation, and software distributions.

v The BDT service will use either the rpt2 or gateway process, depending onwhether a gateway is installed on the managed node. If you attempt to create agateway on a managed node where a BDT service is already active (the rpt2process is running), the gateway process attempts to use the same port to runthe BDT service job.Because two processes cannot use the same port, there is a built-in failover whena BDT port is in use. Instead of the gateway failing, the gateway processattempts to open the specified BDT port (for example, port 13000), waiting 10seconds between each attempt (up to a maximum of 3 times). If the port is stillin use, the gateway process increases the value of the port by 1 (for example,13000 to 13001) and attempts to use that port. If the port+1 value also is in use,


the gateway fails to boot. If the port+1 value is available, the gateway boots anduses this port until the next time the oserv is restarted (odadmin reexec). Whenthe oserv is restarted, the gateway tries to use the port specified in the originalsetting (for example, 13000).Even though there is a built-in failover when a BDT port is in use on a gateway,it is recommended that you follow one of these procedures:Procedure A:1. Set odadmin single_port_bdt to FALSE to temporarily disable single-port

BDT.2. Create a gateway on the managed node.3. Set odadmin single_port_bdt to TRUE to enable single-port BDT again.

Procedure B:1. Temporarily open a new port value in the firewall (for example, port 14000).2. Use the odadmin single_port_bdt command to change to the new port

value.

Note: The original BDT service continues to operate using the old portvalue.

3. Create a gateway on the managed node.

Note: The gateway uses the new port value for the BDT port. Eventually, theold port value will no longer be used. When this occurs, close thefirewall against the old port value and regain single BDT port firewallsecurity (now on port 14000).

OS/2 and NetWare gatewaysTivoli Management Framework provides standalone gateways that are notmanaged nodes. These gateways are available on OS/2 and NetWare systems. Ingeneral, they provide the same functionality of other gateways:v Endpoint login and communicationv Invocation of methods to be run on the endpoint and gateway

These gateways appear as managed nodes when you run the wlookup command.However, the functionality of these gateway differ by operating system. Thefollowing table indicates supported and unsupported functions for the OS/2 andNetWare gateways.

Gateway function OS/2 NetWare

Graphical user interface (GUI)binaries can be installed onthe gateway

Supported when using TivoliDesktop for Windows

Not supported

Tivoli desktop on a client canconnect to the gateway forGUI support

Supported when using TivoliDesktop for Windows

Not supported

Tivoli desktop can run on thegateway system

Supported Not supported

Gateway creation Supported Not supported

Tivoli ManagementFramework gateway method(provides gatewayfunctionality)

Supported Supported


Gateway function OS/2 NetWare

Scalable collection servicegateway method

Not supported Not supported

Can be configured as amultiplexed distributionrepeater


Can be configured as a RIMhost


Encryption levels of none,simple, and DES

Supported Supported

Kerberos Not supported Not supported

Resource type for managedresources and appearance onTivoli server GUI

Appears as ManagedNode—Managed_Node

Appears as ManagedNode—Managed_Node

Gateway icon Supported Supported

Gateway pop-up menufunctions

Partly supported Not supported

Profiles (configurationmanagement)

Supported Not supported

Notices Supported Not supported

Task libraries, tasks, and jobs Supported Not supported

Scheduler Supported Not supported

spider HTTP function Supported Not supported

rconnect—Tivoli ManagementFramework function

Supported (secure rconnectadded in this release notsupported)

Not supported

Windows 2000Product notes regarding Windows 2000 operating systems include the following:v To maintain the same directory permissions that are allowed in Windows NT,

the tmersrvd account (the Tivoli unprivileged operations account) is grantedread and execute permission for files in the %SystemRoot%\System32 directoryduring installation on a Windows 2000 system. You do not have to perform thisaction when installing Tivoli Management Framework.

v When a Windows 2000 server is configured to be a domain controller, the PowerUsers group does not exist. The installation neither fails nor adds the tmersrvdaccount to an alternate group.If you want to manage the Tivoli server and managed nodes on Windows NT orWindows 2000 domain controllers, manage them as endpoints. If you installapplications with high resource requirements on Windows NT or Windows 2000domain controllers, you must either give the tmersrvd account explicit read andexecute permissions to certain directories or add the tmersrvd account to theServer Operators or Account Operators groups for equivalent Windows NTpermissions.


Interpreter type mappingsThe following table lists the operating systems supported by Tivoli ManagementFramework. For each operating system, the table lists the resources you can createon that operating system and the interpreter type (interp) associated with thatoperating system and resource combination. The resource types are Tivoli server,managed node, gateway, and endpoint.

Operating system Interpreter type Resource type

Generic generic All

AIX aix4-r1 Tivoli serverManaged nodeGatewayEndpoint

OS/400 os400 Endpoint

NetWare nwr-ix86 GatewayEndpoint

OS/2 os2-ix86 GatewayEndpoint

OS/390 os390 Endpoint

HP-UX hpux10 Tivoli serverManaged nodeGatewayEndpoint

Linux on Intel linux-ix86 Tivoli serverManaged nodeGatewayEndpoint

Linux on z/OS linux-s390 Tivoli serverManaged nodeGatewayEndpoint

Solaris solaris2 Tivoli serverManaged nodeGatewayEndpoint

Windows 98 win95 Endpoint

Windows XP w32-ix86 Endpoint

Windows NTWindows 2000

w32-ix86 Tivoli serverManaged nodeGatewayEndpoint

If your Tivoli region contains tier 2 operating systems, you might encounter theinterpreter types listed in the following table. This is not a comprehensive list oftier 2 operating systems. To determine whether an unlisted operating system issupported, contact your IBM support provider.

Interpreter type Operating system and hardware

dgux5 DG Aviion / SVR4

dgux5-ix86 DG Aviion / Intel


Interpreter type Operating system and hardware

mips-irix5 SGI Mips IRIX 5

mips-reliant Pyramid MIServer ES

nextstep-ix86 i486™ / NEXTSTEP

osf-axp Tru64 UNIX(Compaq Alpha / OSF1)

reliant-unix Pyramid/SNI Reliant UNIX

sequent Sequent/Dynix/ptx

solaris-ix86 Solaris on Intel

sysv4-att AT&T 3000 / SVR4

sysv4-m88k Motorola 88k / SVR4

uw2-ix86 i486 / UnixWare

u6000_svr4mp Unisys / SVR4MP


Chapter 3. Software limitations, problems and workarounds

This chapter contains the software limitations, problems, and workarounds forTivoli Management Framework, Version 4.1 in English locales. For informationabout limitations and problems for Tivoli Management Framework, Version 4.1 innon-English locales, see Chapter 5, “Internationalization notes” on page 47.

LimitationsThis section contains the known software limitations for Tivoli ManagementFramework, Version 4.1.v Defect 117517: Tivoli Software Installation Service does not adhere to specified

port range restrictions.v Defect 136410: The installation of a Tivoli server or managed node on a UNIX

system creates a special account under which Tivoli operations run. Theseaccount differ by operating system. Ensure that the /etc/passwd file on thesystem has one of the following accounts defined:

For AIXnobody:*:4294967294:4294967294::/:

For HP-UXtmersrvd:*:59999:59999:Reserved forTME:/:/bin/false

For Solarisnobody:*:60001:60001::/:

When this account does not exist, Tivoli Management Framework randomlyselects an account ID under which it runs required operations. As a rule, TivoliManagement Framework selects an account ID high enough so that conflicts donot occur. To ensure that these conflicts do not arise, add the appropriate line tothe /etc/passwd file.

v Defect 149475: Because of potential user-customizations to the Tivoli desktop,upgrading to Tivoli Management Framework, Version 4.1, on UNIX operatingsystems does not use logos as a new installation of Tivoli ManagementFramework, Version 4.1. In upgrade situations, the desktop shows the olderTivoli logo and does not show the IBM logo. New installations show the newlogos.

v For shell scripts to run on Windows endpoints, you must place a dependency onsh.exe on the run_task method of the TaskEndpoint object. The dependencycauses sh.exe to be downloaded when a task is run on a Windows endpoint, if itis not already there. Follow these steps to define the dependency:1. Get the object ID (OID) of the current dependency set (if any) associated

with the run_task method:wchdep -g Classes:TaskEndpoint run_task

2. Create the dependency:wdepset -c task-library-tool-base \-a w32-ix86 bin/w32-ix86/tools/sh.exe +a +p %TOOLS% \-a w32-ix86 bin/w32-ix86/tools/win32gnu.dll +a +p \%TOOLS%

3. If there is not an existing dependency set, associate the dependency with therun_task method on the TaskEndpoint object:


wchdep @Classes:TaskEndpoint \@DependencyMgr:task-library-tool-base run_task

If there is an existing dependency set, add a nested dependency set to theexisting dependency set:wdepset -e current_depset_OID \-a depset @DependencyMgr:task-library-tool-base

4. Synchronize the gateway’s method cache with the Tivoli server database:wgateway gateway dbcheck

where gateway is the name of your gateway.

Complete these steps for each gateway.

Known defects and workaroundsThis section lists current defects for Tivoli Management Framework, Version 4.1. Aworkaround, if known, is also described.

Endpoint and gatewaysv Defect 128718: The $LCF_DATDIR/updata directory is created when

allow_proxy_upcalls is set to TRUE.Workaround: To prevent the $LCF_DATDIR/updata directory from being createdeach time the endpoint starts, set filefree_upcalls=TRUE before settingallow_proxy_upcalls=TRUE.

v Defect 130738: When migrating an endpoint from a gateway with encryptionlevel NONE to a gateway with encryption level DES, you will receive errorswhen attempting a downcall.Workaround: After migrating the endpoint, run the wep set gateway –g gw_labelcommand. You do not need to run this command when the migration is betweengateways with the same encryption level.

v Defect 149821: Endpoints not at the 41000 level cannot log in to amulticast-enabled gateway.Workaround: Upgrade the endpoint to at least the 41000 level.

Endpoint installationv APAR IY33952: Unable to recognize NetWare server mapped drive.

Workaround: Novell provides Native File Access Pack (NFAP). Install NFAP onthe NetWare server using the vendor-supplied documentation.

v Defect 125080: Remote endpoint installation on a Windows XP system fails whenusing simple file sharing. For details, see the Microsoft Knowledge Base articleQ307874.Workaround: Perform the following procedure:1. From Windows Explorer, select Folder Options from the Tools menu.2. Select the View tab.3. Ensure that the Use simple file sharing (recommended) check box at the

bottom on the Advanced Setting list is not selected.v Defect 128142: Remote endpoint installation on Windows XP Professional

systems, which are not members of a domain, cannot be rebooted remotelywhen no one is logged on to the system.Workaround: Do one of the following:


– Add the system to a domain before starting the installation.– Log on to the system before starting the installation.– Do not reboot the system during the remote installation. Manually reboot it

manually after the installation completes.v Defect 148569: On UNIX operating systems, when you do not have authorization

to the $DBDIR directory and run the winstlcf command, the following error isdisplayed:Size of the encrypted password is zero.

Workaround: Perform one of the following procedures:– Run the winstlcf command as a user with full access to $DBDIR.– Modify the $BINDIR/bin/winstlcf script to use $TEMP instead of $DBDIR.

With any text editor, change line 28 (or around it) from:$DBDIR = $ENV{’DBDIR’};

to$DBDIR = $ENV{’TEMP’};

Before running the modified winstlcf command, set the $TEMP to /tmpusing the appropriate operating system command, like the followingcommand:export TEMP=/tmp

Multiplexed Distributionv Defect 142049: Windows 2000 operating systems have a Media Sense feature that

is enabled. If you disconnect the network cable for a multicast-enabled gateway,you need to restart that gateway after reconnecting the cable.

v Defect 148964: From a hub Tivoli region the wmcast –p command shows onlysuccessful operations.

NetWare gatewayv Defect 131865: When installing a NetWare gateway, you cannot use unattended

installation. You must install the NetWare gateway in interactive mode.v Defect 141352: On NetWare, bulk data transfer (BDT) and inter-object message

(IOM) channels do not adhere to the designated port range. Othercommunications involving the object dispatcher service (the oserv service)observe port range restrictions.

Object dispatcherv Defect 125485: The port range for an object dispatcher is not dynamically

updated when it is set or modified using the odadmin set_port_rangecommand.Workaround: After setting or modifying the port range, recycle the objectdispatcher using the odadmin reexec command.

Product installationv Defect 147350: When running the wuninst command to determine the list of

options to uninstall Tivoli Java Client Framework using the following commandwuninst JCF, the product is uninstalled from the entire Tivoli region instead ofshowing the list of options.

Chapter 3. Software limitations, problems and workarounds 37

v Defect 148129: When using Tivoli Management Framework or Tivoli SoftwareInstallation Service installation mechanisms to install any Tivoli Enterpriseapplication on Windows operating systems, you cannot specify a pathinstallation option that contains spaces.Workaround: Use the tilde (~) character to represent the directory in the path.For example, instead of specifying Program Files as part of the path, specifyprogra~1.

RIMv Defect 137533: Issues were discovered with HP-UX and Oracle 9i clients running

in internationalized environments. In these environments use the Oracle 8.0.6 or8.1.6 client. Additionally, the Oracle 9i client appears to work fine in Englishonly environments. In internationalized environments, the 9i clients should workproperly using the 8.0.6 or 8.1.6 code pages.

Serviceabilityv Defect 124682: The endpoint manager can now dump a stanza to the epmgr.log

file at defined intervals. The stanza contains a list of each type of endpoint loginand the number of attempted and successful logins for each type during the lastinterval. Use the wepmgr set stanza_interval command to change the number ofhours between each dump. The default is 12 hours.

v Defect 134658: The Tivoli tracing facility uses shared memory segments for tracechannels. Solaris systems, by default, restrict the size of shared segments to 1MB, but the tracing facility use shared segments of up to 10 MB.Workaround: To allow the Solaris system to create these shared segments, addthe following line to the /etc/system file to allow unlimited shared segments:set shmsys:shminfo_shmmax=0xffffffff

After adding this line, reboot the system. Other settings are possible, but a tracechannel cannot be larger than the maximum allowed by this statement.

Miscellaneousv Defect 129230: On UNIX operating systems, when using the spider HTTP service

and the network security is set to FORCE_SSL, logins from a Web browser fail.Workaround: Do not use the spider service to Web access. Use the whttpdcommand to forward HTTP requests to a configured third-party Web server. Foradditional information, see the Tivoli Enterprise Installation Guide and the TivoliManagement Framework Reference Manual.

v Defect 135580: After setting a resource as remote in connected Tivoli regions, theremote resources are not part of the output of the wlookup command.Workaround: Run the odadmin reexec all command and reissue the wlookupcommand.


Chapter 4. Documentation

The chapter contains changes to the Tivoli Management Framework documentationlibrary.

Changes affecting UNIX manual pages onlyThe following UNIX manual pages do not match the information in TivoliManagement Framework Reference Manual:

lcfd The values for the http_disable option are as follows:

0 Anyone can use a browser to reconfigure the endpoint. This is thedefault.

1 Anyone can use a browser to view the configuration data, but noone can use a browser to reconfigure the endpoint.

2 No one can use a browser to view or reconfigure the endpoint.

3 Everyone must provide authentication (user name and password)to view or reconfigure the endpoint.

To prevent denial-of-service attacks, the following options were added butare not documented in the manual pages:

recvDataNumAttempts=countSpecifies how many times to receive or attempt to receive data onthe current connection before closing the connection. The default is10.

recvDataQMaxNum=connectionsSpecifies how many connections to hold in the pending connectionqueue. A connection that is waiting for data is considered apending connection and is added to the queue. After this limit isreached, all additional connection attempts are rejected until apending connection is closed. The default is 50.

recvDataTimeout=secondsSpecifies how many seconds that a new connection waits forincoming data before requeuing the connection. If the pendingconnection is full, the connection request is rejected. The default is2.

odadminThe default for the set_allow_rconnect option is version_2, which is moresecure.

wcrtrim, wmvrim, wsetrimThe –t instance_name option is not documented. This option specifies thevalue of the DB2INSTANCE variable. This value is the name of thedatabase instance that was created.

wep The authorization required for using specific options of this command havechanged. To view status information, only user or admin is required.

wgatewayThe epupgrade_by_gateway option is not documented in the manualpages. This option upgrades any endpoint assigned to the specified


gateway during the normal login process. The default is FALSE for allgateways, except NetWare gateways. NetWare gateways cannot run thelogin_policy script without first defining a proxy managed node.

wmcastThe –p option is not documented in the manual pages. This option sends amulticast ping to each endpoint connected to the specified repeater.

wmdistThe –m option is not documented in the manual pages. This option liststhe messages for the distribution and uses the same suboptions as the –eoption.

The information in Tivoli Management Framework Reference Manual is the mostup-to-date information.

Changes affecting all reference informationThe following changes are not documented in Tivoli Management FrameworkReference Manual nor are they correctly reflected in the UNIX manual pages:

idlattr The authorization roles for the idlattr command are not documented. Theauthorization roles are as follows:v To get a value for an attribute: user, admin, senior, or superv To set a value for an attribute or to add an attribute: senior or super

lcfd The address_notif_retry_count keyword was added to the lcfd command.This keyword controls the number of times that the endpoint will retrysending its IP address to the gateway every address_notif_interval secondsbefore attempting to contact another gateway in its login interfaces list. Thedefault is 0. (APAR IY16086)

wadminep, wepupgdThe wadminep command references the wepupgdcli command, whichdoes not exist. This reference should be to the wepupgd command.

The wadminep and wepupgd commands state that if no upgrade_path isspecified, the image is pulled from the managing gateway for theendpoint. The image, however, is pulled from the managed node where thecommand was issued.

wcrtrim, wmvrim, wsetrimOn Windows operating systems when using the wcrtrim, wmvrim, orwsetrim commands, you must use one of the following formats whenspecifying a value for a path that contains spaces:v ″c:\Program Files\sqllib″v c:\progra~1\sqllib

If you do not enclose the value within double quotation marks (″) orinclude the tilde (~) in the path name, the parsing of these commandsthrows an error.

wcrttaskThe documentation for the wcrttask command is missing a cross-referenceto the wsettask command. (APAR IY34491)

wdtmstThe wdtmsg command options are incorrect in all documentation. Theoption for getting the desktop message is –g, and the option for setting thedesktop message is –s.


wenblschedThe –e option of the wenblsched command is not documented. Thisoption synchronizes the encryption level of scheduled jobs with anychanges to the encryption level of a Tivoli region done by the odadminset_encrypt_level command. Run the wenblsched –e commandimmediately after restarting all the managed nodes. (APAR IX81875,IY33267)

wep The following keyword values can be set using the wep set_configcommand and are recorded in the last.cfg file:

address_notif_retry_count=countThe number of times that the endpoint will retry sending its IPaddress to the gateway every address_notif_interval secondsbefore attempting to contact another gateway in its login interfaceslist. The default is 0.

fail_if_pref_port_busy=1 | 0Whether the endpoint should not start if its preferred endpointport is inaccessible.

1 Do not start if the port is unavailable

0 If the port is unavailable, fail over to an alternate port

The default is 0.

filefree_upcalls=TRUE | FALSEWhether consolidated upcalls write the upcall data to disk. Thissetting is valid only when allow_proxy_upcalls=TRUE. In thiscase, the default is to write the upcall data to disk. However, if youdo not want upcall data written to disk, you can setfilefree_upcalls=TRUE and all the upcall data is transferredthrough the wire. The default is FALSE.

preload_loc=locationThe location in which the methods preloaded on an S/390endpoint are stored.

upcall_retry_count=countThe number of attempts to retry on an upcall failure. The default is0.

wol_enable=[0 | 1]Whether the Network Interface Card (NIC) on the box supportswake-on-lan. Valid only for supported Windows and OS/2endpoints. The default is 0.

The output shown with several examples for the wep command areincorrect. The output shown for the login_mode and upgrade_modecharacteristics for the endpoint should match the keyword value. (APARIY28296)

wmdistThe documentation and usage statement for the wmdist are incorrect. Thecorrect information is as follows:v The documentation for the –B option is incorrect in the documentation

and usage statement. The correct syntax is as follows:wmdist [–f] [–A] –B repeater_name

Chapter 4. Documentation 41

v The documentation for the –c, –p, and –r options does not show supportfor canceling, pausing, and resuming distribution to select targets. Thesyntax is as follows:wmdist [–f] –c dist_id [endpoint_id ...]wmdist [–f] –p dist_id [endpoint_id...]wmdist [–f] –r dist_id [endpoint_id...]

v The documentation for the –e option shown the READY state. This stateis currently not used. (APAR IY34893)

v The documentation for the –j and –k options is missing, but shown inthe usage statement. The –j option adds the specified alternative depotdirectories. The –k option removes the specified alternative depotdirectories. The syntax is as follows:wmdist –j depot_directory...wmdist –k depot_directory...

v The usage statement shows the –K option. This option is the –A option.v The syntax shown for the –s option is incorrect in the documentation

and usage statement. The correct syntax is as follows:wmdist –s repeater_name [–C [noprompt | nostart | nostop]][keyword=value...]The –R [default | originalDefault] option, as shown in the usagestatement is not supported.

Changes affecting installation informationThe following changes are not documented in Tivoli Enterprise Installation Guide:v On Windows operating systems, the default installation directory is always a

subdirectory of the %SystemDrive%\Program Files directory. The documentationmight list other default installation directories.

v There is no information about uninstalling Linux endpoints.To uninstall Linux endpoints, assuming /opt/Tivoli/lcf as the defaultinstallation directory, perform the following steps:1. Stop the endpoint service using the lcfd.sh stop command.2. Remove the installation directory:

rm -r /opt/Tivoli/lcf/1

3. Remove the endpoint environment directory:rm -r /etc/Tivoli/lcf/1

4. Remove the /etc/Tivoli/*/userlink.htm file.5. Remove the following autostart files and symbolic links from the system, if

they exist:For Linux for Intel:– /etc/rc.d/init.d/lcfd1.rc– /etc/rc.d/init.d/lcfd1.sh– /etc/rc.d/init.d/Tivoli_lcfd1– /etc/rc.d/rc0.d/K10Tivoli_lcf1– /etc/rc.d/rc1.d/K10Tivoli_lcf1– /etc/rc.d/rc2.d/S99Tivoli_lcf1– /etc/rc.d/rc3.d/S99Tivoli_lcf1– /etc/rc.d/rc4.d/S99Tivoli_lcf1– /etc/rc.d/rc5.d/S99Tivoli_lcf1– /etc/rc.d/rc6.d/S99Tivoli_lcf1


For SuSE (Intel and S/390):– /etc/rc.d/init.d/Tivoli_lcfd1– /etc/rc.d/rc2.d/K10Tivoli_lcf1– /etc/rc.d/rc2.d/S99Tivoli_lcf1– /etc/rc.d/rc3.d/K10Tivoli_lcf1– /etc/rc.d/rc3.d/S99Tivoli_lcf1– /etc/rc.d/rc4.d/K10Tivoli_lcf1– /etc/rc.d/rc4.d/S99Tivoli_lcf1– /etc/rc.d/rc5.d/K10Tivoli_lcf1– /etc/rc.d/rc5.d/S99Tivoli_lcf1

Changes affecting task informationThe following changes are not documented in Tivoli Management Framework User’sGuide:v APAR IY33440: The authorization roles required to subscribe resources to a

profile manager is admin in the following contexts:– The policy region of the profile manager– The policy region of the subscriber

If the administrator does not have the admin authorization role in both of thesepolicy regions, the subscription will fail.

Changes to firewall documentationThe following information and changes are not documented in Tivoli ManagementFramework Firewall Security Toolbox User’s Guide.v In Chapter 3, ″Configuring the Component,″ add the following text to step 2 of

the ″Configuring Backup Gateway Proxies″ procedure:

The gateway-port keyword must be the same for all gateway proxies thatare listed in the same group in the proxy.grp file. Otherwise, the gatewayproxy failover will not work for that group.

v In Chapter 3, ″Configuring the Components,″ the following changes are notdocumented in the ″Configuring Endpoints for Backup Gateway Proxies″section:

If in a Tivoli region there are some endpoints that connect directly to agateway, because there is no firewall between them, and some endpointsthat connect through Firewall Security Toolbox, the login_policy scriptreferred to in Tivoli Management Framework Firewall Security Toolbox User’sGuide must be run only for the endpoints that connect through FirewallSecurity Toolbox. This keeps endpoints that connect directly to a gatewayfrom trying to connect through Firewall Security Toolbox.

To understand whether the endpoint is logging in through FirewallSecurity Toolbox, use the login_policy script in one of the following ways:– Check the $5 value, the IP address of the endpoint. If the IP address is

the same as that of the endpoint proxy, the endpoint is logging inthrough the Firewall Security Toolbox.

– Reserve one gateway in the Tivoli region to log in endpoints throughFirewall Security Toolbox. Check the $4 value, the object reference of thegateway that intercepted the login request from the endpoint. If thevalue is the same as that of the reserved gateway, the endpoint islogging in through Firewall Security Toolbox.


– Use a naming convention for endpoint labels that identifies onlyendpoints that log in through Firewall Security Toolbox. Check the $1value, the endpoint label. If the value matches the naming convention,the endpoint is logging in through Firewall Security Toolbox.

v Add the topic, ″Thread Shortage on UNIX operating systems″ to thetroubleshooting appendix.Problem: On UNIX operating systems, if the number of threads that can becreated simultaneously by a process is less than the number of threads neededby a particular Firewall Security Toolbox component, the component might failto start correctly, stop running, or be unable to perform all its expectedoperations. For example, HP-UX systems have a default value of 64 for themax_thread_proc kernel parameter. This means that a process can run amaximum of 64 threads simultaneously.The following message is logged when a Firewall Security Toolbox componentruns out of threads:

runThread - pthread_create() failed (e=error_number) unable tocreate thread, currently working threads number_of_threads

where:

error_numberIs the error number describing why the thread was not created.

number_of_threadsIndicates how many threads were running simultaneously when thethread failed to be created.

Solution: Increase the number of simultaneous threads allowed per process. Thenumber of required threads depends on the component. The following formulascan help you determine the maximum number of threads needed to ensure thatthe Firewall Security Toolbox component works:

On the endpoint proxy, relay, or gateway proxythread_number = (number_of_endpoints x 4 + 10) x 1.25

where:

thread_numberIs the number of threads required by the component.

number_of_endpointsThe total number of endpoints that connect through thecomponent. For example, if 500 endpoints connect through 2gateway proxies to the same endpoint proxy, the number ofendpoints value is 1000.

On the event sinkthread_number = (max-sessions + 10) x 1.25

where:

thread_numberIs the number of threads required by the component.

max-sessionsIs the max-sessions value that you specify when you configurethe event sink in the RECEPTION section.


These formulas ensure that the components work when they are operatingunder conditions of maximum workload. For example, if you there are 100endpoints for one endpoint proxy, the thread number indicates the maximumnumber of threads required if all the endpoints are sending downcalls andupcalls at the same time.

To understand how to increase the number of threads per process, see thedocumentation for the UNIX operating system installed on the system.



Chapter 5. Internationalization notes

Tivoli Management Framework and Tivoli Software Installation Service aretranslated in the following languages:v Brazilian Portuguesev Chinese (Simplified)v Chinese (Traditional)v Frenchv Germanv Italianv Japanesev Koreanv Spanish

In this release, non-English characters are not supported for host names and hostlabels. For some locales, using non-English characters, including DBCS characters,can cause problems when specifying:v User and group namesv Passwordsv File, directory, and object names

If you have a problem in one of these areas, avoid using non-English characters. Ingeneral, the following limitations apply to object names (labels) for Tivoliresources:v The label can include any alphanumeric charactersv The label can include underscores (_), hyphens (-), a period (.), and spaces.

Installation and upgrade notes

Enabling language supportTo enable these languages, you must install their language support components.Each Tivoli Enterprise product has its own language support CD. To fully enableadditional languages, you must install the Tivoli Management Frameworklanguage support component as well as the language support component for eachTivoli Enterprise product in your Tivoli environment.

Note: If your Tivoli environment contains Tivoli Enterprise applications that useboth Java Client Framework, Version 4.1, and Java Client Framework,Version 3.7.x, you must install the language packs for both versions. If onlythe language pack for Version 3.7.x is installed, the text for the OK andCancel buttons are not found and error messages are used for the buttontext.

Installing language support now follows the procedure for installing any TivoliEnterprise product. Refer to the Tivoli Enterprise Installation Guide for instructionsfor installing products and for information about setting up a non-English systemenvironment.


System requirements for Asian environmentsThis section provides information about system requirements for using TivoliManagement Framework in Asian environments. These notes supplement thegeneral system requirements in “System requirements” on page 16.

Java requirementsOn AIX 4.3.3 or AIX 5.1 operating systems in a non-UTF8 CKJ locale, either installFixpack10 or individually install the following listed filesets:v X11.fnt.fontserver 4.3.3.12v X11.fnt.ucs.ttf (for ja_JP or Ja_JP)v X11.fnt.ucs.ttf_CN 4.3.3.1 (for zh_CN or Zh_CN)v X11.fnt.ucs.ttf_KR (for ko_KR)v X11.motif.lib 5.1.0.15 (for ja_JP or Ja_JP AIX 5.1 users)v X11.fnt.ucs.ttf_TW (for zh_TW or Zh_TW)v jkit.Wnn6.base 2.1.1.5 (for ja_JP or Ja_JP Wnn6 users)v bos.loc.com.JP 4.3.3.11 (for ja_JP or Ja_JP)v bos.loc.utf.ZH_TW 4.3.3.11 (for zh_TW or Zh_TW)v devices.rsa_sio.baud.rte 4.3.2.1

These fixes are required by IBM AIX Developer Kit, Java 2 Technology Edition,Version 1.3.0. If these filesets are not installed, they can be found on the AIX 4.3.3installation media, or you can use the FixDist tool available from the followingWeb site:http://techsupport.services.ibm.com/rs6000/support

Endpoint notesv Japanese OS/2 4.0 requires FixPaks WX02204 and FX00001.v Korean OS/2 4.0 requires patch kjr11660.zip, which can be downloaded from

ftp:/service.boulder.ibm.com/.

Note: After connecting to this site, navigate tops/products/os2/fixes/v4warp/korean. Review the README file in thisdirectory.

v Traditional Chinese OS/2 4.0 requires FixPak 30.

NEC PC98 systemsThe following sections list system requirements and supported operating systemsfor NEC PC98. The NEC PC98 system hardware is usually sold only in Japan.

Endpoints on NEC PC98xx: The Tivoli endpoint is supported on PC98xx systemsrunning the following operating systems:v Microsoft Windows 98Jv Microsoft Windows 4.0J with Service Pack 4

The following table shows the NEC PC9800 models supported for TivoliManagement Framework, Version 4.1.

PC9800 Series Family Name Model Name

Aile PC9821LA13S14R

La Vie PC9821NR150/S20


PC9800 Series Family Name Model Name

MATE PC9821XA200W30R

PC9821RA266M30R

MATE X PC9821Xc16

PC9821Xa20

VALUESTAR PC9821V200/S5 model D3

Endpoints on NEC PC98NX: The Tivoli endpoint is supported on PC98NXsystems running the following operating systems:v Microsoft Windows 98Jv Microsoft Windows 4.0J with Service Pack 4

The following table shows the NEC PC98NX models supported for TivoliManagement Framework, Version 4.1.

NX Series Family Name Model Name

Aile NX AL20C/TS model AAF1

La Vie NX LW20/32A

MATE NX IMA35D/S5 model BAC42

IMA26D/C5 model ATC42

VALUESTAR VC33/47C

VS30/35D

VersaPro NX VA23C/WX model BAB33

Cantonese ChineseThis version of Tivoli Management Framework does not handle the 3,000 uniqueCantonese characters because these characters are not part of Unicode.

Microsoft Windows NT Workstation Pan Chinese 4.00.1381 is supported.

Software limitations, problems, and workaroundsv A Tivoli region might not fully support operating in more than one language.v Some text in the Tivoli desktop is not translated.v In some cases, English text, resource names, resource types, and roles are not

fully translated.v Usage statements for some commands are not fully translated.v Manual pages on all UNIX operating systems are not translated.v For Tivoli Desktop for Windows to work in any Spanish locale, the Regional

Setting Properties must be set to Spanish (Traditional). When set to any otherSpanish setting in the Regional Setting Properties dialog, the login dialog isdisplayed in English.

v Defect 97676: The UserLink HTML page is in English.v Defect 115491: The gateway and status Web pages are not enabled.v Defect 114995: The odadmin info all command returns a date that is not

localized.v Defect 115291: For some locales, the string not found window is truncated on the

top.

Chapter 5. Internationalization notes 49

v Defect 136125: For AIX5L operating systems in the Chinese EUC locale, theTivoli desktop panels display text incorrectly.Workaround: Install the patch bos.rte 5.1.0.25.

v Defect 146385: Although the panels displayed during the installation of theTivoli server on Windows operating systems is locale-specific, the informationdisplayed in command windows is in English.

v Defect 147967: In a DBCS system, the Path name field on the Set Path to TivoliInstall Media windows might be blank. Even when you type a valid path, it isnot updated and you receive an error message.Workaround: This problem is due to inappropriate fonts on the X Windowssystem used to display the Tivoli desktop. To get the list of available fonts, usethe xlsfonts command. From this list, you can get an available font to displayyour language.To specify a different font when starting the Tivoli desktop, enter the followingcommand:tivoli -fn font

Alternatively, you can override the resource files by entering the followingcommand:tivoli -xrm "*fontList: font:font"

If you do not want to pass parameters, you can create a command alias or aresource file by performing the following steps:1. Set the Tivoli environment variables:

. /etc/Tivoli/setup_env.sh

2. Get the value for the XUSERFILESEARCHPATH variable:echo $XUSERFILESEARCHPATH

This value shows a directory like /usr/lib/X11/app-defaults/%L/%N.3. Replace %L with $LANG, and replace %N with Tivoli.4. Add an entry with the font pattern you want to use to the

/usr/lib/X11/app-defaults/$LANG/Tivoli file in the format:"*fontList: font:font"

To use with more than one language, add your entry to the/usr/X11R6/lib/X11/app-defaults/Tivoli file.


��

Part Number: CT1CWIE

Printed in U.S.A.

GI11-0890-00

(1P)

P/N:

CT1CWIE

Documents

Tivoli Management Framework: Release Notespublib.boulder.ibm.com/tividd/td/framework/GI11... · evaluation and verification of operation in conjunction with other products, except