IBM License Metric Tool: Readme file for Fix Pack 7.2.1

IBM License Metric Tool

Readme file for Fix Pack7.2.1-TIV-ILMT-FP0002

��

IBM License Metric Tool

Readme file for Fix Pack7.2.1-TIV-ILMT-FP0002

��

Note

This edition applies to IBM License Metric Tool (program number 5724LMT00) and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2002, 2011.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Readme file . . . . . . . . . . . . . 1

Notices . . . . . . . . . . . . . . . 9

Trademarks . . . . . . . . . . . . . . 10

Index . . . . . . . . . . . . . . . 13

© Copyright IBM Corp. 2002, 2011 iii

iv IBM License Metric Tool: Readme file for Fix Pack 7.2.1-TIV-ILMT-FP0002

Readme file

Known issues for IBM® License Metric Tool 7.2.1 Fix Pack 2 are addressed in thisdocument.

Contents:

v Descriptionv Summary of changesv APARS fixedv System requirementsv Installing the fix pack

– On embedded WebSphere® Application Server– On base version of WebSphere Application Server

v Reverting to the previous version

Description

This readme provides important information about the 7.2.1-TIV-ILMT-FP0002 fixpack for License Metric Tool version 7.2.1. It contains the most current informationfor the fix pack and takes precedence over all other documentation.

Please review this readme thoroughly before installing or using the fix pack!

The License Metric Tool 7.2.1.2 information center can be found at the followingaddress: http://publib.boulder.ibm.com/infocenter/lmt/v7r2m1/topic/com.ibm.license.mgmt.doc/ic-homepage_lmt.html

Summary of changes

The list summarizes the changes introduced by the fix pack:v New Common Inventory Technology packaged with agent installer (2.7.0.0009

build 2011/09/22).

For more information, see http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/IBM_License_Metric_Tool

APARs fixed

The following table lists the APARs that are fixed in the fix pack:

APAR Abstract Description

IZ99671 IN RED HAT LINUX 6,/USR/BIN/KSH IS NOLONGER LINKED TO/BIN/KSH

The agent installation scriptsassumed that the ksh binarywas located in /bin/ksh,which is no longer true forRed Hat Linux 6. Scriptswere reworked to usebinary's root location, whichis /usr/bin/ksh.

© Copyright IBM Corp. 2002, 2011 1

http://publib.boulder.ibm.com/infocenter/lmt/v7r2m1/topic/com.ibm.license.mgmt.doc/ic-homepage_lmt.html

http://publib.boulder.ibm.com/infocenter/lmt/v7r2m1/topic/com.ibm.license.mgmt.doc/ic-homepage_lmt.html

http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/IBM_License_Metric_Tool

http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/IBM_License_Metric_Tool


IZ99484 WHEN AGENT PROCESS ISDROPPED FROM SERVICEMANAGER ON AIX® IT

Multiple tlmagent processescould be triggered on AIX ifthe system resourcecontroller registry wascorrupted. With this fix,excessive tlmagent processesare removed when anytlmagent command is run,for example tlmagent -p ortlmagent -reload.

IZ99395 measure with metric 13 notcreated by VM-manager

In some cases, a VMmanager does not insert allmeasures for the managedVM-Layer. The logic behindretrieving the data from theVM managers has beenimproved to correctly handleall the cases.

IZ97699 PATHS IN EXTENDEDSIGNATURES IGNORED BYTHE AGENT

The agent was not readingthe INSTALL_PATH variablefrom the software scanoutput for signaturesdifferent than file signatures.This behavior caused themulti-instance monitoring tobe disabled for a givencomponent even if all thesignatures found for thiscomponent returned pathscorrectly.

IZ97553 ERROR EXECUTING VMMANAGER CONNECTORTASK

The VM manager task failswith NullPointerException.The exception was caused bythe empty/null datareturned by VMWare SDK,which is the case when thereare no virtual machinescreated or the user does nothave read privileges to anyof the already existing virtualmachines.

IZ97315 agents in INCOMPLETEstate

The data in the database wasnot always correctly updatedduring the VM managerconnection task, whichresulted in an incompleteagent status.

IZ97134 REMOTE/LOCAL SERVERTIMESTAMPSMISALIGNMENT

The agent used Windowsperformance counters tomeasure time. According toMicrosoft, these counters arenot accurate onmultiprocessor machines.The code has been reworkedso as not to use performancecounters.

2 IBM License Metric Tool: Readme file for Fix Pack 7.2.1-TIV-ILMT-FP0002


IZ96882 SOLARIS9, TLMAGENT -GGIVES ERROR "NOLIBGSK7ICCS_64.SO"

Upon agent startup, the pathenvironment variable on64-bit Solaris was setincorrectly.

IZ96567 AGGREGATION ANDRECALCULATIONSYNCHRONIZATION ISSUE

Two main background tasks- aggregation andrecalculation were incorrectlysynchronized which couldcause one of the processes toget insufficient resources tostart. The task prioritizationwas optimized so that theaggregation process has ahigher priority thanrecalculation.

IZ96426 PERIODIC SELF-UPDATEPROCESS NOT WORKINGAS DESIGNED

The agent did not update inthe expected time theinformation about the factthat the periodic updateoption has been chosen.

IZ92844 LMT failed to collect datafrom HyperV Virtualmachine.

When retrieving data fromthe Hyper-V VM manager,the data can be sent byHyper-V in chunks and notin one packet. This situationwas not correctly handled bythe administration server andso the data receiving processfailed.

IZ92266 DEADLOCK ERROENCOUNTEREDCODDB3021E ANDCODUI7003E

The logic for retrieving datafrom the database to bedisplayed on the server UIpanels was in conflict withother server tasks that weretrying to manipulate thesame data in the database.The problem was fixed bychanging the isolation levelfor retrieving data for UIpurposes for the panelswhere the process is done inthe read only mode.

IZ91257 CODCL7053E WHENATTEMPTING IMPORT PVU

The PVU table importprocess was failing in aspecific situation.

IZ91253 Not all product - pidsrelations are being imported

The software catalog importprocess was skipping PIDdetails for particular softwareproducts. Once this fix isdeployed, a new softwarecatalog has to be imported topopulate the missing PIDs indatabase.

Readme file 3


IZ89741 CLICKING ONSTH_CLUSTER DEV TAKESTO STH_CLUSTER DEVNEW

Due to a defect in the codeof the web UI, in somespecific cases incorrect panelswere opened.

IZ89531 Wrong capacity for barematel with BIOS limit

In the case when the numberof logical processors wasbigger than the number ofphysical cores on thephysical machine withoutany virtualization, themachine subcapacity was setaccording to the number oflogical processors instead ofthe number of physicalprocessor cores. This couldonly happen on the x86physical server with novirtualization.

IZ84436 WRONG PVU VALUE FOR5570 NEHALEMPROCESSORS

On 5570 Nehalem processors,the Common InventoryTechnology component wasincorrectly identifying theprocessor type. Thecomponent shipped with thisfix pack recognizes itcorrectly.

IZ83568 deadlocks onLIC.RES_GROUP_REL table

In large environments, thedatabase deadlocks werecaused by the msghandlerserver services interferingwith one another. Thedatabase locking logic wasadjusted to minimize thepossibility of deadlocks.

IZ83402 GETTING EMAILS SAYINGSCANS FAILED WHENTHEY WERE INDEED

The email notification wassent not only when agentshad the missing scan statusbut also when the scan statuswas pending, meaning thatthe server was still waitingfor the scan to be sent froman agent. This was notcorrect since the pendingstatus of a software scan isnot an error or a warningbut simply just aninformation. This logic waschanged to send notificationsonly in case when agentshave the missing scan status.

IZ76600 NOT SYNCHRONIZEDADM.PROD_INV.LINK_IDWITH ADM.LINK TABLE

In specific cases, recordsfrom the ADM.LINK table weredeleted withoutsynchronizing related recordsin the ADM.PROD_INV table.



IZ72360 Add START_MSG andSTOP_MSG to tlm script onHP

The agent service startupscript for the HP platformwas not fully compliant withthe guidelines for this typeof scripts. It resulted inwarning messages whilestarting or stopping theagent service. The script hasbeen modified to conform tothe standard.

IV08405 NO INSTANCES OF THESELECTED PRODUCTS

The query on retrievinginstances of unconfirmedproducts used an inaccuratedata source.

IV04363 TEST CONNECTION FORHYPER-V SERVER FAILS.

Test connection for theHyper-V server fails whennon-English version of theHyper-V system is beingused.

IV01721 NullPointerException duringcommunication withHyper-V

NullPointerException wasthrown from theModelObjectFactory.getHostGuests methodduring the communicationwith Hyper-V.

IV01435 ILMT FAILS TO COLLECTINFORMATION ABOUTHYPER-V CLUSTER

The administration serverattempts to reach allHyper-V nodes from thecluster but failing in casewhen the private network forthe cluster heartbeat wasdefined.

IV01065 AGENTS AREPERFORMING ASELF-UPDATE EVEN ifdisabled

In some cases, an agent wasscheduling the self-updateeven if it was not enabled onthe server side. Thisphenomenon took place onlyin very specificcircumstances (SSL protocolused, threads race conditionpresent, key databasewithout agent's certificate forthe server authentication)and heavily depended on theserver's hardware andoperating system.

IV00719 Automatic report generationissue

In some cases, automaticgeneration of PVU reportswas failing and reports werenot generated. This wascaused by a defect in thereport generation logic onthe server side.

System requirements

Readme file 5

For more information about hardware and software compatibility, see the Installingsection of the information center.

Installing the fix pack

Read the following instructions to learn how to install the fix pack. Once youinstall the fix pack, you cannot uninstall it automatically. For details of how torevert to the previous version, see Reverting to the previous version.

The fix pack includes the following files:

The package for the server deployment on the base version of WebSphereApplication Server:v 7.2.1-TIV-ILMT-FP0002-server-WAS-Base.zip

The packages for the server deployment on embedded WebSphere ApplicationServer:v 7.2.1-TIV-ILMT-FP0002-server-aix-ppc64.zip

v 7.2.1-TIV-ILMT-FP0002-server-hpux-parisc.zip

v 7.2.1-TIV-ILMT-FP0002-server-linux-ppc64.zip

v 7.2.1-TIV-ILMT-FP0002-server-linux-s390_64.zip

v 7.2.1-TIV-ILMT-FP0002-server-linux-x86_32.zip

v 7.2.1-TIV-ILMT-FP0002-server-linux-x86_64.zip

v 7.2.1-TIV-ILMT-FP0002-server-solaris-sparc64.zip

v 7.2.1-TIV-ILMT-FP0002-server-windows-x86_32.zip

v 7.2.1-TIV-ILMT-FP0002-server-windows-x86_64.zip

Native agent installers:v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-aix-ppc.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-hpux.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-i5os.zip

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-linux-ppc.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-linux-s390.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-linux-x86.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-solaris-sparc32.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-solaris-sparc64.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-solaris-x86_64.tar.gz

v 7.2.1-TIV-ILMT-TAD4D-FP0002-agent-windows-x86.zip

SPB based agent installers:v 7.2.1-TIV-ILMT-TAD4D-FP0002-SPB.zip

The fix pack must be applied only to the License Metric Tool 7.2.1 servercomponent. It is not required to patch the database component. If the server is inthe older version, upgrade the server to 7.2.1 level first. It is not possible to installthe administration server using only the fix pack installation file. For moreinformation about installing the server, see the Installing section of the informationcenter.


Important: Before you apply the fix pack, make sure that there is enough spaceavailable in the directory where the administration server is installed. The fix packrequires the additional amount of 520MB during the installation.

Note: During the installation of the fix pack on the administration server, thescript stops and starts the server. If the server is running in a WebSphereApplication Server secure cell, you are asked to provide the user ID and passwordfor the secure cell. Ensure that you have this information before you start.

To install the fix pack on embedded WebSphere Application Server (or to upgradethe database component only), complete the following steps:1. Log on to the computer where the administration server is installed as

Administrator (on Windows) or root (on UNIX).2. Unpack the fix pack file into a temporary directory.3. Launch the installer file for the platform on which you are installing the fix

pack. The file is a script with the following naming convention:7.2.1-TIV-ILMT-FP0002-server<PLATFORM_NAME>.[bat|sh].The installation script starts.

Note: No license agreement is displayed. The fix pack is subject to the sameterms and conditions under which License Metric Tool is licensed.

4. Specify a directory where the wizard can create a backup of your serverconfiguration and other files that are affected by the fix pack, and click Next.

Note: The space required for the backup may vary, depending on the platformon which the administration server is installed, but typically the backuprequires 520MB of disk space.

5. The installer patches your product to fix pack level 2. This is a fully automatedstep.

6. When the installation is complete and you get the confirmation message, clickNext to exit the wizard.

To install the fix pack on the base version of WebSphere Application Server,perform the following steps:1. Stop the server.2. Locate and back up the following directories:

a. <WEBSPHERE_INSTALLATION_PATH>/profiles/<PROFILE_NAME>/installedApps/<CELL_NAME>/LMT-TAD4D_Agent_message_handler.ear/com.ibm.license.mgmt.msghandler.web.war

b. <WEBSPHERE_INSTALLATION_PATH>/systemApps/isclite.ear/lmt_admin.war

3. Overwrite the files listed above with the ones in the 7.2.1-TIV-ILMT-FP0002-server-WAS-Base.zip archive.

4. Start the server.5. Open the server web UI and browse to the About page to verify if the reported

product version is 7.2.1.2 (7.2.1 Fix Pack 2).

Reverting to the previous version

There is no automatic method for uninstalling this fix pack. You must roll back thechanges on each computer with the installed fix pack.

To uninstall the fix pack from the administration server:

Readme file 7

1. Stop the server.2. Restore the files that were backed up before applying the fix pack.3. Restart the server.

To uninstall the fix pack from an agent:v Uninstall the agent.v Install the previous version of the agent.


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 79758 U.S.A

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

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


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Notices 11


Index



��

Printed in USA

Documents

IBM License Metric Tool: Readme file for Fix Pack 7.2.1