  Readme for Interim Fix 2.3.0.3-TIV-TLCM-IF0004

Fixes and known issues for Tivoli Licence Compliance Manager 2.3.0.3
Interim Fix 4 are addressed in this document.

    Contents

    * Description
    * System requirements
    * Installing the interim fix
    * Upgrading agents
    * Reverting to the previous version
    * Product Fixes
    * Known problems


    Description

This readme provides important information about interim fix
2.3.0.3-TIV-TLCM-IF0004 for IBM® Tivoli License Compliance Manager,
version 2.3. It contains the most current information for the interim fix
and takes precedence over all other documentation.

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

Note: To install the interim fix, you must be logged on as Administrator
(on Windows®) or root (on UNIX®) to the computer where Tivoli License
Compliance Manager is installed.

    System requirements

For information about hardware and software compatibility, see Planning
a Tivoli License Compliance Manger Implementation
<http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.itlm.doc/install/tlminmst18.htm#planning>
in the IBM Tivoli License Compliance Manager: Planning, Installation,
and Configuration for detailed system requirements.


    Installing the interim fix

This section contains the instructions for installing the interim fix. Once
you have installed the interim fix, you cannot uninstall it automatically.
For details of how to revert to the previous version see Reverting to
the previous version <#relnotes__reverting>

The interim fix includes the following files:

2.3.0.3–TIV-TLCM-IF0004-servers-</platform/>.zip
    For each supported platform, the compressed file contains the files
    for installing the interim fix on computers where an administration
    server, a runtime server, or an administration server database or
    runtime server database is installed.
2.3.0.3–TIV-TLCM-IF0004-SPB.zip
    This file contains the software package blocks for each supported
    agent platform, to be used when deploying agents using IBM®
    Tivoli® Configuration Manager.
2.3.0.3-TIV-TLCM-IFP0004-agent-gateway.zip
    This file contains the software packages for each supported agent
    platform in PKT format. 
2.3.0.3–TIV-TLCM-IF0004-RSH-SSH-</platform/>.zip
    This contains the files needed to deploy agents on UNIX® platforms
    using the RSH/SSH deployment wizard.
2.3.0.3–TIV-TLCM-IF0004-ManualDeploy-</platform/>.zip
    This contains the files needed to install agents using a local wizard.
2.3.0.3-TIV-TLCM-IF0004-SPB-TOOLS.zip
    This contains the SPBs for agent configuration update.

The interim fix must be applied to all server and database components of
Tivoli License Compliance Manager.

Note:

   1. Before starting the installation, back up the administration and
      runtime server databases and the installation directories of
      administration server and runtime servers.
   2. During the installation of the fix on the administration server or
      a runtime 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 interim fix, complete the following steps on each computer
where a component is installed:

   1. Log on to the computer where one or more of the Tivoli License
      Compliance Manager components is installed as Administrator
      (Windows® ) or root (UNIX).
   2. Unpack the servers compressed file into a temporary directory.
   3. Launch the setup file for the platform on which you are installing
      the interim fix.
      The installation wizard starts.
      Note: No license agreement panel is displayed. The interim fix is
      subject to the same terms and conditions under which Tivoli
      License Compliance Manager 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 wizard calculates the space required to create the
      backup based on the initial size of a server when it is installed.
      Under normal circumstances, the space occupied by the server
      directories should not increase very much. However, if other
      directories, for example directories required for manual agent
      deployment, have been created within the server file structure,
      the space required for the backup could be considerably more than
      anticipated. Under these circumstances, it is possible that the
      installation could fail because of lack of space. If this occurs,
      a message will be displayed informing you that the installation
      has failed, possibly because of insufficient permissions. You must
      then make more space available for the installation.
   5. Check the summary panel for the installation and click *Next* to
      confirm that you want to install the interim fix.

      If you are applying the interim fix to a server that is running in a
      WebSphere Application Server secure cell, you will be prompted to
      supply a valid user ID and password when the wizard stops and
      starts the runtime server.

   6. When the installation is complete, click *Finish*.


    Upgrading agents

To apply the fixes to agents that are already deployed, you must
redeploy or update the agent. For information about how to do redeploy
an agent see the section *Redeploying an agent* in IBM Tivoli License
Compliance Manager: Planning, Installation, and Configuration.

For information about updating agents to this interim fix level when they
are connected to a runtime server where the interim fix has been applied,
see *Configuring a periodic agent self-update* in IBM Tivoli License
Compliance Manager: Planning, Installation, and Configuration.

Agents are supported only when they are registered to a runtime server
with the same, or a higher, Tivoli License Compliance Manager
maintenance level.


    Reverting to the previous version

There is no automatic method for uninstalling this interim fix.

You must rollback the changes on each computer where the interim fix has
been installed, as follows:

   1. Stop the server.
   2. Manually replace the files that were changed by the installation
      of the interim fix with the backup copies taken during the installation.

      The backup directory specified during the installation of the fix
      pack contains a subdirectory 2.3.0.3-TIV-TLCM-IF0004 which contains
      a subset file structure for the Tivoli License Compliance Manager
      components to which the interim fix has been applied. You must copy
      the files manually from each subdirectory of the backup to the
      corresponding directory of the server installation.

   3. If this is the first fix applied to the GA version of the code,
      delete the file <INSTALL_DIR>\product.xml.

      If previous fixes have been applied, the product.xml file is one
      of the files that you have restored from the backup directory.

   4. Restart the server.


   Product Fixes

Interim fixes are not cumulative, so this interim fix must be installed
on top of the last fix pack, what is 2.3.0 TIV-TLCM FP0003.
This subsection provides a summary of the functionality and fixes that
have been added to fix pack 2.3.0 TIV-TLCM FP0003. It aims to help users
who have installed the fix pack 2.3.0 TIV-TLCM FP0003 to understand 
what changes they can expect from this interim fix.

The following issues were fixed in this interim fix:
    * IZ10812  LICENSE TOTAL QUANTITY WILL ONLY ALLOW 5 CHARACTERS
      License "total quantity" field allowed only 5 characters to be entered,
      what limits maximum quantity to 99999. In this fix the limit
      was increased to 7 characters.

    * IZ11406 WRONG VERSION OF GSKIT USED BY AGENT IN CASE OF OTHER GLOBAL
      GSKIT INSTALLATION
      Wrong version of GSKit used by agent in case of other global GSKit
      installation caused that in some situations agent installations failed.
      The fix uses script to install agent that sets library path to local
      GSKit installation.
      
    * IZ15867  PROBLEM CAUSED BY CERTIFICATE THAT HAS EXPIRED
      Defect was causing problem with communication between agents and Runtime 
      Servers in security mode 1 (SSL). New certificate is included in this 
      Interim Fix.    
                  
Known problems from last fixpack fixed in this interim fix:

    * Automatic agent self-update facility is not supported for Windows
      Vista on x86_64 platforms.     
    * When tracking of unlicensed products, it is possible to enable 
      tracking for selected organizations or for all organizations, but 
      not possible to enable or disable tracking for an individual 
      division. When using the command line interface command 
      unlicevent -e |-d -division -n <name>, an error is displayed: 
      "CODCL7053E An internal error has occurred"      
    * Agent is unable to properly detect node structure on framed Sun 
      DSD servers where a few system boards share frame's serial number. 
      As a result, several agents installed on different physical machines
      may appear in TLCM as installed on the same node.
    
This Interim Fix upgrades CIT component to version  2.4.1015

Known problems are documented in the form of individual technotes in the
Support knowledge base at
/http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliLicenseManager.html/.
As problems are discovered and resolved, the IBM Support team updates
the knowledge base. By searching the knowledge base, you can quickly
find workarounds or solutions to problems.

At time of publication, the following installation problems were known:

    * Since some fixes introduced by this deliverable require a specific
      version of IBM Software Catalog to work properly, no Catalog older
      than December 2007 should be imported after upgrading to interim fix 3.
    * Due to the error caused by APAR PK45088, shipped in WebSphere
      Application Server 6.1.0.11 and 6.1.0.13, WASAgent is not able to
      monitor those versions of the product. To restore it's
      functionality upgrade WebSphere Application Server to 6.1.0.15.
    * In Tivoli Configuration Manager with License Management Extension
      environment be careful to install "CM Endpoint Extension, Version
      4.2.3, fix 4.2.3-TIV-CMEXT-LA0002" on the Gateways and to
      distribute an Inventory Scan to download the new CM Endpoint
      Extension executable on the endpoints. This is a prerequisite to
      take advantage of the fix implemented in IY99063.
    * SPBs for changing agent parameters fail when destination agent is
      not running.

   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 give 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 10504-178, U.S.A.

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

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, 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 might 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.

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/101
11400 Burnet Road
Austin, TX  78758 	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 document 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.

Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been
made on development-level systems and there is no guarantee that these
measurements will be the same on generally available systems.
Furthermore, some measurement may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.

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

The following terms are trademarks of the IBM Corporation in the United
States or other countries or both: 

IBM
The IBM logo 
AIX
DB2
DB2 Universal Database
Tivoli
WebSphere
zSeries

Microsoft, Windows, and the Windows logo are registered trademarks, of
Microsoft Corporation in the U.S. and other countries.

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

Intel is a trademark of Intel Corporation in the United States, other
countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.

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