IBM License Metric Tool Version Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

Transcription

1 IBM License Metric Tool Version Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

2

3 IBM License Metric Tool Version Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

4 Note Before using this information and the product it supports, read the information in Documentation notices for IBM License Metric Tool on page 11. April 2011 This edition applies to Fix Pack TIV-LMT-FP0001 IBM License Metric Tool IBM welcomes your comments. Address your comments to: IBM License Metric Tool Information Development SWG Krakow Laboratory IBM Polska Sp. z o.o. ul. Armii Krajowej Krakow Poland Fax Number: (+48) When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright IBM Corporation 2004, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Readme file for Fix Pack TIV-LMT-FP0001 Known issues for IBM License Metric Tool Fix Pack 1 are addressed in this document. Contents v Description v Summary of changes v System requirements on page 3 v Installing the fix pack on page 4 v Reverting to the previous version on page 8 Description This readme provides important information about Fix Pack 1 for License Metric Tool version It contains the most current information for the fix 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: Summary of changes This section summarizes the changes that have been made to License Metric Tool, version by Fix Pack 1: v Reworked agent installer on AIX with support for the fileset relocation mechanism. For more information, see infocenter/lmt/v7r2m2/index.jsp?topic=/com.ibm.license.mgmt.planinconf.doc/ t_agent_preinstallation.html. v Support for IBM zenterprise BladeCenter Extension (zbx). v Support for Sun UltraSPARC T3 processor identification. v Support for wild cards in file names for use monitoring signatures. v New Common Inventory Technology packaged with agent installer ( build 2011/03/18). For more information, see support/ibmlicensemetrictool.html. APARs fixed The following APARs have been fixed in the fix pack: IZ91257 CODCL7053E WHEN ATTEMPTING IMPORT PVU The PVU table import problem. The problem does not occur with the newest PVU table. Copyright IBM Corp. 2004,

6 IZ89741 IZ92254 IZ92266 IZ92844 IZ91253 IZ92675 IZ94999 IZ95325 IZ96426 IZ95762 IZ96567 IZ96916 CURRENT CAPACITY SERVER LINKS POINTING TO WRONG DETAIL PANELS PID AND PART NUMBER INFORMATION MISSING DEADLOCK ERROR ENCOUNTERED CODDB3021E AND CODUI7003E LMT FAILED TO COLLECT DATA FROM HYPERV VIRTUAL MACHINE MISSING PID INFORMATION MANUAL CATALOG IMPORT POINTS TO WRONG URL AGGREGATION FAILS WITH JAVA. LANG. NULLPOINTER EXCEPTION COM.IBM. LICENSE. MGMT.ADMIN. AGGREGATION. CORE. HWMCALCULATOR. PROCES HOSTNAME UNIXSYSTEMPARAMS MISSING ON HPUX PERIODIC SELF-UPDATE PROCESS NOT WORKING AS DESIGNED APPLICATION TRUST STORE PASSWORD CANNOT BE CHANGED AGGREGATION AND RECALCULATION SYNCHRONIZATION ISSUE ADDITIONAL TIMEOUT HANDLER WHEN PROCFILES COMMAND HANGS The defect in the user interface logic - some links were leading to wrong locations. Some PIDs were not listed in the PVU report. Database deadlocks in big environments (mostly Tivoli Asset Discovery for Distributed) when some UI operations are performed in parallel. The problem occurs only in the following situation - when a lot of Hyper-V VMs are managed by a VM manager (Hyper-V environments only). Not all PIDs were imported from the software catalog. Wrong URL in the UI for the manual catalog import. Automatic import works correctly. The problem with aggregation when the License Metric Tool server is installed on specific locales. It does not apply to US locales. The Common Inventory Technology issue in hardware scan on HP-UX. The periodic self-update not working. Since fix is on the agent side, the self-update from agents older that may not work in the periodic mode. The password to the trust store used for the server CLI communication was hardcoded and could not be changed. Performance issues with recalculation that is running long and prevents aggregation from starting. The Common Inventory Technology APAR for hanging use scanner (snapshot) on some AIX machines. 2 IBM License Metric Tool: Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

7 IZ96955 IZ96956 IZ96882 IZ97063 IZ97064 IZ97134 IZ97315 IZ97898 IZ95101 IZ98530 FAILING UPGRADE ON WINDOWS FROM TLCM 2.3 AND LMT 7.1 TO LMT/TAD4D 'TLMAGENT' WINDOWS SERVICE NOT REMOVED WHEN UNINSTALLING AGENT USING THE 'TLMUNINS' SCRIPT "NO LIBGSK7ICCS_64.SO" ERROR ON SOLARIS9 CODUI7003E DISPLAYED WHEN DOWNLOADING SUMMARY AS CSV RECONFIGURE CIT USE SCANNER WHEN RC=51 RECEIVED FROM SNAPSHOT ERROR IN LOGFILE:SERVICE 8-DOWNLOAD PARAMETERS TIME NOT IN SYNC REMOTE/LOCAL SERVER TIMESTAMPS MISALIGNMENT THE SOFTSCANS ARE NOT WORKING CORRECTLY THE VALUE OF A HOST VARIABLE IN THE EXECUTE OR OPEN STATEMENT IS OUT OF RANGE FOR ITS CORRESPONDING USE AGENTS DO NOT SHOW THE SOFTWARE AND HARDWARE SCAN RESULTS NO INFO: CPU CORE ON PARTITION/LOGICAL CPU CORE ON PARTITION The issue on agent side related to wrong handling of Windows service names. The agent could not be upgraded only from versions 2.3 or 7.1. The agent service was not removed after agent uninstallation on Windows. The problem with exporting a correct environmental variable in tlmagent script only for 64-bit Solaris machines. Exporting to CSV fails for view only reports with NullPointerException. Agent fix for correct handling of Common Inventory Technology upgrades during the agent operation with use monitoring enabled. Problem with Windows performance counters resulting in problems with agent-server communication. Node name change not reflected in the TLMA database for VMware environments with configured VM managers. Failing software scan uploads with native scan enabled when too long fields retrieved from system registry. SQL exception during hardware scan upload with too long manufacturer name. The ADM.TIER table is not always correctly filled with data by the GA installer. System requirements For information about hardware and software compatibility, see Installing License Metric Tool for detailed system requirements. Readme file for Fix Pack TIV-LMT-FP0001 3

8 Installing the fix pack This section contains the instructions for installing the fix pack. Once you have installed the fix pack, you cannot uninstall it automatically. For details of how to revert to the previous version, see Reverting to the previous version on page 8. The fix pack includes the following files: The package for the server deployment on the base version of WebSphere Application Server (for the database component upgrade, use the files for embedded WebSphere Application Server deployment): v TIV-ILMT-FP0001-server-WAS-manual-deployment.zip The packages for the server deployment on embedded WebSphere Application Server: v TIV-ILMT-FP0001-server-aix-ppc64.zip v TIV-ILMT-FP0001-server-hpux-ia64.zip v TIV-ILMT-FP0001-server-linux-ppc64.zip v TIV-ILMT-FP0001-server-linux-s390_64.zip v TIV-ILMT-FP0001-server-linux-x86_32.zip v TIV-ILMT-FP0001-server-linux-x86_64.zip v TIV-ILMT-FP0001-server-solaris-sparc64.zip v TIV-ILMT-FP0001-server-windows-x86_32.zip v TIV-ILMT-FP0001-server-windows-x86_64.zip Binary agent installers: v TIV-ILMT-TAD4D-FP0001-agent-aix-ppc.bin v TIV-ILMT-TAD4D-FP0001-agent-hpux.bin v TIV-ILMT-TAD4D-FP0001-agent-linux-ppc.bin v TIV-ILMT-TAD4D-FP0001-agent-linux-s390.bin v TIV-ILMT-TAD4D-FP0001-agent-linux-x86.bin v TIV-ILMT-TAD4D-FP0001-agent-solaris-sparc32.bin v TIV-ILMT-TAD4D-FP0001-agent-solaris-sparc64.bin v TIV-ILMT-TAD4D-FP0001-agent-solaris-x86_64.bin v TIV-ILMT-TAD4D-FP0001-agent-multi_unix.bin Native agent installers: v TIV-ILMT-TAD4D-FP0001-agent-aix-ppc.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-hpux.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-i5os.zip v TIV-ILMT-TAD4D-FP0001-agent-linux-ppc.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-linux-s390.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-linux-x86.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-solaris-sparc32.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-solaris-sparc64.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-solaris-x86_64.tar.gz v TIV-ILMT-TAD4D-FP0001-agent-windows-x86.zip SPB based agent installers: 4 IBM License Metric Tool: Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

9 v TIV-ILMT-TAD4D-FP0001-agent-SPB.zip UPGRADING THE SERVER The fix pack must be applied to the License Metric Tool server and to the database components. It is not possible to install the administration server or database using the fix pack installation file only. In case the administration server is installed on a different node than the database, the fix pack has to be applied to the database component before applying it to the server component. For information about installing the server, see Installing the server in the License Metric Tool Installation Guide. v Running the installer in silent mode The response file (installresponse.txt) is shipped with the installation script. It contains values for the options that enable the License Metric Tool installation setup file to be run from the command-line interface. A common use of the response file is to run the wizard in silent mode. This lets the options file author to specify wizard settings without having to run the wizard in the graphical mode. The response file is required only if the server component alone or the server with its database is to be patched. Patching the database component alone does not require the response file. To use the response file in silent mode, use the following command-line arguments when running the wizard: (UNIX) TIV-ILMT-FP0001-<PLATFORM_NAME>.sh -f "<full_path_to_response_file>" -i silent (WINDOWS) start /wait TIV-ILMT-FP0001-<PLATFORM_NAME>.bat -f "<full_path_to_response_file>" -i silent v Upgrading the server on embedded WebSphere Application Server Important: 1. Back up the administration server database before applying the fix pack. 2. Before you apply the fix pack, make sure there is enough space available in the directory where the License Metric Tool server is installed. The fix pack requires the additional amount of 350 MB during the installation. 3. The following sections state that you must be an Administrator to run the installer on Windows platforms. If installer is to upgrade the database component, make sure that the Administrator account is a member of DB2ADMNS group. Note: During the installation of the fix on the administration server, the wizard stops and starts the server. If the server is running in a WebSphere Application Server secure cell, you will be 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 with both the License Metric Tool server and database components installed on a single computer, complete the following steps: 1. Log on to the computer where the License Metric Tool server is installed as Administrator (Windows) or root (UNIX ). Readme file for Fix Pack TIV-LMT-FP0001 5

10 2. Unpack the fix pack compressed file into a temporary directory. The file to be used has the following naming convention: TIV-ILMT-FP0001- server-<platform_name>.zip. 3. Launch the setup file for the platform on which you are installing the fix pack. The setup file is a script with the following naming convention: TIV-ILMT-FP0001-<PLATFORM_NAME>.[bat sh]. The installation script starts. Note: No license agreement panel 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. If the wizard is unable to create the backup, the installation cannot continue. Ensure that you have the correct permissions to write to the specified directory and that there is sufficient space to create the backup. Note: The space required for backup may vary, depending on the platform on which the administration server was installed, but typically backup requires 350 MB of disk space. 5. Installer patches your product to fix pack 1 level. This is a fully automated step. 6. When the installation is complete and you get the confirmation message, click Next to exit the wizard. Important: If the installer shows an error message about the failure of installing the fix pack, perform the following steps: a. Analyze the error message and fix the problem that caused the failure. b. Rollback the changes the installer made (see Revering to the previous version). c. Run the installer again. To install the fix pack on embedded WebSphere Application Server with the License Metric Tool server and database components installed on separate computers, complete the following steps: 1. Stop the License Metric Tool server. 2. Log on to the computer where the License Metric Tool database is installed as Administrator (Windows) or root (UNIX ). 3. Unpack the fix pack compressed file into a temporary directory. The file to be used has the following naming convention: TIV-ILMT- FP0001-server-<PLATFORM_NAME>.zip. 4. Launch the setup file for the platform on which you are installing the fix pack. The setup file is a script with the following naming convention: TIV-ILMT-FP0001-<PLATFORM_NAME>.[bat sh]. The installation script starts. Note: No license agreement panel is displayed. The fix pack is subject to the same terms and conditions under which License Metric Tool is licensed. 5. Installer patches your database component to fix pack 1 level. This is a fully automated step. 6 IBM License Metric Tool: Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

11 6. When the installation is complete and you get the confirmation message, click Next to exit the wizard. 7. Log on to the computer where License Metric Tool server is installed as Administrator (Windows) or root (UNIX). 8. Unpack the fix pack compressed file into a temporary directory. The file to be used has the following naming convention: TIV-ILMT- FP0001-server<PLATFORM>.zip. 9. Launch the setup file for the platform on which you are installing the fix pack. The setup file is a script with the following naming convention: TIV-ILMT-FP0001-<PLATFORM_NAME>.[bat sh]. The installation script starts. Note: No license agreement panel is displayed. The fix pack is subject to the same terms and conditions under which License Metric Tool is licensed. 10. 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. If the wizard is unable to create the backup, the installation cannot continue. Ensure that you have the correct permissions to write to the specified directory and that there is sufficient space to create the backup. Note: The space required for backup may vary, depending on the platform on which the administration server was installed, but typically backup requires 350 MB of disk space. 11. Installer patches your server component to fix pack 1 level. This is a fully automated step. 12. When the installation is complete and you get the confirmation message, click Next to exit the wizard. 13. Open the server Web UI and browse to the About page to verify if the reported product version is v Important: If the installer shows an error message about the failure of installing the fix pack, perform the following steps: a. Analyze the error message and fix the problem that caused the failure. b. Rollback the changes the installer made (see Revering to the previous version). c. Run the installer again. Upgrading the server on the base version of WebSphere Application Server To apply this fix pack to License Metric Tool installed on the base version of WebSphere Application Server, perform the following steps: 1. Stop the License Metric Tool server. 2. Log on to the computer where the License Metric Tool database component is installed as Administrator (Windows) or root (UNIX). 3. Unpack the fix pack compressed file into a temporary directory. The file to be used has the following naming convention: TIV-ILMT- FP0001-server-<PLATFORM_NAME>.zip. 4. Launch the setup file for the platform on which you are installing the fix pack. The setup file is a script with the following naming convention: TIV-ILMT-FP0001-<PLATFORM_NAME>.[bat sh]. The installation script starts. Readme file for Fix Pack TIV-LMT-FP0001 7

12 Note: No license agreement panel is displayed. The fix pack is subject to the same terms and conditions under which License Metric Tool is licensed. 5. Installer patches your database component to fix pack 1 level. This is a fully automated step. v Important: If the installer shows an error message about the failure of installing the fix pack, perform the following steps: a. Analyze the error message and fix the problem that caused the failure. b. Rollback the changes the installer made (see Revering to the previous version). c. Run the installer again. 6. Log on to the computer where the License Metric Tool server component is installed as Administrator (Windows) or root (UNIX). 7. Locate and backup the following directories: - WebSphere_installation_path/profiles/profile_name/istalledApps/ cell_name/lmt-tad4d_agent_message_handler.ear/ com.ibm.license.mgmt.msghandler.web.war - WebSphere_installation_path/systemApps/isclite.ear/lmt_admin.war - the cli directory created in the user-specified location during the product installation 8. Overwrite the files located above with the ones supplied in TIV-ILMT-FP0001-server-WAS-manual-deployment.zip archive. 9. Edit the cli/lmtcli.[sh bat] file and assign the actual values to the following attributes: WAS_HOME, ADMIN_WAR_NAME. You can use for your reference the backup of the file that was done in step Start the License Metric Tool server. 11. Open the server Web UI and browse to the About page to verify if the reported product version is Upgrading agents - perform this step if you have encountered any of the agent problems listed in the table with APARs For more information, see the Upgrading agents section in the information center. Reverting to the previous version There is no automatic method for uninstalling this fix pack. You must rollback the changes on each computer where the fix pack has been installed. To uninstall fix pack from the administration server: 1. Stop the server. 2. Restore the administration server database backup that was done before applying the fix pack. 3. Restore the files that were backed up before applying the fix pack. 4. Restart the server. To uninstall fix pack from an agent: 1. Uninstall the agent. 8 IBM License Metric Tool: Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

13 2. Install the previous version of the agent. Readme file for Fix Pack TIV-LMT-FP0001 9

14 10 IBM License Metric Tool: Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

15 Documentation notices for IBM License Metric Tool 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. 2004,

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. 12 IBM License Metric Tool: Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

17 Trademarks The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM iseries pseries Tivoli WebSphere zseries IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (&regtm; or &tm;), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. 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. Other product and service names might be trademarks of IBM or other companies. Copyright IBM Corp. 2004,

18 14 IBM License Metric Tool: Readme File for: IBM License Metric Tool, Fix Pack TIV-LMT-FP0001

19

20 Product Number: