IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


Documentation problems and corrections contained in this fix pack

User’s Guide for Inventory

This section contains new and updated information for IBM Tivoli Configuration Manager User’s Guide for Inventory:

In Appendix F. Troubleshooting, in the "Scalable Collection Service" section, before the "Log and data files" section:

add the following information:

Symptom catalog and log files adapters

Starting from the Autonomic Computing AC Log and Trace 4.5.0.3 fix pack, adapters are supported for the mcollect.log file.

In this fix pack are available also the symptom catalogs for Tivoli Configuration Manager version 4.3.1.

Defect 247275
In Appendix E. Installing and uninstalling Common Inventory Technology (CIT), in the "Scanning virtual environments" section:

add the following row to the "Versions of VMware tested on CIT" table:

ESX Server 3.5

APAR IZ50799
In Chapter 3. Working with Inventory profiles in the "Software scan configuration options" section, subsection "Scan Options" replace the current text:

Signature data includes the name, size, and usually the quick checksum value of the file used to identify the software product.

with the following text:

Signature data includes the name and the size of the file used to identify the software product.

APAR IZ50799
In Chapter 5. Collecting custom information with Inventory in the "Using signatures" section replace the current text:

Signature data includes the name, size, and usually the Quick checksum value of the file used to identify the software product.

with the following text:

Signature data includes the name and the size of the file used to identify the software product.

APAR IZ50799
In Appendix B. Commands in the "winvsig" section replace the current description for the -a command option with the following text:

Adds one or more signatures to the configuration repository, and modifies existing signatures. Each signature must have a unique file name and size. If the specified signature already exists, the information for the existing signature (for example, the description or version) is modified.

APAR IZ50799
In Appendix B. Commands in the "winvsig" section replace the current description for the -f command option with the following text:

Specifies the name of a file that contains the data for one or more signatures. The signature data in the file must be in the following format:

<I>,name,size,description,version

The signature file supports also the XML file format.

APAR IZ53312
At the end of Appendix E. Installing and uninstalling Common Inventory Technology (CIT), add the following new section:

Setting the CIT processes priority on Windows

On Windows platforms, you can specify locally on each endpoint the priority for the different CIT processes by editing the cit.properties file and adding, for example, the following priorities:

fscanner.changepriority=low
swscanner.changepriority=low
hwscanner.changepriority=low
vpdscanner.changepriority=low
If you want to add the priority settings directly to the CIT_win.spb package used to install CIT, perform the following steps:
  1. Take the CIT_win.spb package from a gateway. The package is located under the ..bin/lcf_bundle.41100/lib/w32-ix86/inv/CIT/SPB directory.
  2. Using the Software Package Editor disconnected command line, unbuild the CIT_win.spb package by running the command:
    wdubldsp.exe
    The command extracts a software package (.sp file) and the CIT files.
  3. Edit the unpacked cit.properties file and add, at the bottom of the file, the following lines:
    fscanner.changepriority=low
    swscanner.changepriority=low
    hwscanner.changepriority=low
    vpdscanner.changepriority=low
    Save the file.
  4. Build the CIT_win.spb again by running the command:
    wdbldspb.exe
    The new CIT_win.spb now includes the new cit.properties file with the priority settings that you set.
  5. Save the original CIT_win.spb on the gateways and store the new CIT_win.spb under the same directory.
  6. During the next CIT installations, on the endpoints, are automatically included the CIT priority settings contained in the cit.properties file.
APAR IZ53836
In Appendix B. Commands in the "wqueryinv" section add the following note:

Note:
When using a Tivoli query containing views sharing the same TME_OBJECT_ID field and running the wqueryinv command against that query, the command fails with a parse error due to an ambiguous column reference. For example, if you are using an Oracle database the error message displayed is the following:
ORA-00918: column ambiguously defined
You can run the command only with Tivoli queries where only one table and view have the TME_OBJECT_ID field.

Database Schema Reference

This section contains new and updated information for IBM Tivoli Configuration Manager Database Schema Reference:

Defect 245830
In Chapter 3. Configuration repository views add the following columns to the following views:
Table 15. Columns added to views
Configuration repository view Columns added to the view
V_ACT_ST

COUNTER

V_ACT_STATUS_EX

TARGETS

GATEWAYS

DEPOTS

V_PLAN_STATUS

TGT_RESOURCE_TYPE

V_PLAN_STATUS_EX

ACTIVITIES

REC_NUM

V_TGT_ACT_DEP_ST

DEPOT_LABEL

COUNTER

START_TIME

COMPLETION_TIME

V_TGT_ACT_GW_ST

COUNTER

START_TIME

COMPLETION_TIME

V_TGT_ACT_ST

COUNTER

V_TGT_GW_FLTR

COUNTER

START_TIME

COMPLETION_TIME

ASP_VIEW

COMPUTER_SYS_ID

TME_OBJECT_ID

CHECK_PACKAGES

PLATFORM

COMPUTER_VIEW

OS_ARCH

IP_ADDR_VIEW

PERM_MAC_ADDRESS

LPAR_VIEW

NODECAP_IN_CORES

LPARCAP_IN_CORES

SHAREDPC_IN_CORES

PHYS_SHAREDPC

PHYS_SHAREDPC_CORES

LPAR_ONLINE_VP_COUNT

LPAR_IS_SHARED_TYPE

LPAR_IS_CAPPED

LPAR_ENTITLEMENT

LPAR_MIN_VP_COUNT

LPAR_MAX_VP_COUNT

LPAR_MIN_CAPACITY

LPAR_MAX_CAPACITY

LPAR_IDLE_CP_WEIGHT

SMT_IS_ENABLED

NODE_ACT_PROC_COUNT

LOGICAL_PARTITIONS_VIEW

PHYS_SHAREDPC

PHYS_SHAREDPC_CORES

LPAR_ONLINE_VP_COUNT

LPAR_IS_SHARED_TYPE

LPAR_IS_CAPPED

LPAR_ENTITLEMENT

LPAR_MIN_VP_COUNT

LPAR_MAX_VP_COUNT

LPAR_MIN_CAPACITY

LPAR_MAX_CAPACITY

LPAR_IDLE_CP_WEIGHT

SMT_IS_ENABLED

NODE_ACT_PROC_COUNT

MEM_MODULES_TOTAL

TME_OBJECT_ID

OS_VIEW

OS_ARCH

PACKAGE_FILE_VIEW

PLATFORM

PC_BIOS_VIEW

UPTIME

SERVICE_INFO_VIEW

TME_OBJECT_LABEL

TME_OBJECT_ID

SMBIOS_DATA_VIEW

SYS_PRODUCT_NAME

POWERON_PASSWORD

SWARE_MATCH_CRC32

CHECKSUM_CRC32

SWARE_MATCH_MD5

CHECKSUM_MD5

SWARE_MATCH_QUICK

CHECKSUM_QUICK

EP_PATCHES_VIEW

GUID

UPDATEID

REBOOTBEHAVIOR

PM_PATCHES_VIEW

GUID

UPDATEID

REBOOTBEHAVIOR

SP_PATCHES_VIEW

GUID

UPDATEID

REBOOTBEHAVIOR

DEV_DET_BEA_VIEW

DEVICE_ID

DEV_DET_EXT_VIEW

DEVICE_ID

DEV_INFO_BEA_VIEW

DEVICE_ID

DEV_INFO_EXT_VIEW

DEVICE_ID

DMACC_CON_EXT_VIEW

DEVICE_ID

MO_LOGIN_VIEW

NAME

TW

LOGINTY

DATA

RECORD_TIME

Defect 245830
In Chapter 3. Configuration repository views remove the following columns from the following views:
Table 16. Columns removed from views
Configuration repository view Columns removed from the view
V_PLAN_STATUS_EX

REC_NUMBER

SMBIOS_DATA_VIEW

PRODUCT_NAME

NOSIG_FILES_VIEW

PATH

DEV_DET_BEA_VIEW

LABEL

DEV_DET_EXT_VIEW

LABEL

DEV_INFO_BEA_VIEW

LABEL

DEV_INFO_EXT_VIEW

LABEL

DMACC_CON_EXT_VIEW

LABEL

Defect 245830
In Chapter 4. Queries add the following columns to the following queries:
Table 17. Columns added to queries
Query Columns added to the query
ASP_QUERY

TME_OBJECT_ID

COMPUTER_SYS_ID

COMPUTER_QUERY

OS_ARCH

INST_FILE_QUERY

FILE_SIZE_KB

INVENTORY_SWARE

ACCESSED_TIME

IP_ADDR_QUERY

PERM_MAC_ADDRESS

LOGICAL_PARTITIONED_SYSTEMS_QUERY

NODECAP_IN_CORES

LOGICAL_PARTITIONS_QUERY

LPARCAP_IN_CORES

NODECAP_IN_CORES

SHAREDPC_IN_CORES

PHYS_SHAREDPC

PHYS_SHAREDPC_CORES

LPAR_ONLINE_VP_COUNT

LPAR_IS_SHARED_TYPE

LPAR_IS_CAPPED

LPAR_ENTITLEMENT

LPAR_MIN_VP_COUNT

LPAR_MAX_VP_COUNT

LPAR_MIN_CAPACITY

LPAR_MAX_CAPACITY

LPAR_IDLE_CP_WEIGHT

SMT_IS_ENABLED

NODE_ACT_PROC_COUNT

MEM_MODULES_TOTAL

TME_OBJECT_ID

OS_QUERY

OS_ARCH

SERVICE_INFO_QUERY

TME_OBJECT_LABEL

TME_OBJECT_ID

COMPUTER_SYS_ID

RECORD_TIME

SOLARIS_CPU_QUERY

PROCESSOR_NUM

MO_AP_NAP_QUERY

RECORD_TIME

MO_AP_NAPB_QUERY

RECORD_TIME

MO_AP_NAPD_QUERY

RECORD_TIME

MO_AP_NAPN_QUERY

RECORD_TIME

MO_AP_PX_QUERY

RECORD_TIME

MO_AP_PXA_QUERY

RECORD_TIME

MO_AP_PXD_QUERY

RECORD_TIME

MO_AP_PXN_QUERY

RECORD_TIME

MO_AP_PXNO_QUERY

RECORD_TIME

MO_AP_PXP_QUERY

RECORD_TIME

MO_DS_DB_QUERY

RECORD_TIME

CM_STATUS_QUERY

TME_OBJECT_ID

Defect 245830
In Chapter 4. Queries remove the following columns from the following queries:
Table 18. Columns removed from queries
Query Columns removed from the query
ALL_NET_CARD_QUERY

ADAPTER_ID

SERVICE_INFO_QUERY

SPATH_NAME

SSTARTED

MO_AP_NAP_QUERY

DEVICE_ID

MO_AP_NAPB_QUERY

DEVICE_ID

MO_AP_NAPD_QUERY

DEVICE_ID

MO_AP_NAPN_QUERY

DEVICE_ID

MO_AP_PX_QUERY

DEVICE_ID

MO_AP_PXA_QUERY

DEVICE_ID

MO_AP_PXD_QUERY

DEVICE_ID

MO_AP_PXN_QUERY

DEVICE_ID

MO_AP_PXNO_QUERY

DEVICE_ID

MO_AP_PXP_QUERY

DEVICE_ID

MO_DS_DB_QUERY

DEVICE_ID

Defect 245830
In Chapter 4. Queries add the following queries to the table contained in the section named "Subscription queries":
Defect 245830
In Chapter 5. Configuration repository tables add the following columns to the following tables:
Table 19. Columns added to tables
Configuration repository table Columns added to the table
COMPUTER

OS_ARCH

FILE_DESC

FILE_SIZE_KB

INST_SERVICE_INFO

DNAME

SDESC

SPATH_NAME

STYPE

SSTARTED

SSTART_MODE

SDISPLAY_NAME

SSTATE

SSTATUS

INST_SMBIOS_DATA

POWERON_PASSWORD

IP_ADDR

PERM_MAC_ADDRESS

LPAR

PHYS_SHAREDPC

PHYS_SHAREDPC_CORES

LPAR_ONLINE_VP_COUNT

LPAR_IS_SHARED_TYPE

LPAR_IS_CAPPED

LPAR_ENTITLEMENT

LPAR_MIN_VP_COUNT

LPAR_MAX_VP_COUNT

LPAR_MIN_CAPACITY

LPAR_MAX_CAPACITY

LPAR_IDLE_CP_WEIGHT

SMT_IS_ENABLED

NODE_ACT_PROC_COUNT

MATCHED_SWARE

MD5_ID

PM_PATCH_INFO

GUID

UPDATEID

REBOOTBEHAVIOR

PM_PATCH_PKG

GUID

SYNCDM_DMACC

ADDR

Defect 245830
In Chapter 5. Configuration repository tables remove the following columns from the following tables:
Table 20. Columns removed from tables
Configuration repository table Columns removed from the table
PM_PATCH_PKG

PROD_MAJOR_VER

PROD_MINOR_VER

PROD_LANG

OS_BASE_NAME

OS_ARCHITECTURE

OS_TYPE

OS_SUBTYPE

OS_SP_MAJOR_VER

OS_SP_MINOR_VER

SYNCDM_DMACC

ADDRESS

NAME

Defect 245830
In Chapter 3. Configuration repository views remove the following views from the chapter:
Defect 245830
In Chapter 5. Configuration repository tables remove the following tables from the chapter:
Feature 235414
In Chapter 2. History tracking in section "Modifying history tracking for efficiency" replace the first bullet of the section with the following text:

APAR IZ48308
In Chapter 3. Configuration repository views in section "PHYSICAL_PROCESSOR_VIEW" add the following columns to the current table:
Table 21. Columns added to Physical Processor View
Column Name Description
MANUFACTURER Processor manufacturer. Examples: Intel, AMD, IBM, SUN, HP. If the manufacturer is not recognized (is not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown".
FAMILY Processor family. Examples: Pentium 4, Xeon, Athlon 64, POWER5, UltraSparc-T1, PA-RISC. If the family is not recognized (not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown".
TYPE Processor type. Examples: 170 for AMD Opteron 150, 670 for Intel Pentium 4 670. If Common Inventory Technology does not support type identification for the family of processors then this field has value of an empty string. If Common Inventory Technology supports type identification for the family of processors but the type of processor is not recognized then this field has value of "Unknown".
CPU_FREQ Processor frequency in MHz. This field is optional and vendor specific. Depending on the processor family it might be nominal or current CPU frequency. CPU frequency might be interpreted differently across processor architectures and families. If not valid this field is 0.
L2_CACHE_SIZE Size of L2 cache in Kilobytes. This field is optional, 0 if not valid.
L3_CACHE_SIZE Size of L3 cache in Kilobytes. This field is optional, 0 if not valid or there is no L3 cache.
SIGNATURE Processor signature. This field is optional and platform- and vendor-specific. The value of this field might be taken from different sources on each platform and even for different processor families. If available this is the processor model identifier reported by CPUID instruction, BIOS or OS. This field is for internal Common Inventory Technology purposes only; the exploiter should make no assumption on contents or format of this field.
APAR IZ51439
In Chapter 3. Configuration repository views, in the "NET_CARD_VIEW" section, modify the following information:

APAR IZ53642
In Chapter 3. Configuration repository views, in the "PRINTER_VIEW" section, replace the current description for the PRINTER_IS_LOCAL column with the following description:

Whether the printer is a local printer or a network printer, and is the default printer or not. This column can assume one of the following values:

Y
The printer is not the default printer and is local.
N
The printer is not the default printer and is not local.
Z
The printer is the default printer and is local.
O
The printer is the default printer and is not local.

Patch Management Guide

This section contains new and updated information for IBM Tivoli Configuration Manager Patch Management Guide:

Defect 66832
In Chapter 1. Introduction, section "Operating systems and applications managed with this solution" add the following operating systems to the current list: and add the following note at the end of the list:
Note:
To enable WSUS 3.0 to manage Windows 7 and Windows 2008 r2 endpoints for Patch Management operations, you must download the Windows Server Update Services 3.0 SP2 from the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a206ae20-2695-436c-9578-3403a7d46e40

Defect 66531
In Chapter 5. Patch installation, section "Managing emergency patches", replace the current description for the os_base_name variable with the following text:

os_base_name
Identifies the name of the operating system (winxp, win2k, win2k3, win2k8, vista).
APAR IZ41238
In Chapter 7. Troubleshooting, section "Problems with the Tivoli Configuration Manager Automation Server silent installation", subsection named "Checks run during installation", replace the current step 4 of the procedure:

Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files and that Windows Instrumentation Service is not running to prevent the failure of the MQ Series component.

with the following text:

Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files.

APAR IZ41238
In Chapter 2. Installing the automated patch management solution, section "Installing and configuring Cygwin", add at the end of the current step 4 the following text:

The new output of the mount -m command will be:

mount -f -s -b "C:/cygwin/bin" "/usr/bin" mount -f -s -b
"C:/cygwin/lib" "/usr/lib" mount -f -s -b "C:/cygwin" "/"
APAR IZ41238
In Chapter 2. Installing the automated patch management solution, section "Installing and configuring Cygwin", add at the end of the current section the following new steps:

Planning and Installation Guide

This section contains new and updated information for IBM Tivoli Configuration Manager Planning and Installation Guide:

Defect 66291
In Chapter 5. IBM Tivoli Configuration Manager Installation and Upgrade, section "Custom Server Installation", in step 11 of the procedure, add after the following bullet: the following information:

If you are using a Windows workstation and the password policy rules are enabled, the password that you specify for the new tivapm user must meet the operating system password requirements. Otherwise the Activity Planner installation completes successfully, but the user is not created.

APAR IZ40233
In Chapter 3. Component Installation Prerequisites, section "Installation Options", subsection "Software Package Editor" add the following note at the end of the section:
Note:
For Red Hat Enterprise Linux 5.0 platforms, before you start using Software Package Editor, ensure that you have the following required packages installed:
  • libXp.so.6 (included in libXp-1.0.0-8.i386.rpm)
  • libXmu.so.6 (included in libXmu-1.0.2-5.i386.rpm)
APAR IZ46662
In Chapter 3. Component Installation Prerequisites in section "Components Installed From Software Package Blocks" subsection "Software Packages for the IBM Tivoli Configuration Manager Administrative Interfaces", remove the following row from Table 9. Software Packages for Installing the Administrative Interfaces:

Table 22. Software Packages for Installing the Administrative Interfaces
Tivoli_MD2GUI_L10N The language support packages for the Distribution Status console, version 4.3.1. The prerequisite for this package is Tivoli_MD2GUI.
APAR IZ51452
In Chapter 7. Maintaining and Troubleshooting a Configuration Management Environment, add the following section after the section named "Troubleshooting a Tivoli Management Framework installation":

Troubleshooting a Tivoli Management Framework silent installation

When you install IBM Tivoli Configuration Manager on Windows 2008 platforms in Japanese language using a silent installation, the Tivoli Management Framework installation might hang. As a workaround, proceed first with the Tivoli Management Framework installation using Tivoli Management Framework CD 1. When this installation is complete, launch the usual IBM Tivoli Configuration Manager installation using the product CD 5.

APAR IZ44183
In Chapter 4 "Working With Repositories and Queries", remove the current section named "Upgrade and migration considerations".
APAR IZ44183
Between Appendix A and Appendix B add the following new Appendix named "Upgrade and migration considerations".
Upgrade and migration considerations

This chapter describes how to upgrade Tivoli Management Framework and the IBM Tivoli Configuration Manager components.

Tivoli Management Framework backward compatibility rules

The upgrade is based on the following Tivoli Management Framework version 4.3.1 backward compatibility rules:

Tivoli Configuration Manager backward compatibility rules

The upgrade is also based on the following IBM Tivoli Configuration Manager 4.3.1 backward compatibility rules:

The upgrade can be performed using the classical procedure based on Tivoli Management Framework, the InstallShield MultiPlatform (ISMP) installation on the supported platforms, or the Tivoli Software Installation Service (SIS) on the supported platforms.

The IBM Tivoli Configuration Manager version 4.3.1 release does not contain enhancements that require changes in the Inventory schema. The Inventory schema upgrade modifies only the schema from the starting IBM Tivoli Configuration Manager release to the latest 4.2.3 maintenance level.

To upgrade the Inventory schema, apply the same procedure used when installing a IBM Tivoli Configuration Manager fix pack.

The images of IBM Tivoli Configuration Manager version 4.3.1 contain all the SQL scripts released with any 4.2.2 and 4.2.3 fix pack, up to 4.2.2-TIV-TCM-FP0006. You must run a subset of these scripts depending on the database vendor and the starting IBM Tivoli Configuration Manager release or fix pack.

Recommended steps for migrating large environments

To migrate large environments, it is recommended that you first upgrade to Tivoli Management Framework 4.3.1, and then start upgrading to IBM Tivoli Configuration Manager 4.3.1.

Upgrading Tivoli Management Framework

To upgrade Tivoli Management Framework, it is recommended that you use the following order (top-down approach):

  1. Hubs (First the Tivoli server, then the managed nodes and the gateways)
  2. Spokes (First the Tivoli server, then the managed nodes and the gateways)
  3. Endpoints

At the end of this phase you will have the Tivoli Management Framework infrastructure upgraded to 4.3.1 and IBM Tivoli Configuration Manager still working at 4.2.x level.

Upgrading IBM Tivoli Configuration Manager

To upgrade IBM Tivoli Configuration Manager, it is recommended that you use the following order (bottom-up approach):

  1. Spokes Tivoli Configuration Manager gateways
  2. Hubs Tivoli Configuration Manager gateways
  3. Spokes Tivoli Configuration Manager server
  4. Hubs Tivoli Configuration Manager server
  5. Database schema

If during the upgrade phase you want to run an Inventory scan from a back level Configuration Manager server to 4.3.1 endpoints attached to gateways on which IBM Tivoli Configuration Manager has already been upgraded to 4.3.1, run the following command against each gateway that has already been upgraded to Tivoli Management Framework 4.3.1:

wlevlmeth -a gateway_name (| all) 

The wlevlmeth utility is located under the /utils folder of the IBM Tivoli Configuration Manager version 4.3.1 CD. Use the wlevlmeth command to force the endpoints already upgraded to Tivoli Management Framework 4.3.1 to download binaries starting from the gateway bundles older than the 4.3.1 ones.

To upgrade IBM Tivoli Configuration Manager, perform these steps:

  1. Keep the Configuration Manager server components at back level.
  2. If needed, run the commands wlevmeth -a gateway_name or wlevmeth -a all, depending on if you want to issue the command against a specific gateway or against each gateway in the Tivoli region.
  3. Upgrade the Configuration Manager gateway components in your environment. During this phase, you can perform any Configuration Manager action against all the endpoints in your environment.
  4. When all the gateways are upgraded, and all the endpoints are upgraded to Tivoli Management Framework 4.3.1, ensure that no Configuration Manager distributions are running.
  5. Upgrade the Configuration Manager server components and the schema.
  6. If you issued the wlevmeth command, run now the commands wlevmeth -r gateway_name or wlevmeth -r all to reset the dependency download mechanism. After performing these commands, the 4.3.1 endpoints are allowed to download binaries starting from 4.3.1 gateway bundles.
  7. Check that the back level method flag has been restored by running wgateway gw_name get backlevel_methods. The command should return for each gateway the following output:
    backlevel_methods: NULL
  8. Start to perform any Configuration Manager action in the upgraded environment.
Notes:
  1. After upgrading the Configuration Manager server components and schema to 4.3.1, within a Tivoli region boundary, the 4.3.1 Inventory component might no longer support back level endpoints (for example at 3.7.x or 4.1.x level) because the database schema and scanner are no longer synchronized. For this reason some information, such as the signature software scan related data, cannot be collected, or there is a performance issue when trying to insert data to no longer existing or modified tables, such as service_info, matched_sware. Because these issues occur for all Configuration Manager schemas older than 4.2.3 Fix Pack 4, it is strongly recommended that you migrate all the endpoints to 4.3.1 before upgrading the Configuration Manager server and schema to 4.3.1.
  2. Configuration Manager 4.3.1 server components change the dependency set. A new 3.7.x or 4.1.x endpoint, that never received an Inventory scan or a Software Distribution action before the Configuration Manager upgrade to 4.3.1, might not be able to download from the gateway all the necessary binaries. For this reason it is strongly recommended to have all new endpoints, installed after the Configuration Manager upgrade to 4.3.1, at Tivoli Management Framework 4.3.1 level.

    You cannot perform a Fresh Install of 4.2.3 Configuration Manager gateway components, after upgrading to 4.3.1 Tivoli Management Framework on the managed nodes of your environment.

    If you cannot exclude the possibility that an old 3.7.x or 4.1.x endpoint connects to a Configuration Manager environment already migrated to 4.3.1, to minimize the impact caused by a mismatch between the Configuration Manager 4.3.1 schema and the 4.3.1 scanners we suggest that you:

  3. If you upgrade Configuration Manager starting from one of the following versions: take into account that the Configuration Manager scan is performed, after 4.2.3 Fix Pack 2, by the Common Inventory Technology (CIT) component. This is a component of Tivoli Configuration Manager, which can be installed from the Software Distribution disconnected command line using SPB files. The Software Distribution disconnected command line and the SPB files for installing Common Inventory Technology are downloaded to the endpoint when the first Inventory scan is performed, after the upgrade of the Configuration Manager server and gateways to 4.3.1. During this Inventory scan, the first action that occurs is the Common Inventory Technology installation.

    For more details about disk space requirements, refer to IBM Tivoli Configuration Manager: Release Notes version 4.3.1.

    Common Inventory Technology is installed using the following default paths:
    UNIX
    /opt/tivoli/cit /etc/cit
    Windows
    C:\Program Files\Tivoli\cit and C:\Windows\cit
    You can change the default installation path and also plan to install Common Inventory Technology in a more controlled way by using Software Distribution from the Configuration Manager server.

    For more details about how to install Common Inventory Technology, refer to IBM Tivoli Configuration Manager: User's Guide for Inventory version 4.3.1

    Common Inventory Technology does not interact with a Tivoli Configuration Manager Inventory component installed before 4.2.3 Fix Pack 2, until it is upgraded to 4.3.1. Ensure that you plan to install Common Inventory Technology in a controlled way before upgrading to 4.3.1.
  4. If you upgrade Configuration Manager starting from a version older than 4.2.3 Fix Pack 2, the first scan you perform on the endpoints fails because of a number of mismatches in the MIF file attribute, because the MIF file structure changed after 4.2.3 Fix Pack 2. To work around this problem, delete the previous *.bk* and *.mif files from the inv/SCAN directory before running a new scan. You can perform this operation by inserting the delete statements (for example, "rm *.bk*" or "del *.bk*") in the before scan script section of the InventoryConfig profile.

Reference Manual for Software Distribution

This section contains new and updated information for IBM Tivoli Configuration Manager Reference Manual for Software Distribution:

APAR IZ53412
In Chapter 1. Editing the Software Package Definition File, section "Structure of the SPD File", before the paragraph:

The sections where these stanzas are described show the structure in which you should define each stanza and provide examples.

add the following paragraph:

At installation time, the installation of a software package starts only if, during the check of the conditions specified in all software package stanzas, all these conditions are verified.

APAR IZ57893
In Chapter 1. Editing the Software Package Definition File, section "Attributes in the File System Stanzas" table "SPD File attributes in file system stanzas" in the row for the descend_dirs attribute:

add the following note:

On UNIX platforms if you set this attribute to y when creating software packages, to which a directory is added containing backward slashes, performing the winstsp command on the software package fails. To successfully install the software package on UNIX platforms, do not add to the package a directory containing backward slashes.

User's Guide for Deployment Services

This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Deployment Services:

In Chapter 4. Troubleshooting, before the "Activity Planner Logs and Traces" section:

add the following information:

Symptom catalog and log files adapters

Starting from the Autonomic Computing AC Log and Trace 4.5.0.3 fix pack, adapters are supported for the apmlog0 log file.

From this fix pack also the symptom catalogs for Tivoli Configuration Manager 4.3.1. are available.

Release Notes

This section contains new and updated information for IBM Tivoli Configuration Manager Release Notes:

Defect 66684
In Chapter 3. Software limitations, problems, and workarounds, section "Software limitations", subsection "Activity Planner" replace the current bullet: with the following text:
Defect 66684
In Chapter 2. Installation and upgrade notes, section "Installation program requirements", subsection "General prerequisites for installation programs" remove the following information: and replace the URL: with the following URL:
APAR IZ40926
In Chapter 2. Installation and upgrade notes, section "Application Prerequisites" replace the current bullet: with the following text:
Defect 66322
In Chapter 2. Installation and upgrade notes, section "Application Prerequisites" replace the current bullet: with the following text:

On Red Hat Linux® Enterprise Server, version 5 32-bit operating systems, the following packages are required:

On Red Hat Linux Enterprise Server, version 5 64-bit operating systems, the following packages are required:

APAR IZ44669
In Chapter 3. Software limitations, problems, and workarounds in section "Software problems and workarounds" in subsection named "Installation", add the following text to the current list:

APAR IZ44669

Problem: When installing Tivoli Configuration Manager version 431 on Red Hat Linux Enterprise Server version 5 in Japanese language, the installation wizard panels display garbled characters because some language font files are missing.

Workaround: Before installing Tivoli Configuration Manager version 431, perform the following steps:

  1. Download tnrwt_j.ttf, which is the Japanese language font file for IBM World Type Font, from official IBM Web sites such as:
    ftp://submit.boulder.ibm.com/download/typography/fonts/worldtype/
    archive/wt__/2002-02-13/
  2. Copy the tnrwt_j.ttf file to the JRE_HOME/lib/fonts directory on the server where you want to install Tivoli Configuration Manager version 431.
  3. Move to the JRE_HOME/lib/fonts directory.
  4. Run the command:
    ttmkfdir > fonts.dir
  5. Run the command:
    chkfontpath --add JRE_HOME/lib/fonts
Note:
An example for the JRE_HOME/lib/fonts directory is:
/opt/IBMJava2-131/jre/lib/fonts
APAR IZ51452
In Chapter 3. Software limitations, problems, and workarounds, section "Software problems and workarounds" subsection "Installation", add the following bullet:

License Management with License Compliance Manager Version 2.3 Fix Pack 4

This section contains new and updated information for IBM Tivoli Configuration Manager License Management with License Compliance Manager Version 2.3 Fix Pack 4:

Defect 65890
In Chapter 5. Deploying and configuring agents, section "Reassigning agents to divisions", in the sample XML input file described in the section, replace the line:
<!DOCTYPE agentRemappings SYSTEM "agtRemappings.dtd">
with the following line:
<!DOCTYPE agentRemappings SYSTEM "AgentRemappings.dtd">
Defect 65890
In Chapter 11. Command reference, section "agtremap" replace the xml_file description:

The absolute path to the XML file containing the list of agent IDs and Tivoli® OIDs to be remapped to different divisions. This file must be located in the same folder as the document type definition (DTD) file. The DTD file is copied to the path

$INSTALL_DIR/admin/SLM_Admin_Application.ear\slm_admin.war\webdoc\xml\
import\agentRemappings.dtd

with the installation of the License Compliance Manager administration server infrastructure element.

with the following text:

The absolute path to the XML file containing the list of agent IDs and Tivoli OIDs to be remapped to different divisions. Add to the XML file a DOCTYPE line containing the full path to the document type definition (DTD) file as shown in the following example:

<!DOCTYPE agentRemappings SYSTEM "C:\Program Files\IBM\TLM\admin\
SLM_Admin_Application.ear\slm_admin.war\
webdoc\xml\import\AgentRemappings.dtd">

[ Top of Page | Previous Page | Next Page | Contents ]