IBM License Metric Tool. Readme file for Fix Pack TIV-ILMT-FP0002

Transcription

1 IBM License Metric Tool Readme file for Fix Pack TIV-ILMT-FP0002

2

3 IBM License Metric Tool Readme file for Fix Pack TIV-ILMT-FP0002

4 Note This edition applies to IBM License Metric Tool (program number 5724LMT00) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2002, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Readme file Notices Trademarks Index Copyright IBM Corp. 2002, 2011 iii

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

7 Readme file Known issues for IBM License Metric Tool Fix Pack 2 are addressed in this document. Contents: v Description v Summary of changes v APARS fixed v System requirements v 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 TIV-ILMT-FP0002 fix pack for License Metric Tool version It contains the most current information for 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 information center can be found at the following address: 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 ( build 2011/09/22). For more information, see 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 NO LONGER LINKED TO /BIN/KSH The agent installation scripts assumed that the ksh binary was located in /bin/ksh, which is no longer true for Red Hat Linux 6. Scripts were reworked to use binary's root location, which is /usr/bin/ksh. Copyright IBM Corp. 2002,

8 APAR Abstract Description IZ99484 WHEN AGENT PROCESS IS DROPPED FROM SERVICE MANAGER ON AIX IT Multiple tlmagent processes could be triggered on AIX if the system resource controller registry was corrupted. With this fix, excessive tlmagent processes are removed when any tlmagent command is run, for example tlmagent -p or tlmagent -reload. IZ99395 IZ97699 IZ97553 IZ97315 IZ97134 measure with metric 13 not created by VM-manager PATHS IN EXTENDED SIGNATURES IGNORED BY THE AGENT ERROR EXECUTING VM MANAGER CONNECTOR TASK agents in INCOMPLETE state REMOTE/LOCAL SERVER TIMESTAMPS MISALIGNMENT In some cases, a VM manager does not insert all measures for the managed VM-Layer. The logic behind retrieving the data from the VM managers has been improved to correctly handle all the cases. The agent was not reading the INSTALL_PATH variable from the software scan output for signatures different than file signatures. This behavior caused the multi-instance monitoring to be disabled for a given component even if all the signatures found for this component returned paths correctly. The VM manager task fails with NullPointerException. The exception was caused by the empty/null data returned by VMWare SDK, which is the case when there are no virtual machines created or the user does not have read privileges to any of the already existing virtual machines. The data in the database was not always correctly updated during the VM manager connection task, which resulted in an incomplete agent status. The agent used Windows performance counters to measure time. According to Microsoft, these counters are not accurate on multiprocessor machines. The code has been reworked so as not to use performance counters. 2 IBM License Metric Tool: Readme file for Fix Pack TIV-ILMT-FP0002

9 APAR Abstract Description IZ96882 SOLARIS9, TLMAGENT -G GIVES ERROR "NO LIBGSK7ICCS_64.SO" IZ96567 IZ96426 IZ92844 IZ92266 IZ91257 IZ91253 AGGREGATION AND RECALCULATION SYNCHRONIZATION ISSUE PERIODIC SELF-UPDATE PROCESS NOT WORKING AS DESIGNED LMT failed to collect data from HyperV Virtual machine. DEADLOCK ERRO ENCOUNTERED CODDB3021E AND CODUI7003E CODCL7053E WHEN ATTEMPTING IMPORT PVU Not all product - pids relations are being imported Upon agent startup, the path environment variable on 64-bit Solaris was set incorrectly. Two main background tasks - aggregation and recalculation were incorrectly synchronized which could cause one of the processes to get insufficient resources to start. The task prioritization was optimized so that the aggregation process has a higher priority than recalculation. The agent did not update in the expected time the information about the fact that the periodic update option has been chosen. When retrieving data from the Hyper-V VM manager, the data can be sent by Hyper-V in chunks and not in one packet. This situation was not correctly handled by the administration server and so the data receiving process failed. The logic for retrieving data from the database to be displayed on the server UI panels was in conflict with other server tasks that were trying to manipulate the same data in the database. The problem was fixed by changing the isolation level for retrieving data for UI purposes for the panels where the process is done in the read only mode. The PVU table import process was failing in a specific situation. The software catalog import process was skipping PID details for particular software products. Once this fix is deployed, a new software catalog has to be imported to populate the missing PIDs in database. Readme file 3

10 APAR Abstract Description IZ89741 CLICKING ON STH_CLUSTER DEV TAKES TO STH_CLUSTER DEV NEW Due to a defect in the code of the web UI, in some specific cases incorrect panels were opened. IZ89531 IZ84436 IZ83568 IZ83402 IZ76600 Wrong capacity for bare matel with BIOS limit WRONG PVU VALUE FOR 5570 NEHALEM PROCESSORS deadlocks on LIC.RES_GROUP_REL table GETTING S SAYING SCANS FAILED WHEN THEY WERE INDEED NOT SYNCHRONIZED ADM.PROD_INV.LINK_ID WITH ADM.LINK TABLE In the case when the number of logical processors was bigger than the number of physical cores on the physical machine without any virtualization, the machine subcapacity was set according to the number of logical processors instead of the number of physical processor cores. This could only happen on the x86 physical server with no virtualization. On 5570 Nehalem processors, the Common Inventory Technology component was incorrectly identifying the processor type. The component shipped with this fix pack recognizes it correctly. In large environments, the database deadlocks were caused by the msghandler server services interfering with one another. The database locking logic was adjusted to minimize the possibility of deadlocks. The notification was sent not only when agents had the missing scan status but also when the scan status was pending, meaning that the server was still waiting for the scan to be sent from an agent. This was not correct since the pending status of a software scan is not an error or a warning but simply just an information. This logic was changed to send notifications only in case when agents have the missing scan status. In specific cases, records from the ADM.LINK table were deleted without synchronizing related records in the ADM.PROD_INV table. 4 IBM License Metric Tool: Readme file for Fix Pack TIV-ILMT-FP0002

11 APAR Abstract Description IZ72360 Add START_MSG and STOP_MSG to tlm script on HP The agent service startup script for the HP platform was not fully compliant with the guidelines for this type of scripts. It resulted in warning messages while starting or stopping the agent service. The script has been modified to conform to the standard. IV08405 IV04363 IV01721 IV01435 IV01065 IV00719 NO INSTANCES OF THE SELECTED PRODUCTS TEST CONNECTION FOR HYPER-V SERVER FAILS. NullPointerException during communication with Hyper-V ILMT FAILS TO COLLECT INFORMATION ABOUT HYPER-V CLUSTER AGENTS ARE PERFORMING A SELF-UPDATE EVEN if disabled Automatic report generation issue The query on retrieving instances of unconfirmed products used an inaccurate data source. Test connection for the Hyper-V server fails when non-english version of the Hyper-V system is being used. NullPointerException was thrown from the ModelObjectFactory. gethostguests method during the communication with Hyper-V. The administration server attempts to reach all Hyper-V nodes from the cluster but failing in case when the private network for the cluster heartbeat was defined. In some cases, an agent was scheduling the self-update even if it was not enabled on the server side. This phenomenon took place only in very specific circumstances (SSL protocol used, threads race condition present, key database without agent's certificate for the server authentication) and heavily depended on the server's hardware and operating system. In some cases, automatic generation of PVU reports was failing and reports were not generated. This was caused by a defect in the report generation logic on the server side. System requirements Readme file 5

12 For more information about hardware and software compatibility, see the Installing section of the information center. Installing the fix pack Read the following instructions to learn how to install the fix pack. Once you install the fix pack, you cannot uninstall it automatically. For details of how to revert 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 WebSphere Application Server: v TIV-ILMT-FP0002-server-WAS-Base.zip The packages for the server deployment on embedded WebSphere Application Server: v TIV-ILMT-FP0002-server-aix-ppc64.zip v TIV-ILMT-FP0002-server-hpux-parisc.zip v TIV-ILMT-FP0002-server-linux-ppc64.zip v TIV-ILMT-FP0002-server-linux-s390_64.zip v TIV-ILMT-FP0002-server-linux-x86_32.zip v TIV-ILMT-FP0002-server-linux-x86_64.zip v TIV-ILMT-FP0002-server-solaris-sparc64.zip v TIV-ILMT-FP0002-server-windows-x86_32.zip v TIV-ILMT-FP0002-server-windows-x86_64.zip Native agent installers: v TIV-ILMT-TAD4D-FP0002-agent-aix-ppc.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-hpux.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-i5os.zip v TIV-ILMT-TAD4D-FP0002-agent-linux-ppc.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-linux-s390.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-linux-x86.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-solaris-sparc32.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-solaris-sparc64.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-solaris-x86_64.tar.gz v TIV-ILMT-TAD4D-FP0002-agent-windows-x86.zip SPB based agent installers: v TIV-ILMT-TAD4D-FP0002-SPB.zip The fix pack must be applied only to the License Metric Tool server component. It is not required to patch the database component. If the server is in the older version, upgrade the server to level first. It is not possible to install the administration server using only the fix pack installation file. For more information about installing the server, see the Installing section of the information center. 6 IBM License Metric Tool: Readme file for Fix Pack TIV-ILMT-FP0002

13 Important: Before you apply the fix pack, make sure that there is enough space available in the directory where the administration server is installed. The fix pack requires the additional amount of 520MB during the installation. Note: During the installation of the fix pack on the administration server, the script stops and starts the server. If the server is running in a WebSphere Application Server secure cell, you are asked to provide the user ID and password for the secure cell. Ensure that you have this information before you start. To install the fix pack on embedded WebSphere Application Server (or to upgrade the 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: 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 same terms and conditions under which License Metric Tool is licensed. 4. Specify a directory where the wizard can create a backup of your server configuration 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 platform on which the administration server is installed, but typically the backup requires 520MB of disk space. 5. The installer patches your product to fix pack level 2. This is a fully automated step. 6. When the installation is complete and you get the confirmation message, click Next 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 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 Fix Pack 2). Reverting to the previous version There is no automatic method for uninstalling this fix pack. You must roll back the changes on each computer with the installed fix pack. To uninstall the fix pack from the administration server: Readme file 7

14 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. 8 IBM License Metric Tool: Readme file for Fix Pack TIV-ILMT-FP0002

15 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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Copyright IBM Corp. 2002,

16 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX 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 material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International 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 and trademark information at Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. 10 IBM License Metric Tool: Readme file for Fix Pack TIV-ILMT-FP0002

17 Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Notices 11

18 12 IBM License Metric Tool: Readme file for Fix Pack TIV-ILMT-FP0002

19 Index Copyright IBM Corp. 2002,

20 14 IBM License Metric Tool: Readme file for Fix Pack TIV-ILMT-FP0002

21

22 Printed in USA